Ask for one document. Build the audit pack from it.
Pick the auditor's request and this says the smallest thing to ask the client for — usually the bank statement PDF and nothing else — then builds the working paper from it against the ledger you already hold.
An audit request is usually answered with a questionnaire back to the client asking for six things, two of which the client cannot produce and one of which you already have. What comes back is a screenshot and a spreadsheet someone retyped, so the tie-out starts again. The slow part is never the arithmetic. It is deciding what document actually answers the question, and then turning whatever arrived into a working paper that a reviewer will accept.
How it works
Open the request
Every auditor request in your engagement list is here with its type, its status and what is already attached to it. Bank balances, creditor confirmations, stock listings, payroll, fixed assets, opening balances and prior-year adjustments are recognised by name.
Get the one-line ask
Instead of a checklist, it names the single document that answers the request and the format the client can produce without effort — a statement PDF downloaded as it appears on screen, not a schedule rebuilt in Excel. If the evidence is already attached, it says so and stops asking.
Send it and upload what comes back
The wording is ready to paste into an email. The file lands against the request, its text is read out of the document — including a compressed PDF — and the ledger side is taken from your own books, so nothing is retyped.
Build the pack
Opening balance, movements, closing balance, agreed against the statement. Where the two differ, each difference is a named line with the amount and the suggested clearance: unpresented items, deposits in transit, a fee taken inside a payment, a transfer between your own accounts, a posting in the wrong period.
Leave something a reviewer can read
The working paper, the schedule rows and the difference list go into the audit pack export with the evidence files alongside them, and the note back to the auditor is drafted from what the engine found rather than from memory in December.
Outcomes, not features.
- One document to ask for, in words you can send as they are
- A working paper built from the upload instead of a blank template
- Every difference listed with an amount and how to clear it
- Opening and closing balances agreed where they were only asserted before
- The evidence, the schedule and the export in one place for the auditor
- Nothing invented: a figure it cannot find in the document or the ledger is reported as missing
Questions
No, and that distinction is the point. The tie-out is arithmetic run against your ledger and the text of the uploaded document by the same engine the audit pack always used. The model chooses which document to ask for, words the request to the client and phrases the summary. If the arithmetic does not agree, no amount of wording makes it agree, and the screen reports the difference instead.
One PDF: the statement covering the period, with opening and closing balances visible. The transaction lines inside it are matched against the bank ledger you already have, so the client does not need to prepare a reconciliation or export anything into a template.
It says what is still missing before the pack is described as ready, and the same one-line ask is regenerated for what remains. A screenshot of a balance is treated as backing, not as a schedule.
No. It is a preparation tool for the firm answering an auditor, and anything it writes is labelled as decision support rather than professional audit advice. A reviewer signs the working paper.
The request title, its type, the filenames already attached and the ledger figures our own tools returned. Not the body of the client's documents, and never account numbers, sort codes or credentials. With the add-on switched off for your workspace the same screens are produced by the rules engine and nothing is sent.
See it on your own numbers.
Start the trial and import your ledger export — or book a walkthrough first.