Create or Update OH Set - APOHBTUB

Use the Accounts Payable (AP) Create/Update OH Set (APOHBTUB) page to enter invoices for specific vendors that will be paid later. Using the AP Open Hold page, you will be able to create a Set of transactions or update existing Sets.

If you are using the automatic tax calculation process, the NU Common Codes NUUPCD, with a Category/Value of OHTX/TABLE1 should be defined so that the tax entries are created using the same Set ID as the invoices within the Set. This may or may not be a change in the way you process your Use Tax payments. If you do need to change this common code, your selection for payment process may need to change as well. Please review the option of this NU Common Code. You may want to use a separate division for Use Tax payments, a separate status (i.e., H0-H9 could be used as a "hold" status), etc.

Set

To create a new Set ID, select Add from the page menu, arrow down to the last line or click into the Set ID field on the last line. The Set ID and subsequent fields will be blank. You are now ready to create your new Set ID.  To update an existing un-posted Set, simply click on the Set ID. You can also use the arrow keys on your keyboard. Once you have selected your Set ID, you only need to click on the Invoice tab to begin updating. At this point, the User Set Total field can also be updated.

The following functions can be performed on the Set tab:

• Enter a new Set in the grid or single record view.

• View all un-posted, posted, and user-created sets by filtering by Status.

• View Set ID, system Set total, invoice count, record count, creator, Set status, create date, last update date and user.

• Select and edit an existing un-posted Set.

• Change the user total of an existing Set.

• Change the sort method display of Sets.

Set ID: Up to 16 characters which uniquely identifies a set of transactions. The set must begin with an alpha character and be free of special characters. Using Ctrl+T, or using the ellipsis button to the right of the field will generate an automatic Set ID, based upon NU Common Codes with a Category/Value of SYNO/BTCHIDOH.

User Set Total: The user-defined total of all transactions within the Set ID. This amount must match the total in the System Set Total in order to distribute the set if NU Common Codes with Category/Value of APBP/STOPDS is set to ON.

Set Type: A static system code that indicates the type of Set. This is a required field and defaults to OH (Open Hold).

Post State: Display-only field showing a two-character code that indicates the status of the Set. Upon Set creation, this field will be set to BE. When the Set is posted (to Open Hold or to the General Ledger), the status will then change to DS.

Create Date: Display-only field showing the date of creation.

By: The User ID of the person who created the Set.

Last Update Date: Display-only field showing the date of the last update.

By: The User ID of the person who last updated the Set.

Totals

Set Total: Display-only field indicates a system-generated total of the amounts entered, showing the running total of distribution amounts for the given Set ID.

Set Invoice Count: A display-only field showing the number of invoices within the set

Set Record Count: A display-only field showing the number of invoice detail lines within the set

Invoice

The Invoice tab page opens in single record view; the grid mode is available by pressing Ctrl+G. The Invoice tab page displays additional tabbed pages: Invoice Details (containing the Main page and the Misc page), Invoice Text, and Address.

You can perform the following functions with this page:

• View an invoice at the total level.

• See vendor ID, vendor name, invoice number, invoice date, system invoice total, and user invoice total.

• Edit vendor ID, invoice number, invoice date, and user invoice total.

• Use Find/Search command under the Find menu (or by pressing Ctrl+F), also known as QBE or Query by Example.

• Interactively lookup and select vendors.

• Interactively select vendor addresses.

• Interactively lookup and select GL and JL account numbers.

Set ID: It is a read-only field that will fetch the Set ID value from the Set tab.

Invoice: Up to 16 characters which identify the invoice. Using Ctrl+T, or the ellipsis button to the right of the field will generate an automatic invoice number, based upon NU Common Codes with a Category/Value of SYNO/OHREFxx.

Invoice Date: Enter the date of the invoice. Dates may be entered as MMDDYY, MM/DD/YY, MMDDCCYY, or MM/DD/CCYY. For example, May 3, 2013 may be entered as 050313, 05/03/13, 05032013, or 05/03/2013. The invoice date repeats on subsequent forms that relate to the same invoice.

Vendor ID: This field contains up to 12 characters that identify the vendor to which this transaction relates. Use the Lookup function to locate an existing vendor. The system will automatically bring up the page used to look up vendor information or create a new vendor (provided security has been granted for the user to create vendors). There is no Apply button for the Vendor ID lookup, data is filtered as the user types in the text. When adding a new vendor, the vendor ID may be entered or the system can assign a unique vendor ID. Many clients make use of alphanumeric vendor IDs, as they tend to be easier to remember. The system supports an unlimited number of addresses that may be associated with one vendor. For example, a software company may be assigned a vendor ID such as PowerSchool; with offices at different locations, these addresses would be associated with the vendor ID PowerSchool.

Addr Cd: Select the address code that will be used for the transaction. The Address Code is defined in NU Common Codes, with a Code Category /Value of PEAD/xx, where XX represents the Address type. 
Additionally, NU Common Codes with a Code Category/Value of APAH/ADDRESS, and the desired hierarchy in the Short Description, may be used to set an address hierarchy that determines the appropriate Address Code to assign at data entry time. For example, if the AP Address Code is to be listed first, the BL Address Code second, and the PO Address Code third, enter APBLPO in the Short Description. 

Security Code: A Security Code may be associated with the invoice. Most users will have their Security Code default automatically through managed security settings; this will trigger approvals as required for the Security Code entered. When required, the Security Code also determines what invoices the user can browse later. Users can be set up to have Read or Read/Write access to particular Security Codes. When creating an invoice, the user must have Write access for the Security Code used. To browse an invoice, the user must have Read or Write access to the Security Code. Additionally, if security codes are defined, a workflow model can be designed that will automatically create the required approvals for each invoice. The Security Code field is disabled in find mode.

User Invoice Total: Enter the amount of the invoice. This field is required if using Extraction. This amount must match the total in the System Invoice Total in order to distribute the set if NU Common Codes with Category/Value of APBP/STOPDS is set to ON.

System Total: This display-only field indicates system-generated totals of the amounts entered within the displayed invoice.

Extract

PO: Enter the Purchase Order Number (PO), up to eight characters, related to this Invoice. The system will verify that the PO is in either the Purchasing or the Encumbrance database. If the PO has not been entered into the system, leave this field blank. PO numbers should only be entered if the PO Extraction is to be used.

Partial: Indicate whether this is a "P" (partial) or "F" (full / final) payment of the Encumbered Purchase Order. The system will fully disencumber the given Purchase Order Number if an "F" is entered, regardless of the actual amount that has been paid. A "P" will tag the payment as partial. This type field updates both the status of the Purchase Order in the Purchasing subsystem and the encumbrance in the Encumbrance subsystem. Note: The AP General Information page has an Auto Full Pay check box. If this is checked and P is entered for partial, the software will automatically change the payment to "full / final payment" when the quantity paid is equal or greater than the quantity received and the quantity received is equal or greater than the quantity ordered.

Extract: Click the Extract button to extract the entries. Depending upon the Extraction Method selected on the AP General Information (APOHUPGN) page, one of two things will occur: if a W exists in the field, the system will place all PO Item transactions into the Set after pressing the Extract button. If a V, S, or O exists in the Extraction Method field, the Extraction Page is shown thus allowing the user the option to view and/or select some or all items to be placed in the Set. To run the PO extract as a job with a tail sheet, check the Run as Job box. 

An allowable "tolerance" percentage or amount may be set using common codes. Common code APPO/PAYTOTx is used to control over-payments. This code allows the system to check the Accounts Payable batch proofs and compare the dollar amount paid on an item to the dollar amount stated on the Purchase Order. The difference between the PO stated price and the total of the payments on an item must be less than that specified on the code. Similarly, common code APEN/PAYTOTx is used to control over payments of encumbered amounts on POs. If a Purchase Order Number is entered and the system finds no received items, a message is displayed. Pressing the Extract Button at this point will cause the system to retrieve all items that are held for the given Purchase Order from either the Purchasing database or the Encumbrance database. If only Received items are to be paid (i.e., the system should not pull in items from the PO), this must be set up in common code APUB/POPAID. 

Invoice Details

Main

Account: A general ledger (GL) account must be keyed into this field. If the Job Ledger (JL) module is used and this transaction relates to an account in the JL, enter a JL account number. Use the Lookup function to locate and select a ledger code or account part (key, object, etc.):

• XX Org Key-Object: Select this option or press Ctrl+K to display the account entry format as the ledger organization key and object code. Account numbers may be entered as fully qualified, organization key and object code as specified on GLUPGN, Miscellaneous tab.

• XX Quick: This option allows you to find an account using a quick key that you may have set up in the Quick Account Numbers GLUPQU page.

• Show Ledger: Selecting this option displays the ledger in the account string and allows you to identify a specific general ledger.

• Show JL Side: Selecting this option displays the JL ledger account string field and allows you to identify a specific job ledger.

• Show Work Order: Selecting this option displays the Work Order field for entry. The Work Order number must exist in the Work Order module, if the "Validate Work Order" box is checked on the Ledger Definition (GLUPGN) page.

Description: Enter up to 30 characters that describe this invoice line. This is typically entered as a description of the item being expensed. If the Description field is left blank, the system will enter the description of the Object Code used in the GL account.

PO#: If the PO was extracted into the Set, this field will be automatically populated. Otherwise, the PO# related to this invoice may be entered. The system will verify that the PO is in either the Purchasing or the Encumbrance database. If the PO has not been previously entered into the system, leave this field blank. Note that when an accounts payable transaction references a Purchase Order number and the PO has been marked as prior year encumbrance by the Roll End Balances To Next Year utility (ENUTRE), the accounts payable transaction may be created with a Miscellaneous Code of PYEN. This code will inform the posting process that the payment is for a prior year encumbrance and it will be dealt with in an appropriate manner. If the values placed into this field are to be validated, then they must be defined on the NU Common Codes page, with a Code Category/Value of OHMC/xxxx (up to four-character MISC code).

P/F: Indicate whether this is a "P" (partial) or "F" (full / final) payment of the Encumbered Purchase Order. The system will fully disencumber the given Purchase Order Number if an "F" is entered, regardless of the actual amount that has been paid. A "P" will tag the payment as partial. This type field updates both the status of the Purchase Order in the Purchasing subsystem and the encumbrance in the Encumbrance subsystem. Note: AP General Information (APOHUPGN) has an Auto Full Pay check box. If this is checked and P is entered for partial, the software will automatically change the payment to "full / final payment" when the quantity paid is equal or greater than the quantity received and the quantity received is equal or greater than the quantity ordered.

Quantity: This field contains the amount of units, such as 10.

Unit Price: This field contains a per unit price, such as 123.98.

Div: Up to four characters which identify the division to which the transaction relates. The division must have been previously defined on the Open Hold AP Division (APOHUPDV) page. Division Codes are used to logically divide the AP database into groups of transactions (sub ledgers). These groupings are useful for aged analysis, separate reporting needs, and many other important functions such as the manner in which the system is to automatically post entries to the general ledger. 

Misc: When transactions are entered into the Accounts Payable system, each transaction may have an optional Miscellaneous Code associated with it. Miscellaneous Codes are four-character codes that are used for a variety of purposes. For example, it may be helpful to put a Miscellaneous Code of HAZM on all A/P transactions that relate to the purchase of hazardous materials. These Miscellaneous Codes may be free form or they may be code validated. If they are to be free form (i.e. anything put in as a Miscellaneous Code is accepted by the system), then this must be indicated on the A/P General Information (APOHUPGN) page. If the system is to accept only Miscellaneous Codes that have been previously defined, this also must be indicated on the A/P General Information (APOHUPGN) page. Define Misc Codes on the NU Common Codes (NUUPCD) page, with a Code Category/Value of OHMC/xxxx (up to four-character MISC code). The Misc Code's description displays in the drop-down list; it is derived from the common code's Medium Desc field.

Tax Code/Amount 1 & 2: The "Tax Code" fields are used by the system to automatically calculate a Tax Amount, such as a Sales Tax. Codes available in the drop-down list of these fields are defined on the NU Common Codes page, with a Category of SYTX. When a code is entered in this field, the system locates this code in the NU Common Codes file and uses the first Associated Numeric Value as the percent to be multiplied times the Distribution amount to determine the tax amount. The Tax Code field is also used in the automatic creation of Use Tax entries within the Set. If desired, simply tab over the Tax Code field and key in the amount of the tax directly into the Amount field.

Second Ref: Up to 16 characters of additional information regarding the invoice. Ctrl+T or clicking the ellipsis button will allow the system to automatically assign a unique Secondary Reference Number. The NU Common Codes, with a Category/Value of SYNO/OHSREFNO needs to be set up for the system to provide Secondary Reference numbers.

Product ID: This field may contain a Product ID. The Product Code must be previously defined in the Product Information (PEUPPR) page prior to referencing. You may use Ctrl+L or the ellipsis button to look up Product Information or create a new product (provided security has been granted for the user to create new products). Information regarding Product Codes can be obtained from the Stores Inventory, Purchasing, and/or Person Entity User Guides.

Relate 1 & 2: Each transaction may have up to two, two-character, Relate To Codes that are used to specify the transaction's relationship to other systems. For example, if this is a Travel Advance, many clients will use an "AR" in the first Relate To Code so that the transaction will be tagged as an item to be set up in Accounts Receivable, where trip expenses are reconciled. These fields are also used to show that the transaction relates to 1099s. When flagging 1099-MISC transactions, the first Relate To Code field should be used, as this is the only one that will be stored in the Bank Reconciliation (BK) subsystem. Values available in this drop-down box are defined in the NU Common Codes, with a Code Category/Value of RT01/xx (i.e. AR for AR related transactions). For the second Relate To Code field, do the same thing with the exception of the Code Category being RT02. The system may be installed with certain Relate To Code values already defined. Do not delete these values. Most clients use Relate To Codes to indicate if a particular distribution amount is applicable for 1099-MISC reporting. This is done by inputting a code that "relates" the transaction to a particular box on the 1099-MISC form. In the first Relate To field, the most commonly used is "CC", "Non-Employee Compensation". A Vendor may be defined in the Person/Entity database with a "Y" in the 1099 field, which indicates that all the vendor's transactions will become 1099-MISC reportable transactions. If a Vendor is set up to receive a 1099-MISC and the distribution amount is not to be included, enter "EX" in the first Relate To Code field and the system will exclude this amount when preparing the Vendor's 1099-MISC.

Charge Code (and Amount): The Charge Cd part of these two fields is used to have the system automatically calculate a Charge Amt, such as a shipping charge. The amount of the standard charge to be paid is derived from NU Common Codes, with a Code Category of SYCH. When a code is entered into this field, the system locates this code in the NU Common Codes file and uses the first Associated Numeric Value as the percentage to be multiplied times the Distribution amount to determine the Charge amount. If desired, simply tab over the Charge Cd field and key in the amount of the Charge directly into the Amount field.

1099 Flag:  Display-only field, derived from the vendor setup of same value in PEUPPE.

1099 Dflt:  Display-only field, derived from the vendor setup of same value in PEUPPE.

Duty Code (and Amount): The Duty Code part of these two fields is used to have the system automatically calculates a Duty Amount, such as an Import Duty. The amount of the standard Duty to be paid is derived from NU Common Codes, with a Code Category of SYDU. When a code is entered into this field, the system locates this code in the NU Common Codes file and uses the first Associated Numeric Value as the percent to be multiplied times the Distribution amount to determine the Duty amount. If desired, simply tab over the Duty Code field and key in the amount of the Duty directly into the Amount field. 

Due Date: The date payment of this invoice is due. If left blank, the system will automatically use the Invoice Date. This date may be entered as per Invoice Date. The Due Date may be automatically derived from data stored on the Vendor in the PE Data. The system calculates the Due Date by adding the number in the DUE DAYS field (on the Person/Entity Information Update page, Vendor tab) to the Invoice Date, to derive the Due Date. Additionally, the Due Date can be calculated using the Received Date, instead of the Invoice Date field, when the NU Common Code with a Category/Value of APOH/SETDUEDT is activated.

Received Date: Enter the date the invoice was received from the vendor. 

Disc. Terms: The amount to markdown the invoice, which will be computed by the system. Discount terms are entered as number without the percentage sign, with or without a decimal. For example, entering 2.75 represents a 2.75% discount; or a 2% discount would be entered as 2. 
Other fields within this area of calculations, such as Tax or Duty, will be discounted per the setup defined for those codes. See common code SYTX/xxxx where xx defines a particular code for the given Category Code. Also see common codes SYDU/xxxx and SYCH/xxxx.

Discount:  The value is derived from the Discount Terms field.

Authorized Date: The purpose of this field is to record the date of the authorization for payment of this invoice. Validation of this date is optional. 

Discount Date: This field is used to display the date the invoice must be paid by in order to be eligible for a discount to be taken. The Discount Date field will be automatically populated based on optional Discount Flag and Discount Days settings from the vendor record, on the Person/Entity Information Update (PEUPPI or PEUPPE) page, Vendor tab, Miscellaneous section. The Discount Days field will be used to define the number of days from the Invoice Date that the invoice must be paid by in order for the discount to be allowed. This value is added to the Invoice Date and used to populate the new Discount Date field on the invoice line item records. For example, if the Discount Days field is set to 10 and the Invoice Date is 5/25/2013, the Discount Date field on the invoice would be set to 6/4/2013, which is 10 days after the Invoice Date. 

Bank ID: Select the code that identifies the bank account from which checks are written. Check stock codes are typically set up during system installation. Codes available in the list have are defined in NU Common Codes (NUUPCD), with a Code Category of CKID/xx.

Check No: This field is not populated for OH transactions. This field is only populated for RV and HW type transactions when using the Void, Typed & Reversed Check (APTRBTUB) page.

Extended Amount: This display-only field shows the total amount of the invoice, including tax, duty, discount, etc.

Vendor of Rec: This field contains up to 12 characters that identify the vendor to which this transaction relates. The vendor of record field is used when the actual vendor supplying the goods or services differs from the primary vendor being issued payment. This is useful in tracking vendors for the purpose of issuing tax documents when credit cards are used in procurement.  To look up an existing vendor of record or create a new vendor ID, you may use either Ctrl+L or the ellipsis button to the right of this field. The system will automatically bring up the page used to look up vendor information or create a new vendor (provided security has been granted for the user to create vendors). When adding a new vendor, the vendor ID may be entered or the system can assign a unique vendor ID. Many clients make use of alpha/numeric vendor IDs, as they tend to be easier to remember. The system supports an unlimited number of addresses that may be associated with one vendor. For example, a software company may be assigned a vendor ID such as PowerSchool; with offices at different locations, these addresses would be associated with the vendor ID PowerSchool. 

The field impacts 1099 reporting when the 1099 process is run from the Open Hold database only, in other words, BK99CC is run for OHDB.

Alt Address Code:  The address code derived based on the Vendor of Rec ID.  The code has similar functionality as the Vendor Address Code in that it follows the Address Hierarchy.

Misc

On the Misc tab, only the Transaction Format field is required. Included on this page are fields that may be used to track payments against contracts or bids.

Transaction Format: Select the static system code that directs the manner in which the description, as it would appear in the general ledger, is to be created by the system. The following describes each possible Transaction Format code and its meaning:

Vendor Account: If there is an open account with a Vendor and it is recorded in the corresponding field on the Purchase Requests (POUPPR or POUPPE) page, it will be extracted with the Purchase Order and displayed here. Otherwise, enter the number you wish to have recorded as the account number and it can be used to reference the transaction.

PR #: The Purchase Requisition Number associated with this transaction. If the entry was created through Extraction, the PR number was extracted from the Purchasing database or the Encumbrance database.

PR Item #: The requisition item number associated with this transaction. If the entry was created through the Batch method, the PR Item number was extracted from the Purchasing database or the Encumbrance database.

Refund Type: Select the code to identify the type of refund being made. Codes available in the list have been defined on the NU Common Codes page, with a Code Category of APRF.

Bid: If there is a Bid number associated with a Vendor and it is recorded in the analogous field on the Purchase Requests page, it will be extracted with the Purchase Order and displayed here. Otherwise, enter the number you wish to have recorded as the Bid number and it can be used to reference the transaction.

Former Bank ID: The former bank ID 

Former Check No: Former check number (i.e., the check this payment is replacing).

Contract: If there is a Contract associated with a Vendor and it is recorded in the corresponding field on the Purchase Requests page, it will be extracted with the Purchase Order and displayed here. Otherwise, enter the alpha/numeric code you wish to have recorded as the Contract and it can be used to reference the transaction.

Retail Amount: If paying other than the Retail Amount, the actual Retail Amount may be entered here for reference. Some clients, such as those operating a book store, like to put what they plan to charge for items at the Retail Level when they are purchasing their stock.

P-Card Ref: System generated reference number, based on setup in the SYNO/PCARDREF common code. It is generated by the Send to AP process.

Status: A system code that indicates the status of the transaction being held in the database. "DS" indicates that the transaction will be distributed but has not been paid. "WP" indicates that the transaction is awaiting payment. "PD" indicates that the transaction has already been paid. H0 through H9 may also be used to indicate an on-hold status. The purpose of the hold status is to allow users to mark these Open Hold entries as on-hold so they will not be selected for payment. These 10 codes can be used to group invoices based on "why" they are on hold. For example, H0 might mean that the vendor needs to be contacted; h2 may represent the Use Tax payments that are paid quarterly.

Misc Ref: P-Card holders' name.

Posting Code: This display-only field indicates the two-character Posting Code used to direct the automatic posting to the general ledger. The system will generate this code based upon the defined Posting Preference. Posting Preferences are typically set up by lead accountants during system installation.

Asset ID: The ID of the asset associated with this invoice.

Origination Source: System-generated, two character value, assigned during record creation to indicate from where the invoice record originated. Some examples are: FA - Asset Management, PC - P-Card, PY - Payroll.

Item Number: A display-only field showing the number of records in the batch. The user may want to clean up unwanted files that have a record size of 0 (zero).

Sep Check: By entering an alpha/numeric character in this field, the system will produce a separate check for this invoice. By leaving this field blank, the system will total all invoices for the same Person or Entity and issue one check. If more than two checks need to be cut, use another letter to distinguish the transaction. At check time, the system will match all blanks, all A's, all B's, and so forth, into separate checks. Up to two characters may be used to distinguish each check. This field is editable in the Edit mode.

In Person/Entity Information Update (PEUPPI or PEUPPE), if a vendor is defined with an association assignment of SEPCHECK, every transaction entered to that vendor through A/P Immediate Pay (APIPBTUB) or A/P Open Hold (APOHBTUB) will generate an individual (separate) check. For example, if there are 10 records for one invoice number in the Set, the vendor will receive 10 checks because this setup generates a separate check for each transaction in the Set. 

Setup - Two NU Common Codes need to be defined: 
1) Code Category/Value of PEAS/SEPCHECK – no required fields. 
2) Code Category/Value of SYNO/SEPCHECK with 03 right justified in Associated Code (1). For each vendor who is a "forced separate check" vendor, add a PE Association Assignment of SEPCHECK. This is done on the Person/Entity Information Update page, Assignment tab, by entering SEPCHECK in Code field. 

When inputting records to these "forced separate check vendors" through A/P Immediate Pay (APIPBTUB) or A/P Open Hold (APOHBTUB), the separate check field will be automatically populated based on a seed number. This will force individual checks per Set record at check printing time.
Note : Force a one-time check for a vendor set for EFT disbursements by adding "NE" to the Sep Check field. This feature requires the PEID to have "SEPCHECK" saved with the PE's profile on the PEUPPE page, Association tab. If SEPCHECK is not an option within the Code column's drop-down list (Associations tab), add common code PEAS/SEPCHECK. 

Delete Flag: This display-only field indicates the status of the record, either present or deleted.

Invoice Text

The Invoice Text tab page is for text that may be associated with an invoice for a vendor.

Address

The Address tab page displays the vendor address associated with the PE ID and address code chosen on the Invoice page.

Reversals

Fields on this tab are only used in the Void, Typed, and Reversed Checks Set (APTRBTUB) page. They are not used for Open Hold. Although the fields will accept data, clicking extract will not perform any action. In a future release, this tab will be grayed out for OH.

Bank ID: Select the code that identifies the bank account from which checks are written. Check stock codes are typically set up during system installation. Codes available in the list have been defined in common code CKID/xx.

Check No: Not populated for OH transactions. This field is only populated for RV type transactions when using the Void, Typed, and Reversed Checks Set page.

Set Total: This display only field indicates the total of the current Set.

Tools

Ledger Settings

Used to set user’s default ledgers.

Copy OH Set

Attachments

See Document Capture and AP Invoices for information on how to attach AP invoices.