Reconcile Payments

Reliability

Two identical requests produce identical output, and re-ordering the arrays changes nothing: payments are sorted by date then id, invoices by due date then id, before any matching starts. Passes run in order and never reuse a payment: 1 exact reference and exact amount, 2 reference under your normalization with amounts inside your tolerance, 3 amount inside your tolerance and date window, 4 combinations of 2 to maxCombinationSize payments that settle the invoice, 5 a single part payment when allowPartial is on. The order is part of the answer, so it is published rather than left to be discovered: pass 5 is last because a payment spent as a partial is gone, and two payments that together settle an invoice should be reported as that rather than as one partial plus an orphan. Passes 1 to 4 never accept an underpayment beyond your tolerance, so allowPartial can only add matches, never move them. The search is bounded at 250,000 candidate comparisons, so a book too large to match is refused rather than left running. Unknown top-level request properties are refused rather than ignored, so a misspelled rules or payments never looks like one we honoured. RECONCILE_INPUT_INVALID — trigger: an empty payment or invoice list, a missing or blank id, an amount or date we cannot read, an amount finer than the currency's minor units, or an entry carrying a property we do not define; retryable: no, the same payload always fails; next: check the entry position we name in the details, dates as YYYY-MM-DD and amounts as plain decimal strings. CURRENCY_UNKNOWN — trigger: the batch shares one currency code but it is not one we support; retryable: no; next: send a supported ISO 4217 code — the same code this pack's other skills accept. RECONCILE_ID_DUPLICATE — trigger: two payments or two invoices share an id, so a match could not be attributed to one of them; retryable: no; next: make ids unique within the call — we name the field and the position, never the id itself. RECONCILE_CURRENCY_MIXED — trigger: the batch carries more than one currency code and we never convert; retryable: no; next: split the batch per currency, converting with finance.fx_rate_apply first if you need to. RECONCILE_RULES_INVALID — trigger: an unknown rule name, a strategy or referenceMatch outside the accepted values, a negative tolerance, a date window outside 0 to 365, or a combination size outside 2 to 4; retryable: no; next: correct the rule we name and call again. RECONCILE_LIMIT_EXCEEDED — trigger: more than 5,000 payments or 5,000 invoices in one call, whether you overshoot by one row or by a thousand — the limit is ours and it is the rule you are told you broke, with your actual count in the details; retryable: no; next: reconcile in batches, by period or by customer. RECONCILE_SEARCH_LIMIT_EXCEEDED — trigger: the rules you set need more than 250,000 candidate comparisons, which usually means combinations over a large book; retryable: no, the same rules always cost the same; next: reconcile in smaller batches, narrow the date window, or turn combinations off.