New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

convert_invoice

Convert an e-invoice between formats via the shared EN 16931 canonical model: parse the source document, re-serialize as the target, and validate the result before returning it — never a document that has not been checked. Format ids: "UBL_2.1" (OASIS UBL, the universal Peppol/EN16931 baseline), ...

SERVERInvoicehub SOURCEhttps://api.invoicehub.dev/mcp
Medium RISK CLASS
Category Write
Parameters 33 required
Recommended Rate-limitedsee the rule below
Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/dev-invoicehub-invoicehub/convert-invoice.md

What convert_invoice does on Invoicehub

AI agents use convert_invoice to create or update resources in Invoicehub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Invoicehub environment.

ParameterTypeRequiredDescription
to string Yes Target format id, e.g. "UN_CEFACT_CII", "XRechnung_UBL", "XRechnung_CII", or "Factur-X".
from string Yes Source format id, e.g. "UBL_2.1".
document string Yes The source document: raw text for XML formats, base64 for binary formats (Factur-X).

Parameters from the server's own tool schema.

Why convert_invoice is rated Medium

An AI agent can call convert_invoice faster than any human can review: one bad instruction and it creates or modifies resources in Invoicehub by the hundred, each call as confident as the last.

Questions about convert_invoice

What does the convert_invoice tool do? +

Convert an e-invoice between formats via the shared EN 16931 canonical model: parse the source document, re-serialize as the target, and validate the result before returning it — never a document that has not been checked. Format ids: "UBL_2.1" (OASIS UBL, the universal Peppol/EN16931 baseline), "UN_CEFACT_CII" (UN/CEFACT Cross Industry Invoice, required syntax for Chorus Pro/France and many ERP back-ends), "XRechnung_UBL" / "XRechnung_CII" (Germany's mandatory B2G format, XRechnung 3.0 — required for invoicing German public-sector buyers), "Factur-X" (France/Germany hybrid PDF+XML — a human-readable PDF/A-3 with the structured invoice embedded, common for French B2B). Binary formats (Factur-X) are base64 in both directions. Requires an API key on the Pro plan or above for any target beyond plain UBL_2.1 — call list_supported_formats to see current availability. It is categorised as a Write tool in the Invoicehub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does convert_invoice accept? +

convert_invoice accepts 3 parameters: to, from, document. Required: to, from, document. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on convert_invoice? +

Register the Invoicehub MCP server in PolicyLayer and add a rule for convert_invoice: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Invoicehub. Nothing to install.

What risk level is convert_invoice? +

convert_invoice is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit convert_invoice? +

Yes. Add a rate_limit block to the convert_invoice rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block convert_invoice completely? +

Set action: deny in the PolicyLayer policy for convert_invoice. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides convert_invoice? +

convert_invoice is provided by the Invoicehub MCP server (https://api.invoicehub.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Invoicehub, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Invoicehub's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.