ERP Audit Consultant, Norway

What the audit covers, and what stays with your auditor

The word audit carries weight in Norway, so the boundary needs to be clear from the start. Your external auditor examines the annual accounts and issues an opinion. Your accountant prepares filings and advises on bookkeeping. An ERP audit does neither. It examines the business system that produces the numbers: how it is configured, what data it holds, which controls it enforces and how far people rely on workarounds.

In practice that means questions such as these:

• Do sales, purchasing, project and finance processes run in the ERP, or around it?
• Would a SAF-T file produced today hold up to scrutiny without manual repair?
• Do payments, invoices and project costs land where they should without someone moving them?
• Can the reports management uses be rebuilt from system data alone?
• Are permissions in line with the authority the company intended?

Where a finding touches VAT treatment, bookkeeping obligations or the annual accounts, I describe what the system does and hand the question to your accountant or tax advisor. I do not interpret the regulations myself. Several findings will still be of real interest to your auditor, particularly on access and segregation of duties, and the report is written so it can be shared with them. The general method is described on my ERP health check page.

A test SAF-T export as a health indicator

Norwegian bookkeeping rules expect businesses to be able to deliver ledger data in the standard SAF-T structure when the tax authorities request it. Many companies have never actually produced the file from their current ERP, or produced it once at go-live and not since. That makes a test export one of the most revealing checks in a Norwegian audit.

I ask for a test file covering a recent period and review it together with the trial balance. The questions are practical:

1. Is every account in the chart mapped to a standard account, and do the mappings still make sense after accounts were added?
2. Are the company's VAT codes linked to the standard tax codes in a way your accountant agrees with?
3. Do customers and suppliers in the file carry complete master data, including organization numbers?
4. Do dimensions such as department or project appear, and do they match what management reports?
5. Does the file agree with the ledger totals for the same period?

Mapping problems found here usually also explain other symptoms, such as VAT reports that need manual adjustment. I list each gap with the setting that causes it; your accountant confirms the correct mapping, and your partner makes the change. The ERP business analyst page for Norway covers how these requirements are written before a new system is configured.

Can project, vessel and contract margins be trusted?

For Norwegian project, offshore and maritime suppliers, the most important report is usually margin per job, vessel or contract. It is also the report most likely to be quietly wrong. The audit tests it by following costs from their source to the job report.

I take a sample of recently closed and still-open jobs and trace how each cost reached them: purchase orders, subcontractor invoices, rental equipment, stock issues, hours from the time system and travel expenses. The common failure points are predictable:

• Supplier invoices posted without a project dimension and reallocated by journal at month-end.
• Hours approved late, so a job looks profitable until the time arrives.
• Rental or equipment charges booked to an overhead account instead of the contract.
• Change orders invoiced but never linked to the original contract value.
• Currency contracts revalued in the ledger but not reflected in the job report.

For each job in the sample I show the margin the report presents and the margin the evidence supports, without quoting a figure in the findings summary for management. The fixes are usually dimension rules, mandatory fields and approval timing rather than new software. Where reporting needs a wider rework, the project costing and ERP optimization pages explain the approach.

KID payments, EHF invoices and the bank link

Cash handling in a Norwegian ERP depends on a chain of small details working together, and the audit follows that chain with real documents.

On receivables, I check that every customer invoice carries a valid KID reference, that the bank statement or payment file reaches the ERP without manual downloads, and how the matching rules treat part payments, credit notes and payments where the customer typed the wrong number. The size and age of the unmatched list is a direct measure of setup quality, and I trace a sample of entries in it to their cause.

On payables, I follow supplier invoices arriving as EHF through your access point: are they created as drafts automatically, does the order reference link them to a purchase order, and what happens to invoices that arrive in another format? Then I check how payment proposals are approved and sent, and whether changed supplier bank details trigger any review.

Outbound EHF to public buyers gets its own test. I look at whether buyer references and order numbers are captured at the order stage, how rejections come back and who sees them. A rejected invoice that nobody notices is an unpaid invoice, so this is often a quick and valuable fix. If the findings reveal a project that never truly finished, the ERP rescue page for Norway describes the next step.

Access, payroll postings, licenses and the report

The final review area covers who can do what and what flows into the ledger from elsewhere.

User access is compared against the authority your management intended. I look for users who can both create a supplier and change its bank account, approve and pay the same invoice, or post journals in closed periods. Dormant accounts of former staff and external consultants are listed for removal. Payroll and HR data gets particular attention because it is personal data under GDPR; I check that access is limited sensibly and leave legal interpretation to whoever owns data protection.

Payroll in Norway is usually run in a dedicated payroll system or by a provider who also handles employer reporting. I do not review the payroll calculation, but I do check the posting interface into the ERP: whether accounts, departments and projects arrive correctly and whether anyone reposts the file by hand.

Licenses are matched to actual use, with a list of users who could move to a lighter type and add-ons nobody opens.

The report is structured for decision-makers:

More context on Norwegian projects is on the ERP consultant page for Norway and the Norway overview.