8000 [IMP] accounting: clarify mass-sequencing highlights and errors · odoo/documentation@910037a · GitHub
[go: up one dir, main page]
Skip to content

Commit 910037a

Browse files
afma-odooafma-odoo
committed
[IMP] accounting: clarify mass-sequencing highlights and errors
task-4725955 closes #12926 Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
1 parent 779d713 commit 910037a

File tree

4 files changed

+47
-9
lines changed

4 files changed

+47
-9
lines changed

‎content/applications/finance/accounting/customer_invoices/invoice-sequencing.png

-11.6 KB
Binary file not shown.

‎content/applications/finance/accounting/customer_invoices/sequence.rst

Lines changed: 24 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,9 @@
22
Invoice sequence
33
================
44

5-
When confirming an invoice, Odoo generates a unique invoice reference number. By default, Odoo uses
6-
the following sequence format `INV/year/incrementing-number` (e.g., `INV/2025/00001`), which
7-
restarts from `00001` each year.
5+
When confirming an invoice, Odoo generates a unique invoice reference number. By default, it uses
6+
the sequence format `INV/year/incrementing-number` (e.g., `INV/2025/00001`), which restarts from
7+
`00001` each year.
88

99
However, it is possible to :ref:`change the sequence format <accounting/invoice/resequencing>` and
1010
its periodicity, and to :ref:`mass-resequence invoices <accounting/invoice/mass-resequencing>`.
@@ -60,7 +60,26 @@ Follow these steps to resequence invoice numbers:
6060
#. Set the :guilabel:`First New Sequence`.
6161
#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
6262

63-
The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
64-
6563
.. image:: sequence/invoice-sequencing.png
6664
:alt: Resequence options window
65+
66+
.. note::
67+
- To indicate where the sequence change began, the first invoice in the new sequence is
68+
highlighted in red in the :guilabel:`Customer Invoices` list. This visual marker is permanent
69+
and purely informational.
70+
- If there are any irregularities in the new sequence, such as gaps, cancelled, or deleted
71+
entries within the open period, a :guilabel:`Gaps in the sequence` message appears in the
72+
:guilabel:`Customer Invoices` journal on the Accounting dashboard. To view more details about
73+
the related invoice(s), click :guilabel:`Gaps in the sequence`. This visual marker is temporary
74+
and will disappear once the entry's accounting date is on or after the lock date.
75+
76+
.. tip::
77+
Resequencing is not possible:
78+
79+
- When entries are before a lock date.
80+
- When the sequence leads to a duplicate.
81+
- When the range is invalid. For example, if the :guilabel:`Invoice Date` doesn't align with the
82+
date in the new sequence, such as using a 2024 sequence (INV/2024/XXXXX) for an invoice dated
83+
in 2025.
84+
85+
In these cases, a :guilabel:`Validation Error` message appears.

‎content/applications/finance/accounting/customer_invoices/sequence/invoice-sequencing.png

943 Bytes
Loading

‎content/applications/finance/accounting/vendor_bills/sequence.rst

Lines changed: 23 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ Vendor bill sequence
33
====================
44

55
When confirming a vendor bill, Odoo generates a unique vendor bill reference number. By default, it
6-
uses the following sequence format `BILL/year/month/incrementing-number` (e.g.,
7-
`BILL/2025/01/00001`), which restarts from `00001` each year.
6+
uses the sequence format `BILL/year/month/incrementing-number` (e.g., `BILL/2025/01/00001`), which
7+
restarts from `00001` each year.
88

99
However, it is possible to :ref:`change the sequence format <accounting/vendor_bills/resequencing>`
1010
and its periodicity, and to :ref:`mass-resequence vendor bills
@@ -60,7 +60,26 @@ Follow these steps to resequence vendor bill numbers:
6060
#. Set the :guilabel:`First New Sequence`.
6161
#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
6262

63-
The first vendor bill using the new sequence appears in red in the :guilabel:`Bills` list view.
64-
6563
.. image:: sequence/sequence-bill-sequencing.png
6664
:alt: Resequence options window
65+
66+
.. note::
67+
- To indicate where the sequence change began, the first vendor bill in the new sequence is
68+
highlighted in red in the :guilabel:`Vendor Bills` list. This visual marker is permanent
69+
and purely informational.
70+
- If there are any irregularities in the new sequence, such as gaps, cancelled, or deleted
71+
entries within the open period, a :guilabel:`Gaps in the sequence` message appears in the
72+
:guilabel:`Vendor Bills` journal on the Accounting dashboard. To view more details about the
73+
related vendor bill(s), click :guilabel:`Gaps in the sequence`. This visual marker is temporary
74+
and will disappear once the entry's accounting date is on or after the lock date.
75+
76+
.. tip::
77+
Resequencing is not possible:
78+
79+
- When entries are before a lock date.
80+
- When the sequence leads to a duplicate.
81+
- When the range is invalid. For example, if the :guilabel:`Bill Date` doesn't align with the
82+
date in the new sequence, such as using a 2024 sequence (BILL/2024/MM/XXXX) for an vendor bill
83+
dated in 2025.
84+
85+
In these cases, a :guilabel:`Validation Error` message appears.

0 commit comments

Comments
 (0)
0