Accounts Receivable · Embedded Payments

Get paid where the invoice already is.

Your invoice already reaches the customer by email, by EDI, by post or through the B2BE customer portal. The embedded payments solution puts a payment link inside that same delivery, so settling the invoice is one click from the document rather than a separate trip to a bank portal. The same rails that let you control how you pay suppliers now let your customers pay you.

The problem

The invoice arrives. The payment is a separate job.

Most accounts receivable friction is not a dispute. It is a gap. The invoice lands in an inbox or a portal, and paying it means someone opens a different system, keys a reference, matches an amount and schedules a run. The document and the payment live in different places, so the payment waits for the next cycle rather than the moment of intent.

Closing that gap is worth more than chasing. When paying is one click from the document the customer is already looking at, more invoices are settled on the day they are read, remittance data arrives structured rather than typed, and your team spends less time matching cash to invoices after the fact.

Who carries the cost, and what the customer gets back.

Both models put the same payment link in front of the same customer, and in both the customer enrols with GlobalFinex B2B before they can use it. What differs is who bears the transaction cost and how far the benefit travels beyond your invoice.

Model one

Supplier-funded

You carry the transaction cost, exactly as a merchant carries a card fee today. Your customer enrols, follows the link and pays, and the cost of that transaction never reaches them.

i
The cost sits with you. Price it as a collection cost against the DSO it removes, the same way you would judge any acceptance decision today.
i
An easier ask of the customer. They are not being asked to justify a new cost internally, which is usually what stalls a change to how someone pays.
i
One decision, not one per customer. You choose which customers it is offered to and the commercial terms are settled once, on your side.

Model two

Customer joins the network

Your customer enrols and carries the cost themselves. In exchange they are not only able to pay your invoices: they can settle invoices from any of their other suppliers through the same control layer, on their own terms.

i
The cost moves. The customer is making a funding decision about their own payables, so the economics sit with them rather than with you.
i
They get the buy-side levers. Method and timing on their whole payables book, not just on what they owe you.
i
Your invoice becomes the front door. Every enrolled customer arrives through a supplier they already trust and pay.

Why the models are separate rather than a setting. In a growing number of markets the cost of accepting a card payment can no longer be passed to the customer paying by card. Australia's reform takes effect on 1 October 2026, and comparable surcharging and interchange rules already apply across the United Kingdom, the European Union and a number of other jurisdictions, with the detail differing in each. Model one keeps the cost where those rules put it. Model two is not an acceptance decision at all: the customer has chosen how to fund their own payables, which is their side of the transaction and their cost to carry.

The link travels with the invoice.

Delivered through B2BE Managed Invoice Distribution, so the payment option reaches each customer in whichever channel they already receive invoices on. Nothing new for them to learn and nothing new for you to run.

In the document

Embedded in the invoice

A pay link on the invoice itself, carrying the reference and the amount, so the payment arrives already matched to the document that raised it.

In the delivery

In the email

Branded email delivery with the payment option in the body, for the many customers whose process starts and ends in the inbox.

In the portal

In the customer portal

The B2BE customer portal, where a customer can see what is outstanding, retrieve the document and settle it in the same place.

Managed Invoice Distribution already delivers invoices by EDI, email PDF, web portal, print and post, and through government e-invoicing networks. The payment option is added to those channels rather than replacing any of them, so customers who want a printed invoice keep getting one.

Cash arrives matched, not just faster.

Payment initiated from the document, so the reference and amount are carried rather than retyped

Structured remittance against the invoice, which is where most cash application effort disappears

Fewer part-payments and keying errors to investigate at month end

Visibility of which invoices have been opened and which have been paid, in the same place

No change to your ledger, your terms or your collections policy

This does not change your terms. The customer is offered a way to pay what they already owe, on the date it is already due. Nothing here shortens a term, applies a discount or asks a customer to fund anything early.

You already know this mechanism from the buy side.

On your payables, Flow: ePayment governs how an approved invoice is settled: card rails inside a managed environment, with GlobalFinex B2B as Merchant of Record and the supplier paid by EFT. Embedded receivables is that same control layer pointed the other way, so the business paying you gets the option and you get the cash.

Model two is where the two sides meet. A customer who enrols to pay you is enrolled to pay everyone, which means the invoice you were sending anyway becomes the route by which the network grows.

Worth a conversation about customer payments?

The useful version of this discussion starts with your invoice volume, your channel mix and who your top customers are. Thirty minutes with your receivables lead is usually enough to tell whether either model is worth modelling properly.