PracticeIntegrations

The file that missed year end: how to use SAF-T in the audit

The SAF-T file can give the auditor the entire general ledger, but only if it is complete. A story about a file fetched too early, and five minutes of checks that would have saved the team a week in busy season.

It is mid-January, and the client is quick. Before you have time to chase it, the SAF-T file is in your inbox: a retailer with three shops, tidy books and a bookkeeper who answers the same day. Your team member reads the file in, runs the analytics and starts documenting. By early February the planning is done and journal entry testing is well under way.

In mid-March the engagement partner sits with the financial statements and the trial balance next to the working papers. She stops at depreciation. It is in the accounts, but none of the tests has seen it. The same goes for the bonus accrual and a large inventory write-down.

"Why can't I find the year-end entries in the analytics?"

The answer takes half an hour to find and a second to understand. The file was exported on 14 January. The year-end entries were posted in February. What the team had tested was a set of accounts that no longer existed.

The rest of the week goes on fetching a new file, reading it in, rerunning the analytics and rewriting the documentation. In March. Nobody did anything foolish. The file was simply never checked against the accounts you were actually auditing.

What the SAF-T file really is

SAF-T Financial is a standard format for exporting accounting data. In Norway it has been required for accounting periods from 1 January 2020, and version 1.30 has been mandatory from 1 January 2025. Businesses with turnover below NOK 5 million are exempt unless their accounts are kept electronically. The file is sent to the Norwegian Tax Administration only on request, typically during a tax audit.

For the auditor, the format matters more than the requirement. The structure is the same whether the client uses Tripletex, Fiken, PowerOffice, Visma or another system. A check you build once can be used on every client.

A SAF-T file has, broadly, three parts:

  • A header that says which company, which period and which system the file comes from.
  • Master data with the chart of accounts, opening and closing balance per account, customers, suppliers and VAT codes.
  • The entries, with date, voucher number, description, account, amount and who recorded them, as far as the system exports it.

The last part is what makes the file valuable. You do not get a sample or a trial balance. You get everything. And that is exactly why it is so dangerous when "everything" is missing a month.

Why it goes wrong

The retailer's story is not unusual, and it is rarely about carelessness. It happens because a SAF-T file looks finished. It has a header, a period and thousands of entries. It balances. Nothing in the file itself says that something is missing.

Three things come up again and again when a file is not what the auditor thinks:

  • It was fetched too early, before the year-end entries were posted.
  • It covers the wrong period, for example year to date instead of the full financial year.
  • It comes from the wrong company, because the client runs several companies in the same system.

What all three have in common is that the file is internally consistent. The control totals can agree, debits can equal credits, and the format can validate. The error only shows when the file is held up against something outside it: the trial balance and the financial statements you are auditing.

Five minutes when the file arrives

The checks that would have caught the error in January take a few minutes. Do them the day the file arrives, before anyone builds on it:

  • Look at the first and last entry dates. Are they within the financial year, and is year end included?
  • Reconcile the closing balance per account to the trial balance and the financial statements. A difference means the file and the accounts are not the same.
  • Check that the opening balance plus the movements gives the closing balance for every account.
  • Check that every voucher balances, and that total debits equal total credits.
  • Confirm that the file is from the right company and conforms to the schema of the version it declares.

Document that the reconciliation was done, and against which version of the trial balance. If the client posts new entries afterwards, you know the file must be fetched again. Everything you later conclude from the file rests on this reconciliation.

Ask for the right file from the start

Much of the problem can be solved when you request the file. All the common accounting systems can export SAF-T, usually from a report or export menu. Menus change between versions, so ask the client to follow the system vendor's own help page rather than last year's screenshot. What decides the quality is timing and scope:

  • Ask for the full financial year, not the period up to today.
  • Ask for the file after the year-end entries are posted, and agree that you will be told if anything is posted afterwards.
  • Give the organisation number of the company you are auditing, so it does not get mixed up.

If you need an early file for planning, that is fine. Mark it as preliminary, and decide there and then when the final file will be fetched.

What the file lets you do

Once the file is complete and reconciled, it opens up audit procedures that are cumbersome without it. You can test the whole population instead of a sample:

  • Journal entry testing under ISA 240, with entries at period end, on rarely used accounts, or by users who do not normally post.
  • Cut-off around the balance sheet date, where entries may belong in the wrong year.
  • Analytical procedures with monthly movements, compared with last year and with your expectations.
  • Consistency between VAT codes and accounts.

Findings are not conclusions. They are questions you need to ask, and the answers need to be documented. But the questions get better when they are based on every entry.

The pitfalls you cannot see

Even a complete file has a few traps:

  • Older exports may use an earlier version of the format. Your tool must read the version the file is actually in.
  • Accounts are mapped to a standard grouping. Wrong mapping gives a wrong picture in the analytics, even when the numbers add up.
  • Not every system fills in every field, such as who recorded a voucher. Check what is there before you build a test on it.
  • The file can contain names of customers, suppliers and employees. Treat it as client data, with access control and deletion routines.

How we do it in Revios

In Revios the SAF-T file is read straight onto the engagement. The control totals in the file are reconciled on import and the result is shown on the import, so a difference is visible before anyone builds on the file. The file itself is retained unchanged with the engagement, so it is always possible to see exactly which file the analytics were based on. The entries are then used by the analytics on the same engagement, and the suggestions the auditor accepts or rejects are recorded in the signed audit log.

Reconciling to the trial balance is still the auditor's job. But when the file, the import and the assessments live in the same place, it is easy to see what was checked, and when.

Back to January

Picture the same client, but with five minutes on the day the file arrived. Your team member sees that the last entry date is 14 January, and that the closing balance on depreciation does not agree with the trial balance the client sent along. She notes that the file is preliminary and asks for a new one once year end is posted.

In March the engagement partner reads the same working papers. The year-end entries are in the analytics, and the file records when it was fetched and which trial balance it was reconciled to. Her question is never asked.

It is not a big change. It is a habit. But it is the difference between a week in busy season and five minutes in January.

Want to see what a SAF-T import looks like in Revios? We are happy to walk you through an engagement from import to review using sample data. You do not need to send us any client information.

About Revios

Revios is cloud-based audit software for audit firms in the Nordics, delivered by Halifax AS. The whole engagement comes together in one workflow that follows ISA, with AI suggestions the auditor approves, SAF-T import and a signed audit log.

Media contact

post@revios.no

Share this article

See one engagement from import to review

See how figures become workpapers, how the team records its assessments, and what the engagement partner reviews. We use sample data. You do not need to send client information.