Unapplied Payable Documents List View

Unapplied Payable Documents List View

The purpose of this page is to display all the outstanding A/P Credit Memos and Manual Payments. Outstanding transactions are defined as transactions that have not been fully applied. This page will be filtered to display transactions associated with the Vendor(s) selected on the Vendor Balances List View. If no Vendors are selected, then this page will display all outstanding debit balance transactions that have not been fully applied. From here, users can select a single transaction and click the 'Apply Document' icon in the header toolbar to manually apply the selected transaction to one or more credit balance transactions. 

Software Version: 2021.04.09 and newer

Page Header

Toolbar Icons

Description

Toolbar Icons

Description

Apply Document

Opens the Apply Payables Document Record View. Users must select a transaction prior clicking this toolbar icon. Only one transaction can be selected at a time.

Excel

Grid Layout

Help

Inquiry Criteria

  • Include transactions through: A textbox that defaults to the current date.

  • Hide fully applied transactions: A Yes/No lookup that defaults to "Yes". If set to "Yes", then fully applied transactions will not be in the returned results. 

  • Vendor: A multi-select lookup that defaults to the Vendor(s) that was selected prior to clicking the Apply Documents button on the Vendor Balances list view. If no Vendor was selected, this field defaults to blank.

Refresh

Fields

Description

Checkbox

Used to select one transaction to apply a document to.

Doc Date

This field is required. It comes from the 'Payment Date' field on the header of the Process Payments Record View for payment transactions. It comes from the 'Doc Date' field on the 'Home' tab of the Credit Memo Record View for Credit Memo transactions. This field is not editable after the transaction has been posted.

Database Fields: ERPx_APTransactionHeader.TransactionDate (Credit Memo), ERPx_MFTransactionBatch.BatchDate (Payment)

Doc No

This field is required. For Payment transactions, this field comes from the 'Payment #' field on the payment grid of the Process Payments Record View (e.g. this is the most often the Check #). For Credit Memo transactions, this field comes from the 'Doc No' field on the 'Home' tab of the Credit Memo Record View. This field is not editable after the transaction has been posted.

Database Field: ERPx_APTransactionHeader.DocNumber (Credit Memo), ERPx_MFTransactionBatch.TransactionID (Payment)

GL Date

This field is required and is not editable after the transaction has been posted. For Payment transactions, this field field comes from the 'Payment Date' field on the header of the Process Payments Record View. For Credit Memos this comes from the GL Date field.

Database Field: ERPx_ARTransactionHeader.GLDate (Credit Memo), ERPx_MFTransactionBatch.BatchDate (Payment)

GL Period

This field is required and calculated using the 'GL Date' property of the transaction. This field is not editable.

GL Year

  This field is required and calculated using the 'GL Date' property of the transaction. This field is not editable.

Original Amount

 This is the original amount of the transaction when it was posted, prior to any applications being done. This field is required. For Payment transactions, this field comes from the is the 'Amount' field in the payments grid of the Process Payments Record View. For Credit Memo transactions, this field comes from the 'Amount' field on the 'Home' tab of the Credit Memo Record View. This field is not editable after the transaction has been posted.

Database Fields: ERPx_APTransactionHeader.ExtendedAmount (Credit Memo), ERPx_MFCheckbookTransaction.Amount (Payment)

Transaction

Clicking on this link opens the record view for the selected transaction. This is a system assigned number that comes from the 'Transaction Class' for Credit Memo transactions and the 'Next Check #' or 'Next ACH #' of the associated checkbook for Payment transactions. This field is not editable.

Database Field: ERPx_APTransactionHeader.TransactionID (Credit Memo), ERPx_MFTransactionBatch.TransactionID (Payment)

Transaction Type

This is required and comes from the Transaction Type selected when starting a new transaction. This field is not editable. The following transaction types have the ability to debit the Accounts Payable account and display on this page:

  • Credit Memo

  • Payment

Database Fields: ERPx_APTransactionType.TransactionName, ERPx_APTransactionClass.TransactionTypeSK, ERPx_APTransactionHeader.TransactionClassSK

Unapplied Amount

This is required and updates when amounts are entered in the 'Applied Amount' field on the Apply Payables Document Record View. This is calculated by subtracting previous applications from the 'Original Amount'. This value is not stored in the database.

Vendor

This field is required and is not editable after the transaction has been posted.

Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.VendorSK (Credit Memo), ERPx_MFCheckbookTransaction.EntitySK (Payment)

Vendor Name

 This field is required and is not editable after the transaction has been posted.

Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK (Credit Memo), ERPx_MFCheckbookTransaction.EntitySK (Payment)

Related Topics

User Guide: Vendor Balances

 

Page Definitions

 

Technical Details