Factur-X: Generate & Validate E-Invoices

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Validate Factur-X, CII & UBL e-invoices free, no key. Generate compliant invoices from JSON.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Factur-X: Generate & Validate E-Invoices": {
      "url": "https://facturx.orvel.dev/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (10)

• view_invoice_demo read-only

  Demonstrate the engine on bundled synthetic samples only; never checks a user's invoice. Use for product evaluation without a key. To check a supplied document, choose validate_invoice. Choose sample=valid to inspect a passing CII invoice or sample=invalid to see the missing-buyer-name finding. Both use the production XSD and EN 16931 engine; results may be cached for 24 hours for the same engine version and input. Inspect validated_at and cached; a cache hit is not a fresh run. Call with {} to validate the passing sample, or sample=downloads for PDF/CII/UBL files and the published report. Accepts no document data, URLs or extra arguments. No PDF or business-register checks in live mode. Shared rate limits return a retryable tool error; unavailable checks never become a passing result. Use explain_finding for a returned rule id. Your own invoices require validate_invoice with a verified-account trial, prepaid or monthly-plan key. Nothing is stored except reports for these public fixtures.

  Parameters:

  • sample — string — valid (default): passing CII invoice; invalid: missing buyer name; downloads: published files.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• generate_invoice read-only

  Create an EN 16931 e-invoice from structured data: Factur-X PDF/A-3, CII XML, or UBL 2.1 XML. Use when you have the parties, lines and dates and need the document. To revise one, correct the input and regenerate; save and deliver the returned file through your own system. Do not use when you already have a visual PDF and CII XML: call embed_xml. To check a document you did not create here, call validate_invoice; to read one, call extract_invoice. Start invoice from get_invoice_example, replacing sample parties and dates. Leave totals and line net_amount omitted to compute them from quantities, prices, allowances and charges. For ubl-xml, profile must be en16931 or extended-ctc-fr; extended and basicwl are CII/PDF-only. profile selects the XML model while check selects validation rules: use check=base for non-French invoices; changing check does not disable party_check. language and footer_text affect only the visual PDF. Omitted party_check enables registry checks only for extended-ctc-fr; true/false explicitly overrides that default. Enabled checks send party identifiers/address and seller IBAN to EU Verify. A not_ready verdict blocks output with field pointers. Successful checks add evidence ids; registry outages do not block generation and are reported as warnings, not proof of readiness. XSD/business-rule failures return a tool error with rule ids; fix the input and retry. Requires an authenticated trial, prepaid or subscription allowance (OAuth or API key). Each successful result uses one document operation, including repeated calls. Returns a JSON text summary (totals, warnings, evidence) and an embedded resource: base64 PDF or XML text. No invoice is stored or sent to a recipient.

  Parameters:

  • invoice (required) — object — Invoice data: seller, buyer, lines, dates, payment terms. Amounts are decimal strings ("1200.00"), dates ISO 8601. Totals and the VAT breakdown are computed. Full JSON Schema in the resource facturx://schema/invoice.
  • check — string — Rule set the output must pass before it is returned: fr-ctc (default) = EN 16931 + French CTC rules (BR-FR-*), base = EN 16931 only (non-French sellers).
  • output — string — facturx-pdf (default): PDF/A-3 with the visual invoice and CII XML inside, the hybrid file French platforms accept. cii-xml: UN/CEFACT CII XML alone. ubl-xml: UBL 2.1 XML alone.
  • profile — string — EN 16931 conformance level written in the XML: en16931 (default, full semantic model), extended (optional business terms), extended-ctc-fr (French B2B mandate; parties are checked before the file is emitted), basicwl (no lines)
  • language — string — Language of the visual PDF: fr (default) or en. Ignored when output is cii-xml or ubl-xml.
  • footer_text — Optional text printed in the PDF footer. Omit it for no footer. Ignored for XML-only output.
  • party_check — Ask EU Verify whether the seller and buyer are invoice-ready before emitting. true checks. false skips. Omit it and extended-ctc-fr checks, other profiles do not. not_ready is a tool error and no file is returned.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world yes

• embed_xml read-only

  Combine a visual PDF you already have with CII XML into one Factur-X PDF/A-3. Use for an existing visual invoice; use generate_invoice to render invoice data or produce UBL. Match the PDF's parties, lines and totals to xml yourself: check examines only XML and cannot detect disagreement with the visible PDF. The embedded profile comes from xml; neither check nor language changes it. language does not translate the PDF. Invalid input or failed rules return a tool error with no file; rule errors include ids. For a findings report use validate_invoice. Success returns a JSON summary (profile, size_bytes, warning count) and a base64 PDF/A-3 resource. Requires a trial, prepaid or subscription allowance via OAuth or key; success consumes one document, errors consume none. Nothing is stored or sent.

  Parameters:

  • pdf_base64 (required) — string — Standard base64 of PDF bytes starting with %PDF-. Not a URL or data-URI.
  • xml (required) — string — Unencoded CII XML text (Factur-X / EN 16931); UBL is not supported.
  • check — string — XML validation rules: fr-ctc adds French BR-FR-* to EN 16931; base uses EN 16931 only.
  • language — string — Language written in the PDF metadata: fr (default) or en.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• validate_invoice read-only

  Check a Factur-X PDF, CII XML or UBL XML against EN 16931, and report the fields to fix. Use when the caller supplies a document, including after corrections; use extract_invoice for business data. With no document and only a request to try the product, choose view_invoice_demo instead. Supply one source: nonblank xml overrides document_base64 without inspecting it. To check a PDF's attachment, omit xml. check adds rules to the detected profile; it cannot change that profile. Use base for non-French invoices to avoid French-field findings. Returns validity and findings with rule ids and field pointers for explain_finding. XSD failures skip schematron; inspect checks_skipped before treating validation as complete. Warnings alone do not invalidate an invoice. Rule failures or a PDF without XML return valid=false; missing input, invalid base64, malformed or unrecognized XML return a tool error. Free without a key (shared daily limit, files up to 5 MB). With an OAuth connection or API key, completed reports consume one operation even when invalid; tool errors do not. No invoice is changed, stored or sent.

  Parameters:

  • xml — CII or UBL XML as unencoded text.
  • check — string — fr-ctc: EN 16931 plus French CTC rules (BR-FR-*). base: EN 16931 only.
  • document_base64 — Standard base64 of a Factur-X PDF, CII XML or UBL XML file; no data-URI prefix.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• extract_invoice read-only

  Extract invoice parties, dates, lines, totals and VAT as JSON for bookkeeping or matching. Use validate_invoice for compliance; this performs no OCR or recalculation. Supply one source: nonblank xml overrides document_base64 without inspecting it, so omit xml to extract a PDF's attachment. include_xml returns that selected source for archiving or validation, not XML reconstructed from fields. Extracted fields need mapping before use as generate_invoice input. Returns fields and format/profile metadata, plus PDF metadata for PDF input. Missing business values remain null; numeric values are strings. Missing input, invalid base64, malformed/unrecognized XML or a PDF without embedded XML returns a tool error, not an empty extraction. Requires a trial, prepaid or subscription allowance via OAuth or API key; success consumes one operation, errors consume none. Nothing is stored or sent.

  Parameters:

  • xml — CII or UBL XML as unencoded text.
  • include_xml — boolean — Include source XML text in the result; this can substantially increase response size.
  • document_base64 — Standard base64 of a Factur-X PDF, CII XML or UBL XML file; no data-URI prefix.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• check_party read-only

  Check exactly one seller or buyer's registry identifiers and readiness through EU Verify. Use to correct one party's identifiers; use check_invoice_parties to check seller and buyer together, or validate_invoice for document rules. Supply siren, siret or vat; siret wins over siren. A SIREN/SIRET, country_code=FR or FR VAT triggers French checks requiring a SIREN/SIRET. Omitted vat can be derived from a successful French lookup; foreign parties normally need explicit VAT. Send address fields with a coherent country_code; requester_vat cannot substitute for the checked party's vat. Sends supplied fields to EU Verify and applicable registers. A Pro/Scale key enables checks; other plans return plan_excluded. No Factur-X document quota is consumed. Returns status, reasons with field pointers and available evidence: invoice_ready is positive, not_ready needs correction, upstream_unavailable is inconclusive and retryable, invalid_input indicates rejected input. Register results and evidence ids may change between calls. No invoice is created or stored.

  Parameters:

  • vat — Party's EU VAT number, for example FR40732829320.
  • city — City, checked with the address.
  • eori — EORI. Checked only when you send it.
  • iban — Party IBAN. Checked only when you send it.
  • role — string — Party role recorded in the evidence; defaults to buyer.
  • siren — 9-digit French SIREN, including leading zeros.
  • siret — 14-digit French SIRET, including leading zeros.
  • address — Street line; any address, postal_code or city activates address checking.
  • postal_code — Postal code, checked with the address.
  • country_code — ISO 3166-1 alpha-2 country code, for example FR or DE.
  • requester_vat — Your VAT number, so the evidence pack can include a VIES request identifier.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world yes

• check_invoice_parties read-only

  Check a supplied seller AND buyer together, returning combined readiness and separate evidence. Use before generate_invoice; use check_party for one party and validate_invoice for document rules. Each party needs siren, siret or vat; siret wins over siren. French identifiers or country_code=FR require SIREN/SIRET; a French lookup can derive omitted vat. Address fields activate address checks. requester_vat applies to both lookups but cannot replace either party's vat. Roles follow seller/buyer argument names; no invoice lines or full invoice body is needed. Makes at most two EU Verify requests with the caller's plan key; Pro/Scale enable register access. Returns status and parties.seller/buyer, each with status, reasons and available evidence. Only two positive results yield invoice_ready; any not_ready yields not_ready, otherwise inconclusive. Inspect both results: denied plans, invalid input, quotas and outages never establish readiness. No document quota is consumed; upstream limits still apply per lookup. Results may change on retry. No invoice is generated, stored or sent.

  Parameters:

  • seller (required) — object — Seller's registry identifiers and optional checks.
  • buyer (required) — object — Buyer's registry identifiers and optional checks.
  • requester_vat — Your VAT number for VIES request evidence.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world yes

• explain_finding read-only

  Turn a validation rule id into the invoice field to change and an example value. Use after validate_invoice or a generate_invoice rule error, not to validate an invoice itself. rule is trimmed and uppercased to select a guide entry. message/json_pointer must come from that same finding: nonempty values override its generic context, but never change the selected fix or example. Omit them to use guide defaults for known rules. Returns rule, known, message, json_pointer, fix and example; known rules also include problem. Selected BR-FR rules and BR-CO-17/BR-CO-26 have guidance. Unknown ids return known=false and example=null with the supplied context, not an error; consult the original finding. No key or document quota is needed; nothing is stored.

  Parameters:

  • rule (required) — string — Validation rule identifier, for example BR-FR-01 or BR-CO-26.
  • message — Original finding's message text.
  • json_pointer — Original finding's json_pointer field path.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_invoice_example read-only

  Return a complete invoice or credit-note example to edit and pass to generate_invoice. Use this first, instead of inventing fields. No API key is required, and the call does not count as a document. The seller and buyer are sample data: replace them, the number, the dates and the lines before you generate. For credit_note, also replace preceding_invoices with the original invoice reference. To credit a real invoice already in hand, use draft_credit_note instead of this synthetic example. Amounts are positive decimal strings. Nothing is stored, and no file is created. Returns the invoice plus the profile and check to pass to generate_invoice.

  Parameters:

  • profile — string — en16931 (default) or extended-ctc-fr. The body is the same. extended-ctc-fr sets party_check so generate_invoice asks EU Verify before emitting a file.
  • document_type — string — invoice (default): type 380; credit_note: type 381 with a sample original-invoice reference.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• draft_credit_note read-only

  Draft a type-381 credit note from an existing invoice, for all lines or selected quantities. Use to reverse an existing invoice's charges; use get_invoice_example for a synthetic credit-note example. invoice must be the original generate_invoice input object, not extract_invoice output. number and issue_date belong to the new credit note; the original number/date are copied into preceding_invoices. Give number a distinct value and use YYYY-MM-DD dates. due_date replaces the original deadline; omitting it removes that deadline rather than inheriting it. Omit credit_lines to retain all original lines and amounts. Otherwise select distinct 1-based array positions, not line ids: [{"line_index":1,"quantity":"2"}] credits two units of the first line. Omitted lines are excluded; quantities cannot exceed the original. Prices and VAT rates are retained. Selected-line mode clears original totals, prepayments, rounding and paid status for recalculation. Document allowances/charges, or reduced quantities on adjusted lines or overridden net amounts, need explicit allocation: these cases return an error; prepare a credit body for generate_invoice. No prior-credit history is stored: the caller must prevent cumulative credits beyond the original. Keep amounts positive: type 381 expresses the credit. Existing credit notes, a reused invoice number or negative line amounts produce a tool error. Default payment remittance references follow the new number; a custom reference is preserved. Returns invoice, type_code, preceding_invoice and next. Pass the returned invoice to generate_invoice with the original profile to create the document. No key or document quota is needed for drafting; nothing is stored, sent or refunded.

  Parameters:

  • invoice (required) — object — The original invoice object you passed to generate_invoice. Not an extract_invoice result.
  • number (required) — string — Credit note number, different from the invoice number. Max 35 characters: letters, digits, and . _ / -.
  • issue_date (required) — string — Credit note issue date, ISO 8601 (YYYY-MM-DD).
  • due_date — Optional due date. Omit it to drop the original invoice due date.
  • credit_lines — Selected original line positions and quantities. Omit for a full credit; an empty list is invalid.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.