Receipt (Chitanță) Generator

TL;DR

Generate a simple receipt (chitanță) PDF for situations where you need to document payment/collection. Treat this as a convenience generator: requirements can vary by entity type, payment method, and accounting practice, so keep your workflow aligned with your accountant.

Who this is for

• Contractors handling cash/receipt-style confirmations.
• People needing quick paperwork for internal records.
• Anyone who needs a “payment confirmation” document that references an invoice/contract.

How to use it

1. Fill issuer and customer.
2. Add a single line item describing what the receipt is for.
3. Print/save as PDF.

When a receipt is useful (and when it’s usually not)

In many B2B situations, a bank transfer already creates a traceable payment record (bank statement + invoice reference). In other situations (cash or certain workflows), a receipt can be required or expected.

Typical use cases:

• cash payments that need a paper trail
• internal “payment received” documentation (advance/partial payments)
• archiving where finance teams want an explicit receipt linked to an invoice

What to include so it’s hard to dispute later

Even for a simple receipt, include:

• a clear receipt number/reference and date
• payer and payee (customer and issuer)
• amount, currency, and payment method (cash/bank/other)
• what it relates to: invoice number/date, contract, milestone, or service period

If you attach the receipt to an email, include the invoice reference in the email subject as well (small detail, big future savings).

Practical checklist (before you send it)

• Does the receipt clearly reference the invoice/contract it settles?
• Is the payer name consistent with the invoice (same legal entity)?
• Is the amount exactly the amount received (especially for partial payments)?
• Is the payment method accurate (cash vs bank transfer)?
• Can someone understand this receipt 6 months from now without extra context?

Best practices for contractors

Keep receipts and invoices together

When you archive, store:

• the invoice (or proforma)
• the receipt (if used)
• proof of payment (bank confirmation or cash record) in the same folder. This makes accountant reviews and audits dramatically faster.

Partial payments: be explicit

If a client pays in two parts, issue receipts that are clearly labeled (in the description/notes) as partial payments and reference the same invoice number.

Don’t use a receipt as a workaround for unclear invoicing

If you need a document to request payment, use a proforma or invoice:

• Proforma template
• Invoice PDF (quick) A receipt should confirm payment not request it.

Worked examples

Example 1: payment confirmation

Use a receipt to confirm a payment received for an invoice number/date.

Example 2: advance payment record

Document an advance payment that will be settled on the final invoice.

Example 3: internal audit trail

Use consistent numbering and keep PDFs together with invoices.

Edge cases & gotchas

• Receipt requirements can vary by accounting practice and situation.
• Make sure receipt references invoice/contract where applicable.
• Don’t confuse a receipt with an invoice. A receipt confirms payment; an invoice requests payment.
• If you receive partial payments, issue receipts that clearly state “partial payment” and the remaining balance context (in your internal notes/workflow).

FAQ

Is a receipt always required?

Not always; ask your accountant based on payment method and entity type.

Can I issue a receipt for a bank transfer?

Sometimes it’s not necessary, but some clients request it for internal processes. If you do, reference the bank transfer date/reference and the invoice number.

Does a receipt replace the invoice?

No. The invoice/proforma describes the transaction; the receipt confirms that money was received. In most workflows you need both (or at least the invoice + bank proof).

Should I keep a numbering series?

Yes, consistency helps. Use a predictable numbering approach and keep receipts archived next to invoices and contracts.

What should I read next?

See Invoice vs proforma vs receipt : when to use each.

Sources

• ANAF: https://www.anaf.ro/

Next steps (IT Jobs List)

For documents (invoice/proforma/receipt), consistency beats “perfection”: numbering rules, correct data, and complete fields.

Related tools

Related guides

• Invoice vs proforma vs receipt : when to use each

Quick recommendation

• Save your assumptions (rates, breaks, thresholds) so you can reproduce the result.
• If you use the output in an invoice/offer, include a short explanation (what’s included and what’s not).

Practical checklist (IT Jobs List)

• Verify required fields (issuer, client, number, date, description, totals).
• If you charge VAT, include base + VAT + total and the VAT rate.
• Keep consistent numbering and clear line-item descriptions.