Compare commits
33 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
dc438a53d4 |
force rebuild
uniquifier: 3IYmB5d+inNorkRa
For-Commit-Id:
|
||
|
|
19cb93e6b5 | [I18N] *: fetch 18.0 translations | ||
|
|
a9c2961ded |
[ADD] sales: discounts
Apply suggestions from LARM review edits Apply suggestions from FEKU review edits edits2 edits3 Apply suggestions from SALI review edits closes odoo/documentation#12115 Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com> Co-authored-by: larm-odoo <121518652+larm-odoo@users.noreply.github.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com> |
||
|
|
7fbf533363 |
[IMP] contributing: documentation macOS make install
closes odoo/documentation#12146
X-original-commit:
|
||
|
|
009dd70bd3 |
[MOV] accounting: invoice sequence section on a separate page
closes odoo/documentation#12134 Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com> |
||
|
|
035e0ec1e8 |
[IMP] Purchase: Reordering Rules Update
closes odoo/documentation#12112 Signed-off-by: Jessica Rogers (jero) <jero@odoo.com> Co-authored-by: Dina Klarisse Dugar <dikd@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com> |
||
|
|
1262245b53 |
[IMP] inventory: view empty locations
closes odoo/documentation#12113 Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> Co-authored-by: larm-odoo <121518652+larm-odoo@users.noreply.github.com> |
||
|
|
aad8aa1314 |
[I18N] *: re-export pot files
As per usual, leave off developer.pot and contributing.pot since we don't translate them (not useful, can't really contribute to/dev in Odoo without knowing English) closes odoo/documentation#12126 Signed-off-by: Tiffany Chang (tic) <tic@odoo.com> |
||
|
|
e32f4ec766 |
[IMP] sales: gelato feedback
Apply suggestions from JERO review edits closes odoo/documentation#12114 Signed-off-by: Zachary Straub (zst) <zst@odoo.com> Co-authored-by: Jess Rogers <104637850+jero-odoo@users.noreply.github.com> |
||
|
|
85d4e6a167 | [I18N] *: fetch 18.0 translations | ||
|
|
0ae856bcf6 |
[FIX] Use <chatter> instead of <div class="oe_chatter">
closes odoo/documentation#12106 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> |
||
|
|
5bb043bd3b |
[ADD] Purchase: Templates
closes odoo/documentation#12070 Signed-off-by: Jessica Rogers (jero) <jero@odoo.com> Co-authored-by: dikd-odoo <dikd@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com> |
||
|
|
d2c610179a |
[IMP] accounting: clarify invoice sequence format
task-4564980 closes odoo/documentation#12053 Signed-off-by: Xavier Platteau (xpl) <xpl@odoo.com> |
||
|
|
35f2768359 |
[IMP] accounting/transactions: view/edit/print statements
Explains how to view, edit, and print statements from both kanban and list views of transactions.
task-4320158
closes odoo/documentation#12028
X-original-commit:
|
||
|
|
7529565384 | [I18N] *: fetch 18.0 translations | ||
|
|
1e412a8780 | [I18N] Update translation terms from Transifex | ||
|
|
77d4d6e359 |
[IMP] data cleaning: content improvements
closes odoo/documentation#12092
X-original-commit:
|
||
|
|
c0dd6b7d1c |
[ADD] sales: gelato integration
edit image sizes edits Apply suggestions from FEKU review edits Apply suggestions from FEKU review edits Apply suggestions from FEKU review edits Update content/applications/sales/sales/gelato.rst edits Apply suggestions from ZST review edits edits sales file Apply suggestions from SALI review Apply suggestions from SALI review2 images Edits closes odoo/documentation#12001 Signed-off-by: Dina Klarisse Dugar (dikd) <dikd@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> Co-authored-by: Zachary Straub <zst@odoo.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com> |
||
|
|
cd2e27084d |
[IMP] sales: subscription products in ecommerce
closes odoo/documentation#12043
X-original-commit:
|
||
|
|
a00a6f5583 |
[FIX] developer/mixins: chatter integration instructions in form view
Previously, the chatter integration instructions described an outdated method using fields and widgets. However, the integration approach has changed, requiring only the `<chatter/ >` element in the form view with configurable options. This commit updates the instructions accordingly. See odoo/odoo@351b047c37 closes odoo/documentation#12057 Signed-off-by: Victor Feyens (vfe) <vfe@odoo.com> |
||
|
|
84051ad9de |
[ADD] sale_shopee: Shopee Connector
Documentation on the benefits of the new shopee connector and guidelines for odoo users. tasks-3623720 closes odoo/documentation#11984 Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> |
||
|
|
5fbab9eba4 |
[IMP] inventory: add a delivery
closes odoo/documentation#12033 Signed-off-by: Jessica Rogers (jero) <jero@odoo.com> Co-authored-by: dikd-odoo <dikd@odoo.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com> |
||
|
|
01cf1d3dd7 |
[IMP] inventory: notifs for expiration dates
closes odoo/documentation#12054 Signed-off-by: Jessica Rogers (jero) <jero@odoo.com> Co-authored-by: larm-odoo <121518652+larm-odoo@users.noreply.github.com> Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com> |
||
|
|
a55fdb6313 |
[FIX] resource folder match
closes odoo/documentation#12074 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> |
||
|
|
a4b841afce |
[FIX] clean unused resource files
Part-of: odoo/documentation#12074 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> |
||
|
|
3f1f02200b |
[IMP] tests: check resource file referenced
Part-of: odoo/documentation#12074 Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com> Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> |
||
|
|
faca8a4bda |
[ADD] l10n_in: add TDS/TCS threshold alert (India)
This PR is backporting of this commit: https://github.com/odoo/documentation/pull/11109/commits/4452b60b5cddb46d45bb8a6b992f0cf10df75c96 This commit introduces TDS/TCS Alert documentation for Indian localization. closes odoo/documentation#12075 Signed-off-by: Raj Bhuva (bhra) <bhra@odoo.com> |
||
|
|
c9fca6c3b6 |
[ADD] Barcode: Processing a transfer
closes odoo/documentation#11979 Signed-off-by: Samuel Lieber (sali) <sali@odoo.com> Co-authored-by: Felicia Kuan <feku@odoo.com> |
||
|
|
3941e55043 |
[IMP] marketing automation: content improvements
closes odoo/documentation#12060
X-original-commit:
|
||
|
|
4b6e34efc5 |
[IMP] studio: automation rules correction
Task-3761784 closes odoo/documentation#12052 Signed-off-by: Audrey Vandromme (auva) <auva@odoo.com> |
||
|
|
7368ad782b | [I18N] *: fetch 18.0 translations | ||
|
|
c4bfeb9cae |
[IMP] website: remove slash in redirect rule expression
task-4113085
closes odoo/documentation#12049
X-original-commit:
|
||
|
|
f4c16bc722 |
[IMP] data cleaning: field cleaning
closes odoo/documentation#12038
X-original-commit:
|
@@ -23,7 +23,7 @@ Edit Security Settings --> Delete Account`. It can also be accessed by going to
|
||||
Upon clicking the :guilabel:`Delete Account` button, a pop-up window appears, requesting
|
||||
confirmation for the account deletion.
|
||||
|
||||
.. image:: odoo_account/delete-account.png
|
||||
.. image:: odoo_accounts/delete-account.png
|
||||
:align: center
|
||||
:alt: Clicking on the Delete Account button will populate a window verifying the change.
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 8.7 KiB |
|
Before Width: | Height: | Size: 3.4 KiB |
|
Before Width: | Height: | Size: 9.0 KiB |
@@ -21,25 +21,23 @@ Import transactions
|
||||
|
||||
Odoo supports multiple file formats to import transactions:
|
||||
|
||||
- SEPA recommended Cash Management format (CAMT.053);
|
||||
- Comma-separated values (.CSV);
|
||||
- Open Financial Exchange (.OFX);
|
||||
- Quicken Interchange Format (.QIF);
|
||||
- Belgium: Coded Statement of Account (.CODA).
|
||||
- SEPA recommended Cash Management format (CAMT.053)
|
||||
- Comma-separated values (CSV)
|
||||
- Open Financial Exchange (OFX)
|
||||
- Quicken Interchange Format (QIF)
|
||||
- Belgium: Coded Statement of Account (CODA)
|
||||
|
||||
To import a file, go to the **Accounting Dashboard**, and in the :guilabel:`Bank` journal,
|
||||
To import a file, go to the :guilabel:`Accounting Dashboard`, and in the :guilabel:`Bank` journal,
|
||||
click on :guilabel:`Import File`.
|
||||
|
||||
.. tip::
|
||||
Alternatively, you can also:
|
||||
|
||||
- click :guilabel:`⋮` on the :guilabel:`Bank` journal and select :guilabel:`Import file`;
|
||||
- or access the transaction list by clicking :guilabel:`⋮` on the :guilabel:`Bank` journal and
|
||||
selecting :guilabel:`Transactions`, then click the gear icon :guilabel:`(⚙)` and select
|
||||
:guilabel:`Import records`.
|
||||
|
||||
.. image:: transactions/import-transactions.png
|
||||
:alt: Import bank transactions from the bank journal
|
||||
- click the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon on the :guilabel:`Bank`
|
||||
journal and select :guilabel:`Import file`;
|
||||
- or access the transaction list by clicking the :icon:`fa-ellipsis-v` :guilabel:`(ellipsis)`
|
||||
icon on the :guilabel:`Bank` journal and selecting :guilabel:`Transactions`, then click
|
||||
the :icon:`fa-cog` :guilabel:`(gear)` icon and select :guilabel:`Import records`.
|
||||
|
||||
Next, select the file and upload it.
|
||||
|
||||
@@ -75,22 +73,28 @@ on your business flow, you may want to record them for control purposes.
|
||||
account balance as of the date you begin synchronizing or importing transactions. This is
|
||||
necessary to ensure the accuracy of your accounting.
|
||||
|
||||
To access a list of statements, go to your :guilabel:`Accounting Dashboard`, click on the vertical
|
||||
ellipsis (:guilabel:`⋮`) button next to the bank or cash journal you want to check, then on
|
||||
:guilabel:`Statements`
|
||||
To access a list of existing statements, go to the :guilabel:`Accounting Dashboard`, click the
|
||||
:icon:`fa-ellipsis-v` :guilabel:`(ellipsis)` icon next to the bank or cash journal you want to
|
||||
check, then click :guilabel:`Statements`.
|
||||
|
||||
.. _transactions/statement-kanban:
|
||||
|
||||
Statement creation from the kanban view
|
||||
---------------------------------------
|
||||
|
||||
Open the bank reconciliation view by clicking on the name of the bank journal, and identify the
|
||||
transaction corresponding to the last transaction of your bank statement. Click on the
|
||||
:guilabel:`STATEMENT` button when hovering on the upper separator line.
|
||||
Open the bank reconciliation (kanban) view from the :guilabel:`Accounting Dashboard` by clicking on
|
||||
the name of the bank journal and identify the transaction corresponding to the last (most recent)
|
||||
transaction of your bank statement. Click on the :guilabel:`Statement` button when hovering on the
|
||||
upper separator line to create a statement from that transaction down to the oldest transaction that
|
||||
is not yet part of a statement.
|
||||
|
||||
.. image:: transactions/statements-kanban.png
|
||||
:alt: A "STATEMENT" button is visible when hovering on the line separating two transactions.
|
||||
:alt: A "Statement" button is visible when hovering on the line separating two transactions.
|
||||
|
||||
Fill out the statement's details and save. The newly created statement includes the previous
|
||||
transactions following the last statement.
|
||||
In the :guilabel:`Create Statement` window, fill out the statement's :guilabel:`Reference`, verify
|
||||
its :guilabel:`Starting Balance` and :guilabel:`Ending Balance`, and click :guilabel:`Save`.
|
||||
|
||||
.. _transactions/statement-list:
|
||||
|
||||
Statement creation from the list view
|
||||
-------------------------------------
|
||||
@@ -100,3 +104,35 @@ view. Select all the transactions corresponding to the bank statement, and, in t
|
||||
:guilabel:`Statement` column, select an existing statement or create a new one by typing its
|
||||
reference, clicking on :guilabel:`Create and edit...`, filling out the statement's details, and
|
||||
saving.
|
||||
|
||||
.. _transactions/view-edit-print:
|
||||
|
||||
Statement viewing, editing, and printing
|
||||
----------------------------------------
|
||||
|
||||
To view an existing statement, click on the statement amount in the reconciliation (kanban) view or
|
||||
click on the statement name in the bank transaction list view. From here, you can edit the
|
||||
:guilabel:`Reference`, :guilabel:`Starting Balance`, or :guilabel:`Ending Balance`.
|
||||
|
||||
.. note::
|
||||
Manually updating the :guilabel:`Starting Balance` automatically updates the :guilabel:`Ending
|
||||
Balance` based on the new value of the :guilabel:`Starting Balance` and the value of the
|
||||
statement's transactions.
|
||||
|
||||
.. warning::
|
||||
If the :guilabel:`Starting Balance` doesn't equal the previous statement's :guilabel:`Ending
|
||||
Balance`, or if the :guilabel:`Ending Balance` doesn't equal the running balance
|
||||
(:guilabel:`Starting Balance` plus the statement's transactions), a warning appears explaining
|
||||
the issue. To maintain flexibility, it is still possible to save without first resolving the
|
||||
issue.
|
||||
|
||||
To attach a digital copy (i.e., JPEG, PNG, or PDF) of the bank statement for enhanced recordkeeping,
|
||||
click the :icon:`fa-paperclip` :guilabel:`Attachments` button and select the file to attach.
|
||||
|
||||
To generate and print a PDF of the bank statement, click the :guilabel:`Print` button (if accessed
|
||||
via the reconciliation view) or click on the :icon:`fa-cog`:guilabel:`(gear)` icon and click
|
||||
:icon:`fa-print`:guilabel:`Statement` (if accessed via the list view).
|
||||
|
||||
.. note::
|
||||
When a bank statement is generated to be printed, it is automatically added to the
|
||||
:guilabel:`Attachments`.
|
||||
|
||||
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 23 KiB |
@@ -7,8 +7,7 @@ Customer invoices
|
||||
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
|
||||
amounts due for the goods and/or services provided, applicable sales taxes, shipping and handling
|
||||
fees, and other charges.
|
||||
Odoo supports multiple invoicing and payment workflows.
|
||||
fees, and other charges. Odoo supports multiple invoicing and payment workflows.
|
||||
|
||||
.. seealso::
|
||||
: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
|
||||
: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
|
||||
:ref:`sequence <accounting/invoice/sequence>`.
|
||||
confirmation, Odoo assigns each invoice a unique number from a defined :doc:`sequence
|
||||
<customer_invoices/sequence>`.
|
||||
|
||||
.. note::
|
||||
- Once confirmed, an invoice can no longer be updated. Click :guilabel:`Reset to draft` if
|
||||
changes are needed.
|
||||
- If required, invoices and other journal entries can be locked once posted
|
||||
using the :ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
|
||||
- If required, invoices and other journal entries can be locked once posted using the
|
||||
:ref:`Secure posted entries with hash <data-inalterability/restricted>` feature.
|
||||
|
||||
.. _accounting/invoice/sending:
|
||||
|
||||
@@ -172,81 +171,6 @@ how much the customer is overdue. These actions are bundled into follow-up level
|
||||
an invoice is overdue by a certain number of days. If there are multiple overdue invoices for the
|
||||
same customer, the actions are performed on the most overdue invoice.
|
||||
|
||||
.. _accounting/invoice/sequence:
|
||||
|
||||
Sequence
|
||||
========
|
||||
|
||||
Odoo assigns each document a unique sequence made up of a prefix and a number. The prefix combines
|
||||
the journal code and the entry date and groups entries by period. The number is unique for each
|
||||
period and is used to identify the entry. The default sequence on customer invoices is
|
||||
INV/YYYY/number. In some specific cases, :ref:`resequencing <accounting/invoice/resequencing>`
|
||||
invoices might be necessary.
|
||||
|
||||
.. _accounting/invoice/resequencing:
|
||||
|
||||
Resequencing
|
||||
------------
|
||||
|
||||
Resequencing is not possible:
|
||||
|
||||
- When entries are before a lock date.
|
||||
- When the sequence leads to a duplicate.
|
||||
- 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
|
||||
the month of the :guilabel:`Invoice date`. Odoo will recognize the "/" term as a month and update
|
||||
the future invoice sequence appropriately with the month of the :guilabel:`Invoice date`. For
|
||||
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
|
||||
:guilabel:`Validation Error` message appears.
|
||||
|
||||
.. note::
|
||||
|
||||
- All sequence changes are logged in the chatter to keep the information.
|
||||
- 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:
|
||||
|
||||
Mass-resequencing invoices
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
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,
|
||||
continuity for the current year must be maintained without restarting from the beginning.
|
||||
|
||||
.. note::
|
||||
This feature is only available to users with administrator or advisor access.
|
||||
|
||||
Follow these steps to resequence invoice numbers:
|
||||
|
||||
#. Activate the :ref:`developer mode <developer-mode>`.
|
||||
#. From the :guilabel:`Accounting Dashboard`, open the :guilabel:`Customer Invoices` journal.
|
||||
#. Select the invoices that need a new sequence.
|
||||
#. Click the :icon:`fa-cog` :guilabel:`Actions` menu and select :guilabel:`Resequence`.
|
||||
#. In the :guilabel:`Ordering` field, choose to
|
||||
|
||||
- :guilabel:`Keep current order`: The order of the numbers remains the same.
|
||||
- :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
|
||||
#. Set the :guilabel:`First New Sequence`.
|
||||
#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
|
||||
|
||||
The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
|
||||
|
||||
.. image:: customer_invoices/invoice-sequencing.png
|
||||
:alt: Resequence options window
|
||||
|
||||
.. _accounting/invoice/reporting:
|
||||
|
||||
Reporting
|
||||
@@ -270,18 +194,18 @@ go to :menuselection:`Accounting --> Reporting --> Partner Ledger`.
|
||||
Aged Receivable
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
To review outstanding customer invoices and their related due dates, use the
|
||||
:ref:`Aged Receivable <accounting/reporting/aged-receivable>` report. To access it, go to
|
||||
:menuselection:`Accounting --> Reporting --> Aged Receivable`.
|
||||
To review outstanding customer invoices and their related due dates, use the :ref:`Aged Receivable
|
||||
<accounting/reporting/aged-receivable>` report. To access it, go to :menuselection:`Accounting -->
|
||||
Reporting --> Aged Receivable`.
|
||||
|
||||
.. _accounting/invoices/aged-payable:
|
||||
|
||||
Aged Payable
|
||||
~~~~~~~~~~~~
|
||||
|
||||
To review outstanding vendor bills and their related due dates, use the
|
||||
:ref:`Aged Payable <accounting/reporting/aged-payable>` report. To access it, go to
|
||||
:menuselection:`Accounting --> Reporting --> Aged Payable`.
|
||||
To review outstanding vendor bills and their related due dates, use the :ref:`Aged Payable
|
||||
<accounting/reporting/aged-payable>` report. To access it, go to :menuselection:`Accounting -->
|
||||
Reporting --> Aged Payable`.
|
||||
|
||||
.. _accounting/invoices/profit-and-loss:
|
||||
|
||||
@@ -311,6 +235,7 @@ liabilities, and equity at a specific time.
|
||||
customer_invoices/cash_rounding
|
||||
customer_invoices/deferred_revenues
|
||||
customer_invoices/electronic_invoicing
|
||||
customer_invoices/sequence
|
||||
customer_invoices/snailmail
|
||||
customer_invoices/epc_qr_code
|
||||
customer_invoices/incoterms
|
||||
|
||||
|
Before Width: | Height: | Size: 6.9 KiB |
@@ -0,0 +1,66 @@
|
||||
================
|
||||
Invoice sequence
|
||||
================
|
||||
|
||||
When confirming an invoice, Odoo generates a unique invoice reference number. By default, Odoo uses
|
||||
the following sequence format `INV/year/incrementing-number` (e.g., `INV/2025/00001`), which
|
||||
restarts from `00001` each year.
|
||||
|
||||
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:
|
||||
|
||||
Changing the default sequence
|
||||
=============================
|
||||
|
||||
To customize the default sequence, open the last confirmed invoice, click :guilabel:`Reset to
|
||||
Draft`, and edit the invoice's reference number.
|
||||
|
||||
.. image:: sequence/reference-number.png
|
||||
:alt: Editing the reference number of an invoice.
|
||||
|
||||
Odoo then explains how the detected format will be applied to all future invoices. For example, if
|
||||
the current invoice's month is added, the sequence's periodicity will change to every month instead
|
||||
of every year.
|
||||
|
||||
.. image:: sequence/sequence-dialog.png
|
||||
:alt: Editing the reference number of an invoice.
|
||||
|
||||
.. tip::
|
||||
The sequence format can be edited directly when creating the first invoice of a given sequence
|
||||
period.
|
||||
|
||||
.. _accounting/invoice/mass-resequencing:
|
||||
|
||||
Mass-resequencing invoices
|
||||
==========================
|
||||
|
||||
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,
|
||||
continuity for the current year must be maintained without restarting from the beginning.
|
||||
|
||||
.. note::
|
||||
This feature is only available to users with administrator or advisor access.
|
||||
|
||||
Follow these steps to resequence invoice numbers:
|
||||
|
||||
#. Activate the :ref:`developer mode <developer-mode>`.
|
||||
#. From the :guilabel:`Accounting Dashboard`, open the :guilabel:`Customer Invoices` journal.
|
||||
#. Select the invoices that need a new sequence.
|
||||
#. Click the :icon:`fa-cog` :guilabel:`Actions` menu and select :guilabel:`Resequence`.
|
||||
#. In the :guilabel:`Ordering` field, choose to
|
||||
|
||||
- :guilabel:`Keep current order`: The order of the numbers remains the same.
|
||||
- :guilabel:`Reorder by accounting date`: The number is reordered by accounting date.
|
||||
|
||||
#. Set the :guilabel:`First New Sequence`.
|
||||
#. :guilabel:`Preview Modifications` and click :guilabel:`Confirm`.
|
||||
|
||||
The first invoice using the new sequence appears in red in the :guilabel:`Customer Invoices` list.
|
||||
|
||||
.. image:: sequence/invoice-sequencing.png
|
||||
:alt: Resequence options window
|
||||
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 6.7 KiB |
|
After Width: | Height: | Size: 9.1 KiB |
|
Before Width: | Height: | Size: 3.0 KiB |
|
Before Width: | Height: | Size: 4.2 KiB |
|
Before Width: | Height: | Size: 3.1 KiB |
|
Before Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 9.2 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 31 KiB |
|
Before Width: | Height: | Size: 9.9 KiB |
|
Before Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 2.9 KiB |
|
Before Width: | Height: | Size: 48 KiB |
|
Before Width: | Height: | Size: 17 KiB |
|
Before Width: | Height: | Size: 31 KiB |
|
Before Width: | Height: | Size: 24 KiB |
@@ -589,3 +589,96 @@ goods (i.e :guilabel:`Opening Stock` + purchases during the period - :guilabel:`
|
||||
|
||||
.. image:: india/profit-and-loss-report.png
|
||||
:alt: Profit and Loss report
|
||||
|
||||
.. _india/tds-tcs-threshold:
|
||||
|
||||
TDS/TCS threshold alert
|
||||
=======================
|
||||
|
||||
:abbr:`TDS (tax deducted at source)` and :abbr:`TCS (tax collected at source)` are tax provisions
|
||||
under Indian law, triggered when transaction amounts exceed specified thresholds. This alert
|
||||
notifies users when the value of invoices or bills surpasses these limits, prompting the application
|
||||
of the appropriate TDS/TCS.
|
||||
|
||||
To configure Odoo to advise you on when to apply TDS/TCS, set the :guilabel:`TDS/TCS section`
|
||||
field on the corresponding account in the chart of accounts. Odoo will display a banner suggesting
|
||||
the TDS/TCS section under which tax might be applicable when recording an invoice or bill.
|
||||
|
||||
Configuration
|
||||
-------------
|
||||
|
||||
#. Navigate to :menuselection:`Accounting --> Configuration --> Settings`.
|
||||
#. In the :guilabel:`Indian Integration` section, enable the :guilabel:`TDS and TCS` feature.
|
||||
#. Navigate to :menuselection:`Accounting --> Configuration --> Chart of Accounts`.
|
||||
#. Click :guilabel:`View` on the desired account, and set the :guilabel:`TDS/TCS Section` field.
|
||||
|
||||
.. note::
|
||||
The TDS/TCS sections are pre-configured with threshold limits. If you need to modify these
|
||||
limits, go to :menuselection:`Accounting --> Configuration --> Taxes`. In the :guilabel:`Advanced
|
||||
Options` tab, click on the :icon:`fa-arrow-right` :guilabel:`(internal link)` icon of the
|
||||
:guilabel:`Section` field.
|
||||
|
||||
.. image:: india/tds-tcs-section-modify.png
|
||||
:alt: TDS/TCS section modify
|
||||
|
||||
Applying TCS/TDS on invoices and bills
|
||||
--------------------------------------
|
||||
|
||||
Based on the account used on the customer invoice or vendor bill, Odoo checks the TCS/TDS threshold
|
||||
limit. If the limit specified in the :guilabel:`TCS/TDS Section` of the account is exceeded, Odoo
|
||||
displays an alert that suggests applying the appropriate TCS/TDS. The alert will disappear once the
|
||||
TCS/TDS is applied.
|
||||
|
||||
.. image:: india/tcs-warning.png
|
||||
:alt: TCS advice
|
||||
|
||||
**TCS** is directly applicable in the tax on the invoice lines. To apply **TDS**, click the
|
||||
:guilabel:`TDS Entry` smart button on the vendor bill/payment. The popup window allows specifying
|
||||
the TDS details. Confirm the entry to apply the TDS.
|
||||
|
||||
.. image:: india/tds-apply.png
|
||||
:alt: TDS application
|
||||
|
||||
In Odoo, the aggregate total is calculated for partners sharing the same PAN number, across all
|
||||
company branches.
|
||||
|
||||
.. example::
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 10 20 10 20 15
|
||||
|
||||
* - **Branch**
|
||||
- **Customer**
|
||||
- **Invoice**
|
||||
- **Transaction Amount (₹)**
|
||||
- **PAN Number**
|
||||
* - IN - MH
|
||||
- XYZ Enterprise - GJ
|
||||
- Invoice 1
|
||||
- ₹50,000
|
||||
- ABCPX1234E
|
||||
* - IN - MH
|
||||
- XYZ Enterprise - GJ
|
||||
- Invoice 2
|
||||
- ₹30,000
|
||||
- ABCPX1234E
|
||||
* - IN - MH
|
||||
- XYZ Enterprise - MH
|
||||
- Invoice 3
|
||||
- ₹40,000
|
||||
- ABCPX1234E
|
||||
* - IN - DL
|
||||
- XYZ Enterprise - GJ
|
||||
- Invoice 4
|
||||
- ₹20,000
|
||||
- ABCPX1234E
|
||||
* - IN - GJ
|
||||
- XYZ Enterprise - MH
|
||||
- Invoice 5
|
||||
- ₹60,000
|
||||
- ABCPX1234E
|
||||
|
||||
- **Aggregate total** = 50,000 + 30,000 + 40,000 + 20,000 + 60,000 = ₹200,000
|
||||
- The aggregate total for all customers (XYZ Enterprise - GJ, MH, DL) sharing the PAN number
|
||||
ABCPX1234E across all branches is ₹200,000.
|
||||
|
||||
|
After Width: | Height: | Size: 5.9 KiB |
|
After Width: | Height: | Size: 10 KiB |
|
After Width: | Height: | Size: 9.2 KiB |
|
Before Width: | Height: | Size: 8.2 KiB |
|
Before Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 5.4 KiB |
|
Before Width: | Height: | Size: 73 KiB |
|
Before Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 9.6 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 9.6 KiB |
|
Before Width: | Height: | Size: 7.9 KiB |
|
Before Width: | Height: | Size: 3.3 KiB |
|
Before Width: | Height: | Size: 39 KiB |
|
Before Width: | Height: | Size: 5.5 KiB |
|
Before Width: | Height: | Size: 11 KiB |
|
Before Width: | Height: | Size: 24 KiB |
|
Before Width: | Height: | Size: 5.5 KiB |
|
Before Width: | Height: | Size: 21 KiB |
|
Before Width: | Height: | Size: 33 KiB |
|
Before Width: | Height: | Size: 9.8 KiB |
|
Before Width: | Height: | Size: 6.9 KiB |
|
Before Width: | Height: | Size: 38 KiB |
|
Before Width: | Height: | Size: 51 KiB |
|
Before Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 65 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 51 KiB |
|
Before Width: | Height: | Size: 33 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 4.4 KiB |
|
Before Width: | Height: | Size: 21 KiB |
|
Before Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 20 KiB |
|
Before Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 31 KiB |
|
Before Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 30 KiB |
|
Before Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 32 KiB |
|
Before Width: | Height: | Size: 10 KiB |
@@ -10,6 +10,7 @@ Daily operations
|
||||
|
||||
operations/adjustments
|
||||
operations/receipts_deliveries
|
||||
operations/process_transfers
|
||||
operations/transfers_scratch
|
||||
operations/barcode_nomenclature
|
||||
operations/gs1_nomenclature
|
||||
|
||||
|
Before Width: | Height: | Size: 76 KiB |
|
Before Width: | Height: | Size: 61 KiB |
|
Before Width: | Height: | Size: 64 KiB |
|
Before Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 7.8 KiB |
|
Before Width: | Height: | Size: 5.4 KiB |
|
Before Width: | Height: | Size: 9.7 KiB |
|
Before Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 2.8 KiB |
@@ -0,0 +1,55 @@
|
||||
=======================
|
||||
Process batch transfers
|
||||
=======================
|
||||
|
||||
The Odoo **Barcode** app can be used to process *Batch*, *Wave*, and *Cluster* transfers that are
|
||||
created in the **Inventory** app.
|
||||
|
||||
.. seealso::
|
||||
This document covers the steps to process transfers in the **Barcode** app. Instructions on
|
||||
creating transfers can be found below:
|
||||
|
||||
- :doc:`../../inventory/shipping_receiving/picking_methods/batch`
|
||||
- :doc:`../../inventory/shipping_receiving/picking_methods/wave`
|
||||
- :doc:`../../inventory/shipping_receiving/picking_methods/cluster`
|
||||
|
||||
Process the batch
|
||||
-----------------
|
||||
|
||||
First, navigate to :menuselection:`Barcode app --> Operations` and select an operation type (like
|
||||
delivery orders) grouped into batches. From here, select the card for the appropriate batch
|
||||
transfer, and click the :guilabel:`BATCH` smart button.
|
||||
|
||||
.. image:: process_transfers/batch-transfer.png
|
||||
:alt: The Delivery Orders page.
|
||||
|
||||
On the batch transfer screen, the products in the picking are grouped by location, and each line is
|
||||
color-coded to associate products in the same picking together.
|
||||
|
||||
Then, follow the prompt to :guilabel:`Scan the source location` barcode for the storage location of
|
||||
the first product. Scan the barcode for the product and package to process the transfer. To record
|
||||
multiple quantities, click the :icon:`fa-pencil` :guilabel:`(edit)` icon, and enter the required
|
||||
quantities for the picking.
|
||||
|
||||
Repeat this for all products, and click the :guilabel:`Validate` button to mark the transfer as
|
||||
:guilabel:`Done`.
|
||||
|
||||
.. note::
|
||||
After creating a batch transfer and assigning a package to a picking, Odoo suggests the specified
|
||||
package by displaying the name *in italics* under the product name, ensuring pickers place
|
||||
products into the correct boxes.
|
||||
|
||||
Products from the same order are labeled with the same color on the left. Completed pickings are
|
||||
highlighted in green.
|
||||
|
||||
.. example::
|
||||
In a batch transfer for 2 `Cabinet with Doors`, 3 `Acoustic Bloc Screens`, and 4 `Four Person
|
||||
Desks`, the `3/3` and `4/4` :guilabel:`Units` indicate that the last two product pickings are
|
||||
complete.
|
||||
|
||||
`1/2` units of the `Cabinet with Doors` has already been picked, and after scanning the product
|
||||
barcode for the second cabinet, Odoo prompts the user to `Scan a serial number` to record the
|
||||
unique serial number for :ref:`product tracking <inventory/product_management/enable-lots>`.
|
||||
|
||||
.. image:: process_transfers/batch-products.png
|
||||
:alt: Products to be picked in barcode view.
|
||||
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 4.5 KiB |
|
Before Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 38 KiB |
|
Before Width: | Height: | Size: 5.2 KiB |
|
Before Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 18 KiB |
|
Before Width: | Height: | Size: 29 KiB |
|
Before Width: | Height: | Size: 13 KiB |