3 min read · Planning guide
Planning & implementation decisions
What should a property-system procurement worksheet capture?
Start with a small, representative portfolio containing a lease change, a partial payment and an unmatched receipt. Require the supplier to explain each account balance and restrict access across properties. Keep property operations separate from public listing requirements.
| Area | Demonstration | Acceptance record |
|---|---|---|
| Portfolio | Distinct owner, unit and lease identifiers | Duplicate and missing-record report |
| Account history | Charge, partial receipt and correction | Explainable balance and approval history |
| Access | Property-scoped staff permissions | Attempted cross-property access result |
| Exit and migration | Sample export and trial import | Reconciled totals and documented exclusions |
- Step 1 →
Register
Identify property, unit and active lease.
- Step 2 →
Bill and receive
Link charges and confirmed payments to the account.
- Step 3
Review
Explain balances and resolve unmatched receipts.
Exception & recovery path
Unknown lease reference → unmatched receipt review. Lease changes preserve prior effective dates and approvals.
How should you test lease and payment history?
Ask the vendor to create a charge, allocate a partial receipt, change a lease under authorization and explain the resulting balance. The example is a procurement test specification, not a claim that a particular platform has passed it.
When does an existing product fit better than custom software?
Compare the demonstrated lease, billing, reporting and approval workflows against your actual operating model. A dedicated product may fit standard operations; institutional approvals or unusual asset structures may require integration or custom work.
What should migration acceptance include?
Map owner, property, unit, occupant and lease identities. Reconcile opening balances and deposits to approved source records; record duplicate units, missing leases and unmatched receipts separately. Confirm export formats and operational responsibility for corrections.
Take this into your project discussion
- Portfolio sample / owners / unit identifiers: ____________________
- Lease and charge rules / authorized approver: ____________________
- Payment allocation / exceptions / evidence: ____________________
- Opening balances / deposits / migration differences: ____________________
- Role tests / exports / support terms: ____________________
Planning content reviewed . Confirm current provider requirements and project-specific assumptions before implementation.
1. Map the Portfolio
Document property owners, sites, buildings, units, categories and the teams that manage them. Identify unique property and occupant references. Where the portfolio spans departments or institutions, decide who can access and change each record.
2. Define Accounts, Charges and Billing Rules
List rent, service charges, deposits, utilities and any other lawful fees. Establish how charges are calculated, their due dates, how adjustments are approved and when notices are generated. Document exceptions instead of embedding one rigid rule for every property.
3. Connect Payment Confirmation to Records
A payment should be associated with the correct lease, unit or account. Identify which system issues references, how supported payment providers confirm transactions, who reviews unmatched receipts and how adjustments are audited.
4. Make Lease and Document Processes Clear
Plan how agreements, renewals, changes, supporting documents and approval histories are stored. Determine retention responsibilities and which users may view confidential contractual details.
5. Define Reporting by Decision-Maker
Property managers need occupancy and maintenance context; finance teams need invoicing, collection and arrears views; leadership may need portfolio summaries. Agree exact reporting formats and reconciliation boundaries with the users.
6. Compare Product and Custom Implementation
Commercial landlords and agencies may find a dedicated property platform suitable. Institutions with different approvals, revenue policies or asset registers may need specialized development. Compare actual demonstrations, integrations, data migration, access control and maintenance cost before choosing.
Frequently asked questions
Can one system handle several property locations and owners?
Yes, that can be included when the data model and user permissions are designed accordingly.
Is this guide the SpotLetting product specification?
No. SpotLetting has its own dedicated website; this guide is intended for specialized institutional requirements.