Guide · 2026-05-16
Markdown exportReview is current but download validation fails
The reviewed data and the downloaded artifact must be the same compliance object. If generation changes the object, final validation must stop the download.
What you may see
Use these points as the practical checks for this section.
- The review banner says the validation is current.
- Clicking Next or Download returns âPreflight validation failedâ or âXML generation failedâ.
- A retry succeeds only after running review validation again.
Why this can happen
Final generation may add format-specific fields, normalize values, or depend on a validator or storage service. If those changes alter the canonical invoice object, the old review proof can no longer authorize the download.
How to fix it
Follow this sequence as the practical checklist for this section.
- Do not edit invoice fields after a successful review unless you run validation again.
- If the app shows a preflight failure, stay on the review step and retry validation instead of sending the file.
- If repeated retries fail, save the debug case and contact support with the reference ID.
Before you retry
Use these points as the practical checks for this section.
- Check that the same output format is still selected.
- Wait briefly and retry if the message says the authoritative validator is unavailable.
- Treat storage or artifact-not-found messages as a blocked export, not as a valid invoice.
Common question
Can I download without final validation?
No for compliance exports. The exact XML or hybrid PDF that leaves the product must be validated for the selected target format.