e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
73 lines
2.5 KiB
ReStructuredText
73 lines
2.5 KiB
ReStructuredText
====================================
|
|
How to forecast future bills to pay?
|
|
====================================
|
|
|
|
When you get hundreds of vendor bills per month with each of them having
|
|
different payment terms, it could be complex to follow what you have to
|
|
pay and when. Paying your vendors too early can decrease your cash
|
|
availabilities and paying too late can lead to extra charges.
|
|
|
|
Fortunately, Odoo provides you the right tools to manage payment orders
|
|
to vendors efficiently.
|
|
|
|
Configuration: payment terms
|
|
============================
|
|
|
|
In order to track the vendor conditions, we use payment terms in Odoo.
|
|
Payment terms allow to keep track of the conditions to compute the due
|
|
date on an invoice. As an example, a payment term can be:
|
|
|
|
- 50% within 30 days
|
|
|
|
- 50% within 45 days
|
|
|
|
To create your most common payment terms, use the menu: :menuselection:`Configuration -->
|
|
Management --> Payment Terms` in the **Accounting** application. The following
|
|
example show a payment term of 30% directly and the balance after 30
|
|
days.
|
|
|
|
.. image:: ./media/forecast01.png
|
|
:align: center
|
|
|
|
Once payment terms are defined, you can assign them to your vendor by
|
|
default. Set the Vendor Payment Term field on the Accounting tab of a
|
|
vendor form. That way, every time you will purchase to this vendor, Odoo
|
|
will propose you automatically the right payment term.
|
|
|
|
.. image:: ./media/forecast02.png
|
|
:align: center
|
|
|
|
.. note::
|
|
|
|
If you do not set a specific payment term on a vendor, you will still be
|
|
able to set a specific payment term on the vendor bill.
|
|
|
|
Forecast bills to pay with the Aged Payables report
|
|
===================================================
|
|
|
|
In order to track amounts to be paid to the vendors, use the Aged
|
|
Payable report. You can get it from the Reports menu of the Accounting
|
|
application. This report gives you a summary per vendor of the amounts
|
|
to pay, compared to their due date (the due date being computed on each
|
|
bill using the payment term).
|
|
|
|
.. image:: ./media/forecast03.png
|
|
:align: center
|
|
|
|
This reports tells you how much you will have to pay within the next
|
|
months.
|
|
|
|
Select bills to pay
|
|
===================
|
|
|
|
Using the menu :menuselection:`Purchases --> Vendor Bills`, you can get a list of vendor
|
|
bills. Using the advanced filters, you can list all the bills that you
|
|
should pay or the bills that are overdue (you are late on the payment).
|
|
|
|
.. image:: ./media/forecast04.png
|
|
:align: center
|
|
|
|
From this screen, you can also switch to the pivot table or the graph
|
|
view to get statistics on the amount due over the next month, using the
|
|
group by "Due Date" feature.
|