Prosaic is the headless ledger for New Zealand and Australia: double-entry accounting as an API, with GST built in, that your customers' accountants can work in directly.
You send journals. Prosaic keeps the books: the chart of accounts, GST-coded lines, the trial balance, profit and loss and balance sheet. The same books open in the Prosaic app, where an accountant can review them, correct them and, in New Zealand, file the GST return.
Where things stand
Australia is in early access. The ledger, AU GST tax codes, an AU chart of accounts, AUD and a 1 July financial year work today. AU bank feeds and BAS are coming.
The pieces
A few words come up on every page:
- Workspace — your Prosaic account. It has users, chart-of-accounts templates and a country, and it holds entities.
- Entity — one set of books for one business. Each entity has its own chart of accounts, tax rates, currency and financial year.
- Chart of accounts — the entity's accounts, each with a code such as
4030. Journal lines name accounts by code. - Tax rate — the entity's GST codes, such as
NZ_GST_15_EXP. Every journal line with an amount carries one. - Journal — a balanced set of debit and credit lines on a date. Posted journals are what the reports read.
Ways to build
Embed the ledger
Use the REST API or the Node SDK to give your product a real general ledger. The usual shape is one entity per end customer, all inside your own platform workspace, in the way a payments platform holds one connected account per merchant. Embedded ledger walks through the model, and the quickstart takes you from an API key to a posted journal and a trial balance.
Connect to accountants
If your product serves businesses whose accountants already use Prosaic, register an OAuth app. A user approves your app, and it then works in the books they can reach, with their permissions. See OAuth apps.
Automate with extensions
Extensions are small TypeScript programs that Prosaic hosts and runs in a sandbox: when something happens in the books, on a schedule, or from a button in the app. They are the low-code option, with no servers for you to run. See Extensions.
Build with AI
Every page on this site is also published as Markdown, with an index at llms.txt and the full text at llms-full.txt. Two MCP servers sit alongside it:
https://developer.prosaic.works/mcplets a coding agent search these docs and the API reference, and scaffold and validate extensions. It needs no sign-in.https://mcp.prosaic.works/mcplets an AI assistant work in a user's own books once they sign in with OAuth.
See Build with AI.
Is Prosaic a good fit?
Good fit:
- Software for New Zealand or Australian businesses that needs a real general ledger (journals, chart of accounts, trial balance, P&L, balance sheet) without building one.
- Embedded accounting in vertical SaaS, point of sale, marketplaces and fintech.
- GST-coded bookkeeping, and NZ GST returns.
- Connecting your product to NZ accounting firms' Prosaic workspaces through OAuth apps.
- Low-code automation with sandboxed TypeScript extensions.
- AI agents that read and write the books over MCP.
Not a fit today:
- Businesses outside New Zealand and Australia.
- Multi-currency or foreign exchange. An entity keeps its books in one currency: NZD in New Zealand, AUD in Australia.
- AU BAS preparation and ATO lodgement. Both are coming.
- Payroll. Prosaic does not run pay; post payroll journals from your payroll system instead.
- Push notifications to your servers. There are no outbound webhooks, so poll the API for changes.
Next steps
- Quickstart — an API key, an entity, a journal and a trial balance.
- Authentication — API keys, OAuth, and choosing a workspace.
- Node SDK — install it and learn its conventions.
- API reference — every endpoint, with the OpenAPI document behind it.
Questions? Write to developer@prosaic.works.
