Client Payment Receipt Email Template Guide

A customer emails to ask whether you received their payment. You open three tabs — QuickBooks, BILL, your inbox — and spend four minutes confirming what the balance actually is before you can reply. Then you type the same email you typed last time.

Every client payment receipt email template in this guide is designed to collapse that process. But the tabs still matter. A receipt email is a statement of confirmed fact, and the fact has to come from your billing system, not your memory. That distinction — receipt versus pending notification — is the first thing to get straight before you copy anything here.

---

Receipt vs. Pending: Why the Difference Matters Before You Write

A receipt is issued after payment is confirmed in your source record. An invoice is issued before payment. Those are different documents with different purposes, and conflating them creates real problems — you send a receipt, the ACH later bounces, and now you have contradicted yourself in writing.

According to QuickBooks, "invoices are issued before a business has received payment from a customer, and a receipt is issued after payment has been collected." Stripe puts it plainly: "a receipt closes the transaction and provides a record for both parties."

A pending payment acknowledgment is not a receipt. It tells the customer you received their payment instruction or that a check is in transit. It does not confirm funds. Label it accordingly — and do not use the word "receipt" in the subject line until the payment clears in your accounting system.

Before drafting any receipt email, confirm three things:

1. The payment status in your source record (QuickBooks, BILL, Stripe, etc.)
2. The exact amount received and any remaining balance
3. Who is authorised to send on behalf of the business

---

The Worked Invoice

All templates below use one consistent fictional invoice. The numbers are arithmetic — check them yourself.

Invoice #LS-2026-0412 Customer: Pinecrest USD Invoice total: $7,412.50 Payment 1 received 2026-04-28: $3,000.00 (partial) Remaining balance: $4,412.50 Payment 2 received 2026-05-14: $4,412.50 (balance settled) Total paid: $7,412.50

---

Six Copyable Templates

Template 1 — Full Payment Receipt

Use this after the entire invoice amount clears in your billing system.

Source check: Confirm the invoice shows $0.00 remaining in QuickBooks or BILL before sending.

---

Subject: Payment received — Invoice #LS-2026-0412 | Pinecrest USD

Hi Dana,

Thank you. We've received your payment of $7,412.50 in full for Invoice #LS-2026-0412 (8 sensors, 1-year licence).

Your account balance is now $0.00. A copy of the invoice is attached for your records.

Please don't hesitate to reach out if you have any questions.

[Your name] [Business name | Phone | Email]

---

Attachment note: Attach the invoice PDF directly, or include a link to a hosted receipt. If using Stripe-hosted receipt links, note that those links expire after 30 days — download and attach the PDF for a permanent record.

---

Template 2 — Partial Payment Receipt

The most failure-prone receipt email template. The risk: sending a number that doesn't match the billing record, or accidentally implying the account is settled.

Source check: Record the amount actually received and the remaining open balance from your accounting system. Do not round.

---

Subject: Payment received — $3,000.00 applied to Invoice #LS-2026-0412

Hi Dana,

Thank you for your payment. We've received $3,000.00 on 28 April 2026, applied to Invoice #LS-2026-0412.

Remaining balance: $4,412.50, due by [agreed payment date].

Your original invoice is attached. You can pay the remaining balance [here: payment link] or via ACH using the attached instructions.

If you have any questions about this balance, please reply to this email or contact our finance team at [email/phone].

[Your name] [Business name]

---

Important: The remaining balance on this email must match the open balance in your accounting system at the time of sending — not the original invoice total minus what you think was paid. Partial payments applied to multiple line items can shift the open balance in ways your memory won't catch.

---

Template 3 — Deposit or Advance Payment Acknowledgment

A deposit is a partial payment made before work begins. The invoice may not yet be fully issued. This template acknowledges receipt of the deposit without implying the full project cost is settled.

---

Subject: Deposit received — $3,000.00 | Invoice #LS-2026-0412

Hi Dana,

We've received your deposit of $3,000.00 on 28 April 2026. Thank you.

This deposit has been applied to Invoice #LS-2026-0412 (total: $7,412.50). The remaining balance of $4,412.50 will be due [per the agreed payment schedule / before shipment / on completion].

A receipt for the deposit amount is attached. Full payment confirmation will follow once the balance clears.

[Your name] [Business name]

---

Template 4 — Multiple-Invoice Allocation

When a customer sends one payment covering multiple invoices, specify the allocation clearly so both sides have a matching record.

Source check: Confirm how the payment was applied in your accounting system before sending. BILL and QuickBooks may auto-apply to the oldest invoice, which may not match what the customer intended.

---

Subject: Payment received — $7,412.50 allocated across two invoices

Hi Dana,

Thank you for your payment of $7,412.50 received on 14 May 2026. We've applied it as follows:

• Invoice #LS-2026-0411 — $2,000.00 (balance cleared)
• Invoice #LS-2026-0412 — $5,412.50 (balance cleared)

Both accounts now show $0.00 outstanding. Copies of both invoices are attached.

Please confirm this allocation matches your records. If you intended a different split, reply and we'll adjust before the books close.

[Your name] [Business name]

---

Template 5 — Pending Payment Notification (Not a Receipt)

This is what you send when a payment is in transit but not yet confirmed. Do not label this a receipt.

---

Subject: Payment instruction received — Invoice #LS-2026-0412 (pending)

Hi Dana,

We've received your payment instruction for Invoice #LS-2026-0412. The transfer is currently processing; we expect it to clear within [2–3 business days / per your bank's standard ACH timeline].

We'll send a full receipt once the funds are confirmed on our end.

If anything looks off in the meantime, please get in touch.

[Your name] [Business name]

---

Template 6 — Receipt Correction

You sent a receipt with an error — wrong amount, wrong invoice number, wrong customer name. Correct it promptly and plainly.

---

Subject: Correction: Payment receipt for Invoice #LS-2026-0412

Hi Dana,

Please disregard the receipt email sent on [original date]. It contained an error: [brief description, e.g., the amount shown was $3,000.00 but the correct received amount is $3,500.00].

The corrected receipt is attached. The remaining balance is $3,912.50.

We apologise for any confusion. If you have questions, please reply directly to this email.

[Your name] [Business name]

---

Before You Send: A Quick Review Checklist

Run through this before any receipt email leaves your outbox.

• Payment confirmed in the source system (QuickBooks, BILL, Stripe), not just a bank notification
• Amount in the email matches the amount in the accounting record exactly
• Remaining balance is correct and matches the open invoice balance in your system
• Subject line doesn't say "receipt" if payment is still pending
• Invoice PDF or receipt link is attached (check link expiry if using hosted URLs)
• Customer name, invoice number and email address are correct
• If correcting a previous receipt, the original email is clearly referenced and superseded
• The right person has approved the email before it goes out

---

What to Include and What Tax Law Actually Says

According to Stripe's receipt template guidance, a receipt email that functions as a tax document should include: transaction date, amount paid, vendor name, description of goods or services, and proof of payment.

QuickBooks recommends also including business contact information, the transaction or order number, payment method, and customer contact information where applicable.

Jurisdiction caveat: These templates are a practical starting point, not a legal or tax compliance guarantee. Receipt requirements vary by country, state and transaction type. If your receipts are used for tax deduction purposes, have an accountant review your format for your specific situation.

---

Customer Query Routing: When a Receipt Email Needs a Human

Some replies to receipt emails should go to a named person, not a general inbox. Set this up in advance:

• Disputed amount → finance lead or account owner, not the sender alias
• "I already paid" response to a follow-up → check the billing system before replying; if unresolved, flag to accounts
• Request for a different invoice format → finance or admin, not sales
• Legal language in the reply → do not respond via template; escalate immediately to the appropriate person

A good receipt email includes a direct reply path. "Reply to this email" is fine when someone will actually read it. A shared finance alias with named coverage is better.

---

Masked References in Shared Environments

If your receipt emails are drafted or approved inside a shared tool — Slack, a shared inbox, a project management system — consider masking sensitive fields in the draft view:

• Customer full name → last name + first initial in logs
• Payment method details → reference method type only in the email body (e.g., "ACH transfer"), never full account details
• Invoice totals → visible to the approver, but consider what's visible in shared channel screenshots

---

Why Checking the Source Record Is an Architectural Problem, Not Just a Habit

The templates above assume you've already confirmed the payment status. But in practice, the person drafting the receipt email is often different from the one who saw the payment clear. The information travels: QuickBooks → someone's mental model → the email → the customer. Every handoff is a place where numbers can drift.

QuickBooks Online sends automated receipts when payment is made through their payments product, but receipt email customisation has significant limitations — a saved custom template is not available in the standard QBO setup, and you must manually edit the message before sending each time. BILL's payment notifications to vendors are system-generated and cannot be customised at all.

That's the gap these templates address: the email your customer actually reads when a payment lands.

For teams running Salesforce → QuickBooks → BILL workflows, the Finance Collections Agent from Splice Work addresses one part of this problem directly. Before every follow-up reminder, it checks payment status in BILL and QuickBooks. If an invoice shows as paid, the reminder never goes out. If the payment is partial, the reminder is rewritten from the actual remaining balance. If payment status can't be read, it sends nothing and flags the row for a human. Every email — including the initial invoice email — sits as a draft in Slack until a person clicks Send.

That's not automated receipt generation (a separate capability not described on the agent page). It's a verification step before any customer-facing finance email goes out, which is the same principle these templates ask you to apply manually. The draft-then-approve model described in Splice Work's AI email reply post makes the same point: a convincing draft cannot substitute for a verified fact. The approve step exists precisely to catch the moment where a draft says "$7,412.50 received" and the source record says "$3,000.00."

---

Exercise: Audit Your Last Five Receipt Emails

Pull the last five receipt or payment confirmation emails your business sent. For each one, check:

1. Did the amount in the email match the amount recorded in your accounting system on the date it was sent?
2. If a balance remained, did the email state the correct remaining amount?
3. Was the email sent before or after payment was confirmed in the source record?
4. Who approved it before it went out?

If you find a mismatch on any of those four questions, you've found the step in your process that needs a check — whether that's a manual confirmation step, a second set of eyes, or a more structured approval before finance emails reach customers.

If the Salesforce → QuickBooks → BILL handoff is where things go sideways, describe that workflow to the Splice Work team and they'll walk through whether the Finance Collections Agent fits.