Olympus Docs

Appearance

Qube Sync ​

Deep dive

How Olympus keeps Qube, the accounting and property-management system of record, in step with what happens in Portal. This is where "why did that show up in Qube?" and "why hasn't it synced?" are answered.

Purpose: Keep finance and tenancy data consistent between Olympus and Qube without anyone re-keying it.

Owner: Platform / development and finance; (add the named subject-matter expert here).

At a glance ​

Writes (event-driven, immediate) ​

When staff act in Portal, events push data into Qube straight away:

  • Approve a deal: syncs the customer, unit, deposit, monthly payments and tenancy documents.
  • Create or update a customer: syncs the customer.
  • Raise a charge or transaction: pushes it to Qube. Raising a transaction also raises a payment notification to the resident.
  • Notes: created, updated and deleted against the tenancy.

Reads (scheduled) ​

Olympus also pulls from Qube on a schedule (see Automation): customer data and unit data hourly, tenancy data every 15 minutes, and lease end dates daily. This is what keeps tenant status and dates current between writes.

Safety & failure handling ​

  • A single master switch can turn Qube writes off across the whole platform.
  • Write failures are logged, not thrown, so a Qube problem never breaks the staff member's action in Portal. That also means a silent Qube failure needs checking in the logs, not the UI.

Tenant status ​

The tenant status values that gate so much behaviour (Resident, Renewing, On Notice, Vacating, Previous, Withdrawn and so on) come from Qube. See Statuses & lifecycles.