Hi Sagar, first thing I'd check is Allow Gaps in Nos. on the No. Series Line. When it's on, BC pulls the number from a database sequence, and a sequence doesn't roll back — so a failed posting, a session timeout or a cancelled document eats the number and it never comes back. Two missing in a row like your P0125 and P0126 looks exactly like that, someone tried to post twice and it errored both times.
The other one people forget is Allow Document Deletion Before, in General Ledger Setup if I remember right. With a date in there posted invoices can actually be deleted, and then the number is gone with nothing behind it.
For the auditors I'd switch on Change Log for the sales header, so next time you have a dated record instead of a story. And the argument that usually lands with them is that the G/L Entry numbering has no gaps, only the document numbering does.
Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis