AI Financial Anomaly & Fraud-Risk Cockpit — Catch the Bills That Shouldn't Be There
Scan your vendor bills, expenses and journal entries for duplicates, split invoices, round and off-hours postings and price outliers — each one scored, explained and linked to the exact document, on a live interactive cockpit. Optional AI analysis. Bring your own API key.
Every anomaly in your books, scored and ready to review — amount at risk, severity, the reason it was flagged and the exact document, at a glance.
- Only catches exact duplicates
- No score, no severity, no reason
- Nothing to review, nothing to act on
- Six anomaly types across bills, expenses and entries
- Every finding scored, explained and linked to its document
- A work-list your team can review, confirm or dismiss — with optional AI
Catch one padded or duplicated bill and it has already paid for itself — many times over.
Act in one click
This is not just a list of findings. When a flagged record needs attention, hit Schedule and its investigation lands as a native Odoo activity — assigned to the analyst, dated and reversible. Or schedule every open finding at once.
The investigation becomes a standard to-do on the flagged record — it shows in the analyst's Activities and inbox. Nothing custom, nothing to learn.
Schedule a single finding from its row, or handle them all in one go with Schedule all open.
Each activity is created for the right analyst and due on the deadline you set in configuration.
It is a standard Odoo activity — mark it done, reschedule or delete it anytime. You confirm before anything is created.
From ledger to review list
Open Fraud Risk. It reads your posted vendor bills, expenses and journal entries — no setup, nothing to import.
One click checks for duplicates, split invoices, round and off-hours postings and price outliers — each scored 0-100 and explained.
Work the list by severity, open the exact document, and mark each finding reviewed, confirmed or dismissed. Nothing is changed for you.
A card for every finding
Click any anomaly for a full card — amount, date, risk score, status, the exact document it points to, the reason it was flagged, an optional AI read and one-click Reviewed / Confirm / Dismiss actions.
Every anomaly linked to its document
A single work-list of every finding — type, the exact record (the bill or entry number), severity, vendor, amount, date and the reason. Sort, filter and group; the whole team sees the same queue.
One click to the source record
Every finding opens the real document — the vendor bill, expense or journal entry — so you can verify it in seconds and move it through New → Reviewed → Confirmed. A full audit trail, right inside Odoo.
AI analysis — optional, your own key
Add your own Anthropic Claude or OpenAI key and get a short forensic read of any finding — and of your overall exposure — plus one verification step, in your language. The module calls the provider directly from your Odoo: no data goes through a third party, and you control the model and the cost. The AI never posts or changes anything.
Set it up once
Choose your scan window and thresholds — approval limit, round-amount floor, price-outlier %, business hours — and, if you want AI, your provider, model and API key. Test the connection in one click.
Features
- Act in one click — schedule an investigation as a native Odoo activity on the flagged record, or on every open finding at once. Reversible from each record.
- Six anomaly detectors — duplicate bills, split invoices (several bills just under the approval limit), suspiciously round amounts, off-hours & weekend postings, price outliers vs the product's own history, and duplicate expenses.
- Risk score (0-100) & severity per finding — so the biggest exposures rise to the top.
- A plain-language reason on every finding — exactly why it was flagged, no black box.
- Linked to the exact document — every finding opens the real bill, expense or journal entry in one click.
- Benford's-law check — a first-digit conformity read on your postings as an early distortion signal.
- Live interactive cockpit — KPIs (findings, high-risk, amount at risk, Benford), severity segments and an anomalies-by-type chart; filter and drill down, not a static report.
- Review workflow — move each finding New → Reviewed → Confirmed or dismiss it, for a clean audit trail.
- Daily automatic scan — a scheduled action keeps the list fresh; re-scan on demand anytime.
- AI analysis (optional) — Anthropic Claude or OpenAI, your own key; a forensic read and a verification step, in your language.
- Works on any Odoo — computes from standard accounting data; expenses are picked up automatically if the Expenses app is installed. Community and Enterprise.
- Multilingual — English, Spanish, French, German, Italian and Portuguese (BR).
Perfect for finance, controllership, internal audit and accounts-payable teams that need to spot suspicious postings early, prioritize what to review and keep a defensible trail — not just eyeball the ledger.
Keywords: fraud detection, financial anomaly detection, duplicate invoice detection, duplicate payment detection, split invoice detection, Benford's Law analysis, internal audit tool, forensic accounting, expense fraud detection, vendor bill fraud, invoice fraud prevention, accounts payable fraud, journal entry anomalies, round number postings, off-hours postings, price outlier detection, AP fraud cockpit, risk scoring, internal controls Odoo, audit trail anomalies, Anthropic Claude, OpenAI, AI fraud analysis.
Palabras clave: detección de fraude, detección de anomalías financieras, facturas duplicadas, pagos duplicados, división de facturas, ley de Benford, auditoría interna, contabilidad forense, fraude en gastos, fraude en facturas de proveedor, prevención de fraude en facturas, fraude en cuentas por pagar, anomalías en asientos contables, montos redondos sospechosos, registros fuera de horario, precios atípicos, control interno Odoo, puntuación de riesgo, auditoría de transacciones, IA, inteligencia artificial, Claude, OpenAI.
Permissions & data security
Built to respect Odoo's access model — audited so nothing leaks between users or companies.
- 🏢 Multi-company isolation. Every record and setting is tagged to its company; a user only ever sees the data of the companies they are allowed into. Cross-company access is impossible — verified.
- 🔑 AI key encrypted & admin-only. Your provider key is stored encrypted at rest (Fernet / AES) — the plaintext is never saved — and is readable or editable only by a system administrator.
- 👤 Role-based access. The app respects Odoo's access groups — there is no portal or public exposure. Everything computes on your standard data through the app's own service, so no restricted field is ever surfaced.
- ✅ Secure by design — multi-company isolation; AI key encrypted at rest and admin-only. Audited across the whole suite.
Requires the Accounting/Invoicing app. Works with Odoo Community and Enterprise.
More from the author: Aski — ask your Odoo in natural language by chat or voice, and get real figures from your phone. https://aski.dev
Questions, or want a quick personalized demo? Email me at jhonrojas.dev@gmail.com — I am happy to answer questions or set up a short demo.
Support: jhonrojas.dev@gmail.com · License: OPL-1
About the author
Jhon Jairo Rojas Ortiz
Odoo developer · custom modules, integrations & business intelligence
5+ years of hands-on Odoo experience — building and shipping real modules, integrations and analytics for companies across LATAM and Europe. Every app I publish is maintained and supported personally.
Custom Odoo modulesIntegrations & APIsBI & analyticsOdoo 14–19
inConnect on LinkedIn →| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 1366 |
| Technical Name |
jjro_fraud_risk |
| License | OPL-1 |
| Website | https://aski.dev |
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