How to Automate Alerts for Service Payments and Corrections

Important collections events wait for someone to notice

A large payment, a correction request, or a new retainer month is something the owner wants to know about now, not at the next dashboard check.

Without triggers, follow-up depends on someone remembering to look.

Alerts that go to the wrong people can leak amounts to staff who must not see them.

Why this happens

• Events in Collections do not start anything automatically.
• Follow-up tasks are created by memory.
• Alert recipients are not chosen with blindness in mind.
• Triggers appear for modules that are not licensed.

Biznsbook addresses this through Collections automation triggers, payment recorded and job created, correction requested and decided when Service Billing & Collections is licensed. Clients are the parties you already keep, and collectors record what they received without seeing the fee or the outstanding.

Services firms lose money in the gap between the work done and the payment recorded. Keeping the fee on the job, the payment against the job, and the collector away from the numbers closes that gap without turning the firm into an accounting office.

Step-by-step: Automate Alerts for Service Payments and Corrections

Built for owners of services firms and the staff who collect client payments in Biznsbook Collections.

1. Open Business Automation. Create a workflow. With Collections licensed, the four Collections triggers appear in the trigger list.
2. Pick Collection Payment Recorded. It fires when a payment counts: recorded on Record a payment, or a client-link payment you accepted.
3. Add a condition. For example, only when the amount is above a set value, or only for one payment mode.
4. Add an action. For example, email the owner, or create a task for the person who looks after the client.
5. Use the job trigger for retainers. Collection Service Job Created fires for new jobs and for each monthly job a retainer adds, so you can notify the assignee when a month is billed.
6. Follow up corrections. Collection Correction Requested fires when a request is saved; Collection Correction Decided fires when it is approved or rejected.
7. Keep recipients to owners. Trigger details include amounts. Send them to owners and managers only, never to collectors.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen names in this guide match Collections in the product: Record a payment, My entries, Dashboard, Jobs, Payments, Payment links, Corrections, Service types, Settings, and Guide. Every screen has a ? help button.

Common mistakes to avoid

• Mistake 1: Events in Collections do not start anything automatically. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.
• Mistake 2: Follow-up tasks are created by memory. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.
• Mistake 3: Alert recipients are not chosen with blindness in mind. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.
• Mistake 4: Triggers appear for modules that are not licensed. Repeating this each month usually shows up first in billed, collected, or outstanding for the period.

Note each recurring gap in the weekly review; each should map to a step in this guide.

Best practices that hold up as you scale

• Open Business Automation — Create a workflow.
• Pick Collection Payment Recorded — It fires when a payment counts: recorded on Record a payment, or a client-link payment you accepted.
• Add a condition — For example, only when the amount is above a set value, or only for one payment mode.
• Add an action — For example, email the owner, or create a task for the person who looks after the client.
• Use the job trigger for retainers — Collection Service Job Created fires for new jobs and for each monthly job a retainer adds, so you can notify the assignee when a month is billed.

Firms that keep the fee on the job, let Collections compute outstanding, and correct by reversal instead of editing a row keep their period totals and their trail intact.

How Biznsbook supports this workflow

Collections automation triggers is part of Biznsbook Service Billing & Collections. Each client is a party you already keep, each job holds its fee, and each payment keeps who entered it, when, and how the client paid.

payment recorded and job created is part of Biznsbook Service Billing & Collections. Each client is a party you already keep, each job holds its fee, and each payment keeps who entered it, when, and how the client paid.

correction requested and decided is part of Biznsbook Service Billing & Collections. Each client is a party you already keep, each job holds its fee, and each payment keeps who entered it, when, and how the client paid.

Ledger posting is off until Collections settings turn it on, and only when Accounting or Finance is licensed. Outstanding is the fee plus any tax, minus the payments on the job. Collectors do not see fees, outstanding, other people’s entries, the dashboard, statements, the correction queue, or a journal.

Suggested implementation timeline

1. Week 1: Add your service types, check that clients exist as parties, and open jobs with fees.
2. Week 2: Start Collections automation triggers with one collector and a handful of clients.
3. Week 3: Add the rest of the collectors and clear the dashboard attention items daily.
4. Week 4: Review billed, collected, and outstanding by age with the client statements.
5. Ongoing: Weekly review using when each trigger fires and the dashboard.

Related guides

Start with track a service job and fee and record a client payment without showing the fee. Then bill a monthly retainer, split a fee into installments, and read billed, collected, and outstanding.

Owner routines: review link payments, confirm cash hand-over, and the daily summary email.

All guides: service billing & collections. Decision page: service billing software vs spreadsheets. Product page: Service Billing & Collections.

What the triggers carry

Payment Recorded carries the payment number, client, amount, mode, reference, date, the service reference it is on, who entered it, and whether it was an over-payment or reused a reference. Job Created carries the client, reference, service date, fee or fee not set, tax, service type, assignee, and whether it came from a retainer.

Correction triggers carry the payment number, the type of correction, the reason, who asked, and — on the decision — whether it was approved and the replacement number.

Keeping automation blind-safe

Collections keeps fees and outstanding away from collectors on every screen. Automation is built by the owner, so the owner decides who receives what. Keep amount-bearing alerts to owners and managers, the same people who can see amounts in Collections.

A safe pattern for collectors is a task that names the client and the service reference only, without the amount.

Example workflows

Large payment alert: trigger Collection Payment Recorded, condition amount greater than a value you choose, action email the owner with the client, the amount, the mode, and the reference.

Correction follow-up: trigger Collection Correction Requested, action create a task for the manager who approves corrections, with the payment number and the reason.

Retainer month billed: trigger Collection Service Job Created, condition from retainer is true, action notify the assignee that the month has been billed.

Triggers and licensing

The Collections triggers appear in the trigger list only when Service Billing & Collections is licensed for the company, so a workflow cannot be built on a module you do not use.

Events are published after the change is saved. If publishing ever fails, the payment, job, or correction is still saved, so automation never blocks collecting money.

Testing a workflow safely

Build the workflow, then record a small test payment against a test job yourself. The run appears in the workflow’s execution log with the trigger details, so you can check the condition and the action before relying on it.

If the test payment should not stay, request a correction with a reason and approve a void; the original is reversed and kept on record.

Metrics to track monthly

• Billed for the date range
• Collected for the date range
• Outstanding, and outstanding older than 90 days
• Collections by payment mode
• Payments not yet reconciled

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Spreadsheets and notebooks vs Biznsbook Collections

Compare running this on spreadsheets with Biznsbook Collections automation triggers and related capabilities.

When each trigger fires

Payment Recorded fires when a payment counts — not for opening credits, link payments still waiting, imports, or the replacement written by a correction. Job Created fires for new jobs and retainer months, not edits. Correction Requested and Decided fire when a request is saved and when it is approved or rejected.

Write this into your weekly owner routine and revisit it when you add collectors or new services.

Frequently asked questions

How this differs by industry