A financial analyst at a multi-entity organization walked us through their accounts payable process recently, and one theme kept coming up: their team spends a lot of hours doing math the system should be doing. They pay bills out of one bank account, charge the other entities for their share, and then someone sits there calculating the split and keying it into the general ledger by hand. If that sounds like your close, this one's for you.
The impress-account problem
Here's the setup. You have several legal entities that share back-office costs. To keep things simple, you pay accounts payable out of one bank account (sometimes called an impress or clearing account), then you charge each entity for its portion. The trouble starts when someone has to figure out that portion. On every allocated invoice, a person calculates who owes what, then types the general ledger accounts and dollar amounts in one line at a time. It works, but it's slow, and manual keying invites errors.
Business Central handles a good chunk of this natively. Allocation accounts and recurring general journals let you define a split once (by percentage, by fixed amount, or by a driver) and apply it when you post. You pick the allocation template, enter the total, and the system distributes it across the accounts and entities for you. You review and post rather than compute and key.
Split now or split at month-end
One useful distinction this team drew: some costs should split the moment AP enters the invoice, and others should sit in a pooled account and allocate at month-end. Both are legitimate, and you don't have to pick just one.
| Approach | When it fits | How Business Central supports it |
|---|---|---|
| Split at entry | You know the allocation the moment the bill arrives | Allocation account or a coded distribution on the purchase invoice |
| Split at month-end | Costs pool in one department, then get shared out later | Recurring allocation journal run at close, driven by the pooled balance |
The catch with month-end allocation is that the invoices going into the pool need to be flagged so the close process knows which ones to pick up. In Business Central, dimensions do that flagging. You tag an invoice with the department, event, or category, and your allocation and reporting keys off the tag. Get the tagging discipline right up front and the month-end run becomes review-and-post instead of hunt-and-calculate.
The settlement entry and the cash side
After you allocate, each entity owes the paying entity. That's your due-to/due-from. Today this team runs a report, drops it in a spreadsheet, and turns it into a manual transfer request for the cash team. Business Central can generate the intercompany settlement entries from the allocation, which removes the spreadsheet middle step. The actual cash movement stays a human decision, as it should. A cash team that wants to control when money leaves a bank account is right to keep that click for themselves.
When the request is really a routing problem (a transfer form that should notify the cash team and land as a draft entry), that's often a low-code Power Automate flow, not custom code. It extends Business Central without locking you into something only your partner can maintain.
A note on customization versus configuration
This team was clear that they want configuration over customization, and they're right to draw that line. The reason matters: heavy custom code can break when the platform updates, and then you're waiting on a developer while your close stalls. Most of what we've described here (allocation accounts, recurring journals, dimensions, intercompany posting) is native or near-native. Some routing and notification pieces are low-code Power Platform work you can maintain yourself. Genuine custom development should be the exception, and when it comes up, it's worth asking whether a third-party app already solves it.
Talk it through
If your multi-entity close runs on spreadsheets and rekeyed allocations, we're happy to walk through how much of it maps to native Business Central and where the honest gaps are. Reach out through our contact form or give us a call, and we'll trade notes on your setup.