What you get
- Automatic intake of income invoices, payment complements, credits, and related cancellations from CargoWise
- Validation and reconciliation before any stamp attempt
- CFDI issuance through Facturapi, with SAT UUID and fiscal artifacts stored in Lambda
- Delivery of stamped XML/PDF (and cancellation receipts) back to CargoWise
- Clear workspace statuses and notes when a document is waiting, failed, or needs support
What this is not
Stamping does not replace CargoWise as the source of accounting truth. Amounts, match lines, FX evidence, and transaction fields come from CargoWise. It also does not invent missing fiscal values. If a required field, parent stamp, balance, or exchange rate is missing or contradictory, Lambda pauses instead of guessing. Analytics is separate. Reporting Postgres does not store invoices, Facturapi responses, or SAT artifacts.Who this is for
Accountants and operations teams use the invoice workspace to follow documents and resolve reviewable issues. Admins connect CargoWise, configure stamping credentials, and keep outbound delivery working. Support uses system-error classifications when configuration, provider availability, or recovery blocked a safe continuation.Start here
How it works
The end-to-end path from CargoWise to Facturapi and back.
Income invoices
The normal bill path and what success looks like.
Payment complements
REPs, PPD vs PUE, and waiting for parents.
Credits and cancellations
Credit paths, SAT cancellations, and blocked chains.
Special behaviors
Parent-cancel credits, REP windows, external stamps, reversals, and EXX lines.
Rules
The constraints Lambda follows every time.
Statuses
What each workspace label means.
Failures
Document and provider issues that stop a stamp.
System errors
Configuration and recovery issues that need ops or support.
Retry
Recovery and corrective paths inside stamping — resume, remap, and what Lambda refuses.