For each single debit or credit entry a separate record is provided. It contains the following data fields.
SWAGGER UI NAME | DESCRIPTION |
accountId | Reference to the underlying current account |
companyId | Tenant |
postingDate | Posting Date |
validityDate | Date of Valuta |
gaap | GAAP for which the booking is generated (HGB, IFRS etc.) |
accountingEventType | The accounting event type explains the trigger for which reason the set of entries has been generated. In general one can differentiate between set of entries which have been generated because A) A cash flow reached its maturity date B) A payment for the deal has been processed C) A Periodical valuation event such as interest accrual, amortisation fair valuing has been |
setOfEntries | Name of set of entries |
bookingSortNo | Number which is unique within a set of entries. It can be used to sort the bookings withing one set of entries for presentation purposes |
genledAccountNumber | Account Number |
genledAccountName | Account Name |
debitCreditSign | Sign which indicates the entry as debit or credit |
signOfMeasureOrRatio | Sign which indicates if the measure/ratio to be booked is + or - |
amountOriginal | Booked amount in Transaction Currency |
currencyOriginal | Currency of transaction |
amountBal | Booked amount in functional currency/balance sheet currency |
measureOrRatioDescription | Name of measure/ratio which describes the amount which has been booked. E.g. “Interest in arrears”, “Repayment” |
bookingCodeShortName | Booking code/transaction code which is individual for each single entry |
bookingCodeDescription | Booking code/transaction code which is individual for each single entry |