A Process NetSuite Doesn't Do Yet
An approval that still lives in email, a calculation done in a spreadsheet, or an invoice your customers see that still looks like the default.
See where it would sitHome / NetSuite Services / Customization
Approval workflows, custom fields, scripts, PDF templates and reports. We build them configuration first, document them inside the account, and test them against every NetSuite release.


Who this is for
A process NetSuite doesn't do yet, a report rebuilt by hand, or scripts nobody can explain.
An approval that still lives in email, a calculation done in a spreadsheet, or an invoice your customers see that still looks like the default.
See where it would sitThe saved search or workbook was never built, so Excel does the job and the numbers never quite match the ledger.
See where it would sitThe developer left, nothing is documented, and every NetSuite release is a gamble. We start with an inventory, not a rewrite.
Start with a customization reviewWhat NetSuite customization is
There are six layers, and each one costs more to keep through NetSuite's two releases a year than the one before. So we work down the list and stop at the first layer that solves the problem. A surprising number of requests end at the first one, as a feature you already licensed and never switched on.
Enable Features, accounting preferences, roles and standard forms. A surprising number of requests end here.
On recordBeyond Air: the chart of accounts and segment usage were fixed before anything new was built.
Custom fields, custom records for data NetSuite has no table for, custom segments that carry a reporting dimension through the ledger, and forms that show each role only the fields it needs.
On recordVineyard Capital Partners and Woodway Energy: segment values enforced on every transaction.
Approvals for purchase orders, vendor bills, journals, expenses, time entries and new vendors; field defaults by role or location; record locks; notifications. The approval history stays on the record.
On record40+ approval workflows across our published case studies, including six each at RedRidge Bio and Micron Biomedical.
Advanced PDF templates for invoices, purchase orders, packing slips and checks; saved searches, SuiteAnalytics workbooks and SuiteQL for the reports people rebuild in Excel; dashboards by role with portlets, KPIs and reminders.
On recordAlafair Biosciences: five PDF layouts plus custom reports and searches, live six weeks after we took over.
An add-on from the SuiteApp Marketplace, chosen when the requirement is one a whole market shares, so the vendor carries the release maintenance instead of you.
On recordRedRidge Bio: Atlar for Swiss payments. Zenas BioPharma: the HitPoint China module.
NetSuite's JavaScript, for what a workflow can't express: user event, client, scheduled and map/reduce scripts, Suitelets and RESTlets, written in SuiteScript 2.1 and deployed with the SuiteCloud Development Framework.
On recordAnthem Holdings: location defaulting and account restriction scripts for 35 users across 80+ locations.
Not sure which layer your request belongs to? That is what the scoping note is for, and sometimes the answer is a setting.
Scope a NetSuite CustomizationSound familiar?
A customization review starts with an inventory of every script, workflow, search and report in the account. These four turn up most often.
Beyond Air came to us after another firm's implementation, with problems in the chart of accounts, segment usage and approval workflows. We fixed all three before the company went to market.
Start with a customization reviewcustomscript_daily_update_2Scheduled scriptNone
It runs every day and nobody can say why. No description, no owner, no design note.
customscript_po_approveUser event scriptLeft in 2022
An approval written as a script, because nobody knew SuiteFlow could route, lock and email the record on its own.
customscript_esign_sendSuiteletContractor
A custom build for a problem a SuiteApp solved years ago: e-signature, bill capture, a country's payment format.
customscript_inv_fix_v3Client scriptUnknown
Fixed in production. No sandbox, no SDF project, so the first anyone hears of a broken script is the morning after a release.
How we build
A PDF template and a scripted process go through the same six steps. Nothing is built in production, and two steps end with a decision that is yours.
Your edition, Enable Features, SuiteBuilder, SuiteFlow and the SuiteApp Marketplace, checked against the requirement before any code is scoped.
One-page recommendationTrigger, record, logic, exceptions, owner, and what happens on failure. Script IDs carry a prefix and values live in parameters, not in the code.
Your sign-offSuiteCloud Development Framework projects under version control, logging in every script, map/reduce where the volume needs it.
A deployable SDF projectWe unit test, then your people run their own scenarios. The test cases are kept, so they run again at the next release.
Your go or no-goEvery script, workflow and custom record carries a description and an owner in NetSuite, not in someone's inbox.
A register your auditor can readNetSuite releases twice a year. For the accounts we run, each customization is checked in the release preview before production upgrades.
Still working the morning afterWhy work with us
Will it work, will it survive the next release, who maintains it, and will anyone tell you when you don't need it? Those are the questions behind choosing a NetSuite development company. Here are our answers.
The configuration check comes first in every scope. When a setting solves the problem, that is our recommendation, even though it costs us the development work.
The consultant who designed your solution leads the build, and Centium's own NetSuite developers write it. Our people average 2.5 NetSuite certifications each.
A sandbox, an SDF project, a design note and a test for every script. That is what lets a customization pass through two releases a year without anyone noticing.
Our Business Optimization team is handed every customization in a 30-day overlap, and 85% of our implementation clients stay on with them.
Customizations on record
Eight of the clients in our published case studies, by what went live in their account.
Vendor and journal entry approvals, location defaulting and account restriction scripts for 35 users, and custom consolidated financial reports.
Vendor, vendor bill and journal entry approvals, plus a workflow that defaults segment values and restricts GL accounts.
Approval workflows, the chart of accounts and segment usage rebuilt after another firm's implementation, then PDF customization.
Custom reports and saved searches, an API-based expense integration and bank ACH, on an implementation we took over.
Atlar for Swiss payment compliance and multi-book statutory reporting across a US and a Swiss entity.
A global chart of accounts and segment structure, and cash burn visuals in place of a spreadsheet forecast.
Automated time entry and AP processing with SquareWorks (now Charted) and FISPAN, built ahead of a planned IPO.
Purchase order, vendor bill and journal entry approvals plus cash disbursement approval, and the HitPoint China module.
Also on record: Carrick Therapeutics, Woolfson Eye Institute, Homesteaders, Variant Bio, Woodway Energy, Pramand and enGene.
Read the case studiesWhat a controller says about Centium
“As our business evolves, we always find a strong partner in Centium to customize the system to deal with ever-increasing complexities.”Artur Sochivko, Senior Director, Assistant Controller, enGene
Some of the companies whose NetSuite accounts carry customizations we built
FAQ
Anything else, ask one of our consultants directly.
Talk to a NetSuite ConsultantConfiguration changes what NetSuite already does, with the settings it gives you: Enable Features, preferences, roles, which fields a form shows. Customization adds something the account didn't have: a custom field or record, a workflow, a script, a PDF template, a saved search, a SuiteApp. NetSuite carries configuration through every release. A customization is yours to maintain, which is why our NetSuite customization services use up the configuration options first.
Almost everything you see, and nothing underneath it. The user interface, fields, records, segments and forms with SuiteBuilder; approvals, defaults and notifications with SuiteFlow; logic, custom pages and APIs in SuiteScript; printed documents with Advanced PDF templates; reports with saved searches, workbooks and SuiteQL; plus SuiteApps. You can't change the application's own code, and that is the point: NetSuite upgrades underneath your layer twice a year.
SuiteFlow whenever it can do the job: approvals, defaults, locks, emails and routing, built by configuration, with a history on the record an auditor can read. SuiteScript for what a workflow can't express: calculations across records, processing at volume, a custom page or API. The same need can go either way. Anthem Holdings got two scripts to default locations and restrict accounts; Vineyard Capital Partners and Woodway Energy got workflows for the equivalent.
Some do, and it is predictable which: old SuiteScript 1.0 code nobody revisited, hardcoded internal IDs, templates that reference a renamed field, workflows nobody has run since their author left. What survives is SuiteScript 2.1 within governance limits, parameters instead of hardcoded values, a design note, and a test run in the release preview account before each release. For the accounts we run, we run that test.
A NetSuite developer, or NetSuite technical consultant, writes SuiteScript, builds SuiteFlow workflows and SuiteBuilder objects, designs PDF templates and deploys through the SuiteCloud Development Framework. A good one also says when the request is a configuration rather than NetSuite scripting. Our NetSuite development services are delivered by Centium's own team, led by the consultant who designed the solution.
Scope sets the date, not typing. A PDF template or a saved search is the quick end; a scripted process takes longer, and most of that time is design and testing. Inside an implementation, RedRidge Bio and Micron Biomedical each took six approval workflows and four templates live with the project, and Alafair Biosciences had five PDF layouts and custom reports live six weeks after we took over.
We scope it per customization after the configuration check, because a request that turns out to be a setting costs nothing to build. The drivers are the layer (a workflow costs less than custom development in SuiteScript), the exceptions the rule has to handle, and testing. On a Business Optimization Services plan, development work can sit inside the plan. The cost people forget is upkeep: a script is tested twice a year, every year.
Yes, starting with an inventory rather than a rewrite. We list every script, workflow, search and report in the account and sort each one: keep and document, rebuild as a workflow, replace with a SuiteApp, or retire. You end up with a documented layer, an owner for each item, and a test before the next release. Beyond Air's account was put right this way after another firm's implementation.
It helps, when it is done in SuiteFlow and documented. Approval workflows are system-driven controls: the record can't post until the right person approves it, and the history stays on the record. That is why NextRNA built five ahead of a planned IPO and RedRidge Bio built six for a future sale or listing. Scripts need the opposite care: the design note and the register go to the auditor.
Start here
Tell us what the system needs to do and who has to approve it. In the first conversation you get a plain read on whether it is a setting, a workflow, a SuiteApp or a script, and a scoping note before any proposal.
Related NetSuite services