Finance | Project Operations, Human Resources, ...

General Journals > There can only be one vendor or customer transaction per voucher

(1) Share

Report

Posted on by SV-18061727-0

582

Hello Experts,

While posting General Journals in one of our environments, I below message

I have updated the General ledger parameter "Allow multiple transactions within one voucher" to "Yes" and I was able to post my entry but want to know what is causing this issue

Thank you

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (0)

André Arnaud de Cal... 298,933 Super User 2025 Season 2 on at

Like (0)

Report

General Journals > There can only be one vendor or customer transaction per voucher

Hi,

The parameter Allow multiple transactions within one voucher is not working in the case of customer and vendor transactions. You need to ensure each journal entry with a customer or vendor account has a unique voucher number.

Was this reply helpful? Yes No
Suggested answer

CA Neeraj Kumar 4,139 on at

Like (0)

Report
General Journals > There can only be one vendor or customer transaction per voucher

Hi @SV-18061727-0,

It is not recommended to use this parameter unless and until your scenario cannot be handled through some other way.

You can refer this article which explains in details on how this parameters impact different areas in the system.

It is explained in detail here with scenarios and latest features handling different scenarios:

https://learn.microsoft.com/en-us/dynamics365/finance/general-ledger/one-voucher

https://learn.microsoft.com/en-us/dynamics365/finance/general-ledger/one-voucher-faq

The One voucher functionality in Dynamics 365 allows posting multiple subledger transactions (customers, vendors, assets, projects, banks) under a single voucher. While useful for scenarios like customer/vendor netting, asset acquisitions, or certain adjustments, it can cause issues in settlement, tax, reversals, and reporting because transaction details aren’t clearly separated. Microsoft advises using One voucher only when required and recommends newer features (like detailed payments with summarized bank posting or customer/vendor netting) for most cases. Organizations should regularly review and disable the “Allow multiple transactions within one voucher” setting unless it’s needed for specific business gaps.

Talking about your current scenario:

If balances of both vendor and customer are to be affected then you must use a Control GL in between, let say first transfer the amount from vendor to Control GL and then from that Control GL to Customer. It will use two different vouchers but help to maintain the data integrity of the system.

Extract from the above article:

"The future of One voucher

Because of the issues that can occur when One voucher is used, the following options are being explored:

New features will continue to be introduced if there's a better way to accomplish a business scenario. For example, a feature that was introduced in Finance version 10.0.32 enables payments to be entered as separate vouchers, but the bank account is still updated in summary. As features are added, they will be documented for each business scenario in the "Alternative" column of the preceding table.

Some transactions might continue to be entered through the journal in a single voucher, but additional data might be tracked to correctly identify transactional details.

A combination of new features might be used, but transactions for the business scenarios might continue to be entered in the journal by using a single voucher.

As new features are introduced, your organization must continuously evaluate whether the Allow multiple transactions within one voucher option on the General ledger parameter page can be turned off. We recommend that you not use One voucher for integrations unless you require the functionality for one of the documented functional gaps.

As functional gaps are filled, Microsoft will communicate the new features to be used instead of One voucher. For some business scenarios, such as a vendor invoice with multiple lines, One voucher will continue to be used but with enhancements. Those enhancements will be communicated as they are delivered."

In case you have any further queries, please let us know.

Regards,

Neeraj Kumar

Was this reply helpful? Yes No
SV-18061727-0 582 on at

Like (0)

Report

General Journals > There can only be one vendor or customer transaction per voucher

Thank you for your explanation. Will it be ok to skip this validation, are there any other repercussions?

Was this reply helpful? Yes No
Sohaib Cheema 48,602 User Group Leader on at

Like (0)

Report

General Journals > There can only be one vendor or customer transaction per voucher

Hi,

You faced that warning message because your voucher had entries involving more than one vendor or customer. The system expected you to have only one vendor/customer mentioned in the entire voucher.

For such an entry, you typically keep one vendor/customer on the top line with an amount in either the Debit or Credit column.
Then, from line two onward, you create lines for the offset side until the total amount of all lines (except the first line) becomes equal to the amount in the top line.

When you enabled that checkbox, you instructed the system to skip this validation.

Was this reply helpful? Yes No