Skip to main content

Receipt template

A record of a payment received, listing what it settles, generated one per payment from your payments data.

Google Docs PDF export No watermark
Start automating See how it automates

Free plan, no credit card. Bring your own design or start from this layout.

The actual template Receipt template shown in Google Docs

What’s in this template

Every block is bound to a field in your data. The layout stays exactly as designed; only the values change from one run to the next.

  • Header with your logo and receipt number {{receipt.number}}
  • Date paid and payment method {{payment.date}} · {{payment.method}}
  • Received-from block from the payer record {{customer.name}}
  • What the payment settles, one row per invoice loop: {{allocations}}
  • Amount received and balance remaining {{payment.amount}} · {{customer.balance}}
  • Reference and thank-you note {{receipt.reference}}

How this template fills itself

Connect Airtable, Google Sheets, a SQL database, a CSV or a REST API, map each field to a placeholder, and generate. One run can produce a single document or one per matching record.

Billing & operations: A record of a payment received, listing what it settles, generated one per payment from your payments data.

Payments · billing system via REST API

ReceiptPayerReceived
RCP-2211Acme Co$4,800
RCP-2212Northwind$1,250
RCP-2213Globex$6,200

Template: Google Slides or Docs

{{receipt.number}}

Receipt · paid {{payment.date}}

{{customer.name}}

loop: {{allocations}} → row

{{payment.amount}} received

one receipt per payment, listing the invoices it settles

Generated output

DocsPDF

RCP-2211

Receipt · paid 12 Sep 2026

Acme Co

2 invoices settled

$4,800 received

Start automating

Who uses this template

Service businesses

Send a receipt the moment a payment lands, showing exactly which invoices it cleared.

Read the guide

Finance and bookkeeping teams

Issue a month of receipts in one run from the payments table instead of writing them one by one.

Read the guide

Membership and subscription operators

Produce a dated receipt for every renewal so members have a document for their own records.

Read the guide

A receipt is the counterpart to the invoice: it is written after the money has moved, and its job is to say how much arrived, when, by what method, and against which invoices. Because a single payment can clear several invoices at once, the settled-against table is the part that varies, which is why this is a Google Doc rather than a fixed slide.

Let the payment record decide what the receipt says

The cleanest setup treats the payment as the source record and the invoices as its children. The receipt then places the amount, date and method from the payment, and repeats a row for each allocation underneath. Nothing is retyped and nothing is totalled in the document, so the receipt can never claim a figure your ledger disagrees with. If a payment is later reallocated, you correct it in the data and regenerate rather than editing a PDF that has already been sent.

Related templates

All billing & operations →
Invoice template for Google Docs: the actual Google Docs template Google Docs

Invoice template for Google Docs

A billing document with a line-item table that grows with the job, generated one per record from your billing data.

View template
Credit note template: the actual Google Docs template Google Docs

Credit note template

A document that cancels part or all of an invoice, naming the lines credited and the reason, generated one per credit from your billing data.

View template
Statement of account template: the actual Google Docs template Google Docs

Statement of account template

A period summary of a customer's invoices, credits and payments with a running balance, generated one per account from your ledger data.

View template
Delivery note template: the actual Google Docs template Google Docs

Delivery note template

A record of goods handed over and signed for on arrival, generated one per delivery from your dispatch data.

View template

Common questions, answered

How is a receipt different from an invoice? +
An invoice asks for money and a receipt confirms it arrived. The two documents carry different dates, different numbering and a different table: an invoice lists the work, a receipt lists the payment and the invoices it was applied to. Generating them from separate records keeps that distinction intact rather than reusing one layout for both.
Can I issue receipts in a batch? +
Yes. Filter the payments table to everything settled since the last run and one pass produces a receipt per payment, each with its own allocations and amount. Many teams run it on a schedule so receipts go out daily without anyone starting the job.
What if one payment covers several invoices? +
That is the repeating block. The allocations table repeats a row for each invoice the payment was applied to, with the amount against each, and the page grows to fit. A payment clearing one invoice and a payment clearing nine both come out laid out correctly.
Can I use my own receipt design? +
Yes, and most teams do, because a receipt should look like it came from the same finance function as the invoice it settles. Build the master in Google Docs with your own letterhead, spacing and wording, mark the number, amount and settled-against table as placeholders, and generate against that instead of this layout.

Generate this document from your data

Start on the free plan, connect a data source, and export a real Google Docs document. No watermark, no credit card.

Start automating See pricing