Hi all, I’m looking for guidance on the best way to enforce an approval requirement for a subset of customers (we use class to identify these customers) before allowing any transactions to be created for them. Requirement: * Certain customers must be reviewed and approved by AR before they can be used on transactions (Sales Orders, Invoices, etc.) * Until approved, users should not be able to create or save transactions for those customers What I’m trying to figure out: * What’s the recommended approach in NetSuite for enforcing this type of control? * Would this typically be handled via (prefer easiest method):* Workflows * SuiteScript (User Event / Client) * Standard features I might be overlooking * Is there a way to prevent users from even selecting restricted customers on transactions, or is blocking at save the only practical option? * Are there any scalability or performance considerations depending on the approach? Goal: Implement a reliable and maintainable way to ensure AR approval happens before any transactional activity for specific customers. Would appreciate any patterns, examples, or best practices others have used. Thanks!

Hi @User_PCF01 Approach A: Standard Feature (Credit Hold) - No Customization Required NetSuite has a native Credit Hold feature designed exactly for AR to control transactional activity. * How it works: When a customer is created in this specific Class, their "Hold" field is set to ON. NetSuite's native accounting preferences (Setup > Accounting > Accounting Preferences > Customer Credit Limit Handling) can be set to Enforce Holds (blocks saving transactions). * The Process: AR reviews the customer. Once approved, AR sets the Hold to OFF or Auto. * Pros: 100% native. Handles blocking Sales Orders and Invoices automatically. * Cons: If you are already using Credit Hold strictly for credit limit breaches, mixing it with an "onboarding approval" process might confuse your AR team. Approach B: SuiteFlow (Workflow) If you want a dedicated "AR Approved" process without touching standard credit holds, a simple Workflow is the best no-code solution. * Setup: Create a custom checkbox on the Customer record called AR Approved (default: unchecked). * The Workflow: Create a Transaction Workflow applied to Sales Orders, Invoices, etc. * Trigger: Before Record Submit * Condition: Customer : AR Approved = F. * Action: Add a Return User Error action. Give it a clear message like: "Error: This customer has not been approved by Accounts Receivable. You cannot create transactions for them yet." * Pros: Very easy to build, maintain, and modify. Hard-blocks UI, CSV imports, and integrations.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Child Item

Ask A Guru

Child Item

Customer Approval (Block Transactions Until AR Approval)

User_PCF01

Hi all,

I’m looking for guidance on the best way to enforce an approval requirement for a subset of customers (we use class to identify these customers) before allowing any transactions to be created for them.

Requirement:

Certain customers must be reviewed and approved by AR before they can be used on transactions (Sales Orders, Invoices, etc.)
Until approved, users should not be able to create or save transactions for those customers

What I’m trying to figure out:

What’s the recommended approach in NetSuite for enforcing this type of control?
Would this typically be handled via (prefer easiest method):
- Workflows
- SuiteScript (User Event / Client)
- Standard features I might be overlooking
Is there a way to prevent users from even selecting restricted customers on transactions, or is blocking at save the only practical option?
Are there any scalability or performance considerations depending on the approach?

Goal:
Implement a reliable and maintainable way to ensure AR approval happens before any transactional activity for specific customers.

Would appreciate any patterns, examples, or best practices others have used.

Thanks!

Find more posts tagged with

suitebuilder!

#customize

Component react.asset.answerThread had an error.

You are not allowed to view comments.

Child Item

Upcoming Events

SuiteWorld | October 25–28, 2026 | Las Vegas
Big ideas. No travel required. SuiteWorld On Air brings the best of SuiteWorld directly to you. Stream keynotes live, access exclusive virtual content, and connect with the NetSuite community from wherever you are. Explore what's next for NetSuite, see AI innovation in action, and discover practical insights designed to…
Learning Lab | DC
Drive better outcomes with AI built into NetSuite Next Capital Hilton,1001 16th St NW, Washington, DC 20036 Join NetSuite experts for a free half-day event where you'll get a tour of NetSuite Next, explore AI-powered capabilities built into the platform, and learn practical ways to optimize NetSuite for your business. At…
Inside the Suite | DC
Take NetSuite Next for a hands-on test drive Capital Hilton, 1001 16th St NW, Washington, DC 20036 What to expect: Inside the Suite is designed for companies exploring modern ERP solutions. This event gives you the opportunity to experience NetSuite Next - the next evolution of NetSuite that brings AI directly into how…
What's Next for Product Companies with NetSuite
WEBINAR What's Next for Product Companies with NetSuite See how NetSuite Next uses AI to improve accuracy and protect margins Ask. Understand. Act. Use Ask Oracle to search, navigate, analyze business data, surface insights, get guidance, and take action using natural language—all through a single conversational…

More events