For NetSuite admins
The requests in your queue, done by the book, approved by you.
Each request is described in plain words, the way finance or operations would put it. SeamSet checks what NetSuite already does and builds only what is missing: a first version in minutes, tested before it goes live. Nothing goes live until you approve it.
A saved search someone wants emailed every Monday. POs approved by email. A CSV reworked by hand before every import. Each one sits behind the close, the role requests and whatever broke this morning. Nobody is slow. There are more requests than hours.
Meanwhile the work happens in spreadsheets and inboxes, even when part of it is within reach in NetSuite. The cost shows up elsewhere: a slower close, cash collected later, decisions made on stale numbers.
Email the overdue invoices search to collections every Monday.
Native, set upPOs over the limit approved in NetSuite, not by email.
Native, set upCheck the journal CSV balances before it loads, and show why not.
Native plus a small scriptStock free to sell at each location, on a tablet at the dock.
New script or app
Requests arrive with your questions answered.
SeamSet asks requesters the questions you would ask: which records, which subsidiaries, who sees it, what happens on an exception. It restates the need in plain words for the requester and you to check, and flags gaps and conflicts with what is already in your account, before anything is built.
Native first, with pragmatism.
Before building anything, SeamSet checks what NetSuite already does: saved searches, workflows, approval routing, the CSV Import Assistant. Each request gets one of three answers:
Native covers it.
SeamSet sets it up (a saved search, a workflow, an approval rule), through the same approval, and writes no code.
Native covers part of it.
SeamSet uses that part and builds only the rest.
Nothing native fits.
SeamSet builds it: a script or an app.
If the native route would cost more to set up and run than the need is worth, SeamSet says so and proposes the lighter option. Account features stay your switch.
Request
"a weekly list of overdue invoices for the collections team"
: Covered natively: a scheduled saved search emails the overdue list.
: Not in this account yet: a worklist for the collectors.
Building only that.
Done by the book. Check every point.
"The right way" is a list any NetSuite developer can check in your account.
SuiteScript 2.1 in SDF projects. No script edits NetSuite's pages directly, which Oracle's development guidelines rule out.
Tested before it goes live. Every change, small ones included.
You decide the access. You connect SeamSet to your account and decide what it can access.
Within NetSuite's governance limits.
Prefixed and linked. A SeamSet prefix in every object ID, linked to its request, so the next person in the account can tell what SeamSet added.
Documented. Each change comes with its documentation.
Collections worklist
- Object ID
customscript_seam_collect_wlcustomdeploy_seam_collect_wl- Request
- REQ-0112 A weekly list of overdue invoices for the collections team
- Touches
- Invoiceopen balance and due date, shown on the worklist
- Invoicenew field
custbody_seam_ptp_date - RolesA/R Clerk, Collections Manager
Nothing goes live without you.
Nobody approves their own request: when you are the one asking, a second approver you name signs off. Before anything reaches production, you see:
- a summary in plain words;
- what it touches;
- a tag per line: Reversible, Removes stored data or Cannot be undone;
- the code, for your developer or partner.
You approve it, send it back or reject it.
The log records who asked, who approved, what changed and when. SeamSet keeps it, and you can export it at any time. NetSuite also logs each deployment in your account.
In plain words
Emails the collections team the overdue list every Monday, from a saved search. Adds a worklist for the collectors and a promise-to-pay date on invoices. Removes the old free-text field Chase note. From the worklist, collectors can send reminder emails.
Touches
- Invoices
- Saved search: Overdue invoices
- Roles: A/R Clerk, Collections Manager
- Email to customers
- Schedules the saved search "Overdue invoices" to email the collections team every MondayReversible
customsearch_seam_overdue_invNative: no code - Adds the page "Collections worklist"Reversible
customscript_seam_collect_wl · customdeploy_seam_collect_wl - Adds the field "Promise to pay" on invoicesReversible
custbody_seam_ptp_date - Removes the free-text field "Chase note" on invoicesRemoves stored data
custbody_chase_note - Sends a reminder email to the customer when a collector clicks SendCannot be undone
customscript_seam_remind · customdeploy_seam_remindA sent email can't be recalled.
Code, folded: 2 scripts, SDF project
What SeamSet will not do
Go live without approval, even for a small change.
Delete posted transactions. Corrections go through credit memos and reversing entries.
After go-live, and before every major release
Before each of NetSuite's two major releases a year, you request a release preview account. SeamSet reruns its checks there and tells you what needs attention. Fixes go through the same approval.
For your security review
The security page covers where each point stands today and what we walk you through in a security review, access and data included.
Bring the request that has waited longest.
Tell us about one request sitting in your queue. We'll talk it through: what NetSuite already covers, what SeamSet would build, and what you would approve.