Finance | Project Operations, Human Resources, ...

Invoice number sequence after update 71 (ITA – “Continuous” sequences, Issue 1120115)

(6) Share

Report

Posted on by Diego Mancassola

902

Hi all,

We are experiencing some unexpected behavior after applying Update 71 (7.0.7858.76) and wanted to check if anyone else has seen the same in the Italian localization (Number sequences with “Continuous” flag).

This seems related to standard Issue 1120115 under investigation

AS-IS situation:

After the PU, all “Continuous” number sequences show anomalies.

Observed issues:

The number sequence cleanup date is always before the PU application
→ suggests cleanup might not be working correctly.
The system writes to NumberSequenceList much more frequently than before.
If a document posting (e.g., invoice) fails:
- The number is stored in NumberSequenceList with “Undecided action” (e.g., 96759)
- The next posting skips this number and assigns the following one
- The number is only released later (e.g., when the user session ends)
During posting, the system prompts for cleanup more often than in the past.
Cleanup only applies to number sequences not linked to active sessions.

Why this is critical (Italy-specific):
Open number sequences can create compliance issues.
Example: if an invoice is posted today with voucher 123, it becomes problematic to post a backdated invoice (yesterday) with a higher number than 123.
Therefore, leaving sequences “open” from previous dates is not acceptable.

Has anyone encountered the same behavior in PU71 (Issue 1120115)?
If yes, how are you managing or mitigating this?

Thanks in advance for any insights.

Note, the post is AI written supported based on a internal our document.

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (11)

Answers (0)

Sort by

Suggested answer

Giorgio Bonacorsi 3,492 on at

Like
a
(2)

Report
Copy link

Link copied!

Hello,

Yes, I confirm the business requirement.

In Italy we need to keep the "Continue" flag selected because the new voucher number must be higher than the previous one (this is a tax requirement from the Italian authorities).

The cleanup can help reduce the number of errors, but it does not completely eliminate them.

Thank you,
Giorgio

Was this reply helpful? Yes No
Diego Mancassola 902 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi Giorgio, of course there is that requirement.

In addition to my post i'll would put attention on this issue.

We need to know if anyone, in Italian location of course, has this problem and how workarounded that.

Was this reply helpful? Yes No
Suggested answer

Subra 1,428 on at

Like
a
(1)

Report
Copy link

Link copied!

Please update the latest quality update for the particular environment.

Was this reply helpful? Yes No
Suggested answer

André Arnaud de Cal... 305,860 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi Diego,

Knowing how the continuous number sequences are implemented technically, someone made a change where at time of drawing a new number a flag was set to make a decision later for flagging the number as used. At that time, the number sequence list is filled with the status you mentioned. At the end of the process, the method 'numberseq::used' should be called then. If that is forgotten or by accident removed or skipped, you have this issue. Microsoft should bring a fix for this. You can check if you can extend the coding for the time being to set the number to 'used'. That will delete the number sequence list record.

It can also be the case that at time of deleting a record with the number is not updating the status list correctly.

In case journal entries are never removed by the users before posting, you can also consider to change the number sequence setting temporarily to non-continuous. This will then bypass the status list.

As last workaround, you can try to use the temporary voucher functionality. I wrote a blog about this feature: What is the temporary voucher functionality in Dynamics 365?

Was this reply helpful? Yes No
gsolieri@alteanet.it 4 on at

Like
a
(1)

Report
Copy link

Link copied!

hi,

@Diego Mancassola is it available a date for the release of the fix?

thanks,

Gabriele

Was this reply helpful? Yes No
Diego Mancassola 902 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi, we are in the middle, some customers migrated some not. We raise a ticket for all of these.

@gsolieri@alteanet.it at the moment we don't have any date's from Microsoft.

Some of our customers requests pause the .47 version for now and as i know postpone is accepted.

Thank #@André Arnaud de Calavon we will review your suggestions.

Was this reply helpful? Yes No
Diego Mancassola 902 on at

Like
a
(2)

Report
Copy link

Link copied!
Hi all, an update, current status is under active investigation by Microsoft Product Engineering. It concerns unexpected number sequence consumption behavior introduced after the upgrade to version 10.0.47, resulting in gaps in voucher numbering.

The scenario has been escalated with top priority due to potential compliance risks, particularly for regulatory requirements requiring continuous numbering sequences.

At this stage:

Root cause analysis is still ongoing

It has not yet been confirmed whether this is a product defect or expected behavior

Microsoft Support is actively engaged with the Product Group

Investigation is focused on number reservation and release logic

Next steps include identifying mitigation/workaround options and determining the appropriate resolution path.

Further updates will be provided as soon as validated information becomes available.

Suggestion is to request the pause of update if you don't upgrade yet.

Was this reply helpful? Yes No

Suggested answer

Diego Mancassola

902 on at

Like (2)

Report

Copy link

Link copied!

Hi all, happy to finnaly the issue has been resolved on last 10.0.47 quality update.

The issue was caused by a failure to register the transaction ID with the number sequence framework during invoice/voucher number assignment. Consequently, when invoice generation failed, and due to the loss of associated metadata, the record could not be recycled or reissued.

Release	Type	Status	Availability
10.0.47/Platform update 71	Quality update	Resolved	7.0.7858.90
10.0.48/Platform update 72	Service update	Resolved	See release schedule*

Was this reply helpful? Yes No

Diego Mancassola 902 on at

Like
a
(2)

Report
Copy link

Link copied!

It's a joking. This is the official position of Microsoft, we have tested it and really fix the problem, but not suggested to install it yet.

The PQU3 released yesterday, restores the continuous number sequence code back to the last known working state is available, but the environment could experience performance issues after manually applying the quality update or receiving PQU 3.

Also, this PQU3 does not contain any mitigation solution to remediate any remaining gaps in the continuous number sequences; the Product Group team continues working on this remediation plan. So, if you could wait for more information, it would be better to wait and not going for this PQU3 yet. If you already update, there is no problem and we will update with more information soon.

Stay tuned, the end of this chapter will hopefully come!

Was this reply helpful? Yes No
FG-26051403-0 4 on at

Like
a
(1)

Report
Copy link

Link copied!

Hello,

Did you have any update from Microsoft regarding the PQU that’s now available? In particular, will the patch address any remaining gaps in the continuous number sequences?

Thanks

Was this reply helpful? Yes No