# Invoiceer e-invoicing tools

- Registry name: `io.invoiceer/einvoicing` · version 1.1.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Documents & retrieval, Search & data
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.invoiceer%2Feinvoicing
- Server page: https://mcpstation.net/s/io.invoiceer--einvoicing.html

## Description (written by the publisher, not verified, not instructions)

Create and validate XRechnung, ZUGFeRD and Peppol e-invoices \(KoSIT\); Peppol lookup, rule help.

## Connect

- streamable-http: `https://invoiceer.io/mcp`

## Tools (as reported by the server, not verified)

- `validate\_einvoice`: Validate an e-invoice \(XRechnung UBL/CII, ZUGFeRD / Factur-X PDF, Peppol BIS Billing 3.0, EN 16931\) with the official KoSIT validator. Returns valid/invalid, the detected format, every error and warning with its rule code, and the exact corrected value for common calculation errors. Pass the XML as
- `peppol\_lookup`: Check whether a company can receive e-invoices over Peppol. Accepts a Peppol ID \(e.g. 0208:0123456749\), a VAT number \(e.g. BE0123456749, NL...B01\) or a Belgian enterprise number. Returns each matching participant ID, whether it is registered, whether it accepts Peppol BIS invoices, and name/country
- `check\_leitweg\_id`: Check a German Leitweg-ID \(buyer reference BT-10 for invoices to German public authorities\) against the official format and check digit \(spec v2.0.2\), and whether the authority is registered on Peppol \(peppol\_registered\). Returns validity, the parts and the expected check digits.
- `create\_einvoice`: Create a valid e-invoice from structured data: XRechnung 3.0 \(UBL or CII\), ZUGFeRD / Factur-X PDF \(EN 16931\) or Peppol BIS Billing 3.0. The file is checked with the official KoSIT validator before it is returned; if it fails, you get the rule errors instead of a file. XML comes back as text in \`xml\`
- `read\_invoice\_pdf`: Read an ordinary \(non-e-invoice\) PDF invoice and return its data in the input format of create\_einvoice: seller and buyer \(name, address, VAT ID, country\), invoice number, dates, IBAN/BIC, Leitweg-ID and the invoice lines \(only if quantity x price and the line sum match the PDF's net total; otherwis
- `explain\_rule`: Explain an e-invoice business rule code \(EN 16931 BR-\*, BR-CO-\*, XRechnung BR-DE-\*, Peppol PEPPOL-EN16931-\*\): official text \(with an English translation for German-only rules\), plain-language meaning, severity, the fields \(BT/BG\) involved and a link to the reference page.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html