Voucher structure

Understand how Findity structures approved expense data into vouchers for export to your bookkeeping, payroll, or payment system.

When expenses are approved and sent, Findity packages them into an export containing vouchers and voucher rows. The voucher output format determines how expenses are grouped — by report, user, or individual expense — and whether full accounting detail (debit/credit/VAT rows) or simplified payment totals are included.

Key concepts

A single expense generates at least one voucher row, but typically produces multiple rows. For example, a standard receipt expense creates:

• One debit row (the expense account)
• One credit row (if bookkeeping is enabled)
• One VAT row (if applicable)

Voucher output formats

The voucher grouping is configured on the API recipient and determines how expenses are packaged into vouchers. There are 8 possible formats, split into two categories.

Formats with accounting

These include full bookkeeping detail — debit rows, credit rows, VAT rows, account numbers, salary codes, and dimensions.

Formats without accounting (payment)

These provide simplified output without bookkeeping detail — useful for payment recipients or outputs where no accounting is needed.

⚙️

The voucher output format is configured by Findity when setting up a new branded integration. You can find it in the API recipient settings. If the configuration option you need is not available, contact [email protected].

Where to find the format in the JSON

The configured format appears in two places in the export JSON:

1. Recipient configuration — under organizations → recipients → verificationListsType
2. Each voucher — in the listType field

{
  "organizations": [
    {
      "recipients": [
        {
          "verificationListsType": "REPORT_PER_EXPENSE",
          "pluginName": "ce-integration-example",
          "id": "8ab28c4f6e238a35016e25d39e00004b"
        }
      ]
    }
  ],
  "vouchers": [
    {
      "listType": "REPORT_PER_EXPENSE",
      "id": "70673d31e9704f768d70748c173ad7c1",
      "ownerId": "8ab28c4f6e238a35016e25ee3b2c0084",
      "organizationId": "8ab28c4f6e238a35016e25d39cc60048",
      "expenseReportId": "36690003376e49f597956c64d7ea7381",
      "voucherRows": []
    }
  ]
}

Voucher structure

Each voucher in the vouchers array contains the following key fields:

Voucher row structure

Each entry in the voucherRows array represents one accounting line:

Fetching voucher data

Use the Connect API to retrieve the voucher package for a specific export:

GET /v1/connect/organizations/{organizationId}/exports/{exportId}/export

→ See the Get export vouchers API reference for full request and response details.

→ See the Export integration guide for the complete step-by-step workflow.

📄

To download a PDF with booking data and receipt images, use the basisUrl from each voucher and append ?format=pdf at the end of the URL.

Processing vouchers

After fetching and importing the voucher data into your system, update the export status to confirm receipt. Send a voucherUpdates array with the processing result for each voucher:

PUT /v1/connect/organizations/{organizationId}/exports/{exportId}/updatestatus

{
  "voucherUpdates": [
    {
      "id": "70673d31e9704f768d70748c173ad7c1",
      "status": "SUCCESS",
      "bookingDate": "2024-02-21T13:58:00Z",
      "voucherNumber": "123",
      "informationText": null,
      "errorText": null
    }
  ]
}

→ See the Process export API reference for full request and response details.

Choosing the right format

Integration tips