You’re offline. This is a read only version of the page.

Dynamics 365 CommunityForums Finance | Project Operations, Human Resources, ... D365FO - Transaction d...

Finance | Project Operations, Human Resources, ...

D365FO - Transaction date on expense reports grouped by voucher date

(1) Share

Report

Posted on by Adis

6,602 Super User 2026 Season 1

Dear all,

I have the following case.

An expense report with multiple lines and transaction dates, belonging to one voucher.

When I check the voucher transactions, the voucher is posted in accounting with the latest transaction date, which is 7th of May here.

I am wondering if there is any setup that defines how the transactions are being grouped by. I would like to have one voucher per month, or one voucher per day. Right now, it seems that one expense report is one voucher.

However, I ve also seen one expense report with different vouchers, actually there was one expense, out of many, that was posted with a different voucher and I dont understand the logic behind it.

Maybe someone has some idea in this case?

Thanks in advance, Adis

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Saif Ali Sabri

2,354 Moderator on at

Like (0)

Report

Copy link

Link copied!

Yes, your observation is correct—Dynamics 365 Finance and Operations (D365FO) groups and posts expense report lines into vouchers based on specific posting rules and configurations. Here's a solution-oriented explanation that clarifies how this works and how you can control the grouping behavior:

✅ Understanding the Current Behavior
In your case:

You have one expense report containing multiple expense lines with different transaction dates.
All lines are grouped into a single voucher (TEV000052299), and the posting date (voucher date) in the general ledger reflects the latest transaction date on the report (07.05.2025).

This is expected when the system is configured to group all lines from a single expense report into one voucher.

🔍 Why Does One Expense Report Sometimes Generate Multiple Vouchers?
This happens due to variations in:

Expense types and posting profiles
Payment methods
Project/financial dimension differences
Date grouping behavior during posting
Manual edits or corrections

In your example, when one expense line was posted with a different voucher, it likely had a different combination of project, ledger dimensions, or configuration that triggered separate voucher creation.

🛠️ How to Control Voucher Grouping Behavior
To control how D365FO groups transactions into vouchers (e.g., one per day, one per month), check the following:
1. Expense Report Posting Configuration
Navigate to:
Expense management > Setup > General > Expense report header fields
Make sure to evaluate:

Posting setup per expense category
Posting per transaction vs per report

D365FO by default groups by report, but you can configure it differently via customization or posting profiles.

2. Ledger Posting Setup
Go to:
Expense management > Setup > Expense management parameters

Under the Posting tab, check the settings for how expense transactions are posted.
Consider whether the system is configured to aggregate or split posting by category, date, or another field.

3. Customization via Posting Classes
If you want full control—e.g., post:

One voucher per day
One voucher per month
Or split based on transaction date

Then customization is required via X++ logic in the LedgerPostingService or class that handles expense report posting. This approach allows you to apply logic like:
x++
CopyEdit
if (groupingBy == "TransactionDate")
{
createNewVoucherPerTransactionDate();
}

✅ Recommended Approach

Goal	Action
One voucher per day	Customize the posting logic to group by transaction date
One voucher per month	Post based on transaction month, using a grouping function in X++
Prevent mixed voucher usage within a report	Enforce consistent financial dimensions and dates

📌 Summary

Current grouping is based on the entire expense report.
Voucher date reflects the latest transaction date among the report lines.
You can control grouping through configuration or customization.
Different vouchers within a report usually indicate differences in config, dimension, or manual intervention.