Skip to content

Match incoming cash to the right invoices.

Duvo reads bank and remittance records, applies clear matches, and sends the remaining balances to AR with the evidence needed to resolve them.

Matched

Payment to invoice

Bank and remittance records are matched against the open receivables they settle.

Explained

Remaining balance

Short payments, deductions, credits, and unknown amounts keep the reason and supporting records attached.

Updated

Customer account

Approved applications and remaining balances are written back to the receivables ledger.

Duvo establishes the baseline and validates the opportunity on your records before a live scope is agreed. No customer result is claimed for this solution yet.

Each payment shows the proposed invoice match and remaining exception.

The product view brings the bank line, remittance, customer account, open invoices, proposed match, and approval into one record.

Cash Application · Illustrative

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
Review
Receipt 802
In Progress
In Progress
Retail account
Review deduction
0
Review
Receipt 803
Completed
Completed
Distributor
Request remittance
0
Closed
Receipt 804
Pending
Pending
Customer account
Apply invoices
1
Review
Receipt 805
Postponed
Postponed
Bank transfer
Identify account
0
Review

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.

Incoming cash is easy to receive and hard to apply correctly.

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

  • The bank line does not explain the payment.

    References are missing, shortened, or inconsistent with the customer and invoice records in the ERP.

  • One payment can cover several outcomes.

    The customer may combine invoices, short-pay a disputed amount, take a credit, or pay across accounts and currencies.

  • Unapplied cash hides the real receivable position.

    The bank balance has moved, but open invoices and collection activity remain wrong until the payment is matched.

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

Clear matches can be applied under the agreed rules. Short payments, missing remittance, and ambiguous accounts pause for AR.

  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

    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.

Accounts receivable keeps authority over ambiguous matches.

  • 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.

Review security and assurance

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

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

Works across

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

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

  • When does Cash Application run?

    A customer payment or remittance lands and needs to be matched to open invoices.

  • Who owns Cash Application?

    Accounts receivable, order-to-cash, credit control, shared services

  • Which systems can Duvo work across?

    Duvo can work across the bank formats, remittance channels, customer accounts, and ERP screens already used by AR. Typical sources include bank statements and payment files, lockbox records, SAP accounts receivable, open invoice and credit records.

  • Where does a person stay in control?

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