For CFOs and finance teams
Get the workarounds out of your finance team's week.
SeamSet builds what your NetSuite account is missing for finance. Your team describes the need in plain words and gets a first version in minutes. It goes live once your NetSuite admin approves.
A normal week in many finance teams:
At the close, the trial balance rebuilt month by month in Excel.
Overdue invoices chased from a spreadsheet.
The weekly report exported, stale by the meeting.
A journal import rejected as out of balance, and nobody can see why.
Vendor bills approved by email, then keyed in.
NetSuite can already do some of this.
The trial balance report can show one column per month. A saved search can email its results every Monday. Setup takes time, and the close comes first.
Native first: if NetSuite already does it, SeamSet sets it up and writes no code. Otherwise it builds only what is missing. For example, a check that shows whether each entry in a journal file balances before anything loads.
Request
"the trial balance, month by month"
: Covered by NetSuite: the trial balance report, with one column per month.
What the workarounds cost
Manual work never shows up as a budget line. It shows up elsewhere:
- A slower close.
- Cash collected later.
- Decisions made on stale numbers.
- A team kept on workarounds,not on the analysis you hired them for.
Custom work is hard to estimate, for everyone
"A NetSuite partner scoped an EPM project at 75 hours. It ended up needing 400+."
On a small request, the cost sits around the code: back-and-forth on the spec, then the wait to go live. So a report here and an approval there rarely justify a quote.
SeamSet cuts the back-and-forth: whoever asked gets a first version directly. Scoping stays with your team. Your NetSuite partner keeps the large projects.
Who approves, and what gets logged
- Tested before it goes live. Every change.
- Your admin approves. They see each change in plain words, then approve it, send it back or reject it. Nobody approves their own request.
- A log of every change. The log records who asked, who approved, what changed and when. You can export it at any time.
- Flagged before approval. Each line of a change is tagged Reversible, Removes stored data or Cannot be undone.
No in-house NetSuite admin? Approval goes to whoever holds that role: a controller, an IT lead, or your NetSuite partner.
What SeamSet builds runs inside your NetSuite account, except portals for people with no NetSuite login and screens NetSuite's pages handle badly.
In plain words
Vendor bills go through an approval workflow instead of email: each bill goes to its budget owner, and to the controller above the department's limit. Adds a budget owner on departments. Removes the old free-text field "Approved by (email)" on bills. Each approver gets a morning email of the bills waiting on them.
- Sets up the approval workflow on vendor bills: budget owner, then controller above the limitNative: no codeReversible
- Adds the field "Budget owner" on departmentsReversible
- Removes the free-text field "Approved by (email)" on vendor billsRemoves stored data
- Sends each approver a morning email of the bills waiting on themA sent email can't be recalled.Cannot be undone
Log
- Maya Lindqvist, AP lead
- Tom Keller, NetSuite admin
- REQ-0240: the approval workflow on vendor bills
- 12 Sep, 14:05
After go-live, and before each major NetSuite release
Before each major NetSuite release, SeamSet reruns its checks in a preview account and tells your admin what needs attention. Fixes go through the same approval.
Each change comes with its documentation.
If you stop using SeamSet, what runs inside NetSuite keeps running; portals stop.
Bring one request from your finance team.
Tell us the workaround your team would drop first. We'll talk it through.
- Your admin will ask how this goes live. Their page:For NetSuite admins