Detect the payment
The incoming amount, bank reference, and date picked up from the feed.
[Cash application]
One payment, several invoices, and the allocation still sitting in a remittance email. That gap is where unapplied cash lives.
The incoming amount, bank reference, and date picked up from the feed.
The email that explains how the payment should be allocated.
Invoice references read, totals checked, partial payments kept visible.
Cash application workflow
One consolidated payment, several invoices, and the allocation still sitting in a remittance email. That gap is where unapplied cash accumulates.
The incoming payment is picked up from the bank feed with its amount, reference, and date.
The remittance email that explains the allocation is located in the customer thread.
Invoice and project references are read out of the remittance and matched to open items.
Totals are checked against the invoices, including partial payments and short payments.
The match is posted, or the exception goes to a person with the evidence attached.
| Amount | Agrees to the cent |
| Reference | ML-1042 appears on the invoice and in the remittance |
| Remittance | Applies the full balance to a single invoice |
| Next step | Post the match, or hold for review before applying |
One payment, many invoices
A single transfer often settles several invoices, spans projects, or arrives short. The workflow reads the intended allocation rather than guessing from the total.
| Invoice | Remittance line | Amount | State |
|---|---|---|---|
| INV-1051 | Applied in full | $6,000 | Ready |
| INV-1055 | Applied in full | $2,400 | Ready |
| INV-1058 | Short by $180 | $800 | Short payment |
Exceptions
An unclear reference is not a failure. It is a task for a person, and it should arrive with everything they need to decide.
Payment, remittance, and candidate invoices stay together on one screen.
The workflow says what does not line up: amount, reference, period, or confidence.
The exception goes to the person responsible, not to a shared queue.
Once decided, the match is posted and the collection sequence continues.
Coverage
Reconciliation works from the same records the collections workflow uses, so a match and a reminder never disagree.
FAQ
The amount, the bank reference, and the remittance line together. The evidence panel shows all three against the candidate invoice so the decision takes seconds rather than a search.
They stay visible as exceptions with their supporting detail attached, and route to the person responsible rather than being auto-applied or dropped.
The difference is kept as an open item on the invoice, and the collection workflow picks it up rather than treating the invoice as settled.
It is designed to. Payments that would otherwise sit unmatched until someone reads the remittance email are matched from the allocation details instead.
Yes. The remittance lines are read individually and matched to their invoices, so a consolidated transfer is allocated correctly.
The customer email thread. Finance Inbox has already classified it as a remittance, so the allocation detail is already tied to the right account.
Start
Bring your workflow, your systems, and who approves what.