Accounts receivable—invoices described
When importing subledger transactions from a CSV or Excel file you must assign fields in the file to Caseware fields in the subledger dataset type you select on import, so that the transaction data displays correctly in the engagement. This topic details the fields in the Accounts receivable—invoices subledger.
For more information on the subledgerset data descriptions, see Understand subledger data.
For more information on importing transaction data from CSV files, see Import the client’s transactions from a CSV.
| Field | Usage |
|---|---|
| Transaction ID ( ar_invoice_transaction_id | A cross-reference to the general ledger (GL) posting. It can contain many different levels to identify the transaction, including cost centers, such as company, division, region, group and branch/department. Data type: Text Required: No Primary key: The value of this field is used to form the unique identifier of this entry. |
| Invoice Fiscal Year ( ar_invoice_invoice_fiscal_year | The fiscal year in which Invoice Date occurs. Data type: Text Required: No |
| Invoice Period ( ar_invoice_invoice_period | The fiscal period in which Invoice Date occurs. Data type: Text Required: No |
| Invoice Due Date ( ar_invoice_invoice_due_date | The date payment is due from the customer. Aging of a receivable is usually calculated based on this date. Data type: Date Required: No |
| Sales Order ID ( ar_invoice_sales_order_id | The sales order identifier for invoiced items. Data type: Text Required: No |
| Invoice Amount ( ar_invoice_invoice_amount | The transaction monetary amount recorded in the functional or group currency. Data type: Money Required: No |
| Reporting Invoice Amount ( ar_invoice_invoice_amount_reporting | The transaction monetary amount recorded in the reporting currency. Data type: Money Required: No |
| Local Invoice Amount ( ar_invoice_invoice_amount_local | The transaction monetary amount in local currency. Usually the amount seen on the original invoice document. Data type: Money Required: No |
| Grouping Code ( ar_invoice_grouping_code | A grouping mechanism for related items in a batch or grouping of invoices, such as the invoice grouping found in certain ERP systems. Data type: Text Required: No |
| Payment Description ( ar_invoice_description | A free-form description of the payment. Data type: Text Required: No |
| Batch Number ( ar_invoice_batch_id | A batch identifier generated by the source system. Data type: Text Required: No |
| Source ID ( ar_invoice_source_id | The posting source. The code for the source where the journal entry originated, such as sales journal, cash receipts journal, general journal, payroll journal, accountant manual entry, spreadsheet, and so on. Data type: Text Required: No |
| Invoice Number ( ar_invoice_invoice_number | An identification number for an internally generated invoice. Data type: Text Required: Yes Primary key: First alternate. If Transaction ID is not present in the data, the value of this field is concatenated with the values of the other alternate fields to form the unique identifier of the entry, for example |
| Invoice Date ( ar_invoice_invoice_date | The date of the invoice, regardless of the date the invoice is entered. This is the date from which the due date is calculated based on the invoice terms. Data type: Date Required: No Primary key: Second alternate. If Transaction ID is not present in the data, the value of this field is concatenated with the values of the other alternate fields to form the unique identifier of the entry, for example |
| Invoice Amount ( ar_invoice_invoice_amount | Transaction monetary amount recorded in the functional or group currency. Data type: Money Required: No |
| Invoice Due Date ( ar_invoice_invoice_due_date | The date payment is due to the supplier. Not all transactions will have a due date (for example, credit memos). Data type: Date Required: No |
| Business Unit Code ( ar_invoice_business_unit_code | Used to identify the business unit, region, branch, and so on at the level that financial statements are being audited. Data type: Text Required: No |
| Other Reference Number ( ar_invoice_reference_number | The identification number for an internally or externally generated transaction. Examples include check number, wire transfer number, or original document identifier. Data type: Text Required: No |
| Other Reference Date ( ar_invoice_reference_date | The date on an externally generated transaction. Examples include check date or wire transfer date. Data type: Date Required: No |
| Customer Account ID ( ar_invoice_customer_account_id | The identifier of the customer from whom payment is expected or to whom unused credits have been applied. Data type: Text Required: No |
| Customer Account Name ( ar_invoice_customer_account_name | The name of the customer. Data type: Text Required: No |
| Invoice Terms Discount Percentage ( ar_invoice_terms_discount_percentage | The discount percentage the customer may take if an invoice is paid before a certain number of days. Data type: Decimal Required: No |
| Invoice Terms Discount Days ( ar_invoice_terms_discount_days | The number of days from the invoice date the customer has to take advantage of discounted terms. Data type: Integer Required: No |
| Invoice Term Due Days ( ar_invoice_terms_due_days | The number of days allowed to meet the obligation before an invoice becomes overdue. Data type: Integer Required: No |
| Entered By ( ar_invoice_entered_by | The date the transaction was entered into the source system. This is sometimes referred to as the creation date. Data type: Date Required: No |
| Entered Date ( ar_invoice_entered_date | The time this transaction was entered into the source system. Data type: Date/time Required: No |
| Entered Time ( ar_invoice_entered_time | The time this transaction was entered into the source system. Data type: Date/time Required: No |
| Approved By ( ar_invoice_approved_by | The user identifier of the person who approved customer master additions or changes. Data type: Text Required: No |
| Approval Date ( ar_invoice_approved_by_date | The date the entry was approved. Data type: Date Required: No |
| Approval Time ( ar_invoice_approved_by_time | The time the entry was approved. Data type: Date/time Required: No |
| Last Modified By ( ar_invoice_last_modified_by | The user identifier of the last person modifying this entry. Data type: Text Required: No |
| Last Modified Date ( ar_invoice_last_modified_date | The date the entry was last modified. Data type: Date Required: No |
| Last Modified Time ( ar_invoice_last_modified_time | The time the entry was last modified. Data type: Date/time Required: No |
| Invoice Currency ( ar_invoice_invoice_amount_currency | The functional or group currency related to the invoice amount. Data type: Text Required: No |
| Reporting Invoice Currency ( ar_invoice_invoice_reporting_currency | The reporting currency related to the invoice reporting amount for nonconsolidated reporting. Data type: Text Required: No |
| Local Invoice Currency ( ar_invoice_invoice_local_currency | The currency for local reporting requirements. Data type: Text Required: No |
| Tax Type ( ar_invoice_tax1_type | The code for the tax type. Examples include Sales, VAT. Data type: Text Required: No |
| Tax Description ( ar_invoice_tax1_type_description | The Tax Type description. For example, the authority to which tax is paid and other information to identify the type of tax. Data type: Text Required: No |
| Tax Amount ( ar_invoice_tax1_local | The amount of the tax indicated in Tax Type that is included in the transaction. Recorded in local currency. Data type: Text Required: No |
| Official Invoice Code ( ar_invoice_official_invoice_code | The unique official code of the invoice, which is usually generated by the tax authorities. Data type: Text Required: No |
| Line Detail - Account ID ( ar_invoice_line_account_id | The general ledger (GL) account code of the GL revenue account. This code can contain a subaccount identifier, as well as many different levels to identify the Account, including cost centers, such as company, division, region, group and branch/department. Data type: Text Required: No |
| Line Detail - Account Description ( ar_invoice_line_account_description | The description of the account whose identifier appears in Line Detail - Account ID. Data type: Text Required: No |
