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 will share the pain points that led them to look at intercompany differently and what they expect Stacks Intercompany to unlock for their finance team.
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, Microsoft Dynamics 365 Business Central and SAP 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 sides, 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 sides, so the pair agrees by design, with nothing stopping each entry from landing in different accounts: short-term loan against long-term, clearing against trade. The difference is absorbed upon elimination and only 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 time the intercompany process took during close
What the co-design process with Stacks looked like
What they expect to be able to do once they know their position every day
What we will demo
The live matrix, every intercompany account matched against open differences
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
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 intercompany account, suggested matches with the agent's reasoning, an FX component isolated, and the adjustment posted back.
Live Q&A with the Stacks team
Intercompany accounts, catch-all against per-pair account structures, multiple currencies, audit support, and who posts in whose books.
Save your seat
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 is visible on any day of the period, what a per-account matrix catches that a net balance hides, and Bloom & Wild's account of the pain points behind their intercompany process and what they expect Stacks Intercompany to change for their business.
HOSTS
Your hosts
Sara Scott
Group Accounting Lead at Bloom & Wild
Owns intercompany across Bloom & Wild's multiple entities and currencies on NetSuite. Covers how the reciprocal view was assembled each period, what was still open at sign-off, and what she expects to change once matching runs continuously.
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 intercompany account, and hear from a finance team that has been running it every close.
