Sales and purchaser records for developers
Unit inventory and bookings with availability that reflects what has been taken, one record per purchaser and unit, and end-financing tracked to disbursement. Bought once and owned outright.
- One purchaser, one unit
- From the booking form to vacant possession.
- What has been taken
- Availability on one position, not a whiteboard.
- Financing per purchaser
- From application to disbursement.
- Owned outright
- Purchaser records stay in the developer's own environment.
From the booking form to handover
Four features on one system, for the sales gallery, sales administration, purchasers, and management and finance.
- Sales and bookingsUnit inventory, bookings and availability on one position.
- Purchaser recordsThe booking, the agreement, the financing and every communication.
- Financing and loan trackingEnd-financing per purchaser, and the units at risk of not completing.
- Through to handoverThe record asasii ledger bills and asasii facilities hands over.
A sale on asasii property
From the phase launch to vacant possession, on one purchaser and one unit record.
- Launch
A phase goes on sale
The phase is brought on as it launches, with its units in the inventory. A phase already selling keeps running on what it has until it is ready to move.
- Launch day
A booking in the gallery
The booking form creates one purchaser and one unit record, and the unit shows as taken.
- End of day
No whiteboard to correct
Availability already reflects what was taken, because every agent sold from the same position.
- Signing
The sale and purchase agreement
It goes on the same purchaser and unit record as the booking.
- Financing
The end-financing application
Tracked per purchaser through offer and acceptance, so sales and credit control see which units are at risk of not completing.
- Each stage
A progressive claim
asasii ledger raises it from the certified stage and the schedule the agreement sets, against the same purchaser and unit.
- Any day
A disbursement is chased
The financing position is on the record, so chasing it stops depending on who last spoke to the bank.
- Handover
Vacant possession
Key collection and defects run in asasii facilities on the same record, and purchaser details carry across rather than being re-entered.
Who it's for
Four groups of people, working from the same purchaser and unit records.
A licence, not a system left behind at completion
The developer buys the system and keeps every record it produces. idataraya is paid to customise, install and maintain it, phase after phase.
| Topic | A separate system for each stage | asasii property |
|---|---|---|
| The purchaser | A new record in billing, the defect list and the service charge account | One purchaser and one unit, from the booking form onwards |
| Availability | A whiteboard corrected at the end of the day | What has actually been taken, on one position |
| Financing | Depends on who last spoke to the bank | Tracked per purchaser, from application to disbursement |
| At vacant possession | The management office starts from scratch | Purchaser details carry across, not re-entered |
| After completion | Handed over and left unmaintained | Owned by the developer, maintained by idataraya under a yearly agreement |
Security and Malaysian compliance
The questions management, finance and audit ask, answered in the system.
Security and data overview- PDPA 2010
- Purchaser data stay in the developer's own environment.
- Purchaser history
- The booking, the agreement, the financing position and every communication, on one record.
- Single sign-on and MFA
- On every console, with the developer's own identity provider.
- Roles
- Each role is scoped by development and function.
- Audit trail
- Every action recorded with the previous value and kept for seven years.
- The developer's records
- Held in the developer's own cloud account or data centre.
Installed and maintained by idataraya
asasii property runs in the developer's own cloud account or data centre. idataraya installs it and keeps it current, and the developer's team holds the keys, the backups and the data.
- Phases brought on as they launch
- Releases, patches and incident response
- Response times by severity, measured monthly
- Monitoring from within the developer's environment
Questions developers ask
About sales, purchasers, handover and the agreement.
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.
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.
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.