# Methodology and editorial policy ERP Localization is written and maintained by a team of **independent ERP localisation editors**. We publish as a team rather than under individual names, so every statement on the site has to stand on a public source that you can open and check, not on anyone's reputation. The editors have professional experience with ERP implementation and multi-country finance systems. Because that experience can come with working relationships with ERP products, nothing is classified from personal experience alone: every support status needs a public source, and the rules below apply to every ERP in the same way. [Source hierarchy](#sources) · [Status definitions](#statuses) · [How a record is verified](#process) · [Review dates](#review-dates) · [Corrections](#corrections) · [Sponsor neutrality](#sponsor-neutrality) · [Licence](#licence) · [What we do not do](#limits) ## Source hierarchy When sources disagree, the higher source wins. A lower source can add detail, but it cannot override a higher one. - **Official tax authority or legislation** – the authority's own pages, the published law or regulation, and official EU Commission pages. This sets what the obligation is: scope, deadlines, formats and filing channel. - **Standard owner** – the body that owns a technical standard or network specification, for format and network rules that the authority refers to. - **ERP vendor documentation** – product help, localisation guides, country-availability lists and release notes from the vendor. This is the only source that can make an ERP function *documented*. - **Partner, provider and marketplace claims** – published by the company selling the product. Shown as a partner or provider claim with its stated limits, never as vendor support. Key facts confirmed only on a reputable secondary source, such as a published country tax guide, are marked **secondary** and stay flagged until an official page confirms them. ## Status definitions VAT-reporting and audit-file support is classified per ERP and per named report, using only evidence linked to that report: | documented | The ERP vendor's own documentation describes the named function for that country and report (for example a return, file or format). It covers what the source describes, not every report in the country. | |---|---| | partner | A partner, provider or marketplace product documents the function for that ERP. Shown as the partner's published claim; it is never upgraded to vendor-documented support. | | community | A community or open-source module documents the function. Treated like a partner route: real, but outside the vendor's own support. | | candidate | A connector or provider route that looks relevant but whose coverage of the named report still needs confirmation. | | historical | Evidence is tied to an older release or a dated announcement; support in the current release has not been established. Never counted as support. | | setup only | The source shows tax configuration, a reporting framework or a preparation aid, but not the named form or file. Never counted as support. | | not established | We researched this ERP for this report and the sources reviewed did not establish support. This is not a finding that the ERP cannot do it. | | not yet researched | No requirement for this country and topic has been researched yet, so the ERP has not been reviewed against a named report. | E-invoicing cells in the [country × ERP matrix](https://erplocalization.com/e-invoicing/#matrix) are **verified** (a source was checked on the date shown), **unverified** (recorded but not yet confirmed on a source) or **not reviewed** (no review recorded yet – not the same as unsupported). Country e-invoicing obligations use these statuses: - **In force** - **Scheduled (enacted)** - **Announced** - **Proposed** - **Voluntary or limited scope** - **Not established** - **Not reviewed** Every source-checked record also states how far its source goes: tax setup, report preparation, file export or transmission. None of these establishes that the authority accepted a submission. ## How a record is verified - Identify the obligation on the official source and record the report, frequency, deadline and filing channel. Fields that the source does not state are shown as *not yet documented*, never guessed. - Look for ERP evidence in the source order above and link each piece of evidence to the specific report it covers, with the edition or version, dependencies and limits it states. - Assign the status from the definitions above. If the evidence is unclear, the lower status applies. - Record the source URL and the date it was checked. Country × ERP summaries are generated from these records; they are not written by hand. ## Review dates Every record shows the date it was last checked against its source, and every page shows when its content last changed. The site currently holds 1600 dated checks, from 2026-10-16 to 2026-10-20. A record is checked again when we learn that the mandate, the vendor's documentation or its release notes have changed (vendor newsrooms are monitored daily), or when someone sends a correction. An old date means the record has not been rechecked since then, not that it has been confirmed again. ## Corrections Use the [correction form](https://erplocalization.com/contact/) (every country, ERP, guide and matrix page links to it with the page prefilled) or email hello@erplocalization.com. Please include a source link. We check each correction against the source hierarchy before publishing. Accepted changes are logged in the [changelog](https://erplocalization.com/changelog/) and the page date is updated. Corrections are never paid for, and a vendor or partner cannot buy a status change. ## Sponsor neutrality The site offers sponsorships, featured placements and commercial data licences. Sponsors never change the verified data, the support classifications or the order of the regular listings. Sponsored and featured content is always labelled, its links are marked as sponsored, and it is not part of the open data or the API. Sponsor claims are shown only if we can confirm them on a public source. Details: [Sponsor](https://erplocalization.com/sponsor/). ## Licence The website is free to read. The datasets (downloads, [API](https://erplocalization.com/api/), Markdown twins and llms files) are licensed [CC BY-NC 4.0](https://creativecommons.org/licenses/by-nc/4.0/) from 16 Oct 2026, with the attribution “ERP Localization (erplocalization.com)”. Commercial use needs a [commercial licence](https://erplocalization.com/data-licence/). Data downloaded before 16 Oct 2026 was released under CC BY 4.0 and remains so. ## What we do not do - We do not test in live ERP tenants. A *documented* status means the vendor documents the function, not that we ran it. - We do not publish prices, ratings or reviews, and we do not rank ERPs. - We do not give tax, legal or implementation advice. Confirm with the tax authority, your ERP vendor and an adviser before go-live. --- Canonical: https://erplocalization.com/methodology/ · Last updated: 2026-10-20 · Informational only; not tax, legal or implementation advice. Featured placements are paid or promotional and do not affect the compliance data. License: data CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/), attribution "ERP Localization (erplocalization.com)"; commercial use needs a paid commercial licence: https://erplocalization.com/data-licence/ (hello@erplocalization.com).