Antoine Vandevenne (anv)
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
71 lines
2.6 KiB
ReStructuredText
71 lines
2.6 KiB
ReStructuredText
=========================================
|
|
Follow-up on invoices and get paid faster
|
|
=========================================
|
|
|
|
It is essential for your business to collect payments when they are
|
|
overdue. Odoo will help you identify payments that are late and will
|
|
allow you to send the appropriate reminders.
|
|
|
|
Manage your follow-ups
|
|
======================
|
|
|
|
.. tip::
|
|
We recommend that you reconcile your bank statements before
|
|
launching your follow-up process. It will avoid you the trouble of
|
|
sending a statement to a customer that has already paid you.
|
|
|
|
The overdue invoices you need to follow-up on are available by default
|
|
in :menuselection:`Accounting --> Sales --> Follow-up Reports`. There,
|
|
you can easily send a reminder by email or print it as a letter. Then,
|
|
you can click on the *Done* button to view the next follow-up that
|
|
needs your attention.
|
|
|
|
Otherwise, if now is not the time for a reminder, click on *Remind me
|
|
later*. You will get the next report according to the *Next Reminder
|
|
Date* set on the statement.
|
|
|
|
.. tip::
|
|
To avoid sending too many reminders in a short period of time,
|
|
change the number of days calculated between each report by going to
|
|
:menuselection:`Accounting --> Configuration --> Settings --> Payment
|
|
Follow-up`.
|
|
|
|
You can also set a trust level for your customers by marking them as
|
|
bad, normal or good debtors on the follow-up reports.
|
|
|
|
.. image:: media/followup01.png
|
|
:align: center
|
|
|
|
Send reminders in batch
|
|
=======================
|
|
|
|
To get your follow-up process easier, you can send reminder emails in
|
|
batch from your follow-up reports page. Select all the reports you would
|
|
like to process, click on *Action* and then on *Process Follow-ups*.
|
|
A pdf document containing all of the follow-up letters for you to print
|
|
will also be automatically generated.
|
|
|
|
.. image:: media/followup02.png
|
|
:align: center
|
|
|
|
Plan a follow-up process
|
|
========================
|
|
|
|
To plan a follow-up process, go to :menuselection:`Accounting -->
|
|
Configuration --> Settings` and activate the *Follow-up Levels*
|
|
feature under the *Customer Payments* section. Then, click on the new
|
|
*Follow-up Levels* button that has appeared on your settings page.
|
|
|
|
A follow-up plan with several actions is available by default in Odoo,
|
|
but you can customize it any way you want. Depending on a specific
|
|
number of overdue days, plan to send an email, a letter or to undertake
|
|
a manual action. You can also edit the template used for the statement
|
|
according to the stage of the process.
|
|
|
|
.. image:: media/followup03.png
|
|
:align: center
|
|
|
|
.. tip::
|
|
If you would like to get a reminder before the actual due date,
|
|
set a negative number of due days.
|