Postings: add transaction posting
postings_add_transactionAdd postings to a transaction using accounts, amounts, VAT codes, and optional cost locations.
Instructions
🟡 WRITE · creates data — Creates new records (receipts, transactions, postings, invoices, master data). Not idempotent — calling twice may create duplicates. add transaction posting Add postings for a specified transaction.
Endpoint: POST /postings/add/transaction
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| vats | Yes | An array of vats. Usage: "vats" : ['vat of posting 1', 'vat of posting 2']. Possible vats: - 0_none ('keine Ust.') - 19_vat ('19% Ust.') - 7_vat ('7% Ust.') - 19_pre ('19% Vst.') - 7_pre ('7% Vst.') - 19_both_1 ('§13b 19% USt./VSt.') - 19_both_2 ('I.g.E. 19% USt./VSt.') - 7_both ('I.g.E. 7% USt./VSt.') - 19_both_1_no_pre ('§13b 19/16% USt.') - 19_both_2_no_pre ('i.g.E. 19/16% USt.') - 7_both_no_pre ('i.g.E. 7/5% USt.') - 19_pre_app ('19/16% Aufz. VSt.') - 7_pre_app ('7/5% Aufz. VSt.') - 19_both_app_1 ('§13b 19/16% USt./Aufz. VSt.') - 19_both_app_2 ('i.g.E. 19/16% USt./Aufz. VSt.') - 7_both_app ('i.g.E. 7/5% USt./Aufz. VSt.') | |
| amounts | Yes | An array of amounts. Usage: "amounts" : ['amount of posting 1', 'amount of posting 2'] Amount must be in format 0000.00 | |
| api_key | No | 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. | |
| postingtexts | Yes | An array of posting texts. Usage: "postingtexts" : ['text of posting 1', 'text of posting 2'] | |
| cost_locations | No | An array of cost_locations. Usage: "cost_locations" : ['cost_location of posting 1', 'cost_location of posting 2']. If specified, the field will be validated. | |
| postingaccounts | Yes | An array of postingaccount numbers. Usage: "postingaccounts" : ['number of posting 1', 'number of posting 2'] | |
| cost_locations_two | No | An array of cost_locations_two. Usage: "cost_locations_two" : ['cost_location_two of posting 1', 'cost_location_two of posting 2']. If specified, the field will be validated. | |
| transaction_id_by_customer | Yes | The id_by_customer of the transaction. | |
| oi_receipts_ids_by_customer | Yes | An array of "open item" receipts ids_by_customer . Usage: "oi_receipts_ids_by_customer" : ['id_by_customer of the receipt for posting 1', null ] The receipts specified will be assigned directly to the respective postings. A null value within the array means explicitly assigning no receipt to the partial posting in that position. IMPORTANT: The field is only required, if OI postings are activated in customers account. |