Skip to content

Frequently asked questions

The questions developers, sales teams and finance ask about bookings, purchaser records, financing and handover, before a proposal.

Sales and bookings

How does availability stay current in the sales gallery?

Availability reflects what has actually been taken. Every agent works from one position rather than a whiteboard that is corrected at the end of the day, and a booking taken in the gallery shows the unit as taken.

Do we have to stop selling to change systems?

No. Phases are brought on as they launch, and a phase already selling keeps running on what it has until it is ready to move. The rollout follows the project's own calendar.

Purchasers and financing

What does the purchaser record hold?

One record per purchaser and per unit, carrying the booking, the sale and purchase agreement, the financing position and every communication since. The person who bought in the gallery is the same record that receives a defect response two years later, so purchasers stop being asked for information the developer already holds.

How is end-financing tracked?

Per purchaser, from application through offer, acceptance and disbursement. Sales and credit control see which units are at risk of not completing, and chasing a disbursement stops depending on who last spoke to the bank.

Can purchasers see their own statements and defects?

Yes, in the purchaser and resident portal in asasii ledger: statements, payment, defect submission and status, facility booking and announcements, for the purchaser before handover and the resident after it. The portal works from the same purchaser and unit as the record in asasii property.

Handover and the agreement

What happens to the purchaser record at vacant possession?

It carries across rather than being re-entered. Vacant possession, key collection and the defect liability period run in asasii facilities, and the service charge account in asasii ledger, on the same purchaser and unit. The management office starts with the developer's records instead of an empty system.

Where does it run, and can our other systems talk to it?

In the developer's own cloud account or data centre. idataraya installs it, hardens it and keeps it current, and the developer's team holds the keys, the backups and the data. It works beside asasii ledger, asasii procure and asasii facilities, and the accounting package and banking arrangements already in use stay where they are. A documented API lets the developer's other systems or a third party read units, bookings and purchaser records.

What does the yearly agreement cover?

Software updates, the customisations made for you, monitoring, severity-based response and restoration targets, and the changes needed as phases launch and completed buildings move into management. Hosting stays with you. It is a fee, not a subscription.

Still have a question?

Send it with the phases and the launch calendar, and an engineer replies within one working day.