Receivables & arrears
Knowing who owes what, for how long, without rebuilding it each month. Charges recur on schedule, late fees apply by rule rather than by memory, and arrears age into buckets you can act on.
What it does
Recurring charges
Rent and periodic charges generate on schedule against the lease, so billing is not a monthly manual exercise.
Rule-based late fees
Late fees apply from configured rules with grace periods, rather than at whoever remembers.
Arrears ageing
Balances age into buckets so the difference between four days late and four months late is visible without arithmetic.
Payment allocation
A receipt is applied against outstanding charges, so a part-payment leaves a correct remaining balance rather than an unallocated credit.
Receipts and history
Every payment produces a receipt and stays on the tenancy record — the evidence a tenant needs and the trail a dispute needs.
Credits
Credits are held and applied to rent explicitly rather than being absorbed into a balance.
How it works
The sequence an operator actually follows, not a feature list rearranged into steps.
- 1
A lease defines its rent and schedule.
- 2
Charges generate; the tenant is notified.
- 3
Payment arrives, is allocated against the oldest outstanding charge, and posts to the ledger.
- 4
Anything unpaid ages, and late fees apply by rule.
What the database guarantees
These hold whether or not the interface remembers to check.
- A payment posts to the ledger once, keyed on the payment, not on the attempt.
- Allocation is recorded, so a balance can always be explained.
What it does not do yet
You will ask this in an evaluation, so here it is without being asked.
- Automated dunning sequences are not built. Arrears are surfaced; chasing them is a person's job.
- Direct debit / standing order mandates are not integrated.
Works with
These share the same database, so nothing is re-keyed between them.