CFDI is stamped on the web
A rule that runs through all of Repartya: the sale happens in the field (mobile), but the CFDI 4.0 invoice is always stamped from the web console, never on the phone. Here's why and how it flows.
The rule, in one line
The rep takes orders and collects on mobile; the CFDI stamping (the tax invoice) happens in the web console. They're two separate moments: first the commercial operation, then the tax document.
Why it works this way
Stamping a CFDI requires an online connection to the PAC (the authorized certifier), your digital seal certificates (CSD) and real-time tax validation. Mobile is designed to work offline and shouldn't hold certificates. Separating the sale from stamping avoids tax errors and keeps route work simple and fast.
The full flow
On the route, even offline.
The order and payment upload to the web console.
Validates the customer's tax data and the order contents.
The console sends to the PAC and gets the document with its fiscal folio (UUID).
By email (PDF and XML) or from the self-invoicing portal.
The detailed "how" of stamping lives in Billing & CFDI 4.0.
The customer's tax data
To stamp you need the customer's correct tax data: RFC, tax regime, CFDI use and ZIP code. Capture them well when creating the customer so stamping is straightforward: see Customers.
The SAT rejects the CFDI if the RFC, regime or ZIP code don't match the customer's tax record. Verify them before stamping.
Watch the walkthrough
Videos land in Phase 2. The layout is already set up to embed them with ES/EN captions and a transcript.
Common issues
- I can't invoice from mobile: that's by design; stamping is always on the web.
- Stamping was rejected: it's almost always the customer's tax data or an expired CSD; fix and retry.
- The customer didn't get the invoice: resend it from the invoice detail or share the self-invoicing portal.
More detail in Troubleshooting.