One Voucher Depreciation

(0) Share

Report

Posted on by Daniel_CH

Its future depreciation has been announced in 2018 (https://docs.microsoft.com/en-us/business-applications-release-notes/april18/dynamics365-finance-operations/one-voucher-deprecation).

My customer is using it for the supplier payment registration.

Questions:

- From which release on is the feature depreciated?

- By what solution is One Voucher replaced?

- starting available from which release ?

- How can a customer prepare for adpapting the business processes ?

Thanks, Daniel

I have the same question (0)

All responses (6)

Answers (0)

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello Daniel,

Can you elaborate what you refer to by 'supplier payment registration'?

What form / process do you use for that?

Many thanks,

Ludwig

Was this reply helpful? Yes No
Daniel_CH on at

Like (0)

Report

“In the supplier payment journals, we use one voucher for all the lines (the last line is the bank account). Please find the screenshot below. Once one voucher will be depreciated, we will have to proceed different.

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi Daniel,

Many thanks for that update.

Can't you change the way how the payment and voucher is generated?

I mean, what difference does it make if you have one voucher for each line?

Best regards,

Ludwig

Was this reply helpful? Yes No
Daniel_CH on at

Like (0)

Report

Today, a payment journal with one voucher generates one bank transaction for the payment total amount. The bank statement has also one line, and it is easy for our treasures to reconcile. If we switch to one voucher per line, we will have as many bank transactions as vendor lines in the journal, and we will have to match x lines versus one bank statement line, which will complexify the bank reconciliation. We have a huge volume of data.

Was this reply helpful? Yes No
Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Ok.

The issue is then actually related to bank reconciliation.

How do you do your bank reconciliation?

Are you using the standard bank reconciliation functionality in the banking module or something that has been customized?

Best regards,

Ludwig

Was this reply helpful? Yes No
Suggested answer

Sheela Ningappa on at

Like (0)

Report

Hi Daniel,

We have got the below feedback from the product group on the one voucher depreciation.

When will the One voucher functionality be deprecated?

We cannot provide an ETA. As the external documentation says, we must first full all the functional gaps through delivery of new features. After all those functional gaps are filled we must wait at least ONE YEAR to deprecate the feature. It will likely be years before the functionality is deprecated.

Where do we find the progress of the feature gaps being filled?

As with every new feature, customers must watch the Roadmap. Each feature will be clearly added, likely with a note that it’s a feature to fill a gap within the One voucher functionality.

When the deprecation date is identified, where will it be communicated?

The deprecation of One voucher is a HUGE change that this will be widely communicated. The published document will be updated. A blog will be created. The Roadmap will be updated. It will be communicated at the ISV conferences we have.

What is the solution look like for replacing One voucher?

We cannot give a specific solution because each feature gap is different and has to be evaluated based on the business requirements. Some functional gaps will likely be replaced with features specifically for the business process, while other gaps may be filled by still allowing the entry into the journal as is, but enhancing the data model to track more detail as necessary.

Regards,

Sheela

Was this reply helpful? Yes No