Understand the General ledger dataset
When importing general ledger transactions from a CSV or Excel file you must assign fields in the file to Caseware fields in the General ledger dataset type you select on import, so that the general ledger data displays correctly in the engagement. This topic details how unique identifiers are autogenerated upon import as well as general ledger data descriptions.
For more information on importing transaction data from CSV files, see Import the client’s transactions from a CSV.
How unique identifiers for general ledger data rows are autogenerated
Knowing how unique identifiers are autogenerated is important if ever data conflicts arise upon data import. See Resolve data import conflicts for more information on how they can happen and what you can do to resolve them.
When you import general ledger data in CSV or Excel files, each data row must be uniquely identifiable. To accomplish this, Cloud creates a unique identifier made up of the values of the fields you assign to the Caseware fields Entry ID (entry_id) and Line Number (line_number) to form a unique identifier for each data row:
{entry_id}-{line_number}
- Where fields from the incoming import file are assigned to Entry ID but not Line Number or vice versa, a unique value is autogenerated for either Entry ID or Line Number, whichever is missing.
- Where fields from the incoming import file are not assigned at all to both Entry ID and Line Number, unique combinations are autogenerated across both of these Caseware fields.
- Where users assign a field to Entry Number but not Entry ID, Entry ID will be autofilled with values from Entry Number.
General ledger dataset described
See the links below for field descriptions in the General ledger dataset type.
