FrontierERP
Sign inTalk to Frontier
Applied guide

Automate the NetSuite board pack: what to review

Which parts of a monthly board pack to automate from NetSuite, which stay with the finance owner, and the checks to run before the numbers are pulled.

Frontier · October 26, 2026

An applied guide for the finance owner who signs the board pack.

Every month the board pack has the same shape: the income statement against budget, the balance sheet, cash, a page of KPIs, a page of commentary, an outlook. Every month somebody rebuilds it from NetSuite exports, and the rebuilding is the part nobody would miss.

Most of what ranks for NetSuite reporting automation — spreadsheet connectors, BI pipelines, FP&A platforms — makes one argument: connect NetSuite to the tool and the pack builds itself. Half of it can. The other half is the reason the board reads it — and the line between the two, plus the moment the numbers are pulled, decides whether an automated pack is an improvement or a faster way to send the wrong figure.

The short answer.

  • Automate the ledger half. Statements, budget and prior-period comparisons, subsidiary and segment cuts, aging, cash, the arithmetic behind each KPI, and the tie-outs that prove the pack agrees with the books. It is the same query on the same definitions every month.
  • Review the judgment half. The executive summary, the explanation of each variance, what counts as a one-off, the outlook, the reading of any covenant and the decisions you are asking the board to take. Then sign it.
  • Gate the pull. Automating the ledger half is safe only on a closed period, after consolidation, with the definitions fixed. The failure to design against is a pack pulled too early, not one computed wrongly.

What goes in a monthly board pack.

Packs differ by company and by board; this is the common shape at a company running NetSuite, and which side of the line each part sits on.

Section Comes from Automate or review
Income statement vs budget, prior year, prior month ledger and budget Automate the numbers; review the commentary
Balance sheet: working capital, receivables, payables, cash, debt ledger Automate
Cash flow and cash position ledger and bank Automate the actuals; review the forecast
Subsidiary, segment or department cuts ledger dimensions Automate, once the dimensions are clean
Receivables and payables aging ledger Automate
KPIs ledger plus your definitions Automate the arithmetic; own the definitions
Covenant calculations ledger plus the loan agreement Automate the calculation; review the reading
Executive summary, variance explanations, outlook, decisions management Review — this is the pack

The ledger half: what to automate.

NetSuite has the parts. Financial statements sit under Reports > Financial; the Financial Report Builder changes their columns, filters, sorting and layout; on OneWorld each subsidiary's statements run in that subsidiary's base currency, and the parent's run consolidated. Saved searches produce lists, SuiteAnalytics Workbook pivots and charts, and a report can be scheduled to arrive by email.

A realistic native set-up uses each for what it is good at: the Financial Report Builder for the statements, per subsidiary and consolidated; saved searches for the exception lists and the tie-outs below; Workbook for the subsidiary and segment cuts; scheduling to have them waiting the morning after close. What none of them does is assemble the pack, check it against itself, or write a word of it — and that is where the days go.

Pulling the statements is the smallest part of the work worth automating. The larger part is what the analyst does after the pull:

  • The tie-outs. The statements agree with the trial balance. The consolidated figure equals the subsidiaries plus the eliminations. The balance sheet balances. Closing cash on the balance sheet equals closing cash on the cash flow. Each is a check a query can make every month and a person forgets in the month it matters. Automate the aging, then tie it to the A/R account: why A/R aging won't tie to the balance sheet names the five lines that can sit between them.
  • The variance arithmetic. Actual against budget, prior year and prior month, in amount and percentage, for every line.
  • The flags. A written threshold — say, more than 10% and more than a fixed amount — that marks which variances need a sentence. Choosing the threshold is judgment; applying it is not.
  • The charts, redrawn from the same numbers rather than pasted from last month's file.

The judgment half: what stays with you.

A query can say revenue came in 8% under budget and list the customers that make up the gap. It cannot know the largest order slipped because the customer's own year-end moved. Everything on that side of the line stays with the finance team:

  • The executive summary — what the month means, in the order the board should hear it.
  • The variance explanations — why, not how much.
  • One-offs and normalisations. What counts as non-recurring is a policy. Write it down once, apply it the same way every month, and decide the edge cases yourself.
  • The estimates underneath. Accruals and reserves were judged at close; the pack inherits them and should not be the first place anyone questions them.
  • The forecast and outlook.
  • Covenants. The ratio is arithmetic. Whether you are near a threshold, and what you will do about it, is not.
  • The decisions you are asking for.

And the sign-off. A common split is that the controller owns close quality and the integrity of the balance sheet, FP&A owns the budget and forecast context, and the CFO owns the framing. Automation changes how long each of those takes. It does not change who owns them.

Gate the pull: six checks before the automation runs.

This is the part the tooling pages leave out, and the part that decides whether the automated pack can be trusted.

  1. The period is closed, not just locked. Oracle's wording is that closing a period "prevents posting to the general ledger for any dates included in the period, by anyone." Locking A/R, A/P or everything is a step on the way, and a user with the Override Period Restrictions permission can still post to a locked transaction type. A pack pulled from a locked period can be wrong by the time the board reads it — and a closed period can still be reopened, which is what check 6 is for.
  2. Consolidation is finished. On the Period Close Checklist (Setup > Accounting > Manage G/L > Manage Accounting Periods, then the period's Checklist icon) that means Revalue Open Foreign Currency Balances, then Calculate Consolidated Exchange Rates, then Eliminate Intercompany Transactions — the checklist's own order, all three done before the period is closed. A pack pulled before the rates are calculated translates at stale rates; one pulled before elimination counts intercompany revenue as revenue. A pull that is not the report itself also has to follow the report's own rules; Why a saved search won't match NetSuite's P&L reconciles the five that most often differ. NetSuite intercompany eliminations: what breaks works through what the elimination leaves behind, and Intercompany eliminations: a worked example shows a consolidated figure built from the subsidiaries plus the eliminations, line by line.
  3. Every account maps to a line. A GL account opened since last month has to land in a pack line or stop the run. The check is simple: the pack's lines sum to the trial balance.
  4. The layouts have not moved. A financial report layout in NetSuite can be shared across reports, so an edit made for one report changes every report that uses it. Compare the row list with last month's.
  5. The definitions are written down. Every KPI has a written definition and a date it took effect. When one changes, the pack says so and restates the prior period on the new basis.
  6. Last month still says what last month said. Compare the prior period in this pack with the figures you sent last month. A difference is a restatement or a posting into a period that should have been closed, and the board should hear about it from you.

Where scheduled reports need watching.

Oracle documents three behaviours of scheduled reports worth designing around: a report that runs longer than three minutes during peak hours is disabled automatically, emails sent from NetSuite cannot be bigger than 20MB, and if the person who created a schedule leaves, its "from" address cannot be changed. None of these is a reason not to schedule. Each is a reason the pack's first check is that it arrived, complete.

Where Frontier fits.

Frontier takes the ledger half and keeps the working attached to it.

Ask for a figure in plain language and it is computed live off your NetSuite account, with the query and the rows that produced it attached. The statements a pack is built from — income statement, balance sheet, trial balance, direct cash flow, receivables and payables aging, revenue per customer, vendor spend — are fixed queries rather than ones written per question, each checked against a real NetSuite instance before it shipped. Each runs for one subsidiary or consolidated, and is held to one accounting book. Asking the ledger lists them and what each one needs from you. A KPI on your own definitions, or a covenant ratio, sits outside that set: the agent writes the query, it is generated rather than pre-validated, and you read it before the number goes in a pack.

On the platform, the same work can run on a schedule, and a saved result stays exactly as it was computed until someone chooses to run it again — which is the property a board pack needs. It carries through to the deliverable: PowerPoint, Word and PDF materials from reusable layouts and company branding, grounded in the analysis the team reviewed.

Frontier reads NetSuite and does not post to it. It does not close the period, write commentary you have not read, or sign the pack. What it takes off the finance team is the rebuilding; what is left is the reading, the writing and the sign-off — the part worth their days. Its output can be wrong, and the query and rows are attached so that you can check it before it reaches the board.

What to check before relying on any of this.

The NetSuite behaviour described here is Oracle's documentation; your account's features, roles and customisations decide what it actually does. The pack contents are a common shape rather than a standard — your board sets its own. And treat any figure Frontier returns the way the documentation says to: check it before it affects your books, your close or a filing.

Questions this raises

Can a NetSuite board pack be fully automated?
The numbers can; the pack cannot. Statements, budget and prior-period comparisons, segment cuts, aging and KPI arithmetic are the same query every month, and they automate well once the period is closed and the definitions are fixed. The executive summary, variance explanations, normalisations, outlook and sign-off are judgment, and that half is the reason the board reads the pack.
When should the board pack be pulled from NetSuite?
After the period is closed rather than only locked, consolidated exchange rates have been calculated and intercompany eliminations have run. Oracle's documentation notes that closing a period prevents posting to it by anyone, while a user with the Override Period Restrictions permission can still post to a locked transaction type.
What NetSuite limits affect scheduled board reporting?
Oracle documents three worth designing around: a scheduled report that runs longer than three minutes during peak hours is disabled automatically, emails sent from NetSuite cannot be bigger than 20MB, and a schedule's 'from' address cannot be changed after the person who created it leaves.

← All notes

Push the Frontier

Work alongside our team to establish your first operational capabilities, built around the problems that matter most to your business.

Explore the platformTalk to Frontier
FrontierERP

Set a new standard for how businesses operate.

Platform
Solutions
Resources
Company
© 2026 Frontier ERP, Inc.PrivacyTerms