Skip to Content
Credit Control

Credit Control

This course covers Credit Control (automated collections/dunning) in Quickenerp: building an escalating reminder policy, running it periodically, reviewing and sending reminder communications, and tracking who's overdue and by how much.

Responsible System
Last Update 07/21/2026
Completion Time 1 day 16 hours
Members 1
Accounting & Finance
Setting Up Policies & Escalation Levels
Setting Up Policies & Escalation Levels

Designing Your Collections Escalation

Go to Accounting > Configuration > Credit Control PoliciesCreate.

Adding Levels

Each level defines:

  • Compute Mode – how the delay is measured: from the invoice's Due Date, Due Date, End of Month (rounds to month-end, common for consolidated monthly statements), or from the Previous Reminder (each level counts from when the last one went out, not the original due date).
  • Delay (Days) – how many days after that reference point this level triggers.
  • Channel – how the reminder goes out (email, physical letter — see the SMS & Snail Mail course for the postal option).
  • Email Template – the message used at this level.
  • Custom Message – text specific to this escalation stage (friendly at Level 1, firm at Level 3).
  • Show Invoice Details – whether to list every overdue invoice's specifics in the reminder, or keep it a simple notice.

A Typical 3-Level Policy

  1. Level 1 (7 days overdue) – friendly email reminder, invoice details included.
  2. Level 2 (30 days overdue) – firmer email, cc'd to a manager.
  3. Level 3 (60 days overdue) – final notice, potentially by post as well as email.

Assigning a Policy

Set a default company-wide policy, or override it per customer (e.g. a strategic account gets a gentler policy, a chronically late payer gets a stricter one) on the partner's own record.

Credit Control Overview
View all
New Content
Setting Up Policies & Escalation Levels
Setting Up Policies & Escalation Levels
Preview

Designing Your Collections Escalation

Go to Accounting > Configuration > Credit Control PoliciesCreate.

Adding Levels

Each level defines:

  • Compute Mode – how the delay is measured: from the invoice's Due Date, Due Date, End of Month (rounds to month-end, common for consolidated monthly statements), or from the Previous Reminder (each level counts from when the last one went out, not the original due date).
  • Delay (Days) – how many days after that reference point this level triggers.
  • Channel – how the reminder goes out (email, physical letter — see the SMS & Snail Mail course for the postal option).
  • Email Template – the message used at this level.
  • Custom Message – text specific to this escalation stage (friendly at Level 1, firm at Level 3).
  • Show Invoice Details – whether to list every overdue invoice's specifics in the reminder, or keep it a simple notice.

A Typical 3-Level Policy

  1. Level 1 (7 days overdue) – friendly email reminder, invoice details included.
  2. Level 2 (30 days overdue) – firmer email, cc'd to a manager.
  3. Level 3 (60 days overdue) – final notice, potentially by post as well as email.

Assigning a Policy

Set a default company-wide policy, or override it per customer (e.g. a strategic account gets a gentler policy, a chronically late payer gets a stricter one) on the partner's own record.

New Content
Running, Reviewing & Sending Reminders
Running, Reviewing & Sending Reminders
Preview

From Overdue Invoice to Sent Reminder

Running the Policy

  1. Go to Accounting > Management > Credit Control Run → set the run date (usually today) → Generate Credit Lines.
  2. Quickenerp scans every overdue invoice, determines which policy level (if any) applies right now, and creates a Credit Control Line for each.

Reviewing Before Sending

Lines start Draft and need triage:

  • To Do – confirmed, ready to actually send.
  • Ignored – mark a specific line to skip (e.g. you already know the customer disputes this invoice and a reminder would be premature/incorrect).
  • QueuedDone – sent successfully.
  • Error / Emailing Error – something failed (e.g. missing customer email) — review and correct before re-attempting.

Communications

Multiple overdue lines for the same customer at the same level are grouped into one Communication rather than sending a separate email per invoice — a customer with 4 overdue invoices at Level 1 gets one consolidated reminder listing all 4, not 4 separate emails.

Sending

Confirm the To Do lines and send communications — either individually reviewed each run, or, once you trust the process, mark lines "To Do" and send in bulk. Keep reviewing at least the first few runs manually before fully automating.

New Content
Introduction to Credit Control
Introduction to Credit Control
Preview

Automating "Please Pay Your Invoice"

Rather than an accountant manually deciding who to chase and when, Credit Control lets you define an escalating reminder schedule once, then run it regularly — it automatically finds every overdue invoice, figures out which reminder level each customer is due for, and prepares (or sends) the right communication.

Core Concepts

ConceptDescription
PolicyYour overall dunning strategy — a named set of escalation levels, assignable per customer or used as the company default.
Policy LevelOne step in the escalation (e.g. Level 1 = friendly reminder, Level 2 = firm notice, Level 3 = final demand), each with its own delay, tone, and email template.
RunExecuting the policy for a given date — scans all overdue invoices and generates the lines below.
LineOne overdue invoice's reminder record for that run, with its own status.
CommunicationThe actual reminder document/email sent to a customer, grouping all their overdue lines at the appropriate level together into one message.
This documentation is updated continuously. Some features described here may be renamed, deprecated, or still being finalized.