README.rst

Account Credit Control

Account Credit Control module is a part of Financial Tools used in business to ensure that once sales are made they are realised as cash. This module helps to identify outstanding debt beyond tolerance level and setup followup method.

Table of contents

• Configuration
• Usage
• Bug Tracker
• Credits
  • Authors
  • Contributors
  • Maintainers

Configuration

Configure the policies and policy levels in Invoicing > Configuration > Credit Control > Credit Control Policies. You can define as many policy levels as you need. You must set on which accounts are applied every Credit Control Policy under Accounts tab.

Configure a tolerance for the Credit control and a default policy applied on all partners in each company, under the Accounting tab in your company form.

You are able to specify a particular policy for one partner or one invoice.

Usage

Menu entries are located in Invoicing > Adviser > Credit Control.

Create a new "run" in the Credit Control Run menu with the controlling date. Then, use the Compute Credit Lines button. All the credit control lines will be generated. You can find them in the Credit Control Lines menu.

On each generated line, you have many choices:

• Send a email
• Print a letter
• Change the state (so you can ignore or reopen lines)
• Mark a line as Manually Overridden. The line will get the ignored state when a second credit control run is done.
• Mark one line as Manual followup will also mark all the lines of the partner. The partner will be visible in "Do Manual Follow-ups".

Once your lines are properly set up, go back to the "run" and click on Run channel action to massively generate and queue communication emails or letters for all linked lines.

Then, use the Communications smart button to see all email communication processes that have been created and follow them.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

• Camptocamp
• Okia
• Access Bookings
• Tecnativa
• ACSONE SA/NV

Contributors

• Nicolas Bessi (Camptocamp)
• Guewen Baconnier (Camptocamp)
• Sylvain Van Hoof (Okia SPRL) <[email protected]>
• Akim Juillerat (Camptocamp) <[email protected]>
• Kinner Vachhani (Access Bookings Ltd) <[email protected]>
• Raf Ven <[email protected]>
• Quentin Groulard (ACSONE) <[email protected]>
• Tecnativa:
  • Vicent Cubells
  • Manuel Calero
  • Ernesto Tejeda
  • Pedro M. Baeza
  • Jairo Llopis
  • João Marques
  • Víctor Martínez
• Enric Tobella <[email protected]>
• Naglis Jonaitis (Versada UAB) <[email protected]>

Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/credit-control project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.