Split one transaction across multiple bills

POST/api/v1/bills/payments/batch

Apply a single bank transaction to multiple bills and/or direct expense lines in one atomic request. Validates the total allocation against the transaction's remaining unallocated balance before creating any payments.

Operation ID: create_bill_payments_batch·View as markdown·OpenAPI slice

Authentication

Bearer token authentication. Pass your DayZero API token in the Authorization header and the target business UUID in x-business-id.

Request body

Schema: BillBatchPaymentRequest

transaction_idstringrequired

UUID of the bank transaction representing the payment.

allocationsarray · BillBatchPaymentAllocationBillBatchPaymentAllocation

Bill slices (0+). Each bill_id must be unique.

2 fields

bill_idstringrequired: UUID of the bill receiving this slice of the transaction.
amountintegerrequired: Amount in cents to allocate to this bill. Must be > 0.

expense_linesarray · BillBatchExpenseLineBillBatchExpenseLine

Optional expense lines for any remaining balance. Each line debits an expense ledger on the transaction's journal entry.

3 fields

ledger_idstringrequired: UUID of the expense ledger account to debit.
amountintegerrequired: Amount in cents to categorize as expense. Must be > 0.
descriptionstring: Optional memo stored on the journal-entry line.

paid_onstring · date-time

Override payment date applied to every allocation. Defaults to the transaction datetime if omitted.

override_holdboolean

Record the payment even though an allocated bill is on payment hold. Requires override_reason; both are written to the audit log.

override_reasonstring

Why a held bill is being paid anyway (required with override_hold).

Responses

201Successful Response

Schema: SuccessEnvelope_BillBatchPaymentResponse_

successboolean
messagestring
codestring
dataBillBatchPaymentResponse

400Bad Request - Invalid input

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

401Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

403Forbidden - Insufficient permissions

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

404Not Found - Resource does not exist

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

422Validation Error

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

Code samples

POST/api/v1/bills/payments/batch

bash

curl -X POST 'https://api.ondayzero.com/api/v1/bills/payments/batch' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "allocations": [
    {
      "amount": 50000,
      "bill_id": "019ab37c-b111-7000-8000-000000000001"
    },
    {
      "amount": 75000,
      "bill_id": "019ab37c-b111-7000-8000-000000000002"
    }
  ],
  "transaction_id": "019ab37c-7801-7000-8000-000000000001"
}'