Customer work, connected.

Help & supportMyAccount
Tenancy Compliance & Compliance Records · How-to guide

Use deposit protection workflows

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to manage deposit receipt, scheme protection, prescribed information, acknowledgement and end-of-tenancy status.

Audience: Compliance administrators and authorised property staffPermission: Compliance Monitor: ViewModule v1.0.0
Jump to steps
Where to goTenancy Compliance → Deposit Protection Workflows
Before you startConfirm the correct property, tenant, record and evidence before changing a compliance status.

What this guide helps you do

Manage deposit receipt, scheme protection, prescribed information, acknowledgement and end-of-tenancy status. The supplied Compliance Monitor module keeps live operational records, source documents, generated evidence and audit history connected through shared section keys, compliance types and linked-entity references.

How it works

This feature sits inside the Compliance Monitor lifecycle. Source evidence is attached to a linked entity, reviewed by authorised staff and converted into an approved record only when the required fields and evidence are complete.

Follow these steps

  1. Go to Deposit Protection Workflows.
  2. Select the linked property and review recent deposit activity.
  3. Create or open the deposit intake.
  4. Complete the protection and prescribed-information fields.
  5. Use the return or deduction workflow only when the tenancy reaches the relevant stage.

Settings to check

Deposit received dateThe date funds were received.
Deposit amountThe protected sum recorded by the workflow.
Scheme usedThe deposit scheme or protection route.
Protection and service datesProtection date and prescribed-information served date.

Record, audit and evidence checks

Reopen the relevant workspace after saving. Confirm the intake ID or record reference, linked entity, status, dates, evidence list, generated PDF and any notification or audit entry. Where the module offers separate source evidence and system PDF buttons, review both rather than assuming they contain the same information.

Check it worked

The resulting status, evidence, PDF, notification or audit event remains available through the relevant Compliance Monitor register. A successful browser message confirms that the request was handled; the register and audit history confirm what was actually retained.

Common mistakes to avoid

  • Verify the linked property, tenant, company or record ID before uploading, approving, sending, exporting or deleting.
  • Do not treat OCR, parsing, confidence or a success alert as a substitute for human evidence review.
  • Verify the saved record and audit history after every state-changing action.
  • Keep original uploaded evidence distinct from system-generated PDFs and notification evidence.
  • Use least privilege and avoid administrator-only actions unless the task genuinely requires them.
  • This module supports operational compliance records; it does not replace professional legal, regulatory or safety advice.
Compliance and data safetyUse the module as an operational evidence and workflow tool. Verify legal, safety, tax, licensing, data-protection and regulatory decisions with the organisation’s authorised professional process.
Browse connected topics:tenancy compliancecompliance records

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page