Skip to main content

Short-pay reconciliation: cash, credits and gaps

Match cash to the invoices named in the remittance, then account for posted credits once. Keep unmatched payments and unexplained balances visible.

Sources checked

Match before deciding what to dispute

Use this review method for partial payments or one payment covering several invoices. Matching comes before deciding whether a deduction should be challenged. Oracle's JD Edwards documentation distinguishes applied credit memos from cash and allows an invoice to remain open for a residual.

This is a software-independent crosswalk, not an instruction to post, write off or settle an amount in your accounting system.

Gather the minimum records

Use an invoice-level receivables export, cash receipt, remittance detail and linked credit/adjustment register for the same period. A similar amount alone is not a match.

  • Invoice: reference, date, original amount and currency.
  • Payment: reference, invoice-level cash allocation and unallocated cash.
  • Credit: ID, amount, posting status, linked invoice and whether the starting balance already includes it.
  • Deduction: original reason/reference, plus any supporting adjustment record.
  • Duplicates: investigate repeated transaction IDs before summing or deleting rows.

Make the balance bridge explicit

Starting from the original invoice: original amount minus cash applied minus linked posted credits and other separately evidenced adjustments equals the remaining ledger balance. Show adjustment signs. Never subtract a credit again from a balance already net of that credit.

Tie invoice allocations back to the remittance total. Keep remittance-to-bank differences separate until references and settlement detail explain them. Do not allocate an unexplained total proportionally.

Worked examples: allocation and credits

Fictional USD records only. Invoices of 1,250, 800 and 450 total 2,500. Remittance allocations of 1,200, 725 and 450 total 2,375. Gaps of 50, 75 and 0 total 125.

Assume an applicable agreement explains the first 50. The output marks 50 for customer verification and 75 awaiting reason detail; it does not mark all three invoices disputed.

Separately: original invoice 3,000 minus cash 2,700 minus one posted credit of 200 leaves 100. Starting instead with the credit-net balance of 2,800 means subtracting only the 2,700 cash. These are arithmetic examples, not recovered cash.

Stop at an unsupported match

Leave cash unallocated if its invoice match is unproven; request remittance detail or a customer-confirmed allocation. Keep currencies separate unless an evidenced conversion explains settlement.

A residual does not establish validity, collectability or a due date. Use the evidence register for unresolved deduction components. For an assessment, describe the matching problem without transaction data and arrange the minimum useful records securely.

Download a working template

Sources

Describe the document work that is stuck

LogLyn prepares documents and review materials. You verify the facts and control every submission, counterparty contact, and payment decision.

Keep invoices, bank details, customer data, and credentials out of the public inquiry. We agree the minimum assessment inputs and transfer method before files move. Your supported estimate comes before a paid proposal; public upload is currently unavailable.

Describe the problem