[IMP] accounting: clarify invoice sequence format
task-4564980
closes odoo/documentation#12097
X-original-commit: d2c610179a
Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com>
This commit is contained in:
parent
875a0be668
commit
d34b5fa06f
@ -7,8 +7,7 @@ Customer invoices
|
|||||||
A customer invoice is a document issued by a company for products and/or services sold to a
|
A customer invoice is a document issued by a company for products and/or services sold to a
|
||||||
customer. It records receivables as they are sent to customers. Customer invoices can include
|
customer. It records receivables as they are sent to customers. Customer invoices can include
|
||||||
amounts due for the goods and/or services provided, applicable sales taxes, shipping and handling
|
amounts due for the goods and/or services provided, applicable sales taxes, shipping and handling
|
||||||
fees, and other charges.
|
fees, and other charges. Odoo supports multiple invoicing and payment workflows.
|
||||||
Odoo supports multiple invoicing and payment workflows.
|
|
||||||
|
|
||||||
.. seealso::
|
.. seealso::
|
||||||
:doc:`/applications/finance/accounting/customer_invoices/overview`
|
:doc:`/applications/finance/accounting/customer_invoices/overview`
|
||||||
@ -84,14 +83,14 @@ Invoice confirmation
|
|||||||
|
|
||||||
Click :guilabel:`Confirm` when the invoice is completed. The invoice's status changes to
|
Click :guilabel:`Confirm` when the invoice is completed. The invoice's status changes to
|
||||||
:guilabel:`Posted`, and a journal entry is generated based on the invoice configuration. On
|
:guilabel:`Posted`, and a journal entry is generated based on the invoice configuration. On
|
||||||
confirmation, Odoo assigns each invoice a unique number from a defined
|
confirmation, Odoo assigns each invoice a unique number from a defined :ref:`sequence
|
||||||
:ref:`sequence <accounting/invoice/sequence>`.
|
<accounting/invoice/sequence>`.
|
||||||
|
|
||||||
.. note::
|
.. note::
|
||||||
- Once confirmed, an invoice can no longer be updated. Click :guilabel:`Reset to draft` if
|
- Once confirmed, an invoice can no longer be updated. Click :guilabel:`Reset to draft` if
|
||||||
changes are needed.
|
changes are needed.
|
||||||
- If required, invoices and other journal entries can be locked once posted
|
- If required, invoices and other journal entries can be locked once posted using the
|
||||||
using the :ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
|
:ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
|
||||||
|
|
||||||
.. _accounting/invoice/sending:
|
.. _accounting/invoice/sending:
|
||||||
|
|
||||||
@ -174,53 +173,45 @@ same customer, the actions are performed on the most overdue invoice.
|
|||||||
|
|
||||||
.. _accounting/invoice/sequence:
|
.. _accounting/invoice/sequence:
|
||||||
|
|
||||||
Sequence
|
Invoice sequence
|
||||||
========
|
================
|
||||||
|
|
||||||
Odoo assigns each document a unique sequence made up of a prefix and a number. The prefix combines
|
When confirming an invoice, Odoo generates a unique invoice reference number. By default, Odoo uses
|
||||||
the journal code and the entry date and groups entries by period. The number is unique for each
|
the following sequence format `INV/year/incrementing-number` (e.g., `INV/2025/00001`), which
|
||||||
period and is used to identify the entry. The default sequence on customer invoices is
|
restarts from `00001` each year.
|
||||||
INV/YYYY/number. In some specific cases, :ref:`resequencing <accounting/invoice/resequencing>`
|
|
||||||
invoices might be necessary.
|
However, it is possible to :ref:`change the sequence format <accounting/invoice/resequencing>` and
|
||||||
|
its periodicity, and to :ref:`mass-resequence invoices <accounting/invoice/mass-resequencing>`.
|
||||||
|
|
||||||
|
.. note::
|
||||||
|
Changes made to reference numbers are logged in the chatter.
|
||||||
|
|
||||||
.. _accounting/invoice/resequencing:
|
.. _accounting/invoice/resequencing:
|
||||||
|
|
||||||
Resequencing
|
Changing the default sequence
|
||||||
------------
|
-----------------------------
|
||||||
|
|
||||||
Resequencing is not possible:
|
To customize the default sequence, open the last confirmed invoice, click :guilabel:`Reset to
|
||||||
|
Draft`, and edit the invoice's reference number.
|
||||||
|
|
||||||
- When entries are before a lock date.
|
.. image:: customer_invoices/reference-number.png
|
||||||
- When the sequence leads to a duplicate.
|
:alt: Editing the reference number of an invoice.
|
||||||
- When the :guilabel:`Invoice Date` doesn't match the date contained in the new sequence number,
|
|
||||||
e.g., if the sequence is changed to INV/2023/XXXXX for a document with an :guilabel:`Invoice Date`
|
|
||||||
of 2024.
|
|
||||||
|
|
||||||
To change the invoice sequence with the structure INV/YYYY/MM/number, add `/MM` with the number of
|
Odoo then explains how the detected format will be applied to all future invoices. For example, if
|
||||||
the month of the :guilabel:`Invoice date`. Odoo will recognize the "/" term as a month and update
|
the current invoice's month is added, the sequence's periodicity will change to every month instead
|
||||||
the future invoice sequence appropriately with the month of the :guilabel:`Invoice date`. For
|
of every year.
|
||||||
example, if the invoice date is January, change the sequence to `INV/2024/01/XXXXX`.
|
|
||||||
|
|
||||||
In this case, if the :guilabel:`Invoice date` isn't aligned with the sequence number, a
|
.. image:: customer_invoices/sequence-dialog.png
|
||||||
:guilabel:`Validation Error` message appears.
|
:alt: Editing the reference number of an invoice.
|
||||||
|
|
||||||
.. note::
|
.. tip::
|
||||||
|
The sequence format can be edited directly when creating the first invoice of a given sequence
|
||||||
- All sequence changes are logged in the chatter to keep the information.
|
period.
|
||||||
- Sequence changes also affect the format of future invoices' sequences.
|
|
||||||
|
|
||||||
.. _accounting/invoice/resequencing-one-invoice:
|
|
||||||
|
|
||||||
Resequencing a single invoice
|
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
||||||
|
|
||||||
To resequence the last confirmed invoice, click :guilabel:`Reset to Draft`, then change the
|
|
||||||
sequence. The invoice now appears in red on the :guilabel:`Customer Invoices` list.
|
|
||||||
|
|
||||||
.. _accounting/invoice/mass-resequencing:
|
.. _accounting/invoice/mass-resequencing:
|
||||||
|
|
||||||
Mass-resequencing invoices
|
Mass-resequencing invoices
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
--------------------------
|
||||||
|
|
||||||
It can be helpful to resequence multiple invoice numbers. For example, when importing invoices from
|
It can be helpful to resequence multiple invoice numbers. For example, when importing invoices from
|
||||||
another invoicing or accounting system and the reference originates from the previous software,
|
another invoicing or accounting system and the reference originates from the previous software,
|
||||||
@ -239,6 +230,7 @@ Follow these steps to resequence invoice numbers:
|
|||||||
|
|
||||||
- :guilabel:`Keep current order`: The order of the numbers remains the same.
|
- :guilabel:`Keep current order`: The order of the numbers remains the same.
|
||||||
- :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
|
- :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
|
||||||
|
|
||||||
#. Set the :guilabel:`First New Sequence`.
|
#. Set the :guilabel:`First New Sequence`.
|
||||||
#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
|
#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
|
||||||
|
|
||||||
@ -270,18 +262,18 @@ go to :menuselection:`Accounting --> Reporting --> Partner Ledger`.
|
|||||||
Aged Receivable
|
Aged Receivable
|
||||||
~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
To review outstanding customer invoices and their related due dates, use the
|
To review outstanding customer invoices and their related due dates, use the :ref:`Aged Receivable
|
||||||
:ref:`Aged Receivable <accounting/reporting/aged-receivable>` report. To access it, go to
|
<accounting/reporting/aged-receivable>` report. To access it, go to :menuselection:`Accounting -->
|
||||||
:menuselection:`Accounting --> Reporting --> Aged Receivable`.
|
Reporting --> Aged Receivable`.
|
||||||
|
|
||||||
.. _accounting/invoices/aged-payable:
|
.. _accounting/invoices/aged-payable:
|
||||||
|
|
||||||
Aged Payable
|
Aged Payable
|
||||||
~~~~~~~~~~~~
|
~~~~~~~~~~~~
|
||||||
|
|
||||||
To review outstanding vendor bills and their related due dates, use the
|
To review outstanding vendor bills and their related due dates, use the :ref:`Aged Payable
|
||||||
:ref:`Aged Payable <accounting/reporting/aged-payable>` report. To access it, go to
|
<accounting/reporting/aged-payable>` report. To access it, go to :menuselection:`Accounting -->
|
||||||
:menuselection:`Accounting --> Reporting --> Aged Payable`.
|
Reporting --> Aged Payable`.
|
||||||
|
|
||||||
.. _accounting/invoices/profit-and-loss:
|
.. _accounting/invoices/profit-and-loss:
|
||||||
|
|
||||||
|
Binary file not shown.
After Width: | Height: | Size: 6.7 KiB |
Binary file not shown.
After Width: | Height: | Size: 9.1 KiB |
Loading…
Reference in New Issue
Block a user