PayLocker for financiers & lenders · Australia
Funding aligned to verified project progress.
PayLocker gives lenders permissioned visibility of how project funds are allocated and released against approved obligations — while every credit decision stays with you.
A construction lender's information is strongest at the moment of approval and weakest immediately afterwards. A drawdown is assessed against stage completion, valuation, inspection, borrower certification and a builder invoice. Once the funds are released, visibility of who was actually paid — and whether obligations behind that completed stage remain outstanding — can become fragmented across several parties and systems.
PayLocker is a construction payment integrity platform. Project funds are held in a project-specific account and released through a controlled process aligned to approved progress and verified claims. Where the project's participants agree to it, lenders can be given permissioned visibility of that payment activity.
§ 02 — The gap between approval and application
Construction lending doesn't end when the drawdown is approved.
Providing the funds is one part of the relationship. The other is what happens to the money afterwards, as it moves through a chain of parties the lender has no direct contractual relationship with.
Funds move from the financier to the developer or borrower, to the builder, then outward to contractors, trades and suppliers. Every step in that chain is a legitimate part of building. But each one also adds a party, a system and a record — and the further money travels from the facility, the harder it becomes to establish where it went and what it settled.
That can create several practical difficulties:
- Fragmented payment information. Records sit with different parties, in different formats, assembled only when someone asks.
- Unclear payment status. Whether a claim has been submitted, approved, queued or paid may not be visible to anyone outside the immediate transaction.
- Delayed visibility of payment issues. Downstream payment problems often surface as programme delay first and as a financial problem second.
- Cash-flow pressure that isn't visible in a progress report. A project can be on programme physically while its remaining funds no longer comfortably cover its remaining obligations.
- Verification that confirms work, not settlement. Inspection and valuation confirm a stage was reached. They aren't designed to confirm the obligations behind that stage were paid.
- Evidence assembled after the fact. When a question does arise, reconstructing what happened to earlier funds can be slow and incomplete.
None of this suggests that construction payments generally go wrong, or that builders are the cause when they do. Most Australian projects are delivered by capable builders doing careful work. The difficulty is structural: staged payment was designed to determine when money is paid, not to track what happens to it afterwards. That gap sits in the system, not in the character of the people working within it.
§ 03 — Where project money can lose visibility
Follow the money past the drawdown.
The path a construction dollar takes is well understood. What is less visible is how much information is lost at each handover.
Visibility is strong at the top of that chain and strong again at the bottom. It thins in the middle — which is precisely where a lender's exposure sits.
PayLocker exists to close that middle. The principle is simple: construction money should stay connected to the project — to the approved work it funds, the verified participants entitled to receive it, and the obligations required to complete it.
§ 04 — Construction payment is obligation flow, not cash flow
A completed stage and a settled stage are not the same thing.
This is the idea underneath everything PayLocker does, and it matters more to a financier than to almost anyone else.
Money paid into a construction project is not free cash. By the time it arrives, most of it is already committed — to subcontractors who have worked, suppliers who have delivered, materials ordered for the next stage, supervision, procurement and the obligations required to reach completion. It is obligation flow, not cash flow.
Treating it as cash flow produces a specific blind spot. A project can be inspected, valued, certified and confirmed at lock-up, and still carry substantial unpaid obligations behind that milestone. The stage is complete. The stage is not settled. Nothing in a standard progress verification is designed to tell the two apart.
For a lender, this is the difference between knowing that work was done and knowing that the project remains financially able to reach completion. Those are different questions, and only the second one predicts whether the facility performs.
Read the full concept: Obligation flow — why construction payment is more than cash flow
§ 05 — What PayLocker does
A governance layer beneath the payment, not a replacement for the finance above it.
PayLocker is Australian payment governance technology built for construction. It doesn't lend, assess credit, hold security or manage the build. It governs how project money is received, approved and released — and it records what happened at each step.
In practice, that means:
- Project-specific accounts. A project's funds are received, held and released through an account structure kept separate from general business cash flow, so money stays identifiable to the project it was paid for.
- Verified participants. Parties are identified through KYC and KYB processes before they can be paid, with records that may include legal and trading name, ABN or ACN, GST registration status, licence or registration details, nominated bank account, project role and appointment information. This reduces ambiguity about who is entitled to receive money.
- Milestone-based payment structures. Payment stages are defined against the project's agreed programme, so inflows are connected to progress rather than to timing alone.
- Evidence-based verification and multi-party approval. Claims are submitted against work performed and pass through an approval workflow. Approval and payment release are recorded as separate, visible steps.
- Approved obligations drive payment. Where funds are available and an obligation has been properly approved, the entitled participant may be paid in the approved sequence. Where approved obligations exceed the available balance, payments are processed in the approved order, partial payments are recorded, and outstanding balances remain visible.
- Structured payment pathways. Approved payments follow a defined route to verified participants rather than passing through general business cash flow.
- Records of decisions. Claims, evidence, approvals and releases are recorded through the platform — who approved what, when, and against which evidence.
- Project-health indicators. Available funds, approved and committed obligations, budget, variations and projected completion cost can be compared to surface financial deterioration earlier than physical progress alone would show it.
- Permissioned visibility. Each participant sees what their role entitles them to see, and no more.
More on the governance model: Construction payment governance
Stated plainly
What PayLocker does not do
PayLocker does not lend, assess credit, take security, provide financial advice, underwrite risk, guarantee payment, guarantee project completion, or manage construction. It does not replace a lender's facility documentation, credit assessment, valuation, inspection or drawdown process. It is infrastructure that sits beneath those arrangements.
§ 06 — Why payment governance matters to financiers
Six things structured payment governance can change.
Greater payment visibility
Where a project's participants agree to it, PayLocker can give a financier permissioned visibility of funds contributed, approved obligations, payment recipients, project progress, remaining balances, cost overruns and variations — information that otherwise has to be requested, assembled and taken on trust.
Stronger payment governance
Defined approval and release processes apply the same discipline to every payment on the project. Payment governance stops depending on how carefully any individual party happens to administer it, and starts depending on the process itself.
Greater stakeholder transparency
When the borrower, builder, contractors and suppliers work from the same payment information, fewer disagreements begin as misunderstandings about what was claimed, approved or paid.
Better payment accountability
Approval and release are recorded as distinct steps against identified participants and specific obligations. That produces clearer evidence of how project funds were applied — during the project, not reconstructed afterwards.
Reduced payment friction
Clearer processes reduce uncertainty about payment timing and approval. Less time is spent chasing status, and fewer programme delays begin as payment delays.
Earlier visibility of project stress
Comparing available funds against approved and committed obligations can surface financial deterioration earlier than percentage-complete reporting, which by design shows physical progress rather than financial position.
§ 07 — Where PayLocker sits in the payment chain
Beneath the finance. Alongside the build.
Role — unchanged by PayLocker
Where PayLocker fits
PayLocker runs underneath that entire chain as a governance and payment layer. It doesn't sit between the lender and the borrower, and it doesn't take on any part of anyone's role.
The lender's role is unchanged. Credit assessment, facility terms, security, valuation, inspection and drawdown approval all remain exactly where they are. What changes is the quality of information available about what happens to funds after they are released, and the consistency of the process that releases them.
The builder's role is unchanged too. Builders keep control of the build — programme, scope, appointments, claims, approvals, variations and delivery. What changes is that they are no longer required to act as the project's bank, financier and paymaster on top of building it.
§ 08 — What better payment visibility can support
Practical differences, honestly stated.
Better information doesn't remove construction risk. It changes what can be seen, and when. Where a project operates on PayLocker and its participants permission the access, a financier may be able to draw on:
- clearer visibility of payment activity on the project
- stronger supporting evidence at drawdown, from platform records rather than assembled attestation
- a clearer picture of approved obligations still outstanding against remaining funds
- earlier visibility of payment-related issues, before they present as programme delay
- more consistent project payment records across a portfolio
- improved communication between the lender, borrower, builder and downstream parties
- clearer records of who was paid, when, and against which approved obligation
- better-supported borrower monitoring between inspection points
These are capabilities the platform is designed to support. They are not guarantees of outcome. Construction projects can be affected by matters no payment system governs — design, weather, market conditions, contractual disputes, supply chains and commercial decisions among them. PayLocker improves the visibility and discipline of payment. It does not remove risk from construction, and it does not stand behind anyone's obligations.
§ 09 — A different starting point
Where payment information usually comes from, and where it could come from instead.
| Challenge in a fragmented payment environment | The PayLocker approach |
|---|---|
| Payment information sits across several parties and systems | Payment activity is recorded in one structured place |
| Many parties, each with their own records and processes | A connected payment workflow all parties operate within |
| Payment progression is unclear between reporting points | Clearer status: submitted, approved, queued, paid |
| Evidence is assembled manually when a question arises | Approvals and releases are recorded as they occur |
| Approval processes vary between projects and parties | Structured approvals and defined payment workflows |
| Project funds can become difficult to identify once received | Funds are received, held and released through a project-specific account |
| Entitlement to payment is established informally | Participants are verified through KYC and KYB before payment |
| Financial stress becomes visible after physical progress stalls | Available funds compared against approved and committed obligations |
§ 10 — Built around the whole payment chain
Payment governance only works if it works for everyone on the project.
A payment system that serves one party at the expense of another doesn't get adopted, and a system that isn't adopted produces no information for anyone. This is the practical reason PayLocker is built for every party on a project rather than for the party paying for it.
Financiers gain permissioned visibility of how funds are applied against approved obligations. Developers and principals gain structured governance across multi-party delivery. Builders keep full control of the build while shedding the burden of acting as the project's bank — and gain a way to demonstrate payment discipline when tendering. Contractors and trades gain a clearer pathway from approved work to payment. Suppliers gain payment connected to the project rather than to a builder's general cash-flow position. Homeowners and clients gain confidence that their money stays connected to their project.
Those interests are usually described as competing. They aren't. Every one of them improves when project money stays connected to the project — which is why the same infrastructure can serve all of them at once.
Trust, certainty and transparency, from day one to done.
§ 11 — How it works
Five steps.
Establish the project
The project is set up with its participants, contract structure and payment stages. Builders, contractors and suppliers are verified through KYC and KYB before they can be paid.
Connect the funds
Project funds are received into a project-specific account and stay connected to that project rather than entering general business cash flow.
Define stages and obligations
Payment stages are defined against the agreed programme. Downstream appointments and obligations are recorded against the project as they are made.
Verify and approve
Claims are submitted against work performed, supported by evidence where required, and pass through the agreed approval workflow. Approval is recorded as a distinct step from payment.
Release payment
Where funds are available and an obligation has been approved, the entitled participant is paid in the approved sequence, directly to their verified account. Where approved obligations exceed the available balance, payments are made in the approved order, partial payments are recorded, and outstanding balances stay visible.
§ 12 — For banks and financial institutions
For construction finance, credit risk and portfolio teams.
Construction lending carries a structural information asymmetry that other secured lending does not. Security is a partially built asset whose value depends on completion. Completion depends on a payment chain the lender funds but does not control. And the information available about that chain is weakest in the period between inspections — which is exactly when a project's financial position changes.
Structured payment governance is relevant to that asymmetry in three specific ways.
Evidence quality at drawdown
Where a project operates on PayLocker, records of approved obligations, payments made and remaining balances can supplement the valuation, inspection and certification a lender already relies on — not replacing any existing control, but reducing how much of the picture rests on attestation between inspection points.
Monitoring between inspections
Comparing available funds with approved and committed obligations gives a financial reading of project position that runs continuously, alongside the physical reading an inspection provides at a point in time.
Consistency across a portfolio
Where several projects operate on the same payment governance framework, payment information arrives in a consistent structure rather than in whatever form each borrower and builder happens to produce.
Two boundaries matter, and PayLocker states them plainly rather than leaving them to be discovered. First, none of this is a credit control. Credit assessment, facility structure, security, covenants and drawdown authority remain entirely the lender's, and PayLocker neither performs nor informs those decisions. Second, PayLocker holds no authority over the project's money beyond executing instructions that have already been properly approved under the project's agreed process. It is a governance and record layer, not a decision-maker.
For institutions assessing whether the model is relevant to their construction book, the practical next step is a conversation about a specific portfolio or a specific project type. PayLocker is based in Melbourne and built for Australian construction, Australian progress-payment practice and the Australian security-of-payment environment.
§ 13 — Working alongside existing finance structures
Complementary infrastructure, not a replacement.
PayLocker is designed to operate within existing financial and legal arrangements, not to displace them.
It does not replace a bank or a lender. It does not replace loan or facility agreements, construction finance facilities, credit assessment, security arrangements, valuations, quantity-surveyor reporting, existing lender controls, contractual arrangements between the parties, or any regulatory obligation applying to a financier.
It is also not a substitute for the frameworks Australian governments have built. Security-of-payment legislation operates in every state and territory, and several jurisdictions have introduced statutory project or retention trust arrangements — Queensland's regime under the BIF Act, retention money trust requirements in New South Wales, and Western Australia's staged scheme among them. Those frameworks establish legal rights and obligations. PayLocker is technology that supports payment discipline in practice. It is designed to complement statutory frameworks, and it neither alters nor satisfies any obligation arising under them.
The direction of Australian policy is worth noting, because it is the clearest external validation of the model: governments are already legislating toward keeping construction money connected to the projects it was paid for. PayLocker is a practical, technology-delivered expression of that same principle.
How funds are held and what protections apply: Security & compliance
§ 14 — Questions from financiers and lenders
Questions from financiers and lenders
What is PayLocker?
PayLocker is an Australian construction payment integrity platform. It keeps construction money connected to the project by holding project funds in a project-specific account and releasing them through a controlled process aligned to approved progress, verified claims and approved payment obligations. It is based in Melbourne and built for Australian construction.
How does PayLocker work on a construction project?
The project is established with its participants, contract structure and payment stages. Builders, contractors and suppliers are verified through KYC and KYB processes before they can be paid. Project funds are received into a project-specific account. As work progresses, claims are submitted against the work, supported by evidence where required, and pass through the agreed approval workflow. Where funds are available and an obligation has been approved, the entitled participant is paid in the approved sequence, directly to their verified account. Each of those steps is recorded.
Why would this be relevant to a construction financier?
Because a lender's information about a project is strongest at approval and weakest immediately afterwards. Once a drawdown is released, visibility of who was paid, whether obligations behind a completed stage remain outstanding, and whether funds stayed within the project can become fragmented. Where a project operates on PayLocker and its participants permission the access, a financier can be given visibility of funds contributed, approved obligations, payment recipients, project progress, remaining balances, cost overruns and variations.
Does PayLocker replace a construction lender?
No. PayLocker does not lend, does not assess credit, does not take security and does not make drawdown decisions. Credit assessment, facility terms, security arrangements, valuations, inspections and drawdown authority all remain entirely the lender's. PayLocker is payment governance infrastructure that sits beneath those arrangements — it is designed to complement existing finance structures, not replace them.
Is PayLocker a bank?
No. PayLocker is a technology platform providing payment governance for construction projects. It is not a bank, and it does not offer banking products, lending, deposit-taking or insurance.
Is PayLocker an ADI?
No. PayLocker Pty Ltd is not an Authorised Deposit-taking Institution and is not regulated by the Australian Prudential Regulation Authority. PayLocker's preferred online payment partner is Australian Settlements Limited, which is an ADI regulated by APRA. PayLocker facilitates connections between users and that partner's payment services; PayLocker does not itself hold or transfer deposits or project payments.
Does PayLocker provide financial advice?
No. PayLocker does not provide financial advice or financial services as defined under the relevant Australian legislation. Nothing on this website is financial, legal or credit advice, and financiers should form their own view and take their own advice on any arrangement they enter into.
Who holds the project funds?
Project funds are held through PayLocker's payment partner arrangements rather than by PayLocker itself. How funds are held, what account structures apply and what protections attach are set out in full on our security and compliance page and in the Product Disclosure Statement.
How does PayLocker create payment transparency?
Through four mechanisms working together: participants are verified before they can be paid, so entitlement is clear; payment stages are defined against the agreed programme, so inflows connect to progress; claims are verified and approved through a defined workflow, with approval recorded separately from release; and payments are made to verified participants in the approved sequence, with each step recorded. Access is permissioned — each participant sees what their role entitles them to see, and no more.
Can PayLocker work alongside our existing finance arrangements?
It is designed to. PayLocker operates as a payment governance layer beneath existing arrangements and is not intended to replace loan or facility agreements, credit assessment, security, valuations, quantity-surveyor reporting or existing lender controls. Whether it suits a particular facility structure is a question worth working through against your own documentation, and we're happy to have that conversation.
How are payments linked to project progress?
Payment stages are defined against the project's agreed programme. Claims are submitted against work performed and, where required, supported by evidence. Once a claim is verified and approved under the project's agreed process, the approved obligation becomes payable in sequence when funds are available. Where approved obligations exceed the available balance, payments are processed in the approved order, partial payments are recorded, and outstanding balances remain visible rather than disappearing from the record.
How does PayLocker handle payment disputes?
Because approval and release are recorded as distinct steps against identified participants and specific obligations, the factual record of what was claimed, what evidence was provided, what was approved and what was paid is available to the parties. That record can support resolution, but PayLocker does not determine disputes, does not adjudicate entitlement, and does not affect any right a party has under their contract or under security-of-payment legislation. Our complaints and dispute resolution process is set out separately.
§ 15 — Next step
Talk to us about your construction book.
If you fund Australian construction and want to understand what structured payment governance could mean for a specific portfolio or project type, we're happy to have that conversation — no obligation, no pitch deck.