Document Italy invoice archiving in the SDI sending guide#475
Merged
Conversation
Certified archiving now ships in the default Italy workflow templates, so document it as a short subsection of the sending guide rather than a standalone guide: an Archiving row in the sandbox/live table and a section explaining the legal requirement, the template steps, the receipt attachments, and the async/retry behaviour. Console step names, provider strings, and retention-period claims are left out pending confirmation. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds documentation about Italy e-invoice archiving (“conservazione a norma”) to the SDI sending guide so customers understand the legal requirement, where it’s handled in the default workflow templates, and what artifacts/metadata to expect.
Changes:
- Adds an Archiving row to the Sandbox vs Live comparison table.
- Adds a new “Archiving (conservazione a norma)” subsection describing behavior, receipts, and retry/asynchronous semantics.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| |---|---|---| | ||
| | **Responses** | Simulated by A-Cube (no real SDI sandbox) | Real SDI responses | | ||
| | **Configuration** | Simulated response type must be set | — | | ||
| | **Archiving** | A-Cube test environment (no legal validity) | Certified preservation | |
Comment on lines
+111
to
+112
| Archiving is built into the standard Italy templates, so no extra setup is needed: | ||
|
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Adds a brief "Archiving (conservazione a norma)" section to the SDI sending guide (
guides/it-sdi-sending.mdx), plus an Archiving row in the sandbox/live comparison table.Why
Certified archiving via A-Cube now ships in the default Italy workflow templates, so it doesn't warrant a standalone guide — a short subsection in the sending guide covers what customers need: the legal requirement, that the default registration and send templates already include the archiving steps, the receipt attachments (
archive-receipt.pdf/archive-receipt.xml,archive-uuidmetadata), and the async/retry behaviour.Notes for reviewers
sdi-it.archive.*provider strings are intentionally not mentioned — they haven't been confirmed yet, so the steps are described generically.snippets/workflows/it/sdi-send.mdx,sdi-register-customer.mdx) still show the pre-archiving JSON. Once the provider strings are confirmed, those should be updated to match the shipped templates.🤖 Generated with Claude Code