Skip to main content
Lambda stores fiscal files before it treats CargoWise delivery as complete. Every file belongs to one fiscal operation and keeps its source and integrity evidence.

File sources

Lambda does not replace provider XML with a locally generated XML. The stored stamped XML is the provider result.

Design snapshot

When Lambda reserves a stamp attempt, it freezes:
  • the requested Detailed or Minimal design
  • the logo identity and version
  • whether the logo is synchronized to the bound Facturapi organization
  • the resolved design and fallback reason
If Detailed was requested but the synchronization proof is missing, stale, or tied to another Facturapi organization, Lambda uses Minimal for that attempt. A later logo or setting change cannot switch an in-flight attempt.

Immutable storage

Stored artifacts include size, hash, source, design provenance, and attempt identity. Recovery may backfill a missing file from the exact issued evidence. It does not replace an existing historical artifact with a newer file. Issuance XML and cancellation XML are separate. Cancelling a CFDI does not overwrite the original CFDI file.

CargoWise delivery

Lambda outbound sends stored files to CargoWise inbound with the configured target, DocManager module, document type, and CargoWise source key.
  • Live stamps start normal delivery after fiscal verification.
  • Test stamps stay in the test lane and do not start normal live delivery.
  • Income and credit artifacts use INV.
  • REP artifacts use RRC and the configured payment complement type.
  • Accepted cancellation XML uses the cancellation document type, or the normal XML type when no cancellation type is configured.
Each file purpose has its own delivery identity and retry state. XML delivery can complete while PDF delivery is pending. A cancellation receipt can fail without reopening the original stamp.

Read each outcome separately

If the CFDI exists and delivery fails, use Recovery. Do not issue a replacement CFDI to solve a delivery problem.