Income Ally
Sign in →
For Regulatory Compliance

Where the law says stop, it stops.

Thirteen duties change what the product will and will not do — which cases appear, which are suppressed, and what the send button refuses. Not a badge on a screen. A refusal.

Every duty, in full

Rent collection is the process with the most statutory contact points and the least tolerance for getting one of them wrong. It runs every day, at volume, largely by automation, against the tenants least able to absorb a mistake.

One moratorium missed, one letter sent to somebody who can only receive post — and the finding is about the organisation, not the officer who pressed send.

Enforcement, not reporting

Six duties, and what each one actually does

The distinction that matters in this category: a duty that produces a report is a duty somebody still has to act on. A duty wired into the product is one that holds when nobody is watching the report.

Statutory holds, enforced three layers deep

Debt Respite Scheme Regulations 2020 · Insolvency Act 1986

Breathing Space, mental-health crisis moratoria, Debt Relief Orders, bankruptcy and live complaints are enforced at the rules, at the automation, and at the send endpoint — three separate layers.

Why three: a hold applied only at the queue is a hold somebody bypasses by opening the account directly. The send endpoint is the last gate before a message leaves the building, and it checks again.

The six-year clock as a live suppression

Limitation Act 1980

Not a quarterly report. The account stops being chased, and the remaining exposure is ordered by what lapses first, with the date each clock runs from and what would restart it.

One deliberate exception: the clock keeps reporting inside a moratorium, because a statutory deadline does not pause for one and a silent clock is how a debt expires unnoticed.

An unread access need refuses the send

Equality Act 2010 s.20 · Pre-Action Protocol

Where a resident carries a recorded communication requirement, the email does not go until somebody confirms they have read it — and the confirmation stores what they read, so it is evidence rather than a tick.

It stops counting if the needs change. A confirmation against an older version of the record does not stand in for one made against the current one.

Protocol evidence with no bare ticks

Pre-Action Protocol for Possession Claims by Social Landlords

Each requirement evidenced or not, per current tenancy in arrears, and which requirement is the gap — across the book rather than per case after somebody opens it.

Compliance is judged at the point the claim is issued, so evidence assembled afterwards is worth very little. That is the whole reason this is a standing figure rather than a pre-court checklist.

Two Equality Act figures, kept apart

Equality Act 2010 s.149 · Article 8 proportionality

Where a protected characteristic is recorded, and where the assessment and the adjustment offer both exist. Collapsing those two into one number is how a public sector equality duty gets reported as discharged when it has not been.

A landlord that thought carefully and wrote nothing down stands where one that never looked stands. The second figure is the one that survives being tested.

The tenancy regime decides the route before the balance does

Housing Act 1985 s.83 · Housing Act 1988 Sch 2

The mandatory arrears ground does not exist against a secure tenant, so it is not offered as an option against one. Where the regime is not recorded, the product says the grounds cannot be stated rather than guessing one.

Refusing to answer is a feature here. A system that guesses a tenancy regime produces a possession route that reads as authoritative and is wrong.

Transparency

Explaining a decision about a tenant

The question is getting harder to answer across the sector, and a model whose weightings are commercially confidential does not answer it.

What you cannot say

  • “The system prioritised her, and the weightings are the vendor’s.”
  • “The threshold has always been 14 days” — with no record of who set it, when, or what it was before.
  • “We took her circumstances into account”, evidenced by a case note that does not say what was taken into account.

What is on the record

  • The rule that raised the case, in readable terms, with the threshold it crossed.
  • Who changed that threshold, from what to what, when, and how many cases it moved.
  • The communication needs read before contact, the version read, and what was done differently.
  • Every suppression, with the statute that caused it.

Where this stops

What it does not do

This is the section to read first. A compliance function is the one buyer who should be more interested in the limits than the claims.

We never say “compliant”

The Regulator of Social Housing regulates landlords, not software. No product can make you compliant, and a vendor who says otherwise has written you a sentence you would have to defend after an adverse finding.

It evidences; it does not certify

It shows, per tenancy, whether the evidence exists. Whether that evidence is sufficient in a given case is for your solicitor and ultimately a court. The product does not offer an opinion on that.

It enforces what is recorded

A moratorium nobody registered cannot suppress an account. An access need held in an officer’s memory cannot refuse a send. The product enforces your record rigorously; it does not know what is missing from it.

Thirteen duties, and two places it stops short

The full list is published, including the two points where this deliberately does not go further, and the things it evidences without certifying.

Read the full list →

The rest of the committee

The same product, four other arguments

Written separately because these are genuinely different questions, not the same pitch with the job title swapped.

Start with the book you already have

One patch, one team, your own data loaded. Tell us your account volumes and which housing management system you run, and we will put a number to it.

Sign in