Buchhaltungsbutler MCP

Invoices: create invoice

invoices_create

Create a final outgoing invoice for a customer and book it immediately. Provide recipient, line items, prices, and VAT to generate a numbered invoice.

Instructions

🟡 WRITE · creates data: Creates new records (receipts, transactions, postings, invoices, master data). Not idempotent: calling twice may create duplicates.

create invoice

Add an invoice for the specified customer.

Use to issue a final outgoing invoice that is booked immediately.

For an invoice that should stay editable, use invoices_create_draft. For a structured XML invoice in XRechnung or ZUGFeRD format, use invoices_create_e_invoice.

Not idempotent: a second call issues a second invoice with a new number. v1 offers no endpoint to list, change or cancel an invoice once created.

Endpoint: POST /invoices/create

Input Schema

TableJSON Schema

Name	Required	Description
`zip`	No	The zip of the recipient company. If specified, the field will be validated.
`city`	No	The city of the recipient company. If specified, the field will be validated.
`date`	Yes	The date of the invoice.
`type`	Yes	Can be either 'invoice' ("Rechnung"), 'credit' ("Gutschrift") or 'offer' ("Angebot").
`email`	No	The email for sending the invoice. If specified, the field will be validated.
`street`	No	The street of the recipient company. If specified, the field will be validated.
`country`	No	The country of the recipient company. If specified, the field will be validated. Valid cases are only the German version of the country name [Dänemark] OR the two digit ISO code of the country [DK].
`due_days`	No	The number of days between the invoice date and the due date. If specified, the field will be validated.
`item_vat`	Yes	An array of invoice item vats. Usage: "item_vat" : ['7', '19'] Valid vat rates are floating point numbers between 0 and 100.
`language`	No	The language for translatable invoice labels (e.g. headings, table headers, payment terms). Can be either 'de_DE' ("Deutsch", default) or 'en_US' ("English"). If omitted, German is used.
`item_name`	Yes	An array of invoice items. Usage: "item_name" : ['Item 1', 'Item 2']
`item_unit`	Yes	An array of invoice items units. Usage: "item_unit" : ['Std.', 'Stk.']
`item_amount`	Yes	An array of invoice item amounts. Usage: "item_amount" : ['10', '20']
`company_name`	Yes	The company name of the recipient.
`discount_type`	No	The type of the discount. Can be either 'percent' or 'EUR'. If specified, the field will be validated.
`invoicenumber`	No	The invoicenumber for the invoice. If not specified, the default BHB number will be created. If specified, the field will be validated.
`show_bankdata`	No	Show the the bank data on the invoice. If specified, the field will be validated.
`correspondence`	No	The optional correspondence to the invoice recipient. If specified, the field will be validated.
`date_of_supply`	No	Date or period of service/delivery. NOTE: The date_of_supply will be displayed on the PDF, but when the date AND the date_of_supply is specified in the format "YYYY-MM-DD", the date_of_supply will also be taken over as date_delivery of the receipt in the 'Belege' or 'Belege/Buchen' view. IMPORTANT: Due to the DATEV compatibility, we cannot accept a date_of_supply that is after the invoice date. In that case it will be ignored!
`discount_value`	No	The value of granted discount. If specified, the field will be validated.
`customer_number`	No	The customer number of the recipient. If specified, the field will be validated.
`final_provisions`	No	The final comment of the invoice. If specified, the field will be validated.
`item_description`	No	An array of invoice item description. Usage: "item_description" : ['Description Item 1', 'Description Item 2']. If specified, the field will be validated.
`show_contactdata`	No	Show the contact data on the invoice. If specified, the field will be validated.
`show_prices_type`	Yes	Can be either 'net' ("Netto") or 'gross' ("Brutto").
`item_single_price`	Yes	An array of invoice item single_prices. Usage: "item_single_price" : ['20', '19.99']
`payment_reference`	No	The payment reference id. If specified correctly, the resulting receipt of the created invoice will match with the corresponding transaction. NOTE: Currently we support Amazon order id, PayPal transaction id and Stripe transaction id!
`payment_conditions`	No	The payment conditions of the invoice. If specified, the field will be validated.
`recurring_interval`	No	An interval for recurring invoices. Can be either 'weekly', 'monthly', 'quarterly' or 'yearly'. If specified, the field will be validated.
`contact_person_name`	No	The name of the contact person of the recipient company. If specified, the field will be validated.
`recurring_date_next`	No	The next date of a recurring invoice. IMPORTANT: The field is required, if "recurring_interval" is specified. If specified, the field will be validated.
`additional_addressline`	No	The additional address information of the recipient company. If specified, the field will be validated.

Output Schema

TableJSON Schema

Name	Required	Description
`message`	No	blank
`success`	Yes	Success boolean
`file_name`	No	Filename of the created invoice
`invoicenumber`	No	blank
`id_by_customer`	No	blank

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.2Sep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "file_name": {
+      "description": "Filename of the created invoice",
+      "type": "string"
+    },
+    "id_by_customer": {
+      "description": "blank",
+      "type": "string"
+    },
+    "invoicenumber": {
+      "description": "blank",
+      "type": "string"
+    },
+    "message": {
+      "description": "blank",
+      "type": "string"
+    },
+    "success": {
+      "description": "Success boolean",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv1.1.0Sep 9, 2026

removedInput schema / properties / api_key

Removed value: -{
-  "description": "Optional. The BB customer api_key to act on. Defaults to the BB_API_KEY configured on the server — only set this to target a different customer.",
-  "type": "string"
-}

Changed1 schema field changedv1.0.2Sep 5, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "The language for translatable invoice labels (e.g. headings, table headers, payment terms). Can be either 'de_DE' (\"Deutsch\", default) or 'en_US' (\"English\").\n\nIf omitted, German is used.",
+  "type": "string"
+}

First observedv1.0.0Jul 29, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description adds concrete behavioral context: creates data, not idempotent (a second call issues a second invoice with a new number), and v1 offers no endpoint to list/change/cancel. This goes beyond the annotation flags and gives practical operational details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficient: it opens with a generic write warning, then a bold 'create invoice' heading, and a concise paragraph covering purpose, alternatives, and caveats. It's slightly longer than necessary but each sentence adds value—no fluff. The key differentiators are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with 32 parameters (9 required) and a rich output schema, the description covers purpose, usage guidance, behavioral caveats, and alternatives. The schema handles parameter details, so nothing critical is missing. The agent can decide when to invoke and what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already explains every parameter. The description does not add parameter-specific semantics beyond what the schema provides, though it does mention the 'type' (invoice/credit/offer) implicitly through 'final outgoing invoice'. Baseline 3 is appropriate since the schema carries the parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates invoices for a specified customer, and explicitly distinguishes it from siblings (invoices_create_draft, invoices_create_e_invoice) by noting when to use each. The verb 'create' and resource 'invoice' are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says when to use this tool (final outgoing invoice that is booked immediately) and when not to (for editable drafts or structured XML e-invoices), naming the alternative tools. It also warns about non-idempotency and lack of list/change/cancel endpoints, which informs usage decisions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server