SuiteApprovals Terminology

The following terms are used when referring to SuiteApprovals:

Approval Routing – Approval routing provides a measure of oversight to persons of authority who can choose to reject some transactions if they do not want them to continue being processed.

For more information, see Approval Routing.
Approver Gatekeeper – An approver who reviews and controls all approver replies through the email approval log.
Approver Type – A type of approval the user can perform.

Approver Types do not include record approvers, such as Journal Entry Approver, Expense Approver, Sales Order Approver, Vendor Bill Approver, or Purchase Approver.

For more information, see Setting Employee Approval Information.
Project Approver – The role assigned to project managers in project-based approvals. With this role, you can approve expense reports, purchase orders, and vendor bills that are linked to projects.

A project approver is considered as a valid approver based on the following criteria.
- An active employee
- Has login access
- Has access to the subsidiary of the transaction for approval
Record Type – A record used to collect and store information. In SuiteApprovals, the following record types are supported:
- Journal Entries – This transaction changes the balance in a ledger account does so by posting a journal entry. Transactions that post to ledger accounts are called posting transactions. Journal entry transactions are not posted until they are approved.
  
  For more information, see Journal Entries.
- Engineering Change Order – This feature is provided by the Supply Chain Management SuiteApp. You can generate engineering change order (ECO) records to document changes to your Bills of Materials (BOMs) and authorize the implementation of those changes using the SuiteApprovals workflow.
  
  For more information, see Engineering Change Order.
- Expense Reports – An expense report transaction records an employee’s expenses for approval and conversion into a bill. The expense total remains in an unapproved expense account and has no accounting impact until the expense is approved by someone with accounting authority. After the expense report is approved, a bill is created, and the expense amount is reflected in the books. For more information, read Expense Reporting.
- Requisitions – When an employee needs something that must be purchased using company funds, they can use a requisition to initiate the purchasing process. The requester specifies which items, services, or expenses they need a buyer to purchase. Buyers can then use requisitions to create the purchase orders necessary to fulfill the requisition requests.
  
  For more information, see Requisitions.
- Purchase Orders (PO) – This transaction authorize vendors to provide items, materials, or services to your company. When you enter purchase orders, you can track pending and received items.
  
  For more information, see Purchase Order Management.
- Purchase Order Approval Workflow – The Purchase Order Approval Workflow SuiteApp combines the features of the standard NetSuite approval routing and the flexibility of the NetSuite workflow manager.
  
  For more information, see Purchase Order Approval Workflow SuiteApp.
- Vendor Bills – Track your payables by entering bills as they arrive from vendors and pay them from the payables list when they are due. For more information, see Vendor Bills.
  
  You can require approval for vendor bill processing and enforce approval processes in two ways: using Standard Vendor Bill Approval and using SuiteFlow. For more information, see Vendor Bill Approvals.
- Sales Orders – A sales order is a transaction that records a commitment to sell items or services to a customer. Sales orders have no accounting impact until items are shipped or services are completed.
  
  For more information, see Sales Orders.

Related Topics