Resolve PUE or PPD
Lambda uses this priority order:- Recognized
PUEorPPDvalues in direct custom fields on the AccountingInvoice. - The CargoWise
PostDateandDueDateas Mexico City calendar dates. - A failure when the evidence is missing, invalid, or conflicting.
Direct evidence wins even when the dates disagree. Date comparison uses calendar days, not elapsed
hours. A PPD income CFDI uses SAT payment form
99, meaning the payment method will be defined later.
Normal path
1
Receive and capture
CargoWise outbound sends the invoice. Lambda stores the immutable source and identifies the
workspace and CargoWise document key.
2
Prepare and reconcile
Lambda reads customer data, lines, taxes, totals, currency, dates, payment evidence, and the
enabled PUE or PPD route.
3
Issue
Facturapi submits the prepared CFDI to SAT. The exact provider outcome is recorded.
4
Verify and deliver
Lambda verifies the returned UUID and fiscal values, stores XML and PDF, and starts Lambda
outbound delivery.
Existing Government Number
If CargoWise already includes a valid Government Number, Lambda records Stamped externally and does not call Facturapi to create another CFDI. Lambda stores the UUID and source evidence so it can be used as parent evidence when a later payment or credit needs it. An external stamp is not a Lambda-owned provider record. Lambda cannot perform its normal cancellation or replacement flow for that CFDI.CargoWise re-pushes
- An exact duplicate delivery is idempotent and restores missing durable work when needed.
- A delivery with different CargoWise data is normal new ingress with its own immutable capture. It never rewrites an older capture.
- After issuance, Lambda keeps the issued CFDI and its fiscal snapshot unchanged.
GovernmentNumber. Do not use the absence of a later push as proof that Lambda did not stamp.
See Files and delivery for artifact ownership and
Recovery for safe retry behavior.