XML Auditfile Financieel (XAF) Validated before delivery With RGS codes

Custom Auditfile Financieel integration development

When the Dutch Tax Administration, your accountant or a trustee in bankruptcy asks for your financial records, they usually want the Auditfile Financieel: an XML file containing general ledger accounts, journal entries, debtors and creditors, in the format of the XAF standard. Many accounting packages produce such a file, but not every system does so correctly or completely. Appfront builds the integration that creates, validates or imports an Auditfile Financieel from your own accounting system.

What is an Auditfile Financieel integration?

An Auditfile Financieel integration ensures that your financial records can be supplied and imported in the form of the XML Auditfile Financieel, or XAF for short. According to the Dutch Tax Administration, an auditfile is a computer file filled with the data from your records that is needed for an audit, and many accounting packages support it. The Auditfile Financieel contains data from the financial records, such as general ledger accounts, general ledger transactions and debtor and creditor data. Besides Financieel, there are auditfiles for payroll, point-of-sale systems and trip registration, among others. The Dutch Tax Administration describes XAF as an open standard for exchanging data from administrative systems for reporting and audit purposes, with the Tax Administration, trustees in bankruptcy and accountants among its users.

The auditfiles are developed under the direction of the Auditfile Platform, in which software developers work together through NL ICT, NBA, NOB, ECP, SRA and the Dutch Tax Administration; SRA and the Tax Administration lead it. Version 4.0 is a further development of XAF 3.2 from 2014. The number of data fields went from 250 to 90, optional fields must be filled in if the data is available in the software, and the Reference General Ledger Scheme (RGS) is defined more clearly. The current documentation on the Tax Administration's website for software developers is XAF 4.0.3. Developers test their files with the Validation Test Service. XAF is not on the lists of the Forum Standaardisatie (the Dutch standardisation forum).

We build custom because not every set of records comes from a single package. A company with its own ERP, multiple sets of records or a legacy system being phased out often has no button that produces a complete and correct auditfile. The integration retrieves general ledger accounts, journals, entries, relations and outstanding items, adds RGS codes where they are missing, and converts everything to the structure of XAF. Before the file goes out, it checks it against the schema and against the content, such as balanced entries and known accounts. In the other direction, it imports auditfiles from others, for example for a migration or an analysis.

Full

General ledger, entries, relations.

With RGS

Codes per account.

Checked

Before delivery.

How we build your Auditfile Financieel integration

We start with your records: which systems they are in, for which years an auditfile is needed, who is asking for it and which version that recipient expects. Next, we establish where general ledger accounts, journals, entries and relations are located in your systems and how they map to the fields of XAF. We first build an auditfile for one set of records and one financial year, validate it against the schema and have your controller or accountant review the result. Other sets of records, other years and the import of auditfiles follow if that goes well. After that, we keep the integration up to date when the standard gets a new version.

1
Mapping your administrations

Systems, years, recipient.

2
Mapping fields

Your data to XAF.

3
First auditfile

Validated and reviewed.

4
Go-live and maintenance

Go-live, monitoring, and maintenance when new versions arrive.

What an Auditfile Financieel integration actually does

The components below appear in almost every integration for the Auditfile Financieel. Which ones you need depends on the number of sets of records and on what you do with the auditfile.

Compile

Auditfile from your records.

RGS codes

Per general ledger account.

Schema validation

Following the XAF structure.

Contents

Balanced entries and balances.

Import

Other parties' audit files.

Log

Every file traceable.

Who we build an Audit File Financial integration for

The integration is intended for organisations that need an audit file their software does not provide, or does not provide in full, and for parties that process audit files from others. The more administrations and years involved, the more it delivers.

Companies with their own ERP

Audit file without standard software.

Accountancy firms

Client audit files imported.

Insolvency trustees

Quick insight into the books.

Software builders

XAF in your software.

Technology and integrations

This page is about the XML Audit File Financial: creating, checking and importing the file. If you mainly want to align your chart of accounts with the Reference Chart of Accounts (RGS), see our RGS integration. For returns and reports via Standard Business Reporting there is the SBR integration, and for financial statements in XBRL the XBRL integration. If you use Twinfield, also take a look at the Twinfield integration. You can read about our approach on custom software development.

XAF 4.0 XAF 3.2 XML and XSD Reference Chart of Accounts (RGS) Validation Test Service ERP and accounting software General ledger and journals Debtors and creditors Roles and permissions Log

Why Appfront for your Audit File Financial integration?

An audit file that stops halfway through the year, accounts without descriptions, or a file that fails the recipient's checks costs you time at the moment you have the least of it: during an audit or a takeover. That is what we build around: an audit file that comes straight from your administration, checks before the file leaves the building, and a log where you can see what was delivered.

Full

All data from the source.

Checked

Schema and content checked up front.

Traceable

Every file logged.

Security and privacy in an Audit File Financial integration

An audit file contains your entire financial administration, including the names and addresses of customers and suppliers. For sole traders and private individuals these are personal data, and the GDPR applies. The integration only creates an audit file for the administrations and periods you approve, records who created the file and who it was delivered to, and keeps imported audit files from others separate from your own data.

The integration runs in a European data centre, with encrypted connections and storage. Audit files are stored encrypted and only shared via a secure route of your choosing. We agree with you in advance who may create an audit file, who may download it and who may view imported files.

Frequently asked questions about an Audit File Financial integration

Questions that controllers, accountants and software vendors ask before they get started.

An XML file containing the data from your financial administration that is needed for an audit, such as general ledger accounts, ledger entries and debtor and creditor data. The format is called XML Audit File Financial, XAF for short. Many accounting packages can create it.

The Dutch Tax and Customs Administration describes XAF as an open standard for exchanging data from administrative systems for reporting and audit purposes. The standard is developed under the direction of the Auditfile Platform. XAF is not on the Forum Standaardisatie's comply-or-explain list or its list of recommended standards.

Version 4.0 is a further development of 3.2 from 2014. The number of data fields has been reduced from 250 to 90, optional fields must be filled in when the data is available, and the Reference Chart of Accounts is defined more clearly. The current Tax Administration documentation is XAF 4.0.3.

The Reference General Ledger Scheme (RGS) is an open standard that assigns a fixed code to each general ledger account. The audit file can carry the RGS code for every account. According to the Dutch Tax Administration, this lets it prepare an audit better and ask more targeted questions.

Software developers can test their files with the Dutch Tax Administration's Validation Test Service. The integration also runs its own checks before delivery: does the file match the schema, do the journal entries balance, and do all entries belong to known accounts and relations.

Yes. An audit file from another package or another organisation can be read in for a migration, an analysis or the merging of administrations. The integration translates the data into your own structure and records which file was used.

For organisations with their own or heavily customised ERP, with multiple administrations or with a legacy system that is being phased out, and for software vendors who want to support XAF. If your accounting package already produces a complete audit file, an integration is often not needed.

An audit file that is correct, straight from your own administration?

Tell us which systems hold your administrations and who is asking for the audit file. We will show you how an integration creates, checks and delivers it.

Edit content