How Do I Match Customer Payments to Invoices When Remittance Information Is Missing?

Start with the identifiers on the payment itself, such as the amount and the bank reference. If those don’t settle it, look for the remittance somewhere else: lockbox images, BAI2 addenda, portal confirmations or an email sitting in a shared inbox. When none of that produces a match you could defend to an auditor, the payment goes to an unapplied cash queue with an owner and a next step.

For wires specifically, our guide to matching a wire with no remittance information walks through the identification hierarchy with a worked example.

What should you check first?

If an invoice number appears anywhere in the memo or payment reference, apply the payment and move on. Most of the effort goes into payments that fail that test. For those, check identifiers roughly in order of reliability:

• the exact amount against open invoices, which is often enough when only one invoice matches
• memo text that includes a transaction reference or check number
• the originating account or BIC, to narrow the payment to one payer or subsidiary
• posting date and settlement currency, as tie-breakers

Note what you tried on each payment so the next person doesn’t repeat it.

Which signals help when several invoices fit?

Payment habits are the most useful. Many AP teams pay on the same weekday or round amounts the same way, so a payment that matches the payer’s usual timing and sending account is a strong lead. Keep payer aliases in one place, since a slightly different payer name can otherwise split one customer’s history across several profiles. Correspondent bank and settlement currency can also rule out invoices that look alike.

In Monk, deterministic matching applies a payment automatically only at 100% confidence. When confidence is lower, the payment comes with ranked suggestions for a person to review.

Where can you recover missing remittance?

Check these before emailing the customer.

Lockbox images. Check stubs and payment coupons often carry invoice numbers that the digital feed drops.

BAI2 files. Addenda records in the full bank file sometimes hold invoice-level detail that summary feeds leave out.

Shared inboxes. Many AP teams send remittance as a separate attachment, and those files can sit unread for weeks.

Portals and email threads. Look in the customer’s AP portal and in recent threads for a payment confirmation around the settlement date.

With Monk’s Upload Remittances feature, recovered files go straight into cash application, so the match and its source stay together in the record.

When should a match become a rule?

Automate slowly, since a rule built on a weak signal creates exceptions of its own. Wait until the same manual match has come from a consistent sending account several times, and keep automatic application to amounts your team is comfortable with. Have someone approve the first payment a new rule applies.

About 80% of payments match automatically in Monk, rising to 95% once suggested rules are accepted. Monk proposes those rules from matches people have already made by hand, as our post on suggested rules explains.

How should you triage unapplied cash?

Every unapplied payment needs a named owner and an evidence status, because each one keeps an invoice open on the aging report and pushes DSO up.

Payments with bank details or partial remittance should be resolved within 24 to 48 hours, either through a new rule or by contacting the customer. Low-value payments with no evidence at all can wait for a scheduled batch review. Large payments shouldn’t wait in the queue; send them to customer outreach the same day.

In Monk, unmatched payments land in a cash exceptions queue where someone can review and assign them.

What should you ask the customer?

Give their AP team what they need to find the transfer: the credit date and amount as your bank shows them, plus the bank’s trace or transaction ID. Then ask for the remittance file or the list of invoice numbers the payment covers. A screenshot of their remittance confirmation works as well as a file.

Julia, Monk’s AI agent for Intelligent Collections, gets a 24% higher response rate than standard dunning, which helps with requests like these.

How do you prevent missing remittance?

Most of the fixes are small and sit upstream. Publish one remittance address, such as remittance@yourcompany.com, and tell every payer to use it. Buyers can also be asked to put your invoice number in the payment reference on ACH and wire payments, which works best when that number is printed prominently on the invoice. If your bank offers ACH addenda capture or lockbox imaging, it’s worth switching both on.

For SLA templates and remittance capture in more depth, see our guide to reducing time spent on cash application. The full matching process is covered in our cash application guide.

To see how Monk would handle the payments in your unapplied queue, book a demo.

Frequently Asked Questions

Can I apply an unidentified payment to the oldest open invoice?

Only if your policy allows it, since applying to the wrong invoice creates a dispute later. Most teams keep the payment unapplied with an owner until they have evidence, and send large variances to the AR lead.

What’s the difference between unidentified and unapplied cash?

Unidentified cash hasn’t been tied to any customer yet. A payment is unapplied when the payer is known but it isn’t matched to specific invoices.

How should overpayments without remittance be handled?

Apply what you can match and hold the excess as a customer credit, with a note on where it came from. Confirm with the customer before refunding it or using it against future invoices.

Can remittance arrive after the payment?

Often. Many AP teams send the advice separately once the payment run is complete, so check the remittance inbox before escalating a recent payment.

What if the payer name doesn’t match any customer?

Payment rails often truncate names, so normalize the payer string and compare it with customer and registered company names. The wire guide linked above covers name normalization in detail.

Who should own the unapplied cash queue?

Someone in cash application usually owns it, with collections taking over once the customer needs to be contacted. Either way, every item needs one named owner.