Accounts receivable—cash received 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—cash received subledger.
For more information on the subledger dataset 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 | 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. |
| Receipt Number | The unique identifier for each payment received, from which accounts receivable (AR) is derived. 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 |
| Receipt Date | The date the customer is recognized to have made the payment or have had a credit applied. Data type: Date Required: No |
| Receipt Fiscal Year | The fiscal year in which Receipt Date occurs. Data type: Text Required: No |
| Receipt Period | The fiscal period in which Receipt Date occurs. Data type: Text Required: No |
| Amount Type—Debit / Credit | Indicates whether the amount is a credit or debit. Data type: Text Required: No Possible values: |
| Receipt Type | The code value or indicator of the method by which the transaction debit or credit amount was extinguished or apportioned to the debt by the customer. Examples include check, wire transfer, cash, and so on. Data type: Text Required: No |
| Receipt Amount | The transaction monetary amount recorded in the functional or group currency. Data type: Money Required: No |
| Receipt Amount Reporting | The transaction monetary amount recorded in the reporting currency. Data type: Money Required: No |
| Receipt Amount Local | Transaction monetary amount in local currency. Data type: Money Required: No |
| Posting Status | Indicates whether the transaction has been posted to the general ledger (GL). Data type: Text Required: No Possible values: Posted, Not Posted |
| Receipt Number ( ar_cash_received_receipt_number | The number of the cash received, from which accounts receivable (AR) is derived. Data type: Text Required: No |
| Project ID ( ar_cash_received_project_id | The unique identifier for the project, from which accounts receivable (AR) is derived. Data type: Text Required: No |
| Functional Amount ( ar_cash_received_functional_amount | The transaction monetary amount recorded in the functional or group currency. Data type: Money Required: No |
| Description ( ar_cash_received_remark | A free-form text description. Data type: Text Required: No |
| Batch Number ( ar_cash_received_batch_id | A batch identifier generated by the source system. Data type: Text Required: No |
| Payment Description ( ar_cash_received_description | A description of the payment. Data type: Text Required: No |
| Source ID ( ar_cash_received_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 |
| Customer Account ID ( ar_cash_received_customer_account_id | Identifier of the customer from whom payment is received or to whom credits have been applied. Data type: Text Required: No |
| Customer Account Name ( ar_cash_received_customer_account_name | The name of the customer. Data type: Text Required: No |
| Business Unit Code ( ar_cash_received_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 |
| Invoice Number ( ar_cash_received_invoice_number | The identification number for an internally or externally generated transaction. Examples include check number, wire transfer number, or original document ID. Data type: Text 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 Date ( ar_cash_received_invoice_date | The date on an externally generated transaction. Examples include check date or wire transfer date. Data type: Date Required: No |
| Other Reference Number ( ar_cash_received_reference_number | An 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_cash_received_reference_date | The date on an externally generated transaction. Examples include check date or wire transfer date. Data type: Date Required: No |
| Sales Contract ID ( ar_cash_received_sales_contract_id | The unique identifier for the sales contract, from which AR is derived. Data type: Text Required: No |
| Receipt Amount Currency ( ar_cash_received_receipt_amount_currency | The functional or group currency related to the receipt amount. Data type: Text Required: No |
| Receipt Amount Reporting Currency ( ar_cash_received_receipt_amount_reporting_currency | The reporting currency related to the receipt amount for nonconsolidated reporting. Data type: Text Required: No |
| Receipt Amount Local Currency ( ar_cash_received_receipt_amount_local_currency | The currency for local reporting requirements. Data type: Text Required: No |
| Functional Currency Code ( ar_cash_received_functional_currency_code | The recording currency used in financial accounting software. Data type: Text Required: No |
| GL Debit Account Number ( ar_cash_received_gl_debit_account_number | The general ledger (GL) account number on which the debit side of the transaction has been posted. Data type: Text Required: No |
| GL Credit Account Number ( ar_cash_received_gl_credit_account_number | The general ledger (GL) account number on which the credit side of the transaction has been posted. Data type: Text Required: No |
| Line Detail - Account ID ( ar_cash_received_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_cash_received_line_account_description | The description of Invoice Line. Data type: Text Required: No |
| Entered By ( ar_cash_received_entered_by | The user identifier of the person who created the record. Data type: Text Required: No |
| Entered Date ( ar_cash_received_entered_date | The date this transaction was entered into the source system. This is sometimes referred to as the creation date. Data type: Date Required: No |
| Entered Time ( ar_cash_received_entered_time | The time this transaction was entered into the source system. Data type: Date/time Required: No |
| Approved By ( ar_cash_received_approved_by | The user identifier of the person who approved customer master additions or changes. Data type: Text Required: No |
| Approval Date ( ar_cash_received_approved_date | The date the entry was approved. Data type: Date Required: No |
| Approval Time ( ar_cash_received_approved_time | The time the entry was approved. Data type: Date/time Required: No |
| Last Modified By ( ar_cash_received_last_modified_by | The user identifier of the last person to modify this entry. Data type: Text Required: No |
| Last Modified Date ( ar_cash_received_last_modified_date | The date the entry was last modified. Data type: Date Required: No |
| Last Modified Time ( ar_cash_received_last_modified_time | The time the entry was last modified. Data type: Date/time Required: No |
| Entry ID ( ar_cash_received_journal_id | The unique identifier for the journal entry. This is autogenerated by the source system. Data type: Text Required: No |
