Home › Guides

How to map invoices, tax returns, audit files and statutory accounts

Start with a list of outputs the business must produce. Give each output its own record, source, owner and acceptance test. This avoids a common purchasing error: accepting invoice transmission as evidence that every accounting and tax obligation is covered.

Use this guide when opening a country, replacing an ERP or checking the scope of a localization partner. The register is a recommended control. The authority sources determine which records apply to your business.

One operation can require several outputsConceptual obligation categories. Each applicable output has its own source, owner and acceptance test. One operation can require several outputs 01 Invoice exchange Customer or supplier 02 Tax reporting Authority data 03 Periodic returns Tax-period population 04 Audit exports Specific scope and trigger 05 Annual accounts Accounting and filing Conceptual obligation categories. Each applicable output has its own source, owner and acceptance test.

Diagram: One financial operation can feed several independently required outputs. Conceptual obligation categories. Each applicable output has its own source, owner and acceptance test.

Describe the transaction population

Record the legal entity, tax registrations, establishments, customers, suppliers and source systems. Identify where stock is held, who imports it and whether sales are domestic, cross-border, consumer or government transactions.

Have the tax owner classify the population. Keep the decision and supporting source with the record. Registration thresholds and exemptions can depend on establishment, activity or a specific turnover measurement. A country-wide yes-or-no field cannot express all those conditions.

Separate the required outputs

Create distinct records for invoice creation, exchange with the customer, authority validation, transaction reporting, periodic tax returns, audit exports, payroll reports and annual accounts.

For every record, identify its trigger. An invoice may be processed per transaction, a return per tax period and an audit export when requested. Annual accounts follow a separate accounting process and filing calendar.

EU guidance states that limited-liability companies must prepare annual accounts and file them with the relevant national register. It also distinguishes listed-company consolidated IFRS accounts from other accounting regimes. The applicable local rules and size conditions still matter. Your Europe, accounting for small and micro businesses

Use country examples without flattening their differences

France's FEC is an accounting file for a tax-audit context. DGFiP provides standard-file information and schemas. Record it separately from France's invoice exchange and e-reporting flows. DGFiP, standard accounting files

Portugal's authority describes SAF-T PT as a standardized XML export covering defined accounting and invoicing information. It also documents communication of invoice elements through a file based on SAF-T. The shared file family does not make those two purposes interchangeable. AT, SAF-T PT overview, AT, communication of invoice elements

Romania publishes D406 materials, including validation tools and guidance for different information sections. Identify the relevant section and reporting trigger before buying an export. ANAF, SAF-T project and technical materials

These examples establish why the register needs country, purpose and trigger. They do not supply a universal SAF-T filing frequency.

Complete an obligation record

Use this form for each output. Supply actual evidence before marking the record ready.

Keep a due-date rule rather than a copied calendar date where the rule repeats. Identify the authority calendar used for holidays or special extensions. Have the local owner approve the calculation.

Map sources to outputs

Identify every application that creates transactions in the required population. Include point-of-sale, procurement, billing, expenses, payroll and external accountants where applicable.

For each flow, define the authoritative transaction record, mapping and output owner. If a provider or accountant transforms the data, record the inputs supplied and evidence returned. Include approved manual adjustments in the reconciliation.

Separate data preparation from direct filing. An ERP can prepare a return that an accountant files elsewhere. Record that as a two-step process rather than claiming automated submission.

Reconcile the population, then the amounts

First establish which documents belong in the output. Explain exclusions, cancelled items and period differences. Then compare amounts using the relevant tax or accounting basis.

For a hypothetical period with 1,000 source invoices, the provider may show 980 accepted, 15 rejected and five pending. That accounts for the document population. It does not establish that all amounts or tax classifications are correct. Review the accepted population and resolve the 20 exceptions before accepting the relevant reporting outcome.

Maintain separate adjustments for tax-only entries, journal postings or documents outside the exchange channel. Do not force an invoice total to equal a tax-return box that measures something else.

Assign responsibility and acceptance

Finance decides applicability and reviews the accounting result. IT owns configuration and interfaces. Operations monitors the process. The filing owner submits and retains acknowledgement. Identify the person who can act when those responsibilities cross suppliers.

Accept each output independently. Retain a sample file or submission, validation evidence, reconciliation and the version used. A successful invoice test should not automatically close the return or audit-export requirement.

Keep the register current

Review a record when the business adds an entity, hires in another country, moves inventory, changes source systems or enters a new sales channel. Review it again when legislation, a schema or a supplier release changes.

Use the change-management guide for that operating routine. Use the country pages to identify local research starting points. Local applicability, filing deadlines and specialized industry obligations still need their own decisions.

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: · Markdown version

Newsletter – monthly digest of mandate and ERP support changes. Subscribe on the home page.