Skip to Content

Linking Stripe to Odoo accounting without a paid connector

A small scheduled script replaced a paid aggregation service, then gave way to an open source OCA module.
November 16, 2026 by
Linking Stripe to Odoo accounting without a paid connector
Federico Solutions, Myrko Federico

Linking Stripe to Odoo accounting without a paid connector

Field: accounting, Odoo ERP, online payments

Period: from May to September 2026, then handed over to an open source module

Client: internal project, my own companies (Lab 77, R&D)

For accounting purposes, Stripe is not a payment tool: it is a bank. Money comes in, fees go out, transfers leave for the bank account. In May 2026, I replaced the paid service that brought these transactions into Odoo with a small scheduled script. A few months later, an open source module replaced it in turn. Here is how I designed it from an accounting point of view, and what I take away from it.

Context

My companies collect part of their sales through Stripe. In spring 2026, my accounts ran on Odoo Online. For Stripe transactions to appear in the statements and be reconciled with invoices, you had to go through a paid third-party bank aggregation service. The article on Odoo and the MCP protocol sums up this script in one paragraph; here I come back to the why and to the accounting choices.

Problem

  • A subscription for very little: the service was billed per currency and per month. With several currencies, the bill multiplied.
  • Gross or net: Stripe deducts its fees at source. Record the wrong amount, and the balance will never match.
  • Duplicates: an import rerun by mistake, or a period that overlaps the previous one, must not record the same payment twice.
  • The audit trail: you must be able to show what was imported, in a format any accounting software can read.
  • Caution: a program that deals with money must not be able to move any.

The approach

1. Treat Stripe as a bank

In Odoo, Stripe has its own bank journal, like any other account. Properly kept, its balance returns towards zero with each payout: a balance that drifts signals an error.

2. Record net amounts, keep fees in sight

Each line carries the amount actually credited to the Stripe account, that is, net of fees. That is what the payout to the bank adds up. The fees do not vanish, though: their amount is noted on the line, so that the gap between the invoice and the amount received can be booked as bank charges at reconciliation time. Importing the gross amount and then the fees separately would have complicated reconciliation.

3. A unique reference per transaction

Stripe gives each transaction an identifier. The script derived a unique reference from it for each statement line, and checked that it did not already exist before writing; Odoo, for its part, refuses two lines carrying the same import reference. The script also remembered the date of the last imported transaction, so as to ask Stripe only for what came next. It could therefore be rerun without fear.

4. Archive in the standard banking format

On each run, the script also produced, for each currency, a statement in camt.053 format: the account statement of the ISO 20022 standard, the one banks use for their electronic statements. Since the script could not go through Odoo Online's file import, it wrote the lines directly, and the standard file served as an archive.

5. Read-only access, once a month

Stripe lets you create restricted access keys. The script's key could only read: no refunds, no transfers, no changes of any kind. A scheduled task ran it once a month.

Result

The first import took place on 7 May 2026, and the subscription no longer had any reason to exist. Stripe transactions arrived in Odoo every month like those of a bank, ready to be reconciled. This is also the basis on which my AI assistant helps me keep my accounts.

At the end of August 2026, I migrated to Odoo Community, installed on my own server. The Odoo Community Association (OCA) publishes, in its repository dedicated to bank statement imports, a Stripe module that queries Stripe and creates the statements on its own. I installed it in September 2026: the script handed over. One difference worth knowing: the module only keeps transactions in the journal's currency; several currencies require one journal per currency.

What I take away from it

  • For accounting, a payment provider is a bank. Same reflexes, and the balance returning towards zero serves as a check.
  • Net is the truth of the account. Fees are read on the line and booked as charges at reconciliation, without extra lines.
  • Duplicate protection is designed from the start. A unique reference taken from the source makes the import safe to replay.
  • Archive in an open format. A camt.053 statement outlives both the tool that produced it and the one that reads it.
  • As few rights as possible. Access that can only read reduces the worst case to an information leak.
  • A home-made script is a bridge, not a destination. It bought a few months without a subscription. Keeping it once the module arrived would have meant maintaining alone what others maintain together.

Going further

Do you collect payments through Stripe or another payment provider, and do your statements still arrive by hand, or through one more subscription? I connect these flows to your Odoo accounts, with open source modules where they exist. See business applications, or book a 20-minute discovery call.

Sources

Tags: Odoo, Stripe, accounting, bank statement, camt.053, ISO 20022, OCA, open source software

Several AI agents working together without losing track
The rules that let several AI agents hand work to one another without anything getting lost.