Why the allocation needs a record
A partial payment can be applied to one invoice or split across several. The allocation should follow the customer's remittance and the approved rule. A split that is invented to make the aging report look better hides the real balance. Name the owner in the same line as the action.
The record should show the receipt, the invoices, the amount applied, and the amount open. The next reviewer should be able to follow the money without opening a chat. Review the first few notes together before the process expands. Keep the boundary visible in the place where the work is assigned.
Record the receipt and the remittance
Write the receipt date, the amount, and the source. Attach the remittance or the bank reference. A payment without the remittance is a question, not a clean match. A short note with four fields is easier to use than a long narrative.
Record the customer's instruction if one exists. If the customer said the payment is for invoice 2201, do not split it to cover 2198 because the aging looks worse. Test the rule on one real account before applying it to the queue. Record the exception and the person who approved it.
Record the allocation and the open balance
Write the amount applied to each invoice and the reason. Record the remaining balance and the owner. A partial payment without an owner will sit. Keep the boundary visible in the place where the work is assigned.
If the allocation changes, record the change and the approver. Do not overwrite the original allocation without a trace. Record the exception and the person who approved it. A short note with four fields is easier to use than a long narrative.
Explore the related specialist service to define scope, ownership, and evidence.
Handle the disputed portion
If the customer withheld part of the payment, record the claim and the amount. Keep the disputed amount separate from the undisputed payment. A dispute that is mixed into the allocation is hard to resolve. Keep the evidence with the record rather than in a separate log.
Route the dispute to the named owner and set a response date. The payment record should show the link. Review the first few notes together before the process expands. A control that depends on memory is not yet a control.
Review the allocation with the controller
Review a sample of partial payments with the controller. Check the source, the allocation, and the open balance. A sample that includes a split payment is more useful than one that only includes clean matches. Name the owner in the same line as the action.
Update the allocation rule if the sample shows a recurring problem. The goal is a record that explains the balance, not a faster split. Record the exception and the person who approved it. Write the deadline as a date and a local time.
Financial Accounting Standards Board provides public guidance that can inform a documented review.
Keep the record with the receipt
Store the allocation with the receipt and the invoice. A later audit may need to see the original instruction and the change. Update the template when the same question appears twice. Use the same format for every handover so the next reader can scan it.
Review the format quarterly. A new payment channel may require a new field. Review the first few notes together before the process expands. Use the same format for every handover so the next reader can scan it.
Common questions answered
How should a partial payment be allocated?
Follow the customer's remittance and the approved rule, and record the amount applied and the open balance.
What should happen to the disputed portion?
Keep it separate, route it to the named owner, and set a response date.
Define one reviewable receivables workflow.
Bring the queue, owner, source records, and exceptions you need to make visible.
Book a free consultation