We are introducing a new entity: Accounting Transactions.

Accounting Transactions

In Pliant it's possible to

• assign accounting-relevant data fields (e.g. G/L accounts, VAT rates...) to a transaction
• and split one transaction into multiple sub-transactions

We do store this information not on the transaction level (transactionId) but on the accounting transaction level (accountingTransactionId). We do start exposing this data in our APIs as well by adding the following endpoints/callbacks:

1. 🔗 POST /accounting/transactions
   Returns accounting transactions for 1-n transactions, cards, cardholders or organizations
2. 🔗 POST /accounting/transactions/subscription
   Available events: ACCOUNTING_TRANSACTION_CREATED & ACCOUNTING_TRANSACTION_UPDATED

Accounting Data fields

In Pliant we do offer multiple tags/attributes that can be first created and later assigned to an accounting transaction:

• G/L Accounts
• VAT Rates
• Suppliers
• Teams (Cost Centers)
• Projects (Cost Units)

Over time we plan to expose the CRUD operations for these accounting data fields. For now we do offer reading, creating, updating and deleting for

• 🔗 Projects (Cost Centers)
• 🔗 Projects (Cost Units)

In addition to that projects can also be restricted to certain teams:

• This can be done by assigning a team to a project via
  🔗 POST /accounting/projects/team/assign.
• There is an endpoint available to unassign a team from a project via
  🔗 POST /accounting/projects/team/unassign
• If no team is assigned to a project it is accessible/visible to all members.