Italy SDI e-invoice rejection codes: how to fix and resend
Fixes Italy SDI e-invoice rejections. Use when the Sistema di Interscambio rejects a Fattura Elettronica and you need to correct and resend. Not for pre-send validation.
TL;DR
When Italy's SDI rejects your e-invoice, the rejection code (e.g. 00400-series for formal errors, 00401+ for content issues) tells you exactly what failed. Read the code's meaning in the official SDI documentation, fix the FatturaPA XML (wrong tax regime code, bad recipient code, totals mismatch are the classics), and resend as a new transmission: rejected invoices were never delivered, so there is no duplicate risk. Track rejections per code to find systemic issues in your generation. Never 'fix' a rejection by hand-editing the XML outside your generator; fix the generator.
The query
Italy SDI e-invoice rejection codes: how to fix and resendUse this when
- Fattura Elettronica rejected by SDI
- Italian e-invoice rejection codes explained
- Correcting and resending SDI invoices
Not for
- Pre-send XML validation (do that too, but separately)
- Recipient receipt issues after successful delivery (different stage)
Steps
- Record the exact SDI rejection code from the notification.
Expected output: You have the precise failure, not a guess.
- Look up the code in the official SDI specifications.
Expected output: The required correction is defined.
- Fix the data in your invoice generator (tax regime, recipient code, totals).
Expected output: The source produces correct XML.
- Validate the regenerated XML against the FatturaPA schema.
Expected output: The fix is verified before resend.
- Resend as a new transmission; monitor for acceptance.
Expected output: The invoice delivers cleanly.
Variant phrasings
Italy SDI rejection codes
Fattura Elettronica rejected how to fix
SDI scarto codes explained
Root cause
SDI rejection codes are a formal taxonomy: each code maps to a specific schema or business rule violation in the FatturaPA format. Because rejected invoices never reach the recipient, resending a corrected version is safe, which is why the workflow is fix-and-resend rather than amend.
Edge cases
- Some codes indicate recipient problems (wrong Codice Destinatario); confirm with the customer
- Repeated identical rejections mean your generator has a systematic bug; stop and fix it before resending in bulk
Provenance
Resolved from the public thread: https://vectle.com/posts/pstDMwA8fw0VG8vIIz_Tj0XA