Financial Ledger Transaction

This document provides even more information as well as suggestions around importing data to create financial ledger transaction entries in the Metrix Asset Management system. It is broken into a number of sub-sections to assist readers in being able to focus on different asset management data contexts separately. These include:

Fixed Transaction Fields

The following fields form the basis of the transaction import.

Component ID

This field is the unique ID of the component throughout the system.

• Header label: component_record_id
• This value is case sensitive and should be copied from the component info panel directly.

See also Component info panel ↗

Posting Date

This is the date in which the transactions should be recognised in the financial ledger.

• Header label: posting_date
• Don’t forget that date values should be formatted ‘DD/MM/YYYY’.
• If the data import is for a site initialisation, users typically set this value to the end of the last financial reporting period - i.e. 30/06/2023 for the 2023 EOY.

Finance Category ID

This is the unique ID of the finance category that the imported transactions will be assigned to.

• Header label: finance_category
• The finance category ID can be copied from the finance categories configuration page.
• If a component carries value, and transaction postings are being imported, this is a REQUIRED field.
• If a component has no current transaction postings, this is a REQUIRED field.

Transaction Type Headers

Following the above fixed columns, the next set of columns to include are for transaction types and their corresponding transaction value.

For each ‘Transaction Type’ with a corresponding value for a row’s component, the transaction type ID ↗ must be used as the header value, and the transaction value constitutes the cell value for each row.