Erpnext: Non sequencial final invoice number - Blocking accountacy issue for France, Swiss, Germany (at least)

[AmauryVanEspen]

Draft is not a submitted invoice. Once it is posted, it can't be changed. Deletion can be controlled via permissions. Those who have access to the database (self hosted) can do whatever they want. Most countries have systems to generate invoice numbers via government API. 3rd party validation is the only way this is fool proof. Rest is notional.
…

Indeed, drafts are not submitted invoices, but they are nevertheless being given Invoice numbers.

We all understand that everything is mutable if you have access to the hardware, but this is more of a workflow issue. Notional or not, many of us are bound by accounting standards that insist on strictly sequential documentation. If we create a draft and then decide not to submit it, what is the correct way to move forward?

_Originally posted by @theopen-institute in https://github.com/frappe/erpnext/issues/8765#issuecomment-652261056_

[dalers]

This isn't my domain, can anyone comment on if and how strictly sequential documentation applies in Canada?

From: "Amaury Van Espen" [e-mail]
To: "frappe" [e-mail]
Cc: "Subscribed" [e-mail]
Sent: Saturday, July 4, 2020 6:38:42 AM
Subject: [frappe/erpnext] Non sequencial final invoice number - Blocking
accountacy issue for France, Swiss, Germany (at least) (#22582)

Draft is not a submitted invoice. Once it is posted, it can't be changed.
Deletion can be controlled via permissions. Those who have access to the
database (self hosted) can do whatever they want. Most countries have systems
to generate invoice numbers via government API. 3rd party validation is the
only way this is fool proof. Rest is notional.
[ https://wm-no.glb.shawcable.net/zimbra/mail# | … ]
Indeed, drafts are not submitted invoices, but they are nevertheless being given
Invoice numbers.

We all understand that everything is mutable if you have access to the hardware,
but this is more of a workflow issue. Notional or not, many of us are bound by
accounting standards that insist on strictly sequential documentation. If we
create a draft and then decide not to submit it, what is the correct way to
move forward?

Originally posted by [ https://github.com/theopen-institute | @theopen-institute
] in [ https://github.com/frappe/erpnext/issues/8765#issuecomment-652261056 |

8765 (comment) ]

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [ https://github.com/frappe/erpnext/issues/22582 |
view it on GitHub ] , or [
https://github.com/notifications/unsubscribe-auth/AAKFYYGWP7XFEI32SLXCUU3RZ4PFFANCNFSM4OQMHP5A
| unsubscribe ] .

[mvincent514]

It may look dumb but what if drafts get their own invoice naming series and once submitted, it takes a valid naming serie invoice? Is it possible to do so?

[AmauryVanEspen]

Hello, is there any suggestion about fonctional or technical workaround for this issue ?

[AmauryVanEspen]

Hello, it seems the issue could be solved by a PR (import) from Dokos
https://gitlab.com/dokos/dokos/-/tree/develop/erpnext
which manage the constraint of legal and compliant invoicing sytem
Could you tell us more please ?
Thank you
Amaury

[aakvatech]

It may look dumb but what if drafts get their own invoice naming series and once submitted, it takes a valid naming serie invoice? Is it possible to do so?

This is a good suggestion as well, and also under the scope of ERPNext rather than affecting the Frappe functionality. Would this be applicable to certain types of DocTypes only? or would it be required as a blanket requirement across all the DocTypes?