InkVoice — XRechnung & E-Invoicing

net.inkvoice/inkvoice

XRechnung and ZUGFeRD e-invoicing (EN 16931): create, validate, check Leitweg-IDs, German VAT.

Yes, your AI can use this right now.Answered a live MCP handshake in 889 ms with no sign-in needed and exposes 5 tools.

Connect it

Settings → Connectors → Add custom connector
URL: https://api.inkvoice.net/mcp

5 tools, verified live

Pulled straight from the server with tools/list on 2026-10-18.
create_zugferdread-only

Builds a ZUGFeRD 2.x / Factur-X hybrid invoice from the same details create_xrechnung takes, and returns it as a PDF file. A hybrid is one invoice stated twice in one file: a PDF/A-3 document a person reads, carrying the same invoice inside it as EN 16931 XML a machine books. This is the format private-sector German B2B buyers generally want, where XRechnung is what public bodies require. If the

calculate_vatread-only

Converts between net, tax and gross for a given VAT rate, in either direction. Give an amount and say whether it is net or gross, and you get all three figures back rounded to the cent. Germany's rates are 19 % (standard) and 7 % (reduced), but any rate from 0 to 100 is accepted, so this also works for an Austrian or French invoice. Rounding is half-away-from-zero, the convention invoices and ta

create_xrechnungread-only

Builds a German XRechnung 3.x electronic invoice (EN 16931, CII syntax) from invoice details and returns the XML as text. This is the format German public-sector buyers are legally required to receive, and that many private B2B buyers now ask for. The EN 16931 business rules are checked before anything is built, and a rejected call comes back naming the rules that failed and the business term (BT

check_leitweg_idread-only

Checks a German Leitweg-ID — the routing identifier that goes in BT-10 of an XRechnung to a public authority. An invoice to a German public body with a wrong or missing Leitweg-ID is rejected, so this is worth checking before building a document. It verifies the structure (Grobadressierung of 2 to 12 digits, an optional Feinadressierung of up to 30 alphanumerics, then two check digits) and recomp

validate_einvoiceread-only

Reads an existing electronic invoice and reports what is wrong with it. Accepts XRechnung and ZUGFeRD XML in either EN 16931 syntax — CII (used by XRechnung and ZUGFeRD) and UBL — and reports the syntax and profile it found along with the invoice's key fields, so it also answers "what is this file?". It checks the rules behind most real rejections: BT-10 buyer reference present, and its Leitweg-I

Alternatives in Other

Compare →
Try “Notion”, “Stripe”, “create invoice”, “browser”