CRIBIS Credit Limit Link
A thin bridge that lets the CRIBIS credit capacity set a customer credit limit and a red CRIBIS semafor block an over risk invoice, cleared by a manager override on the invoice. Auto installs when both CRIBIS Business Data and Customer Credit Limit are present.
Why this module
Turn a risk grade into a posting gate.
The external capacity becomes the internal limit
When a report is applied, the CRIBIS credit capacity is converted to the company currency and written to the partner credit limit override, so the number the credit gate enforces comes from the rating, not a guess.
A red semafor blocks an over risk invoice
Posting a customer invoice or refund for a red semafor contact is refused until a manager records an override reason on that specific invoice, reusing the credit limit gate's own positive act so there is one override story, not two.
Two switches, both off by default
Auto credit limit and block on red are independent settings under the CRIBIS configuration, so a deployment turns on exactly the wiring it wants and nothing changes until it does.
Day in the life
A risky customer is priced and gated automatically
A clerk pulls a CRIBIS report on a new customer. Its capacity sets the credit limit; its red semafor is noted. The clerk drafts an invoice and tries to post it. The gate refuses and names the risk. A manager reviews, records a reason on the invoice, and the post goes through, with the override written to the chatter.
Edge cases
The cases most modules quietly ignore.
In the shipped code today, each one a place where a cheaper module silently does the wrong thing.
The credit capacity is converted from its source currency to the company currency before it becomes the limit, so the gate always compares like with like.
Clearing one red semafor invoice does not clear the next; each over risk post needs its own recorded reason.
What is inside
Built to do the job, end to end.
- Partner hook. Extends the CRIBIS apply hook to write the credit limit from the capacity when the setting is on, with a chatter note recording the change.
- Post gate. Extends account.move posting to refuse a red semafor customer invoice unless an override reason is present, reusing the credit limit module's override field.
Honest about the edges
What this does not do, so nothing surprises you.
- This bridge only acts when the separate Customer Credit Limit module is installed; it auto installs alongside it and does nothing on its own.
- Both behaviours are opt in and off until switched on in the CRIBIS settings.
- The red semafor value comes from the CRIBIS data; keeping it current is a matter of pulling reports or running monitoring.
odoo credit limit from rating, block invoice on risk, cribis credit control, customer risk posting gate, credit hold from external score, auto credit limit odoo, risk based invoicing odoo
A red semafor holds the invoice
When the CRIBIS semafor is red, posting a customer invoice is blocked until a manager records an override reason, which is written to the invoice chatter. Both behaviours are opt in from the CRIBIS settings.
Blocked at post time, not just flaggedThe post is refused with a clear message naming the risk, and the CRIBIS credit capacity drives the customer credit limit.
Two switches, both off by defaultSet the credit limit from CRIBIS, and block invoices on a red semafor, each turned on only when you want it.
Languages
Available in 19 languages
The interface ships translated out of the box. Switch language in Odoo and the fields, menus, and messages follow.
Please log in to comment on this module