If you try to post the invoice and you receives an error (mostly when you try to post document with obliged dimensions), then sometimes it is possible that NAV allready assigns a posted document number to the unposted invoice/credit memo. Afterwords the user deletes this invoice and this causes a gap in the posted number series.
So the COMMIT in codeunit 80 / 90 should be reviewed, so that a complete roll-back could be possible when an error is occured during the posting routine. The posted number series may never been raised if an error is occured.
It should be prevented that there are GAPS and it should also be prevented that NAV creates documents with text 'Deleted document'. Auditors/fiscal controllers does not like 'deleted documents'.
Comments
A reproduction for a Purchase invoice is posting the purchase invoice leaving the Amount Incl VAT blank.
This will always assign a Posting No.
Category: Financial Management
If you have date order enabled for the posting series which is very commonly used for posted invoices, you can use the "posting no." of the "potentially orders to delete" only in the current day. Next day there will be new documents posted with higher posting number and you cannot take the unused numbers for new documents as the date order will stop you.
As you can imagine, users not always report this to admins immediately or even so they can be some delay and problem cannot be avoided.
So, this design/bug is quite unpleasant, not liked by the auditors, not liked by the customer and definitely not liked by the partners which needs to explain and defend the system transactional reliability.
Category: Financial Management
We are implementing french localisation for BCv17 and have faced this issue:
1. Gaps when having posting errors ( i would suggest to make all the checks/validation before fetching the next posting no., because now you know it will post!)
2. When creating the document to fill the gap, the entry does not appear in the G/L Register, hence the Audit file does not contain that entry, this invalidates the file. It also creates a gap in the document no. which invalidates the integrity of the sequence.
3. Deleted document is also posted on the current date instead of the posting date of the document. This messes the no. series as you cannot assign posting no. series before that date. It is an issue if you are still processing a list of sales order of the previous day.
Category: Financial Management
I think this should not be treated as a suggestion but as an important bug. Transactionality must always be guaranteed. In this case it is not so, the posting is being done partially.
Navision has always had transactional posting issues, and it's time for Microsoft to fix them.
Category: Financial Management
Many auditors does not like to have 'deleted documents' with text line 'deleted document'...
They think it is deleted because of fraud.
Category: Financial Management
Not sure…
In case that this is still by design, I think we need have a report / feature that show the gaps in the posted document numbers… with such report the user be aware that he/she need to delete something…
Category: Financial Management
some details about how repro:
BC 14.x RTM (on-prem)
1-Go to ‘Item Card’ (LS-81), set
- “Prevent Negative Inventory” = yes
2-Create new ‘Sales Invoice’
Header:
- Customer = 1000
Line:
- Item = LS-81
- Quantity = 1 // Answer Yes
Try to post, as result error:
“You have insufficient quantity of Item LS-81 on inventory.”
3-Check that in the document (unposted document) we could see “Posting No.” = 103032 ?!
4-Create new ‘Sales Invoice’
Header:
- Customer = 1000
Line:
- Item = LS-75
- Quantity = 2 // Answer Yes
Post
5-Go to ‘Posted Sales Invoice’, last 5 lines:
No.
103028
103029
103030
103031
103033
We could see a gap.
+
Additional info:
6-If now delete the document from step 2 then system create 'an empty document with the only text line "deleted document"' 103032 - as result no gap
Not sure that this help in scenario when we never delete
Category: Financial Management
In Belgium auditors do not like to see 'deleted documents'. Therefore we usually choose to set up unposted numbers to sales/purchase documents. When the document is posted, then we would like to receive a posted document number.
But this set-up does not work 100% correct. In case there is an error during posting routines (f.e. obligatory dimension is missing), we see also that the posted document number is allready linked to the unposted document. And when such a document is deleted, we receive a deleted document.
An other good solution could be that the application stores in an extended table linked to number series line, the deleted numbers. And when the application needs to have a new number that first re-uses the deleted number instead of taking a number out of the normal ranges.
Category: Financial Management
There should be no gap in the posted documents.
If there is no error in the posting routines, NAV/BC creates (in germany) an empty document with the only text line "deleted document"
Category: Financial Management
Business Central Team (administrator)
Thank you for your feedback. This is a great suggestion! We are considering it for our roadmap.
Your help is greatly appreciated,
Ivan Koletic
PM, Microsoft