Skip to main content
An income invoice is the original bill. In the normal path, CargoWise sends an unstamped accounting invoice, Lambda stamps it through Facturapi, and the SAT UUID is stored and returned to CargoWise.

​
Expected path

1

CargoWise sends the invoice

CargoWise outbound pushes an unstamped income document to Lambda ingress. A Government Number is usually absent on this first push — that is expected.
2

Lambda validates

Lambda checks fiscal fields, customer data, amounts, and route configuration. Eligible documents move toward stamp submission.
3

Facturapi issues the CFDI

When the document is ready, Facturapi submits it to SAT. Lambda stores the SAT UUID and fiscal artifacts.
4

Artifacts return to CargoWise

Lambda outbound delivers the stamped XML and PDF to CargoWise inbound. Fiscal success and file delivery are tracked separately.
Success in the workspace is Stamped.

​
What to watch

Open the invoice timeline for the sequence of events. Use Statuses when a label is unfamiliar.

​
Corrections before stamp

If Lambda stops before a CFDI exists, the note explains what disagreed — missing fiscal fields, rejected customer data, unsupported values, or a route that is not configured to stamp. Some failures are reviewable in the workspace. Others need a corrected CargoWise source document. Lambda does not invent fiscal values to push the document through. After stamp, a later CargoWise push that disagrees with the issued CFDI is handled as source drift, not as a silent re-stamp. See Troubleshooting.

​
External stamps

If CargoWise reports a Government Number for a CFDI stamped outside Lambda, the workspace shows Stamped externally. Lambda records that evidence and does not create another stamp — see External stamps.