AP Invoices represent transactions that carry amounts the company owes for purchasing goods or services from a Vendor. AP Credit Memos represent transactions that carry amounts owed to the company because of returns and/or credits on goods or services previously purchased from a Vendor. The purpose of this page is to view, add, edit, remove, and post AP Invoices and Credit Memos. Additionally, users can Mass Update the GL Date, Pmt/Apply Hold, and Status of multiple transactions at once.
This list view also contains columns for each Attribute that is set up for the 'AP Purchasing' attribute type. Because these are user defined, they are not included in the default view but can be added a saved layout. AP Purchasing attributes are not included in the help documentation.
Software Version: YYYY.MM.DD and newer
Page Header
Toolbar Icons | Description |
---|---|
Delete | Deletes the selected record(s). When clicked, users will be prompted with: "Are you sure you want to delete the selected records?". Click "OK" to confirm, or "Cancel" to return without deleting. WARNING: Records cannot be recovered once they are deleted! |
Edit | Opens the selected record for editing. If a record is not selected, the page will not open. |
Excel | Export the contents of the list view to an Excel file that will automatically download. The contents that export are those that are visible to the user. Therefore, if the user has filtered the view only the filtered contents will be exported. |
Favorites | Clicking on the star icon when it is an outline, adds the page to the 'My Shortcuts' tab and fills in the star. Clicking on the star icon when it is filled in (solid color), removes the page from the 'My Shortcuts' tab and returns the icon to an outline. Users must log out and back in before the pages will be visible in the 'My Shortcuts' tab. |
Grid Layout | Opens the Saved Grid Layout menu that allows the user to select another saved layout, create a new layout, save changes to a layout, or assign a saved layout as the default for the page. Once changes are made to a grid, such as columns are added or removed, the user can click the Saved Grid Layout icon and save the changes to the grid layout and name the new layout. The new layout can also be set as the default, instead of the System View. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific). The bolded view is the default view, which will determine the view will automatically display in when opened. |
Help | Opens the online WIKI help page for the current page. This icon is only visible on pages that are documented in the online help. |
Mass Update | Opens the mass update dialog, which allows to mass update the following properties:
|
New | Allows users to select the type of transaction or record they want to add. The list contains:
|
Opens the Print dialog window, where transaction and/or analysis reports can be downloaded, printed and/or emailed. | |
Fields | Description |
Checkbox | Used to select one or more records to perform an action, such as Mass Update, More Actions, or Delete. |
Amount | Displays the amount of the transaction, in the currency and currency format of the transaction. This comes from the 'Amount' on the 'Home' tab of the Invoice/Credit Memo Record View and is calculated based on the sum of all transaction lines. This can only be edited by changing the quantity and/or price of one or more transaction lines. Database Field: ERPx_APTransactionHeader.ExtendedAmount |
Currency | Identifies the Currency assigned to the transaction. This comes from the 'Currency ID' on the 'Properties' tab of the Invoice/Credit Memo Record View. This defaults from the Currency setup on the Vendor and is not editable on the transaction. The Currency identifies the kind of money used for transactions. For example, if a Customer or Vendor is setup with a Currency of "USD" then all transactions for them are stated in terms of US Dollars and all payments received or made must be in US Dollars. Database Fields: ERPx_MFCurrency.CurrencyID, ERPx_APTransactionHeader.CurrencySK |
Doc Date | Identifies the date of the transaction. This comes from the 'Doc Date' on the 'Home' tab of the Invoice/Credit Memo Record View. This defaults from the current date and is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionHeader.TransactionDate |
Doc Description | Error rendering macro 'excerpt-include' : No link could be created for 'Doc Description'. This comes from the 'Description' on the 'Home' tab of the Invoice/Credit Memo Record View. This defaults as blank and is always editable, even after the transaction is Posted.Database Field: ERPx_APTransactionHeader.Description |
Doc No | Identifies the Doc No (document number) for the transaction. Unlike a Transaction ID that is system assigned based on the Transaction Class of the Transaction Type, this is a manually entered value. This comes from the 'Doc No' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the transaction/Invoice # assigned by your Vendor. This defaults as blank and is required. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionHeader.DocNumber |
GL Date | Identifies the date the transaction posted (or will post) to the general ledger. This comes from the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View. This defaults as blank and if not manually edited, will be automatically set to match the 'Doc Date' when the transaction is saved with a Status of either Approved or Ready to Post. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionHeader.GLDate |
GL Period | Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This is calculated using the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View. This can only be edited by changing the GL Date. |
GL Year | Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This is calculated using the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View. This can only be edited by changing the GL Date. |
Payment Terms | Identifies the Payment Terms assigned to the transaction. This comes from the 'Payment Terms' on the 'Home' tab of the Invoice/Credit Memo Record View. This defaults from the 'Payment Terms' setup on the Vendor and is always editable while the transaction is in a Status of New. If the Payment Terms are changed, the 'Due Date' and 'Discount Date' values will be automatically updated based on the new Payment Terms. Payment Terms identify the terms your company extends to your Customers and that your Vendors extend to you. Payment Terms are used to calculate aging and payment discounts. Database Fields: ERPx_MFPaymentTerms.PaymentTermName, ERPx_APTransactionHeader.PaymentTermSK |
Pmt./Apply Hold | Displays as "Yes" for AP Invoices and Credit Memos that are on a Payment or Application hold. This comes from the 'Pmt./Apply Hold' on the 'Properties' tab of the Invoice/Credit Memo Record View. This defaults as blank and is always editable, even for posted transactions as long as they have not yet been fully applied.
Database Field: ERPx_APTransactionHeader.IsOnApplicationHold |
PO | Identifies the Purchase Order number (PO number) entered for the transaction or transaction line item. This comes from the 'PO' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the purchase order you used when making the purchase. This defaults as blank and is not required. This is always editable while the transaction is in a Status of New. Database Field: ERPx_APTransactionHeader.PurchaseOrderID |
Status | Identifies the Status of the transaction. This comes from the 'Status' on the 'Home' tab of the Invoice/Credit Memo Record View and represents the status of the transaction. This defaults as 'New' and is required. This is always editable while the transaction is in a Status of 'New' or 'Approved'. Status is used to identify where a transaction, Purchase Order, Price List, BOM, or Master File record is in its life cycle. Records start in a Status of 'New' and progress sequentially through additional statuses until they are 'Posted' or 'Closed'. The list of potential Statuses changes depending on the transaction type. The Statuses that apply to transactions in this List View include: New: This is the default Status for all new Transactions. While in the Status of 'New' transactions are considered open and all editable fields are open for edit, no posting or approval validations are performed, GL Dates are not assigned, and journal entries are not created. If the transaction was moved back from Approved to New, the GL Date will be assigned and a Journal Entry will exist. Approved: Performs all the data validations required to post the transaction and applies to all Transactions. While in the Status of 'Approved' transactions are considered open but have limited fields open for edit. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled except for the Status lookup (and any fields that are always editable), journal entries are created/updated, journal ID's are assigned to the journal entry, and blank 'GL Dates' are assigned. Ready to Post: Runs the Approval validations and applies to all transactions. While in the Status of 'Ready to Post' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable. If one or more validations fail, messages are provided indicating what needs to be corrected. If all the validations pass, then all the fields are disabled with the exception any fields that are always editable and updates the Transaction Status to "Posted". Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APTransactionHeader.TransactionStatusSK |
Transaction | Identifies the unique Transaction ID for each transaction. Clicking on this link opens the AP Invoice / Credit Memo Record View for the selected record. This is a system assigned number that comes from the 'Transaction Class' and is required but is not editable by users. Transaction numbers are system assigned IDs to differentiate unique transactions. Transaction ID's are unique by the unique combination of 'Transaction Type' + 'Transaction Class'. Database Field: ERPx_APTransactionHeader.TransactionID |
Transaction Class | The unique identifier of the Transaction Class. This comes from the 'Transaction Class' on the 'Properties' tab of the Invoice/Credit Memo Record View. This defaults as 'Default' and is not editable. Transaction Classes are used to differentiate transactions within a Transaction Type. For example, Transaction Classes of Fresh and Frozen can be setup for the Transaction Type of 'Sales Order'. Transaction Classes are used in all functional areas throughout the application. Database Fields: ERPx_APTransactionClass.TransactionClassDescription, ERPx_APTransactionHeader.TransactionClassSK |
Transaction Type | Error rendering macro 'excerpt-include' : No link could be created for 'Transaction Type - lv'. This comes from the Transaction Type selected when starting a new transaction. This is never editable.Transaction Types are used to differentiate unique types transactions within the system. Transactions with the same Transaction Type share the same record view pages and business rules. Transaction Types can be further classified using Transaction Classes. Every transaction in the system is assigned a Transaction Type. Database Fields: ERPx_APTransactionType.TransactionName, ERPx_APTransactionHeader.TransactionClassSK |
Vendor | Identifies the ID of the Vendor account that is assigned to the transaction. This represents the ID of the 'Vendor' on the 'Home' tab of the Invoice/Credit Memo Record View. This is only editable by changing the Vendor assigned to the transaction. Vendor IDs are used as a short description and unique identifier for Vendor records. They can be changed at any time to any alphanumeric value. If you do not have an existing strategy for Vendor IDs the 3-3-2 method would be recommended. Database Fields: ERPx_APVendor.VendorID, ERPx_APTransactionHeader.VendorSK |
Vendor Class | Identifies the class that is assigned to the Vendor on the transaction. This comes from the 'Vendor Class' assigned to the 'Vendor' that is selected on the 'Home' tab of the Invoice/Credit Memo Record View. Because this defaults from the Vendor it is not editable on the transaction. Vendor Classes are used to identify default values that will be applied to new Vendor accounts and to group Vendor accounts together for reporting purposes. Database Field: ERPx_APVendorClass.ClassDescription, ERPx_APTransactionHeader.VendorSK |
Vendor Name | Identifies the name of the Vendor assigned to the transaction or master file. This is set in the Vendor Record View. This represents the name of the 'Vendor' on the 'Home' tab of the Invoice/Credit Memo Record View. This is only editable by changing the Vendor assigned to the transaction. Vendor Names are used as a long description for Vendors. Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK |