NetSuite 2026.1 Consolidated Reports: MCP Subsidiary Selection

Use ns_getSubsidiaries and ns_runReport to select consolidated or context subsidiaries for reports from an AI client. Learn what negative internal IDs mean and how to verify the report’s scope.

·7 min read·By NetSuite Changelog

NetSuite 2026.1 consolidated reports let AI-client users select consolidated or context subsidiaries through the MCP Standard Tools SuiteApp. Retrieve the choices with ns_getSubsidiaries, then use the appropriate negative internal ID with ns_runReport for a report that supports consolidations.

The important decision is which view the requester needs: the selected subsidiary and all its children, or accessible child-subsidiary data presented in a chosen context subsidiary’s currency.

Key takeaways

  • MCP Standard Tools SuiteApp version 1.0.6 introduced consolidated and context subsidiary reporting functionality.
  • ns_getSubsidiaries returns individual, consolidated, and context subsidiaries. Individual IDs are positive; consolidated and context IDs are negative.
  • Use the applicable returned negative ID with ns_runReport when the report supports consolidations.
  • Consolidated reports include the selected subsidiary and all child subsidiaries. Context reports show accessible child-subsidiary data in the chosen context subsidiary’s currency.
  • A negative ID alone does not distinguish a consolidated choice from a context choice.

What does NetSuite 2026.1 add to MCP reporting?

The enhancement supports consolidated and context subsidiary selection when generating reports from an AI client. It connects two tools: ns_getSubsidiaries supplies subsidiary choices, and ns_runReport runs reports using the applicable selection.

This article covers that MCP reporting workflow, rather than a standard reporting UI procedure or a consolidation query written in SuiteQL. Frame the task as subsidiary discovery followed by report execution. A familiar subsidiary name is not enough: the requester must also decide between consolidated and context scope.

For the broader data-access context, see consolidated reporting and SuiteQL in NetSuite. The workflow below focuses on report selection rather than constructing a custom query.

Prerequisites: define the report before selecting an ID

“Run the group report” leaves the most important choice unresolved. Ask whether the requester wants the selected subsidiary plus all its children, or accessible child-subsidiary data presented in a chosen context currency.

Prepare these items:

  • An AI-client workflow using the MCP Standard Tools SuiteApp. Version 1.0.6 introduced the subsidiary-reporting functionality described here.
  • Access to ns_getSubsidiaries and ns_runReport. These provide subsidiary discovery and report execution.
  • A report that supports consolidations. The documented use of negative subsidiary IDs depends on this requirement.
  • An agreed scope. Decide between consolidated and context reporting before selecting an ID.
  • A review expectation. For a context report, identify the intended context subsidiary and its currency, and consider which child subsidiaries the reporting user can access.

Treat these as separate decisions. A subsidiary choice returned by the discovery tool does not establish that every report supports consolidations. Likewise, selecting a report does not settle which subsidiary scope the requester intended.

Identify subsidiary options with ns_getSubsidiaries

1. Retrieve the available choices

Use ns_getSubsidiaries from the AI client. The tool returns individual, consolidated, and context subsidiaries.

Review the returned choices before running the report. Keep enough information in your working notes to connect the intended subsidiary selection with its internal ID. This is a recommended review practice, not a prescribed response schema or a requirement to use particular output field names.

2. Interpret positive and negative IDs

Returned subsidiary category Internal ID sign Reporting meaning
Individual Subsidiaries Positive An individual subsidiary rather than a consolidated or context selection.
Consolidated Subsidiaries Negative The selected subsidiary and all child subsidiaries.
Context Subsidiaries Negative Accessible child-subsidiary data in the chosen context subsidiary’s currency.

The sign provides an initial distinction, not a complete scope definition. Both consolidated and context subsidiaries use negative IDs. Selecting the first negative ID associated with a familiar name therefore leaves room for choosing the wrong reporting view.

3. Match the returned choice to the request

For a consolidated request, select the consolidated subsidiary choice. For a context request, select the context subsidiary whose currency matches the requested presentation.

Use the applicable ID returned by the tool. Do not attempt to manufacture a consolidated or context ID by negating an individual subsidiary’s positive ID; that is not the workflow described in the source.

For additional context when documenting the decision, see consolidated and context subsidiary reporting.

Run the report with ns_runReport

4. Check consolidation support

Confirm that the intended report supports consolidations before using the selected negative ID with ns_runReport. Keep this check distinct from subsidiary discovery: one concerns the report’s support, while the other concerns the requested scope.

5. Use the selected negative ID

Request the report through ns_runReport using the applicable negative internal ID from ns_getSubsidiaries. Preserve the distinction between the report being requested and the subsidiary selection applied to it.

For a consolidated report, the intended scope is the selected subsidiary and all child subsidiaries. For a context report, the intended scope is accessible child-subsidiary data, formatted in the currency of the chosen context subsidiary.

Worked example: ask for two distinct views

Suppose a finance requester wants both views for review. Rather than asking for “the parent report” twice, make the difference explicit. The following natural-language template illustrates the selection sequence; it is not an API request schema. Supply the actual report request and use IDs returned in your own session.

Use ns_getSubsidiaries to retrieve the available subsidiary choices.
Help me identify the consolidated and context options and their
returned internal IDs. Pause before running either report so I can
confirm the selections.

First view:
- Use my selected consolidated subsidiary choice.
- Confirm that the requested report supports consolidations.
- Run it with ns_runReport using the applicable returned negative ID.
- Intended scope: the selected subsidiary and all child subsidiaries.

Second view:
- Use my selected context subsidiary choice.
- Confirm that the requested report supports consolidations.
- Run it with ns_runReport using the applicable returned negative ID.
- Intended scope: child-subsidiary data accessible to my user,
  formatted in the chosen context subsidiary's currency.

Keep the selected subsidiary choices and IDs in the review notes
so I can compare them with the discovery results.

The pause is a suggested administrative safeguard, not a documented tool-enforced approval step. Its purpose is to expose an ambiguous scope choice before execution. It also gives the requester an opportunity to distinguish a currency-context requirement from a request for the selected subsidiary and all children.

Verify scope and currency after execution

The following checks are a recommended review process. The source describes report behavior; it does not establish an automatic verification feature that certifies the requested scope.

Start with the selection used, then assess the result. A plausible total alone does not demonstrate that the correct subsidiary category was selected.

  1. Compare the ID with the discovery result. Check that the negative ID used with ns_runReport corresponds to the intended consolidated or context choice returned by ns_getSubsidiaries.
  2. Recheck report support. Confirm that the report supports consolidations rather than treating a returned subsidiary option as proof of compatibility.
  3. Review consolidated scope. Compare the result with the expectation of the selected subsidiary and all child subsidiaries.
  4. Review context accessibility and currency. Compare the contributing child subsidiaries with the user’s access, and the presentation currency with the chosen context subsidiary.
  5. Retain review notes. Record the report identity, subsidiary category, and returned ID so another reviewer can understand the selection.

For an administrator investigating missing context data, child-subsidiary accessibility is a relevant check before concluding that reporting is defective. For a business analyst investigating an unexpected currency, start with the chosen context subsidiary rather than assuming that the underlying data is wrong.

These checks address selection and scope, not the correctness of every financial amount. Keep that distinction when preparing an AI-generated narrative report summary: an explanation of results is separate from evidence that the intended subsidiary choice was used.

Troubleshoot the decision, not the ID sign

If a result differs from the request, return to the specific decision that could explain the difference.

Review finding Next check
The requester wanted the selected subsidiary and all children Verify that the selected choice was consolidated rather than context.
The context currency is unexpected Review which context subsidiary was chosen.
Expected child-subsidiary data is absent from a context report Check whether that child subsidiary is accessible to the reporting user.
A negative ID was selected, but report suitability remains unclear Recheck whether the requested report supports consolidations.

These are diagnostic starting points, not an exhaustive list of causes. Avoid changing IDs experimentally: first establish whether the issue concerns category, context currency, accessibility, or report support.

FAQ

Does a negative subsidiary ID always mean consolidated reporting?

No. Both consolidated and context subsidiaries have negative internal IDs. Review the actual choice, not just its sign.

Are context reports simply consolidated reports in another currency?

That description misses the scope distinction. Consolidated reports include the selected subsidiary and all child subsidiaries. Context reports show data from child subsidiaries accessible to the user, formatted in the chosen context subsidiary’s currency.

Do I need to write a SuiteQL query for this workflow?

The workflow described here uses ns_getSubsidiaries and ns_runReport. The source separately describes ns_getSuiteQLMetadata for retrieving SuiteQL record metadata; that is a different task from selecting a subsidiary for these reports.

Related reading

For Oracle’s reporting reference, see Report Tools.