
Plenty of teams start with “it is just invoices and totals” and meet the hard parts later: rounding, tax, corrections and audits. This guide is for developers and founders considering a build. It is general guidance, not legal or tax advice.
Should you build at all?
Build when accounting is part of your product, for example a marketplace or vertical tool that needs ledger-backed invoicing. If you only need to record invoices from your own app in a normal set of books, integrate with accounting software through an API instead. AvrioBooks has a REST API for this. See the developers page and API documentation.
Core features
- A double-entry ledger. Every transaction is a set of debits and credits that balance. Reports are views over the ledger, not separate tables. See what is double-entry bookkeeping.
- A chart of accounts. Assets, liabilities, equity, income and expenses, editable by the user. See the chart of accounts.
- Invoices, bills and credit notes with sequential numbering, line items and statuses.
- Tax rates per line, with correct rounding and reporting.
- Payments and allocation against invoices, including partial payments.
- Bank import and reconciliation. See bank reconciliation explained.
- Multi-user access with roles and permissions.
- An audit trail of who changed what and when.
- Period locking so closed periods cannot change.
- Export and reports: profit and loss, balance sheet, trial balance and ageing.
Common mistakes
- Using floating-point numbers for money. Use integers (minor units) or a decimal type, and define your rounding rule up front.
- Editing posted entries. Correct with a reversing entry or a credit note, not by overwriting. History must stay intact.
- No audit trail. You will need it the first time a customer asks why a figure changed.
- Gaps or duplicates in invoice numbers. Generate numbers inside a transaction, and decide how voids are handled.
- Tax rounding per document instead of per line (or the reverse), without checking which rule your jurisdiction expects.
- Time zones and date boundaries. A sale just before midnight can land in the wrong period. Store dates deliberately.
- Multi-currency as an afterthought. Store the original currency, rate and base-currency amount, and plan for revaluation. See foreign currency gains and losses.
- Weak tenant isolation. One customer must never see another’s data. Test this explicitly.
- Skipping lock dates. Someone will edit last year’s numbers after the accountant has finished.
- Underestimating tax and regulation. Rules such as Making Tax Digital for VAT change, and some jurisdictions require specific invoice content.
A sensible build order
- Ledger and chart of accounts, with tests that every entry balances.
- Invoices and payments.
- Tax and reporting.
- Audit log, roles and period locks.
- Bank import, then reconciliation.
If you integrate instead
AvrioBooks provides a REST API, and the app is built by Qodexify. See about AvrioBooks. We would still suggest checking whether the API covers your use case before committing to either route.
Frequently asked questions
Should I build my own accounting software?
Only if accounting is core to your product. Otherwise integrate with existing software through an API.
Why not store money as floats?
Floating-point numbers cause rounding errors. Use integers in minor units or a decimal type.
How should I handle corrections?
Use reversing entries or credit notes so history stays intact, rather than overwriting posted transactions.
Does AvrioBooks have an API?
Yes. There is a REST API. See the developers page and API documentation.
Keep reading
Private by design: why accounting data should not go to an outside AI service
Your accounts hold customer names, bank details and tax data. Think carefully before sending any of it to an outside service.
18 November 2026 · 6 min readAccounting trends 2026: what is real and what is hype
Every year brings a list of accounting trends. Here is which ones will change your work and which you can ignore.
10 November 2026 · 7 min readBookkeeper vs accountant: which do you need, and when?
They are not the same job. Here is what each does and which one your business needs now.
8 November 2026 · 6 min read