Accounts payable—payments made 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 payable—payments made 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 (ap_payment_made_transaction_id) | A cross-reference to the general ledger posting. It can contain many different levels to identify the transaction. Examples include 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. |
Payment Number (ap_payment_made_payment_id) | The unique identifier for each payment made. This identifier may need to be created by concatenating fields, for example, supplier and payment number to uniquely identify each transaction. 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 |
| Payment Date | The date the payment was made or credit was applied. Data type: Date Required: No |
| Payment Year | Fiscal year in which Payment Date occurs. Data type: Text Required: No Primary key: No |
| Payment Period ( ap_payment_made_payment_period) | Fiscal period in which Payment Date occurs. Data type: Text Required: No Primary key: No |
| Amount Type (Debit / Credit) ( ap_payment_made_amount_credit_debit_indicator) | Indicates whether the amount is a credit or debit. Data type: Text Required: No Possible values: |
| Payment Type ( ap_payment_made_payment_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 supplier. Examples include checks, wire transfers, cash, and so on. Data type: Text Required: No |
| Payment Amount ( ap_payment_made_payment_amount) | Transaction monetary amount recorded in the functional or group currency. Data type: Money Required: No |
| Reporting Payment Amount ( ap_payment_made_payment_amount_reporting) | Transaction monetary amount recorded in the reporting currency. Data type: Money Required: No |
| Local Payment Amount ( ap_payment_made_payment_amount_local) | Transaction monetary amount in the local currency. Data type: Money Required: No |
| Posting Status ( ap_payment_made_posting_status) | Indicates whether the transaction has been posted to the General Ledger. Data type: Text Required: No Possible values: |
| Batch Number ( ap_payment_made_batch_id) | A batch identifier generated by the source system. Data type: Text Required: No |
| Payment Description ( ap_payment_made_description) | A description of the payment. Data type: Text Required: No |
| Source ID ( ap_payment_made_source_id) | 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 |
Supplier ID (ap_payment_made_supplier_account_id) | Identifier of the supplier to whom payment is received or from whom credits have been applied. Data type: Text Required: No |
| Supplier Name ( ap_payment_made_supplier_account_name) | The name of the supplier. Data type: Text Required: No |
| Entered By ( ap_payment_made_entered_by) | The user identifier of the person who created the record. Data type: Text Required: No |
| Entered Date ( ap_payment_made_entered_date) | 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 Time ( ap_payment_made_entered_time) | The time this transaction was entered into the source system. Data type: Date/time Required: No |
| Approved By ( ap_payment_made_approved_by) | The user identifier of the person who approved the entry. Data type: Text Required: No |
| Approval Date ( ap_payment_made_approved_by_date) | The date the entry was approved. Data type: Date Required: No |
| Approval Time ( ap_payment_made_approved_by_time) | The time the entry was approved. Data type: Date/time Required: No |
| Last Modified By ( ap_payment_made_last_modified_by) | The user identifier of the last person to modify this entry. Data type: Text Required: No |
| Last Modified Date ( ap_payment_made_last_modified_date) | The date the entry was last modified. Data type: Date Required: No |
| Last Modified Time ( ap_payment_made_last_modified_time) | The time the entry was last modified. Data type: Date/time Required: No |
| Invoice Number ( ap_payment_made_invoice_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 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 identifier of the entry, for example |
| Invoice Date ( ap_payment_made_invoice_date) | The date on an externally generated transaction. Examples include check date or wire transfer date. Data type: Date Required: No |
| Business Unit Code ( ap_payment_made_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 |
| GL Debit Account Number ( ap_payment_made_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 ( ap_payment_made_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 ( ap_payment_made_line_account_id) | The general ledger (GL) account code of the GL revenue account. This can include a subaccount identifier, as well as can 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 ( ap_payment_made_line_account_description) | A description of the account whose identifier appears in Line Detail - Account ID. Data type: Text Required: No |
| Payment Currency ( ap_payment_made_payment_amount_currency) | The functional or group currency related to the payment amount. Data type: Text Required: No |
| Reporting Payment Currency ( ap_payment_made_payment_amount_reporting_currency) | The reporting currency related to the payment amount for nonconsolidated reporting. Data type: Text Required: No |
| Local Payment Currency ( ap_payment_made_payment_amount_local_currency) | The currency for local reporting requirements. Data type: Text Required: No |
| Entry ID ( ap_payment_made_journal_id) | The unique identifier for a journal entry. Data type: Text Required: No |
