Before you start
How it works
How Bitta Collections adds a worklist, dunning, promises, disputes, credit holds and cash application to Business Central on the live customer ledger.
updated: applies-to: 1.2.0.0
Bitta Collections is a Business Central app for accounts receivable collections and cash application. It runs inside Business Central online and reads amounts live from the customer ledger. There is no second receivables ledger and nothing to sync.
Applies to: Bitta Collections 1.2 on Business Central online, version 28 or later.
What Business Central does on its own
Business Central already has the basics of collections. Reminder terms and levels send reminders with fees and interest. Reminder Automation creates, issues and sends them on a schedule. The Customer Statement report prints statements. The Payment Reconciliation Journal matches bank lines to open entries. Customer ledger entries have a Promised Pay Date and a Dispute Status field.
What is missing is the collector's daily work: a list of who to contact first, a record of what was agreed, a check that promises were kept, disputes that pause the right invoice, and holds that follow rules. Bitta Collections adds that work on top of the native features instead of replacing them.
The collector's day
- Once scheduled, the collections job runs every weekday at 06:00. It checks promises and disputes, evaluates credit holds, runs the dunning sequences and refreshes the worklist.
- The collector opens the Collections Worklist. Each customer with overdue money has one work item, scored from 0 to 100. The Score Explanation says why, for example "3,500.00 USD overdue, oldest 40 days, no risk rating".
- The collector calls or emails the top customer and logs the outcome with Log Activity. A promise to pay or a dispute is recorded in the same step.
- Routine contact runs on its own. A dunning sequence sends a courtesy email before the due date, reminders, a statement, a native reminder, a call task, a credit hold and an escalation as invoices get older. A step can run automatically or wait for the collector.
- When the customer pays, the payment is applied in Business Central. The promise is marked Kept, Partly Kept or Broken from the applied payments, and the work item updates.
How the parts fit together
| Part | What it does | What it builds on in Business Central |
|---|---|---|
| Worklist and activities | One scored work item per customer, with a log of calls, emails, notes and meetings | Customer ledger entries, read live |
| Dunning sequences | Steps by days overdue, one contact per customer per run | Reminder terms, Create Reminders, Issue and Send, the Email module |
| Promises to pay | Promise per invoice, checked against applied payments | The native Promised Pay Date field |
| Disputes | Dispute per invoice with reason, owner and due date; pauses dunning for that invoice | The native Dispute Status codes and field |
| Payment plans and agencies | Installments with an agreement; hand-off to a collection agency | Promised Pay Date, the native On Hold field, general journals |
| Pay links | Pay now links through your own Stripe account (card and US ACH) or your payment services; paid Stripe payments become journal lines | Payment Services, cash receipt journals |
| Cash application | Matching suggestions with an explanation; a person accepts and posts | Payment Reconciliation Journal, Apply Customer Entries |
| Credit holds | Holds by rule per risk rating; release with a reason code | Release and posting checks on sales documents, Reason Codes |
| Communication | Emails, statements, letters and letters by post | Email module, Report Selections |
| AI features (preview) | Draft emails, account summaries, ranked matches and reply triage; a person confirms | The Business Central Copilot framework |
| Forecast and reports | Predicted pay dates, a cash forecast, role center KPIs and more than 40 reports | Report and Excel layouts |
| Collections API | Read and act on collections data from Power Automate, Power BI and other API clients | Business Central API pages |
Because Bitta Collections writes the native Promised Pay Date and Dispute Status fields, people who never open the app still see promises and disputes on customer ledger entries. Native reminders and finance charge memos also skip invoices that are disputed or promised, so a customer is not chased for money it already agreed to pay.
What a person always does
Bitta Collections prepares and suggests. People decide. No payment is applied and nothing is posted until a person accepts it. AI drafts are never sent by the app; a person reviews and sends them. Holds placed by hand are never released automatically, and every release needs a reason code.
Who it is for
Bitta Collections is built for receivables between businesses, for companies in the United States and Canada on Business Central online. See Requirements for what each feature needs, and Compare your options for how it relates to native Business Central.
What's next
Install the app and run the assisted setup: Getting started.