How to match one bank payment that covers several invoices
When a customer pays several invoices in one lump sum, find the open invoices that add up to the deposit — by hand in a spreadsheet, or with RemitWeave.
· 7 min read
This post answers
How do I match one bank payment that covers several invoices?
To match one bank payment that covers several invoices, take the deposit amount and look at that customer’s open invoices, oldest first. Find the set of invoices whose amounts add up exactly to the deposit; that’s almost always what the customer paid. The bank description often helps: it may name the customer or list some of the invoice numbers. If the totals don’t add up exactly, check for a bank fee or a short payment before you match anything. You can do this by hand in a spreadsheet, or let RemitWeave find the combination and tell you why it thinks it’s right.
The problem: one lump sum, many invoices
A small business owner on r/smallbusiness described losing a Saturday to this. Matching 47 invoices to their bank transactions took about four hours, and the slowest part wasn’t the straightforward one-invoice, one-payment cases. It was customers who paid several invoices with a single transfer, so no single invoice matched the amount in the bank.
That’s the case this post is about. Matching a $475 deposit to a $475 invoice is easy, and plenty of free CSV tools and accounting packages already help with it. Working out that a $3,450 deposit is really three separate invoices is where the time goes.
Why combined payments are hard to match
A lump-sum payment hides three things from you:
- Which invoices it covers. The amount doesn’t equal any one invoice.
- Who paid. Bank descriptions are often truncated, or name a parent company or a payment app rather than the customer.
- Whether it’s complete. A customer may have paid three invoices and deducted a fee, or paid two in full and part of a third.
So you’re really answering a small puzzle: which of this customer’s open invoices add up to this number?
The example
Here are some open invoices and a few deposits from the bank export. It’s the same demo data RemitWeave loads when you try it.
Open invoices (some of them):
| Invoice | Customer | Amount |
|---|---|---|
| INV-1001 | Acme Corp | $1,200.00 |
| INV-1002 | Acme Corp | $850.00 |
| INV-1003 | Acme Corp | $1,400.00 |
| INV-1005 | Northwind Traders | $2,750.00 |
| INV-1008 | Greenleaf Dental | $1,980.00 |
Deposits (some of them):
| Description | Amount |
|---|---|
| ACH CREDIT ACME CORP PAYMENT | $3,450.00 |
| WIRE IN REF INV-1005 NORTHWIND | $2,750.00 |
| ZELLE FROM GREENLEAF DENTAL INV 1008 | $1,955.00 |
| ACH CREDIT UNKNOWN PAYER 88213 | $1,250.00 |
No single invoice is $3,450.00, so the Acme payment is a lump sum.
Method 1: the spreadsheet
Step 1 — put open invoices and deposits side by side. Paste the open invoices on one sheet (number, customer, date, amount) and the bank deposits on another. Leave out invoices you’ve already matched, and leave out withdrawals.
Step 2 — sort invoices by customer, then by date. Grouping by customer matters because a lump sum almost always comes from one customer. Sorting oldest first matters because customers usually pay their oldest invoices first.
Step 3 — find the customer. Read the deposit’s description. “ACH CREDIT ACME CORP PAYMENT” points to Acme Corp. If the description doesn’t name anyone, you may have to try likely customers in turn.
Step 4 — add up open invoices until you hit the amount. Add a running total down the customer’s invoices:
| Invoice | Amount | Running total |
|---|---|---|
| INV-1001 | $1,200.00 | $1,200.00 |
| INV-1002 | $850.00 | $2,050.00 |
| INV-1003 | $1,400.00 | $3,450.00 |
The running total reaches $3,450.00 exactly at INV-1003, so the deposit covers INV-1001, INV-1002 and INV-1003.
When the running total jumps past the deposit, the customer may have skipped an invoice — perhaps one is disputed — so you have to try other combinations. SUM over a hand-picked range works, but with eight or ten open invoices the number of combinations grows quickly. It also helps to check whether more than one combination adds up, because then you need to ask the customer.
Step 5 — check the rest. The Northwind deposit names INV-1005 and matches its amount, so it’s easy. The Greenleaf deposit names INV-1008 but is $25.00 short of $1,980.00. That’s a bank fee or a short payment, and worth a note before you mark the invoice paid. The $1,250.00 deposit names nobody and doesn’t match any open invoice, so it needs a follow-up.
This is all doable. It’s just slow, and you redo the same searching every time a batch of payments comes in.
Method 2: RemitWeave
RemitWeave does the same detective work from the two files you already have: an invoice list from your accounting software and your bank’s CSV export.
1. Upload both files. On the Import page, upload your open invoices (invoice number, customer, amount due, invoice date) and your bank transactions (date, amount — or separate credit and debit columns — and description). RemitWeave guesses which column is which, and you can change any of them in the preview. Withdrawals are ignored, and re-importing a file you’ve already loaded skips anything already there. As soon as an import finishes, matching runs.
2. Read the suggestions. For each deposit, RemitWeave looks at three things:
-
Invoice numbers in the description, written as
INV-1005,inv 1005or#1005. - An exact amount that matches a single open invoice.
- Combined payments: two or more open invoices from the same customer whose amounts add up exactly to the deposit. If the description names a customer, only that customer’s invoices are searched. Otherwise every customer is, at lower confidence.
Each suggestion has a confidence score and a list of plain-English reasons. For the example, the review queue shows:
| Deposit | Suggested invoices | Confidence | Why |
|---|---|---|---|
| ACH CREDIT ACME CORP PAYMENT, $3,450.00 | INV-1001 + INV-1002 + INV-1003 | 85% | “Combined payment: 3 invoices (INV-1001, INV-1002, INV-1003) add up to exactly $3,450.00.” · “Customer Acme Corp named in the description.” · “Paid 15–25 days after the invoice dates.” |
| WIRE IN REF INV-1005 NORTHWIND, $2,750.00 | INV-1005 | 99% | “Invoice INV-1005 referenced in the description.” · “Amount matches exactly.” · “Customer Northwind Traders named in the description.” |
| ZELLE FROM GREENLEAF DENTAL INV 1008, $1,955.00 | INV-1008 | 60% | “Invoice INV-1008 referenced in the description.” · “Payment is $25.00 less than invoiced — a bank fee or short payment?” |
The Acme lump sum is broken down into the three invoices it covers. The card shows each invoice with its date and amount next to the deposit, so you can see the arithmetic. When several combinations add up to the same amount, RemitWeave picks the one with the oldest invoices, lowers the score, and says how many other combinations also fit.
3. Accept or reject. Accept a suggestion and that deposit and those invoices leave the open pool. Reject it, and RemitWeave looks for the next best option; a rejected suggestion is never made again. If you trust the high scores, Accept high-confidence accepts everything at 80% or above in one click. Nothing is accepted unless you choose to.
4. Deal with the exceptions. The Exceptions page lists what still needs a person:
- Payments nobody could match, each with a reason. For the example: “No open invoice for $1,250.00, and the description doesn’t mention an invoice number or a known customer.” Next to each one is a form to match it to one or more invoices by hand.
- Unpaid invoices, with a note on whether a suggestion is waiting for review or the invoice is overdue.
- Accepted matches with a difference. If you accept the Greenleaf payment, it appears here with its $25.00 shortfall.
5. Export. Download a reconciled CSV: one row per invoice with its status (paid, suggested or unpaid) and the payment it was matched to, plus a row for each payment that isn’t matched yet.
What RemitWeave doesn’t do (yet)
A few limits are worth knowing before you try it:
- A combined payment has to add up exactly to be suggested from amounts alone. A lump sum that’s short by a fee is only suggested automatically when the description mentions the invoice numbers. Otherwise you match it by hand on the Exceptions page.
- Partial balances aren’t tracked. Accepting a short payment treats the invoices as paid; the difference is listed on the Exceptions page, not carried forward as a balance on the invoice.
- Combinations are capped. A single payment can be matched automatically to up to six invoices from one customer. Larger batches can still be matched by hand.
- It doesn’t connect to your bank or accounting software. It works from CSV exports, and you record the result in your books yourself.
How this compares with other tools
Most accounting packages let you apply one customer payment to several invoices when you record it, and their bank reconciliation screens let you match a deposit against more than one item. Free CSV matching tools are good at pairing rows on an exact amount or reference. If those cover your payments, you may not need anything else.
RemitWeave is narrower on purpose. It focuses on the case those tools leave to you — working out which invoices a lump sum covers — and on showing its reasoning, so you can check a suggestion in a few seconds instead of re-adding the numbers yourself.
Try it on your own payments
You can load the example above in RemitWeave with one click, then import your own invoice list and bank export. Start a 14-day free trial of RemitWeave; after the trial it’s $29 a month.
Frequently asked questions
- Does a combined payment have to add up exactly to be matched?
- To be suggested automatically from amounts alone, yes: RemitWeave looks for open invoices from one customer whose totals add up exactly to the deposit. If the bank description mentions the invoice numbers, a payment that's a little short is still suggested and the difference is shown. Anything else you can match by hand from the Exceptions page.
- What if more than one combination of invoices adds up to the payment?
- RemitWeave suggests the combination with the oldest invoices, lowers its confidence score, and says in the reasons how many other combinations also add up — so you know to check before accepting. If it picked the wrong one, reject it and the next best option is suggested.
- Does RemitWeave track partial payments?
- Not yet. If you accept a match where the payment is less than the invoices, the invoices are treated as paid and the difference is listed under "Accepted with a difference" on the Exceptions page, so it isn't lost — but there's no remaining balance carried on the invoice.
- What files do I need?
- Two CSVs: a list of open invoices (invoice number, customer, amount due and invoice date — for example an invoice list exported from your accounting software) and your bank's transaction export (date, amount or credit/debit columns, and description). Withdrawals in the bank file are ignored.
- Will RemitWeave accept matches on its own?
- No. Every match is a suggestion until you accept it. There's an option to accept all suggestions with 80% confidence or more in one click, but nothing is accepted unless you choose to.