SuiteApprovals Terminology
The following terms are used when referring to SuiteApprovals:
-
Approval Routing – Approval routing gives people in charge the ability to reject transactions if they don't want them to go through. For more information, see Approval Routing.
-
Approver Gatekeeper – An approver who reviews and manages all approval replies through the email approval log.
-
Approver Type – A type of approval a user can do.
Approver types don't include the following record approvers:
-
Journal Entry Approver
-
Expense Approver
-
Sales Order Approver
-
Vendor Bill Approver
-
Purchase Approver
For more information, see Setting Employee Approval Information.
-
-
Project Approver – This role is for project managers in project-based approvals, and it lets you approve expense reports, purchase orders, and vendor bills 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
-
-
Purchase Order Approval Workflow – The Purchase Order Approval Workflow SuiteApp combines the standard NetSuite approval routing and the flexibility of the NetSuite workflow manager. For more information, see Purchase Order Approval Workflow SuiteApp.
-
Record Type – A record used to collect and store information. In SuiteApprovals, the following record types are supported:
-
Journal Entries – This transaction changes a ledger account balance by posting a journal entry. Transactions that post to ledger accounts are called posting transactions, and journal entries are not posted until they're approved. For more information, see Journal Entries.
-
Engineering Change Order – This feature comes from the Supply Chain Management SuiteApp. You can create Engineering Change Order (ECO) records to document changes to your Bills of Materials (BOMs) and approve those changes using the SuiteApprovals workflow. For more information, see Engineering Change Order.
-
Expense Reports – This record tracks an employee's expenses for approval and converts them into a bill. The expense total remains in an unapproved expense account and doesn't have accounting impact until someone with accounting authority approves the expense. After the expense report is approved, a bill is created and the expense is reflected in the books. For more information, read Expense Reporting.
-
Requisitions – This record starts the requisition process when an employee needs to buy something with company funds. The requester lists the items, services, or expenses they need a buyer to purchase, and buyers use those requisitions to create the purchase orders. For more information, see Requisitions.
-
Purchase Orders (PO) – This transaction authorizes 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.
-
Vendor Bills – This transaction lets you track your payables by entering bills from vendors, and paying them from the payables list when they're due. For more information, see Vendor Bills.
You can require approval for vendor bills and enforce approval in two ways: using Standard Vendor Bill Approval or SuiteFlow. For more information, see Vendor Bill Approvals.
-
Sales Orders – This transaction records your commitment to sell items or services to a customer. Sales orders have no accounting impact until you ship the items or finish the services. For more information, see Sales Orders.
-
Related Topics
- SuiteApprovals SuiteApp
- Prerequisites for SuiteApprovals
- Installing the SuiteApprovals SuiteApp
- Setting Up SuiteApprovals
- Defining Approval Rules
- SuiteApprovals Approval Workflow States
- SuiteApprovals Portlets
- Tracking Email Notifications for SuiteApprovals
- Automatic Approvals
- Project-Based Approvals
- Managing Approvals with SuiteApprovals
- Email Approvals