Does it change our working papers?

No. It reads them. Nothing is written back into a source system, and nothing inside the memory overwrites anything: the record is append-only, so a later figure sits beside the earlier one rather than replacing it.

What about spreadsheets?

A sheet is laid out as a table without interpretation before a model reads the figures from it, and each figure cites the sheet it came from. Records from a connected CRM are the only ones that skip the model entirely.

Can two offices share one memory?

Yes, and they still see different things. Visibility is composed from the permissions of the sources, so an office whose files are separate stays separate inside it.

Does it file anything?

No. It is not a system of record: it does not submit, sign or file. It holds what the practice already produced and tells you where each part came from.

For accountancy practices

Engagements and working papers, joined across systems

The practice management system knows the engagement. The working papers know the numbers. The correspondence knows what the client said. Nothing knows all three, so every year the join is made again by hand. Nemosyne makes it once and keeps it.

Start free → Request a demo

Where the work already lives.

Read in place, including the systems whose values need no interpretation at all.

Working papers and trial balances, in the document store or the engagement file.
Exports from the practice management system — engagement lists, deadlines, who is responsible — in the document store.
Filed statutory accounts, and the public register they went to.
Client correspondence — the email that explains the unusual journal.
Ledger exports and trial balances from the bookkeeping system, read as tables.

A spreadsheet is laid out as a table, exactly as it was, before any model reads it, and each figure taken from it cites the sheet. Records from a connected CRM land field by field with no model at all.

Three kinds of recurring work.

The same three shapes come round every quarter. What changes is not that the work disappears — it is that nobody has to reassemble the record before it can start.

Year-end preparation

last year's file is rolled forward and the exceptions are rediscovered, because the reason for each one lived in an email.

the prior year's treatment and the reason recorded at the time come back with their documents, dated, beside this year's papers.

The review point

a reviewer asks why a balance moved and the answer is reconstructed from the ledger and somebody's memory.

the reviewer asks why the balance moved, and the documents that discuss it come back cited — or nothing does, which is itself the answer.

Questions across the portfolio

“which of our clients have this exposure” means asking every manager and hoping.

the question is a query over the practice's own record, and each answer names the file it came from.

A worked example.

Illustrative — the firms, names and figures below are invented

Hallam & Co prepares the statutory accounts for Redwing Manufacturing. A stock provision that was released last year appears again this year, at a different figure.

Papers · FY24: Stock provision of €340k recognised; basis recorded as slow-moving lines.
Email · FY24: The client's finance director explains it relates to one discontinued product.
Accounts · FY24: Filed with the provision released in full.
Papers · FY25: Provision of €410k recognised; no basis recorded.
Engagement · FY25: Same manager, different senior.

The FY25 provision has no recorded basis, and the FY24 basis — a single discontinued product — was released in full. Asked about the provision, Nemosyne returns both years' papers rather than treating the second as a continuation of the first, because nothing in the record connects them.

What your assistant answers.

Through the same Claude, ChatGPT or Cursor your firm already uses — one connection per firm, and each person sees only what they are allowed to see.

Why does Redwing have a stock provision again this year?

FY24's provision related to one discontinued product and was released in full on filing.

FY25's provision is larger and carries no recorded basis in the working papers.

The reviewer raises the point before the file goes out, rather than after a query comes back.

See how the answer is assembled →

The first thing we would ask you.

Are your clients companies, individuals, or both?

It is the first thing the setup asks, because Nemosyne models companies today — sole traders and individual taxpayers are not yet covered — and the answer tells you how much of the practice's book it will hold.

Questions this raises.

Does it change our working papers?: No. It reads them. Nothing is written back into a source system, and nothing inside the memory overwrites anything: the record is append-only, so a later figure sits beside the earlier one rather than replacing it.
What about spreadsheets?: A sheet is laid out as a table without interpretation before a model reads the figures from it, and each figure cites the sheet it came from. Records from a connected CRM are the only ones that skip the model entirely.
Can two offices share one memory?: Yes, and they still see different things. Visibility is composed from the permissions of the sources, so an office whose files are separate stays separate inside it.
Does it file anything?: No. It is not a system of record: it does not submit, sign or file. It holds what the practice already produced and tells you where each part came from.

Start with what your firm already knows.

Free for three people and about a hundred documents. No card, no expiry.

Start free →

Also written up for Private equity · Private credit · Legal · Tax · Audit