Payment Receipt Reconciliation

Purpose

Payment Receipt Reconciliation turns the supplied records into cash-application sheet and reconciliation report with exact matches, grouped settlements, partials, unapplied receipts, short-pays, and variance totals. It keeps source facts, derived values, recommendations, and limitations separate so each conclusion can be checked.

Scope

Cover receipt_id, value date, payer, amount, currency, remittance invoice, open invoice, balance, credit note, fee, short-pay reason. Preserve source identifiers, dates, units, and wording needed to trace every result.

Excluded for cash application and unapplied receipts: changing source records, taking external actions, making a human approval or employment decision, and asserting facts absent from the corpus.

Data basis

• Process documents and tables containing receipt_id, value date, payer, amount, currency, remittance invoice, open invoice, balance, credit note, fee, short-pay reason.
• Company policy, rubric, schema, templates, and reference tables in scope.
• Run input for period, audience, entity, or threshold when it changes this run.

Result

Produce cash-application sheet and reconciliation report with exact matches, grouped settlements, partials, unapplied receipts, short-pays, and variance totals. Each material row and conclusion cites a document, section, page, row, field, or run input.

Quality criteria

• Every receipt-to-invoice matching and variance totals record is included or has an exclusion reason.
• Calculations state fields, units, denominator, and rule.
• Missing, contradictory, stale, and ambiguous values stay labelled rather than guessed.
• Facts, interpretations, and proposed next actions use separate fields.
• Supplied terminology, thresholds, and status values are used consistently.
• The final limitations section states what the corpus could not establish.

Instructions

Match on remittance invoice, payer, currency, amount, and open balance. Keep grouped and partial settlements traceable. Do not apply cash when payer or currency is ambiguous; classify fees separately. Preserve original values beside normalized values, cite every material finding, and use “not assessed” when required evidence or a rule is absent. When sources disagree, show both citations and explain the conflict. Keep row-level evidence in the supporting sheet and summarize only supported conclusions in the document.

Adapt before use

• Map the bank, remittance, and open-AR mapping fields and row citation convention.
• Add the governing policy, rubric, schema, or reference tables to the scope.
• Define thresholds, status values, units, and exception severity.