Skip to main content
Each document is mapped to one route before provider submission. The route and its required settings must be usable before Lambda performs the fiscal action.

​
Fiscal routes

All five routes are enabled by default. When a route is disabled, Lambda records a settings finding and does not perform that action. A full-value credit has one controlled alternative: when parent cancellation is disabled, Lambda can stamp a Tipo E credit if that route is enabled and the required parent evidence is usable. Lambda checks the route again before issuance. If the settings changed after capture, Lambda stops instead of silently choosing a different fiscal action.

​
Facturapi environment

Test and live stamping use separate Facturapi readiness. The requested environment must have a usable organization binding and certificate state. A document does not switch environments during an attempt.

​
REP eligibility window

The REP eligibility window has:
  • Enabled
  • Window (days) from 0 through 365
When enabled, it can treat a parent as PUE when a payment arrives within the configured Mexico City calendar-day window. Lambda freezes the decision with the payment intent, so a later setting change does not rewrite an in-flight REP. See Payments for the complete decision.

​
Invoice design

The Invoice design setting offers: Detailed is the default. Lambda uses Minimal when the exact attempt cannot prove that the current logo is synchronized to the current Facturapi organization.

​
CargoWise delivery

Lambda outbound requires a CargoWise outbound URL and usable connection credentials. File allocation also uses:
  • CFDI XML doc type
  • Cancellation XML doc type
  • CFDI PDF doc type
When Cancellation XML doc type is empty, Lambda uses CFDI XML doc type for the cancellation XML. DocManager modules are selected by document: A missing setting blocks only the action that needs it. For example, a missing CargoWise target can stop delivery after the CFDI has already been issued and stored.