MODULES / CUSTOMER

Customer Follow-up

Configure overdue stages and schedule auditable internal collection activities.

Overview

Module idask_customer_followup
Version1.0.0
Who uses itAnyone who uses the screens listed below.
InstalledOn demand, from Settings → Modules. Anything it needs is installed with it.

Where to find it

Reports / Receivables & payablesCustomer follow-up

The menu entries appear once the module is installed and your role allows them.

How it links to other modules

A module that is needed cannot be turned off while the module that needs it is on.

Details

Customer Follow-up

ASKERP adaptation of om_account_followup from the authorized Odoo 18 source tree D:/Odoo18/sparkosol/addons.odoo18/om_account_followup (LGPL-3).

The module reads overdue customer residuals from ASKERP's posted-ledger aged receivable service. Company-configured stages set an overdue-day threshold, order, internal activity summary/note, and optional company-member assignee. Scheduling creates a normal partner activity, notification, chatter event and immutable follow-up action snapshot in the same transaction. Each customer has at most one open case; stages progress once in order. A case can be resolved after its overdue receivable balance clears. Disabling the module hides its screens and service reads but retains cases and action history for reinstall.

The Odoo source also sends letters and emails. Stages may now have an optional reminder subject and plain-text body. A user with Sales and Accounting draft rights explicitly queues the message; no customer is enrolled in automatic sends. The recipient, message and posted-receivable balance are resolved server-side and stored as an immutable snapshot before the SMTP worker sends. Queue/send outcomes remain visible in the email history. Templates accept {{customer}}, {{company}}, {{amount}}, {{currency}}, {{days}}, {{oldest_due}} and {{as_of}}. The message also lists up to 100 overdue documents. Email requires the company's existing SMTP configuration. The addon still does not create invoices, payments, reconciliation rows or ledger entries. Existing recovery letters remain separate. The board shows posted receivables only, uses aging as of the reader's date, and subtracts open customer credits from the overdue total.

Migrations 0109_customer_followup.sql and 0117_customer_followup_emails.sql add tenant-RLS-protected stage, case, action and email history. A partial unique index enforces one open case per partner; database guards retain terminal cases, immutable action evidence and immutable email snapshots. Partner rows are locked before case rows in schedule, resolve and email-queue workflows.

Validation: npx vitest run addons/ask_customer_followup/addon.test.ts, npm run test:migrations, npm run typecheck, and npm run lint.

Customer Follow-up | ASKERP Docs