Arrears that no longer settle in
From the friendly reminder to the complete file, every step leaves on time and leaves its trace.
The problem
What costs is the delay, not the amount
A debt chased within the month gets recovered. The same one, forgotten for twelve months, becomes litigation, ties up the owner council and weighs on everyone else's budget. A spreadsheet chases nobody.
Demonstration
A recovery campaign, from day one to the file
The timeline runs on its own. Every step produces a document, and every document is archived.
A recovery campaign
The delays below are those of a typical campaign. They are configured building by building.
- 1
Due date
Day 0
The budget call falls due. The owner's account moves to overdue.
- 2
Reminder
Day 15
A neutral reminder. Most delays stop here.
- 3
Chase
Day 45
Written chase with the itemised statement of sums due.
- 4
Formal notice
Day 90
Formal letter itemising sums by chapter, archived with proof of sending.
- 5
File assembled
Beyond
History, documents and statements gathered for the owner council or legal counsel.
Moving to litigation depends on the building rules and on your legal counsel's advice. The platform builds the file; it does not decide for you.
What the module actually does
Automatic triggering
Reminders go out on the defined due dates, without a manager thinking about it.
Every send leaves a trace
Date, recipient, channel and content are logged. So is a non-send, with its reason.
Formal notice ready
The letter itemises the sums due by chapter, as the decree requires of the agent.
A complete file
History, documents and statements gathered for the owner council or legal counsel.
Who it is for
The shortest path is still seeing it run
Thirty minutes, a demonstration building, and your real cases entered in front of you.