Skip to content

Scenario · Accounts · CollectionsScenario · Collections

Who follows up the payment once the invoice is sent?

At Beta1, Anika sends the invoices and then remembers which ones to chase. When a customer said “after the 20th”, it went in her notebook. When one held payment over two leaking valves, quality never heard about it, and the invoice crossed 45 days.

TaskMIS task 0922-0002, Collect payment: invoice 2261, Trichy contractor: Accounts, Receivables, raised by Aarav Shah on 22 Sept, deadline changed once; assigned to Anika Bose, In Progress, High priority, due 28 Oct, was 22 Oct, moved once, Client delay; waiting for Kiara — inspection of the 2 returned valves since 21 Oct; request HOD, High business impact; what done looks like: invoice 2261 of 22 Sep, 30-day terms, 36 butterfly valves, order 2557. Shown on Wednesday 21 Oct at 10:45 AM
Task 0922-0002 on Wednesday 21 Oct, 10:45 AM · Beta1 demo workspace, sample data
See the same month in TaskMIS

Illustrative scenario. Beta1 is a fictional company. Not a customer story.

Meet Beta1 — a fictional valve manufacturer in Coimbatore.

  • Anika BoseAnika · Accounts
  • Aarav ShahAarav · Sales · Admin
  • Kiara RaoKiara · Quality

What went wrong

The invoice went out. The follow-up stayed in one notebook.

  1. AccountsInvoices sent; due dates in a notebook.
  2. Customer“Payment after the 20th.” Noted, nowhere else.
  3. Trichy contractorHolds payment over two leaking valves. Quality does not know.
  4. Month endNobody can say which invoices are late, or why.

One notebook. Three costs.

  • Collections start lateThe first call happens after the due date, not before it.
  • A dispute waits on the wrong deskAccounts cannot fix two leaking valves, and quality does not know they came back.
  • No record of the promisesWhen a customer moves their payment date, nobody can see how often.

The same month with TaskMIS

Same invoices. Each one has a collection task and a date.

  1. 01 ListTue 13 Oct
  2. 02 RemindWed 14 Oct
  3. 03 Dispute21 – 23 Oct
  4. 04 Month endFri 30 Oct

Tue 13 Oct, 9:00 AM · ListTue 13 Oct, 9:00 AM · Every invoice has a collection task

Every invoice has a collection task, due on its due date.

When an invoice goes out, Aarav raises a collection task for Anika: the invoice, the customer and the terms in the name, the payment due date as the target. Searched for “Collect payment”, the list is the collection calendar.

5 collections · due 15 Oct – 6 Nov · owner: Anika

Tasks searched for Collect payment, Tuesday 13 Oct at 9 AM: 5 tasks, all Accounts, Receivables, Anika Bose, High. 1007-0006 invoice 2275, Hosur pump maker, due 06 Nov; 1003-0005 invoice 2270, Salem dealer, due 02 Nov; 0929-0003 invoice 2266, Coimbatore pump maker, due 29 Oct; 0922-0002 invoice 2261, Trichy contractor, due 22 Oct; 0915-0001 invoice 2254, Erode pump maker, due 15 Oct
Tasks → search “Collect payment”, Tuesday

Wed 14 Oct, 7:00 AM · Remind

The reminder comes before the due date, not after it.

The day before invoice 2254 is due, Anika gets the reminder. She calls at 11: the invoice is approved, but the customer pays on the 20th. She moves the date with the reason Client delay, and Aarav, who raised the task, gets the mail. The money arrives on the 20th.

Reminder mail to Anika Bose: due tomorrow, this task is due tomorrow, Collect payment: invoice 2254, Erode pump maker; due Thu 15 Oct 2026; raised by Aarav Shah; priority High; task 0915-0001; Not going to make it? Move the date now, with the reason, so Aarav Shah hears it before the day.
Anika’s reminder, Wednesday 7 AM

Reminder mail to Anika

21 – 23 Oct · DisputeWed 21 Oct, 10:30 AM – Fri 23 Oct, 12:25 PM · A dispute goes to the right desk

A held payment goes to the person who can fix it.

The Trichy contractor holds invoice 2261: two valves came back leaking. Anika writes it on the task, raises an inspection task for Kiara, and marks the collection as waiting for her. Kiara finds the packing damaged in transit and releases two replacements on Friday. Paid on the 28th.

The record of task 0922-0002, 7 entries: Aarav Shah raised this task on 22 Sept at 15:30, assigned to Anika Bose, target date 22 Oct; Status: Not Started → In Progress, Anika Bose, 21 Oct, 10:20; Anika Bose at 10:30: Customer is holding payment: 2 valves returned as leaking; Now waiting for: Kiara — inspection of the 2 returned valves, 10:35; Date moved 22 Oct → 28 Oct by Anika Bose, Client delay — customer holding payment until the 2 returned valves are replaced; No longer waiting — unblocked, 23 Oct, 12:20; Anika Bose at 12:25: Replacement valves sent today. Customer will pay on receipt
Invoice 2261’s collection task, Friday · append-only, no user can edit

Fri 30 Oct, 5:00 PM · Month endFri 30 Oct, 5:00 PM · What is collected, and what is next

At month end, the collections answer for themselves.

Three October invoices are collected and in the Archive, each with its date and, where it moved, the reason. The next three are open with their due dates, and the first of them falls due on Monday.

Collected: 3 · open: 3, first due Mon 2 Nov

Tasks searched for Collect payment, Friday 30 Oct at 5 PM: 3 open tasks, Anika Bose, Not Started. 1014-0012 invoice 2281, Madurai dealer, due 13 Nov; 1007-0006 invoice 2275, Hosur pump maker, due 06 Nov; 1003-0005 invoice 2270, Salem dealer, due 02 Nov
Tasks → search “Collect payment”, 30 Oct · what is next
Archive searched for Collect payment, Friday 30 Oct: 3 completed tasks. 0922-0002 invoice 2261, Trichy contractor, Anika Bose, completed 28 Oct; 0929-0003 invoice 2266, Coimbatore pump maker, completed 28 Oct; 0915-0001 invoice 2254, Erode pump maker, completed 20 Oct
Archive → search “Collect payment” · collected, with the dates

Try it on this month’s invoices.

Free for up to 6 members. No credit card required.

Join TaskMIS Today

The difference

Same customers. Different month end.

DateIn a notebookIn TaskMIS
13 OctTueNotebookDue dates in Anika’s notebook.In TaskMISFive collection tasks, each due on its date
14 OctWedNotebookThe first call is after the due date.In TaskMISReminder the day before; promise moved with a reason
21 OctWedNotebookThe held payment waits in accounts.In TaskMISInspection task for Kiara; collection waits for her
23 OctFriNotebookQuality hears about the valves at month end.In TaskMISCause found; replacements released
30 OctFriNotebookWhich invoices are late, and why? Nobody can say.In TaskMISArchive: 3 collected; 3 open with datesNothing forgotten

The customers paid when they paid either way. The difference is that every promise and every hold was on record, with an owner.

What could change

Three outcomes for Beta1

Collection calls start before the due date.

Each invoice’s collection is a task, and the reminder comes the day before.

FeatureReminders before the due date · A target date is required

A dispute reaches the person who can settle it.

The collection waits for a named person, with their own task and a date.

FeatureWaiting for · One owner on every task

Every customer promise is on record.

A moved payment date carries its reason, and the person who raised it hears the same day.

FeatureA reason for every date change · The raiser hears about it

Possible outcomes in a fictional scenario, not measured customer results.

Used in this scenario

  • One owner on every task
  • A target date is required
  • Reminders before the due date
  • Updates on the task
  • Waiting for
  • A reason for every date change
  • The raiser hears about it
  • Archive
See every feature on the Product page →

For the owner

Four answers about money owed

  • Which collections fall due this week?

    Answered in: Tasks · Search “Collect payment”
  • Which payments are held, and who is fixing it?

    Answered in: Tasks · Waiting on someone
  • How often has this customer moved their date?

    Answered in: Task record
  • What did we collect this month?

    Answered in: Archive · Search

Start this week

Start with the invoices open today

  1. Raise one collection task per open invoice, with the invoice number and customer in the name and the due date as the target.
  2. When a customer gives a new date, move the task to it with the reason, the same day.
  3. When a payment is held over a complaint, raise a task for the person who can fix it and mark the collection as waiting for them.

Questions

Quick answers

Does TaskMIS record payments or send invoices?

No. Keep invoices and receipts in your accounts software. TaskMIS tracks the follow-up: who is chasing, by when, and why the date moved.

Can the customer see the task?

No. Only your team works in TaskMIS. Accounts records what the customer promised, and why the date changed.

Who gets the reminder?

The task’s owner, the day before it is due by default, and again on the day. The admin can set it to 0, 1, 2, 3, 5 or 7 days before.

Bring clarity and accountability to your team.

Join TaskMIS Today

Free for up to 6 members. No credit card required.