Naarvin keeps the audit trail, the reconciliations and the evidence as the year runs, so the audit is a review rather than a scramble. Auditor requests are tracked with an owner and a date, balances are grouped into lead schedules, unusual journals are found and sampled before the auditors do it, and auditors get time-limited, read-only access where every view is logged.
Why is audit season so disruptive?
The audit asks for a year of evidence in a few weeks. The request list arrives as a spreadsheet, the team stops the close to answer it, documents are emailed in pieces, and the same question comes back because nobody can find what was sent last time.
- Requests are tracked in a spreadsheet passed between the firm and the team.
- Reconciliations exist, but not with a preparer, a reviewer and a date.
- Manual journals near year end are found by the auditors first.
- Evidence is scattered across inboxes and shared drives.
- Auditors need access, and giving it safely is awkward.
How does audit preparation run with Naarvin?
- Keep the trail all yearEvery action is recorded in a log that cannot be edited: who did what, and when.
- Reconcile with sign-offBalance sheet accounts are reconciled with supporting balances, prepared by one person and signed off by another.
- Track the requestsEach auditor request has an owner, a due date and its evidence attached, so nothing is answered twice.
- Build the lead schedulesBalances are grouped the way auditors test them, with last year alongside.
- Test journals firstUnusual entries, such as weekend postings, round amounts or late manual journals, are found and sampled before fieldwork starts.
- Give auditors a roomAuditors get time-limited, read-only access to the evidence and requests. Every view is logged.
What does Naarvin prepare, and what stays with people?
| Area | Naarvin | Your team and auditors |
|---|---|---|
| Requests | One list with owners, dates and evidence | Your team answers; auditors review |
| Reconciliations | Supporting balances and differences | Prepared and signed off by two different people |
| Lead schedules | Balances grouped by audit area, year on year | Auditors test them |
| Journal testing | Unusual entries found and sampled | Your team explains them |
| Access | Read-only access that ends on a date | You decide who gets it and for how long |
Which controls do auditors look at first?
Usually approvals and access. In Naarvin, payments and journals go to the right approver by amount and nobody approves their own request. Conflicting permissions are flagged as segregation-of-duties findings, and access is reviewed regularly. Our guide to the approval matrix and segregation of duties explains what a good set-up looks like.
What do you need to start?
- Your accounting system connected, ideally from the start of the financial year.
- Last year's audit request list, to start this year's from it.
- Owners for each balance sheet reconciliation.
- The audit firm's contacts, for read-only access when fieldwork begins.
Who is this for?
Companies with an external audit every year, groups audited company by company, and finance teams that want the audit to stop interrupting the close. Naarvin supports the audit; the audit itself stays with your auditors.
Questions people ask
Does Naarvin replace our auditors?
No. Naarvin prepares evidence, schedules and tests so your team is ready. The audit opinion stays with your audit firm.
Can auditors log in?
Yes, with time-limited, read-only access that you grant. Access ends on the date you set, and every view is logged.
Can the audit trail be edited?
No. Actions are recorded in a log that cannot be edited, showing who did what and when.
What does journal testing look for?
Entries auditors usually question, such as postings at unusual times, round or repeated amounts, and late manual journals, with a sample ready for review.