TL;DR: Embedded finance is the integration of financial products inside the software SMEs already use. It works when the finance product matches a real cashflow trigger inside the workflow. It stalls when platforms bolt on generic credit without an underwriting view or a clear repayment path. This article covers the conditions that separate the two.
What embedded finance actually means for an SME
Embedded finance is not a new product category. It is a delivery mechanism. The financial product itself (a loan, an advance, a payment facility) is not new. What is new is where it lives.
For a small business, embedded finance means the funding option appears inside software they already use every day. Their accounting platform. Their job management tool. Their industry marketplace. Instead of going to a lender separately, the option is there when they need it, built into the workflow that already holds their financial data.
In Australia and New Zealand, the clearest current examples are invoice finance embedded into accounting software. The business raises an invoice in Xero or MYOB. The platform has visibility of that invoice. A finance option appears alongside it. The SME elects to fund the invoice, receives the cash that day, and repays when the client pays. No separate application. No separate login.
The four conditions that have to be true for embedded finance to work
Most embedded finance partnerships that underperform fail on one of four conditions.
1. The finance product must match a real cashflow trigger in the platform.
The trigger has to be something that happens inside the software on a regular basis. An invoice being raised. A contract being signed. A payroll run being initiated. If the trigger is too abstract or too infrequent, the finance option sits unused.
2. The platform must have underwriting-relevant data.
The reason embedded finance can be faster than traditional lending is that the underwriting data is already in the system. Invoice amount, debtor, payment history, revenue patterns. If the platform does not hold this data, or the finance partner cannot access it with appropriate consent, the underwriting falls back to a manual process and the speed advantage disappears.
3. There must be a clear and automated repayment pathway.
For the product to be low-friction, repayment needs to happen without the SME manually initiating it. For invoice finance, the repayment event is the debtor paying the invoice. That needs to be visible to the platform and passed to the finance provider automatically.
4. Support and escalation must be resolved before launch.
When something goes wrong, who does the SME call? The platform? The finance provider? If neither party has a clear answer to this before launch, the customer experience breaks at the worst possible moment.
Where embedded invoice finance fits the AU/NZ market specifically
The AU/NZ SME market has a structural cashflow problem that makes embedded invoice finance a strong fit. Payment terms in New Zealand average 39 days. In Australia, payment times for small businesses are among the longest in the OECD. A business that invoices on 30-day terms and actually waits 40 to 50 days has a predictable, recurring cashflow gap that does not require a new financial product. It requires faster access to money that is already owed.
Invoice finance is not a loan against future revenue. It is an advance on revenue that has already been earned. That distinction matters for underwriting (the invoice is collateral, not a projection) and for how SMEs understand and accept the product.
The AU/NZ accounting software market, led by Xero with approximately 1.5 million subscribers across both markets, is already integrated with invoice data. The underwriting infrastructure is closer to being in place than in markets where financial data is more fragmented.
Common failure modes: bolt-on credit, generic underwriting, no repayment plumbing
The most common failure mode in embedded finance is bolt-on credit. A platform adds a generic credit facility from a third-party lender without adapting it to the specific trigger, data, or repayment structure of their platform. The product exists, but it does not match the workflow. Users see it, do not understand when to use it, and ignore it.
The second failure mode is generic underwriting. A finance partner assesses the SME using their standard credit model, which may not account for the platform's data or the specific transaction being financed. Approvals are slower than the platform promised. Decline rates are higher than expected. The platform loses trust with its users.
The third failure mode is no repayment plumbing. The finance provider handles disbursement but has no clean mechanism to receive repayment when the debtor pays the invoice. Manual repayment processes create late payments, reconciliation errors, and customer complaints that land with neither party clearly owning the response.
What software platforms should look for in a finance partner
The due diligence a platform should run on a finance partner is not just commercial. It is product and operational.
On underwriting: Does the partner understand the specific transaction type your platform enables? Can they underwrite using your data, with appropriate consent frameworks? What are their typical approval rates and approval times for your user profile?
On integration: What is the API surface? How deep is the data integration? What does the user experience look like at the point of offer?
On support: Who owns the relationship with the SME when they have a question about their advance? How is the escalation path structured?
On commercial structure: Referral fee, revenue share, white-label, or fully embedded? Who carries regulatory responsibility in AU and NZ for the financial product?
What SMEs should look for before clicking apply
Cost: What is the actual fee for advancing this invoice? For invoice finance specifically, look for a flat percentage per invoice with no ongoing fees, no minimum draw, and no lock-in commitment. FundTap charges 4 to 6% per invoice in AU and NZ.
Speed: What is the realistic time from application to funds? Same-day funding is achievable in AU/NZ for invoices submitted before a cut-off time.
Client notification: Does funding the invoice notify your client? Selective invoice finance models that do not notify the debtor are available and common in the AU/NZ market. FundTap does not notify debtors.
Exit: What happens if you want to stop using the product? No lock-in is a standard feature of on-demand invoice finance.
Frequently asked questions
What is embedded finance?
Embedded finance is the integration of financial products such as payments, lending, or insurance directly into software that businesses already use. For SMEs, this typically means invoice finance, buy now pay later, or payment processing built into their accounting software, ERP, or industry platform.
How is embedded finance different from a traditional loan?
A traditional loan is a separate product you apply for outside your existing software and workflow. Embedded finance is triggered by data already in the platform. Approval is faster because the platform has existing visibility of your business. Repayment is structured around the underlying transaction rather than a fixed schedule.
Why is invoice finance well-suited to embedded delivery?
Invoice finance is a natural fit for embedded delivery because the invoice is already in the system. An accounting platform or ERP has visibility of the invoice date, amount, debtor, and payment terms. That is the underwriting data. The trigger and the repayment event are both inside the platform.
What should a software platform consider before adding finance to its product?
Four questions: Does the finance product match a real cashflow trigger? Does the partner have underwriting capability built around your data? Is the repayment pathway clear and automated? Who handles the customer when something goes wrong? If any of these cannot be answered clearly, the partnership is not ready to launch.
Are you a software platform or fintech exploring an embedded finance partnership? Talk to FundTap about platform partnerships.
Author: Shane Laurence, Head of Growth at FundTap. Published: 15 May 2026. Updated: 15 May 2026.
Back
.png)