Payroll Precheck
Compare your own declarations and review exceptions before continuing your payroll process.
From sources to an explicit review
1. Import your own sources
Use the CSV template and/or payroll XML for the same project. With only one source, comparisons requiring the other remain unknown; missing records are not invented.
2. Compare declarations
Inspect XML structure, declared amount sums and exact source matches separately. An unavailable comparison does not prove absence, a wrong employee or an executed payment.
3. Review and document
Complete the checklist with explicit decisions and version control. Review does not change original observations or certify compliance; exceptions are exported for human review.
Capabilities confirmed by the service
The catalog separates available functions from the consumer and parser that require configuration. An unconfirmed capability is shown as unavailable; local code does not establish production readiness.
Pre-payroll CSV prechecks
Checking…CFDI4 XML with Nómina1.2
Checking…Pinned local XSD structural validation
Checking…Declared amount sums
Checking…Exact source comparisons
Checking…Human review checklist
Checking…Private JSON and TXT exports
Checking…ViciousByte evidence signature
Checking…Statutory payroll calculations
Legal calculations are not performedFiscal authenticity certification
Does not verify fiscal authenticityPayroll payments and payouts
Payments and payouts are not performedAI processing
AI processing is not performed
What each check means
Structural validation uses a pinned local set of official SAT XSDs for CFDI4, Nómina1.2 and TimbreFiscalDigital1.1. Its snapshot date is published with the limits. It does not query SAT or download schemas supplied by a document. Unsupported complements are reported explicitly; a stamp’s presence establishes neither authenticity nor current temporal catalog validity.
Declared leaf amounts are summed once and compared with totals and net values using Decimal, without rounding or currency conversion. Nested subsidy or compensation data are not added as another payment. Optional totals missing while components are present remain missing or unknown, rather than a passing zero.
Comparison uses declared RFC, period start and end, payment date, payroll type and currency. Duplicate CSV or XML groups remain ambiguous; receipts are never silently selected or added. Without a project company RFC, the employer remains unconfirmed. A match does not verify identity, employment or payment.
The report separates accepted sources, XSD scope, arithmetic checks and source comparisons. Windows and visible finding limits state coverage and truncation: no visible exceptions do not establish universal absence or fiscal compliance.
The checklist records source ownership, employee and period, amounts, legal review and exceptions. These are versioned human assertions; they do not alter technical results. JSON, TXT and CSV exports are private. The optional ViciousByte attestation signs a manifest of source, result and review hashes; it is not a SAT stamp or client-side cryptographic verification.
Formats, limits and budget
Strict UTF-8 CSV, with optional BOM, using the template columns. UTF-8 CFDI4 type N XML with one Nómina1.2 complement. MXN profile with nonnegative amounts of up to 18 integer digits and 2 decimals, YYYY-MM-DD dates and O/E payroll types; unsupported precision is explicitly rejected without rounding. Payment date is compared as a declaration, without inventing a legal timing rule.
Payroll Precheck requires its own pilot grant or paid project period and payroll_attempt budget, independent of other modules and plans. An admission covers the bounded comparison job. Proposed plans and packs are shown subject to review; purchasing requires approval; there are no automatic charges or unlimited usage.
Current limits or policy could not be confirmed. Capacity, budget and retention are not assumed; check the dashboard before uploading information.
Private data, minimization and deletion
Original XML may contain names, CURP, bank details and other sensitive information. The derived report minimizes data with masked RFCs and hash references: they are pseudonymous, not anonymized. A user-supplied employee reference may also contain sensitive information. Lists show counts; originals and evidence have private account/project access. No AI processing or transfer to AI providers is performed.
Expiry remains fixed from admission. Expiry or a deletion request revokes reads and queues purging of originals, reports and reviews; immediate physical deletion is not promised. Cancelling or deleting does not turn an executed attempt into a quota refund.
Payroll Precheck requires a pilot grant or current paid project period; CFDI Guard or Document API access does not activate it. Requesting access records pending interest without granting permissions or starting payments.
Plans and additional units
Prepaid 30-day base per project and service. Manual renewal after expiry; no automatic charges or automatic overage purchases.
Checking commercial terms…
Proposed pricing
A public view of a commercial proposal that has not been approved. These amounts are not available purchase offers and do not enable charges. Final terms may change after review.
Proposal dated October 25, 2026 · USD · base amounts exclude VAT (16%) · 30 days · manual renewal · no automatic chargesStarter
USD 9.00
5 payroll attempts
Project base for one 30-day periodPro
USD 25.00
15 payroll attempts
Project base for one 30-day periodBusiness
USD 59.00
40 payroll attempts
Project base for one 30-day period5 payroll attempts
USD 10.00 · Proposed · subject to review
10 payroll attempts
USD 18.00 · Proposed · subject to review
20 payroll attempts
USD 32.00 · Proposed · subject to review
Request pilot access
Register a Payroll prevalidation request for your account. This does not create a subscription, activate permissions or execute a payment.