Skip to content

Stop unapplied cash from hiding what customers still owe.

A customer who has already paid can still receive a collection reminder or have a new order held if the cash remains unapplied. Duvo matches bank receipts and remittances to the right invoices, applies approved matches and gives AR the evidence to resolve short payments. Customer balances reflect what is actually still owed.

Book a process call

Agree the supported records, system access and approval rules for your process before execution.

Cash Application

Needs input

Receipt 801

Match status
Exact match
Scope
Customer account
Decision
Apply cash

Next action

Match rules are approved by AR

Tolerance, account, currency, deduction, and multi-invoice rules are defined against the customer’s real receipts.

View the wider product queue

Cash Application

Incoming payments and remittance records are matched to open invoices, with unmatched balances held for review.

Adds cases
Bank Statement
Processes cases
Cash Match Review
Total

24

Pending

5

Postponed

2

In progress

4

Needs input

3

Failed

0

Completed

10

Add filter
Case
Case Status
Match status
Scope
Decision
Exceptions
Next action
Receipt 801
Needs Input
Needs Input
Customer account
Apply cash
1
Receipt 802
In Progress
In Progress
Retail account
Review deduction
0
Receipt 803
Completed
Completed
Distributor
Request remittance
0
Receipt 804
Pending
Pending
Customer account
Apply invoices
1
Receipt 805
Postponed
Postponed
Bank transfer
Identify account
0

Showing 5 of 24 cases

  1. 1

    Approval

    Exceptions pause for the named owner

    Each exception carries the source records, applied rule, recommended action, and the person authorised to decide.

  2. 2

    Match status

    Match status is visible before the action

    Each payment shows the invoices matched, the remaining balance, and the evidence needed to clear an exception.

Move each receipt from the bank statement to the correct invoices.

A payment may cover several invoices, arrive without remittance, include a deduction, or use a payer name that does not match the customer record.

  1. 01Collect

    Read the payment and remittance.

    Duvo reads bank statements, payment files, lockbox records, remittance emails, EDI, and portal data as they arrive.

  2. 02Identify

    Identify the customer account.

    Payer names, bank accounts, references, invoice numbers, and known relationships are used to find the right account.

  3. 03Match

    Match the payment to open invoices.

    The amount and remittance are compared with open invoices, credits, deductions, and prior balances to propose the application.

  4. 04Approve

    Your team decides

    Pause ambiguous balances.

    Short payments, unknown payers, disputed invoices, and multi-account matches reach AR with the evidence behind the proposal.

  5. 05Apply

    Write the approved match back.

    Applied cash, remaining balances, deduction reasons, and review decisions update the ERP and the customer account.

Match cash across the bank, remittance, and receivables records.

Systems and control details

Duvo can work across the bank formats, remittance channels, customer accounts, and ERP screens already used by AR.

bank statements and payment files, lockbox records, SAP accounts receivable, open invoice and credit records, remittance email and EDI, customer portals, customer master data, deduction and dispute records

  • Match rules are approved by AR

    Tolerance, account, currency, deduction, and multi-invoice rules are defined against the customer’s real receipts.

  • Unclear applications pause for review

    Unknown payers, short payments, disputed balances, and cross-account matches do not post without the named owner.

  • Every posting can be traced back

    The bank line, remittance, proposed match, approval, and ERP posting remain connected.

Contracted guarantee

5x ROI, guaranteed

If measured results fall below 5x the total proposal price, the whole contract is free.

What teams ask about Cash Application

  • How is a payment matched when the payer name differs from our customer record?

    Duvo uses payer names, bank accounts, references, invoice numbers and known relationships to find the account. Unknown payers and cross-account matches go to AR with the evidence and do not post without the named owner.

  • What happens with a short payment?

    It pauses for AR with the evidence behind the proposed match. Once approved, the applied cash, remaining balance and deduction reason update the ERP and the customer account.

  • Who sets the matching tolerances?

    AR approves them. Tolerance, account, currency, deduction and multi-invoice rules are defined against your real receipts.

  • Where does Duvo pick up remittance details?

    From bank statements, payment files, lockbox records, remittance emails, EDI and customer portals as they arrive.

Related processes