NetClose - Flux Analysis Tips and Troubleshooting

Overview

This article collects practical tips for working with NetClose Flux Analysis, fixes for the issues we see most often, and a reference for the background scripts that run the module. If your flux is showing only parent accounts, a submitted analysis reverted to Not Started, the Submit or Approve button is greyed out, or a scenario won't generate, start here.

Tips

Set flux up in order before you generate. Flux Analysis has a setup chain, and generation fails or comes back empty when a step is skipped. Work through it in this order: set up your flux accounts, set up flux account groups, create a flux scenario, then generate the scenario. If the comparison-period fields are greyed out or you get "Missing required parameter" on generate, the scenario itself isn't fully configured.

Decide how summary accounts should roll up before your first generate. The Include Subaccount Activity field on the Setup Flux Accounts page tells NetClose to create a single flux record for the parent and fold the child activity into it - so the children won't appear as their own lines. Leave unchecked if you want individual child-account flux records.

Set thresholds so only material lines need an explanation. On the flux scenario, set a balance sheet and/or income statement threshold (amount, percent, or both). If a scenario has no thresholds at all, every line requires an explanation - including lines with a $0 change. A threshold of even $0.01 excludes zero-change lines. Use the quick filters on the Review Flux Analysis page (Explanation Needed, Balance Changed) to work only the lines that matter.

Default preparers and reviewers come from your account mapping. The preparer and reviewer stamped on each generated flux line are pulled from the defaults on the Setup Flux Accounts page (also reachable as Setup > Flux Analysis Account Mapping). Set them there before you generate; reviewers can be multi-selected. To view or change who is assigned by account, department, or subsidiary, use the pencil icon on that page.

Expect a submitted flux to reopen if its balance changes. By design, if a flux is Submitted for Review or Complete and the underlying GL balance changes, the next balance refresh sends the status back to Not Started, notifies the preparer and reviewer, and flags the line with a yellow "balance changed" icon. This protects your close - it isn't a bug. See Refresh Flux Balances and Real-Time Updates. If the notifications are noisy, you can turn them off (see FAQ).

Keep scenarios lean for speed. A single scenario spanning all accounts across every department and subsidiary creates a large number of records, which slows generation and the Review page. Split broad analyses into a few narrower scenarios, and inactivate scenarios you no longer use. Flux runs on NetSuite Map/Reduce, so generation time also depends on your account's concurrency and what else is running.

Stay on the latest SuiteApp version

More flux issues are resolved by a version update than by any single setting. Fixes for duplicate flux records, threshold values changing on generation (10% becoming 0.1%), decimal-rounding false balance changes, wrong auto-generated periods, and status incorrectly reverting have all shipped in NetClose SuiteApp updates. Netgain updates production versions - if you suspect you're behind, or a fixed behavior is still happening, contact support to confirm your version.

Troubleshooting

Issue	What to check
Flux is showing only parent accounts, or child accounts aren't generating.	Check: Include Subaccount Activity on the Setup Flux Accounts page. If checked, child accounts roll up into the parent account and do not generate their own flux. To restore individual child-account flux, uncheck the setting on the relevant parent accounts and regenerate the scenario. An inactive parent/summary account can appear in place of active children; consolidated hierarchies keep inactive summary accounts in scope.
A submitted or approved flux reverted to Not Started.	Check: by design, a balance change on a Submitted-for-Review or Complete line reopens it on the next refresh and notifies the preparer and reviewer. Confirm the GL balance actually moved. If the balance did not change, make sure you're on the latest SuiteApp version - a decimal-rounding defect and a revert defect that caused false balance changes were both fixed. After updating, submit and approve again; it should hold. To stop the balance-change emails and on-screen alert, see the FAQ ("How do I stop the flux balance-change notifications?").
The Submit button is greyed out after clicking Start.	Check: The Enforce Preparer setting under NetClose > Setup > System Setup - when on, only the flux line's assigned preparer can submit it for review. Confirm the person submitting is the preparer. The user's NetClose Flux permission is Edit level or higher - see Permissions Overview. The period and the Flux module aren't locked in Close Control.
The Approve button isn't appearing for a submitted flux (only Restart).	Check: The reviewer's NetClose Flux permission level and that they are set as the reviewer on the line. There is no separate "Reviewed" button by design - reviewer actions are Approve, Reject, Restart, and Reopen. If approve is missing on records that also have a roll-up problem, resolve the consolidation setting above and regenerate, then confirm you're on the latest version.
The scenario won't generate - blank page, spinner, or "Missing required parameter."	Check: The full setup chain is complete: flux accounts, flux account groups, those groups added on the GL accounts, and a saved flux scenario. The scenario's comparison-period fields are populated. If they're greyed out, the scenario's date configuration (relative or fixed periods) isn't set. The Flux module isn't locked in Close Control for the period. The NetClose \| Flux Generate \| MR job status (see Viewing Script Errors).
The generated flux doesn't match the template (for example, a 10% threshold becomes 0.1%).	Check: You're on the latest SuiteApp version - this was a defect and is fixed. Regenerate the scenario from the template after updating. The template value is entered as the whole number (10 for 10%, not 0.1), and no account-level Override Percent Threshold is reapplying a different value.
Auto-generate ran but pulled the wrong periods, or didn't run.	Check: The Auto Generation Period on the scenario. For relative scenarios it should be Current Period; Previous Period pulls a period earlier than expected. You're on the latest version - a "Cannot read property 'id' of undefined" error in the auto-generate MAP stage (a relative date range that matched no posting period) was fixed. The target accounting periods exist and are marked as posting periods, so the relative range can resolve. The NetClose \| Flux Auto Generate \| MR deployment is scheduled and its run day accounts for your time zone versus NetSuite server time.
Refreshing balances creates duplicate flux lines instead of updating them.	This is generally caused by a change in the set of accounts assigned to a flux group from original generation to the refresh. Check: You're on the latest SuiteApp version - duplicate-on-refresh was a defect and is fixed. After updating, delete the duplicated scenario (NetClose > Flux Analysis > Flux Scenario > View > Delete Scenario, type CONFIRM) and regenerate. The Real-Time Balances section should then appear and refresh should update lines in place.
Preparers and reviewers didn't populate on the generated lines.	Check: Defaults are set on the Setup Flux Accounts page for those accounts. You're on the latest version - a defect where account-level generation didn't apply the defaults was fixed. Regenerate the scenario after updating.
Flux Analysis is slow to load or takes hours to generate.	Check: How many active scenarios you have - inactivate old ones to declutter the Review page. Whether one scenario covers all accounts across every department and subsidiary; split it into narrower scenarios. NetSuite concurrency and other Map/Reduce jobs running at the same time - flux generation shares that capacity. For very large transaction volumes, the underlying NetSuite transaction query can time out; a tighter scenario scope helps.

Viewing Script Errors

Everything Flux Analysis automates - generating scenarios, auto-generating, refreshing balances, and sending notifications - runs as NetSuite scripts. When something doesn't happen, the script log usually says why.

To view logs across all scripts:

Go to Customization > Scripting > Script Execution Logs.
Filter Type to Error (and Date to today) to see only failures.
Read the Details column for the message.

To check a specific job:

For the Map/Reduce jobs (anything ending in | MR), open Customization > Scripting > Map/Reduce Script Status to see whether the run is Pending, Processing, Complete, or Failed.
Or open the script directly at Customization > Scripting > Scripts, click the script, open its Deployments, and review the Execution Log subtab.

NetClose writes errors in the form script id | stage | error name: message (for example, customscript_nact_generate_flux_mr | MAP | ...), so the log tells you which script and which phase failed.

If you have the Netgain Tools SuiteApp, there's a faster way.

The Netgain Tools SuiteApp - the same one that delivers Shared Transactions and Cross-Validation Rules - adds Netgain's own log viewer at Netgain > Development > Script Logs. It reads the same execution logs but is built for troubleshooting: you can search the log message text directly (an error name or a record ID), filter across several scripts, log types, and a date range at once, and see timestamps in your local time instead of server time. A companion Scripts view lists every script with its deployments and log levels. The Netgain menu only appears when that SuiteApp is installed, so it is not available on a NetClose-only account.

When you contact support

Copy the full error text from the Details column and note the script name and the timestamp. With the script, stage, and message - plus the scenario, period, and subsidiary involved - Netgain support can pinpoint the cause quickly. To grant access for a support case, see NetClose - Providing Access to NetSuite Account for Support Cases.

Flux Analysis Scripts

These are the scripts behind the Flux Analysis module. You don't run them by hand - NetClose triggers them from the flux pages or on a schedule - but knowing what each one does helps when you're reading a log or asking support a question. Find any of them at Customization > Scripting > Scripts, searching by the name below.

Script (NetSuite name)	Type	What it does	When it runs
NetClose \| Flux Generate \| MR	Map/Reduce	Creates flux analysis records from your flux scenarios and refreshes their balances	When you click Generate on the Generate Flux Scenario page or Submit on Refresh Flux Balances
NetClose \| Flux Auto Generate \| MR	Map/Reduce	Auto-creates flux scenarios for new periods without a manual click	On its scheduled deployment
NetClose \| Flux Email Automation \| MR	Map/Reduce	Sends flux notification emails (assignment, balance-changed, and review triggers)	On its scheduled deployment
NetClose \| Flux App \| SL	Suitelet	Serves the Setup, Generate, Review, and Refresh flux pages	Whenever you open a Flux Analysis page
NetClose \| Flux Analysis \| UE	User Event	Maintains flux analysis record status, explanation-required state, and balance-changed flags as a record is saved	Automatically when a flux analysis record is created or edited
NetClose \| Flux Scenario \| CS / UE	Client / User Event	Drive validation and field behavior on the flux scenario form	Automatically while you work with a flux scenario
NetClose \| Flux Group \| CS / UE	Client / User Event	Maintain flux account group records	Automatically when a flux group is saved
NetClose \| Flux Analysis / Flux Scenario / Ad Hoc Flux Analysis \| MCP	MCP tool	Expose flux data, scenarios, and ad-hoc variance to AI assistants via the Netgain MCP integration	When an AI assistant queries or runs flux

Several other user-event and client scripts also run automatically as you work in the module.

Frequently Asked Questions

Question	Answer
How does NetClose decide which flux lines need an explanation?	By the thresholds on the scenario. If you set a balance sheet or income statement threshold (amount, percent, or both), only lines that meet it require an explanation. If a scenario has no thresholds, every line requires an explanation - including $0-change lines. Set a small threshold (even $0.01) to exclude zero-change lines. NetClose never auto-completes a line; moving a line to Complete is always user-initiated.
Why did my submitted (or approved) flux go back to Not Started?	Because the GL balance behind that line changed. When a Submitted-for-Review or Complete flux has a balance change, the next refresh reopens it to Not Started, notifies the preparer and reviewer, and flags it with a yellow "balance changed" icon so nothing approved on stale numbers slips through. If the balance did not actually change, update to the latest SuiteApp version - rounding and revert defects that caused false balance changes have been fixed.
How do I stop the flux balance-change notifications?	Go to NetClose > Setup > System Setup > System Features, and under the Flux Analysis section check Disabled Flux Balance Change Notifications, then Save. If you don't see the setting, you may be on an older version - contact support to update. This stops the emails and the alert; the balance-change flag still appears on the line.
Can I bulk-update flux status by CSV import?	No. Flux analysis status can't be mass-updated by CSV or from a NetClose page - there's no status field to map on import, and status is changed on each record. As a workaround, use the quick filters on the Review Flux Analysis page (Explanation Needed, Balance Changed) to process only the lines that need action.
Can I export both the primary and alternate explanations, or share flux results with someone who doesn't have a license?	The export on the Review Flux Analysis page includes the primary explanation only. To pull additional fields (alternate explanations, reviewer, status) or to hand results to a viewer without a license, build a NetClose Flux saved search with the columns you want and export it to Excel.
Do AI-generated explanations go straight into the primary explanation?	No. On the flux scenario record, you can mark "Copy AI Explanation to Primary Explanation" to automatically copy it. AI flux is available whenever Flux is enabled. See AI Generated Flux Analysis.
Why is the Trending Periods field greyed out?	Because the scenario has a relative date set. When a scenario uses relative periods, comparison periods are calculated at run time, so Trending Periods is disabled to avoid a conflict. Use a fixed-period scenario if you need trending columns.
Does the Review Flux Analysis page remember my sort and filters?	Not currently. Filters and sort on the Review page clear when you leave the page, and re-sorting is needed when you return. A common workaround is to bookmark the page after applying your filters. Persistent sort is a logged enhancement request.
How do I see or change who's assigned to flux lines?	Go to NetClose > Setup > Flux Analysis Account Mapping (Setup Flux Accounts). It lists assignments by account, and you can filter by department or subsidiary when segment grouping is enabled. Use the pencil icon to change the default preparer or reviewer, then regenerate for the change to flow to new flux records.

Still Need Help?

If these steps don't resolve the issue, or you're seeing an error that isn't covered here, contact Netgain support at support@netgain.tech. Include the script name, the error message and timestamp from the execution log, and the scenario, period, and subsidiary involved. Keeping your SuiteApp up to date also resolves many flux issues, since fixes ship in updates.

Was this article helpful?