Integrations
Compliance status, where your team already works.
The point of an integration is that nobody has to remember to check a second system. Contractor compliance status is written back into your management platform, so it is visible at the moment someone is choosing who to engage.
Looking for the government registries we verify licences against? Those are data sources rather than software integrations — they are listed, with their status, in the sources table.
What moves
What flows in each direction
Into TradeVerify
Your contractor and supplier records — names, trade types, contact details. That is what builds the register, and it is why nobody has to re-key a contractor list.
Back into your platform
Compliance data per contractor, the expiry dates behind it, and the time of the last check. Status changes flow through as they happen, so a lapsed licence shows up where the work order gets raised.
Platforms
The strata and property management software we connect to today
Automated
| Platform | What it does | Status |
|---|---|---|
| Urbanise Strata | Two-way. Supplier records flow in, and licence and insurance status is written back against the supplier in Urbanise. | Live |
File Transfer
| Platform | What it does | Status |
|---|---|---|
| MRI StrataMaster | Licence and Insurance data records are updated upon a manual file transfer process update occurring, driven by the end user | Live |
| StrataMax | Licence and Insurance data records are updated upon a manual file transfer process update occurring, driven by the end user | Live |
| StrataSphere | Licence and Insurance data records are updated upon a manual file transfer process update occurring, driven by the end user | Live |
In practice
What a two-way sync has to get right.
Moving records between two systems is straightforward until they disagree. The value is in what happens then.
- Matched on identity, not on spelling
- An incoming supplier is matched to a contractor by ABN first, and only then by registered business name. Two spellings of the same business do not become two contractors.
- Nothing is silently dropped
- A supplier with no ABN, an ABN that does not check out, or no contact address cannot be matched confidently — so it goes to a review queue, sorted by the reason it could not be resolved. It is not guessed at and it is not discarded.
- Your trade names, mapped once
- The licence and trade types in your platform are mapped across to ours, so the requirements engine works from your vocabulary. If your platform retires a type, the mapping is flagged rather than quietly losing the trade behind it.
What flows back is the compliance status, the expiry dates behind it and the licence and insurance detail — so the supplier record your team sees when they raise a work order is the same verified record we hold. How the verification itself works.
Not listed?
If your platform isn't here
Three options, and none of them is waiting for a roadmap.
Ask us about a direct connection
If you run your own management system, talk to us about connecting it directly. We will tell you honestly whether it is worth building.
File transfer sync
Not every management system has an API. Where one doesn't, contractor data can still move by scheduled file transfer — including from several older platforms still in common use across Australian strata. Ask us about yours.
Use it standalone
The service works without any integration. You lose the write-back into your system, not the verification, the chasing or the audit trail.
If there is a platform you would need us to support, tell us which one. We would rather hear it from the firm that needs it than guess from a market map.
See it against your own stack.
A demo covers what the integration writes back, and what it would take to switch it on for your firm.