GST/VAT billing is a rules engine plus an audit trail. Rates, place of supply, registration thresholds and invoice content vary by jurisdiction; the software must make the correct treatment explicit.
Key takeaways
- Store the tax rate, jurisdiction, place of supply and the legal basis for each line.
- Validate tax IDs where the rules require it; do not trust a client-side check.
- Invoice content and numbering requirements vary by country.
- Model the state and the exceptions before building the happy path.
What the system must model
- Credit notes and refunds must adjust the tax correctly.
- Keep an audit trail of rate changes and filings.
How to build it
- Map the jurisdictions. Where you sell, where you are registered and the thresholds.
- Define the rules. Rate, place of supply, exemptions and reverse charge.
- Configure invoices. Content, numbering, currency and rounding.
- Validate tax IDs. Use the official service where required.
- Test scenarios. Domestic, cross-border, B2B, B2C and refunds.
- Reconcile and file. Report totals to the accountant and keep evidence.
Design decisions
| Area | What to decide | Why |
|---|---|---|
| Jurisdiction | Registration and thresholds | Get professional advice |
| Rate | Product/service and date | Rates change |
| Place of supply | B2B/B2C and location | Often the hardest rule |
| Invoice | Content and numbering | Legal requirements |
| Credit notes | Tax adjustment | Keep the link to the invoice |
| Audit | Rate history and filings | Evidence for inspections |
Controls and reconciliation
- Keep an audit trail for money, tax and access changes.
- Make every event idempotent; retries are normal.
- Reconcile the provider, the ledger and the bank on a schedule.
- Test failure paths: declined payments, duplicate webhooks, refunds and partial payments.
- Document who owns finance, tax and technical support.
A minimum data model
| Entity | What it must hold | Why it matters |
|---|---|---|
| Customer | Identity, tax status, addresses, consent | Invoices and tax depend on it |
| Product/plan | Price, currency, tax code, effective dates | Prices change over time |
| Invoice | Lines, tax, due date, status | The legal record |
| Payment | Provider ID, amount, status, timestamps | Reconciliation |
| Credit/refund | Reason, amount, approval | Revenue and tax corrections |
| Audit event | Actor, action, before/after | Disputes and controls |
Launch checklist
- Test a full lifecycle: quote, invoice, payment, refund and credit note.
- Test a failed payment, a duplicate webhook and a manual retry.
- Reconcile a full day of transactions against the provider and the bank.
- Check tax rounding, currency formatting and negative amounts.
- Give finance a read-only view and a documented correction process.
- Monitor queue depth, failed jobs and reconciliation differences.
Failure modes to design for
| Failure | What the system should do | What to monitor |
|---|---|---|
| Duplicate webhook | Ignore by event ID; keep one ledger entry | Duplicate-event count |
| Payment timeout | Show an unknown state; reconcile, never assume failure | Pending payments |
| Price change mid-cart | Revalidate and show the new total | Price-mismatch errors |
| Partial refund | Adjust the invoice and tax proportionally | Refund reconciliation |
| Currency mismatch | Reject or convert with an explicit rate | FX differences |
| Job backlog | Alert before invoices or emails are late | Queue age |
Operational metrics
- Invoices created, paid, overdue and failed, by day.
- Reconciliation differences and the time to resolve them.
- Payment success rate by method and market.
- Tax and currency exceptions that required manual review.
- Time to close the month and the number of manual journals.
- Support tickets per hundred transactions.
Common mistakes
- Building the checkout before the billing state model.
- Trusting client-side amounts, currencies or tax rates.
- Ignoring refunds, credit notes and failed payments.
- Launching without daily reconciliation.
Frequently asked questions
Stripe Tax can calculate tax, but you are still responsible for registration, filing and the correctness of the treatment. Confirm with an accountant.
Check the place-of-supply rules, reverse charge and valid tax ID requirements for each jurisdiction. Do not assume one rule fits all.
Requirements vary, but typically seller details, customer details, invoice number, date, description, net amount, tax rate/amount and total. Check the local rules.
Issue a credit note, adjust the tax and keep the link to the original invoice. Reconcile the refund in the ledger.
Sources and further reading
- GOV.UK: VAT (gov.uk)
- EU VAT rules for businesses (europa.eu)
- Stripe Billing documentation (docs.stripe.com)
Related services
Building a billing or POS flow?
Describe the plans, currencies and payment methods. I will map the state model and the reconciliation points before you build.
How to cite this guide: Nur Hossain Repon, “Build GST/VAT billing for your business: guide”, Nhrepon Portfolio, reviewed October 2026, https://nhrepon.com/posts/build-gst-vat-billing-for-your-business-guide.





Comments
No comments yet.