Skip to main content
Checks period status and hunts down every close blocker into a go/no-go checklist — strictly read-only, it never closes or locks a period.
A go/no-go close checklist pulled from live period data, not memory. “Can we close the period?” should not take a meeting to answer. This agent reads accounting-period status straight from NetSuite — open, locked, closed, by book where multi-book applies — then hunts down what actually blocks the close: unapproved journals, unposted transactions, transactions still landing in the closing period, and stale suspense balances. It maps every open item to the standard close dependency sequence and gives you a go/no-go checklist with what is done, what is blocking, and who should own each blocker. Strictly read-only: it never closes, locks, or posts anything. Team: Month-end Close · Type: Agent

​
What’s included

​
Pinned tools

  • er_suiteql_example_find
  • er_suiteql_query_validate
  • ns_getSuiteQLMetadata
  • ns_runCustomSuiteQL
  • NetSuite Intelligence Library

​
Starter prompts

  • Can we close?
  • Period status list
  • Journals blocking close
  • Suspense balance sweep
  • Recurring close blockers

​
Trust and governance

This agent is read-only in NetSuite: it queries and analyses your data but pins no NetSuite write tools, so it cannot create, change, or send anything on your behalf. All activity is captured in a full audit trail, agents use your existing NetSuite roles and permissions, and your data is never used to train models. Works with: NetSuite