Early access — now open

Just ask. Your books answer.

Zympli reads what your bank and your suppliers sent you and builds the ledger. Then you can ask it anything about your own numbers — in plain English, with no chart of accounts in sight.

No accounting knowledge needed
Built from your own documents
Your rules beat the AI
zympli.com Preview

How are takings tracking this month?

$38,600 so far — about 6% ahead of last month at the same point.

Takings · week by week

W1W2W3W4W5

What am I paying my suppliers?

$11,240 this month. Dairy and coffee beans are two thirds of it.

Suppliers · this month

Dairy $4,180
Coffee beans $3,510
Everything else $3,550

There's a $420 payment I don't recognise last Tuesday.

SQ *TRADE SUPPLY — no invoice against it. It's the only unmatched payment over $100 this month.

Ask Marta for the invoice.

Asked her. I'll match it and code it when it arrives.

1 document requested

awaiting Marta

The bean roaster invoice is always cost of sales.

Saved.

Rule saved · Roaster → Cost of Sales

14 past payments recoded

Can I claim the coffees I give the staff?

There's published guidance on staff amenities versus entertainment and I can show it to you — but which side yours falls on is a registered accountant's call.

Send to a registered accountant

Your file goes with it, already prepared

Ask Zympli anything about your books

See it for your kind of books

What happens to your documents Live

There is a machine behind the conversation

This part is running in production today. It is what lets the assistant answer from evidence rather than from a guess — every figure it gives back has the document it came from still attached.

01

Upload

Bank statement PDFs from Westpac, ANZ, CommBank and NAB. CSVs, spreadsheets, photos of receipts.

02

Extract

Every transaction pulled out — date, merchant, amount — with the document it came from still attached.

03

Classify

Your rules run first, then your own confirmed examples, then the model. Never the other way round.

04

Review

Only what the engine couldn't settle reaches you. Nothing posts until a person confirms it.

The full detail — bank by bank, rule by rule — is on the business page.

Why it's different

Three things that are hard to copy

The ledger is built from your documents

Not inherited from someone else's file. So every figure keeps the invoice or statement line behind it, and the assistant can show you what it used.

Your corrections become permanent

Fix a coding once and it becomes a rule that runs before the model, on every future document. It gets better because you used it — and that improvement is yours, not a shared model's.

The hard questions reach a registered human

With your file attached. Not a name from a directory to go and chase — an accountant opening books that are already built, classified and auditable.

The model

A business, an engine, and a registered human

Most accounting software sells to one side or the other. The interesting part is what happens between them — and it happens at the exact moment the software has to stop.

The business Live

Keeps its own books, without keeping them

Uploads whatever the bank and the suppliers sent. Gets a classified ledger, reports, and an answer when it asks what the numbers say. Never codes a transaction.

  • Documents in
  • Ledger and reports out
  • Asks its own books
Zympli In build

Answers what it may, and stops where it must

Builds the ledger from the documents themselves, so every answer has evidence behind it. Facts about the books it will answer. A tax treatment it will not — it drafts the position instead and hands it over.

  • Rules, then your examples, then AI
  • Cites what it used
  • Knows where the line is
The firm Planned

Reviews what crossed the line, and signs it

Receives a drafted position on books that are already built, classified and auditable — with the part that needs a registration clearly marked. Confirms or corrects, and releases it signed.

  • A prepared file, not a lead
  • Reviews rather than rebuilds
  • Signs under their registration

“This needs to be validated by an accountant” stops being a warning and becomes a price tag.

The moment the software has to stop is the moment it can hand you someone who doesn't — with your file already prepared. That handover is designed and priced. It is not built yet, and nothing on this site charges for it.

No surprises

Where the product is today

We are in early access and some of what is described on this page is not finished. Rather than leave you to find out which parts, here is the whole list.

Live

Running in production

  • Documents in — extracted, classified, reviewed
  • Chart of accounts, templated by industry
  • Rules engine, running ahead of the AI
  • Review queue with live progress
  • Balance Sheet, P&L, General Ledger, FY statements
  • The workspace accounting firms use for their clients
In build

Being built now

  • The self-managed experience for a business keeping its own books — it works, but it still wears the shape of the firm product
  • Provider connections, the prerequisite for any agent turn at all
Planned

Designed and priced, not built

  • The agent that operates the platform and explains what it did
  • Access from your own AI client, over MCP
  • The link between a business and its accountant, with consent and scope
  • Escalation to an accountant-validated position

A working engine, a designed business, and the layer between them still to build. That is the honest position, and it is why we are asking for your email rather than your card.

Early access — now open

Get the books off your desk

Early access is open to Australian businesses keeping their own books, and to the practices that keep them for others. Tell us which you are and we'll come to you when your side is ready.

Built in Sydney · Australian data infrastructure · No lock-in