A Letting-Agent Portal: Deposit Received, Protected and Explained to the Tenant Are Separate Tasks

A letting-agent portal should not mark a tenancy deposit complete merely because the payment arrived. Before commissioning it, separate receipt of money, protection through the applicable scheme and provision of the required information. Staff need to know which task remains open, not simply whether the deposit balance matches the expected amount.

This guide uses current GOV.UK tenancy-deposit guidance as an English residential-letting example. It is not advice on whether a particular tenancy is covered, which scheme to choose or how to resolve a dispute. Have an appropriately qualified adviser establish the rules and responsibilities for your actual tenancies before turning them into software controls.

Establish the kind of money and tenancy first

A fictional agency receives money while arranging a home letting. The app should record what the payment is for and which tenancy it relates to. Do not assume that every incoming amount labelled deposit has the same purpose or protection treatment.

The GOV.UK tenancy deposit protection overview describes protection for deposits associated with assured periodic tenancies and says these replaced assured shorthold tenancies on 1 May 2026. It separately discusses holding deposits and deposits paid by third parties, and directs readers to separate schemes in Scotland and Northern Ireland.

For your brief, have the reviewer confirm applicability using the actual tenancy and current jurisdiction. A translated interface does not make the English arrangement an Austrian, German or Arabic-market rule. Likewise, an old tenancy-type dropdown should not silently decide the applicable process after a legal change.

Track the actual receipt, not only the expected due date

The overview states that the landlord or letting agent must put the deposit in the scheme within 30 days of receiving it. Its information page also uses receipt as the starting point for the information obligation. Those are reasons to make the evidenced receipt date visible to the responsible staff.

Ask what event your financial process treats as receipt, who verifies that evidence and how corrections are reviewed. A date when the tenant was asked to pay is not automatically the date the money arrived. Do not let a future expected payment postpone a real recorded receipt without review.

These are proposed application controls, not a complete legal deadline calculator. Your adviser must resolve the actual timing rules and exceptions. The app should show the basis of its deadline and any unresolved date question, rather than manufacture a reassuring countdown from whichever date happens to be populated.

A prepared scheme submission is not confirmed protection

Keep preparation, submission and external confirmation distinguishable where those stages exist in your chosen process. Record the actual scheme, tenancy, amount and reference supported by the evidence. Do not create a protection certificate or scheme reference locally and present it as an external result.

If an integration or manual submission has an uncertain outcome, assign reconciliation before another submission. Staff should be able to check the scheme's record through the authorised process rather than repeatedly sending the same case because the local screen lacks confirmation.

The official overview does not establish that your custom app can register deposits automatically. Choose an existing supported scheme workflow first, then verify the actual integration permissions and evidence available. A copied PDF alone is not a demonstrated live connection.

Keep the tenant-information task independently visible

The official information landlords must give tenants page lists information to provide within 30 days of receipt. It includes the property address, deposit amount, protection arrangements, scheme and dispute-service contacts, landlord or agency contacts, and details of a third party who paid the deposit. It also covers return, deductions and what to do if the landlord cannot be reached or a dispute arises.

Have the responsible adviser approve the actual information package and delivery process. Track its version, intended recipients and evidence of the action completed. Scheme protection and providing information are separate tasks; one status must not close the other without its own basis.

An email prepared locally is not evidence that the approved package was sent. Conversely, do not label an unavailable delivery or reading receipt as a confirmed failure. Display only the events your process can support and give uncertain cases a usable next action.

Accept a deposit with an unfinished obligation

Use fictional tenancies and test payments. Demonstrate received money with scheme confirmation still missing, confirmed protection with the information task still open, a third-party payer and an incorrectly recorded receipt date that needs review. Have the adviser specify the expected outcome for each.

Then change an information package after an earlier action and verify that the old evidence remains attached to the version actually used. The portal should not declare a tenancy universally compliant from these records or decide deposit deductions itself.

Bring blank examples to a letting-workflow application discussion. First assess the tools and scheme processes you already use. The useful feature is an explainable record of separate obligations and their evidence, not another green badge beside a received payment.