Māori Economy · Productive Capital · Discussion 06
Why are complex capital transactions so difficult to coordinate?
Because getting a transaction approved is only part of the job. The applicant, capital provider, lawyer, vendor, advisers, security documents, conditions and settlement all have to become true at the same time.
Discussion 05 asked whether a productive asset could support more of its own financing.
That immediately creates another problem.
The more sophisticated the capital structure becomes, the more parties have to coordinate.
A simple consumer loan can sometimes look like:
borrower → bank → money.
A commercial acquisition can look more like:
applicant → accountant → broker → lender → investor → lawyer → vendor → agent → valuer → security registry → settlement.
And every one of those parties can be waiting for something from somebody else.
A capital transaction can be economically viable and still fail operationally because the people, evidence, approvals and settlement steps never line up cleanly.
Approval is not the same thing as completion
This distinction is fundamental.
A lender can like the transaction.
A credit committee can approve it.
An investor can agree to participate.
And the transaction can still be nowhere near settlement.
An approval may be subject to:
legal documentation,
valuation,
insurance,
proof of equity,
entity resolutions,
security registration,
AML/CFT checks,
financial information,
vendor documents,
or other conditions.
Until those conditions are satisfied, there may be no money available to release.
“Approved” is a credit decision. “Ready to settle” is a transaction state.
Start with the applicant
The applicant has to establish who it is and what it is authorised to do.
For a company, that can mean:
company details,
directors,
shareholders,
beneficial owners,
authorised signatories,
financial statements,
tax information,
bank statements,
and board authority.
For a trust or collectively governed entity, the authority question can become more complicated.
The capital provider and lawyer may need to understand:
the trust deed or order,
who the current trustees are,
what powers they hold,
whether a resolution is required,
how many trustees must approve,
and whether any restriction applies to the transaction or security.
This is not administrative decoration.
If the wrong person signs, the transaction can carry a fundamental authority problem.
Then the asset being acquired has to be understood
Business.govt.nz recommends substantial due diligence before acquiring a business.
That can include checking:
financial records,
stock,
debts,
legal disputes,
ownership of key assets,
employment arrangements,
sales and supply contracts,
premises,
customers,
suppliers,
and goodwill.
Business.govt.nz — Buying a Business or Franchise ↗
Some of that information is needed by the buyer.
Some is needed by the lender.
Some by the investor.
Some by the accountant.
Some by the lawyer.
The same source document can therefore be requested several times for different reasons.
The broker or adviser is trying to make the transaction financeable
The intermediary's job is not simply to forward a PDF application.
In a complex transaction, the broker or adviser may need to work out:
which capital provider fits the risk,
how much senior debt the business can carry,
whether subordinated capital is required,
whether vendor finance is possible,
how much equity the buyer must contribute,
what security is available,
and what evidence each provider will require.
If the first lender declines, the structure itself may need to change before another provider will consider it.
That creates versioning.
Version one of the transaction may not be the transaction that finally settles.
The lender sees a different transaction from the buyer
The buyer sees an opportunity.
The lender sees a series of risks.
It asks:
Can the business service the debt?
What happens if revenue falls?
What collateral exists?
What is the recovery value?
Who ranks ahead of us?
What equity is beneath us?
Are the people competent?
Is the purchase price credible?
What happens if one important customer leaves?
This is why the same business plan that excites a buyer may be insufficient for credit approval.
An investor asks a different set of questions again
Equity capital does not sit in the same place as debt.
An investor may care about:
ownership percentage,
voting rights,
board rights,
dividends,
future capital raises,
exit rights,
valuation,
and protection from dilution.
If Māori ownership is part of the transaction objective, those rights matter enormously.
A financing package can solve a short-term cash problem while quietly transferring too much long-term economic control.
That is why debt and equity cannot simply be entered into one box labelled “funding”.
The lawyer is not merely witnessing signatures
Business.govt.nz specifically recommends using a lawyer to prepare the business-sale contract and to make sure the agreement addresses matters such as price, payment, staff, restraints and due-diligence periods.
Business.govt.nz — Business Sale Contracts ↗
In a financed acquisition, legal work can also include:
reviewing the sale agreement,
reviewing finance documents,
checking entity authority,
documenting guarantees,
documenting security,
confirming conditions,
and coordinating settlement.
The lawyer has professional duties to the client.
A technology platform should make evidence and workflow easier.
It should not try to replace legal advice.
The vendor has its own conditions
The seller wants certainty that:
the buyer can complete,
the purchase price will arrive,
required consents are obtained,
the correct assets or shares transfer,
and any vendor finance or earn-out is properly documented.
If the seller is providing part of the capital, the vendor may simultaneously be:
the seller,
a creditor,
and sometimes a continuing stakeholder in the business.
That creates additional conflicts and documentation requirements.
Then security has to match the capital structure
Discussion 05 showed that New Zealand's Personal Property Securities Register can be used to register security interests over a wide range of personal property.
Companies Office — What Is the PPSR? ↗
But registering security is not just an administrative final step.
In a transaction with several capital providers, everyone needs to know:
which assets are secured,
which lender has priority,
whether another security interest already exists,
which registrations must be released,
and whether an intercreditor arrangement is needed.
A capital stack cannot be governed properly if every participant has a different understanding of who ranks first.
The transaction does not merely need capital. It needs a legally coherent map of who has a claim over what.
Conditions precedent are where coordination becomes visible
A condition precedent is simply something that must be satisfied before the next contractual step — often before funds can be drawn or settlement can occur.
A commercial financing transaction may have a checklist containing items such as:
executed finance documents,
board or trustee resolutions,
proof of buyer equity,
insurance certificates,
valuation,
security documents,
PPSR registrations,
AML/CFT completion,
legal opinions or certifications,
vendor documents,
or evidence that another capital provider is ready.
The important part is not the phrase “condition precedent”.
It is the dependency.
One missing item can block everything downstream.
This is why email becomes dangerous at scale
Email is excellent for communication.
It is weak as a transaction-state system.
Imagine a 60-message thread.
The lender has version 4 of the forecast.
The lawyer has version 5.
The broker has just received version 6.
The buyer thinks the valuation condition has been satisfied.
The lender is still waiting for the signed final report.
The vendor changed the settlement date yesterday.
The investor has not seen the amended purchase agreement.
Nobody is necessarily incompetent.
The system is simply fragmented.
The problem with email is not that messages disappear. It is that the transaction state has to be reconstructed from messages.
PDFs create a similar version problem
A PDF can prove what a document said at a moment in time.
But a folder full of PDFs does not automatically tell us:
which document is current,
who approved it,
what it replaced,
which transaction condition it satisfies,
or whether another participant has accepted it.
The document and the workflow are different things.
A better system needs both.
AML/CFT can cause legitimate repetition
Financial transactions often involve multiple regulated or reporting entities.
The Department of Internal Affairs' updated 2026 AML/CFT guidance for lawyers and conveyancers includes separate guidance for companies, trusts, beneficial ownership, enhanced customer due diligence, third-party outsourcing and reliance on another reporting entity.
Department of Internal Affairs — AML/CFT for Lawyers and Conveyancers ↗
That tells us something important.
“The applicant already gave their identity documents to someone else” does not automatically mean every participant can simply skip its own legal obligations.
Reliance can sometimes be structured under the law and guidance.
But responsibility, eligibility and evidence still matter.
A good platform can reduce unnecessary duplication.
It cannot tell regulated parties to ignore AML/CFT duties.
Trusts and companies create more beneficial-ownership questions
Current AML/CFT guidance requires reporting entities to identify and verify customers, beneficial owners and people acting on behalf of customers where the Act applies.
Department of Internal Affairs — Customer Due Diligence Guidance ↗
For a simple individual customer, the authority chain can be short.
For a company, trust or investment structure, the question can involve:
legal ownership,
beneficial ownership,
control,
authority to act,
and source-of-funds information.
That is particularly relevant to a system designed for trusts and companies rather than consumer borrowers.
Settlement is a sequence, not a payment button
At settlement, several things may need to happen in a defined order.
Buyer equity must be available.
Lender funds must be authorised.
Investor capital may need to be received.
Security documents must be effective or capable of becoming effective.
The sale agreement conditions must be satisfied.
The vendor must be ready to transfer ownership.
Existing security may need to be discharged.
New security may need to be registered.
Lawyers may need to give undertakings or certifications.
Funds then move.
Ownership changes.
And afterward the transaction needs to be reconciled against what was supposed to happen.
Settlement is the moment when legal state, financial state and operational state have to agree.
One missing party can stop everyone else
This is what makes transaction coordination expensive.
The lender cannot release funds because the lawyer has not certified a condition.
The lawyer cannot certify because the applicant has not supplied a resolution.
The applicant is waiting for the broker to confirm the final capital structure.
The broker cannot confirm it because the investor changed its commitment.
The vendor is waiting for confirmation of settlement.
Every party may be acting rationally.
The transaction is still blocked.
Small transactions can suffer disproportionately
The Reserve Bank's Māori access-to-capital research explains how information asymmetries can make smaller, younger and rural firms more expensive to assess and monitor.
Where lenders cannot easily distinguish stronger from weaker projects, viable firms can face higher prices or exclusion.
Reserve Bank — Māori Access to Capital: Market Failures ↗
This is where transaction coordination becomes economically important.
A $50 million transaction can support substantial legal, advisory and due-diligence cost.
A $750,000 acquisition may not.
If the fixed cost of proving the transaction is too high relative to its size, otherwise viable smaller deals can become uneconomic to process.
That is not unique to Māori.
But it can matter for Māori SMEs and collectively governed entities where information, authority or collateral pathways already require more explanation.
The Reserve Bank has already shown that clearer process can reduce transaction costs
Its guidance on lending over whenua Māori says clarifying the mortgage process can help landowners, lawyers and banks understand the required steps, potentially reduce transaction costs and broaden financing options.
Reserve Bank — Practice Note for Lending on Whenua Māori ↗
That is a useful general principle.
When everyone understands:
what is required,
who must do it,
what evidence proves completion,
and what happens next,
transaction friction can fall without lowering the legal or credit standard.
This is the actual design problem behind Source Code Open Finance
The current Source Code + KAURI architecture is designed around a governed commercial finance transaction path rather than a single approval screen.
KAURI is the applicant-facing layer.
Source Code coordinates the transaction across roles.
The current control sequence is built around:
applicant information,
finance placement,
capital-provider decision,
legal completion,
vendor or agent requirements,
security,
conditions precedent,
settlement,
and payment.
The governance principle is that no single participant controls the entire transaction.
That is the point inherited from the earlier NSB payment architecture that remains genuinely useful here:
complex financial execution benefits from role separation, evidence, explicit state and auditability.
But Source Code should not become a giant shared inbox
If all we build is one place where everybody uploads PDFs, we have centralised the clutter without solving the coordination problem.
The platform needs to understand transaction state.
I would expect a productive-capital workflow to distinguish states such as:
Draft.
Application evidence complete.
Capital sourcing.
Indicative terms received.
Credit approved subject to conditions.
Legal documentation in progress.
Conditions precedent outstanding.
Conditions satisfied.
Ready to settle.
Settled.
Reconciled and closed.
Those names may evolve.
The principle should not.
A transaction platform needs a single source of truth without creating a single source of authority.
Each condition should have an owner
A useful condition record should answer:
What is required?
Who is responsible?
Who decides whether it is satisfied?
What evidence supports that decision?
Which version of the evidence is current?
When was it completed?
Does it block settlement?
This turns a vague checklist into a governed dependency map.
Each capital provider should be represented separately
If a transaction has:
senior debt,
vendor finance,
equity,
and a guarantee,
the platform should not flatten them into one number called “approved finance”.
Each instrument should have its own:
provider,
amount,
status,
conditions,
security or ownership rights,
priority,
and settlement requirement.
Only then can the system answer a simple but critical question:
Is the whole capital stack actually ready?
Permissions need to follow the role
The applicant should not be able to mark the lender's credit condition satisfied.
The broker should not provide the lawyer's legal certification.
The lawyer should not approve the lender's credit risk.
The vendor should not alter buyer authority records.
The system should therefore separate:
who can submit,
who can review,
who can approve,
who can amend,
and who can release the transaction to the next state.
This is where maker/checker thinking becomes useful outside payments.
Exceptions need to be first-class objects
Real transactions do not follow a perfect straight line.
A valuation expires.
A trustee changes.
A lender reduces the approved amount.
The vendor delays settlement.
A document is rejected.
A security interest is discovered.
A capital provider withdraws.
The system needs to record:
what changed,
who identified it,
what transaction state is affected,
what must be repeated,
and who can clear the exception.
An exception hidden inside an email chain is an operational risk.
Auditability matters because memory is not evidence
After a transaction settles, somebody should be able to reconstruct:
who submitted each material item,
which version was relied on,
who approved it,
which conditions were satisfied,
what funds were expected,
what funds actually moved,
and what exceptions occurred.
That is useful for:
the applicant,
the lender,
investors,
auditors,
lawyers,
and potentially regulators where relevant.
What technology should not decide
There are boundaries.
Source Code should not decide that a business is creditworthy.
It should not decide that legal advice is unnecessary.
It should not substitute for an independent valuation.
It should not determine whether a trustee has complied with fiduciary duties.
It should not waive AML/CFT obligations.
And it should not automatically release capital simply because enough boxes appear green.
Those decisions belong to the authorised participant under the relevant contract, law and professional duty.
Software should coordinate authority. It should not impersonate authority.
This could also improve the data we have been missing
If every transaction has structured states rather than an email trail, we can begin measuring:
time from application to first capital response,
time spent in due diligence,
how often information is resubmitted,
which conditions cause the most delay,
where applicants abandon transactions,
how often collateral becomes the constraint,
how often capital stacks fail to complete,
and how long settlement takes after credit approval.
This could help distinguish:
capital shortage,
credit decline,
information failure,
governance delay,
legal delay,
and transaction-process failure.
That is exactly the kind of distinction the current Māori access-to-capital data cannot always make.
My conclusion
Complex capital transactions are difficult because there is no single decision that completes them.
The applicant must prove identity, authority and economics.
The adviser must structure the transaction.
The lender must approve credit.
The investor must approve ownership risk.
The lawyer must complete legal work.
The seller must be ready to transfer the asset.
Security must be coherent.
Conditions precedent must be satisfied.
And settlement must occur in the correct sequence.
Email and PDFs are useful tools inside that process.
They are not the process itself.
The real infrastructure problem is turning many independent decisions into one transaction that can safely reach settlement.
Next
Once the transaction can be seen clearly, we can finally ask whether it is creating the outcome we actually want:
What should a Māori productive-capital pipeline measure? →
Discussion 07 moves beyond “capital deployed” and examines acquisitions completed, Māori ownership retained, cash flow, equity growth, jobs, export capacity, debt service, failures and whether each transaction leaves the next generation with a stronger balance sheet.
Primary sources
Reserve Bank — Māori Access to Capital: Market Failures ↗
Reserve Bank — Practice Note for Lending on Whenua Māori ↗
Business.govt.nz — Buying a Business or Franchise ↗
Companies Office — Personal Property Securities Register ↗
Department of Internal Affairs — AML/CFT Guidance for Lawyers and Conveyancers ↗
Department of Internal Affairs — 2026 AML/CFT Guidance Updates ↗