# Subscription Billing All in One with Card Charging

> A subscription with a saved payment method is charged the moment its invoice is posted, and charged again on the dunning rung that says so. Installed by itself alongside Subscription Billing and Odoo's invoice payments.

- **What it is:** A subscription with a saved payment method is charged the moment its invoice is posted, and charged again on the dunning rung that says so. Installed by itself alongside Subscription Billing and Odoo's invoice payments.
- **For:** Accounting/Accounting
- **Odoo versions:** 16.0, 17.0, 18.0, 19.0, 20.0 - Community and Enterprise
- **Runs on:** Odoo.sh or Odoo you host yourself - not Odoo Online, which accepts no third-party apps
- **Price:** 198 EUR, one-time, on the Odoo Apps Store
- **Technical name:** bambooforge_subscription_payment
- **Not for:** Charge the invoice or credit note of a plan change. They are not billed periods.; Refund. A credit note is not paid back to the card.; Ask the customer. No card is saved here: the customer saves one while paying on the portal.
- **Manual:** https://docs.bambooforge.dev/bambooforge_subscription_payment/
- **Live demo:** https://demo20.bambooforge.dev/odoo
- **Store page:** https://apps.odoo.com/apps/modules/20.0/bambooforge_subscription_payment
- **Manual last updated:** 2026-11-12

---
# Subscription Billing All in One with Card Charging

A subscription bills the same customer every period; this add-on charges the card that customer
saved. Pick one of the customer's saved payment methods on the subscription, and each invoice the
billing posts is charged with it through your payment provider. A refused charge is written on the
subscription, and the dunning rung that charges again tries once more. It installs by itself with
Subscription Billing on Odoo 20.

This page is the complete manual: what is charged, when, by whom, and what a refusal does.

## Overview

**For whom.** A business that bills subscriptions and has its customers' cards on file with a
payment provider. It needs Subscription Billing and Odoo's Invoice Online Payment, on Odoo 20.

### What it does

- **A saved card on the subscription.** *Charge automatically with* takes one of the customer's
  saved payment methods: the customer's own or one of a contact of the same company.
- **Charged when the billing posts.** With *Post automatically* on, each invoice the billing makes
  and posts is charged at once for what is left to pay on it: one payment transaction with the
  token, sent to the provider, linked to the invoice and to the subscription.
- **Odoo reconciles.** When the provider confirms, Odoo's own payment flow pays the invoice.
- **A note either way.** The amount charged, or the provider's refusal, is written on the
  subscription.
- **Charged again by the dunning.** The rung *Charge the stored payment method again* charges every
  posted invoice of the subscription that is still unpaid.
- **Charges.** A button on the subscription lists its transactions.
- **Posted by hand, charged too.** An invoice of a billed period posted by a person is charged when
  it is posted.

### What it does not do

- **Charge the invoice or credit note of a plan change.** They are not billed periods.
- **Refund.** A credit note is not paid back to the card.
- **Ask the customer.** No card is saved here: the customer saves one while paying on the portal.

### What it needs

- **Subscription Billing** and **Invoice Online Payment** (`account_payment`, installed with
  Invoicing), on Odoo 20, Community or Enterprise.
- A payment provider that saves cards, enabled (or in test mode): Odoo ships them disabled.
- A card the customer saved with that provider.

## Concepts

**Saved card.** A payment method the customer saved with a provider (a token in Odoo).

**Charge.** One payment transaction for one invoice, sent to the provider.

**Charge again.** The dunning rung that charges every posted unpaid invoice of the subscription.

## Install and first run

1. Install **Subscription Billing**: with Invoicing, Odoo has Invoice Online Payment, and this
   add-on installs by itself when its folder is in the addons path.
   
   Expected: the subscription form has *Charge automatically with* under *Post automatically*.
2. Enable a payment provider that saves cards, and let the customer save a card through it.
   
   Expected: the card is offered in *Charge automatically with* on that customer's subscriptions.
3. Pick the card, tick *Post automatically*, and press **Bill what is due**.
   
   Expected: the invoice is posted, a note says what was charged or why it failed, and the
   **Charges** button counts one.

### Uninstalling

Uninstalling removes the field on the subscription and the link from each transaction to its
subscription. Transactions and payments stay.

## Flows

Two things the add-on does for you.

### Charge a subscription automatically

1. Open a subscription and choose the card in *Charge automatically with*.
2. Tick *Post automatically*.
3. Each period the billing makes the invoice, posts it, and charges what is left to pay on it.
4. **Charges** lists the transactions; the chatter says what each did.

### When a charge is refused

1. The note says *Charging ... failed:* with the provider's words. The invoice stays open.
2. The dunning job counts the invoice overdue from its due date.
3. On the rung that charges again, every posted unpaid invoice of the subscription is charged once
   more; the reminder goes out when no charge went through.
4. Replace the card on the subscription if the customer saved a new one.

## How it works

### When a charge is made

- **When.** Right after the billing posts an invoice it made and records the billed period, and on
  the dunning rung that charges again. Never on a draft. Also when a person posts an invoice of a
  billed period.
- **How much.** What is left to pay on the invoice, in its currency.
- **Skipped.** No card, an archived card, or an invoice already paid or in payment, or one with a
  charge done, authorised or waiting.
- **One transaction per invoice per attempt**, operation *offline*, with the card and the invoice.
- **The note.** Done, authorised or pending: the amount charged. Anything else: *failed* with the
  state or the provider's message.
- **Odoo 20.** The provider's answer is recorded and processed by Odoo's payment job a moment later.
  A charge still waiting for it is noted as sent.

### Who reads and writes what

- Whoever may change the subscription (Invoicing users) chooses the card; Odoo lets Invoicing users
  read every saved card.
- A card of another customer is refused. So is a card of another company's provider.
- The transaction is made with full rights after Odoo's own access to the subscription and the
  invoice was checked; the note is written as the user who billed, or OdooBot for the jobs.

### What leans on Odoo's settings

- **Payment providers** are disabled by default on 16.0 to 20.0: enable one, or put it in test mode.
- **Post automatically** on the subscription is off by default: until it is ticked, nothing is
  charged at posting.
- **The dunning rungs** installed with Subscription Billing charge again at 10 days overdue.

### How we make sure it works

Before every release, **11 automated checks** run against this app on Odoo 16, 17, 18, 19 and 20.
Among them:

- A refused charge is a note not silence.
- A draft invoice is not charged.
- Somebody elses card is refused.
- A posted invoice is charged with the token.
- Retry charges the open invoices again.

The complete list is in the source you receive.

## For managers

The add-on has no analysis of its own: the **Charges** button on a subscription lists its
transactions. Odoo 20 has no menu for the transactions themselves.

No document prints from this add-on.

## Reference

The complete reference of this add-on is generated from the code on every release and published
with this manual at https://docs.bambooforge.dev/bambooforge_subscription_payment/ under
*Reference*.

## Troubleshooting and FAQ

- *That payment method belongs to another customer.* The card's customer is not the subscription's.
- *That payment method's provider belongs to another company.*
- *Charging ... failed: ...* (chatter): the provider's answer or the transaction's state. Check the
  card with the provider, then wait for the dunning or bill again after replacing it.
- No card offered in *Charge automatically with*: the customer has saved none, or the provider is
  disabled.

### Questions people ask

**Is the card charged when I post an invoice myself?** Yes, when the invoice belongs to a billed
period.

**Can a customer be charged twice?** Not by two runs racing. A charge in progress is not repeated by
the dunning.

**Who is the money paid to?** The provider of the card, to its account.

### Support

Write to [support@bambooforge.dev](mailto:support@bambooforge.dev) with your Odoo series, your payment provider and what the note
said.

## Changelog

### 20.0.1.0.1

- The subscription's link on a transaction has a help text; the help of *Charge automatically with*
  says which invoices are charged.
- This manual, the add-on's first.

### 20.0.1.0.0

- A subscription with a saved payment method is charged when the billing posts its invoice, and
  charged again on the dunning rung that says so.


## Reference

Generated from the module's own code (version 20.0.1.0.1, series 20.0) on 2026-11-12; every menu, field, setting, scheduled action, group, rule, report and endpoint below is read from the files, not written by hand.

### Models

#### bf.subscription (extends bambooforge\_subscription's bf.subscription)

| Field | Technical name | Type | Help | Flags |
|---|---|---|---|---|
| Charge automatically with | `payment_token_id` | Many2one to payment.token | A payment method the customer saved with a provider. An invoice the billing posts by itself (Post automatically) is charged with it at once; an invoice of a billed period posted by hand is charged when it is posted. |   |
| Charge Count | `charge_count` | Integer |   | computed |

#### account.move (extends Odoo's account.move)

Adds no fields.

#### payment.transaction (extends Odoo's payment.transaction)

| Field | Technical name | Type | Help | Flags |
|---|---|---|---|---|
| Subscription | `bf_subscription_id` | Many2one to bf.subscription | The subscription whose invoice this charge was made for. |   |
