web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Sales order invoice du...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Sales order invoice duplicate

(3) ShareShare
ReportReport
Posted on by udaY-ch 5,175
Hi Folks
 
We identified a scenario where the sales order invoice has duplicated and used the same invoice number more than once which was used before and it is a manual posting and i dont think summary update is used and yet not sure how this is happened but similar duplicates found in other legal entities. and there is no customization around the invoice posting.
 
 
 
 
Changing the parameter of continous to Yes would solve the problem, Has anyone faced similar problem and any solution for this issue ?
 
 
Thanks
Uday
 
Categories:
Dynamics 365 Finance
I have the same question (0)
  • Diego Mancassola Profile Picture
    Diego Mancassola 867 on at
    Hello, typically, sales invoices are configured with continuous number sequences precisely to avoid this kind of situation.

    When the number sequence is not continuous, gaps and even re-use of numbers can occur in specific scenarios (for example manual posting, aborted postings, or parallel processing across legal entities), even without customizations and without summary update.

    For legal and accounting reasons, invoices are normally required to have a unique and strictly sequential number, so setting the invoice number sequence to Continuous = Yes is the recommended and standard approach.

    In our experience, enabling continuous numbering resolves duplicate invoice number issues and aligns the system with typical fiscal compliance requirements.
  • udaY-ch Profile Picture
    udaY-ch 5,175 on at
    Hi Deigo
     
    Thank you. I just wanted to reconfirm before making a choice of setting the toggle to yes on continous setting.
     
    Thanks
    Uday
  • Suggested answer
    Giorgio Bonacorsi Profile Picture
    Giorgio Bonacorsi 2,852 on at
    Hello, 
     
    As mentioned by Diego you can enable the continuous.
    Furthermore, if you want to avoid at 100% this situation, you can even enable the validation check of the invoice number:
     
     
    Thank you,
    Giorgio
  • Suggested answer
    H.M.Burhan Profile Picture
    H.M.Burhan 443 Super User 2026 Season 1 on at
    Hi,
     
    You can avoid this situation by selecting the Reject duplicate option in Accounts Receivable parameters. If, for any reason, the system assigns the same invoice number to different invoices, you will receive an error. In that case, you can fix the number sequence to prevent this from happening.
     
     
     
    Cheers,
    Burhan
  • Martin Dráb Profile Picture
    Martin Dráb 239,451 Most Valuable Professional on at
    I disagree.
     
    Saying that non-continuous number sequences can generate duplicate IDs is simply not true, as far as I know. It would be a critical kernel bug that would cause problems everywhere (because almost all number sequences are non-continuous). By using a continues number sequence, you'll decrease performance and possibly cause other problems, all to avoid the bug that doesn't actually exist.
    On the contrary, it's the continues number sequence that can generate duplicate IDs, when it tries to fill gaps and it incorrectly believes that a number wasn't used. Non-continues number sequences don't have this problem.
     
    Check the invoice number used is a localization for a few European countries for cases when you enable Edit invoice ID on sales orders. Therefore it's not applicable to most customers. If you're in one of those countries and you want to always get invoice IDs from the number sequence, you should disable Edit invoice ID on sales orders. If you're not using this localization or you have Edit invoice ID on sales orders disabled, then Check the invoice number used doesn't apply to you either.
  • Suggested answer
    Syed Haris Shah Profile Picture
    Syed Haris Shah 1,666 Super User 2026 Season 1 on at
     
    I agree with @Martin Dráb a non-continuous number sequence is not the root cause here (and it can also have a performance impact). What you’re seeing looks much more like the Customer Invoice number sequence was changed or reset at some point.

    Also, to prevent this, the “Reject duplicate invoice numbers” parameter in Accounts receivable should be enabled, as advised by other folks.

    I would recommend checking the Customer Invoice number sequence History to see what happened to the sequence.
     
    Under normal, standard manual posting, the system should not behave like this. This typically only happens if the invoice was posted via batch and retried, through an integration, or due to custom code, or if the number sequence was manually modified/reset.
     
    If you find this answer helpful, please consider verifying the answer. 👍
     
    Regards,
    Syed Haris Shah
  • udaY-ch Profile Picture
    udaY-ch 5,175 on at
    Hi Folks
     
    Thank you all for your answers. Check invoice number feature works only for free text invoice and it cannot be used for sales order based invoices.  This is for free text invoice
     
    Martin : I did checked the flag "check invoice number used" which is specific to certain EU regions and I am having this issue in US. I thought not to extend the flag to make the functionality global and felt enabling the continous on the number sequence would be a fix but I read there would be implications on the performance when it is being enabled and we have around 15+ legal entities. I have read your old comments on the similar question before but still wanted to check on the community is there any better solution for the problem.
     
    I am also thinking about contacting Mirosoft since this is not happening every day and once in a while and there is no standard option without any cusotmization.
     
    Thanks
    Uday
  • Suggested answer
    Giorgio Bonacorsi Profile Picture
    Giorgio Bonacorsi 2,852 on at
    Hello,

    This issue usually occurs when the system reuses a previously held number or fails to correctly update to the next available number.
    To prevent it, you can:
    - Implement validation to ensure the new number is not already in use, or
    - Maintain the sequence as clean as possible (avoid gaps, orphaned records, manual edits, etc.).
     
    Concerning the validation is the configuration see previously. If you would like you can even use the configuration set "to a higher number". It forces the new number number to be higher than the previous:
     
     
    Concerning the clean sequence number, there are other two point you can change. Both reduce the performance, But that helps maintain consistent customer invoice numbers (choose based on your priority):
     
    - Uncheck the pre-allocation: it reduce confusion during invoice issue:
    - This process releases numbers that were reserved/held but never actually used.
     
    Thank you ,
    Giorgio
  • Diego Mancassola Profile Picture
    Diego Mancassola 867 on at

    Hello,

    My fault, i’ve been rethinking about it, and you’re right: the continuous sequence is not the cause.

    My mistake was confusing the localization requirement—where invoice numbering must not have gaps—with the root cause of the issue. In this case, the setting is always enabled, and i never seen a gap or a duplicate invoice, but the sequence itself normally behaves as a proper continuous sequence.

    Enabling that cause a performance problem, true, but you can evaluate it if resolve your problem.

    Most likely, in your scenario, it would be necessary to investigate what happens to the number sequence at a certain point and why it falls back to a previously used number and cause the issue.

  • Suggested answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 304,711 Super User 2026 Season 1 on at
    Hi Uday,

    When looking carefully at your screenshots, the invoice number is the same, the dates are different, but also the voucher is different. The amounts are positive and negative, meaning there is a different number sequence used for invoices and credit notes via the parameters form.
     
    Check the number sequence configuration on the parameters. In case you have two different series, they are now most likely overlapping with numbers due to the same prefix and pattern. Usually, I do use exactly the same number sequence code for both the invoice and credit note references. 
     
    In addition, enable the parameter to avoid duplicate invoice numbers as suggested above.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 608

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 591 Super User 2026 Season 1

#3
CP04-islander Profile Picture

CP04-islander 430

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP
License usage reporting (in-app and PPAC) with Entra dynamic groups

Product updates

Dynamics 365 release plans