Apply incoming payments to open invoices
Payments arrive with remittance advice in emails, PDFs and portal downloads. The system reads each one, matches it to open invoices and posts the application. Short pays, overpayments and unknown payers are queued with a suggested explanation. Aimed at accounts receivable teams that apply cash by hand.
Function: Finance · Industry: Any industry
Apply incoming payments to open invoices
6 steps
At a glance
- Trigger
- A payment lands in the bank, or a remittance advice arrives.
- Typical inputs
- Bank lines and lockbox files
- Remittance advice (email, PDF or portal)
- Open invoices and credit memos
- Customer aliases and parent-child account mappings
- Systems it usually connects to
- NetSuite
- QuickBooks
- Gmail
- Stripe
- How the work splits
3 rules, 2 model, 1 person steps
How it runs, step by step
6 steps, each tagged by what does the work. Rules are fixed logic, a model reads or drafts, and a person decides.
- Rules Fixed logic in code
- Model AI reads or drafts, with a confidence score
- Person A named person decides
- 1
Read the remittance
ModelA model pulls payer, invoice numbers, amounts and deductions from emails and PDFs, in whatever format each customer uses.
- 2
Match to open items
RulesInvoice numbers and amounts are matched exactly, and customer aliases are resolved to the right account.
- 3
Propose a match when references are missing
ModelWhen there is no invoice number, a model suggests the combination of open invoices that fits the amount and payer.
- 4
Post the application
RulesMatches above your confidence bar are applied automatically, and deductions are coded to your standard reason codes.
- 5
Resolve the leftovers
PersonA collector handles short pays, overpayments and unidentified payments, with the system's suggested reason attached.
- 6
Update collections status
RulesApplied invoices leave the dunning list, and short-paid invoices are marked for follow-up.
Where people approve
The decisions that stay with your team, whatever the confidence score says.
- A collector confirms every model-proposed application that is not an exact match.
- Credits and write-offs need a supervisor.
- Unidentified payments are never applied until the payer is confirmed.
KPIs to track
What to measure, before and after. Targets come from your own baseline.
- 01Share of cash applied without manual work
- 02Unapplied cash balance and its age
- 03Days between payment received and applied
- 04Reminders sent in error for invoices already paid
Questions about this workflow
What about customers who deduct amounts for their own reasons?
Deductions are captured as separate lines with a reason code and sent to the collector who owns the account. The model can suggest the reason from the remittance text, but a person decides whether to dispute it.
Does it work with lockbox files?
Yes. Lockbox and bank files are one input among several. Scanned checks with handwriting are the weakest case and are routed to a person when confidence is low.
Which steps use rules, a model and a person?
Rules: match to open items; post the application; update collections status. Model: read the remittance; propose a match when references are missing. Person: resolve the leftovers. Rules are fixed logic in code. A model reads or drafts and reports its confidence. A named person decides.
What do we need to start?
Typically: bank lines and lockbox files; remittance advice (email, PDF or portal); open invoices and credit memos; customer aliases and parent-child account mappings. You also need read access to NetSuite, QuickBooks, Gmail and Stripe, or the equivalents you use. A workflow audit measures your volumes and past cases first, then gives a fixed price for the build, so you can decide with real numbers.