Interactive aged-balance dashboards for Odoo with configurable buckets, customer/vendor drill-down, multi-currency views and collection-priority scoring. Built to order, installed and supported by ECOSIRE on Odoo 17, 18 and 19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $199.00 USD; request a quote for a scoped proposal.

Interactive aged-balance dashboards for Odoo with configurable buckets, customer/vendor drill-down, multi-currency views and collection-priority scoring. Built to order, installed and supported by ECOSIRE on Odoo 17, 18 and 19.
لا حاجة للدفع الآن. يؤدي هذا إلى إرسال طلب عرض سعر إلى فريقنا — وسنتواصل معك عبر البريد الإلكتروني بالأسعار والخطوات التالية.
Every credit controller knows the pain: Odoo's stock Aged Receivable and Aged Partner Balance reports give you fixed 30/60/90/120 buckets, a partner ledger you have to read line by line, and a PDF that is stale the moment it prints. When the CFO asks "who should we chase first?" or "what is our overdue exposure in USD across three companies?", the native reports can't answer — the aging thresholds don't match your credit terms, there is no priority ranking, and multi-currency balances are shown at posting rate with no consolidated view. Teams end up exporting to spreadsheets every week, which is exactly where the numbers stop being trustworthy.
Configurable aging buckets defined in a settings model (any number of ranges, custom day boundaries, per-report profiles) instead of Odoo's hard-coded 30/60/90/120
Reads open items directly from `account.move.line` filtered on `account_type` receivable/payable, `parent_state='posted'` and `reconciled=false` for ledger-accurate residuals
Aging computed from `date_maturity` (fallback `invoice_date_due`) against a user-selectable as-of date, not just today
Uses `amount_residual` / `amount_residual_currency` so partially-paid invoices show correct remaining exposure, never the gross amount
Stored collection-priority score (`@api.depends` compute) weighting overdue value, days-past-due, credit-limit proximity and payment behaviour into one rankable figure
Multi-currency aged balances with per-item currency amounts plus company-currency consolidation via `res.currency._convert()` at a chosen rate date
Aged Receivable / Payable Analytics is a build-to-order Odoo module that turns aging into an operational tool instead of a month-end artifact. We add a dedicated model (for example ecosire.aged.analytics.line) that reads directly from account.move.line — filtered on account_id.account_type in asset_receivable / liability_payable, parent_state = 'posted' and reconciled = false — and computes the residual per invoice using amount_residual and amount_residual_currency. Aging days are derived from date_maturity (falling back to invoice_date_due) against a configurable "as-of" date, and each open item is dropped into buckets you define in a settings model rather than the hard-coded native ranges. Compute fields use @api.depends so drill-downs stay live, and the whole set is exposed through Odoo pivot, graph, list and OWL dashboard views.
On top of the raw aging we build the two things native Odoo lacks. First, a collection-priority score: a stored compute that weights overdue amount, days-past-due, days-to-credit-limit and payment history into a single rankable figure, so the collections list opens already sorted by who to call today. Second, real multi-currency handling — every open item carries its currency amount and a company-currency conversion via res.currency._convert() at your chosen rate date, so a multi-company group sees one consolidated exposure number and each entity keeps its own currency detail. Overdue-trend charts snapshot bucket totals over time (via a small history model populated by a scheduled ir.cron automated action) so you can see whether your DSO is drifting week over week. Everything is secured with ir.model.access.csv plus record rules that respect res.company multi-company boundaries, and the same data is reachable over XML-RPC/JSON-RPC for BI tools or a treasury portal.
Because it is build-to-order, nothing here is a generic download. We start from your real chart of accounts, credit terms and currency setup, confirm the bucket definitions and scoring weights that match how your business actually chases money, and only then build. You get the module scoped to your Odoo edition and version — it works on Community and Enterprise, and we adapt to the accounting differences (Enterprise's dynamic financial reports vs Community's list-based reports) so the analytics sit naturally alongside what you already run. Typical delivery is 2–4 weeks from confirmed scope, validated on a staging copy of your database before it ever touches production.
Needs a single prioritized worklist each morning — who to chase first by overdue value and days-past-due — with one-click drill-down to the exact open invoices, not a fixed-bucket PDF re-exported to Excel every week.
Wants consolidated overdue exposure across companies and currencies, DSO trend over time, and confidence the aging thresholds match the group's real credit terms rather than Odoo's default 30/60/90 grid.
Manages the payables side — aged vendor balances by custom buckets to protect early-payment discounts and cash-flow timing, with multi-currency visibility on what is due when.
Pulls the aged AR/AP dataset over XML-RPC/JSON-RPC into Power BI or a cash-flow model, needing a stable, secured API source rather than manual report exports.
قم بشراء الترخيص من موقع ecosire.com وقم بتنزيل وحدة Aged Receivable / Payable Analytics ZIP من لوحة تحكم حسابك.
قم باستخراج ملف ZIP إلى مجلد إضافات Odoo المخصصة على الخادم (أو تحميله عبر التطبيقات > التثبيت من ملف على Odoo.sh / runbot).
قم بتنشيط وضع المطور، وافتح التطبيقات، وانقر فوق تحديث قائمة التطبيقات، وابحث عن Aged Receivable / Payable Analytics، ثم اضغط على تثبيت.
افتح القائمة الجديدة، والصق مفتاح ترخيص ECOSIRE الخاص بك، وقم بتوصيل أي بيانات اعتماد خارجية (Shopify، وAmazon، وStripe، وما إلى ذلك)، ثم احفظها.
قم بتشغيل اختبار الاتصال المدمج، وقم بمزامنة أول 10 سجلات لديك، وقم بجدولة عملية cron المتكررة. اتصل بالدعم إذا فشل أي شيء.
| المعيار | ECOSIRE | بناء مخصص | منافس | أودو الأصلي |
|---|---|---|---|---|
| Aging buckets | Fully configurable, any ranges, saved per report profile | Whatever you build, but from scratch each time | Usually a few preset bucket options | |
| Collection priority | Stored weighted score tuned to your policy | Possible but you design and maintain the logic | Rarely included; simple sorts at best | |
| Multi-currency | Per-item currency plus consolidated company-currency view | Depends on effort invested | Often single-currency or posting-rate only | |
| Drill-down | Bucket → partner → individual open invoices, live | Build the views yourself | Partial, often report-only | |
| Trend charts | Scheduled snapshots power DSO/overdue trend over time | Requires building a history model | Seldom offered | |
| API access | Models exposed via XML-RPC/JSON-RPC, secured | You expose and secure it | Varies, often none | |
| Fit to your business | Scoped from your CoA, terms and currencies | Fully bespoke but full cost and risk on you | Generic, take it as shipped | |
| Support & ownership | Support window + full git repo handover | In-house maintenance burden | Vendor SLA, no source control |
This is build-to-order, so it is not an instant download. Typical delivery is 2–4 weeks from confirmed scope — that clock starts once we've agreed your bucket definitions, scoring weights, currency setup and target Odoo version. We validate everything on a staging copy of your database before production.
Both. The analytics read from standard accounting models (`account.move.line`, `res.currency`) that exist in Community and Enterprise. We adapt to each edition's reporting differences — for example Enterprise's dynamic financial report engine versus Community's list-based reports — and target Odoo 17.0, 18.0 or 19.0 as you require.
The native report uses fixed 30/60/90/120 buckets, has no collection-priority ranking, no consolidated multi-currency exposure and produces a static PDF. We add configurable buckets, a stored priority score, live drill-down, multi-company/currency consolidation and overdue-trend charts driven by a scheduled snapshot job.
Yes. Record rules scope data per `res.company`, and a group-level consolidated view aggregates across entities. Each open item keeps its own currency amount, and company-currency figures are converted with `res.currency._convert()` at a rate date you choose, so shared credit teams see one exposure number without losing detail.
Every build includes a post-go-live support window for bug fixes and configuration tweaks. You also receive the full git repository so your own team can maintain it. Beyond the included window, we offer ongoing support and version-migration (for example moving from Odoo 17 to 18/19) as a separate engagement.
Yes. The module's models are exposed over Odoo's XML-RPC/JSON-RPC API and secured by `ir.model.access.csv` and record rules, so BI tools, a treasury system or a customer portal can pull the same aged AR/AP figures without manual exports.
That's exactly what the scoping call is for. The score is a weighted compute over overdue amount, days-past-due, credit-limit proximity and payment history — we tune those weights to your collections policy so the list opens sorted the way your controllers already think about risk.
Interactive aged-balance dashboards for Odoo with configurable buckets, customer/vendor drill-down, multi-currency views and collection-priority scoring. Built to order, installed and supported by ECOSIRE on Odoo 17, 18 and 19.