Receivables and collections in one traceable flow.
Every business that sells on credit is running two businesses at once: the one that delivers and the one that chases. The chasing half rarely has a system — it has a spreadsheet, a stack of calls and the memory of whoever handles collections. Tenderely BPM turns each outstanding invoice into a structured record with a history, a next step and a visible ageing position, without code.
What does a collections process repeat?
01
Issuing the sales invoice
An invoice needs to reach the right person at the customer, in the right format, at the right time. One that lands in the wrong inbox is effectively never sent.
02
Tracking outstanding balances
Which customer owes how much, since when, against which invoice. Without a single source of truth this question takes time to answer every time it is asked.
03
Recording payments
Partial payments, split payments across invoices and advance receipts all need to be matched correctly or the balance shown is wrong.
04
Collecting a promise to pay
A customer commits to paying by a date. That commitment needs to be recorded, and the team needs a reminder if the date passes without money arriving.
05
Ageing and prioritisation
Not all overdue amounts are equal. A bucket view — current, 30 days, 60 days, 90 days and beyond — tells the team where to focus effort first.
06
Escalation and approval
Some decisions — writing off a balance, extending terms, handing a case to legal — need a manager's sign-off and a record that it happened.
Where does this break down today?
The balance lives in a spreadsheet nobody trusts
Two people maintain it in parallel, payments land at different times, and by mid-month the number in the spreadsheet and the number in accounting no longer agree.
Chasing depends on one person's memory
Who was called, what they promised, when to follow up — if the person who makes collection calls is away, nothing moves. There is no handover because there is no record.
Promises to pay are verbal
A customer says they will pay on Friday. It is not written anywhere. Friday comes and goes, and nobody follows up because nobody was reminded.
Escalation decisions leave no trace
A manager agrees to extend a customer's payment terms or write off a small amount over the phone. Six months later, when the auditor asks, there is no record that it was authorised.
What changes with Tenderely BPM
01
Every invoice is a live record
Issue date, due date, amount, customer, partial payments received — all in one place. The balance is not calculated from memory; it is derived from what has been recorded.
02
Promises to pay are on the record
When a customer commits to a date, the commitment is logged. If the date passes without a payment being recorded, a reminder goes out automatically.
03
Ageing is always visible
Current, 30, 60, 90 days and beyond — the ageing position sits on a dashboard and updates as records change, without anyone running a report.
04
Escalation is a step, not a phone call
Decisions to extend terms, write off balances or escalate to legal pass through a conditional approval step. The authorisation is recorded as a by-product of the process.
05
Collections happen on a phone
Tenderely BPM runs in the iOS and Android apps, so a collections team member can log a call outcome, record a promise to pay and move a case forward from wherever they are.
06
Customers can be reached with a public form
Send a customer a link to a public form for submitting a payment commitment or a dispute. Their response lands on the same record without them needing an account.
FAQ
Does this replace our accounting software?
+
No, and it is not designed to. Accounting software owns the ledger. This module owns the operational process around collections: the chasing, the promises, the approvals and the communication history. The two are complementary, and records can be exchanged between them through the available export, webhook and API options.
Can we set different collection workflows for different customer segments?
+
Yes. Conditional branching means the flow a record follows can depend on customer type, overdue bucket, amount or any other field you define. A small overdue balance and a large one can have entirely different escalation paths without any code.
Who can see which customer's balance?
+
Role- and unit-level permissions decide who sees what. A sales representative can be limited to their own accounts, a regional manager to their territory, and finance to everything. Individual sensitive fields can be hidden from specific roles.
How do we know who contacted a customer and what was said?
+
Every action taken on a record — a note added, a promise recorded, a status changed, an approval given — is stored in the audit history with a timestamp and the name of the person who did it. The full contact history is on the record.
Can we start with a ready setup and adjust it?
+
Yes. The Receivables and Collections package installs with forms, flows and a dashboard already in place, giving you a working starting point within minutes. You then adjust each piece to match how your business actually operates.