What should you email a customer who short-paid an invoice?

Key Takeaways

• Transformance’s AI agents investigate a short payment and propose the likely cause with evidence before a person writes; ClearMatch auto-matches 95% of payments (Transformance customer data, 2026).
• Check first: a payment on the wrong invoice, an earned discount or an open credit memo can explain a short payment without any email.
• Every email carries invoiced, paid and balance, the evidence, one question with a date and an invitation to correct you.
• The four templates are a starting policy you adapt; none mentions fees, interest or consequences.
• In consumer goods, a retail key account often short-pays with a debit memo or claim number: validate it before you write.

In This Article

• Key Takeaways
• What should you email a customer who short-paid an invoice?
• What do you check before you write?
• What goes into every short-payment email?
• What should the email say in each case?
• What happens after you send the email?
• How do you automate short-payment triage and emails?

What should you email a customer who short-paid an invoice?

After agents like Transformance’s Vero have found the likely cause, send one email per case: invoiced, paid and balance, the evidence attached, and one question with a date.

Short payment: check first, then pick the email (illustrative numbers: invoiced USD 37,500, paid USD 36,750, balance USD 750)

Rows 1-4 are the four templates, with these numbers; in the first and last rows, no email is the next step.

A short payment is a payment below the invoiced amount, with or without a stated reason.

Why write soon: in a field experiment with Australian business taxpayers, a simple reminder letter raised the probability of payment by about 25 percentage points against no letter, and earlier reminders brought faster payment (Gillitzer and Sinning, IZA Discussion Paper 11599, 2018). It covers tax debts, not trade invoices, so it supports the direction only. We found no independent figure on how often B2B invoices are short-paid, only vendor surveys, so this page uses none.

The worked numbers: 1,500 cases at USD 25.00 make USD 37,500; the customer paid USD 36,750. The USD 750 balance is a USD 0.50 price gap on 1,500 cases (case 1), 30 cases not received (case 2), a 2% discount (case 3) or unexplained (case 4).

Takeaway: a short payment gets the email that matches its cause, never one generic text.

What do you check before you write?

Check that the payment sits on the right invoice, that no discount or credit memo explains the gap, and what the remittance says: a short payment can resolve right there.

1. Is the payment on the right invoice? A payment on the wrong open item, or parked as unapplied cash, looks short on one invoice and over on another (matching a payment with no reference; clearing an unapplied cash backlog).
2. Does a discount or credit explain it? A discount taken inside its period, or a credit memo you issued but have not applied, closes the gap on your side.
3. What does the remittance say? Read the remittance advice, portal note or EDI line first (where remittance advice comes from). In the GS1 EANCOM remittance message, adjustment reason codes include 4 short delivery, 5 price query, 66 cash discount and 75 promotion discount (GS1 EANCOM REMADV, updated 2021). Coding what you find: deduction reason codes.
4. Has this customer short-paid before? The same gap again usually means the same cause, and often a pricing or master-data fix on your side.

When the gap is yours, send no short-payment email. Unapplied credit, a valid discount, a price change you announced late: fix it, and tell the customer in one line if useful.

‍

‍

Triage by cause. The four cases follow where customer deductions come from, which lists the evidence per cause.

In consumer goods, many short pays come with a reason. A grocery chain, drugstore chain or wholesaler often deducts a promotion allowance, an advertising allowance, a listing fee, a year-end rebate, a shortage at its distribution center or a compliance fine, announced in a debit memo with a claim number. That is a deduction with a reason: validate it against the trade terms agreement, the promotion records or the proof of delivery first (how CPG manufacturers resolve retailer deductions). The emails below cover the cases where the customer must act; terms: dispute, deduction, short pay, chargeback.

Transformance’s ClearMatch and ClaimIQ agents handle the matching and the deduction classification that this triage starts from.

Takeaway: the cheapest short payment to resolve is the one you never have to email about.

What goes into every short-payment email?

Every short-payment email has six parts: a subject with invoice number and balance, three numbers, the evidence, one dated question, a part-payment sentence and an invitation to correct you.

Six parts of every short-payment email

1. Subject line with the invoice number and the balance.
2. Three numbers: invoiced, paid, balance.
3. The evidence for the likely cause, attached.
4. One question with a date.
5. A sentence that the payment is applied as a part payment and the balance remains due.
6. An invitation to tell you if you are wrong.

One ask. Two questions tend to get one answer, so offer “pay the balance or tell us which part you did not pay and why” as one decision.

‍

‍

The part-payment sentence. It records in writing that you took the payment as a part payment and the balance stays due. This is practice; “paid in full” payments are the exception (see below).

The invitation to correct you. Pricing and shortage claims are sometimes right; “if we have it wrong, we will correct it” keeps the relationship and brings the customer’s evidence sooner.

Channel. Reply to the remittance contact or the customer’s AP contact; if the customer pays through an AP or retailer portal, answer in the portal. Follow-up rhythm: B2B dunning cadence.

Takeaway: the same six parts every time make the email quick to write and quick to answer.

What should the email say in each case?

Use the template that matches the cause: pricing difference, not received, unauthorized or late discount, or unexplained; each is short, factual and ends with one dated question.

These templates are a starting policy, not a standard: adapt names, dates, terms and tone to your contracts and customers. Brackets mark what you fill in.

Template 1: pricing difference. Attach the price agreement or quote and the invoice.

Subject: Invoice [number]: USD 750 open (price difference)

Hello [Name],

Thank you for your payment of USD 36,750 on [date] against invoice [number] (USD 37,500).

The difference of USD 750 looks like a price difference: we invoiced USD 25.00 per case, and your payment reflects USD 24.50 on 1,500 cases. Our price comes from [price agreement or quote number, valid from date]; it is attached with the invoice.

Could you check your purchase order [PO number] and let us know by [date] either that you will pay the balance, or which order line or price you are working from? If we have it wrong, we will correct it on our side.

We have applied your payment as a part payment; the balance of USD 750 remains due.

Thank you,

[Name, role, phone]

Consumer goods variant. When a retail key account paid a promotion price on an order outside the promotion window, replace the second paragraph with: “The difference of USD 750 matches the promotion price of USD 24.50 per case from promotion [number], which applied to orders from [date] to [date]. PO [number] was placed on [date], so it was invoiced at USD 25.00. The promotion terms and the invoice are attached.”

Template 2: not received. For example, a grocery chain’s distribution center reports 30 cases missing. Attach the signed proof of delivery and the invoice. If the invoice itself never arrived, see when a customer says the invoice never arrived.

Subject: Invoice [number]: delivery record for USD 750

Hello [Name],

Thank you for your payment of USD 36,750 on [date] against invoice [number] (USD 37,500).

The payment is USD 750 short, and your remittance notes that 30 cases were not received at [distribution center or ship-to]. The attached proof of delivery shows all 1,500 cases received on [date] and signed by [name].

Could you check your receiving record for this delivery and send it to us by [date] if it differs? If the goods were received in full, please release the balance of USD 750.

We have applied your payment as a part payment; the balance of USD 750 remains due.

Thank you,

[Name, role, phone]

Template 3: unauthorized or late discount. Attach the invoice with its terms; the recovery path is in how to recover unauthorized cash discount deductions.

Subject: Invoice [number]: discount taken after the discount period

Hello [Name],

Thank you for your payment of USD 36,750 on [date] against invoice [number] (USD 37,500).

The payment is USD 750 short, which matches a [2]% discount. The terms on the invoice offer this discount only for payment within [10] days of the invoice date; your payment reached us on [date], day [number]. The invoice and terms are attached.

Could you release the balance of USD 750 by [date]? If we have agreed different terms with you, please send us the agreement and we will review it.

We have applied your payment as a part payment; the balance of USD 750 remains due.

Thank you,

[Name, role, phone]

Template 4: unexplained. Attach the invoice and the statement of account.

Subject: Invoice [number]: USD 750 unexplained difference

Hello [Name],

We received USD 36,750 on [date] against invoice [number] for USD 37,500. The payment came without detail for the difference of USD 750. The invoice and your statement of account are attached.

Could you tell us by [date] which part you did not pay and why, for example price, quantity, a discount or a credit note, or pay the balance? If it relates to a promotion or a debit memo, the claim number is enough. That lets us fix our side if the cause is ours.

We have applied your payment as a part payment; the balance of USD 750 remains due.

Thank you,

[Name, role, phone]

What stays out of every template: threats, deadlines with consequences, fees, interest, accusations such as “you underpaid”, labels such as “second notice”, all-caps words.

Takeaway: four short texts, one per cause, each ending in one question with a date.

What happens after you send the email?

One of three things: the customer pays, the customer answers with a claim that moves to the dispute track, or nobody answers and the balance joins your follow-up.

• The customer pays. Apply the payment and close the item.
• The customer answers with a claim. The invoice moves to the dispute track, with an owner and the evidence on both sides (AI dispute management in accounts receivable; step by step: the B2B invoice dispute workflow). If the claim is valid, a credit memo settles it; tell the customer in one line.
• Nobody answers by the date. The balance continues in your dunning cadence (dunning process email templates; when a B2B customer is not responding).

“Paid in full” payments. When a check, payment note or cover email says a payment below the invoice amount settles it in full, do not deposit it or reply until the person who owns legal risk in your company has decided: such a marking can change what accepting the payment means. This is general guidance, not legal advice.

Takeaway: the email starts one of three tracks; decide in advance who owns each.

How do you automate short-payment triage and emails?

Automate the check, the case and the evidence, and keep a person deciding what goes out: ClearMatch auto-matches 95% of payments; ClaimIQ classifies each deduction in under 15 seconds.

Matching first. ClearMatch auto-matches 95% of payments and runs end to end in under 8 minutes (Transformance customer data, 2026); it validates 100% of postings, and nothing posts without human sign-off. This is the step that handles the “not really short” row.

Deductions next. ClaimIQ identifies deductions with 97% accuracy (Transformance platform data, 2026), classifies each one into six categories in under 15 seconds (manual: 45 minutes) and validates about 40% of trade deductions by rules (Transformance customer data, 2026). The person who writes the email starts from a classified case, not a bank line.

Vero on the exception. Vero, Transformance’s AI agent, investigates each exception from Customer 360, fetches information from internal and external sources and proposes the cause with the evidence. A person approves. If the balance stays open, CollectPulse actions 100% of overdue invoices within 24 hours, against 30-40% for manual teams (Transformance customer data, 2026). More: automate partial payments and deductions in AR.

In your ERP. Transformance reads open items and remittances and writes clearing postings after approval (ERP integrations; consumer goods on SAP: AR automation for CPG and FMCG).

Takeaway: agents find the case and the evidence; a person decides what reaches the customer and approves what posts.

Who Transformance is for

• ERP: finance teams that run AR in SAP S/4HANA (on-premises, private or public cloud), SAP ECC, NetSuite, Microsoft Dynamics 365 Finance & Operations or Business Central, or Odoo, all running in production with customers; Oracle and Infor are supported.
• Size: mid-market to large enterprise, 250 to 2,000+ employees, including groups with several entities and shared service centres.
• Payment volume: from under 1,000 to over 100,000 payments a month.
• Industries: manufacturing, consumer goods and food and beverage, logistics, e-commerce, agriculture, energy and professional services.
• Scope: cash application alone, or the full order-to-cash: cash application, deductions, AR collections and cash forecasting.

Conclusion: check, pick the case, ask once

Check first, pick the email that matches the cause, attach the evidence and ask one question with a date. Apply the payment as a part payment, keep the balance open, and let the answer decide the next track. Book a Call to see Transformance’s agents prepare your short payments with case and evidence.

Key terms

• Short pay: a payment below the invoiced amount, with or without a reason.
• Deduction management: identifying, validating, resolving and recovering customer short payments.
• Proof of delivery: the signed record of delivery that decides not-received claims.
• Remittance advice: the customer’s notice of what a payment covers.
• Skonto: a discount for payment within a stated period, a frequent reason for a short payment.
• Credit memo: the document that reduces the receivable when a deduction is accepted.

Related guides

• Which ERP systems does Transformance integrate with?
• What does a B2B invoice dispute workflow look like, step by step?
• How should you code customer deductions with reason codes?
• Dispute, deduction, short pay, chargeback: what’s the difference?
• How do CPG manufacturers resolve retailer deductions?
• Automate partial payments and deductions in AR

Frequently Asked Questions

How soon should you email a customer who short-paid?

Within two working days of finding the shortfall, once you have checked that no misapplied payment, discount or credit explains the gap. That is practice, not a rule.

Should the first email mention fees, interest or consequences?

No. It states the numbers, attaches the evidence and asks one dated question; consequences belong to your terms and dunning policy.

What if the payment is marked paid in full?

Do not deposit it or reply until the person who owns legal risk in your company has decided, because accepting a payment marked as full settlement can change what it means. Until then, the balance stays open.

Which ERP systems does Transformance work with?

SAP S/4HANA, SAP ECC, NetSuite, Microsoft Dynamics 365 (Finance & Operations and Business Central) and Odoo run in production with customers; Oracle and Infor are supported. The ERP connection typically takes 2-3 days; your IT team may be involved.

How large does a company need to be, and how many payments can it handle?

Mid-market to large enterprise teams with 250 to 2,000+ employees and from under 1,000 to over 100,000 payments a month, including groups with several entities.

How long does it take and what does it cost?

A full rollout takes up to 4-8 weeks (Transformance customer data, 2026). The cost depends on scope, from cash application alone to the full order-to-cash, and the number of entities: Book a Call and we size it with you.