Audit trail configuration
Create a reliable record of who changed what and when. Audit trail coverage is checked against your control requirements, configurable gaps are addressed and clear retrieval methods are set up in advance. When an audit or investigation begins, the evidence is complete, accessible and ready to use.
An untested audit trail can undermine your control documentation
The control narrative may say that changes are logged, but an auditor will ask to see the evidence. Whether it exists can depend on the field, record type and route used to make the change. Audit coverage varies, so relying on assumptions creates risk. Audit trail configuration checks what NetSuite records, identifies any gaps and confirms which gaps can be addressed. It also documents how to retrieve the evidence when an audit or investigation requires it.
How we configure the audit trail in NetSuite
Senior consultants oversee the work, and you can see progress as it happens. Approvals and decisions stay with your team.
- Audit trail coverage checksThe fields and record types named in your control documentation are tested to confirm that NetSuite records the expected changes in system notes. This replaces assumptions with verified evidence.
- Gap analysis & closureWhere capture falls short of the claim, configurable gaps are closed and structural ones are documented plainly with compensating routes.
- Sensitive-change focusThe trails that matter most, covering bank details, prices, permissions and posted-period edits, receive explicit verification.
- Retrieval engineeringSaved searches and SuiteQL queries are built over the notes before any investigation needs them, so who-changed-this is answered in minutes.
- Retention reviewNetSuite’s audit trail retention is compared with your evidence requirements. The available history is documented, and an export process is established where your policy requires records to be kept for longer.
- Trail-health checksPeriodic sampling confirms the capture still works, giving the control its own control on the SOX calendar.
Could you prove who changed what?
We handle audit trail configuration so changes stay traceable after the event. Talk it through with a senior consultant. It’s free, it takes 30 minutes and there’s no sales pitch.
What handing it over buys you
The narrative survives the walkthrough
Verified coverage means the claimed log is demonstrably logging.
Investigations start at the answer
Retrieval tooling finds the bank-detail change in minutes, with its author.
Gaps are known, not discovered
Structural limits are documented with their compensating controls.
The trail stays trustworthy
Health checks verify capture on a rhythm rather than assuming it still works.
From assumed coverage to verified capture
Verify the claims – the control narrative is tested against actual system-notes behaviour.
Close & document – configurable gaps are fixed and structural ones stated.
Build retrieval – the investigation queries are made ready in advance.
Check on rhythm – trail health is sampled on the SOX calendar.
What to know before you hand it over
- !Audit trail coverage has clear limits. NetSuite’s system notes vary by record type and by how a change is made. If your control documentation expects more than the platform records, the narrative is corrected or a compensating control is introduced. Any limitation is documented clearly.
- !Retention horizons are platform facts, mapped not promised. What is retrievable, and for how long, follows NetSuite’s behaviour. Your evidence-retention policy meets that reality through exports where needed, and we state the limits plainly.
- !Audit trails detect changes rather than prevent them. The log provides evidence of what happened after an action took place. Access controls help prevent unauthorised activity, so the control design uses both and documents their different purposes clearly.
Audit Trail Configuration FAQs
Does NetSuite log every change?
Can we see who changed a bank account number?
Where is the NetSuite audit trail found?
Can the audit trail be edited or deleted?
Do system notes affect performance?
How far back does the audit trail go?
Last reviewed: 9 November 2026 · Written by the Suite Generation team
Suite Generation is an independent, senior-led NetSuite consultancy. Every project is designed and delivered by consultants at or close to solution-architect level. We don’t resell licences or carry partner targets. Our advice is ours, whether you’re implementing NetSuite, rescuing a stalled project or fixing a system that never delivered.
