AWRA OpsHub Search
Intermediate Certificate on pass

External Audit: Evidence Packs and Auditor Access

Hand your external auditor a period’s books as one checksummed ZIP, and give them a time-limited, read-only sign-in that is fenced on the server, needs two-factor authentication and logs every request.

3 lessons 35 min 6-question assessment 70% to pass

What you’ll learn

  • Request an evidence pack for a fiscal year or custom dates and explain what each section holds
  • Choose an attachment threshold and know how long a pack can be downloaded
  • Invite an external auditor with an end date and share the packs they need
  • Explain what an auditor can open, what is refused, and how to extend or end access

Course content

3 lessons · 35 min of reading
01
Lesson 1 of 3 Practice 12 min

Building an evidence pack for a period

Audit evidence packs are under Accounting, on the Accounting overview or by typing Audit Evidence Packs in the command palette, for anyone holding the export audit evidence permission. Choose a Fiscal year or Custom dates (From and To, up to about thirteen months), add a Label such as FY2025 statutory audit, and click Build pack. The pack is built in the background, one at a time per workspace, and the list shows its status from Queued through Building to Ready. When it is ready you get a bell notification and, unless the workspace has switched that email off, an email with a download link. A ready pack can be downloaded for 30 days; after that it expires and you build it again.

Each pack is one ZIP with an index page and a manifest listing every file with its size and SHA-256 checksum, so an auditor can prove nothing was altered after it left you. Inside are numbered sections: the trial balance; every general ledger line in the period; the certified statements for that period, or the income statement and balance sheet computed from the ledger when none matches, labelled as not signed off; bank reconciliations; receivables and payables open at period end; the fixed asset register with depreciation; journals with their approval trail; the month-end close records, reopen requests and integrity checks; the accounting audit log; and attachments. A people file maps the user ids in the other files to names.

In practice: a Nairobi NGO’s auditor asks for the year to 30 June. The finance manager builds the pack for that fiscal year. Journal and bill attachments can make a pack very large, so under Only at or above she enters 50,000.00: only journals and bills of KES 50,000 or more bring their files, and the rest are still listed in the ledger sections. Leaving the field empty includes the attachments of every journal and bill in the period. The pack is ready twenty minutes later and she shares it with the auditor’s account rather than emailing a ZIP around.

Key takeaways

  • Build pack runs in the background for a fiscal year or custom dates; you are told in the bell, and by email if it is on, when it is ready.
  • Every file is listed with its SHA-256 checksum in the manifest.
  • Sections cover trial balance, GL detail, statements, bank reconciliations, agings, fixed assets, journals, close records, audit log and attachments.
  • Only at or above limits which journals and bills bring their files; a ready pack downloads for 30 days.
02
Lesson 2 of 3 Practice 11 min

Inviting an external auditor

Auditor access, next to the evidence packs and reached the same way, is for people holding the manage auditor access permission. Click Invite an auditor and fill in Name, Email, Firm, Access ends and an optional Note, tick any Evidence packs to share, then Send invitation. Access ends at the end of the chosen day and can be at most 180 days away. Use an address only for this engagement: an address that already has an AWRA OpsHub account cannot be invited. While active, the auditor uses one seat.

The auditor gets the same set-password email every new user gets, then must turn on two-factor authentication before anything else opens. They land on their own home page listing Reports you can open and Evidence packs shared with you, each pack with its size and SHA-256. They can read the general ledger, trial balance, income statement, balance sheet, cash flow, receivables and payables, the fixed asset register, aging, the accounting periods and close screens, certified statements, attachments on postings and the drill-down from a statement line to its postings. That is the whole list.

In practice: the finance director of a Kigali hotel invites Jane Wanjiru of Kamau & Partners LLP with access ending in six weeks and shares the FY2025 pack. Jane sets her password, turns on two-factor authentication and downloads the pack from her home page. Halfway through fieldwork she wants the supporting files of a March journal that was below the pack’s threshold; she opens them from the posting drill-down instead, because attachments on postings are on her list. The director later builds a second pack for the first quarter of the new year and uses Share selected on Jane’s record to add it.

Key takeaways

  • Invite an auditor with a name, an email used only for this engagement, a firm and an end date at most 180 days away.
  • The auditor sets a password and must turn on two-factor authentication before anything opens.
  • They read accounting reports, ledgers, certified statements, attachments on postings and the packs you share.
  • An active auditor uses one seat; more packs are added later with Share selected.
03
Lesson 3 of 3 Reading 12 min

The read-only fence, the activity log and ending access

An auditor account is fenced on the server, not just by its role. Every change is refused, whatever permission the External Auditor role might later be given, and any screen outside the list brings them back to their home page. Every request they make, allowed or refused, is written to the Activity log on their record, with the time, the screen and the result. Refused means they tried to change something or open a screen outside auditor access. Their home page tells them this in plain words: nothing can be changed from an auditor account, and every page they open is recorded for the organization that invited them.

On the auditor’s record you can Change end date to extend fieldwork, still within 180 days of today, Withdraw a shared pack, or End access now with a short reason. Access also ends on its own: AWRA checks every hour, and at the end date the access is revoked, the auditor is signed out of every browser and device, and the seat is freed. A pack shared with an auditor that later expires after its 30 days shows as No longer available on their home page until you build and share a fresh one.

In practice: fieldwork at a Mombasa logistics firm overruns by a week, so the controller uses Change end date. Reviewing the Activity log afterwards, she sees two Refused entries where the auditor tried to open the supplier bills list, which is outside auditor access; she covers what the auditor was looking for in the next pack, whose payables and attachments sections carry the bills, instead of widening the access. On the day the audit opinion is signed she clicks End access now with the reason Fieldwork finished, and the auditor’s access is revoked.

Key takeaways

  • Every write is refused on the server, and screens outside the list send the auditor back to their home page.
  • The Activity log records every request, including refused ones.
  • Change end date extends within 180 days; End access now takes a reason; Withdraw removes a shared pack.
  • At the end date an hourly check revokes access, signs the auditor out everywhere and frees the seat.

Finished the material?

Take the 6-question assessment and earn your certificate — 70% to pass.

Take the assessment

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.

Search all approved AWRA public help articles.

Open Help Center