Launched this week
Factur-X by Orvel
Generate and validate e-invoices via REST, MCP and n8n
2 followers
Generate and validate e-invoices via REST, MCP and n8n
2 followers
Turn invoice data into Factur-X PDFs, CII or UBL. Get validation findings with rule IDs and check coverage through REST, MCP or a ready-to-import n8n workflow. Explore fixed samples without an account, or try your own documents with 10 operations over 14 days for eligible verified accounts. No card; limited launch availability. Connect your own invoice-delivery provider.
Factur-X by Orvel is for developers adding e-invoicing to an ERP, SaaS or automation workflow. The aim is to make both the file and the validation result useful: rule references, affected fields, correction guidance, and a record of which checks ran.
You can generate Factur-X PDFs, CII or UBL through REST or MCP. The free n8n example uses built-in nodes and checks the report before releasing the PDF: https://github.com/LeBorgneAntoine/facturx-mcp/tree/main/examples/n8n
Start with the fixed synthetic demo without an account. For your own documents, eligible verified accounts can try 10 operations over 14 days, with up to 30 processing attempts, no card and no renewal. Launch trial availability is limited. Current paid allowances, prices and terms: https://facturx.orvel.dev/docs/p....
Factur-X produces and checks files; it does not deliver invoices to recipients or replace a Plateforme Agreee or Peppol access point. Reports include check coverage and limitations.
Which integration is the hardest part of your workflow: mapping invoice data, understanding validation errors, or connecting to your delivery provider? Feedback on a concrete integration would be especially useful.