DAC7 · REPAIR AT THE RIGHT LAYER

DAC7 duplicate DocRefId: keep document references unique

Find duplicate document references in a DAC7 XML export and repair the source generator without breaking correction links. The validator reports DAC7-DOC-ID with the XML path and line. This guide concerns reference consistency, not fiscal qualification or filing acceptance.

Open the fictional error →

What triggers this result

A platform operator and seller share the same DocRefId, or two sellers receive the same reference. A file can be well formed and still collide at the document-reference layer. In DE a DIP envelope can carry multiple DPI payloads: references must remain unique across the whole chosen file.

MessageRefId identifies a message; DocRefId identifies a document block. Poland DPI-IS uses its own header and numeric document references; do not fabricate a MessageRefId requirement for that national form. Poland DPI-FR is a registration form, while FR in the country selector means France.

Failing example and repair

Before

<DocRefId>2025000001</DocRefId>
<DocRefId>2025000001</DocRefId>

After: this reference issue is resolved

<DocRefId>2025000001</DocRefId>
<DocRefId>2025000002</DocRefId>

Assign distinct references in the export generator, then regenerate the file. Do not blindly replace repeated text: an existing CorrDocRefId may intentionally refer to a prior document. Persist the actual emitted references in your own reporting system.

Download fictional failing XML · Passing fictional PL example · Known outcomes and locations

Repair and retest

  1. Select the receiving national package and reporting year first. OECD DPI is not a universal national upload format.
  2. Use the path and line to fix the generator. Keep message identifiers separate from document identifiers.
  3. For external corrections, supply an accurate local history JSON only when needed. Missing history means the relationship remains unverified; the tool never queries tax-authority history.
  4. Run again and read XML, selected XSD, independent business, plausibility and unchecked layers separately. A successful schema check concerns only that exact package.

Primary sources and scope

MF Poland DPI publications establish the distinct national DPI-IS(1) and DPI-FR(1) structures. BZSt amtlicher Datensatz 1.2 supplies the German DPI 1.0 / DIP 2.0 package; its ZIP was opened again. DGFiP revenus-2025 collection ZIP is a different collection variant. These source artifacts were rechecked on 6 November 2026.

All explanations and checks here are independently written. Polish national XSD and its MF import are supplied with conditional-reuse attribution; DE/France require authorised local BYO. RO/HR remain generic BYO. There is no identity, actual tax-residence, exemption, authority-history or acceptance verification. OECD terms do not grant blanket rights to national modifications, third-party types or software; no protected guide translation is supplied.

Check the regenerated file

DAC7 platform reporting validator · Related DAC7 reference guide · API / CLI scope