Finance and accountingConcept

A customer paid $18,400 with no remittance. Matched.

Lump-sum payments, short payments and remittances buried in emails are matched to invoices. Only real disputes reach your team.

Industry: Finance and accounting
Systems connected: Bank feed, accounting system, accounts inbox
Headline result: Concept, not yet built

Expected outcome

Expected: payments applied the day they arrive, no more chasing customers who have already paid, and staff time spent only on real disputes.

The business

Designed for B2B businesses that invoice many customers and receive payments that rarely line up neatly with single invoices.

The problem

Customers pay several invoices at once, pay short, or send remittance details in a separate email or PDF. Accounts staff spend days matching payments by hand. Until they do, payments sit unapplied and customers get chased for invoices they have already paid.

Before

Payment arrives
Search inbox for remittance
Match invoices by hand
Chase unclear payments
Customer chased in error

After

Payment arrives
Remittance found and read
Invoices matched
Deductions logged with reason
Disputes to a person

Simplified process diagram. Dashed steps were done by hand.

My approach

The answer is split across the bank feed, the accounting system and the inbox, which is why built-in bookkeeping tools only handle the clean matches. The agent reads remittances in any format, proposes the match, and explains any difference. Staff approve, and only genuine disputes need their time.

How I’d solve it

Watches the bank feed and the accounts inbox for payments and remittance advice.
Reads remittances from emails and attachments and matches payments to open invoices, including partial and combined payments.
Logs short payments as deductions with the reason the customer gave, and drafts a reply where one is needed.
Shows a short daily queue of anything it couldn’t match confidently.