Services · Streamline & Outsource

IT general controls (ITGC) documentation

Document how access, system changes and day-to-day operations are controlled in NetSuite. The service brings your IT general controls (ITGC) into one clear, consistent set of documents and keeps them updated as your processes change. Auditors receive a clear, current record of how the system is controlled, reducing the need to rebuild the explanation at every audit.

One coherent packageAuditor-shaped, maintained
The problem

Scattered ITGC documentation makes audits harder than they need to be

Access management, change management and IT operations are often documented separately, using different terms and pointing to evidence stored in several places. Auditors must piece the controls together, resolve conflicting explanations and request missing information, which creates delays and raises avoidable questions. A structured ITGC file brings everything into one consistent package. It explains how the controls work, uses the same terminology throughout and links each control to its supporting evidence, giving auditors a clear and reliable account of how the system is governed.

What we run

How we document IT general controls in NetSuite

Senior consultants oversee the work, and you can see progress as it happens. Approvals and decisions stay with your team.

  • Framework mappingYour audit framework’s ITGC expectations are mapped to the NetSuite estate, giving the file a table of contents agreed with your programme.
  • Access-domain assemblyProvisioning, reviews, SoD and authentication controls are written into the access chapter with evidence pointers.
  • Change management documentationThe change process, testing procedures, log reviews and release checks are brought together in one chapter. It shows how a request moves from initial approval through testing and into production.
  • Operations-domain assemblyScheduling, monitoring and the backup-and-availability posture are documented at the true platform boundary, with what Oracle runs and what you govern drawn plainly.
  • Consistent documentationTerminology, control owners and cross-references are aligned across every chapter, giving the ITGC file one clear and consistent voice.
  • Cycle maintenanceThe package is updated on every relevant change and audit finding, keeping the file alive on the SOX calendar.

ITGC evidence scattered across inboxes?

We document your ITGC in the form auditors expect to receive. Talk it through with a senior consultant. It’s free, it takes 30 minutes and there’s no sales pitch.

The payoff

What handing it over buys you

The audit starts with a clearer picture

A well-organised ITGC package helps auditors understand the control environment quickly, reducing the time spent finding documents and piecing together how the controls connect.

Contradictions get edited out

Reconciled chapters keep the access narrative in agreement with the change one.

The SaaS boundary is pre-drawn

The operations chapter answers the Oracle-runs-it questions before they are asked.

The file compounds

Cycle maintenance means each audit inherits last year’s package plus changes, not a rebuild.

How handover works

From scattered controls to one ITGC file

  1. Map the framework – expected controls are mapped to the estate and the contents agreed.

  2. Assemble the domains – the access, change and operations chapters are written from how the system runs.

  3. Edit for coherence – the file is unified into one voice, cross-referenced and evidence-pointed.

  4. Maintain – updates follow every relevant change and finding, on calendar.

Good to know

What to know before you hand it over

  • !The SaaS responsibility boundary is clearly documented. Oracle manages areas such as infrastructure, backups and platform availability under your subscription, while your team controls how NetSuite is configured and used. The operations chapter explains this division and links to Oracle’s relevant assurance reports, giving auditors an accurate view of which controls your business actually operates.
  • !Your audit framework defines the required controls. Your assurance programme and auditors decide which ITGCs need to be covered. The documentation is then structured around those requirements and records how each control operates.
  • !Bringing the documentation together can reveal control gaps. If the review finds that a required control does not exist, the gap is reported clearly to the appropriate owner. The documentation reflects the actual control environment rather than hiding missing processes behind polished wording.
Straight answers

IT General Controls (ITGC) Documentation FAQs

What belongs in the operations chapter for a SaaS system?
The chapter documents the controls your business operates, including job scheduling and monitoring, incident management, release preparation and post-upgrade checks. It also explains which responsibilities sit with Oracle, such as the underlying infrastructure, backups and platform availability. The purpose is to show the boundary clearly, so auditors can see which controls you manage directly and where you rely on Oracle’s assurance.
Can auditors work directly from the ITGC file?
Yes. The file is organised around your audit framework and links each control to its supporting evidence. This gives auditors a clear starting point and can reduce follow-up requests for information because many common PBC items are already identified and easy to locate.
Which ITGC controls are most important in NetSuite?
User access is usually the main focus. Auditors want to see how accounts are approved, how leavers are removed, who holds administrator access and whether conflicting permissions are identified and reviewed. They also examine how NetSuite changes reach production, including the approval, testing and evidence behind each release. Operational controls cover areas such as scheduled jobs, incidents and release monitoring. Oracle manages the platform infrastructure, so this section also explains where your responsibilities end and Oracle’s begin. The ITGC file gives the greatest detail to the controls carrying the most risk and links each one to the evidence auditors will need.
Can you help us prepare for our first IT general controls audit?
Yes. Preparation starts with the framework your auditors plan to use, then brings your access, change management and operational controls into one structured ITGC file. Each control is documented as it works today and linked to the evidence that supports it. The review may also uncover missing or informal controls. These are recorded as findings and sent to the relevant owners, giving your team time to address them before fieldwork begins. Starting a few months before the audit gives your team time to address any weaknesses, while a later review can still bring the evidence together and clearly document any open gaps.
How does this differ from control narratives?
Control narratives explain how individual controls work, including who performs them, when they happen and what evidence they produce. The ITGC file brings those narratives together into one structured package covering access, change management and operations. The narratives provide the detail; the ITGC file gives auditors the complete view.

Last reviewed: 9 November 2026 · Written by the Suite Generation team

Ready to hand this one over?

Tell us the state of your ITGC file and the problems you are seeing, and we will scope the parallel run.

Scoping Call — Sitewide

We reply within 24 hours.

or email hello@suitegeneration.net

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.

Independent – no licence resellingSenior-led – solution-architect levelTrusted to fix failed implementations
Talk to a solution architect