Partial payment matching: check invoice allocations

What does partial payment matching actually establish?

Partial payment matching records how much of a particular receipt has been assigned to a particular invoice. An invoice records an amount requested from a customer. An allocation records a specified part of a receipt against that invoice. Seeing money in a bank export does not, by itself, establish which invoice it settles.

Keep three lists separate: invoices, unique receipts and allocation lines connecting them. One receipt can fund several invoices. One invoice can receive several receipts over time. A receipt identifier appearing on two allocation lines is therefore not automatically a duplicate. The allocation line needs its own identity, and the total assigned from the receipt must stay within its available amount.

This exercise covers one fictional customer, one currency and records available through the end of 29 October 2026. There are no credit notes, discounts, refunds, exchange differences or bank charges. If those exist in your records, extend the model before using its result. The overdue invoice guide addresses follow-up communication; this exercise stops before sending any collection message.

Preserve the invoice and receipt registers first

All identifiers, amounts and dates below are invented teaching inputs. They are not a bank statement, an Anar client case or evidence of money recovered. The arithmetic has been executed separately, but no bank connection or accounting application has been operated. You can reproduce the result using the published rows without granting access to any live financial account.

The invoice register totals 230. The unique receipt register totals 175. Save these independent controls before joining any tables. If you copy the full receipt amount beside every allocation and sum the resulting column, a split receipt will be counted repeatedly. The fact that every row looks plausible does not protect the grand total.

Label the source snapshot V1 and record its cutoff. Preserve later receipts in a new version rather than silently changing the starting exercise. The cash-flow worksheet needs receipt dates for another purpose. A correct cash date and a correct invoice allocation remain separate checks.

Use allocation lines without inventing their authority

The fictional source supplies three allocation instructions: A1 assigns 100 from P1 to I1; A2 assigns 20 from P1 to I2; A3 assigns 40 from P2 to I2. These are given inputs, not recommendations about which invoice deserves payment first. Missing customer instructions cannot be replaced by a guess that the oldest invoice must be the right one.

For P1, 100 plus 20 equals its receipt amount of 120. For P2, the assigned 40 equals its available 40. Both receipts are fully allocated in this worksheet. P3 has no allocation instruction, so its 15 remains unallocated. Do not assign it to I3 merely because that invoice remains open or because the amount would reduce the total outstanding.

Microsoft documents specified partial application amounts and allocation across multiple entries. That supports the conceptual distinction, not a claim that this file performs Business Central posting. The second official page also limits split application to entries for the same account. Our one-customer exercise stays within that boundary without proposing a cross-customer accounting procedure.

Check the invoice direction and receipt direction separately

First total allocations by invoice. I1 has 100 assigned and zero remaining. I2 has 20 plus 40 assigned, leaving 80 minus 60, or 20. I3 has no allocation in the complete supplied list, leaving its full 50 open. That zero assigned amount follows from checking the full allocation list; it is not a rule that missing source data means zero.

Now record both control identities: invoices 230 equal allocated 160 plus open 70; receipts 175 equal allocated 160 plus unallocated 15. Subtracting all receipts from all invoices gives 55, but that is not the invoice-level open amount. The worksheet still has 70 open on invoices and 15 whose destination is unresolved. Netting them silently conceals the missing relationship.

Nor does allocation measure profit. The profit margin guide needs sales and cost information not present here. Use a precise file title such as “allocation review” rather than “accounts approved” so another person does not mistake these controls for a complete financial sign-off.

Keep duplicate and excess-allocation tests visible

In a separate negative test, import A3 twice with the same identifier and values. Flag the repeated allocation rather than adding another 40. If the same allocation identifier arrives with different values, retain both source rows and request clarification. Choosing the convenient amount would manufacture a clean result rather than verify the records.

For another test, add A4 assigning a further 10 from P2 to I3. P2 now has 50 allocated against a receipt of 40. The ten-unit excess makes the proposed allocation invalid. Do not delete the evidence to make the worksheet balance. Save the failed test separately from V1, which has not been changed.

Invoice over-allocation is a separate failure. If I1 receives 110 against its invoice amount of 100, its raw remaining amount is negative ten. Do not clamp that value to zero and hide the excess. Unknown receipt identifiers, unknown invoice identifiers, wrong customer, incompatible currency and dates beyond the cutoff also belong in the manual-review list.

Negative receipts and credit notes need an explicitly extended model; the exercise accepts only positive receipts and allocations. A risk record can preserve the missing evidence and the role responsible for clarification. A mathematical total cannot establish that a payment reference is genuine or legally conclusive.

Finish with a saved ledger and unresolved-items list

On Windows, search Start for Notepad, open it and create a blank document. Title it “Allocation review V1 — fictional exercise”. Create sections named Invoices, Receipts, Allocations and Exceptions. Copy every row of the three source tables above into the first three sections as text, preserving identifiers, amounts and dates. Check unique identifiers within each source list, then check each allocation references an existing invoice and receipt within scope. Calculate totals manually from valid rows; Notepad does not calculate them. Keep rejected test rows and reasons separate rather than adding them to the V1 source.

Snapshot: V1, end of 2026-10-29
Scope: one fictional customer, one currency
Invoices: 230
Unique receipts: 175
Allocated: 160
Invoice open amount: 70
Unallocated receipt amount: 15, P3
Next review: confirm destination of P3
No live ledger changes performed

In Invoices, record I2 as original 80, assigned 60 and open 20. In Receipts, record P3 as received 15, assigned zero and unallocated 15. Retain the summary block and the unresolved P3 question. Choose File → Save As, select Documents and save allocation-review-V1.txt. If the name exists, choose another rather than overwrite it. Close Notepad, then reopen that file from Documents in File Explorer. Find all three source lists, the I2/P3 details and both controls, 230=160+70 and 175=160+15. Missing detail means the handoff is incomplete. Do not label readback completed until you actually perform it.

For a fifteen-minute exercise, spend roughly five minutes preserving inputs, five calculating controls and five running a negative test and reopening the saved file. This is a proposed work plan, not a measured speed claim. Record a review owner and the exact missing evidence in the decision register. Stop with an honest unresolved item rather than implying that a teaching spreadsheet has updated a bank or certified the accounts.