IPEX
Strengthening existing legal protections
The suite of industry-standard rights and responsibilities (‘stat decs’ for confirming subcontractors have been paid, ‘step in’ rights) have proven to be largely ineffective in preventing construction industry payment problems. There are countless instances where a builder has entered administration, leaving behind subcontractors and suppliers that are owed large sums of money across multiple progress claims.
Without oversight or control over how progress payments are being distributed by the builder, developers are forced to accept builder statutory declarations at face value and continue to make payments.
Often, by the time a developer has sufficient information to confirm that subcontractors have not been paid, it’s too late to act on or make effective use of their legal protections.

Using IPEX
Benefits for developer clients
About IPEX
IPEX combines a range of practical controls with existing legal protections to greatly reduce the risk & impact of builder insolvency for developers. The IPEX payment platform ‘ring fences’ project funds paid to the builder; progress payments can be used only to pay approved subcontractors & suppliers linked to that specific project. Developers can then verify who has been paid & when rather than relying on solely a statutory declaration and, in the event that the builder has failed to pay those linked to the previous claim, the developer can seek to have this remedied before the next claim is approved. In the case of more serious/repeated breaches, developers have access to the right information at the right time to act on existing protective clauses i.e. ‘step in’.
Should a payment default event occur, IPEX helps to minimise the impact to the developer via a range of practical controls that complement existing legal protections. Progress payments already made to the builder via IPEX have either been distributed to approved subcontractors & suppliers or, remain in the account – the funds can’t be siphoned off to other projects/accounts in the period leading up to the appointment of administrators. In addition, the developer receives full visibility of all previous transactions, removing much of the work associated with substantiating creditor claims & establishing their exact position on the project.
IPEX process
- IPEX provisions are included in the head contract (or any deed of variation). Standard builder obligations re: payment of subcontractors remain unchanged.
- There is no change to subcontractor/builder claim process and no impact on the builders’ payment; builders can access their own entitlements immediately (only subcontractors and suppliers entitlements are off limits). Importantly, IPEX provides developers with this additional visibility over who has been paid and when, without requiring a builder to share commercially sensitive information including their margin or subcontract values.
- IPEX does not change the agreement between a developer and their builder, it just provides a range of practical controls to ensure they are always operating within it.
New project vs distressed project application
-
Protect against future builders' cashflow issues
Prevention from day 1 -
Guide 'troubled' projects to completion safely
Mid-project implementation
- Guard against the potential impact of other, less-feasible developments linked to your builder
- Additional protection when working with a builder for the first time or builder is ‘stepping up’ a level
- Provide lender comfort should builder due diligence has raised minor red flags
- Provide lender comfort on developer-builder projects
- ‘Controlled’ payments to assist your builder with funding supplier deposits
- ‘Ring-fence’ additional payments outside of the contract to ensure they’re spent on your project
- Move forward with the builder despite substantiated instances of non/delayed payment of subcontractors or suppliers
Market adoption
There are 2 levels of transparency available to developers – standard vs open book.
Most developers are happy for their builder to keep values confidential and are just seeking to verify who has been paid and when – the level of transparency provided by our standard portal view should not be of concern to any builder any most (~80%) agreements are implemented at this level initially. However, our contract templates contain clauses that allow developers to escalate visibility levels should a ‘payment default’ event occur. Of course, no matter what transparency level is agreed, the same restrictions apply to how builders can use project funds.
Typically, projects operating under a cost-plus agreement or ‘distressed’ projects would run under the open book visibility setting.
There are various other settings, controls and alerts that can be customised to manage specific situations and processes. These additional protections can be scaled up or down on a project-by-project basis in direct relation to level of perceived risk to the developer.
Testimonials
What our customer say

