By Eric Kuvykin. Substantially revised October 17, 2026. The original publication date and URL are retained.
Start with the customer’s instruction
A single business payment may cover several invoices, a credit and a short-paid amount. The bank entry alone may not explain that allocation. Before automating the match, define how the accounts-receivable team obtains and preserves the customer’s remittance instruction.
Create a standard request for invoice references and an explanation of adjustments. Keep it short enough for customers to use. A consistent customer identifier is helpful when a trading name differs from the legal entity that owes the invoices.
Keep unapplied amounts visible
If the instruction is missing or ambiguous, place the payment in a review queue. Record the bank reference, amount, customer contact and next action. Follow the business’s reviewed accounting policy rather than silently choosing an allocation to make the ledger appear balanced.
Separate an unexplained short payment from a confirmed discount, credit or dispute. Each requires different evidence. Preserve the original invoice and the customer’s message so a later reviewer can understand why an amount remains open.
Test a realistic combined payment
Use a sample containing two fully paid invoices, one partial payment and a credit. Verify how the accounting system records the allocation and how a customer statement displays it. Ask whether an integration can reverse an incorrect allocation without erasing its history.
For a New Jersey supplier serving customers in New York and Florida, retain the correct customer entity and invoice series. Do not let a similar company name or shared contact cause a payment to be assigned to the wrong account. This is a record-control example rather than a state-specific allocation rule.
Evaluate speed separately from matching quality
The Federal Reserve’s FedNow resources describe instant payments accessed through participating financial institutions. Faster receipt does not by itself supply the remittance information needed for allocation. Ask the bank or provider how payment references reach the accounting workflow.
Measure the age and value of unapplied cash alongside collection totals. If a new payment method reduces transfer time but increases manual investigation, include both effects in the evaluation. Avoid declaring an invoice resolved merely because money has appeared in the bank.
End each review with assigned follow-ups and documented resolutions. A good allocation process lets the customer, support team and bookkeeper see the same explanation of what was paid and what remains outstanding.
References and related reading
Primary resource checked for this review: Federal Reserve’s FedNow frequently asked questions. Confirm the current requirements and implementation with the responsible provider or appropriate adviser.
Continue with B2B Payments: Connect the Invoice, Remittance and Bank Record and Payments Data: Build a Weekly Operating Review From Source Records.
For state and local business resources alongside this operating checklist, use the New Jersey business operations guide on All State Merchants.
