Skip to content
All insights
GrowBusiness CentralExplainerAugust 20, 2026

Cost allocation and intercompany due-to/due-from in Business Central: automating the entries you build by hand

A financial analyst at a multi-entity organization walked us through their accounts payable process, 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.

Imprest Account

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 imprest 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.

Microsoft Dynamics 365 Business Central handles a good chunk of this natively, and it helps to know that the work falls into two separate features. Splitting a cost across accounts and departments is allocation. Charging part of that cost to another legal entity is intercompany. Business Central does both, with different tools.

Allocation Tools

For the split itself, Business Central gives you three ways to define the math once and reuse it.

  • Allocation accounts work on purchase invoices, sales documents, and general journal lines. A fixed allocation account holds a set of destination accounts with a share or percentage for each. A variable allocation account calculates the percentages from statistical accounts, which hold non-financial drivers such as headcount or square footage, so the split moves when the driver moves. Each destination line can carry its own dimensions.
  • Allocation keys on recurring general journals split a journal line by percentage, quantity, or amount. The recurring journal also has a Balance recurring method that takes whatever has accumulated in a pooled account and clears it out across the allocation lines, which is the month-end pattern described below. Note that Microsoft documents allocation accounts as unsupported inside recurring journals, so the two features do not stack: allocation accounts at entry, allocation keys at close.
  • Cost accounting is a separate module that mirrors the general ledger into cost types, cost centers, and cost objects, then runs multi-level allocations on top without touching the ledger. It suits organizations that want management-accounting allocations alongside the books, and it is more setup than most teams in this situation need.

In all three cases, you pick the template, enter the total, and the system writes the lines. You review and post.

Allocation Timing

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 on the purchase invoice line, or an intercompany partner code on the line when the share belongs to another entity
Split at month-end Costs pool in one department, then get shared out later Recurring general journal with allocation keys, using the Balance recurring method to clear the pooled account

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, property, or category, and your allocation and reporting key off the tag. Two settings keep the tagging consistent: a default dimension on a vendor or account fills the tag in automatically, and the Code Mandatory value-posting rule stops a line from posting without one. The recurring journal's Balance by Dimension method then allocates the pooled balance separately for each dimension value, so each department's pool clears to its own targets. Get the tagging discipline right up front and the month-end run becomes a review step.

Intercompany Entries

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's intercompany feature records that debt at the moment you post. Each entity is set up as an intercompany partner, linked to a customer record and a vendor record in the other companies, with a shared intercompany chart of accounts that maps each company's accounts to the others'. From there, Microsoft documents two ways to charge a cost to another entity:

  • On the purchase invoice itself. A general ledger line on the invoice carries an intercompany partner code and the partner's account, so the share is charged to the other entity as part of posting the bill. This is the fit when one company does the purchasing for the group.
  • In an intercompany general journal. The vendor invoice posts on one line, and one line per partner charges each entity its share. This is the fit for a service bought centrally and shared out afterward.

Either way, the paying company posts a receivable from each partner, and a matching transaction goes to the partner's intercompany inbox, where it becomes the payable in that company's books. When all the entities live in the same Business Central environment, automatic acceptance creates the receiving lines for you. A person in the receiving company still posts them. The built-in Intercompany Transactions report lists every posted intercompany entry across the companies, which is the reconciliation most teams build in a spreadsheet today.

The cash movement stays a human decision. Settling the due-to/due-from is a payment, posted through the payment journal like any other, and a cash team that wants to control when money leaves a bank account keeps that click for themselves. If the group also produces consolidated statements, the same intercompany entries feed the consolidation and elimination reports.

WHERE POWER PLATFORM FITS

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. A Business Central license includes the right to use Power Automate with Business Central data, flows can start when a record is posted or changed, and approval flows ship as templates. It extends Business Central with something your own team can maintain.

Configuration Boundary

This team was clear that they want configuration over customization, and that line is worth drawing early. Business Central online takes a major update twice a year, in April and October, and a minor update every month. Custom code lives in extensions that have to stay compatible with each release, and when one doesn't, you are waiting on a developer while your close stalls. Everything described here (allocation accounts, recurring journals, dimensions, intercompany posting, Power Automate flows) is native or low-code. Custom development should be the exception, and when it comes up, it's worth checking AppSource for an app that already solves it.

Next Conversation

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 gaps are. Reach out through our contact form or give us a call, and we'll trade notes on your setup.

See where you stand. Then move forward.

Book a free intro call. We'll talk through where you are today and map a plan for growth, protection, automation, and alignment.

30 minutesNo obligationGet an initial estimate within one week