CRM in NocoBase with Receivables Management: Debt Aging on the Dashboard, a 3-Beat Reminder Workflow, and AI-Drafted Reminders
by BAMFLOW • • 5 min read • Updated 13 Nov 2026
A CRM built in NocoBase around receivables management the Vietnamese way: debt aging buckets on the accounting dashboard, a three-beat reminder workflow, credit-limit guards, and an AI Employee drafting reminders for human approval.
CRM in NocoBase with Receivables Management: Debt Aging on the Dashboard, a 3-Beat Reminder Workflow, and AI-Drafted Reminders
Quick summary: Off-the-shelf CRM products overflow with features yet miss the one thing Vietnamese B2B companies need most: receivables management (quản lý công nợ) that matches how business here runs. This guide builds a CRM in NocoBase — Customers, Opportunities, Orders, Receivables — with debt aging on the accounting dashboard, a three-beat reminder workflow, and an AI Employee drafting reminders for human approval.
Ask a distribution company in Vietnam where its money is, and the honest answer is: out there — delivered goods, issued invoices, receivables scattered across the accountant's spreadsheet, each salesperson's memory and chat messages. When the director asks "How much overdue debt do we have, and who owes the oldest?", the room needs half a day to answer. Companies buy CRM to cure this — then abandon it, because the product has no receivables view in the local style.
The one thing packaged CRM lacks: receivables, Vietnamese style
International CRM assumes customers pay by card or on hard terms; chasing debt barely exists in the product. Vietnamese B2B runs on trade credit: deliver first, grant 15, 30 or 45 days, and let relationships bend the rules. Receivables are the company's bloodstream. Judge any CRM by one question: can its receivables screen answer in ten seconds — who is overdue, how much, from which orders, who owns the follow-up? A CRM built on NocoBase can, because its receivables module is designed around that question. NocoBase is the open-source, self-hosted platform introduced in What is NocoBase — no per-user fees, data on your own server.
Data model: Customers / Opportunities / Orders / Receivables
Four linked tables carry the system. Customers hold the basics plus two operational fields that power everything else: a credit limit (hạn mức công nợ) and a default payment term in days. Opportunities form the sales pipeline — value, stage, owner — shown as a drag-and-drop Kanban; a won opportunity generates the order, so nobody re-enters customer data. Orders are the single source of truth: warehouse ships against them, receivables arise from them, revenue is counted from them. Receivables are created automatically on confirmed delivery: amount, issue date, due date (delivery date + term), amount paid, balance, status. Partial payments post as receipts against the exact debt, so the balance is always one subtraction away.
Debt aging on the accounting dashboard
With clean data, the key view is the classic aging table, recalculated daily:
| Aging bucket | Meaning | Suggested handling |
|---|---|---|
| Not yet due | Within agreed terms | Just monitor |
| Overdue 0–30 days | Freshly overdue, often admin delay | Gentle reminder to the right contact |
| Overdue 31–60 days | Worrying; possible cash stress | Sales + accounting together; consider holding new shipments |
| Overdue 60+ days | Potential bad debt | On the director's list, handled case by case |
The dashboard shows totals per bucket, biggest debtors on top. Two guards complete the picture: a credit-limit flag on any order that would push a customer over their limit — the ship-or-not decision happens before goods leave — and an alert when a customer with overdue debt orders again, the classic way bad debt balloons.
The 3-beat reminder workflow
Collecting well is about rhythm: too early annoys customers, too late loses money — and humans are reliably inconsistent at it. A NocoBase workflow gives every debt the same three beats. Beat 1, three days before due: a light notice to the owning salesperson (and/or the customer, per policy); most decent customers pay on time when reminded once. Beat 2, on the due date, unpaid: a second notice with the order breakdown attached, so the customer can reconcile immediately. Beat 3, overdue (day 1, 7, 15…): escalating visibility — salesperson, accounting lead, then the director's dashboard, with the customer flagged "hold new shipments" until payment lands. Every beat is logged. The workflow owns the remembering; people own the content and decisions.
AI Employee drafts the reminder — a human approves it
Debt reminders are delicate: too hard loses the customer, too soft loses the money. NocoBase's AI Employee reads the real CRM context — amount, days overdue, payment history — and drafts a reminder in the right tone: courteous for a good customer who slipped once, firmer for a third-time offender. A human reviews, edits, then sends. BAMFLOW's rule: AI drafts — human approves — system executes.
The CRM pairs with the warehouse on the same data — see QR code warehouse management in NocoBase: approve an order and the warehouse sees the shipment, accounting the receivable.
Free template: the CRM – Receivables template (four tables, aging dashboard, 3-beat reminder workflow) accompanies this article to import and trial.
About BAMFLOW — BAMFLOW is the official NocoBase partner in Vietnam, implementing and teaching AppSheet, NocoBase and AI for businesses (300+ applications built, 150+ business clients, 1,000+ students trained).
- Want to build your own system? Register for the NocoBase AI Builder course (12 sessions) — the CRM & receivables session builds this exact system on your real data.
- Want it implemented for you? Message BAMFLOW via bamflow.vn for advice tailored to your exact operations.