- Home
- Skills
- APIs & Backend
- Factur-X & French E-Invoicing, Validated
Factur-X & French E-Invoicing, Validated
Build and validate Factur-X invoices before a platform rejects them: container, profile fields, VAT arithmetic, status lifecycle.
$49
Works with the AI Agents you already use
Factur-X & French E-Invoicing, Validated
Example session with this skill installed
Validate a PDF/A-3 invoice named invoice_789.pdf against the EN16931 profile and check why the 0% VAT rate on the export line might be causing a rejection.
- Read your context and instructions
- Compiled the factur-x & french
I have analyzed invoice_789.pdf using the EN16931 profile. The container is a valid PDF/A-3, and the internal XML is correctly named factur-x.xml. However, I found a critical validation error regarding the VAT logic.
Validation Results
| Check Category | Status | Detail |
|---|---|---|
| Container Type | PASS | Valid PDF/A-3 with proper XML relationship |
| Profile Match | FAIL | Missing mandatory field: Buyer VAT ID for EN16931 |
| Arithmetic | PASS | Sum of lines matches taxable total and grand total |
| VAT Reason | FAIL | 0% Rate detected without VatExemptionReasonCode |
Technical Analysis
The rejection is caused by the 0% VAT rate on Line 2. While the amount is correct, the XML lacks the Condition or Reason code required by the French tax authority for exports. For an export to a non-EU country, you must include the code VATEX-EU-G or the specific text reference to the General Tax Code (CGI). Additionally, because you declared the
EN16931 profile, the buyer's VAT ID is now a mandatory field which is currently missing from your data model.
Next steps
- Add the
VatExemptionReasonCode(e.g., 'Export outside EU') to the XML generation logic for all 0% lines. - Update the data mapping to include the
Buyer VAT IDor downgrade the declared profile to
BASIC if that data is unavailable.
3. Rerun the valider_facturx.py script to confirm the XML and PDF totals are perfectly synchronized.
Connects securely to your tools. The creator never sees your data.
About this skill
Catch the rejection before the platform does.
Make a business ready for French electronic invoicing - choose the Factur-X profile, build a PDF/A-3 that carries a valid XML, get the mandatory fields and the VAT arithmetic right, handle the status lifecycle with a certified platform, and fix the rejections that arrive days later. Use when a company must send or receive structured invoices in France, when a platform rejects an invoice, or when an existing invoicing system must be adapted.
An invoice is rejected for one of three reasons, in this order: the XML is attached but not named as the standard requires, a mandatory field for the declared profile is missing, or the totals do not add up. None of the three is visible to the person who sent it, and the rejection comes back days later from a platform, in a message nobody on the team can read.
Tested scripts: scripts/valider_facturx.py opens the container, extracts the embedded XML, checks the attachment name and the PDF/A-3 marker, verifies every field mandatory for the profile you declare, and recomputes the arithmetic - taxable total plus VAT against the grand total, line totals against the taxable total, amount due against the grand total, and a 0 % VAT rate with no exemption reason, which is the single most common rejection. Verified on a conforming invoice and on five deliberately broken ones: wrong totals, 0 % with no reason, a missing mandatory field, an undeclared profile, malformed XML. The same file passes as MINIMUM and fails as EN16931, which is exactly the behaviour you want when deciding what to declare.
Includes an EXPERT.md reference (exact parameters, thresholds, failure diagnosis): the standards and which one binds you, the field matrix across the four profiles, the arithmetic a platform recomputes and why you round per VAT rate rather than once at the end, the exemption reasons, the status lifecycle with the transition that costs a quarter of cash flow when it is confused, receiving as the half that is usually forgotten, archiving the transmitted bytes rather than a regeneration, a migration order that avoids a cliff, and a rejection table mapping each message to its cause.
Acceptable use: producing, validating, transmitting and archiving invoices for a business you operate or are mandated to assist. The skill refuses issuing an invoice for a transaction that did not take place, altering a transmitted invoice instead of issuing a credit note, backdating, producing two versions of the same invoice with different figures, and any arrangement whose purpose is to misstate VAT.
Not legal advice. The French calendar, the platform regime and the mandatory mentions have been amended more than once: verify the current texts and the applicable dates with your accountant or your certified platform before relying on any schedule. The script needs no network and writes nothing.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for APIs & Backend.
Does not provide legal advice. Requires valid Python 3. Verification of current French tax dates and VAT rates must be performed by the user.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 27 days ago
- Software
Python