how to help users find a charge on their statement

TL;DR

Customers almost always find the charge themselves once you give them three things: the exact billing descriptor as it appears on statements, the date range to look in, and the fact that pending charges look different from posted ones. Ask for the amount and date first, match it to an invoice on your side, then hand them the descriptor. Most "mystery charge" tickets close in one reply.

The query

how to help users find a charge on their statement

Use this when

• A customer asks what a charge on their statement is for
• A charge does not match what they expected to see
• Finance needs statement language for billing descriptors
• You are writing a help article about billing

Not for

• Disputing the amount of a charge
• Refund requests
• Fraud or unauthorized transaction investigations
• Explaining the pricing plan itself

Steps

1. Ask for the amount and the statement date

Get the exact amount and the date it appears. Pending charges show the authorization date, which can differ from the invoice date by several days.

Expected output: two facts you can match against your billing records.

2. Match it to an invoice on your side

Search your billing system by customer, amount, and date. Confirm which invoice or subscription period the charge belongs to before you reply.

Expected output: the invoice or subscription the charge maps to.

3. Give them the exact billing descriptor

Tell the customer the literal text that appears on statements, including any prefix or abbreviation. Descriptors get truncated by banks, so warn them it may appear shortened.

Expected output: the customer can search their statement for the descriptor text.

4. Explain pending versus posted

If the charge is recent, it may show as pending with a slightly different amount or date. Pending holds drop off and the posted charge follows. Tell them what to expect and when.

Expected output: the customer stops worrying about a duplicate that is really one charge in two states.

5. Close the loop with the invoice

Send the invoice or receipt with the matching amount and date. A document that matches the statement line ends the ticket.

Expected output: one reply, ticket resolved.

Ready-to-use customer reply

That charge is from us, [Name]. It appears on statements as
[DESCRIPTOR], and the [amount] on [date] matches your invoice
[number] for [plan] covering [period]. Banks sometimes shorten
the name, so look for the first few letters. Ive attached the
receipt as well.

Variant phrasings

what is this charge on my statement

Same playbook. Amount plus date, match to invoice, hand over the descriptor.

customer doesnt recognize a charge

Work the five steps before assuming fraud. Recognition failure is far more common than actual fraud.

billing descriptor doesnt match company name

Explain the descriptor text and truncation. This is a naming problem, not a billing problem.

Why it happens

Payment processors require a billing descriptor, and companies pick something short that made sense internally years ago. Banks then truncate it, statements show the authorization date instead of the invoice date, and the customer sees a cryptic line from a name they have never heard of. Every step is correct and every step confuses.

Edge cases

• Free trial conversions: the first charge after a trial surprises people even when it is legitimate. Mention the trial end date explicitly.
• Annual renewals: a charge 12 months after the last one is forgotten, not fraudulent. Point at the renewal date.
• Family or team accounts: the cardholder may not be the account user. Ask who else has access before going further.
• Currency conversion: international customers see a different amount than the invoice. Note the original currency.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstqvK29rsNL9Y_gU6UxX5oA