MASTERCLASS

MASTERCLASS

NetSuite and Dynamics 365 BC won't build your intercompany matrix. Stacks agents do.

NetSuite and Dynamics 365 BC won't build your intercompany matrix. Stacks agents do.

NetSuite and Dynamics 365 BC won't build your intercompany matrix. Stacks agents do.

KNOW YOUR INTERCOMPANY POSITION IN REAL TIME

KNOW YOUR INTERCOMPANY POSITION IN REAL TIME

KNOW YOUR INTERCOMPANY POSITION IN REAL TIME

Every close, intercompany goes back into Excel: balances pulled from the ERP, a matrix built and colour-coded by hand, then worked line by line to find the difference, in a workbook with no controls. Most of the week goes into finding the break rather than fixing it.

Bloom & Wild ran intercompany the same way, in a spreadsheet rebuilt every month across their entities. Their team will share what changed when Stacks Intercompany agents took over the matching and kept the matrix live per entity pair and per account, and what it means to see their position every day.

Free 45-minute live masterclass

Tuesday, October 13 at 4pm BST / 5pm CET

ABOUT THE MASTERCLASS

What you'll learn

Why the matrix still gets built by hand

NetSuite and Microsoft Dynamics 365 Business Central report per subsidiary, so the reciprocal view gets assembled outside the ERP. Whichever intercompany posting routine you run covers only what goes through it, leaving invoices, bills, credit notes and manual journals with nothing linking the two legs, and the counterparty tag is only as reliable as whoever keyed it.

Balanced at the total, wrong at account level

A two-sided intercompany journal posts both legs, so the pair agrees by design, with nothing stopping those legs landing in different accounts: short-term loan against long-term, clearing against trade. The difference is absorbed on elimination and surfaces when someone ties the loan schedule, or the auditor asks for support.

FX noise, aged differences and audit support

Across five or more currencies small differences are constant even when both sides posted correctly, so we match on transaction currency and flag the reporting-currency difference as the likely cause. Every match, suggestion and adjustment is logged, so an aged balance and the support behind it come out of the log instead of an email thread.

What Bloom & Wild will share

  • How much of the close intercompany took, and where their differences came from

  • What changed once the agents took over the matching

  • What the team does with the position known every day

What we will demo

  • The live matrix, every entity pair matched against open differences, filtered per intercompany account

  • Auto-matches on amount, reference and memo, with suggested matches carrying the agent's reasoning

  • An amount mismatch isolated, the FX component identified, and the adjustment posted back into the ERP

  • One intercompany account per entity pair or a single catch-all carrying the counterparty tag, both handled

Your ERP stays the source of record

Stacks reads from your ERP and posts adjustments back, with no separate intercompany ledger holding a second copy of the data, and each entity's team keeps working its own books. Setup is confirming the intercompany accounts we detect.

AGENDA

The Agenda

Bloom & Wild: intercompany before Stacks

Where the close time went, how differences were found, and what had rolled forward by the time the auditors asked for support.

What the agents changed

How differences get caught as transactions post, and what a position that holds on any day does to the close calendar.

Live demo: the matrix, the differences, the adjustment

The matrix on live ERP data per entity pair and per intercompany account, suggested matches with the agent's reasoning, an FX component isolated, and the adjustment posted back.

Live Q&A

Entity pairs, catch-all against per-pair account structures, multiple currencies, audit support, and who posts in whose books.

Save your seat

See the matrix maintained per entity pair and per intercompany account, and hear from a finance team that has been running it every close.

See the matrix maintained per entity pair and per intercompany account, and hear from a finance team that has been running it every close.

Who This Is For

Controllers, group controllers and heads of accounting at groups of entities across several currencies, where the reciprocal view is rebuilt in Excel each period, differences are chased over email, and the support gets reassembled for the auditors.

What You'll Walk Away With

What intercompany looks like when matching runs as transactions post, so the position holds on any day of the period, what a per-account matrix catches that a netted pair balance hides, and Bloom & Wild's account of how Stacks Intercompany reduces risks to their business.

HOSTS

Your hosts

Sara Scott

Group Accounting Lead at Bloom & Wild

Owns intercompany across Bloom & Wild's [n] entities and [n] currencies on NetSuite. Covers how the reciprocal view was assembled each period, what was still open at sign-off, and what changed once the matching ran continuously.

Mari Kubo

Group Financial Control & Reporting Lead at Bloom & Wild

Owns group reporting and the control environment, including what intercompany has to look like before consolidation and audit.

Freddie Higgs

GTM at Stacks

Demonstrates an intercompany position that holds on any day of the period: the matrix per entity pair and per account, why the agent proposed each match and what blocked an automatic one, and the adjustment posted back into the ERP.

Save your seat

See the matrix maintained per entity pair and per intercompany account, and hear from a finance team that has been running it every close.