Ownership
CargoWise owns accounting truth
CargoWise owns accounting truth
Amounts, match lines, FX evidence, and transaction fields come from CargoWise. Lambda maps and
reconciles that evidence; it does not invent missing accounting values.
Facturapi and SAT own stamp validity
Facturapi and SAT own stamp validity
Field catalogs, RFC rules, PUE/PPD constraints, and stamp or cancellation acceptance belong to
Facturapi and SAT. Lambda surfaces those results in the workspace note.
Lambda owns safe continuation
Lambda owns safe continuation
Lambda decides when a document can stamp, wait for a parent, fail for review, or stop for
support. Safe continuation always beats forcing a stamp.
Document rules
PPD income gets REPs; PUE income does not
PPD income gets REPs; PUE income does not
Paid-later income expects payment complements. Paid-at-invoice income must not receive a REP.
Mixed receipts stamp only the PPD lines. Organizations may also use the REP eligibility
window.
Payment balances must stay consistent
Payment balances must stay consistent
Each installment needs a coherent previous balance, paid amount, and remaining balance. When
those disagree, Lambda pauses with labeled values in the note.
Parents must be fiscally usable
Parents must be fiscally usable
Payments and credits need verifiable parent evidence before they continue. Missing parents wait;
contradictory parents fail with a note.
Exchange-difference lines stay out of REPs
Exchange-difference lines stay out of REPs
CargoWise EXX lines are accounting adjustments and are excluded from the stamped payment
complement. See Exchange-difference lines.
No invented FX
No invented FX
Cross-currency payments need proven rate or MXN evidence from CargoWise. Lambda will not invent
a rate to make a stamp succeed.
Lifecycle rules
Do not duplicate an in-flight stamp
Do not duplicate an in-flight stamp
While a document is processing or waiting on SAT, do not submit a separate stamp for the same
work. Lambda and Facturapi already own that attempt. See Recovery.
Stamp success and CargoWise delivery are separate
Stamp success and CargoWise delivery are separate
A CFDI can be issued while XML/PDF delivery is still retrying. Delivery retries do not re-stamp.
Post-stamp drift is not a silent re-stamp
Post-stamp drift is not a silent re-stamp
If later CargoWise data disagrees with an already-issued CFDI, Lambda will not quietly stamp
again to match. Recovery waits for matching evidence or a deliberate support path — see
Corrective retry.
Failed vs system error
Failed vs system error
A document failure means continuing could create an invalid fiscal result. A system error means
configuration, provider availability, delivery, or recovery blocked a document that is not
necessarily wrong. The workspace may show Failed for both — the note says which.
External stamps are observed, not re-created
External stamps are observed, not re-created
When CargoWise reports a Government Number from outside Lambda, Lambda records Stamped
externally and does not create another CFDI. See External
stamps.
How to use these rules
- Read the workspace status — Statuses.
- Read the note for observed values and the classification ID.
- Match the ID to Failures or System errors.