Skip to main content
Lambda uses the CargoWise payment-time evidence to express one payment in three related views: payment currency, parent document currency, and MXN value at the payment date.

Terms

For a cross-currency parent:
Lambda uses the recorded payment-time allocation. It does not invent a rate from current market data.

Precision and verification

Intermediate comparisons allow a small rounding tolerance where calculation order can differ. After issuance, Lambda checks the returned REP against the reconciled amount, currency, rate, balance, installment, and tax values.

Same currency

A receipt pays MXN 1,800 against an MXN parent:

USD payment against an MXN parent

A USD 100 receipt is valued at MXN 18.00 per USD and applies MXN 1,800 to an MXN parent.
The payment and parent currencies still differ, so the REP uses TipoCambioP = 18.000000 and EquivalenciaDR = 18.0000000000.

USD payment against a EUR parent

A USD 100 receipt is valued at MXN 18.00 per USD. It applies MXN 1,800 to EUR 90 of a EUR parent.
The REP uses TipoCambioP = 18.000000 and EquivalenciaDR = 0.9000000000.

Evidence rules

For a foreign parent, Lambda stops before issuance when the payment exchange rate or applied MXN is missing, invalid, or inconsistent. The same rule applies when the derived payment amount does not match the receipt or the returned REP changes the system-owned FX values. Payment currency, document currency, exchange rate, applied MXN, and EquivalenciaDR are deterministic reconciliation facts. Lambda cannot patch them automatically. See Payments for parent selection and balance rules.