RouteurStable

Propose payment allocation

Analyzes a company's open receivables and proposes candidate allocations for a received amount, then routes according to factual matching quality.

Contexte financier

Propose payment allocation

Finance

Typed result

Vue d’ensemble

Analyzes a company's open receivables and proposes candidate allocations for a received amount, then routes according to factual matching quality.

Exemple

Receive EUR 1,000 without a usable reference and determine whether it exactly matches one invoice, several invoices, an underpayment, or an ambiguous situation.

Decision routes

exact_match

Match exact

A candidate allocation explains the amount exactly with sufficient factual matching.

Recommended actionApply the proposal with reconcile_payment if your policy does not require additional review.

underpayment

Sous-paiement

The received amount is lower than the amount of the most plausible target.

Recommended actionDecide whether the partial payment should be applied or reviewed manually.

overpayment

Surpaiement

The received amount exceeds the amount of the selected candidate receivables.

Recommended actionApply only an allocation consistent with your policy and explicitly handle the remainder.

ambiguous

Ambigu

Several plausible allocations remain in competition without a sufficiently factual winner.

Recommended actionRequest review or use additional data before applying anything.

unmatched

No match

No usable candidate allocation was found within the configured constraints.

Recommended actionBroaden search data or explicitly mark the payment unmatched according to your process.

Parameters 11

companyRequisCompany

Buyer company used as the context for payment intent or reconciliation.

amountRequisamount

Operation amount in minor monetary units. When optional, the node may use the residual amount defined by its contract.

currencyRequiscurrency code

ISO 4217 currency used to interpret all amounts in the operation.

invoiceOptionnelInvoice

Invoice used to bound or derive the financial context of the operation.

orderOptionnelOrder

Order used to bound or derive the financial context of the operation.

source_referenceOptionnelstring

Durable reference from your system used for correlation or idempotency when the operation supports it.

invoice_window_past_daysOptionnelinteger

Past time window in which open invoices remain candidates for reconciliation.

invoice_window_future_daysOptionnelinteger

Allowed future window for candidate invoices when policy permits it.

max_invoices_per_combinationOptionnelinteger

Maximum number of invoices combined in a candidate proposal.

max_line_items_per_combinationOptionnelinteger

Maximum number of invoice lines considered in a candidate combination.

max_candidatesOptionnelinteger

Maximum number of alternative proposals retained for the matching result.

Outputs 2

selected_routeenum

Matching route chosen from the factual outcome of the allocation proposal.

allocation_proposalreceivable allocation

Structured proposal for allocating the received amount, including the best combination and the information needed to decide whether to apply it.

Behavior

The node searches candidate invoices in the configured windows, bounds combinatorics, then returns the best proposal and a route describing the matching result.

Key point Always distinguish the canonical object created by Ormuz from any external effect. A payment or refund intent in draft status does not prove that a provider executed the movement of funds.

Limits and responsibilities

The node proposes an allocation; it changes no balance until reconcile_payment runs.
Window and combinatorics limits influence candidates considered and must be sized according to your volume and matching policy.