A build-to-order Odoo module that automatically imports your online card-processor payouts, transactions, and processing fees into Odoo accounting, then matches them against invoices and bank statements. ECOSIRE scopes, builds, installs, and supports it for your instance. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo module that automatically imports your online card-processor payouts, transactions, and processing fees into Odoo accounting, then matches them against invoices and bank statements. ECOSIRE scopes, builds, installs, and supports it for your instance.
Sem pagamento agora. Isto envia um pedido de orçamento à nossa equipe — responderemos por e-mail com preços e próximos passos.
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.
Scheduled `ir.cron` automated action pulls new balance transactions and payout events from the processor REST API on a configurable interval
Dedicated Odoo models store payouts, balance transactions, and fee lines with a one-to-many link from each payout to its constituent charges
Idempotent import keyed on the external transaction id so re-runs and API retries never create duplicate records
Per-transaction processing fees posted to a nominated expense account so the P&L shows true gross revenue and real processing cost separately
Automatic matching of imported payouts against `account.bank.statement.line` records using amount, date, and reference heuristics
Explicit modeling of refunds, partial refunds, chargebacks, and disputes as distinct record types rather than netted adjustments
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 2 to 4 weeks 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 $249 (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.
Runs monthly close for an online store processing high card volume and needs each net payout to reconcile automatically down to gross charges and fees, instead of exporting CSVs and matching by hand.
Bills recurring card payments and wants processing fees booked to a real expense account and each charge tied back to its invoice, so revenue and cost of payments are reported honestly.
Settles in several currencies and needs presentment vs settlement amounts, FX differences, and per-account routing modeled explicitly rather than collapsed into one bank line.
Owns reconciliation across clients and wants a repeatable, auditable payout-to-statement workflow with QWeb reports and role-scoped access rather than ad-hoc spreadsheets.
Compre a licença em ecosire.com e baixe o ZIP do módulo Stripe Statements Reconciliation for Odoo no painel da sua conta.
Extraia o ZIP em sua pasta de complementos personalizados do Odoo no servidor (ou faça upload via Aplicativos > Instalar do arquivo em Odoo.sh/runbot).
Ative o modo de desenvolvedor, abra Aplicativos, clique em Atualizar lista de aplicativos, procure por Stripe Statements Reconciliation for Odoo e pressione Instalar.
Abra o novo menu, cole sua chave de licença ECOSIRE, conecte quaisquer credenciais externas (Shopify, Amazon, Stripe, etc.) e salve.
Execute o teste de conexão integrado, sincronize seus primeiros 10 registros e agende o cron recorrente. Entre em contato com o suporte se algo falhar.
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| How you get it | Scoped, built, and installed for your instance | Built from scratch by your own developers | Generic download, install immediately | |
| Payout-to-charge breakdown | Full gross-to-net down to each charge and fee | Whatever you build | Usually summary-level only | |
| Fee accounting | Booked to a nominated expense account per rule | Depends on your implementation | Often a single lump entry | |
| Fit to your chart of accounts | Mapped to your accounts during scoping | Fully yours to define | Fixed assumptions, limited config | |
| Refunds and chargebacks | Modeled as distinct record types | If you build it | Often netted or ignored | |
| Version and edition coverage | Built for your 17/18/19, Community or Enterprise | Whatever you target | Varies; may lag releases | |
| Support and ownership | Support window plus full git repo handover | You own and maintain everything | Vendor support varies, code often closed | |
| Cost model | From $249 indicative, fixed quote after scoping | Higher dev cost and time | Low upfront, limited fit |
No. This is a build-to-order module that ECOSIRE scopes, builds, installs, and supports for your specific Odoo instance. It is not an existing apps.odoo.com download. We start with a scoping call, agree the exact behavior, then build it for you.
Typical delivery is 2 to 4 weeks from confirmed scope. The exact timeline depends on complexity — number of processor accounts, currencies, historical data to migrate, and your team's availability for UAT. We commit to a date in writing once scope is fixed.
Pricing starts from $249 (indicative, single-company base scope). It is not a firm price. After a short scoping call we send a fixed written quotation. Drivers like multi-company consolidation, additional processor accounts or currencies, historical data migration volume, and bespoke fee-routing rules increase the quoted scope.
We build for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. During scoping we account for edition differences — for example, Enterprise's native bank-sync and follow-up features — so the module complements your setup instead of conflicting with it.
Every build includes a post-go-live support window for defect fixes and configuration adjustments. You also receive the full git repository, so your own developers can maintain it. Version upgrades (for example migrating the module to a newer Odoo release) can be quoted separately as a scoped engagement.
Fees are posted to a dedicated expense account you nominate, so your P&L shows true gross revenue and real processing cost separately rather than a netted figure. Refunds, partial refunds, and chargebacks are modeled as distinct record types and reconciled against the correct payouts.
API credentials are stored via Odoo configuration parameters, never hard-coded, and the sync runs server-side on a scheduled cron. Raw transaction data is restricted to accounting roles using `ir.model.access.csv` and record rules, so operational users never see it.

A build-to-order 2Checkout (Verifone) payment integration for ERPNext, giving global digital-goods sellers card acceptance, 45+ local payment methods, multi-currency checkout, and reconciled invoices. ECOSIRE scopes, builds, installs, and supports it on your ERPNext v15/v16 instance.

A build-to-order 2Checkout / Verifone payment gateway for Magento 2 and Adobe Commerce: localized checkout in 12 languages, iDEAL, Giropay and regional methods, multi-currency global selling, subscription billing and tax/invoicing automation — engineered, installed and supported by ECOSIRE.

A build-to-order ERPNext application for anonymous 360-degree reviews — configurable peer, manager, report and self rater groups, weighted competency scoring, and aggregated gap-analysis and heatmap reports. ECOSIRE scopes, builds, installs and supports it on your Frappe/ERPNext v15/v16 instance.
A build-to-order Odoo module that automatically imports your online card-processor payouts, transactions, and processing fees into Odoo accounting, then matches them against invoices and bank statements. ECOSIRE scopes, builds, installs, and supports it for your instance.