Overview - Lambda

Stamping is Lambda’s fiscal control plane for CargoWise. It turns accounting evidence into CFDIs, verifies the result with Facturapi and SAT, stores the fiscal files, and returns the files through CargoWise inbound. Stamping protects the boundary between two kinds of truth:

CargoWise owns accounting facts and relationships.
Lambda owns mapping, reconciliation, fiscal workflow, result verification, and delivery.
Facturapi and SAT own provider and legal validation.

What it handles

CargoWise input	Possible result
Unstamped income invoice	PUE or PPD income CFDI
Payment receipt	REP for eligible PPD parents
Credit note	Related or standalone Tipo E credit, or full-value parent cancellation
Paired receipt reversal	Cancellation of the original REP, or completion without a CFDI when no REP existed
Invoice with a Government Number	External stamp recorded without creating a second CFDI

The complete boundary

CargoWise outbound
        |
        v
Lambda ingress: capture, identify, map, reconcile
        |
        v
Facturapi and SAT: issue or cancel
        |
        v
Lambda: verify and store XML and PDF
        |
        v
Lambda outbound
        |
        v
CargoWise inbound

The first CargoWise push normally does not contain GovernmentNumber. CargoWise usually writes that value after a successful stamp. A later push can therefore be a duplicate, a source correction, or an external stamp observation. These cases do not all mean “stamp again”.

What Stamping guarantees

The original CargoWise source is retained for review and recovery.
Lambda reconciles the fiscal request before it calls the provider.
A provider result that may already exist is verified before another create request is allowed.
XML, PDF, and cancellation files remain tied to the exact fiscal operation that produced them.
Fiscal completion and CargoWise delivery remain separate. A delivery retry never issues another CFDI.

Read the result in this order

Check the fiscal status and SAT UUID.
Check whether the required XML and PDF files are stored.
Check each CargoWise delivery result.
If something stopped, read the public failure type and the action offered in the workspace.

Use Behavior for the full path. Use Statuses for the workspace labels and Reliability for the control model behind them.

​What it handles

​The complete boundary

​What Stamping guarantees

​Read the result in this order

What it handles

The complete boundary

What Stamping guarantees

Read the result in this order