/bff/expense/create

Creates a new expense ledger entry. The accountingEntityExternalId is required only when multiple entities exist for the organisation — when omitted, the org default is used.

ExpensepostBffExpenseCreate

Parameters

21 body

21 total

Body · 21

accountingEntityExternalIdstring

Length: 24–24

branchSlugstring | null

supplierContactExternalIdstring | null

External id of the "PŘÍJEMCE" (payee) contact. Optional. When omitted or null, the expense is stored with supplier=NULL — the BFF does NOT invent a fallback (historically it auto-picked the org internal contact for write-offs, dropped 2026-07 so a genuinely unknown recipient stays unknown). Fill it in later via /update.

invoiceExternalIdstring | null

purchaseInvoiceSequenceNumberstring | null

orderHashstring | null

accountCodestring | null

vatRatenumber | null

totalMoneynumber | null

netMoneynumber | null

vatMoneynumber | null

currencystring

Length: 3–3

effectiveDatestringRequired

YYYY-MM-DD

dueDatestring | null

paidDatestring | null

paymentMethodstring | null

descriptionstringRequired

Length: 1–∞

internalNotestring | null

payerContactExternalIdstring | null

External id of the "PLÁTCE" — the contact liable to pay the expense. Optional. When omitted or null, the expense is stored with payer=NULL — the BFF does NOT invent a fallback (operators sometimes don't know the counterparty at creation time; the admin fills the default at the UI layer). Fill it in later via /update.

attachmentBlobTokensstring[]

Request

POST /bff/expense/create

post

curl -X POST "https://api.bizkithub.com/bff/expense/create" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
  "accountingEntityExternalId": "example_accountingEntityExternalId",
  "currency": "example_currency",
  "effectiveDate": "example_effectiveDate",
  "description": "example_description",
  "attachmentBlobTokens": [
    "string"
  ]
}'

Response

JSON payload

{
  "success": true,
  "externalId": "example_externalId",
  "attachmentCount": 0
}

All response codes

1 status code documented

Need an API key?

All BizKitHub API endpoints require authentication via API key.

Get API Key