Teams selling online typically process thousands of card charges, refunds, disputes, and per-transaction fees through a payment processor, then receive periodic net payouts to their bank. Reconciling those payouts by hand is where finance loses days each month: a single bank deposit can represent hundreds of gross charges minus refunds minus processing fees minus platform commissions, and Odoo's native bank reconciliation only sees the net line that hit the account. Out of the box, Odoo core has no concept of the underlying gross-to-net breakdown, so accountants export CSVs from the processor dashboard and match them manually, or worse, book fees as a lump journal entry that never ties back to individual invoices.

This is a build-to-order module that ECOSIRE designs, builds, installs, and supports for your specific Odoo instance — it is not an existing apps.odoo.com download you install today. We build a dedicated set of models (models.Model) to store the processor's balance transactions, payouts, and fee lines, each linked to the originating account.move invoice or sale.order where a match exists. A scheduled automated action calls the processor's REST API on a configurable interval to pull new transactions and payout events; incoming records are normalized, deduplicated on the external transaction id, and staged for review. Fees are posted to a dedicated expense account you nominate during scoping, so your P&L shows true processing cost instead of a netted revenue figure. Currency conversion, refund and chargeback handling, and multi-account routing are all modeled explicitly rather than collapsed into one entry.

Technically, the module ships with ir.model.access.csv rules plus record rules so only accounting roles see raw transaction data, OWL/XML views for a payout workspace and a fee dashboard, and a QWeb report that reconciles each payout down to its constituent charges and fees for audit. A reconciliation engine proposes matches between processor payouts and imported bank statement lines using amount, date, and reference heuristics, leaving a clean one-click confirmation for your accountant. All processor credentials are stored using Odoo's configuration parameters and the whole sync runs server-side through the @api.depends compute chain and cron, so nothing depends on a user having a browser open. We support Odoo 17.0, 18.0, and 19.0, and we account for Community vs Enterprise differences (for example, Enterprise's bank-sync and follow-up features) so the module complements rather than fights whatever edition you run.

Delivery is build-to-order: it starts with a scoping call to confirm your processor account structure, chart-of-accounts mapping, currencies, and edge cases, after which we issue a fixed quotation and a written scope. Typical delivery is one working week from confirmed scope, depending on complexity and your team's availability for UAT. You receive the full installable source, a git repository, technical and user documentation, a training session, and a post-go-live support window. Pricing starts from $999 (indicative, single-company base scope); multi-company consolidation, additional processor accounts or currencies, historical data migration volume, and bespoke fee-routing rules increase the quoted scope. The firm price is fixed after the scoping call — never before.