Celigo Square Integration App
Back to products
RingCentral for NetSuite

Yantra Master Controller

Status: Unverified

Multiple people with access rights to create masters may lead to duplicate records. For example, there are two custom records with slight change in the name and these records were created by two different sales people. This might further add confusion while creating Estimate or Sales Order etc. This product is designed to control master record creation. With the help of central approving authority, this product will help user to avoid duplicate masters. Approving authority will be responsible to verify the master record for duplication as well as for the data like CoA, Shipping/Billing Address etc. Up on submitting master record for approval, Approver will receive email notification. Approval can be done through email only.

View on Suiteapp.com

Categories: , ,
Description

Control your master records.

This SuiteApp is designed to control master creating by adding a approval workflow.Setup record helps user to configure the SuiteApp.
Master record will remain inactive until it is approved by defined approver.

Key Benefits

Avoid duplicate master records.
Add approval workflow on master creation.
Approver, before approving record, can check all the details added on master record.
Upon rejection, user can ask for more details or update existing fields.

Two step validation of master data

Creator can enter all the master data/fields and verify before submitting it for approval.
Approver can verify all the details like Vendor’s shipping address, customer’s billing address, CoA configured on Item record etc.
One level approval will help to avoid human errors.

FEATURES

Create and Submit master record for approval

Create master record with all required and important data.
Submit the master record for approval.
Master record will remain inactiv until record is approved.

Approval of master record.

Approver can be defined during setup of the SuiteApp.
Approver can verify all the fields on the master record as well as for the duplicate master records.
Once approved, master record will become active and will be available for use.

Rejection of master record.

During verification of the master record approver is expected to verify the data as well as to check for the duplication of master record. Approver can reject by specifying the 'Reason for Rejection'.
Upon Rejection, user will have to submit reason for rejection which will further be captured on master record and will also be notified to creator.