---
title: "List Accounting Transactions"
method: POST
path: "/accounting/transactions"
tags: ["Accounting Transactions"]
---

# List Accounting Transactions

`POST /accounting/transactions`

Returns accounting transactions for one or more transactions depending on the given input. You can also request accounting transaction details per card(s), cardholder(s) or organization(s). The API returns all accounting transaction details to the given input which can be found in the system. So you can also combine the different input fields (OR relation). Be aware that the usage of [cardholder](/docs/cardholder-entity) or organizations IDs most likely add multiple accounting transaction details themselves. Also cardholders can be part of multiple organizations, thus when searching via [cardholder](/docs/cardholder-entity) IDs, it might return more data than it would for just one organization this [cardholder](/docs/cardholder-entity) is part of. At least one parameter has to be set.

## Request body

- object
  - `transactionIds` string[] — The unique identifiers of the transactions to filter by.
  - `cardIds` string[] — The unique identifiers of the cards to filter by.
  - `cardholderIds` string[] — The unique identifiers of the cardholders to filter by.
  - `organizationIds` string[] — The unique identifiers of the organizations to filter by.
  - `cardAccountIds` string[] — The unique identifiers of the card accounts to filter by.
  - `exportStatus` 'NOT_EXPORTED' | 'IN_EXPORT_QUEUE' | 'EXPORTING' | 'EXPORTED' — The export status of the transaction. It can be one of the following values: `NOT_EXPORTED`, `IN_EXPORT_QUEUE`, `EXPORTING`, `EXPORTED`.
  - `pagination` object
    - `page` integer — The page number to return, starting with 0, this counts up to the total number of pages. The total number of pages is determined by the total number of records divided by the limit.
    - `limit` integer — The maximum number of items to return per page. The default value if not provided is 100, the maximum allowed value is 1000.

## Response `200`

Ok

- object
  - `data` object[]
    - `transactionId` string, uuid — The ID of the transaction.
    - `organizationId` string, uuid — The ID of the organization this transaction belongs to.
    - `cardAccountId` string, uuid — The ID of the [card account](/docs/card-account) this transaction belongs to.
    - `billingAmount` object — The amount that was billed to the cardholder, in the currency of the card account.
      - `value` number — The value of the monetary amount, converted to minor units of the currency. For instance 1.00 EUR is 100 cents, thus the value here is `100`. See our [guides](/docs/monetary-values) for more details about how to handle monetary amounts.
      - `currency` string — The currency of the monetary amount in ISO 4217 format, for example `EUR` for Euro or `USD` for US Dollar.
    - `transactionAmount` object — The amount that was transacted.
      - `value` number — The value of the monetary amount, converted to minor units of the currency. For instance 1.00 EUR is 100 cents, thus the value here is `100`. See our [guides](/docs/monetary-values) for more details about how to handle monetary amounts.
      - `currency` string — The currency of the monetary amount in ISO 4217 format, for example `EUR` for Euro or `USD` for US Dollar.
    - `supplier` object, nullable — The supplier of the transaction, if assigned.
      - `id` string, uuid — The unique identifier of the supplier.
      - `name` string — The name of the supplier.
      - `accountNumber` string — The account number of the supplier.
      - `autoMatched` boolean — Whether the supplier was automatically matched or manually set by the cardholder.
    - `exportStatus` 'NOT_EXPORTED' | 'IN_EXPORT_QUEUE' | 'EXPORTING' | 'EXPORTED' — The export status of the transaction. It can be one of the following values: `NOT_EXPORTED`, `IN_EXPORT_QUEUE`, `EXPORTING`, `EXPORTED`. This defines whether the transaction is exported to an accounting system or not.
    - `receiptNumber` string — The receipt number of a transaction if it is available. Receipt numbers are typically used to identify a transaction in an accounting system hence we store it on transaction level. If not automatically extracted it can be provided by any user within Pliant. Can be overwritten even if automatically extracted.
    - `accountingTransactions` object[] — The accounting transactions of the transaction. Contains 1..n entries, depending on whether the transaction was split into multiple accounting transactions or not.
      - `accountingTransactionId` string, uuid — The ID of the accounting transaction.
      - `index` integer — The index of the accounting transaction within the transaction.
      - `billingAmount` object — The amount that was billed to the cardholder, in the currency of the card account.
        - `value` number
        - `currency` string
      - `transactionAmount` object — The amount that was transacted.
        - `value` number
        - `currency` string
      - `subcategory` object, nullable — The subcategory of the accounting transaction, if assigned.
        - `id` string, uuid — The unique identifier of the subcategory.
        - `name` string — The name of the subcategory.
        - `accountNumber` string — The account number of the subcategory.
        - `autoMatched` boolean — Whether the subcategory was automatically matched or manually set by the cardholder.
      - `vatRate` object, nullable — The VAT rate of the accounting transaction, if assigned.
        - `id` string, uuid — The unique identifier of the VAT rate.
        - `name` string — The name of the VAT rate.
        - `rate` number, double — The rate of the VAT rate.
        - `code` string — The code of the VAT rate.
        - `autoMatched` boolean — Whether the VAT rate was automatically matched or manually set by the cardholder.
      - `project` object, nullable — The project (cost unit) of the accounting transaction, if assigned.
        - `id` string, uuid — The unique identifier of the project.
        - `name` string — The name of the project.
        - `costUnit` string — The cost unit of the project.
      - `team` object, nullable — The team (cost center) of the accounting transaction, if assigned.
        - `id` string, uuid — The unique identifier of the team.
        - `name` string — The name of the team.
        - `costCenter` string — The cost center of the team.
      - `customFields` Schema[] — The [custom fields](/docs/custom-fields-on-transactions) set on this accounting transaction. — unresolved $ref
  - `hasNextPage` boolean — Indicates whether there is a next page available.

## Other responses

- `400` — unresolved $ref
- `401` — unresolved $ref
- `403` — unresolved $ref
- `500` — unresolved $ref

---

[API](https://skmtc.dev/getpliant/apis/pliant-customer-api.md) · [All operations](https://skmtc.dev/getpliant/apis/pliant-customer-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/getpliant/pliant-customer-api/revisions/f3f589cfa718/schema)