Buchhaltungsbutler MCP

Receipts: get receipt by id_by_customer

receipts_get_by_id

Read-onlyIdempotent

Fetches a single receipt for a customer account using its id_by_customer, which you first obtain from the receipts list method. Use it to retrieve one known receipt, not to search or page through receipts.

Instructions

🟢 READ-ONLY: Fetches data. Makes no changes to the accounting records.

get receipt by id_by_customer

Get a single receipt for a specified customer account by id_by_customer. You can get the "id_by_customer" by using the "/receipts/get method" first. The response includes an array of receipt data.

Use to fetch a single receipt whose id you already have.

To search or page through receipts, use receipts_list.

id_by_customer is the per-customer counter shown in the BuchhaltungsButler UI, not a global database id.

Endpoint: POST /receipts/get/id_by_customer

Input Schema

Name	Required	Description	Default
`get_file`	No	If true, the file will be included as a base64 encoded string (e_invoice_type = 0 -> standard pdf file, e_invoice_type = 1 -> ZUGFeRD pdf file, e_invoice_type = 2 -> xRechnung xml file). If specified, the field will be validated.
`id_by_customer`	Yes	Required per-customer record ID obtained from the corresponding list tool.

Output Schema

Name	Required	Description
`data`	No	An array of receipt data
`message`	No	blank
`success`	Yes	Success boolean

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv1.1.5Nov 1, 2026
- changedOutput schema / properties / data / properties / counterparty / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / currency / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / deleted / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / e_invoice_type / type
```
Previous value: -[
-  "string",
-  "integer"
-]New value: +[
+  "string",
+  "integer",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / file_content / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / file_type / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / filename / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / id_by_customer / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / list_direction / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / type / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
Changed15 schema fields changedv1.1.3Sep 26, 2026
- addedInput schema / properties / id_by_customer
```
Added value: +{
+  "description": "Required per-customer record ID obtained from the corresponding list tool.",
+  "minimum": 1,
+  "type": "integer"
+}
```
- addedInput schema / required
```
Added value: +[
+  "id_by_customer"
+]
```
- changedOutput schema / properties / data / properties / account / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / amount / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / amount_original / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / currency_original / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / date_delivery / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / date_payment_due / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / e_invoice_type / type
```
Previous value: -"string"New value: +[
+  "string",
+  "integer"
+]
```
- changedOutput schema / properties / data / properties / exchangerate / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / invoicenumber / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / link_to_receipt_id_by_customer / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / payment_date / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / payment_reference / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / data / properties / vat / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
Addedv1.1.2Sep 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the "READ-ONLY" header is partly redundant. However, the description adds non-annotation context that matters: `id_by_customer` is a per-customer counter visible in the UI rather than a global DB id, and it discloses the surprising POST endpoint for a read operation.

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?

Front-loads the read-only guarantee and purpose, then usage, then a caveat, then the endpoint — good ordering. The bolded header restating the tool name is mild waste, and the "response includes an array" line sits awkwardly after "get a single receipt".

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

Completeness4/5

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

An output schema exists and both parameters are documented, so the description need only cover routing and id semantics, which it does. The one blemish is the minor tension between "Get a single receipt" and "response includes an array of receipt data," which could leave an agent unsure of the return shape.

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 coverage is 100%, so the baseline is 3; `get_file` is fully documented in the schema and needn't be repeated. The description does add meaning for `id_by_customer` (per-customer counter, not global id), but it points to a "/receipts/get method" while the schema points to a "list tool", leaving the acquisition path slightly ambiguous.

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?

States a specific verb+resource+scope: fetch a single receipt for a customer account by id_by_customer. It also explicitly distinguishes itself from the sibling `receipts_list` used for searching/paging, so the agent can route without opening a schema.

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?

Gives an explicit when-to-use ("Use to fetch a single receipt whose id you already have"), an explicit alternative for the other case ("To search or page through receipts, use `receipts_list`"), and where the required id comes from.

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

Deploy Server