Understand subledger datasets

See Subledger datasets described for the types of subledger dataset you can import into Caseware Cloud. Each dataset description lists the mandatory and optional fields making up transactions for that type of subledger dataset and the purpose of each field. The diagram below explains the basic elements of the subledger dataset descriptions.

For more information on importing transaction data from CSV files, see Import the client’s transactions from a CSV.

Anatomy of a subledger dataset description

Anatomy of a subledger dataset description

 

Element Description
1 User-facing name. The name of the Caseware field as it appears in the drop-downs of the Import Data window, where you map fields in your incoming data to Caseware fields.
2 Field description. This details the purpose of the field and where applicable examples of possible values.
3 Internal field name. The internal name of the Caseware field, which you will need to know if you are manipulating data imported for analytic notebooks or other third-party development work where you are manipulating the raw imported data.
4 Primary key. If a field is a primary key, its value is used to uniquely identify the data entry or row of the data.
5

Data type. The types of values a field can have and the operations that can be performed.

  • Text—Any alphanumeric value.

  • Date—Date. Note that if you map a field containing date and time, only the date portion is imported.

  • Data/time—Date and time.

  • Enum—A list of alphanumeric values can be specified.

  • Money—Values must be numeric and represent amounts of money.

6 Required. Indicates whether the field is required to be able to import a transaction of this type into Caseware Cloud.
7 Primary key alternate. If the field that is designated as the primary key is absent from the data you are importing, the value of the primary key alternate, or one of several primary key alternates, is used to create a unique identifying code for the data entry by concatenating their values together: <FirstAlternate>-<SecondAlternate>-<ThirdAlternate>

 

Subledger datasets described

Subledger dataset Description
Accounts payable - invoices

The Accounts payable—invoices dataset contains all invoices received during the period under review.
Accounts payable - payments made

The Accounts payable—payments made dataset contains all payment transactions (check, wire transfer, cash, and so on) made during the period.
Accounts payable - suppliers

The Accounts payable—suppliers dataset contains all details related to the Supplier such as Contact details, address, credit limit and so on.
Accounts payable - open balances

The Open accounts—payable dataset contains details regarding all open, unpaid, or unresolved payable transactions as of the close of business on a specified date.
Accounts receivable - invoices

The Accounts receivable—invoice dataset contains all invoices generated during the period under review.
Accounts receivable - cash received

The Accounts receivables—cash received dataset contains all payment transactions (check, wire transfer, cash, and so on) received during the period.
Accounts receivable - customers The Accounts receivable—customers dataset contains all details related to the customer, such as contact details, address, credit limit and so on.
Accounts receivable - open balances The Accounts receivable—open balances dataset contains details regarding all open, unpaid, or unresolved customer transactions as of the close of business on a specified date.
Inventory transactions Captures all transactions affecting inventory accounts during the time period specified (for example, receipts, shipments, transfers, returns, and adjustments).
Inventory on hand Captures the on-hand inventory quantities of items by location and amounts as of the specified date.