Account details described

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 data analytics tests to function properly. To learn more see, Mandatory fields for data analytics.

Account Identifier (account_id)

An identifier or the account the entry has been recorded in.
Examples "1001" or "Bank Account 1".

Usage

  • Must be tagged for all transaction-related features to function.
  • Associating trial balance with transaction information.
  • Trial balance drill down into transactions.
  • In all AnalyticsAI tests - All tests require Account Identifier.

Requirements

  • Less than 5,000 unique values.
  • Matches with imported trial balance accounts.

Main Account Description (account_main_description)

An identifier description for the account group the entry has been recorded in.
Examples: "Cash", "Property, plant and equipment".

Usage

Visual text description for accounts.

Entered By (entered_by)

User ID for person creating the entry.

Usage

In these AnalyticsAI tests:

  • Same User Entering and Approving
  • Unusual Users

Entered Date (entered_date)

Actual date/time 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 GL.

Usage

In the Unusual Times AnalyticsAI test.

Requirements

Date format must be properly set:

Day

D: One digit for days below 10 (for example, 2 for the 2nd day of the month)

DD: Two digits (for example, 02 for the 2nd day of the month)

DDD: Day of the year (for example, 365 for December 31st)

DDDD: Three-digit day of the year (for example, 002 for January 2nd)

Month

M: One digit for months below 10 (for example, 4 for April)

MM: Two digits (for example, 04 for April)

MMM: Three-letter abbreviation (for example, Apr for April)

MMMM: Full month name (for example, April)

Year

YY: Two digits (for example, 19 for 2019)

YYYY: Four digits (for example, 2019)

Time

H HH: Hours in 24-hour time (for example, 0 for midnight, 23 for 11 PM)

h hh: Hours in 12-hour time used with AM/PM (for example, 1 for 1 AM, 12 for noon)

k kk: Hours in 24-hour time from 1 to 24 (for example, 1 for 1 AM, 24 for midnight)

a A: Post or ante meridiem (for example, am for morning, pm for afternoon)

m mm: Minutes (for example, 0 for the top of the hour, 59 for the last minute of the hour)

s ss: Seconds (for example, 0 for the start of the minute, 59 for the last second of the minute)

S SS SSS ... SSSSSSSSS: Fractional seconds (for example, 0 for no fractional second, 999999999 for the last fractional second)

Z ZZ: Offset from UTC as +-HH:mm, +-HHmm, or Z (for example, +12:00 for 12 hours ahead of UTC)

Example Transaction

Let's say we have a transaction that occurred on April 2, 2019, at 1:30:45 PM with 123 milliseconds, and the UTC offset is +02:00. Here’s how it would look in different formats:

  • Date: 2/4/19 or 02/04/2019

  • Time: 13:30:45.123 +02:00

Entry Responsible Person (entry_responsible_person)

User ID for person approving the entry.

Usage

In the Same User Entering and Approving AnalyticsAI test.