# Customer Statement All in One with Credit Hold

> A dunning level marked 'put the customer on credit hold' puts the customer on an automatic credit hold when it is reached; the hold is lifted when the level clears. Installed by itself alongside Customer Statement and Credit Limit & Credit Hold.

- **What it is:** A dunning level marked 'put the customer on credit hold' puts the customer on an automatic credit hold when it is reached; the hold is lifted when the level clears. Installed by itself alongside Customer Statement and Credit Limit & Credit Hold.
- **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:** 227 EUR, one-time, on the Odoo Apps Store
- **Technical name:** bambooforge_customer_statement_credit
- **Not for:** Add a screen. It reacts to the dunning step; the box is on the dunning level, the hold on the customer.
- **Manual:** https://docs.bambooforge.dev/bambooforge_customer_statement_credit/
- **Live demo:** https://demo20.bambooforge.dev/odoo
- **Store page:** https://apps.odoo.com/apps/modules/20.0/bambooforge_customer_statement_credit
- **Manual last updated:** 2026-11-12

---
# Customer Statement All in One with Credit Hold

The bridge between the dunning ladder of Customer Statement of Account and the credit hold of Credit
Limit & Credit Hold, on Odoo 20: a dunning level marked *Put the customer on credit hold* puts the
customer on an automatic credit hold when the customer reaches it. It installs by itself when both
apps are installed.

This page is the complete manual of that bridge.

## Overview

**For whom.** A credit controller who runs the dunning ladder of Customer Statement of Account and
the credit hold of Credit Limit & Credit Hold, and wants the second to follow the first.

**What for.** A customer who reaches the rung you choose cannot have a new quotation confirmed,
without anybody setting the hold by hand.

### What it does

- **A hold when the level is reached.** When the dunning step moves a customer onto a level marked
  *Put the customer on credit hold*, the customer gets an automatic credit hold and a note on its
  chatter: *Credit hold: dunning level <level> reached.*
- **Released when the level clears.** When a run finds nothing overdue and clears the level, an
  automatic hold that a holding level set is lifted, with the note *Credit hold lifted: the overdue
  balance is settled.*
- **A manager's decision stands.** A customer with a *Manual Credit Decision* (Forced Hold or Forced
  Release) is left as it is, and a customer already on hold is not held a second time.
- **Held while something is overdue.** Credit Limit's daily job leaves a dunning hold in place while
  the customer has anything overdue, and lifts it the day nothing is.

### What it does not do

- **Add a screen.** It reacts to the dunning step; the box is on the dunning level, the hold on the
  customer.

### What it needs

- Customer Statement of Account & Aging Report and Credit Limit & Credit Hold for Sales Orders, on
  Odoo 20, Community or Enterprise.

## Concepts

**Holding level.** A dunning level with *Put the customer on credit hold* ticked.

**Automatic hold.** A credit hold set by a program, the daily credit job or this bridge, which a
program may lift again.

**Manual credit decision.** A credit manager's Forced Hold or Forced Release, which no program
overrides.

## Install and first run

1. Install both apps: this bridge installs by itself.
   
   Expected: *Apps* shows **Customer Statement All in One with Credit Hold** installed.
2. Open *Invoicing > Configuration > Dunning Levels*, open *Second notice* and tick **Put the
   customer on credit hold**.
   
   Expected: the list of levels shows the box ticked on that level.
3. Let a schedule run, or use *Invoicing > Customers > Send Dunning Now*, for a customer whose
   oldest overdue invoice is 30 days or more past due.
   
   Expected: the customer is on credit hold, with the note on its chatter, and a new quotation for
   it shows *Credit Blocked*.

### Uninstalling

Uninstalling stops the bridge. Holds it set stay, as automatic holds that Credit Limit's daily job
may lift.

## Flows

What happens to a customer.

### A customer reaches a holding level

1. A schedule's run or *Send Dunning Now* finds the customer's oldest overdue receivable old enough
   for a level marked *Put the customer on credit hold*.
2. The customer moves onto that level: the bridge sets *Credit Hold* and marks it automatic, unless
   a manager decided otherwise or the customer is on hold already.
3. A note on the customer says which level held it.
4. Quotations made out to the customer company show *Credit Blocked* until the hold is lifted or a
   credit manager approves them.

### The customer pays

1. The customer pays what was overdue.
2. Credit Limit's next daily run lifts the automatic hold: nothing is overdue.
3. A manager's *Forced Hold* stays whatever is paid.

## How it works

### When the hold moves

- **The trigger** is the dunning step of Customer Statement of Account, which moves the level. The
  hold is set when the new level holds and no manual decision is set and the customer is not on
  hold; it is lifted when the level is cleared, the previous level held, the hold is automatic and
  no manual decision is set.
- **The company.** The hold is written in the company of the schedule being run.
- **Credit Limit's daily job** (*Credit: Apply Overdue Holds*) decides automatic holds from its own
  overdue rules: it leaves a dunning hold in place while the customer has something overdue.

### Who reads and writes what

The hold and the notes are written with the app's rights, past the guard Credit Limit puts on the
hold fields: that guard is for people, and the dunning step decides here. Only the dunning step
moves the hold: writing the customer's level does not.

### How we make sure it works

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

- A level without the flag holds nothing.
- A managers hold is not lifted by a payment.
- Credit job keeps hold.
- Level write keeps hold.
- The rung holds and the payment releases.

The complete list is in the source you receive.

## For managers

This bridge has no analysis of its own. The customers on hold are under *Sales > Reporting > Credit
Holds*, and each dunning level shows how many customers sit on it under *Invoicing > Configuration >
Dunning Levels*.

## Reference

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

## Troubleshooting and FAQ

This bridge raises no message of its own. What it did is in the notes on the customer.

- **A customer at a holding level is not on hold.** It has a *Manual Credit Decision*, or it reached
  the level before the box was ticked: the hold is set when a customer moves onto the level.

### Questions people ask

**Do I have to install it?** It installs by itself with the two apps.

**Does a credit manager's decision stand?** Yes: a Forced Hold or a Forced Release is never touched.

**Which levels hold?** Those with *Put the customer on credit hold* ticked; none of the two
installed levels does until you tick it.

### Support

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

## Changelog

### 20.0.1.0.1

- This manual, the bridge's first.

### 20.0.1.0.0

- A dunning level marked 'put the customer on credit hold' puts the customer on an automatic credit
  hold when it is reached, and lifts it when the level is cleared.
- Built for Odoo 20.


## 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

#### res.partner (extends Odoo's res.partner)

Adds no fields.

#### customer.statement.schedule (extends bambooforge\_customer\_statement's customer.statement.schedule)

Adds no fields.
