The Auditor Who Only Needs to Read
The external auditor needs to read your books for three weeks, not run them. A login that ends on a date, sees the accounting screens and nothing else, cannot write, cannot skip MFA, and logs every page it opens — and beside it, the year’s evidence in one ZIP with a checksum on every file.
Fieldwork at a Nairobi children’s charity starts on the 3rd. The audit senior from the firm wants the trial balance, the general ledger for the year, the bank reconciliations with their statements, the fixed asset register and a sample of journals with their approvals. In past years that was a fortnight of exports, a shared folder nobody could prove was complete, and an administrator login lent to the firm because it was the only login that could see the ledger.
The login that was too powerful
Lending an administrator login to an auditor is common and it is wrong in three ways. It can change the records being audited. It does not end when fieldwork ends. And whatever it did is recorded under somebody else’s name. We wrote about the shape of that problem in the auditor who has to be an administrator. The answer is not a better password policy. It is a different kind of login.
An auditor login with an end date
Under Accounting, Auditors, someone with the right permission invites the auditor by name, firm and email, with an end date no more than 180 days away. The address must not already belong to an AWRA account, so the firm uses an address for this engagement only, and the login cannot be confused with anyone else’s. The auditor gets a welcome email, sets their own password and, before they see a single figure, sets up multi-factor authentication. Until they do, the only screens that open are the MFA setup and sign-out.
- Reads only. Any request that would change something is refused, whatever permissions the role is later given. The role is a second fence; the guard on every request is the first.
- The accounting screens, and nothing else. General ledger, trial balance, income statement, balance sheet, cash flow, receivable and payable accounts, fixed assets, ageing, drill-down to an account or a posting, periods and their close evidence, certified statements and journal attachments.
- Every request logged. Allowed or refused, each page the auditor opens is written to the access log you can read on the auditor’s record.
- A seat while live. The auditor uses a seat on your plan for as long as the access lasts, and frees it the moment it ends.
The auditor’s access ends on the date you set, not on the day someone remembers to switch it off.
Access stops at the end date the moment it is checked, at every door. An hourly job then tidies up: the account is deactivated, its sessions and mobile tokens are deleted and the seat is freed. A missed run never extends anything, because the date was already being enforced. If fieldwork overruns, extend the access to a new date inside the same 180-day rule; if the engagement ends early, revoke it with a reason. Both are recorded.
The evidence pack
The second half is the folder. Under Accounting, Evidence packs, request a pack for a period of up to 400 days, which is one fiscal year with room for a short extension. It is built in the background, you are emailed when it is ready, and it is one ZIP with a fixed layout the audit senior can navigate without a guide.
| Folder | What is in it |
|---|---|
| 01 Trial balance | Opening, period debits and credits, and closing per account |
| 02 General ledger | Every ledger line in the period |
| 03 Statements | The certified statements for the period, or the income statement and balance sheet |
| 04 Bank reconciliations | Reconciliations dated in the period, with their attachments |
| 05 Agings | Receivables and payables open at period end |
| 06 Fixed assets | The register with depreciation to period end |
| 07 Journals | Postings with their approval trail |
| 08 Close | Close checklists, period closes, reopen requests and integrity checks |
| 09 Audit log | The accounting audit trail for the period |
| 10 Attachments | Journal and bill attachments, optionally only above an amount |
An index page and a manifest list every file with its size and a SHA-256 checksum, so the firm can show that what it tested is what you sent. An attachment over 25 MB, or one that would take the pack past 500 MB, is not silently dropped: it is listed as skipped, with the reason. The ZIP is kept for thirty days and then deleted, while the record of the pack stays as history.
Giving the auditor the pack
A pack can be granted to an auditor’s access, and then appears on the auditor’s own landing page to download for as long as both the access and the pack last. Withdrawing it is one click, and both actions are in the log.
For the charity, the senior signs in on the 3rd, sets up MFA, downloads the pack, and spends the first week in the ledger drilling from the trial balance to postings and their attachments without asking anyone to export anything. When the donor asks later whether the auditor could have changed a figure, the answer is on the access log rather than in somebody’s memory. How the second signature on a journal reaches the auditor’s file is in the second signature and the file the auditor keeps.
Three questions before your next audit
Which login did the auditors use last year, and is it still active?
What you will probably hear
The finance manager’s, I think.
How to read it
Then their work is under someone else’s name and the access may still be open.
Could that login have changed a figure?
What you will probably hear
It could, but they would not.
How to read it
An auditor should not have to be trusted with write access they have no use for.
How do we prove the files we sent were complete?
What you will probably hear
They are in the shared folder.
How to read it
A manifest with a checksum per file is proof; a folder is a hope.
What AWRA OpsHub does today
- Auditor logins with an end date no more than 180 days ahead, extendable and revocable with a reason.
- Reads only, on an allow-list of accounting screens, enforced on every request whatever the role is given.
- MFA before anything else, and every request, allowed or refused, logged.
- Hourly expiry that deactivates the account, ends sessions and tokens and frees the seat.
- Evidence packs for up to 400 days: ten folders, an index and a manifest with SHA-256 checksums.
- Packs granted to an auditor and downloaded from their own landing page, kept for thirty days.
More we can add to your workspace
- Auditor queries attached to a ledger line, answered by your team in the same place. Commission it
- A prepared-by-client request list the firm ticks off as items arrive. Commission it
- Auditor access limited to a date range on the ledger screens, such as the year under audit only. Commission it
- Payroll and inventory sections in the evidence pack, beside the accounting ones. Commission it
- An evidence pack built automatically at year end, ready before fieldwork is booked. Commission it
Where we point you to a specialist
- We give an auditor the records and a trail of how they were made. The opinion is theirs, and so is the judgement about what to test.
Queries on a ledger line are the extension firms ask for first, because the auditor is already looking at the line.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsWhere this leaves you
Give the auditor their own login, with an end date, reads only, MFA first and every page logged, and hand them the year in one ZIP with a checksum per file. Nobody lends an administrator password, and nobody rebuilds the shared folder.
See external auditor access
Time-limited, read-only auditor logins and evidence packs with a manifest and checksums.
Explore auditor accessFrequently asked questions
Can an external auditor change anything in AWRA?
No. Every request from an auditor login that would change something is refused, whatever permissions the role carries.
How long can auditor access last?
Up to 180 days from the day it is set, and it can be extended within the same rule or revoked early with a reason.
Does the auditor need multi-factor authentication?
Yes. Until MFA is set up, an auditor login can reach only the MFA setup screens and sign-out.
What is in an evidence pack?
Ten folders: trial balance, general ledger, statements, bank reconciliations, agings, fixed assets, journals with approvals, close records, the accounting audit log and attachments, plus an index and a manifest with a checksum for every file.
How long is an evidence pack kept?
Thirty days. The file is then deleted and the record of the pack stays as history.