Skip to content

Commit b71ddf9

Browse files
committed
[IMP] accounting: update page with new annual closing feature
task-5254108 closes #15255 Signed-off-by: Anne-Françoise Marcq (afma) <afma@odoo.com>
1 parent 5df8dc7 commit b71ddf9

File tree

3 files changed

+129
-24
lines changed

3 files changed

+129
-24
lines changed

content/applications/finance/accounting.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -121,9 +121,9 @@ accounting and reporting rules, including the following:
121121
:doc:`main currency <accounting/get_started/multi_currency>`, and :doc:`taxes <accounting/taxes>`
122122
apply to all branches.
123123
- Branches can manage their own dedicated journals and related records.
124-
- The parent company manages a common :ref:`fiscal period <year-end/fiscal-years>`, so its
125-
:ref:`lock and closing dates <year-end/lock-everything-date>` apply across all branches. However,
126-
branches may set earlier lock dates if needed.
124+
- The parent company manages a common :ref:`fiscal period <accounting/year-end/fiscal-years>`, so
125+
its :ref:`lock and closing dates <accounting/year-end/lock-everything-date>` apply across all
126+
branches. However, branches may set earlier lock dates if needed.
127127
- The parent company can access all :doc:`reports <accounting/reporting>`, :doc:`invoices
128128
<accounting/customer_invoices>`, :doc:`bills <accounting/vendor_bills>`, etc., from its branches,
129129
while each branch can only view its own data.

content/applications/finance/accounting/reporting/tax_returns.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -255,8 +255,8 @@ refunded.
255255

256256
- :guilabel:`Reverse Entry`
257257
- :guilabel:`Reset to Draft`: The :guilabel:`Lock Tax Return` date must be manually removed
258-
using a :ref:`lock date exception <year-end/lock-date-exception>` to reset a tax return entry
259-
to draft.
258+
using a :ref:`lock date exception <accounting/year-end/lock-date-exception>` to reset a tax
259+
return entry to draft.
260260

261261
.. _accounting/tax-returns/vat-return-pay:
262262

content/applications/finance/accounting/reporting/year_end.rst

Lines changed: 124 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,13 @@
22
Year-end closing
33
================
44

5-
Year-end closing is vital for maintaining financial accuracy, complying with regulations, making
5+
Year-end closing is essential for maintaining financial accuracy, complying with regulations, making
66
informed decisions, and ensuring transparency in reporting.
77

88
.. seealso::
99
:doc:`Tax return <tax_returns>`
1010

11-
.. _year-end/fiscal-years:
11+
.. _accounting/year-end/fiscal-years:
1212

1313
Fiscal years
1414
============
@@ -28,30 +28,34 @@ If the period lasts *more* than or *less* than 12 months, enable :guilabel:`Fisc
2828
Once the set fiscal period is over, Odoo automatically reverts to the default periodicity,
2929
considering the value specified in the :guilabel:`Last Day` field.
3030

31-
.. _year-end/checklist:
31+
.. _accounting/year-end/checklist:
3232

3333
Year-end checklist
3434
==================
3535

36-
.. _year-end/before-closure:
36+
.. _accounting/year-end/before-closure:
3737

3838
Before closure
3939
--------------
4040

4141
Before closing a fiscal year, ensure that everything is accurate and up-to-date:
4242

43-
- Make sure all bank accounts are fully :doc:`reconciled <../bank/reconciliation>` up to year-end,
43+
- Make sure all bank accounts are fully :doc:`reconciled <../bank/reconciliation>` up to year-end
4444
and confirm that the ending book balances match the bank statement balances.
45-
- Verify that all :doc:`customer invoices <../customer_invoices>` have been created and
46-
confirmed and that there are no draft invoices.
47-
- Confirm that all :doc:`vendor bills <../vendor_bills>` have been created and confirmed.
45+
- Confirm that all :doc:`customer invoices <../customer_invoices>` and :doc:`vendor bills
46+
<../vendor_bills>` have been created and all draft entries have been either confirmed or
47+
cancelled, as needed.
4848
- Ensure the accuracy of all :doc:`expenses <../../expenses>` and validate them.
4949
- Check that all :doc:`received payments <../payments>` have been encoded and confirmed.
5050
- Close all :ref:`suspense accounts <accounting/journals/bank-cash-cc>`.
51+
- Ensure :doc:`loans <../bank/loans>` are properly registered for automatic amortization
52+
calculations.
53+
- Review overdue payables and receivables aged over 60 days, and assess whether a provision for
54+
uncertain liabilities or an allowance for doubtful accounts is required.
5155
- Book all :doc:`depreciation <../vendor_bills/assets>` and :doc:`deferred revenue
5256
<../customer_invoices/deferred_revenues>` entries.
5357

54-
.. _year-end/closing-a-fiscal-year:
58+
.. _accounting/year-end/closing-a-fiscal-year:
5559

5660
Closing a fiscal year
5761
---------------------
@@ -62,7 +66,7 @@ Then, to close the fiscal year:
6266
correct.
6367
- Reconcile all accounts on the :ref:`balance sheet <accounting/reporting/balance-sheet>`:
6468

65-
- Update the bank balances in Odoo according to the actual balances found on the bank statements.
69+
- Update the bank balances in Odoo to reflect the actual balances as per the bank statements.
6670
- Reconcile all transactions in the cash and bank accounts by running the :ref:`aged receivables
6771
<accounting/reporting/aged-receivable>` and :ref:`aged payables
6872
<accounting/reporting/aged-payable>` reports.
@@ -87,13 +91,14 @@ loans, bank accounts, prepayments, sales tax statements) to compare them against
8791
recorded in Odoo.
8892

8993
.. tip::
90-
As part of this process, setting a :ref:`Lock Everything <year-end/lock-everything-date>` date to
91-
the last day (inclusive) of the preceding fiscal year is good practice. This ensures that journal
92-
entries with an accounting date on or before the lock date cannot be created or modified during
93-
the audit. Users with *administrator* access rights can still create and edit entries if an
94-
exception is configured.
94+
As part of this process, setting a :ref:`Lock Everything
95+
<accounting/year-end/lock-everything-date>` date to the last day (inclusive) of the preceding
96+
fiscal year is good practice. This ensures that journal entries with an accounting date on or
97+
before the lock date cannot be created or modified during the audit. Users with *administrator*
98+
access rights can still create and edit entries if an :ref:`exception is configured
99+
<accounting/year-end/lock-date-exception>`.
95100

96-
.. _year-end/lock-everything-date:
101+
.. _accounting/year-end/lock-everything-date:
97102

98103
Lock everything date
99104
~~~~~~~~~~~~~~~~~~~~
@@ -108,9 +113,9 @@ Dates`. In the :guilabel:`Lock Journal Entries` window, set the :guilabel:`Lock
108113
:guilabel:`Save`.
109114

110115
After setting the :guilabel:`Lock Everything` date, an :ref:`exception
111-
<year-end/lock-date-exception>` can be made if a modification is necessary.
116+
<accounting/year-end/lock-date-exception>` can be made if a modification is necessary.
112117

113-
.. _year-end/lock-date-exception:
118+
.. _accounting/year-end/lock-date-exception:
114119

115120
Lock date exception
116121
*******************
@@ -133,7 +138,7 @@ Accounting app can create exceptions. To do so:
133138
:guilabel:`Hard Lock` date, which is irreversible to ensure inalterability and to meet accounting
134139
requirements in certain countries.
135140

136-
.. _year-end/current-year-earnings:
141+
.. _accounting/year-end/current-year-earnings:
137142

138143
Current year's earnings
139144
~~~~~~~~~~~~~~~~~~~~~~~
@@ -158,3 +163,103 @@ balance. If so, a :guilabel:`Hard Lock date` can be set to the last day of the f
158163
compliance is not applicable, setting this field may not be necessary. However, if required, the
159164
date should only be set once it is confirmed to be correct, as it **cannot be changed or
160165
overridden**, regardless of access rights.
166+
167+
.. _accounting/year-end/annual-closing:
168+
169+
Annual closing
170+
==============
171+
172+
To complete the fiscal year-end process and finalize the annual closing, go to the Accounting
173+
dashboard and click :guilabel:`Tax Returns` on the :guilabel:`Tax Returns` journal from the
174+
Accounting dashboard. Alternatively, go to :menuselection:`Accounting --> Accounting --> Tax
175+
Returns`.
176+
177+
This view displays a chronological list of all pending returns including :ref:`tax returns
178+
<accounting/tax-returns/vat-report>`, :ref:`advance payments
179+
<accounting/tax-returns/advance-payments>` (based on the :doc:`fiscal localization
180+
<../../fiscal_localizations>`), and annual closings. A pending :guilabel:`Annual Closing` follows
181+
two steps: :ref:`review <accounting/year-end/annual-closing/review>` and :ref:`submit
182+
<accounting/year-end/annual-closing/submit>`. The :guilabel:`Annual Closing` item includes:
183+
184+
- A period (year).
185+
- A deadline date.
186+
- The related company and :ref:`branch(es) <general/branches>`, if applicable.
187+
- Action steps, such as :ref:`Review <accounting/year-end/annual-closing/review>` and :ref:`Submit
188+
<accounting/year-end/annual-closing/submit>`, which turn green when completed.
189+
- Action buttons for key tasks.
190+
- A :icon:`fa-ellipsis-v` :guilabel:`(vertical ellipsis)` menu for additional options.
191+
192+
.. note::
193+
- Before the annual closing is reviewed, the number of :guilabel:`Pending` or :guilabel:`Passed`
194+
closing validation checks is displayed in red or green, respectively.
195+
- If the :guilabel:`Deadline` date has passed, it appears in red.
196+
197+
.. _accounting/year-end/annual-closing/review:
198+
199+
Review
200+
------
201+
202+
To start reviewing an annual closing, click the annual closing line. The annual closing checks view
203+
displays the following, depending on the :doc:`fiscal localization <../../fiscal_localizations>`:
204+
205+
- :guilabel:`Aged payables per partner`: Review payables without a partner.
206+
- :guilabel:`Aged receivables per partner`: Review receivables without a partner.
207+
- :guilabel:`Bank Reconciliation`: Reconcile all bank account transactions up to year-end.
208+
- :guilabel:`Deferred Entries`: Ensure start and end dates are correctly set on bills and
209+
invoices.
210+
- :guilabel:`Earnings Allocation`: After adjustments, transfer the undistributed profits/losses to
211+
an equity account.
212+
- :guilabel:`Fixed Assets`: Ensure assets are properly registered for automatic depreciation
213+
calculation.
214+
- :guilabel:`Loans`: Ensure loans are properly registered for automatic amortization calculations.
215+
- :guilabel:`Manual Adjustments`: Complete any necessary manual adjustments and internal checks.
216+
- :guilabel:`No draft entries`: Review and post draft invoices, bills, and entries in the period,
217+
or change their accounting date.
218+
- :guilabel:`Overdue payables`: Review overdue payables aged over 60 days and assess the need for
219+
an allowance for uncertain liabilities.
220+
- :guilabel:`Overdue receivables`: Review overdue receivables aged over 60 days and assess the
221+
need for an allowance for doubtful accounts or expected credit loss provision, as per IFRS 9
222+
guidelines.
223+
- :guilabel:`Total Receivables`: Verify that the total aged receivables equals the customer
224+
account balance.
225+
- :guilabel:`Total payables`: Verify that the total aged payables equals the vendor account
226+
balance.
227+
228+
Some of the checks are performed automatically, while others serve as reminders to review essential
229+
tasks. Each check card is either labeled as:
230+
231+
- :guilabel:`Reviewed` (highlighted in green): The check has passed.
232+
- :guilabel:`To review` (highlighted in grey): Action is required before the check can be manually
233+
marked as :guilabel:`Reviewed` or :guilabel:`Supervised`.
234+
- :guilabel:`Anomaly` (highlighted in red): The automatic check detects an issue. There are two
235+
options:
236+
237+
- Click the failed check's card to fix the issue.
238+
- Click :guilabel:`Anomaly` and select :guilabel:`Reviewed` or :guilabel:`Supervised` to pass the
239+
check without fixing the issue.
240+
241+
Once all closing validation checks have passed, either labeled as :guilabel:`Reviewed` or
242+
:guilabel:`Supervised`, click :guilabel:`Validate` to complete the :guilabel:`Review` step. The
243+
annual closing can then be :ref:`submitted <accounting/year-end/annual-closing/submit>`.
244+
245+
.. tip::
246+
- To add customized checks, activate :ref:`developer mode <developer-mode>`, and go to
247+
:menuselection:`Accounting --> Configuration --> Check`. Then, click :guilabel:`New` and
248+
complete the necessary fields.
249+
- All check status changes are logged in the chatter.
250+
251+
.. _accounting/year-end/annual-closing/submit:
252+
253+
Submit
254+
------
255+
256+
Once a tax return has completed the :ref:`Review <accounting/tax-returns/vat-return-review>` step,
257+
click :guilabel:`Submit`.
258+
259+
If a :guilabel:`Submission Instructions` pop-up window appears, depending on the :doc:`fiscal
260+
localization <../../fiscal_localizations>`, follow the local :guilabel:`Instructions`, and click
261+
:guilabel:`Mark as Submitted`.
262+
263+
.. tip::
264+
To review checks before submitting the annual closing, click the :icon:`fa-ellipsis-v`
265+
:guilabel:`(vertical ellipsis)` icon on the annual closing line and select :guilabel:`Reset`.

0 commit comments

Comments
 (0)