Skip to main content
Accounstone
Platform Workflow Support

NetSuite Accounting Support

Accounting support for entity-level reconciliations, intercompany schedules and close preparation inside an existing NetSuite environment — not implementation or system configuration.

What buyers usually care about

NetSuite handles complexity. Someone still has to close every entity on time.

Multi-subsidiary structures add recurring accounting work: each entity’s balances need to be reconciled, intercompany differences need to be documented and close status needs to be visible. We work inside your existing NetSuite setup on agreed preparation tasks, while implementation, customization and system administration stay with your NetSuite partner.

Workflows

The Accounting Work Around NetSuite

  • Multi-entity and multi-subsidiary account reconciliations
  • Intercompany balance schedules and difference tracking
  • Source-supported balance-sheet schedules for reviewer handoff
  • Close checklist and unresolved-item tracking
  • Period-close reconciliation and account schedule handoff
  • Preparation of agreed entity-level reporting schedules
Common starting points

Where multi-entity close usually gets stuck

Intercompany

Intercompany balances drift out of sync between entities, and eliminations become a manual chase at every close instead of a routine step.

Consolidation

Currency revaluation, subsidiary-level reconciliations and consolidated reporting all need to be reviewed before group-level numbers can be trusted.

Capacity

Your team knows NetSuite, but recurring reconciliations across every entity keep competing with higher-value review work each close cycle.

Related

Connect NetSuite to the accounting work

What actually goes wrong

The Four Things We Find in a NetSuite File

None of these are software faults. They are accounting failures that the software will accept without complaint, which is what makes them expensive — nothing errors, and the file looks fine.

Intercompany balances that never quite agree

In a multi-subsidiary NetSuite account, intercompany balances can differ between entity records because of timing, missing source entries or inconsistent references. The preparation workflow should compare the available detail, identify unmatched items and return the difference for review rather than insert an unsupported elimination.

Close checklists that live in someone's head

NetSuite has a period-close structure, and plenty of accounts run the close outside it anyway, on a spreadsheet the controller maintains. It works while that person is there. The failure mode is not the spreadsheet — it is that nobody else can tell what has actually been done this month.

Reports that do not tie back to source records

An entity or close report is only useful when its totals can be traced to the underlying ledger and supporting schedules. The preparation handoff should identify the report used, the period and entity covered, and any difference that needs the controller’s attention.

Subsidiary-level detail lost to consolidated habits

Where the routine is built around the consolidated view, subsidiary-level reconciliation slips. Each entity still needs its own accounts to stand up on their own — for a local filing, an audit, or a buyer — and rebuilding that from a consolidated position is far more work than maintaining it.

The recurring routine

What Runs Every Month

  • Bank and balance-sheet account reconciliation per subsidiary, not only consolidated
  • Intercompany balances compared across available entity records, with differences documented for review
  • Period-close checklist worked inside NetSuite, so status is visible to more than one person
  • Supporting account schedules prepared from firm-approved instructions and available source records
  • Agreed entity-level report totals checked against the source ledger and supporting schedules
  • Entity-level reconciliation schedules and agreed close reports prepared for review
NetSuite FAQs

Frequently Asked Questions

Can you support a multi-subsidiary NetSuite account?

Yes, and the part that matters most is reconciling per subsidiary rather than only at the consolidated level. Each entity still needs accounts that stand up on their own for a local filing, an audit or a buyer, and rebuilding that from a consolidated position later is much more work than maintaining it.

Do you configure or customise NetSuite?

No. Implementation, configuration, scripting and workflow customisation are a specialist discipline and not one we claim. We work inside an account that already runs — reconciliation, close, intercompany and reporting preparation.

How do you handle intercompany?

Compare the available due-to and due-from balances, transaction references and period detail for each entity in scope. Record unmatched items and the source information available, then return unresolved differences to the controller or CPA for a decision.

Our close runs on a spreadsheet outside NetSuite. Is that a problem?

It works until the person maintaining it is unavailable, and then nobody can tell what has been done this month. We work the close inside NetSuite's own period structure so status is visible to more than one person, without changing what the close actually contains.

Can you take on just part of the NetSuite work?

Yes. A common split is that we take reconciliation and the recurring close preparation while your controller keeps ownership of judgment, review and anything client- or board-facing. The boundary gets written down at onboarding rather than assumed.

What about our saved searches and management reports?

We can organize and reconcile the source reports supplied for the agreed workflow. Changes to saved-search definitions, segment structures or report configuration remain with the client’s NetSuite administrator; accounting differences are documented for the responsible reviewer.

Can you prepare a period-close package inside an existing NetSuite account?

Where the task list and access allow, preparation can include subsidiary-level reconciliations, intercompany schedules, supporting accrual or prepayment schedules and a close-status handoff. The controller or responsible CPA retains review and approval of accounting judgments.

How are differences between a subsidiary ledger and consolidated reporting handled?

Compare the subsidiary records and available close reports, document unmatched items and identify which source records are needed to explain the difference. Mapping, currency and consolidation decisions remain with the responsible controller or specialist.

Can you maintain reconciliations without changing NetSuite configuration?

Yes. Accounting preparation can take place inside an existing account using the approved workflow, without claiming implementation or configuration support. If the issue requires a script, workflow change, role change or platform configuration, it should be referred to the client’s NetSuite administrator or implementation provider.

What system access is needed for NetSuite accounting support?

Access should be confirmed for the subsidiaries, periods, reports and tasks in scope, with the client retaining control of roles and permissions. The engagement should specify required exports or reports, review outputs and escalation steps before processing starts.

Free consultation

Talk to Us About Your NetSuite Close

Tell us how many entities consolidate, and which part of the close keeps slipping.

The consultation and the call are always free. We will agree the workflow, handoffs and deadlines during onboarding.

Where Is Your Multi-Entity Close Getting Stuck?

Tell us whether the pressure is intercompany eliminations, consolidation or simply keeping every entity's close on schedule.