Reapit integration

Property licensing compliance inside Reapit.

Open the Licensing tab on a property in Reapit and you get Kamma's licensing interface in place of the standard form: the compliance position, the licence required, the occupancy that decides it, and the actions outstanding. What you record saves back into Reapit, which stays the system of record.

Reapit logowith Kamma
What you get

Kamma and Reapit, together

Your team never leaves Reapit. Kamma's licensing interface opens from the Licensing tab on a property, or from the Kamma app while you have that property open.
What you record saves back into Reapit for the fields Reapit supports, so Reapit remains the system of record and your data stays in it.
Kamma works out the licence required from the occupancy and household counts Reapit already holds, and keeps the position current as schemes change.
How it works

How Kamma connects to Reapit

Three steps, and none of them change your CRM.

1

Install Kamma from the Reapit AppMarket

Kamma is a listed app in the Reapit AppMarket, so it installs through the route Reapit already gives you for adding software. Your Reapit administrator authorises it once.

2

Open the Licensing tab on any property

Kamma's licensing interface loads in place of Reapit's standard licensing form, either from the Licensing tab on a property or from the Kamma app while you have that property open. Your team does not leave Reapit.

3

Work in Reapit, and Kamma saves back into it

Kamma determines what each property needs, and the information you record is saved back into Reapit for the fields Reapit supports. Reapit stays the system of record and your data stays in it.

The data

What Kamma reads and writes in Reapit

Kamma reads the fields a licensing determination depends on, and saves what you record back into the fields Reapit supports.

Field
Why Kamma needs it
Property address
Resolves the property to its local authority and to the licensing schemes in force at that location.
Property type
Distinguishes a self-contained unit from a shared house, which decides whether HMO licensing is in scope at all.
Occupancy and households
How many people live there and how many households they form. This is what decides whether a property is a licensable HMO.
Tenancy dates
Establishes when the letting began and therefore which scheme rules applied, and when a licence renewal falls due.
Inside Reapit

What the Kamma licensing interface covers

The interface is organised into tabs, each grouping the licensing information that belongs together.

Compliance overview

The property's current position: compliance status, the licence type required, the action outstanding, and every licensing scheme that applies to that address.

Property information

The attributes that change the answer: whether the property is an s257 HMO, whether it sits above commercial premises, whether it falls in an Article 4 direction area, and any restrictions. Kamma fills in the Article 4 position for you.

Tenancy information

Occupant and household counts, calculated from the current tenants in Reapit. These decide which licence is required and whether the property stays inside its licence conditions. A tenancy being arranged shows the licence it will need.

Licence information

Application details, granted licence details and licence documents. Documents open in a preview without leaving the app, and download where the file type cannot be previewed.

Vacant properties

Mark a property vacant to pause its licence requirement while it is empty, without losing the tenancy data. The status stays in step with Kamma Suite in both directions.

Exemptions and overrides

Record a genuine exemption, such as a landlord selling, or override the licence requirement Kamma has determined. Available on request.

Kamma fills in the compliance status, whether a licence is required and which type, and the Article 4 position, so those fields are not left to whoever last edited the record. Compliance tasks, which track the works and documents a licence condition requires and flag a property non-compliant when one falls overdue, are also available on request.

Kamma Suite

What the Reapit integration unlocks in Kamma Suite

Reapit gives you both halves. Inside Reapit you get the Kamma licensing interface in place of the standard form, and your Reapit portfolio also syncs into Kamma Suite, so the same property licensing position is available across every property at once and not only on the record you have open. What you see depends on your Suite tier.

Compliance monitoring across the whole portfolio

Every property that syncs from Reapit is monitored against the schemes in force where it sits. Kamma flags what needs a licence, what is in breach, what is expiring, and what will need a licence when an upcoming scheme starts.

A dashboard that says what to do next

Compliance status and the priority actions summarised in one view, so the team knows where the time is best spent rather than working down a list of everything.

Email alerts without logging in

A portfolio compliance snapshot by email, so whoever owns lettings compliance sees the position and the priority actions without opening Kamma at all.

Schemes before they start

Kamma tracks newly announced schemes and works out which of your properties will need a licence when one begins. That is the window in which applications are calm and cheap rather than urgent.

Filters that match how the work is actually done

Filter your Reapit portfolio by compliance status, licence type required, licence expiry, local authority, branch, the property manager responsible, or properties caught by an upcoming scheme. Action Required surfaces applications in progress and incomplete or unrecognised addresses.

Article 4 and HMO planning constraints

See whether a property sits in an Article 4 direction area, where permitted development rights are restricted and planning permission may be needed before a conversion to an HMO. London properties are also flagged where room sizes may fall below the minimum standards.

Licence conditions tracked as work, not paperwork

Fire safety works, electrical inspections and the other conditions a council attaches to a licence can be logged and tracked to completion, with a property marked non-compliant if a task falls overdue.

Tenancy changes that change the answer

Concurrent tenancies at one property are aggregated so occupants and households produce the correct licence requirement, which is what room-by-room HMO letting needs. More than one licence can sit against a property, so a renewal can be tracked while the existing licence stays in place.

An audit trail you can show a council

A full history of changes to a property and its licensing information, with the timestamp and the person who made each change.

350+licensing schemes monitored daily
4,200+letting agents using Kamma
30 minutestypical time to your first result
13CRM integrations

Getting started with Kamma and Reapit

Your onboarding contact sets the Reapit connection up with your operations lead and walks the team through it. Most agencies are looking at their own portfolio position within 30 minutes.

FAQ

Reapit and Kamma, common questions

Is Kamma available in the Reapit AppMarket?

Yes. Kamma is a listed app in the Reapit AppMarket, which is how it is installed. Your Reapit administrator authorises it once, and there is no separate procurement route to go through.

Does Kamma write into Reapit, or only read from it?

Both. Reapit is the one CRM where Kamma replaces the vendor's own licensing form, so the licensing information you record saves back into Reapit for the fields Reapit supports. Reapit stays the system of record and your data stays in it. For most other CRMs Kamma reads the fields it needs and displays its findings alongside the record instead.

What does Kamma fill in on its own?

The compliance status, whether a licence is required and which type, and whether the property falls in an Article 4 direction area. Occupant and household counts are calculated from the tenants already in Reapit. Those fields are not editable by hand, which is the point: they follow the rules and the data rather than someone's recollection.

How is this different from Reapit's standard licensing form?

The standard form is a place to record what somebody already worked out. Kamma works it out: it resolves the address to its local authority, applies the schemes in force there, reads the occupancy, and tells you the licence required and what is outstanding. It also lets Kamma add licensing features faster than the default form allows.

What is property licensing, and why does it sit with the agent?

Most UK councils require a licence to let certain properties, either because the property is a house in multiple occupation or because the council has designated an additional or selective licensing scheme covering the area. Letting an unlicensed property that needs a licence can attract a civil penalty of up to 30,000 pounds and a rent repayment order of up to twelve months' rent. Agents are usually the party expected to know.

What does the integration cost?

CRM connectivity is part of Kamma rather than a separately priced integration. What you pay depends on portfolio size and the tier you need. The pricing page carries the current tiers.

See Kamma against your own Reapit portfolio.

A 20-minute demo, run on your real addresses, showing which of your properties need a licence today.

Check your property now

Let us know where to send your report

Check your property now

Let us know where to send your report