| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Sales (sale_management) |
| Lines of code | 1123 |
| Technical Name |
cerevantix_customer_credit_limit |
| License | OPL-1 |
| Website | https://cerevantix.com |
| Versions | 17.0 18.0 19.0 |
Customer credit control, governed and visible
Set per-customer credit limits, warn or block at quotation, sales order and invoice, and see true exposure — including confirmed-but-uninvoiced orders — across every account on one screen.
Stock Odoo compares one receivable figure to one limit and, at most, warns. There are no tiered thresholds, no grace periods, no governed overrides, no audit trail, and no single view of who is at risk — so overexposure is discovered only after invoices go unpaid.
A focused credit-control workspace: tiered warnings and hard blocking, exposure that counts confirmed uninvoiced orders, configurable overdue grace, account holds with logged overrides, approval-governed increase requests, and a consolidated risk dashboard.
Everything credit control needs
Every capability below is implemented in the module.
Per-Customer Credit Limit
Set an individual credit ceiling on every customer and see used credit, available credit and utilization right on the partner record.
Tiered Warnings & Hard Block
Choose per company: disabled, warn-only, or hard block. A configurable threshold raises an approaching-limit warning before the ceiling is reached.
True Exposure Math
Exposure adds confirmed-but-uninvoiced sales orders to posted receivables, so committed risk is never understated at the moment of confirmation.
Checks at Quote, Order & Invoice
The credit position is validated at quotation, at sales-order confirmation and at customer-invoice posting, so exposure cannot build undetected earlier in the flow.
Account Hold & Order Override
Freeze a whole account with a reason, or let a manager approve one specific order while the customer otherwise stays on hold. Prepaid orders can be exempted.
Overdue Grace Periods
A company-wide grace period, with an optional per-customer override, decides when an invoice counts as overdue — removing false-positive holds the day an invoice ages.
Increase-Request Approvals
Route limit-increase exceptions through a draft, submit and approve workflow. On approval the new limit is applied to the customer and recorded.
Governed, Audited Actions
A dedicated Credit Manager role governs limits, holds and overrides. Every limit change, hold, override and breach is logged with actor, values and reference.
Single-Screen Risk Dashboard
One sortable board lists limit, receivable, uninvoiced, total exposure, available credit, utilization and hold status for every customer, with an alert when a limit is exceeded.
How it works
Set Limits
Configure per-customer limits, grace periods and the enforcement mode.
Sell Safely
Reps see available credit and tiered warnings as they quote and confirm.
Enforce & Override
Over-limit documents warn or block; a manager overrides with a logged reason.
Govern & Review
Approve increase requests and review the audit trail and risk dashboard.
See it in action
Real screens from the module, captured on Odoo 17.
The risk dashboard: limit, receivable, uninvoiced, total exposure, available credit, utilization and hold status for every customer, colour-coded by risk.
The Credit Control tab on a customer: limit, hold, grace override, exposure breakdown and a live over-limit alert.
An account on hold with a recorded reason and a manager-only Release Hold action.
A quotation showing available credit, the customer credit status, a prepaid exemption toggle and an over-limit banner with a manager override.
The same enforcement on a draft customer invoice, warned or blocked before posting.
A limit-increase request with its draft-submit-approve status flow, justification and chatter.
All increase requests with colour-coded submitted, approved and rejected statuses.
The audit log: limit changes, holds, overrides, breaches and approvals with actor, values and reference.
Company settings: enforcement mode, warning threshold, overdue grace period and whether uninvoiced sales count toward exposure.
Frequently asked
Does it warn or actually block over-limit documents?
Both, and it is your choice per company. The enforcement mode can be disabled, warn-only, or hard block, and a configurable threshold raises an early approaching-limit warning before the ceiling.
What counts toward a customer's exposure?
Posted receivables plus, when enabled, confirmed-but-uninvoiced sales orders. That means the available-credit figure reflects real committed risk, not just what has already been invoiced.
Who can change limits or release a hold?
Only users in the dedicated Credit Manager role. Every limit change, hold, override and approval is written to an audit log with the actor, old and new values, and the related document reference.
Can one urgent order go through while the account stays on hold?
Yes. A Credit Manager can override a single sales order or invoice while the account-level hold stays in place, and prepaid orders can be exempted from blocking entirely.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Explore our other apps
A growing suite of Odoo apps.
Empowering growth through technology.
Governed, visible customer credit control — tiered warnings, holds, audited overrides and a single-screen risk dashboard, built natively on Odoo.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Sales (sale_management) |
| Lines of code | 1123 |
| Technical Name |
cerevantix_customer_credit_limit |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module