Business Central Expense Agent Split Expenses: December 2026 Preview, April 2027 Release

What the roadmap entry says​

The roadmap describes a way to divide a single expense into multiple allocations. Each allocation can go to a different expense user, project, department, customer, or expense category. Expense Agent is meant to help define the split and make sure the allocations add up to the original amount.

Each allocation would be recorded separately for reporting and accounting, while staying linked to the original expense. In practice, that suggests a shared cost such as a client dinner or a conference fee could be assigned to several destinations without losing the source receipt. That is an inference from the description, not a documented design.

Timing and scope​

Microsoft states that roadmap dates are estimates and can change. It also says entries may be removed once a feature ships, is cancelled, or is postponed. As of early November 2026, nothing here is available to enable. The entry-specific text comes from the roadmap metadata, so treat the dates as planning guidance, not a commitment.

What Expense Agent does today​

Microsoft Learn describes Expense Agent as an AI-powered agent that handles receipt intake, data extraction, categorization, itemization, and expense line creation, then groups expenses into reports for review and approval. The documentation is marked prerelease and subject to change.

Some details come from the Learn page as captured for this story:

• Employees can submit receipts through a web app or a shared mailbox, and neither route needs a Business Central license.
• Users must review all expenses before submitting a report, because the agent does the extraction and categorization.
• Controllers and approvers can adjust dimensions and project and task numbers.
• If a project number and task number are filled in on a line, posting also creates a Project Ledger Entry.
• Posting creates Expense, Employee, Detailed Employee, and G/L ledger entries.
• The agent consumes Copilot Credits for AI processing. The Learn page puts the cost at 50 credits per receipt.

The Learn page does not cover splitting an expense across allocations. How a split would interact with dimensions, project ledger entries, or posting is not documented.

Itemization is not allocation​

Expense Agent already handles one kind of division. If a category requires itemization, the amount can be split into separate lines, and Business Central requires those amounts to add back up to the expense total. That is how a hotel folio gets broken into room, tax, and parking.

The planned feature is different. Itemization divides an expense by what was bought. The new split divides it by who or what should bear the cost. The roadmap's "add up to the original amount" rule resembles the existing itemization constraint, but the sources don't say the two will share any mechanism.

Existing allocation tools in Business Central​

Business Central already has allocation accounts for general ledger work. Microsoft Learn says they distribute amounts on sales and purchase documents and general journal lines. The split can be fixed or variable.

• Fixed allocations use shares or percentages that stay the same until you change the setup.
• Variable allocations draw on dimensions and statistical accounts, such as headcount or floor space.
• Splitting a rent expense three ways produces three lines to post for the allocation.
• Allocations can be tested with a Test Allocation action, and journals offer a Posting Preview.
• Before posting, you can redistribute an allocation on a line.

That documentation covers G/L and bank account destinations. It does not show that Expense Agent can split an employee expense today. It also doesn't say the planned feature will build on allocation accounts. Third-party partners such as Continia have offered amount-distribution splitting in their own Business Central expense products. That shows the need is real, but it says nothing about Microsoft's design.

Open questions​

The roadmap text leaves several practical questions unanswered:

• Will splits be fixed amounts, percentages, or both?
• How are rounding and foreign currency handled?
• Can a single expense be split across a user, a project, and a customer at once?
• How do split records appear in approvals and in reports?
• Do approvers see the split before the report is approved?
• Will AI-suggested splits cost extra Copilot Credits beyond the current per-receipt charge?
• Does the preview need any tenant configuration?

What finance teams can do now​

1. Identify the expenses you currently split by hand, such as shared travel, cross-department software, or client-billable costs.
2. List the destinations those splits use (projects, departments, customers, or categories) and check whether they match the targets in the roadmap.
3. Review your dimension and project setup, since those fields already drive reporting and posting today.
4. Watch Microsoft's documentation around the December 2026 preview window for prerequisites, limits, and any billing details.
5. Keep human review in the plan. Current documentation says users must validate agent output before submitting, and the roadmap entry makes no claim about eliminating that review.

The idea is sensible. Manual splits are tedious, and a traceable link between the parent expense and its allocations is what auditors want. Until the preview shows how the split is implemented, treat it as a promising roadmap item and not a settled feature.