Accounting Transaction
Accounting transactions are a sub-entity of transactions and are mainly used for pre-accounting features within Pliant apps. A transaction can have multiple accounting transactions (currently up to 10) but it always consists of at least one accounting transaction. Additional accounting transactions are created once the user (within Pliant apps) splits the transaction into multiple so-called sub-transactions. Each accounting transaction can be enriched with data for pre-accounting purposes automatically or manually.
For each sub-object (subcategory, VAT rate, project and team) the ID
properties are the unique IDs used in the Pliant backend. While the automatched
property indicates how the value has been assigned to the accounting transaction. If true
via rule (can be set up per card or merchant) and if false
, manually via Pliant web or mobile application(s). All properties are nullable in case no values are assigned to the accounting transaction(s).
Data Model
Field | Type | Description |
---|---|---|
accountingTransactionId | uuid | An identifier for the accounting transaction, unique for the platform. |
index | integer | The index of the accounting transaction within the transaction. This defines the position the single accounting transactions have in the UI of Pliant apps. |
billingAmount | object | An array regarding the split billing amount of the accounting transactionvalue (decimal)currency (string)Important: For transactions processed in a foreign currency this parameter includes the corresponding EUR amount. |
transactionAmount | object | An array regarding the split transaction amount for the accounting transaction. For parent transactions in a foreign currency, this property includes the amount in the given currency.value (decimal)currency (string)Important: For transactions processed in EUR this parameter includes the corresponding EUR amount. |
subcategory | object | Each accounting transaction can be assigned a subcategory that equals essentially the G/L account. It is possible to assign different subcategories to different accounting transactions but on the other hand: multiple accounting transactions can have the same subcategory or G/L account. The name is defined by the user during import or set-up within Pliant. This property is nullable. |
vatRate | object | Each accounting transaction can be assigned a VAT Rate. It is possible to assign different VAT rates to different accounting transactions but on the other hand: multiple accounting transactions can have the same VAT rate. Name, rate (percentage) and code are all defined by the user during set-up within Pliant. This property is nullable. |
project | object | Each accounting transaction can be assigned a project that equals essentially the cost unit. It is possible to assign different projects/cost units to different accounting transactions but on the other hand: multiple accounting transactions can have the same project/cost unit assigned. Name and cost unit are all defined by the user during set-up within Pliant. This property is nullable. |
team | object | Each accounting transaction can be assigned to a team that equals essentially the cost center. It is possible to assign different teams/cost centers to different accounting transactions but on the other hand: multiple accounting transactions can have the same team/cost center assigned. Name and cost center are all defined by the user during set-up within Pliant. This property is nullable. |
customFields | string | see this page for more details about custom fields. |
Suppliers
Each transaction can be assigned to a supplier within Pliant for pre-accounting purposes. Currently, it is not possible to assign different suppliers per accounting transaction but the List Accounting Transactions endpoint returns supplier information for the parent transaction. The id
property is the internal ID, while accountNumber
and name
are assigned by the customer manually or automatically during the import of the supplier. The autoMatched
property indicates if the supplier has been automatically assigned by Pliant (based on rules) or manually by a user via the Pliant apps. This property is nullable in case no supplier is assigned to the (accounting) transaction.
Example Data
"data": [
{
"transactionId": "a7ba016a-9818-11ee-b9d1-0242ac120002",
"organizationId": "ac3b1c88-9818-11ee-b9d1-0242ac120002",
"billingAmount": {
"value": 20.50,
"currency": "EUR"
},
"transactionAmount": {
"value": 24.10,
"currency": "USD"
},
"supplier": {
"id": "b02cd96c-9818-11ee-b9d1-0242ac120002",
"name": "Global Warehouse",
"accountNumber": "720042",
"autoMatched": true
},
"accountingTransactions": [
{
"accountingTransactionId": "c09f60f8-9818-11ee-b9d1-0242ac120002",
"index": 0,
"billingAmount": {
"value": 10.25,
"currency": "EUR"
},
"transactionAmount": {
"value": 12.05,
"currency": "USD"
},
"subcategory": {
"id": "c09f60f8-9818-11ee-b9d1-0242ac120002",
"name": "Product Marketing",
"accountNumber": "10010",
"autoMatched": true
},
"vatRate": {
"id": "ed4d4e4e-9818-11ee-b9d1-0242ac120002",
"name": "Default VAT Rate",
"rate": 19.00,
"code": "D-VAT",
"autoMatched": true
},
"project": {
"id": "f0cb4c7e-9818-11ee-b9d1-0242ac120002",
"name": "Apollo",
"costUnit": "100"
},
"team": {
"id": "f4494202-9818-11ee-b9d1-0242ac120002",
"name": "Product Marketing",
"costCenter": "AB10"
}
},
{
"accountingTransactionId": "4f89f29c-9819-11ee-b9d1-0242ac120002",
"index": 0,
"billingAmount": {
"value": 10.25,
"currency": "EUR"
},
"transactionAmount": {
"value": 12.05,
"currency": "USD"
},
"subcategory": {
"id": "5c74df30-9819-11ee-b9d1-0242ac120002",
"name": "Branding",
"accountNumber": "10020",
"autoMatched": true
},
"vatRate": {
"id": "6254214a-9819-11ee-b9d1-0242ac120002",
"name": "Special VAT Rate",
"rate": 14.00,
"code": "S-VAT",
"autoMatched": true
},
"project": {
"id": "66c917ee-9819-11ee-b9d1-0242ac120002",
"name": "Mercury",
"costUnit": "200"
},
"team": {
"id": "6a824cb6-9819-11ee-b9d1-0242ac120002",
"name": "Branding",
"costCenter": "AB20"
}
],
}
],
"hasNextPage": true
}
Updated 7 months ago