Remittance advice request email for an unidentified B2B payment

When a business payment reaches your bank without a usable invoice reference, contact the customer's accounts payable team to confirm the payer and the allocation. Give them enough information to find the transfer. Ask them to list the amount applied to each invoice so a partial payment does not accidentally close the whole balance.
Upload a case

Key facts

Copy this remittance advice request email

Subject Remittance advice request for [amount and currency], received [date]

Hi [name or Accounts Payable team],

We received a payment of [amount and currency] on [date]. The reference visible to us is [reference, or “no reference shown”]. Could you confirm whether your team sent this payment and share the remittance advice?

If you don't have a remittance advice document, please reply with the details below.

  • The name of the company that paid, including any group company that paid on the customer's behalf.
  • The transfer date, amount, currency and payment reference.
  • Each invoice number, its currency and the amount you intended to pay against it.
  • Any credit note, deduction or other adjustment included in the payment, with its reference and amount.

Please use an approved secure channel if supporting documents include sensitive information. A reply with the details above is usually enough to start the check.

Thanks,
[Name]
[Company] Accounts Receivable

If the bank entry gives you no reliable candidate, investigate internally first. Send the request only to a known accounts payable contact once you have a plausible match. If someone contacts you from a new domain, verify the message with the contact in your customer records.

Record the receipt while you wait

Field What to record
Bank evidence Posting date, amount, currency and the visible transfer reference
Identity Unconfirmed payer, or confirmed payer with allocation pending
Candidate invoices References to investigate, with a note on what makes them plausible
Next action Named AR owner, contact used and date to follow up
Resolution Verified invoice allocation and any amount still held for review

Keep the receipt in the unresolved category your accounting process uses until you have evidence for the match. A known customer with a missing invoice instruction is a different exception from a receipt whose payer you cannot identify. Oracle's documentation illustrates both the unidentified receipt workflow and how one receipt can be applied across multiple items. Oracle Receivables guidance

Example with two invoices and a partial allocation

You receive EUR 3,600 with reference PAY-1842. The customer's AP team confirms that a group company sent the transfer, with EUR 2,500 for invoice INV-301 and EUR 1,100 for invoice INV-318. Both invoices are in EUR. You verify the payer relationship and transfer against your records, then apply the two amounts. If INV-318 was open for EUR 1,800 before the receipt, EUR 700 remains open. Carry that balance into the next review and check why it remains unpaid before requesting it again.

If a customer instead explains a shortfall as a deduction, log their reason and supporting reference for the appropriate owner. Confirm the adjustment through your normal approval process before changing the original balance.

See the cash application guide for the wider process. If a documented invoice from a business customer abroad stays overdue after the payment is matched, review your unpaid invoice options.

Sources

  • Oracle's Receivables guide supports the distinction between an unidentified receipt and an allocation across invoices. The email, references and amounts are examples.

RELATED ARTICLES

Illustration of a free e-book representing the 'Free International Debt Collection Guide.' This guide offers proven debt collection techniques. Get your free copy now.
FREE GUIDE

Download our free debt collection guide

Practical steps to get unpaid invoices paid, at home and abroad. Download our debt collection guide for free.

Thank you! The guide will land in your inbox shortly
Oops! Something went wrong while submitting the form.