NUFinancials Purchasing Glossary
Guide to terms used in iBuyNU and NUFinancials purchasing
Term |
Definition |
||||||
Account |
An account is a ChartField segment in NUFinancials that identifies the specific type of asset, liability, equity, revenue, or expense in each transaction. For example, accounts receivable, faculty salary, office supplies. |
||||||
Approver |
A role in workflow that is granted to users. This role is determined by schools/departments. Depending on the transaction type, commodity, chart string and/or dollar amount, some financial transactions are also subject to approval by Approvers in central offices such as PPS, ASRSP, and Research Safety. The Approver role is configured by the NUFinancials system administrator. The responsibilities of the Approver role are: □ Evaluate financial transactions for : □ Compliance with NU financial policies □ Completeness □ Accuracy □ Approve, send back, or hold financial transactions (Approver cannot modify transactions) □ Manage workflow in a timely fashion to leverage benefits of automated processing (e.g., requisition to PO on same day now possible) Approvers are notified via email when a transaction is awaiting their approval. Approvers retrieve transactions awaiting their approval from a workflow inbox on the NU Portal. See also: Workf/ow |
||||||
Aquiire |
The software that is used to power the iBuyNU Marketplace. |
||||||
Assignee |
Requester in the Shopper's school/department to whom the Shopper assigns their iBuyNU shopping cart. |
||||||
Auto-source |
In NUFinancials, Purchase Order Sourcing is an automatic process that turns a requisition into a purchase order. Sourcing runs without the need of user interaction and occurs on a regular schedule. If a requisition has been fully approved and is in a valid budget status, it qualifies to be sourced into a purchase order. For multi line requisitions that contain items from multiple suppliers (which is very common for requisitions that originate from iBuyNU), auto-source splits a single requisition into multiple POs for the appropriate suppliers.
|
||||||
Batch process |
Batch processing is the execution of programs or jobs on a computer without human interaction. Batch jobs are scheduled to run to completion without human interaction, usually at a time of nonpeak usage such as overnight. This is in contrast to online or interactive programs which prompt the user for input or automatic processes which are executed in real time without the need for user interaction. |
||||||
BD (Bid Summary Form) |
Purchasing Policy and Procedure at Northwestern University requires that competitive bidding be conducted for purchases of $25,000 or more (it is recommended for purchases of $5,000 or more). The Bid Documentation Form (BD-1) is to be used by departments and schools to document how an award decision is made whenever a competitive solicitation is performed. It must be attached to the requisition so it can be approved by all approvers. |
||||||
Bid Documentation |
See BD (Bid Summary Form) |
||||||
Blanket |
Blanket orders are to be used primarily to make payments for the regular delivery of a consistent quantity of products or for services that are provided on a regular and consistent basis. Specific examples include:
The underlying theme behind most appropriate blanket orders is that there is a contract/agreement in place, reviewed and approved by Procurement and Payment Services (PPS) and/or Office of General Council (OGC), or an established template was used. Blanket orders are not to be used as an open line of credit or to facilitate the use of phone orders (open account with no detail regarding each individual transaction). Blankets orders should also not be used to manage your budget. Blanket orders will be sent to the supplier, so they know the Purchase Order (PO) number to include on all invoices. ALL blanket purchase order requests will be reviewed and must be approved by PPS, regardless of value. All changes to blanket orders will be processed by PPS. |
||||||
Budget check |
Process of checking a transaction against a specified chart string or budget. When a transaction exceeds the available budget amount, the system either stops the transaction and issues an error notice or passes the transaction with a warning notice, depending on the processing rules specified by NU regarding control budget definition, budget attributes, and source transaction type definition. See also: Commitment Control |
||||||
CA (Cash Advance) |
Cash Advance used to request a check or direct deposit for travel or research. |
||||||
Catalog requisition |
A requisition that is initiated for items that are selected from suppliers included in the iBuyNU Marketplace (web-based ordering experience). |
||||||
Dept ID |
A ChartField segment in NUFinancials that identifies the lowest level at NU where you manage staff and/or control, secure, or report on budget/activity perf ormance. Dept IDs are not the same as Depart ment , which reflect NU's organizational structure. For appropriated funds: Dept ID is the lowest level at NU where staffs and/or budgets are managed, controlled, and reported on. For non-appropriated funds: a more general Dept ID value can be used to link the entire department's various Grants, Construction, Endowment, Gifts, Designate/Discretionary Projects, Student Loans, and Agency activity as the Project value or Fund/Project value will be the lowest level. |
||||||
Direct Payment Request |
The Direct Payment Request process is a way to request a check to pay for something when the transaction does not warrant the issuance of an official purchase order to a supplier. Specific examples include :
The Direct Payment Request process cannot be used to pay invoices for the purchase of products that should have been ordered using a Purchase Order. The Direct Payment Request (DPR) Form shall be completed and submitted to Accounts Payable. |
||||||
Dispatch |
Each supplier's profile will include how they wish to receive purchase orders. Suppliers may select Fax, mail, or e-mail. Purchase orders that are issued via fax will be sent through the University's fax server (which is automated, with no manual intervention required). Orders to suppliers included in the iBuyNU Marketplace will be sent through the Marketplace either electronically (CXML) or by fax server. |
||||||
Encumbrance |
Funds that have been reserved when a purchase order is processed. Encumbered funds are no longer available for use in other tran sactions , but also have not been included in the Actual Funds balance because a payment has not yet been generated and the funds have not physically left the account. The purpose of creating an encumbrance is to avoid budget overspending.
See also: Commitment Control |
||||||
Fax server |
Method of dispatching purchase orders directly from NUFinancials to a supplier's fax machine without need for manual intervention. Dependent on the supplier's ability to receive purchase orders via this method. |
||||||
Fund |
A ChartField segment in NUFinancials that is a 3-digit indicator of source of funds (e.g., federal grant, unrestricted gift, endowment income) |
||||||
General Ledger (GL) |
Accounting module in NUFinancials that serves as the core of the financial management system. The General Ledger module is where budget journal entries are created and maintained. Various modules such as Purchasing, Expenses, and Accounts Payable feed into and receive data from the GL module. |
||||||
Hosted Catalog |
A catalog that is established by Procurement and Payment Services (PPS) on behalf of a preferred supplier that is included in the iBuyNU Marketplace. All item detail is sent to PPS in spreadsheet format that is then turned into a catalog that is placed in the Marketplace. Features of a hosted catalog include:
|
||||||
iBuyNU Marketplace |
The iBuyNU Marketplace is a tool that provides departments and schools with the most streamlined, cost effective way to order from preferred suppliers. It provides end users with a web-based ordering experience. Departments and schools will be shopping on, in many cases, the supplier's actual web site configured for NU. Orders can be dispatched electronically and invoices can also be received by Accounts Payable electronically. The iBuyNU Marketplace is strategically managed by Procurement and Payment Services (PPS) and there are many factors that go into determining whether a particular supplier is enabled. Only preferred suppliers, where PPS has established a formal contract or agreement with on behalf of the University, will be considered for enablement in iBuyNU. |
||||||
KK |
See: Commitment Control |
||||||
Manage Requisitions |
Page in NUFinancials that is unique for each requester to provide them with a means to appropriately track all of their procurement transactions. |
||||||
Marketplace |
See: iBuyNU Marketplace |
||||||
Matching |
Matching is an automatic process that compares Vouchers with Purchase Orders and Receipts to ensure the timely payment of goods and services ordered and received. Matching occurs at the line item level. The system performs the following types of matches: 2-way match
3-way match
If matching is successful and within tolerance levels: System sets status of voucher to Matched and voucher is available for payment in the next voucher posting process. Once voucher is paid, payment is posted and purchase order status is Complete (similar to Closed in CUFS). If matching is not successful or is not within tolerance levels: System flags exceptions. Match exceptions are work flowed to Accounts Payable for resolution. If a match exception is due to a missing Receipt, the Requester is notified via email that a Receipt needs to be created. See also: Tolerance |
||||||
Non-catalog requisition |
A requisition that is initiated for items from suppliers who are NOT included in the iBuyNU Marketplace (manual entry). |
||||||
Northwestern Corporate Card |
The Corporate Card is a very important component of the procurement environment here at NU. It is to be used primarily for purchases less than $500 when the items needed cannot be purchased from a preferred supplier in iBuyNU and when the purchase is low risk (the transaction doesn't warrant the issuance of an official purchase order to a supplier). Specific examples include:
Please note that individual limits can be set by each department or school for each of their Corporate Card holders (both an amount per transaction limit as well as a monthly total limit). Contact Financial Operations for more information about obtaining a Corporate Card. The Corporate Card may be used in lieu of petty cash. Not to be used for travel. |
||||||
NUFinancials |
Oracle-owned enterprise management software selected by NU for financials, including Chart of Accounts, General Ledger, Post-Award Grants, and Supply Chain (purchasing and accounts payable). PeopleSoft is also used by NU for HRIS (Human Resources) and SES (Student). |
||||||
Payment Request |
Module in NUFinancials used for the prescribed policy uses of the Direct Payment Request, Visitor's Expense Report, and the Contracted Services Form for U.S. Residents. |
||||||
Pre-encumbrance |
Funds that have been reserved pending approval when a requisition is budget checked and submitted.
See also: Commitment Control |
||||||
Preferred supplier |
Preferred Supplier relationships at Northwestern are established one of two ways:
Departments and schools are strongly encouraged to utilize Preferred Suppliers for the following reasons:
A list of Preferred Suppliers is maintained on the PPS website. |
||||||
PPS |
Procurement and Payment Services, which is the single point of contact at NU for all central procurement activities. |
||||||
Punchin Catalog |
A punchout catalog with similar features of a hosted catalog. Features of a hosted catalog include:
|
||||||
Punchout |
For many suppliers included in the iBuyNU Marketplace, Procurement and Payment Services (PPS) has decided that it is more advantageous to allow departments and schools to connect to a supplier's actual web site catalog that has been configured specifically to NU's contract (products available, pricing, etc.). Orders to suppliers that are included in the iBuyNU Marketplace using a punchout strategy will generally receive their orders electronically. Features of a punchout include:
|
||||||
Purchase Order |
Once a requisition is successfully budget checked, submitted, and approved, a purchase order is generated and sent to the supplier and reflects specifically what is being ordered. Purchase orders are automatically issued and dispatched multiple times per day. A purchase order number is system-generated and begins with PUR. Suppliers must have a PUR number before delivery of goods or services can occur. |
||||||
Purchasing Decision Documentation Form (PDD) |
The Purchasing Decision Documentation Form must be completed for purchases $25,000 or more and attached to your Requisition. When completing the form, you will be asked a series of questions that must be answered regarding the type of purchase and process used for making your supplier selection. Once you have completed answering the questions, a Bid Summary or Sole Source Justification Form will be created based on your answers.
|
||||||
Requester |
A role in NUFinancials that is available to users as determined by the school/department and configured by the NUFinancials system administrator. The functions of the Requester role are :
|
||||||
Requisition |
A purchase request subject to approval based on NU workflow rules. Creating a requisition is the first step in the procurement process. A requisition is created and submitted by a Requester. When submitted, a requisition ID number (i.e., unique identifier) is generated by the system; requisition ID numbers begin with REQ. Once approved, a requisition becomes a purchase order (PO) and a purchase order ID number (i.e., unique identifier) is generated by the system. PO ID numbers begin with PUR. A REQ number cannot be used in lieu of a PUR number for purchasing. There are 2 types of requisitions: catalog (items found in iBuyNU) and non-catalog (items not found in iBuyNU). |
||||||
Requisition Type |
Non-Catalog (ONL), Blanket (BLK), Receive by dollar amount (SRV), Hold From Further Processing (HLD), Grant Subcontract (SUB) |
||||||
Shopper |
A role in iBuyNU for those that do not have security as a Requester. It allows anyone with the Shopper role access to enjoy a web-based ordering experience from preferred suppliers. The functions of the Shopper role are:
|
||||||
Sourcing workbench |
Used by Procurement and Payment Services to troubleshoot requisitions that may fail to auto-source. Also used to review and update sourcing information or correct errors that may result from the sourcing process. |
||||||
SSJ (Sole Source Justification Form) |
This process can only be used if a single supplier is uniquely qualified to meet the department/school's procurement objective. To be considered a sole source and therefore exempt from the bid process, one of the following conditions must be met:
The Sole Source Justification Form (SSJ-1) must be completed, submitted, and approved prior to the purchase order being issued. |
||||||
Tolerance |
Tolerance is specified to allow for an acceptable and reasonable price difference between the ordered price and the price on the invoice. For example, the price on the purchase order (PO) and invoice can vary by the designated tolerance amount or percentage and still be approved for payment. Tolerance is used in matching, an automatic process that compares Vouchers with Purchase Orders and Receipts to ensure the timely payment of goods and services ordered and received. Matching occurs at the line item level. NU has applied the following percentage and amount tolerances at this time:
See also: Matching |
||||||
Voucher |
In NUFinancials, vouchers are internal documents created when an invoice is received in Accounts Payable. Vouchers are created to record supplier invoice data and accounting information and to initiate supplier payments. |
||||||
Workflow |
Workflow is the process of routing transactions for approval before a purchase order can be issued or payment made. Workflow is triggered when a requisition or expense reimbursement request has been entered, saved, and submitted for approval. The approval path will ultimately depend on the transaction's dollar amount, chart string, and commodity type. Types of approvals are:
See also: Approver |
||||||
Workflow inbox |
Page in NUFinancials that is unique for each approver and includes only items that require their approval. |