Multi-entity distributor, Distribution
Month-end close for a multi-entity distributor
A worked description of how we would run and automate the close for a distributor with several entities, shared inventory and intercompany trade.

This is a delivery blueprint. It shows how we would run this kind of engagement. It is not a report on a past client, and it makes no claim about results.
The challenge
A business like this typically closes across several legal entities that trade with each other and share a warehouse network. Vendor bills arrive in mixed formats, goods are received before invoices, and accruals are built in spreadsheets by whoever knows the supplier. Intercompany balances disagree until someone traces them by hand, and the controller spends the first days of close chasing inputs instead of reviewing results.
What we would do
Step 1 of 5
Map the close as it runs
We sit with the controller and entity accountants, list every task, owner, input and dependency, and mark where work waits on someone. The output is one close calendar with named owners per entity.
Step 2 of 5
Automate the recurring preparation
We build jobs that pull bank feeds, match receipts to open purchase orders for accrual candidates, and prepare reconciliation workpapers. Accountants review proposed entries instead of building them from scratch.
Step 3 of 5
Fix intercompany at the source
We agree a single intercompany pricing and posting rule, add a matching report across entities, and route differences to the responsible pair of accountants during the month, not after cutoff.
Step 4 of 5
Clean the master data feeding the ledger
We deduplicate vendors, standardize customer and item attributes that affect GL coding, and put change requests through a verified workflow, since bad master data creates repeated close corrections.
Step 5 of 5
Hand over with controls
Each automated step logs what it did, who approved it and what it left open. The controller keeps final approval, and runbooks let the team operate and adjust the process without us.
Tech we would use
- NetSuite or Microsoft Dynamics 365 Business Central
- Python
- Power Query
- Power BI
- Azure Functions
- OpenAI API for invoice field extraction
What we would measure
We baseline these before work starts, so you can judge the engagement against your own numbers.
Days to close
We baseline the working days from period end to controller sign-off per entity before changing anything, then track the same definition each month so improvement is attributable.
Post-close adjustments
We count entries booked after sign-off and record the cause of each, because repeated causes point to the control or master data problem that needs fixing.
Unreconciled items aging
We track open reconciling items by age and account, so old balances surface early and teams can see whether the backlog is shrinking or only moving.
Facing something similar?
Send a few lines about the work. A person reads it and replies within 24 hours.
- support@intelyza.com
- +1 973-706-8910
- We reply within 24 hours



