Accounts Receivable
Cash Application, applied automatically.
Match every payment. Surface and resolve every exception.
Donnerstag brings together the bank transaction, remittance advice and open receivables, applies approved matching logic and posts what it can, leaving exceptions with their full context attached.
From incoming payment to applied cash and a documented outcome.
The payment, its matched invoices and the exception.
A payment arrives, the remittance is matched, invoices clear, and the short-paid line is isolated rather than blocking the rest.
Running
Invoice
Open
Applied
Status
Applied
Short-pay
Part-applied
Applied
Applied
01
The payment in context
The bank transaction, method, payer and total, with its matched remittance advice already linked.
02
Match confidence
How strongly the approved rules matched this payment to open receivables. High confidence posts straight through.
03
Applied invoice lines
Each open invoice the cash was applied to, with the amount cleared against the ledger.
04
The exception, isolated
The one short-paid line is flagged and quantified, and handed off as a deduction rather than blocking the rest.
What Cash Application does before anyone touches it.
Remittance is read, payments are matched against open receivables, and anything clearing within tolerance is posted without a person.
Capture remittance
Read remittance advice from bank files, email, portals and EDI, and structure it into usable matching information.
Multi-signal matching
Match on invoice number, amount, customer reference, payment date and payer against open receivables.
Partial & multi-invoice
Split one payment across many invoices and handle partials without forcing a single-line match.
Tolerances
Apply approved tolerances so tiny, expected differences clear automatically instead of becoming exceptions.
Straight-through posting
Post high-confidence matches to the ledger automatically, within the boundaries you approve.
Exception typing
Classify what cannot be applied (short-pay, overpayment, unidentified, ambiguous) and route each accordingly.
Most payments never need a person.
Only the small share that genuinely needs judgment reaches an analyst.
Auto-applied
Exceptions to resolve
The analyst’s day shifts from keying payments to resolving the small share that genuinely needs judgment.
The share that needs a person.
Each exception arrives typed, quantified and evidenced, not as a raw unapplied payment to investigate from scratch.
Short-pay
Partial payment
The payment covers less than the open invoice. The gap is quantified against the specific invoice line.
Resolution:
Create a deduction with the invoice, remittance and evidence attached.
Overpayment
Excess received
The payment exceeds what is open. The surplus is isolated rather than force-applied.
Resolution:
Route to on-account or refund per your policy, with the decision recorded.
Unidentified
No remittance / payer
The payment arrives without enough information to identify the customer or invoices.
Resolution:
Assign for research with candidate matches ranked and evidence gathered.
Ambiguous
Multiple candidates
The amount could apply to more than one invoice or customer within tolerance.
Resolution:
Surface ranked candidates so the analyst confirms the correct application.
How an exception reaches a documented outcome.
Select an action to see what it does, and the authority it runs under.
01
Isolate
Separate the exception from the applied cash so posting is never blocked.
02
Type
Classify the reason and attach the relevant financial impact.
03
Evidence
Connect the invoice, remittance and supporting documents.
04
Assign
Route to the right owner or workflow with a next action.
05
Resolve
Post, dispute, refund or write off, and record the outcome.
Act on an exception
Short-pays become deductions.
A short-payment hands off to the Deduction Worklist with the invoice, remittance and evidence already attached, where it is validated, resolved and recovered.
Applied cash keeps the aging honest.
Once payments are applied, the open receivables balance is current, so the aging buckets reflect what is genuinely outstanding, not a backlog of unapplied cash.
Current
1–30
31–60
61–90
90+
Overdue balances feed dunning.
Everything past due flows into an approved dunning cadence, reminders, escalations and promises to pay, so the aging tail is worked, not just watched.
See the whole operation. Drill to any payment.
An overview of cash application at operation level, then open to the payment, rule and evidence behind every figure.
● Running
Invoice
Open
Applied
Status
Applied
Short-pay
Part-applied
Applied
Applied
Keep every payment answerable.
Know what applied, what didn’t, and why.
What applied?
The invoices cleared and the amounts posted.
What didn’t?
The exception, its type and financial impact.
Why?
The matching result and applicable rule.
What supports it?
The remittance and linked records.
Who owns it?
The analyst or workflow responsible.
How did it end?
Applied, deducted, refunded or written off.
What Accounts Receivable gains
Cash application is where the ledger either stays current or falls behind. These are the outcomes the operation is built to produce.
Apply cash sooner
High-confidence payments post automatically, so the ledger stays current without manual keying.
Shrink the exception queue
Only the payments that genuinely need judgment reach an analyst, already typed and evidenced.
Cleaner aged receivables
Faster, accurate application keeps the aged balance meaningful for collections and reporting.
Seamless handoff
Short-pays flow straight into deduction management with full context, no re-keying between systems.
Consistent matching
Approved rules and tolerances apply the same way every day, across analysts and volumes.
Traceable outcomes
Every applied or exception amount traces back to the payment, rule and evidence behind it.