Correcting a Wrong E-Invoice Across 8 EU Countries: Procedures & E-Reporting Consequences

Italy — SdI / FatturaPA

Correction procedure depends on SdI status:

• Not yet sent to SdI → simply correct and send; no change of invoice number needed. [dgtax.it]
• Rejected by SdI (“scartata”) → within 5 days of the rejection notification, resubmit a corrected invoice with the same number and issue date (using the “re-issue” function). The invoice is treated as never issued until accepted. [dgtax.it], [eu-einvoicing.com]
• Accepted/delivered but wrong content → the invoice cannot be modified. You must issue a nota di credito (TD04) — or TD08 if the original was a simplified TD07 — through SdI, referencing the original in the XML fields, and then issue a new correct invoice. A TD05 debit note is used when the taxable base/VAT must go up. [eu-einvoicing.com], [invoicedat…action.com], [dgtax.it]
• Reverse-charge self-invoices (TD16–TD19) → do not use TD04. First send a cancellation with negative amounts, then resend the correct document using the same document type with positive amounts (confirmed by Agenzia delle Entrate at Telefisco 2026). [invoicedat…action.com], [vatupdate.com]

E-reporting consequences: Both the incorrect invoice and its credit/debit note remain in the SdI archive; the reversal flows automatically into the VAT registers, LIPE and pre-filled VAT returns. Article 26 DPR 633/1972 imposes a 1-year limit for certain error/discount corrections (no limit for cancellations or insolvency). Failure to correct on time creates anomalies in the pre-filled return and exposes the taxpayer to penalties. [invoicedat…action.com], [vatupdate.com]

Romania — RO e-Factura

Correction procedure:

• If ANAF rejects the invoice, resubmit within the transmission window (from 1 Jan 2026: 5 working days from issue date, extended by GEO 89/2025). [amavat.eu], [invoicedat…action.com]
• If the invoice is validated (signed XML issued), it cannot be modified. You must issue either:
  • a credit note (factura storno) — same reference as the original, negative amounts, then a new correct invoice, or
  • a correction invoice (factura de corectie) — issued upon request of the recipient, referencing the original invoice number. [dolibarr.org], [fonoa.com]
• All correction documents must go through RO e-Factura using the RO_CIUS (UBL 2.1, EN 16931). [marosavat.com], [e-invoice.app]

E-reporting consequences: Because Romania runs a clearance model, the recipient can only deduct VAT based on the ANAF-signed XML. An uncorrected error therefore blocks or misstates VAT deduction. Additionally, Romania has a parallel SAF-T obligation (D406) — mismatches between e-Factura and SAF-T are a red flag for ANAF audit. Late transmission or failure to correct triggers fines (RON 1,000–10,000 depending on taxpayer size) and denial of input VAT. [marosavat.com], [e-invoice.app]

Belgium — Peppol (mandatory since 1 Jan 2026)

Correction procedure:

• An invoice sent via Peppol is a final document; neither the network nor the Access Points allow modification or deletion. [peppoledge.com]
• Belgium has no dedicated Peppol correction document today. Standard workflow: issue a credit note through Peppol to cancel the original, then issue a new correct invoice through Peppol. Both documents travel through the same network. [peppoledge.com], [dexxter.be]
• If the recipient contests the invoice, a written protest (email is sufficient) must be sent quickly (1–2 weeks is considered reasonable); silence = tacit acceptance. [dexxter.be]
• Special case: if you sent the invoice to the wrong recipient, the FPS Finance FAQ (“einvoice.belgium.be”) gives specific instructions (credit note + resend correctly). [einvoice.belgium.be]

E-reporting consequences: Belgium’s near-real-time e-reporting layer (planned as a follow-on to the 1 Jan 2026 Peppol mandate) will rely on the same Peppol flow — so credit notes and corrected invoices will re-report automatically. No dual reporting in the near term (subject to the ongoing IHTF/VBO-FEB advocacy for supplier-only reporting). Non-compliance penalties for the e-invoicing mandate range from €1,500 (first offence) up to €5,000 for repeat offences, per Article 70 §4 Belgian VAT Code. [peppolcheck.be], [ey.com]

Croatia — Fiskalizacija 2.0 (from 1 Jan 2026)

Correction procedure:

• Corrections must be issued as structured e-invoices in UBL 2.1 (HR-FISK 2.0 CIUS) referencing the original invoice’s number and date. [vatupdate.com], [ecosio.com]
• The recipient can reject an incorrect invoice through the system; rejections are e-reported to the Tax Administration monthly. [ecosio.com], [theinvoicinghub.com]

E-reporting consequences (this is where Croatia gets tricky — three parallel flows):

1. E-invoice exchange between parties (Peppol / access points).
2. Real-time fiscalisation to the Porezna uprava by both issuer and recipient (cross-validation).
3. Monthly e-reporting of rejected invoices (by recipients) and payments (by issuers). [ecosio.com], [theinvoicinghub.com]

An uncorrected error therefore creates mismatches on all three layers, causing invoice disputes, delayed payments, financial penalties and additional audit/reconciliation work. Note the abolition of the old I-RA/U-RA sales/purchase control lists from 1 Jan 2026 — the e-invoice data now feeds compliance directly. [ecosio.com] [marosavat.com]

Greece — myDATA (+ B2B e-invoicing from March/October 2026)

Correction procedure:

• Every invoice transmitted to myDATA receives a MARK (Unique Registration Number) and a QR code. [edicomgroup.com]
• If the invoice is wrong, the issuer transmits a cancellation summary followed by a corrected summary document (or a credit/debit summary). Both issuer and recipient may be required to transmit if the counterparty does not. [snitechnology.net]
• Under the new B2B mandate (Phase A from 2 March 2026 for >€1m turnover; Phase B all businesses from 1 October 2026), corrections must also flow through the accredited e-invoicing provider channel. [e-invoice.app]

E-reporting consequences: Since 1 January 2024, revenues in the VAT return cannot be lower and expenses cannot be higher than what has been transmitted to myDATA. Discrepancies (e.g. issuer failed to transmit) can be reported by the recipient, but only before the VAT return deadline. Failure to correct promptly = mismatch between books and VAT return → penalties and blocked deduction. [ey.com] [ey.com]

Poland — KSeF (mandatory from Feb/April 2026)

Correction procedure:

• KSeF has no edit/delete button — every invoice is immutable and receives a unique KSeF reference number. [ksefuj.to], [complium.com]
• Fix by issuing a Faktura Korygująca (KOR) via the FA(3) schema, which must contain the original KSeF number (<NumerKSeF>), the original invoice number, and a correction reason. [eu-einvoicing.com], [developer….texinc.com]
• You can correct: net/VAT/gross amounts, quantity, unit price, VAT rate, description, supply date, buyer name/address. [ksefuj.to]
• Exception — wrong buyer NIP: a standard correction is not sufficient. Issue a zero-value correction cancelling the entire invoice, then issue a brand-new invoice with the correct NIP. Legal basis: Art. 106j of the Polish VAT Act. [ksefuj.to]
• Nota Korygująca (buyer’s correction note) is abolished under KSeF — the buyer must request a Faktura Korygująca from the seller. [roedl.pl]

E-reporting consequences: KSeF is a clearance system — the correction only has legal effect once accepted by KSeF and given its own KSeF ID. Both original and correction remain in the archive and feed the VAT return / JPK_V7. Failure to issue a correction results in the wrong VAT being reported and can trigger sanctions under the VAT Act. From 1 Feb 2026 (large taxpayers) and 1 April 2026 (all others), non-compliance also triggers KSeF-specific penalties up to 100% of the VAT amount on non-KSeF invoices. [getsix.eu], [complium.com]

France — Facturation Électronique (from 1 Sept 2026)

Correction procedure:

• Corrections are handled via credit notes (avoir) or rectificative invoices (facture rectificative) transmitted through your Plateforme Agréée (PA). Both must reference the original invoice number and generate new lifecycle events. [fonoa.com]
• Accepted formats: UBL, CII, or Factur-X. [fonoa.com]

E-reporting / lifecycle-status consequences (this is the specifically French part):

• Every invoice follows a normalised lifecycle with 4 mandatory statuses: 200 Déposée, 210 Refusée, 213 Rejetée, 212 Encaissée, plus 10 optional statuses. [frenchinvoice.fr]
• Statuses are transmitted to the PPF (Portail Public de Facturation) in CDAR format within 24 hours. [frenchinvoice.fr]
• If an invoice is rejected (213) by the PA or refused (210) by the buyer, the supplier must perform an accounting cancellation (avoir + new invoice). [frenchinvoice.fr]
• Parallel e-reporting obligation covers B2C, cross-border B2B and payment data — corrections must be reflected in the transaction data flow to allow correct pre-filling of VAT returns. [francenum.gouv.fr], [impots.gouv.fr]

Timing: Receipt obligatory for all companies from 1 Sept 2026; issuance obligation for large and mid-sized companies (ETI) from 1 Sept 2026, SMEs/micro from 1 Sept 2027. [cleartax.com], [impots.gouv.fr]

Germany — E-Rechnung (XRechnung / ZUGFeRD / Peppol BIS)

Correction procedure:

• Germany has adopted a decentralised model (no clearance) — an incorrect structured e-invoice (XRechnung, ZUGFeRD 2.x, or Peppol BIS 3.0) is corrected the traditional way: issue a corrected invoice (berichtigte Rechnung) under§ 14 / § 31 UStDV or a credit note (Gutschrift/Storno) referencing the original invoice number. [eu-einvoicing.com], [e-invoice.app]
• The corrected document must again be in a compliant EN 16931 format and archived under GoBD rules (2nd amendment July 2025). [e-invoice.app]
• Small invoices ≤ €250 (§ 33 UStDV) can stay outside structured e-invoicing — but not for intra-Community supplies (§ 6a UStG), reverse charge (§ 13b UStG) or distance sales (§ 3c UStG). [e-invoice.app]

E-reporting consequences (current state):

• Germany currently has no live CTC / e-reporting system. Corrections therefore only affect the VAT return (UStVA) and ZM (recapitulative statement) as under the standard VAT rules.
• However, a domestic e-reporting obligation is expected as a second phase aligned with ViDA (2030 cross-border, 2035 domestic alignment). [e-invoice.app], [peppolvalidator.com]
• Mandate timeline reminder: receipt mandatory since 1 Jan 2025; issuance for turnover > €800k from 1 Jan 2027; all businesses from 1 Jan 2028. [peppolvalidator.com]

Summary Matrix

Key governance takeaway for your team

The five clearance countries (IT, RO, HR, GR, PL) create an audit-trail obligation because the correction document is itself a legally issued e-invoice with its own reference. In BE, FR, DE, the correction relies on traditional VAT rules but must still comply with the structured-format mandate. This impacts your AR/AP controls, ERP correction workflows, and hypercare monitoring — especially where reconciliation between sales ledger and the clearance/reporting platform is required (Romania SAF-T, Greek myDATA cap, Croatian tripartite flow).