A receipt is not just a paid invoice
It is tempting to treat a receipt as an invoice with "PAID" stamped across it, but in Taiwan and Thailand a receipt is its own document, often with its own numbering sequence and its own tax-ID requirement, because it serves a different legal purpose: it is proof of payment received, which the payer's own business may need for their books.
Not every payer wants — or needs — a receipt
A meaningful share of dues and event payments come from individuals or from companies that do not need a formal receipt for their own accounting. Making a receipt optional per payment — rather than generating one for every transaction automatically — avoids cluttering records with documents nobody asked for, while still making it easy to issue one the moment a payer does ask.
Getting the tax ID right, and handling it when it is missing
- Taiwan: the 統一編號 (Unified Business Number) is an 8-digit code identifying a registered business — capture it exactly as given, since a single wrong digit makes the receipt unusable for the payer's own tax filing.
- Thailand: the equivalent taxpayer identification number follows its own format and validation rules — the same discipline applies, capture it precisely at the point of payment.
- When a company payer has not provided a tax ID, flag the receipt clearly as missing one rather than silently issuing it without — a receipt without a tax ID is often unusable for the payer's own accounting, and it is far easier to collect the ID before issuing than to chase it down after the fact.
- Individual payers frequently do not have a business tax ID at all, which is a legitimate reason for a receipt to have none — the flag is for company payers with a missing ID, not a blanket requirement.
Receipts should stay editable — invoices should not
Unlike an invoice, which is a locked legal record from the moment it is issued, a receipt sometimes needs a correction — a tax ID added after the fact, a billing name fixed. Building the receipt as its own editable object (distinct from the invoice it relates to) lets a chamber fix a genuine data-entry error without reopening or reissuing the underlying invoice.
Where Chamberflow fits
Chamberflow treats receipts as optional, per-payment objects with their own numbering sequence, clearly flags a company payer with no tax ID on file, and keeps the receipt editable for genuine corrections without touching the underlying invoice record. It does not force a receipt on every payment, and it does not let a missing tax ID slip through unnoticed.