An invoice error? Catch it before launch.
Find the failed French e-invoicing rule before your integration goes live.
Sample invoice
Invoice
Document type
UBL 2.1
Profile
France
Field under inspection
SIREN
G1.89Invalid identifier format
No customer details appear in this example.
Validation trace
Found at G1.89.
This fixture is expected to fail the French identifier check.
Provider sandbox: Not executed
Synthetic fixture expectation, not a live test.
From error to evidence.
Choose a sample
Spot the problem
Share the evidence
Compare two outcomes.
One French rule, two synthetic test cases.
Pinned fixture expectations, not validation runs executed here.
French rule check
Expected failureView fixture details
- Pinned scenario
- fr.ubl.g1-89-invalid-siren-shape@1
- SHA-256
- d01e4022b4220d4fbe0907df82496af09c9c6a0b4164c977ed8961fdb2519086
Expected result, not a provider observation or certification.
Run a real invoice validation.
Choose an example and run it through the real Java engine. Both invoices are synthetic: no account, file upload or provider call.
4 tests per session in 24 hours. Shared capacity is limited; technical validation, not certification.
SIREN in the sample invoice
Eight digits: rule G1.89 should detect this format error. This does not confirm that the business exists.
<cbc:CompanyID schemeID="0002">12345678</cbc:CompanyID>No validation has run yet.
Choose a sample; its result will come from a real test.
Use this test in your CI
The kit includes a dependency-free Python client, pinned examples and a GitHub Actions workflow. It uses your InvoiceRig API key; no repository access is requested.
Download the CI starterpython3 .invoicerig/run.py run
python3 .invoicerig/run.py pin-baseline
python3 .invoicerig/run.py run
python3 .invoicerig/run.py compareThe existing Rust CLI remains available to authorized installations. This kit does not depend on an inaccessible private Action.