System implementation services · what we do
How Ledger Summit delivers this engagement
Each engagement runs the same Ledger Summit transition model: discover the current workflow, prove value with a controlled pilot, design controls and evidence packs, integrate with your stack, and stand up managed support so the gains compound.
Our approach to NetSuite implementations
Most NetSuite implementations fail at the seams: data migration, post-go-live support, and the workflows the standard ERP doesn't handle well. We build for those seams from day one. The defining principle: a NetSuite implementation is a controller-led operating-model redesign with the new GL as the artifact that comes out the back. When implementation drives the design, the project ships but the operating model is broken.
- Controls and audit evidence designed before configuration starts
- AI workflow layer (Tool Box AI) planned in scope, not bolted on after
- Parallel close in month 1 — never go live cold
- Risk register, rollback plan, and named owner for every milestone
- Documentation that survives staff turnover (yours and ours)
- Auditor walkthrough at week 5 — not month 6
- Realistic post-go-live optimization list, not feature creep during implementation
What we implement
- Chart of accounts design (multi-entity, dimensions, segments)
- Subsidiaries, intercompany, currency, and consolidation
- AP/AR with approval workflows and three-way match
- Revenue recognition (ASC 606) and project accounting
- Inventory, fixed assets, and depreciation schedules
- Lease accounting (ASC 842) where applicable
- Reporting: management pack, board pack, lender pack
- Integrations with payroll, HRIS, banking, Bill/Ramp, Salesforce/HubSpot, and Tool Box AI
- User roles, permissions, SOX-ready controls
- Data migration with reconciled before/after totals
- Training in role-specific waves with recorded walkthroughs
- Hypercare ticket system stood up before cutover
SuiteApps and modules — what we deploy and why
NetSuite ships with a base platform plus optional modules and a SuiteApps marketplace. The right configuration depends on industry shape and growth path.
| Module / SuiteApp | What it does | When to deploy |
|---|
| OneWorld | Multi-subsidiary, multi-currency, consolidation | 2+ entities or international |
| Advanced Revenue Management (ARM) | ASC 606 revenue recognition | SaaS / subscription with material rev-rec complexity |
| SuitePeople | HRIS + payroll integration | US-based, <500 employees, simple HRIS needs |
| SuiteProjects | Project accounting, time-and-billing | Services delivery; alternative: native NS Projects |
| Advanced Inventory Management (AIM) | Multi-location, lot/serial, demand planning | Manufacturing, distribution |
| Advanced Manufacturing | BOM, work orders, MRP | Light-to-medium manufacturing |
| SuiteAnalytics | Custom dashboards and reporting | All implementations; standard |
| SuiteCommerce / SuiteCommerce Advanced | Ecommerce platform | Direct-to-consumer or B2B portal |
| Fixed Asset Management (FAM) | Depreciation schedules, asset tracking | Material fixed-asset base ($500K+) |
| NetSuite Planning & Budgeting (NSPB) | FP&A planning and consolidation | Mid-market FP&A teams; alternative: Adaptive Planning |
Implementation phases
| Phase | Weeks | What ships |
|---|
| Discovery & design | 2–4 | COA, dimensions, controls, integration map, risk register, project plan |
| Configuration | 4–8 | NetSuite core build, integrations, custom workflows, Tool Box AI layer |
| Data migration | 2–3 | Master data + opening balances; reconciled before/after |
| Parallel close | 1 close cycle | Run NetSuite alongside legacy; reconcile to zero |
| Cutover & hypercare | 4 weeks | Production cutover, training, daily standups, issue triage |
| Post go-live | Ongoing | Optimization, new workflows, managed support if scoped |
Vertical specializations
We've implemented NetSuite for several industries with distinct accounting needs. Each vertical has its own configuration patterns, risk patterns, and integration set.
| Industry | Configuration emphasis | Typical timeline |
|---|
| SaaS / subscription | ARM (ASC 606), Stripe integration, deferred revenue waterfall, modification handling | 120–150 days |
| Multi-entity holdco | OneWorld, intercompany, FX revaluation, CTA tracking, consolidation | 150–180 days |
| Light manufacturing | AIM, BOM, work orders, std cost vs. actual variance | 180–240 days |
| Distribution / wholesale | AIM, multi-location, demand planning, EDI integration | 150–210 days |
| Direct-to-consumer ecomm | SuiteCommerce, Shopify integration, Avalara, multi-channel reconciliation | 180–240 days |
| Professional services | SuiteProjects, time-and-billing, project profitability dashboards | 90–120 days |
| Construction | Job cost, WIP, AIA billing, retainage tracking, percentage-of-completion | 180–240 days |
| GovCon / federal services | Project accounting, indirect rates — usually Costpoint is a better fit | NetSuite rarely the right answer |
| Healthcare services | Multi-location, payer-mix reporting, contractual allowance accruals | 150–210 days |
Data migration strategy
Most NetSuite project failures originate in data migration. Two principles drive ours: migrate the minimum that works for the operating model going forward, and reconcile to zero on every category before cutover.
- Master data first — customers, vendors, items, projects, subsidiaries, accounts: deduplicated, normalized, validated
- Open balances next — open AR / AP / fixed assets / projects with full transaction detail
- Historical GL summary balances — 3 years of monthly summary balances by account-sub-dept (or longer if audit cycle requires)
- Historical transaction detail — usually stays in legacy system as read-only; rarely worth full migration
- Reconciliation gates — trial balance to zero, sub-ledgers to GL, AR/AP to control accounts, all sub-system reconciliations to source
- Spot-check sample — 30 records per category manually validated end-to-end
- Cutover rollback plan — documented for every migration milestone
Common scope traps — and how we avoid them
- COA copied verbatim from legacy. The biggest source of post-go-live cleanup. Spend two weeks on COA design before any configuration starts.
- Integrations underestimated. "We'll integrate Bill" sounds simple. It isn't. Plan integration as its own workstream with its own owner.
- Custom fields imported wholesale. Most legacy custom fields are workarounds for missing native functionality. Don't carry them forward.
- Customizations during phase 1. Customizations that aren't blocking go-live belong on a post-go-live optimization list. They add risk and slip the timeline.
- Training delivered too late. Role-specific training has to happen during configuration, not at cutover.
- Auditor not engaged until cutover. Walk the auditor through your control design at week 5 or 6, not at first audit.
- Cutover at fiscal year-end without runway. Year-end is ideal for cutover but only if the project is on track in October. Otherwise plan a mid-year cutover with a clear comparative-reporting plan.
- "Lift and shift" mentality. Implementation is a redesign opportunity, not a 1-for-1 system swap. Use it.
Integration architecture
NetSuite integrations come in three flavors: native (vendor-provided SuiteApps), middleware (Boomi, Workato, Celigo), and custom (REST/SOAP via SuiteScript or SuiteCloud). The right choice depends on volume, latency, and complexity.
| System | Typical pattern | Notes |
|---|
| Bill (BILL.com) | Native SuiteApp | Vendor sync, AP approval flow, payment |
| Ramp / Brex | Native SuiteApp | Card spend, expense reports, GL coding |
| Salesforce | Celigo or native NS-SF connector | Customer master, opportunity-to-cash, contract sync |
| HubSpot | Celigo or custom | Customer master, deal-to-invoice |
| Stripe | Custom or Celigo | Subscription billing, usage events, settlement reconciliation |
| Shopify | Celigo | Order, refund, settlement reconciliation |
| Avalara | Native SuiteApp | Tax calc on invoices, return filing |
| Payroll (Gusto/Rippling/ADP) | Custom or middleware | Payroll JE summary by GL coding |
| Banking | Native bank connectivity or AutoBank | Bank feeds, payment file delivery |
| EDI (manufacturing/distribution) | Boomi or DiCentral | Order-to-cash, advance ship notice |
Post-implementation rescue
About a third of our NetSuite engagements are rescues — companies who went live with another partner and now have a half-working system. We can come in, stabilize, then optimize. Common rescue scope:
- COA repair — collapse of duplicate accounts, refactor of segment usage
- Intercompany cleanup — un-tangle entity-pair logic, correct elimination posting
- Broken integrations — fix or replace integrations that aren't producing reliable data
- Controls gaps — add segregation of duties, approval flows, audit evidence
- Custom workflow rebuilds — replace fragile SuiteScript with maintainable patterns
- Training and documentation — bring users up to speed and create role-specific playbooks
- Reporting infrastructure — fix saved searches, dashboards, and management packs
When NetSuite isn't the right answer
- Below ~$15M revenue with single entity. QBO Advanced + bolt-on tools (Bill, Ramp, lightweight BI) usually delivers more bang for buck.
- Heavy GovCon or DCAA-regulated. Costpoint or Unanet are typically a better fit; NetSuite GovCon plug-ins exist but rarely match purpose-built systems.
- Real estate / construction / AIA-billing-heavy. Sage Intacct often fits the percentage-of-completion and WIP patterns better.
- Pure ecommerce at high SKU velocity with 3PL complexity. Shopify Plus + dedicated inventory and 3PL tools sometimes outperform NetSuite at this shape.
- Heavy CPM / FP&A consolidation needs at $500M+. OneStream or Anaplan as the consolidation engine, NetSuite as the GL.
Frequently asked questions
How does this compare to other NetSuite implementation partners?
Most NetSuite VARs are great at configuration but light on accounting, controls, and post-go-live operations. We do the configuration with the same rigor a controller would expect, build controls in from the start, and stay engaged after go-live. We also bring Tool Box AI as the workflow layer, which most VARs don't offer.
How long does a NetSuite implementation actually take?
For a $25–100M company with 1–3 subsidiaries, plan on 90–120 days end to end. Larger or more complex (5+ entities, heavy customization, regulated industries) typically run 150–240 days. Our QuickBooks-to-NetSuite case study walks through a 90-day migration.
Can we keep our existing NetSuite license and just have you implement on top?
Yes. We work both as a primary implementation partner and as a workflow/optimization partner sitting on top of an existing NetSuite license.
What does Tool Box AI add to a NetSuite implementation?
Approvals, multi-entity reporting, project accounting, AP/AR exception workflows, and audit-ready evidence packs — all sitting on top of NetSuite. It typically replaces 3–5 third-party SuiteApps and a lot of manual workflow.
Do you handle post-go-live support?
Yes. Hypercare for 4 weeks is included; ongoing managed support is a separate engagement (fixed monthly fee). Most clients keep us on for 6–12 months post go-live, then transition to lighter touch.
Do you sell NetSuite licenses or do you only implement?
Implementation only. NetSuite license is purchased directly from Oracle/NetSuite or a license reseller. We're partner-neutral on license source — it lets us focus exclusively on implementation quality.
How do you handle data migration?
Master data first (customers, vendors, items, projects), then open balances with full detail, then 3 years of GL summary balances. Transaction-level history typically stays in legacy as read-only. Every category reconciles to zero before cutover.
What about training the team?
Role-specific training delivered in waves during configuration: AP team, AR team, accountants, controller, executives. Each role gets a written playbook and a recorded walkthrough they can rewatch.
Can we do a phased rollout (some subs first, others later)?
Yes — phased rollouts are common for groups with 5+ subsidiaries. Typical pattern: parent + largest 1–2 subs in phase 1, remaining subs in phase 2 60–90 days later.
What about SuiteSuccess templates?
SuiteSuccess offers vertical-specific configurations that accelerate phase 1. We use them where they fit but don't force a SuiteSuccess template if it doesn't match the operating model.
Do you handle ASC 842 lease accounting in NetSuite?
Yes — either via NetSuite's native lease module or via a third-party tool (LeaseQuery, Visual Lease) integrated to NetSuite. Choice depends on lease portfolio complexity.
Related Ledger Summit work