Used to select one or more Currencies, as configured in the Currencies master file.  This is a multi-select lookup that is not required to return results. It defaults to the value 'All'. 

Used to select one or more Fiscal Periods, as configured in the Fiscal Periods master file. This is a multi-select lookup that is not required to return results. It defaults to the value 'All'.

The lookup contains a list of all Fiscal Periods.

Fiscal Periods represent budgetary or accounting periods that fall within Fiscal Years. These often match the calendar where there are 12 periods, matching the calendar months. In organization where the fiscal year does not match the calendar year, Fiscal Periods may or may not match the number of days in a calendar month. Every transaction that posts to the general ledger contains a 'GL Date' and that date identifies both the Fiscal Year and Fiscal Period the transaction was posted to the general ledger in. 

Used to select one or more Fiscal Years. This is a text box to enter a GL Year to filter the data but is not required to return results. It defaults to the value 'All'.

The lookup contains a list of all Fiscal Years.

A Fiscal Year is a one-year period that companies use for financial reporting and budgeting. A Fiscal Year is most commonly used for accounting purposes to prepare financial statements. Fiscal Years often start on January 1st and end on December 31st. However, not all Fiscal Years correspond with the calendar year. For example, a company may run their Fiscal Year from May 1st - April 30th. Once a Fiscal Year has been determined, it is unlikely to ever change outside of a company sale and/or merger.

Used to select one or more Vendors. This is a multi-select standard lookup that is not required to return results. It defaults as blank.

A Vendor is a company or person that sells goods or services to your company. They are used in Purchasing and on Brokerage Sales Programs.

The lookup contains a list of all 'Active' Vendors. 

Opens the mass update dialog, which allows to mass update the following properties: 

• Pmt./Apply Hold: Used to place one or more transactions on a Payment Hold.

 Displays a drop down menu of related actions. The list of options includes:

• Journal Details - Opens the record view of the Journal Details. This only applies to Posted transactions. 
  
• Void Transaction - 
  Opens the Void Transaction page so users can void the selected transaction.

Re-queries the contents of the grid/page based on the Inquiry Criteria parameters or the default parameters for grids that do not support Inquiry Criteria. 

Identifies the Currency assigned to the transaction. This is required 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

Identifies the Discount Date of the transaction. This is required on transactions with a 'Payment Terms' that contain a Discount. For Payment Terms that do not include a discount it is blank and disabled.

This is always editable from the Transaction Record View 'Properties' tab, even after the transaction is Posted and can be edited to any date that is both:

1. Greater than or equal to the 'Doc Date'
   1. If not, the message "The Discount Date must occur on or after the Doc Date." will be displayed on Save.
2. Less than or equal to the 'Due Date' 
   1. If not, the message "The Discount Date must occur on or before the Due Date." will be displayed on Save.

 Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. 

 Note: Changing this for a posted transaction will only have an effect if the transaction has an open/unapplied balance. 

This is only applicable to AP Invoice and Credit Memo transaction types. 

The Discount Date represents the last date that Payment Term Discounts apply. 

Database Field: ERPx_APTransactionHeader.DiscountDate

Identifies the date of the transaction. This is required and is editable from the AP Transaction Record View while the transaction is in a status of New, or before a payment batch is posted for Check/ACH payments. 

Database Field: ERPx_APTransactionHeader.TransactionDate

Identifies the header comment/description of the transaction or batch. This is not required and is always editable from the 'Comment' field on the 'Home' tab of the Transaction Record View, even after the transaction is posted.  This is only applicable to AP Invoice and Credit Memo transaction types. 

For transactions auto-generated from a Grower Ticket, this defaults to the value 'Created from Grower Ticket'. 

Database Field: ERPx_APTransactionHeader.Description

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 can be edited from the 'Doc No' on the 'Home' tab of the Transaction Record View and represents the transaction/Invoice # assigned by your Vendor. This is always editable while the transaction is in a Status of New. This is only applicable to AP Invoice and Credit Memo transaction types.

Database Field: ERPx_APTransactionHeader.DocNumber

Identifies the Due Date of the transaction.  This is required and is always editable from the Transaction Record View 'Properties' tab, even after the transaction is Posted and can be edited to any date that is both:

1. Greater than or equal to the 'Doc Date'
   1. If not, the message "The Due Date must occur on or after the Doc Date." will be displayed on Save.
2. Greater than or equal to the 'Discount Date' 
   1. If not, the message "The Due Date must occur on or after the Discount Date." will be displayed on Save.

 Note: If the transaction's 'Payment Terms' are changed, this value will be recalculated. 

 Note: Changing this for a posted transaction will only have an effect if the transaction has an open/unapplied balance. 

This is only applicable to AP Invoice and Credit Memo transaction types. 

The Due Date represents the date the transaction must be paid by.

Database Field: ERPx_APTransactionHeader.DueDate

Identifies the date the transaction posted (or will post) to the general ledger.  This is required and is always editable while the transaction is in a Status of New, or before a payment batch is posted for Check/ACH payments (using the Payment Date field).

Database Field: ERPx_APTransactionHeader.GLDate

Identifies the Fiscal Period based on the GL date on the source transaction or manual journal entry. This is required and calculated using the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View or the 'Payment Date' on a check/ACH payment. This can only be edited by changing the GL Date.

Identifies the Fiscal Year based on the GL date on the source transaction or manual journal entry. This is required and calculated using the 'GL Date' on the 'Properties' tab of the Invoice/Credit Memo Record View or the 'Payment Date' on a check/ACH payment. This can only be edited by changing the GL Date.

Displays the total amount of the transaction. This is required and can only be edited by changing the Quantity and/or Price of the transaction line item on an Invoice/Credit Memo while the transaction is in a status of New, or the Payment Amount on a check/ACH payment before the payment batch is posted.

Database Field: ERPx_APTransactionHeader.ExtendedAmount

Identifies the Payment Terms assigned to the transaction. This can be edited from the 'Payment Terms' on the 'Properties' tab of the Invoice/Credit Memo Record View. This  is always editable while the transaction is in a Status of New.  This is only applicable to AP Invoice and Credit Memo transaction types.

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, APTransactionHeader.PaymentTermSK

Identifies the Purchase Order number (PO number) entered for the transaction or transaction line item. This can be edited 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 is always editable while the transaction is in a Status of New.  This is only appliable to AP Invoice and Credit Memo transaction types. 

Database Field: ERPx_APTransactionHeader.PurchaseOrderID

Identifies the Status of the transaction. For Invoice/Credit Memo transaction types, this can be edited from the 'Status' on the 'Home' tab of the Record View. This is always editable while the transaction is in a Status of 'New' or 'Approved'.  There is no 'Status' field on Check/ACH payment records but is considered 'Posted' when the payment batch is posted.  Unposted payments and transactions will display the status of 'Open'.

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 transaction in this Inquiry include:

Open: This is the default Status for all new records. While in the Status of 'Open', all editable fields are open for edit.

Posted: Signifies the transaction has been posted and/or applied to a transactions (e.g. Payment Receipt). When a transaction is posted, it updates the General Ledger and/or On Hand Item Balances. While in the Status of 'Posted' transactions are considered closed and all the fields are disabled with the exception of a few fields that are always editable.

Void: Signifies a previously posted transaction has been voided. This status is only available for transactions that support voiding posted records (not all transactions support this). Voided transactions remain in the database and can be viewed from history inquiries.

Replaced: Signifies the transaction was voided or corrected. When a transaction is corrected or Voided, the Status of the original transaction is changed to 'Replaced' and a new transaction is cloned and marked as 'Void'. This is done to ensure that a reversal journal entry can be created and posted in an open fiscal period to record the Void.

Database Fields: ERPx_APTransactionStatus.StatusName, ERPx_APTransactionHeader.TransactionStatusSK

Identifies the unique Transaction ID for each transaction. Clicking on this link opens the Record View for the selected record. This is a system assigned number that comes from the 'Transaction Class' Next Doc Number or the Checkbook Next Check # or Next ACH #.

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

Identifies the ID of the Vendor account that is assigned to the transaction. This is required and represents the ID of the 'Vendor' on the transaction. 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

Identifies the name of the Vendor assigned to the transaction or master file. This is set in the Vendor Record View.  This is required and represents the name of the 'Vendor' on the transaction. This is only editable by changing the Vendor assigned to the transaction, or updating the Vendor Name on the Vendor Record View.

Vendor Names are used as a long description for Vendors.

Database Fields: ERPx_APVendor.VendorName, ERPx_APTransactionHeader.VendorSK