When importing general ledger transactions from a CSV or Excel file, you must map the fields, so the transactions data display properly in the engagement.
This topic describes the fields within the ACCOUNT DETAILS category that appear in the General ledger dataset.
Note: that some fields are mandatory for specific analytic tests to function properly. Refer to the descriptions below.
account_id)An identifier or the account the entry has been recorded in.
Examples "1001" or "Bank Account 1".
Must be tagged for all transaction-related features to function.
Associating trial balance with transaction information.
Trial balance drill down into transactions.
Analytic tests (embedded analytics) require Account number.
Less than 5,000 unique values.
Matches with imported trial balance accounts.
account_main_description)An identifier description for the account group the entry has been recorded in.
Examples: "Cash", "Property, plant and equipment".
Visual text description for accounts.
entered_by)User ID for person creating the entry.
In these analytic tests:
Comparison
Unusual items
entered_date)Actual date/time the entry was posted (validated) to the general ledger - provided automatically by system - does not necessarily correspond with the date when the entry was posted to the general ledger.
In the Unusual items analytic test.
Date format must be properly set:
entry_responsible_person)User ID for person approving the entry.
In the Comparison analytic test.