A customer reports paying but the billing team cannot yet match the transfer to the correct invoice.
The useful bits
- Invoice reference
- Payment date and currency
- The response should supply a usable remittance reference without exposing unnecessary financial details.
Before you write
Use this example when a customer reports paying but the billing team cannot yet match the transfer to the correct invoice. Gather the details below so the recipient can act without asking you to reconstruct the situation.
- Invoice reference
- Payment date and currency
- Approved route for remittance evidence
An email you can adapt
The subject “Payment reference check for invoice [number]” identifies the request. Replace each bracketed field with a checked detail and remove any sentence that does not describe your situation.
Subject: Payment reference check for invoice [number] Hi [name], Thank you for letting us know about the payment for invoice [number]. To help our billing team match it, please provide the payment date, amount, currency and remittance reference through [approved route]. Do not send full account credentials, card numbers or security codes. We have not yet confirmed receipt in the relevant record. [Owner] will check the information and update you once the payment has been matched or a discrepancy identified. Best, [sender]
Check the boundary
A customer’s confirmation of sending funds is different from verified receipt and allocation in your own records.
What a useful reply should settle
The response should supply a usable remittance reference without exposing unnecessary financial details.
Confirm allocation only after the authorized billing owner has checked the actual transaction record.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction
