Skip to main content
GoCardless

GoCardless invoice in Odoo: from collection to a posted payout

With GoCardless, Odoo keeps your invoices and GoCardless collects them. Collections are Odoo payment transactions, and each bank payout becomes a single entry, with the fees separated, when an accountant clicks Post to accounting.

FlexigoTech · Editor in charge: Víctor Gómez · Updated 17 November 2026

Key facts

Versions
Odoo 17, 18, 19 and 20
Checked
in the connector's source code, version 20.0 · against the sources linked at the end
Reading time
4 min

Invoices in Odoo, collections in GoCardless

If you use GoCardless, or are about to, the split the connector proposes is simple: Odoo keeps your invoices and GoCardless collects them. The connector extends Odoo's payment transactions, so GoCardless collections appear in the same list as any other payment transaction.

List of payment transactions in Odoo with demonstration data: members' fees collected with the SEPA Direct Debit method and the GoCardless provider, with their invoice reference, customer and amount
GoCardless collections in the payment transactions list (invented gym, simulated API, English interface, demonstration data).

That leaves the other side: the money reaches the bank in payouts. The connector separates collections, fees and, when there are any, refunds and chargebacks within each payout. To take a payout into the accounts it adds a button, Post to accounting, on the payout form.

GoCardless payout form in Odoo with demonstration data: arrival date, paid status, net paid out, fees deducted, items total, variance at zero, breakdown by collection with its fee and the Post to accounting button
A payout with demonstration data (invented gym, test mode, English interface), with the variance at zero and the button to post it.
How to stop copy-pasting between apps (Odoo)
Video: How to stop copy-pasting between apps (Odoo)

When the button shows and what happens when you click it

The module keeps this step manual on purpose: posting to the general ledger is the merchant's accountant's call, not something a connector should do behind their back. What follows is the behaviour of the Odoo 20 code; the condition that hides the button is the same in Odoo 17, 18, 19 and 20.

SituationPost to accounting buttonResult
The payout is paid, balances and has no entryShownBuilds an entry from the breakdown, posts it and stores it in the Journal Entry field. Then it tries to reconcile the collections.
Journal Entry already has an entryHiddenThe view hides it as soon as the field has a value.
The payout's Status is not paidHiddenThe view hides it until the payout is paid.
The payout does not balance (Is Balanced field)HiddenThe view hides it while it does not balance.
Someone who is not an accountant clicks itShown if the conditions above are metOnly accountants can post GoCardless payouts. appears and no entry is created.

The reading is straightforward: the button is only offered when there is something correct to post, and whoever clicks it has to be an accountant. When the button is missing, the cause is one of those three fields.

What entry it builds

The entry is built from the payout's breakdown, not from the net figure. The code explains why: crediting net plus fees as if it were all collections looks balanced, but it goes wrong as soon as a payout contains a refund or a chargeback, because the clearing account keeps a permanent residual and the refund never reaches the books.

Entry lineWhen it appearsSide and account
GoCardless payout …In every payout entryDebit, bank account, for the amount paid out
GoCardless feesIf net fees are positiveDebit, fees account
GoCardless fees refundedIf net fees are negativeCredit, fees account
Refunds and chargebacksIf the payout has refunds or chargebacksDebit, clearing account
GoCardless collections settledIn every payout entryCredit, clearing account, for the collections

Two details in the code prevent mismatches:

  • The module classifies items by type, not by sign. GoCardless returns its fees as positive fee items when a payment fails or is charged back; counting them as collections would overstate fee expense and leave a credit on the clearing account that no payment could ever reconcile.
  • If the payout arrives in a currency other than the company's, each line is converted to the company currency at the rate of the arrival date (or today's date if there is no arrival date). Because each line is rounded on its own, the collections line absorbs any difference of a cent so that Odoo accepts the entry; the original foreign-currency amounts stay exact.

The entry's reference is GoCardless payout … followed by the GoCardless identifier.

After posting: reconciling the collections

Once posted, the module tries to reconcile the payments Odoo had booked for the collections in that payout. Each payment debits its outstanding receipts account and the payout credits the clearing account for the same money. When they are the same account, which is the default, matching them is what moves the payment from in payment to paid.

If something does not fit, the module does not guess:

  • If a payment sits on an account other than the clearing account, the module logs it on the server and leaves it for manual reconciliation.
  • If the clearing account does not allow reconciliation, it logs that too and reconciles nothing.
  • Only the credit for the collections is reconciled. The debit for refunds and chargebacks is left out, because it would match against the payout's own credit and leave payments open.

How FlexigoTech can help

If you do not use Odoo yet, the hard part is not the button: it is having invoices, collections and accounting in one place. FlexigoTech implements Odoo 17, 18, 19 and 20 and builds connectors and bespoke integrations; you can start with the implementation and add the connector afterwards. The Odoo Apps listing and the module page show the GoCardless connector.

Keep reading

Checked in the connector's source code (version 20.0) and the linked sources

Sources

  • Module source code: flexigo_payment_gocardless 20.0 (6fe1a716): static/description/index.html
  • Module source code: flexigo_payment_gocardless 20.0 (6fe1a716): models/payment_transaction.py
  • Module source code: flexigo_payment_gocardless 20.0 (6fe1a716): models/gocardless_payout.py
  • Module source code: flexigo_payment_gocardless 20.0 (6fe1a716): views/gocardless_payout_views.xml
  • flexigotech.com/en/services.html