Skip to content
SeamSetTalk to us

For NetSuite admins

The requests in your queue, done by the book, approved by you.

Finance or operations describe each request to SeamSet in plain words. They get a first version in minutes.

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, and the cost shows up elsewhere: a slower close, cash collected later, decisions made on stale numbers.

Talk to us

  1. Finance

    Email the overdue invoices search to collections every Monday.

    Native, set up

  2. Purchasing

    POs over the limit approved in NetSuite, not by email.

    Native, set up

  3. Finance

    Check the journal CSV balances before it loads, and show why not.

    Native plus a small script

  4. Warehouse

    Stock free to sell at each location, on a tablet at the dock.

    New script or app

Requests arrive with your questions answered.

SeamSet asks each requester the questions you would ask (which records, which subsidiaries, who sees it, what happens on an exception), restates the need for you both to check, and flags gaps and conflicts before anything is built.

Native first, with pragmatism.

Each request goes one of three ways:

  • Native covers it.

    SeamSet sets that up (a saved search, a workflow, an approval rule), through the same approval, and writes no code.

  • Native covers part of it.

    SeamSet builds only the rest.

  • Nothing native fits.

    SeamSet builds it in SuiteScript: a scheduled or map/reduce script, a Suitelet for a custom screen, a user event script. Or an app outside NetSuite, for a portal or a screen NetSuite's pages handle badly.

If the native route costs more than the need is worth, SeamSet says so. Account features stay your switch.

Request

"overdue invoices, with a button to remind each client"

Collections · Calder Freight Co.

Native

: Covered natively: a scheduled saved search emails the overdue list.

Custom

: Not in this account yet: a worklist with a Send reminder button.

Building only that.

Done by the book. Check every point.

"The right way" is a list any NetSuite developer can check in your account.

  1. SuiteScript 2.1 in SDF projects. No script edits NetSuite's pages directly, which Oracle's development guidelines rule out.

  2. Tested before it goes live. Every change, small ones included.

  3. You decide the access. You connect SeamSet to your account.

  4. Within NetSuite's governance limits.

  5. 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.

  6. Documented. Each change comes with its documentation.

Collections worklist

Object ID
customscript_seam_collect_wlcustomdeploy_seam_collect_wl
Request
REQ-0112 Overdue invoices, with a button to remind each client
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.

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. Nobody approves their own request: when you are the one asking, a second approver you name signs off.

The log records who asked, who approved, what changed and when. You can export it at any time. NetSuite also logs each deployment.

REQ-0112 · Requested by Lena Voss, A/R lead · Approver: Daan Achterberg, NetSuite admin

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 Mondaycustomsearch_seam_overdue_invNative: no code
    Reversible
  • Adds the page "Collections worklist"customscript_seam_collect_wl · customdeploy_seam_collect_wl
    Reversible
  • Adds the field "Promise to pay" on invoicescustbody_seam_ptp_date
    Reversible
  • Removes the free-text field "Chase note" on invoicescustbody_chase_note
    Removes stored data
  • Sends a reminder email to the customer when a collector clicks Sendcustomscript_seam_remind · customdeploy_seam_remindA sent email can't be recalled.
    Cannot be undone

Code, folded: 2 scripts, SDF project

ApproveSend backReject

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.

See how it works

After go-live, and before every major release

Before each major NetSuite release, SeamSet reruns its checks in a preview account and tells you what needs attention. Fixes go through the same approval.

For your security review

The security page covers access, data and what we walk you through in a review.

See what SeamSet can access

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.

Talk to us