Before you begin
- Choose a concrete question, such as overdue rent, shared-expense collection, expiring tenancies or overdue repairs.
- Confirm the company, period, property and responsible-person scope before comparing figures.
- Keep rent and expense ledgers separate, and treat seeded amounts and external events as fictional prototype data.
The illustrations use fictional demonstration records. Follow your organisation’s review and approval process before issuing changes.
Move from an overall figure to the record that needs attention without losing the reason for the review.
What the workflow coordinates
Reports assemble portfolio metrics and action lists. Audit log brings dated events and related record references together, with entries presented as non-editable. Export and external-event services are simulated in the demonstration.
What people review
Reviewers define scope, reconcile conflicting totals, inspect underlying records and decide the corrective action; a chart or seeded audit event does not make that decision.
Set the report scope before reading totals
Open Reports and choose the building, unit, tenancy, tenancy status, responsible person and available 3/6/12-month period. Keep the chosen scope visible when discussing a number so a portfolio total is not confused with a single building or ledger.
The property, tenancy, responsibility and period filters match the question being investigated.
The property, tenancy, responsibility and period filters match the question being investigated.
Compare summary cards with the detail
Review occupancy, rent collected, common expenses collected and combined arrears, then compare the monthly and overdue-invoice tables. Preserve the Rent versus Common expenses labels, because combined arrears and rent-only arrears are different measures.
The figure can be identified by metric, ledger scope and reporting period.
The figure can be identified by metric, ledger scope and reporting period.
Follow an actionable exception
Use the Needs action entries or Open repairs/Open costs links to inspect the underlying record rather than acting on a chart alone. Review the record’s actual status, dates, assignee and financial context before choosing the next operational step.
A report exception has been connected to a specific record and a practical next action.
A report exception has been connected to a specific record and a practical next action.
Search the related activity
Open Audit log and search by the record reference or relevant text, then narrow by person, type, area and dates. Read When, Who, What, Area and Records together to separate a dated action from your interpretation of why it occurred.
The activity being discussed has a specific actor, timestamp and related record reference.
The activity being discussed has a specific actor, timestamp and related record reference.
Respect the non-editable audit design
The audit screen says entries cannot be edited or deleted, so use the originating workflow to correct a business record instead of trying to rewrite history. Treat that as interface intent until production event coverage, persistence and tamper resistance have been verified.
A correction is directed to its business workflow, while the original activity reference remains available for review.
A correction is directed to its business workflow, while the original activity reference remains available for review.
Use export and service-status controls with context
This standalone configuration/integration screen is not exposed in the current company or account settings navigation. Its prototype image is retired. Use the adjacent current record or contact the team to confirm this workflow’s availability.
System health and service simulations
This standalone configuration/integration screen is not exposed in the current company or account settings navigation. Its prototype image is retired.
Confirm current availability before attempting this stage.
What you should have at the end
The review links a defined metric or exception to its source record and relevant activity, with limits on exports and service evidence made explicit.
Demonstration notes and availability
- Reviewed against the official demo at demo.estatereal.io. Screenshots are native 3× captures in English/light mode. Preset records and enabled functions can change.
- This review followed navigation, record tabs and unsaved forms. It did not submit payments, signatures, invitations, messages or irreversible record changes.
- Current demo limits: This standalone configuration/integration screen is not exposed in the current company or account settings navigation. Its prototype image is retired.
Useful answers
Why can amounts differ between views?+
Check period, filters and ledger scope. Reports distinguishes rent and common expenses and links to the underlying tenancy or repair.
Which export controls are exposed?+
Reports exposes CSV, Excel and PDF controls, while Audit log exposes CSV. File generation was not exercised as part of the screenshot capture.
Does an activity entry prove an external service completed?+
Read the individual event and any simulated-service label. A recorded workflow event is not independent proof of delivery, a payment settlement or a physical access action.