Voucher Statements

A voucher statement records structured metadata about a voucher (an uploaded accounting document). It captures business context that cannot be read directly from the file itself — the purpose of the expense, who participated, how it was paid, the payor, and any project, category, or tags it relates to. Statements are commonly used to document representation and entertainment expenses where Norwegian accounting rules require the purpose and participants to be recorded.

Voucher statements are nested under a voucher. The voucher_id in the path is the ID of the voucher (an uploaded file).

Endpoints

Authentication

All requests require a valid Authorization: Bearer token. The authenticated user must have access to the client account that owns the voucher; otherwise the request is rejected with 403 Forbidden.

List Voucher Statements

GET /api/v2/vouchers/{voucher_id}/statements

Returns the voucher statements belonging to the given voucher. The response is paginated.

Query Parameters

Example Request

curl "https://api.snapbooks.no/v2/vouchers/4567/statements?with=payor,project" \
  -H "Authorization: Bearer YOUR_TOKEN"

Create Voucher Statement

POST /api/v2/vouchers/{voucher_id}/statements

Creates a statement on the voucher. The voucher_id and client_account_id are taken from the voucher in the path, and created_by_id and user_id are set to the authenticated user — any values for these fields in the request body are ignored.

Request Body

Payment Methods

Purposes

The purpose field accepts a single enum value. Any other value is rejected with 400 Invalid purpose.

Item Categories

The item_categories field accepts one or more enum values separated by commas, semicolons, or whitespace (e.g. "ELECTRONICS, OFFICE_OR_WAREHOUSE_SPACE"). Any value not in the list below is rejected with 400 Invalid item category.

Example Request

curl -X POST "https://api.snapbooks.no/v2/vouchers/4567/statements" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "purpose": "INTERNAL_EMPLOYEE_EVENTS",
    "item_categories": "FOOD, ENTERTAINMENT",
    "participant_information": "Jane Doe (Acme AS), John Smith (Snapbooks AS)",
    "payment_method": "BUSINESS_CARD",
    "payor_id": 56,
    "project_id": 8,
    "tags": [{ "id": 12 }]
  }'

Example Response (201 Created)

{
  "id": 9001,
  "created_at": "2026-06-02T10:15:00Z",
  "created_by_id": 7,
  "client_account_id": 7,
  "voucher_id": 4567,
  "voucher_category_id": null,
  "item_categories": "FOOD, ENTERTAINMENT",
  "purpose": "INTERNAL_EMPLOYEE_EVENTS",
  "participant_information": "Jane Doe (Acme AS), John Smith (Snapbooks AS)",
  "additional_information": null,
  "payment_method": "BUSINESS_CARD",
  "payor_id": 56,
  "project_id": 8,
  "collection_id": null
}

Attributes

Relations

Relations are opt-in. Request them through with, e.g. ?with=payor,project,tags.

Error Responses

Related Resources

• Vouchers
• Voucher Collections
• Business Partners
• Projects
• Tags