| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Contacts (contacts)
• Discuss (mail) |
| Lines of code | 2383 |
| Technical Name |
eh_cribis |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Versions | 16.0 17.0 18.0 19.0 |
CRIBIS Business Data
Bring the CRIBIS view of a Czech business partner straight onto the Odoo contact: the ten grade index and semafor, probability of default, credit capacity, financials, people and alerts, with background change monitoring that reaches a real person instead of sitting in a table.
Why this module
The credit view of a business partner, native on the contact.
A real Odoo page, not an embedded viewer
The index, semafor, probability of default, credit capacity, financials, people, related entities and alerts are proper Odoo fields and models on res.partner, so they filter, group, report and drive automation like any other data. A risk band ribbon and coloured badges read at a glance.
Mock mode demos and tests offline
A fresh install answers from shipped fixtures keyed by registration number, so the module works, demos and runs its full test suite with no network and no paid credit. Drop credentials in the settings, turn mock off, and the same code speaks the live REST or web service channel through one mapping table.
Changes become chatter and activities
A scheduled job pulls change notifications for monitored companies. Each change is posted to the contact chatter and a serious change schedules a to do activity for the salesperson, so an insolvency or an over indebtedness reaches a human instead of sitting silently in a table.
Day in the life
From a registration number to a scored, watched contact
A user opens a company contact, enters its registration number and presses Get microreport. The index, semafor, probability of default, credit capacity, financials, people and alerts populate in one step, and the pull is frozen as a dated snapshot. They enable monitoring with one click. Days later the scheduled job pulls an insolvency notice, posts it to the chatter and raises a review activity, and if the credit bridge is installed the next over risk invoice is held until a manager signs it off.
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.
A report snapshot refuses edits to its figures after it is written; a fresh pull adds a new dated row instead of overwriting history, so the risk trail cannot be quietly rewritten.
Mock mode answers from fixtures, so the module is demonstrable and fully tested offline; a generic subject resolves for an unknown registration number rather than failing.
The payload shape lives in a single mapping layer. When the provider renames a field, a deployment retunes one table, not the models or the views.
The monitoring cron isolates failures per subscription and logs them, so a single unreachable subject cannot abort the whole poll.
What is inside
Built to do the job, end to end.
- Swappable client (cribis.client). An abstract service that hides three transports behind one API: mock fixtures, the REST channel and the web service channel, with OAuth, API key or basic authentication and a cached token. Every method returns a plain payload, so it never knows the shape of a contact.
- One mapping table (cribis.mapping). The only place that knows the CRIBIS payload shape. It normalizes a raw response into the values written onto the contact and the snapshot, so pointing the connector at another contract is a matter of editing paths here.
- Snapshots and child models. cribis.report freezes each pull with its raw payload; cribis.alert, cribis.financial, cribis.person and cribis.related hold the alert feed, financial history, statutory people and related entities as first class records.
- Monitoring and notifications. cribis.monitoring registers watched subjects and a daily cron turns changes into cribis.notification records that post to chatter and schedule activities.
Honest about the edges
What this does not do, so nothing surprises you.
- Live CRIBIS calls require your own CRIBIS Connected account and the final endpoint mapping for your contract. The module ships in mock mode and includes the REST and web service transports ready to wire.
- The relationship graph and full company history are surfaced as link out fields to the provider, not rebuilt inside Odoo.
- Setting a customer credit limit from the credit capacity and blocking a red semafor invoice are provided by the separate credit limit bridge, which auto installs only when the Customer Credit Limit module is present.
odoo cribis, czech company credit report, ICO lookup odoo, business register enrichment, credit risk monitoring odoo, credit index semafor, probability of default odoo, credit limit from external rating, res partner credit data, business intelligence connector odoo, company monitoring notifications, cribis connected api, odoo 19 credit data, supplier risk odoo, customer risk scoring
The credit view, native on the Odoo contact
Real Odoo fields, badges and a risk band ribbon, with an alert and change feed you can filter, group and report on. Populated here from the shipped mock so it demos with no live account.
The whole credit view, in one placeIndex grade, three light semafor, probability of default, credit capacity, financials and classification, a risk band ribbon, and a one click microreport.
A real alert and change feedShort codes, severity grading and historical flags as first class records, not a static widget.
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