Search 1.9 billion lines of Odoo code on GitHub
contract
<a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg">
</a>
<a name="contracts-for-recurrent-invoicing"></a>
<h2>Contracts for recurrent invoicing</h2>
<p>This module forward-port to v10 the contracts management with recurring
invoicing functions. Also you can print and send by email contract report.</p>
<p>In upstream Odoo, this functionality was moved into the Enterprise edition.</p>
<a name="configuration"></a>
<h3>Configuration</h3>
<p>To view discount field set <em>Discount on lines</em> in user access rights.</p>
<p>You might find that generating all pending invoices at once takes too much
time and produces some performance problems, mostly in cases where you
generate a lot of invoices in little time (i.e. when invoicing thousands
of contracts yearly, and you get to January 1st of the next year). To avoid
this bottleneck, the trick is to <strong>increase the cron frequence and decrease
the contracts batch size</strong>. The counterpart is that some invoices could not
be generated in the exact day you expected. To configure that:</p>
<ol class="arabic simple">
<li>Go to <em>Settings > Activate the developer mode</em>.</li>
<li>Go to <em>Settings > Technical > Automation > Scheduled Actions >
Generate Recurring Invoices from Contracts > Edit > Information</em>.</li>
<li>Set a lower interval. For example, change <em>Interval Unit</em> to <em>Hours</em>.</li>
<li>Go to the <em>Technical Data</em> tab, and add a batch size in <em>Arguments</em>.
For example, it should look like <code>(20,)</code>.</li>
<li>Save.</li>
</ol>
<p>That's it! From now on, only 20 invoices per hour will be generated.
That should take only a few seconds each hour, and shouln't block other users.</p>
<a name="usage"></a>
<h3>Usage</h3>
<p>To use this module, you need to:</p>
<ol class="arabic simple">
<li>Go to Accounting -> Contracts and select or create a new contract.</li>
<li>Check <em>Generate recurring invoices automatically</em>.</li>
<li>Fill fields for selecting the recurrency and invoice parameters:<ul>
<li>Journal</li>
<li>Pricelist</li>
<li>Period. It can be any interval of days, weeks, months, months last day or
years.</li>
<li>Start date and next invoice date.</li>
<li>Invoicing type: pre-paid or post-paid.</li>
</ul>
</li>
<li>Add the lines to be invoiced with the product, description, quantity and
price.</li>
<li>You can mark Auto-price? for having a price automatically obtained applying
the pricelist to the product price.</li>
<li>You have the possibility to use the markers #START# or #END# in the
description field to show the start and end date of the invoiced period.</li>
<li>Choosing between pre-paid and post-paid, you modify the dates that are shown
with the markers.</li>
<li>A cron is created with daily interval, but if you are in debug mode, you can
click on <em>Create invoices</em> to force this action.</li>
<li>Click <em>Show recurring invoices</em> link to show all invoices created by the
contract.</li>
<li>Click on <em>Print > Contract</em> menu to print contract report.</li>
<li>Click on <em>Send by Email</em> button to send contract by email.</li>
</ol>
<a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/110/10.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a>
<a name="known-issues-roadmap"></a>
<h3>Known issues / Roadmap</h3>
<ul class="simple">
<li>Recover states and others functional fields in Contracts.</li>
</ul>
<a name="bug-tracker"></a>
<h3>Bug Tracker</h3>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/contract/issues">GitHub Issues</a>. In case of trouble, please
check there if your issue has already been reported. If you spotted it first,
help us smashing it by providing a detailed and welcomed feedback.</p>
<a name="credits"></a>
<h3>Credits</h3>
<a name="contributors"></a>
<h4>Contributors</h4>
<ul class="simple">
<li>Pedro M. Baeza <<a class="reference external" href="mailto:pedro.baeza@tecnativa.com">pedro.baeza@tecnativa.com</a>></li>
<li>Carlos Dauden <<a class="reference external" href="mailto:carlos.dauden@tecnativa.com">carlos.dauden@tecnativa.com</a>></li>
<li>Angel Moya <<a class="reference external" href="mailto:angel.moya@domatix.com">angel.moya@domatix.com</a>></li>
<li>Dave Lasley <<a class="reference external" href="mailto:dave@laslabs.com">dave@laslabs.com</a>></li>
<li>Vicent Cubells <<a class="reference external" href="mailto:vicent.cubells@tecnativa.com">vicent.cubells@tecnativa.com</a>></li>
</ul>
<a name="maintainer"></a>
<h4>Maintainer</h4>
<a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
<p>This module is maintained by the OCA.</p>
<p>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.</p>
<p>To contribute to this module, please visit <a class="reference external" href="https://odoo-community.org">https://odoo-community.org</a>.</p>