The complete path
1
CargoWise sends the source
CargoWise outbound sends accounting XML to Lambda ingress. Lambda authenticates the workspace
and accepts supported income, payment, and credit shapes.
2
Lambda saves the evidence
Lambda stores the source, document identity, and first work request together. Accepted work
therefore has a durable source that later processing and recovery can use.
3
Lambda prepares the fiscal intent
Lambda reads CargoWise amounts, match lines, dates, currencies, exchange-rate evidence, parent
relationships, and transaction fields. It turns those facts into one versioned fiscal intent.
4
Lambda reconciles the document
Lambda checks totals, taxes, parents, PUE or PPD evidence, installments, balances, currency
conversion, and the enabled route. A healthy missing or unstamped parent moves the document to
Waiting for parent invoice.
5
Facturapi works with SAT
Lambda sends an eligible request to Facturapi. Facturapi applies its CFDI and SAT validations,
then submits the operation to SAT.
6
Lambda verifies and stores the result
Lambda verifies the returned UUID, totals, payment complement, or cancellation result. It stores
the XML, PDF, integrity evidence, and the file-design snapshot used for that attempt.
7
Lambda returns the files
Lambda outbound assigns each file to the correct CargoWise DocManager module and document type,
then sends it to CargoWise inbound. A delivery retry never repeats the stamp.
Main decisions
The detailed rules live with the document they affect: Income invoices,
Payments, and
Credits and cancellations.
Ownership
Lambda uses CargoWise facts and surfaces Facturapi or SAT errors. It does not invent accounting
facts or duplicate vendor fiscal rules.
Independent results
If delivery fails after issuance, the SAT UUID and stored files still exist. The next step belongs
to delivery Recovery, not a new issuance.