Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Let the auditor in to read. Only to read, only until the date you set.
Invite your external auditor as a time-limited, read-only user. They sign in with MFA, see the ledger, the statements, the close and the evidence packs you grant — and nothing else. Every request they make, allowed or refused, is written to a log you can read. When the end date passes, the access closes on its own.
- J. Mwangi · Audit firmAccess ends 31 March · MFA set upRead only
- Evidence pack · Jan–Dec 2026Granted to this auditorReady
- Viewed trial balance09:14
- Opened posting JE-2207 and its attachment09:21
- Tried to edit a journalRefused · writes are never allowed09:26
Illustration of the record’s shape. Names and times are examples.
Invite, scope, watch, close.
Invite
Name, an email address used only for this engagement, the firm, an end date within 180 days, and the evidence packs to grant. The auditor gets a set-password email.
They set up MFA
Until they do, the only screens open to them are MFA setup and sign out. Every sign-in method runs your workspace’s normal sign-in checks.
You watch the log
The access record lists every request with its time and whether it was allowed. Grant or withdraw packs, or extend the date, at any point.
It closes itself
An hourly job ends access on the end date. Revoke sooner with a reason, and their next request is refused.
An allow-list of screens, enforced on every request.
The External Auditor role carries read permissions only, but the role is the second fence, not the first. A guard on every request checks the auditor flag, so a write permission added to that role later changes nothing.
What an auditor can open
- The general ledger and trial balance, with drill-down to an account and to a posting.
- Income statement, balance sheet and cash flow, and certified statements with their exports.
- Receivable and payable accounts, aging and fixed assets.
- Accounting periods, close evidence and the close checklist, and journal attachments.
- Their own home page with the evidence packs granted to them.
What is refused
- Any write, anywhere, except signing out and the MFA screens.
- Every screen outside the list — stock, sales, payroll, settings, people.
- Packs you have not granted.
- Anything at all once access is revoked or past its end date, whatever the session says.
One period’s books in one file, with a fingerprint for every page.
Ask for a period of up to 400 days and the pack is built in the background, then emailed as ready. It holds the trial balance, general ledger detail, statements, bank reconciliations, agings at period end, the fixed asset register with depreciation, journals with their approval trail, the close and its integrity checks, the accounting audit log and, if you choose, the attachments.
A manifest with SHA-256
An index page and a manifest list every file in the pack with its size and hash, so the auditor can show that what they tested is what you sent.
Certified statements first
When a certified statement matches the period it goes in, as JSON and PDF or CSV. Otherwise the income statement and balance sheet are generated for the period.
Kept for 30 days
A pack is downloadable for 30 days and then removed. Attachments can be limited to postings at or above a value you set, to keep the file a sensible size.
What AWRA OpsHub does today
- Time-limited auditor users, invited from Accounting with an end date up to 180 days out, extendable and revocable with a reason.
- MFA before anything else, and every sign-in method held to your workspace’s normal sign-in checks.
- Read-only by a guard on every request, on an allow-list of ledger, statement, aging, fixed asset, close and attachment screens.
- A per-auditor log of every request, allowed or refused.
- Automatic expiry, checked every hour.
- Evidence packs for a period of up to 400 days: ledger, statements, reconciliations, agings, fixed assets, journals with approvals, close evidence, audit log and optional attachments, with a SHA-256 manifest.
- Packs granted per auditor, emailed when ready and kept for 30 days.
More we can add to your workspace
- A request list for the audit, where the auditor asks for documents and your team answers each one with an owner and a due date. Commission it
- Comments from the auditor on a posting, answered inside the workspace. Commission it
- Sample selection: a random or value-weighted sample of postings drawn and exported for testing. Commission it
- Read access to the purchase orders, receipts and invoices behind a posting, for auditors who test the trail. Commission it
- Several auditors from one firm under one engagement, with one end date. Commission it
Where we point you to a specialist
- We will not let an auditor change anything. The guard refuses every write, whatever permissions a role is later given.
- We will not leave access open past its end date. It closes on the hour, without anyone remembering to revoke it.
- We will not give an auditor an address that already has an AWRA account. The engagement gets its own login, so it ends cleanly.
- We will not form an audit opinion. The pack and the access are evidence; the opinion is your auditor’s.
An audit request list and sample selection are the two items finance teams ask for first. Tell us how your last audit ran and we will come back with a written spec, a timeline and a price.
The records an auditor reads, and the controls behind them.
Frequently asked questions
What can an external auditor see?
Can an auditor change anything?
How long does access last?
Do we see what the auditor looked at?
Does an auditor use a seat on our plan?
What is in an evidence pack?
Help Center
Need a quick answer while you read?
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.