BuchhaltungsButler

🟢 READ-ONLY: Fetches data. Makes no changes to the accounting records. **get sums report postingaccount ledger** Returns the postingaccount ledger ("Kontenblatt") of one postingaccount, holding its postings of the requested period. The postingaccount numbers available for a sums report are provided by reports/get/sums, both as the keys of the 'sums' object and as its entries' 'postingaccount_number'. In contrast to the report itself the ledger is created on the fly, so no report has to be created beforehand. Note that retrieving the ledger of a postingaccount holding a lot of postings may take a while. Use to read one posting account's ledger for a bounded date range. For the totals across all posting accounts, use `reports_get_sums`. The API returns the ledger on demand; no previously generated sums report or report ID is required. Endpoint: POST /reports/get/sums/ledger

🟡 WRITE · links/unlinks records: Creates or removes an assignment between records (e.g. receipt ↔ transaction). Reversible. **assign receipt to transaction** Assign a receipt to a transaction. Use to match receipts to the bank transactions that paid them, one pair or many at once. To attach a receipt to a posting rather than a bank transaction, use `postings_assign_receipt_to_free`. Takes one or many: pass an array of transactions to receipts in `transactions_to_receipts`. A single record is an array of one. Reversible with `transactions_unassign_receipt`. Creating the link does not book anything: use `postings_create_for_transaction` to post the transaction. Endpoint: POST /transactions/assign-batch/receipt

🟡 WRITE · creates data: Creates new records (receipts, transactions, postings, invoices, master data). Not idempotent: calling twice may create duplicates. **add transaction** Add a transaction to a payment account of the specified customer. Use to import bank transactions that no bank connection delivers automatically, for example from a CSV export or a cash book. Takes one or many: pass an array of transactions in `transactions`. A single record is an array of one. Not idempotent and there is no duplicate detection: re-importing the same statement books every line a second time. Check `transactions_list` for the date range first. v1 offers no endpoint to update or delete an imported transaction. Endpoint: POST /transactions/addBatch

🟢 READ-ONLY: Fetches data. Makes no changes to the accounting records. **get transaction by id_by_customer** Get a single transaction for a specified customer account by id_by_customer. You can get the "id_by_customer" by using the "/transactions/get method" first. The response includes an array of transaction data. Use to fetch a single bank transaction whose id you already have. To search or page through transactions, use `transactions_list`. `id_by_customer` is the per-customer counter shown in the BuchhaltungsButler UI, not a global database id. Endpoint: POST /transactions/get/id_by_customer

🟢 READ-ONLY: Fetches data. Makes no changes to the accounting records. **get transactions** Get transactions for a specified customer account. The response includes the number of returned rows and an array of transaction datas. Use to search bank transactions by account and date range. To fetch one known transaction, use `transactions_get_by_id`. For multi-page exports, prefer `id_by_customer_from` with `limit` and fixed account/date filters: it is exclusive and forces ID-ascending order. Start at 0, then use the greatest returned ID without incrementing it; omit `offset`. Validate IDs and forward progress and continue until empty. Offset pages have overlapped in observed filtered exports; deduplication and an empty final page do not prove completeness. Reconcile IDs/counts and signed amounts independently. `rows` counts the returned page, not the grand total; concurrent changes still need a separate check. Endpoint: POST /transactions/get

🟢 READ-ONLY: Fetches data. Makes no changes to the accounting records. **get all receipts assigned to a specific transaction** Get all receipts assigned to a specific transaction for a specified customer account by id_by_customer. You can get the "id_by_customer" by using the "/transactions/get method" first. Use to see which receipts are linked to a given bank transaction, for example to check whether a payment has its invoice attached. For the opposite direction, use `receipts_list_assigned_transactions`. Endpoint: POST /transactions/assigned-receipts/get

🟡 WRITE · links/unlinks records: Creates or removes an assignment between records (e.g. receipt ↔ transaction). Reversible. **unassign a specific receipt from a transaction** Unassign a specific receipt from a transaction. Use to undo a receipt-to-transaction match that was made in error. Removes only the link. Neither the receipt nor the transaction is deleted. Endpoint: POST /transactions/unassign/receipt