Nemosyne
Menu

For audit and assurance

Audit evidence that keeps its source

An audit is a chain of evidence, and the chain is the part that gets lost: last year's workpapers were rolled forward at the click of a button, the management letter is in a folder, and the reason a judgment was made is in nobody's file. Nemosyne holds the evidence with its provenance, because here provenance is the product.

Where the work already lives.

The file you already hold, read as a file rather than as a folder.

  • The audit file: workpapers, testing, and the conclusion reached on each area.
  • Prior-year files, including whatever was rolled forward without being re-examined.
  • The management letter, and the client's written responses to it.
  • Client-provided schedules, confirmations, and the correspondence around them.
  • The engagement letter, independence records, and the acceptance decision.

Every claim the memory holds cites the passage of the document it came from. A citation is not a footnote here, it is the mechanism — an answer that cannot name its source does not get assembled.

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.

Planning from last year

the prior file is rolled forward and the risk assessment quietly inherits judgments nobody has re-tested.

each year's opinion, basis and findings are held against their own period, so what last year concluded is not silently read as this year's.

Following up the management letter

last year's points are chased by re-reading last year's letter and asking whether anything happened.

ask about a point and the answer gives last year's finding, the client's response and any later document that mentions it, each cited — and says so when it finds nothing.

Answering a reviewer

the evidence behind a conclusion is reassembled from the file, under time pressure, by whoever is available.

the conclusion still names its evidence, so the reassembly is a read rather than an excavation.

A worked example.

Illustrative — the firms, names and figures below are invented

Pellworth Audit LLP audits Kestrel Foods. Last year's management letter raised a control weakness in purchase approvals, and this year's planning needs to know whether it was remediated.

Letter · FY24
Raises a purchase-approval control weakness; recommends dual authorisation.
Response · FY24
Management undertakes to implement dual authorisation by Q2 FY25.
Papers · FY25
Control testing rolled forward from FY24 without re-performance.
Minutes · FY25
The board approves a new purchasing system; no go-live date is recorded.
Correspondence
No document records the control actually being implemented.

The undertaking has no evidence of completion, and this year's testing was rolled forward rather than re-performed. Asked about the point, Nemosyne returns both side by side, because separately each is unremarkable and together they are the planning point.

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.

Was last year's purchase-approval point remediated?

Management undertook to implement dual authorisation by Q2 FY25; no later document records it being implemented.

FY25 control testing was rolled forward from FY24 rather than re-performed.

The manager opens the client response and the workpaper and decides. The memory raises the point; it does not conclude on it.

See how the answer is assembled →

The first thing we would ask you.

What assurance work do you actually do — statutory audits, reviews, compilations, agreed-upon procedures?

Each kind of engagement leaves a different trail: an opinion and its basis, a review conclusion, a compilation, a report of factual findings. The mix decides what the memory has to keep, and we would rather hear it before you connect anything.

Questions this raises.

Is the trail exportable?
Yes, as a file, though not yet from your console. Administrative actions are recorded and readable in your console, and reads are logged — who read, what they asked, and which sources the answer cited. Both export as a file you can hand an inspector, for any period; on the hosted service we run that export for you on request. The read record has no screen yet, and that is published on our trust page as a known limit.
Can it conclude on an audit area?
No. It assembles cited evidence, flags where sources disagree, and says when the evidence for a point is not there. The conclusion is the auditor's, and nothing in the design is trying to change that.
How does it treat a rolled-forward workpaper?
As a document with a date. Last year's paper stays on file beside this year's, so the two can be read together, and where a workpaper records that it was rolled forward, the answer says so.
Does it need access to the client's systems?
No. It reads the audit file you already hold. Connecting a client system is possible, separate, and carries its own permissions.

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 · Accountancy