Purchase Order Approval Workflow

Description

The goal of this project is to create a NetSuite Purchase Approval Workflow. The workflow should have treat require approval based on the employee’s signing Authority level (three levels) and the type of purchase. Purchases fall into three categories, Inventory, Non-Inventory – Budgeted, Non-Inventory – Non-Budgeted. Users should be able to review POs before they are submitted for approval and before for them are approved. Approved POs should be locked for editing. Rejected POs can be modified and resubmitted.

Fields added to PO record:
Inventory Type, Approvers. (User should select a value: otherwise the only administrator can approve the purchase order)

Approvers fields added to:
1. Inventory : Subsidiary Record
2. Non-inventory Budgeted and Non-inventory non- budgeted : Department Record

Workflow

Name: SUIT-1 JJ SUITSCIENCE PO Approval
Internal Id: 112(in training account)
Applied to: Purchase order
Remarks: Create After Submit

Bundle

Name: JJ SUIT- 1 Suitescience PO Approval
Internal Id: 228740
Bundle Description
Purchase Order Approval Workflow Subsidiary record should have the Approvers for the inventory. Department should have the Approvers for the non-inventory.
Note : Administrator will have always the provision to approve PO. For other people other than Approvers and Administrator roles purchase order will be locked after submitted it for approval. Fields added to PO record:
Inventory Type(user should select a value: otherwise only administrator can approve the purchase order).

Summary

Inventory
Dependency:
The approvers (level 1, level 2, level 3) are added to the subsidiary record.

Non- Inventory budgeted and Non- Inventory non-budgeted
Dependency:
The approvers (level 1, level 2, level 3) are added to the department record.

User should do

  1. The user should select an inventory type.
  2. Submit PO for approval
    When the user submit the purchase order for approve using the button, the workflow will send emails to the approvers which are added to the subsidiary record and the purchase order will be locked.
    The email will send according to the approval level. For example
    <=5k
    Email to level 3, level 2 and level 1
    >5k<=100k
    Email to level 2 and level 1
    >100k
    Email to level 1

3. When an approver takes the purchase order the ‘approve’ and  ‘reject’ buttons will add to the purchase order.
When the purchase order approved an email will be sent to the creator of the purchase order and approved field will change to the status ‘approved’
When the purchase order rjected an email will be sent to the creator of the purchase order and he can edit the purchase order and again submit the purchase order for approval.


Leave a comment

Your email address will not be published. Required fields are marked *