The foundation: a configuration graph of your actual NetSuite account.
Every custom field, workflow, script, saved search, role, form, segment and integration — mapped, connected and kept current.
This is what makes automated change safe. Without it, an AI is guessing about your environment.
See how your NetSuite is actually connected.
ConfigLedger turns fragmented NetSuite configuration into a persistent configuration graph. Every field, search, workflow, role, script and customisation becomes an object — then ConfigLedger maps the relationships between them.
Business Unit
- Internal ID
- custbody_business_unit
- Status
- Active
- Dependencies
- 29
- Last changed
- 18 Aug 2026
- Change risk
- HIGH
“Business Unit is a business-critical transaction classification used throughout management reporting and invoice processing.”
Before you change anything, know where it is used.
Changing a seemingly harmless NetSuite field can affect reports, searches, workflows, scripts and permissions elsewhere in the account.
ConfigLedger traces those dependencies before you make the change.
“Sales Channel is used primarily to classify e-commerce and marketplace revenue. It appears to be business-critical because it is referenced by monthly revenue reporting and three integration scripts.”
Changing or deleting this field could affect 32 configuration objects.
Ask why NetSuite behaves the way it does.
Finance teams understand the business process.
They should not need to reverse-engineer SuiteFlow states, script logic and role restrictions every time something behaves unexpectedly.
Every answer links back to the configuration objects it came from — workflows, searches, roles and scripts detected in your account.
Why does this vendor bill require CFO approval?
“Vendor bills above £25,000 require CFO approval.
Bills below £25,000 require Department Head approval only, unless the vendor is marked as New Supplier.
This rule is controlled by Vendor Bill Approval Workflow v4.”
Why can’t Maria see the Sales Dashboard?
Turn complicated workflows into explanations people can understand.
SuiteFlow can become difficult to understand after years of modifications.
ConfigLedger converts workflow configuration into clear business-language explanations.
“Vendor bills below £5,000 are approved automatically unless the vendor is new.
Bills between £5,000 and £25,000 require Department Head approval.
Bills above £25,000 require Department Head and CFO approval.
If no action occurs within three working days, an escalation notification is sent.”
- 1Entered
- 2Validation
- 3Department Approval
- 4CFO Approval
- 5Approved
Find the clutter your NetSuite has accumulated.
Years of implementation work often leave behind duplicate fields, redundant searches, inactive workflows and abandoned configuration.
ConfigLedger continuously surfaces potential clean-up opportunities.
Findings are flagged for review — ConfigLedger does not delete or modify NetSuite configuration.
Duplicate Searches
7 saved searches appear to provide substantially the same AP ageing output.
Similar Fields
custbody_region · custbody_sales_region · custbody_region_new
Unused Configuration
37 active custom fields have no detected populated values during the selected analysis period.
Inactive Roles
7 roles have no currently assigned users.
See what could break before you make the change.
NetSuite changes rarely exist in isolation.
ConfigLedger analyses dependencies and gives administrators a clear impact assessment before configuration is modified.
Change with evidence, not assumptions.
- Revenue reporting
- Department budgeting
- Sales dashboard
- Vendor approval workflow
Know what changed — not just what exists today.
Every ConfigLedger scan creates a configuration snapshot.
Over time, your NetSuite environment becomes a searchable history rather than a constantly changing black box.
- 4 Saved Searches
- 2 Custom Fields
- Vendor Bill Approval Workflow
- Finance Manager Role
- Legacy Revenue Search
Vendor Bill Approval Workflow
CFO approval above £20,000
CFO approval above £30,000
“The CFO approval threshold increased by £10,000. This may represent a material control change and should be reviewed against your current finance policy.”
ConfigLedger becomes the institutional memory of your NetSuite environment.
Automatically document the NetSuite account your team inherited.
NetSuite documentation often lives across spreadsheets, consultants’ notes, old project folders and people’s memories.
ConfigLedger creates a structured account handbook directly from your configuration.
Global Holdings
- 01Company Structure5 pp
- 02Subsidiaries8 pp
- 03Dimensions11 pp
- 04Custom Fields14 pp
- 05Saved Searches17 pp
- 06Workflows20 pp
- 07Roles & Permissions23 pp
- 08Integrations26 pp
- 09SuiteScripts29 pp
- 10Key Finance Processes32 pp
Understand access without digging through permission matrices.
ConfigLedger helps teams understand role configuration and identify potential control conflicts for further review. It is intelligent visibility and control review — not a replacement for enterprise GRC software.
- Can create and approve journals
- Can edit vendors and process vendor payments
- Access across all subsidiaries
- Cannot administer users
Your NetSuite contains years of business logic.
Understand it. Then change it safely.
Map your configuration, trace every dependency, and turn business requests into governed changes that are tested in Sandbox and deployed only when you approve.
Understand → Change → Validate → Control