[aa disclaimer]
Legal Disclaimer: This article is for informational purposes only and does not constitute legal, financial, compliance, or tax advice. Banking eligibility and provider policies vary by jurisdiction, as do regulatory requirements. Consult qualified professionals before making decisions.
[/aa]

A £12,000 payment can arrive while two client invoices remain unmatched. The missing information is who the payment belongs to and what the platform may do with it.

A UK account for a corporate collections platform receiving invoice proceeds must support the agreed arrangement. Operations staff need records that link each payment to the client entitled to it. This guide covers onboarding and daily matching. It also explains how dedicated receiving details relate to the underlying legal structure.

[aa key-takeaways]

Key Takeaways

1. Identify service fees separately from client invoice receipts.

2. Document the receiving account holder and establish precisely when payment to an intermediary settles the buyer's legal obligation to the seller.

3. Link each receipt to a client record and the invoices it settles.

4. Keep refunds connected to their original payments, with independent approval.

5. Confirm the provider accepts the actual fund flow before using account details on invoices.
   [/aa]

UK account for a corporate collections platform: receiving invoice proceeds

Invoice proceeds are payments against invoices. For a collections platform, the first question is whether those invoices represent its own revenue or amounts owed to its business clients. Identical payment references can conceal very different obligations.

Consider two contracts. A subscriber pays £500 for access to the software. Separately, a buyer sends £12,000 through the platform to settle invoices issued by a supplier. The service fee is revenue under the subscription contract; handling the payment owed to the supplier needs a documented collection arrangement.

A bank or an electronic money institution (EMI) may provide the receiving account for either model. The account provider must understand the distinction.

The Financial Conduct Authority (FCA) explains that receiving customer money before passing it to a seller may constitute a payment service. The guidance covers accounts in the business's own name. A standard business-account approval therefore cannot substitute for an assessment of the platform's activities.

Document the collection model before onboarding

Establish whose receivable is being paid

A receivable is an amount a customer owes. The provider review should start with the legal entity named on the invoice and follow the money through to that entity. Record whether the platform can hold funds, deduct its fees or instruct refunds.

Timing matters. If the payer sends £12,000 on Monday and the client receives settlement on Thursday, the contracts should explain who is entitled to the funds during those three days.

Some platforms describe themselves as commercial agents. The commercial agent exclusion has specific conditions: the agent must have formal authority to negotiate or conclude a sale for either the payer or the payee. It cannot act for both under that exclusion. Simply accepting money or labelling a contract “agency” does not establish those conditions.

A regulated payment service provider (PSP) can manage collections within an agreed arrangement. Its involvement does not automatically settle whether the platform's own activities require authorisation or registration.

Prepare the provider review pack

Prepare one diagram showing each legal entity and each account the money passes through. Support it with evidence:

• Collection agreements and representative client invoices.

• Company registration and ownership documents.

• Expected monthly receipt values and transaction counts.

• Payer countries and settlement currencies, plus typical holding periods.

• Rules for fees, refunds, rejected payments and client settlements.

The pack should also state when payment legally settles the payer's debt. A contractual term saying the client has received payment only after onward settlement can affect the assessment.

Providers can then compare the declared activity with actual transfers. For example, a platform expecting 400 corporate invoice payments each month should report a shift to thousands of small individual payments. The provider can then confirm whether the account remains suitable.

A B2B marketplace supplier-payout model raises similar questions about who owns receipts before onward payment. The account structure must follow the contracts.

Choose a dedicated business IBAN for the approved flow

Distinguish account ownership from payment routing

An International Bank Account Number (IBAN) identifies an account for payments. A dedicated business IBAN may help identify the receiving business, but the provider's terms determine the precise arrangement.

A virtual IBAN can route receipts to an underlying account. The European Banking Authority's report on virtual IBANs describes this mechanism and the different models found in the EU. That research explains the technology; it does not determine a UK platform's permissions.

Ask whose name appears against the receiving details, who holds the underlying account and which client receives the credit. A separate identifier does not, by itself, prove a separate legal account or protection from another party's insolvency.

Maintain the client-to-account mapping

Assign a stable client ID to each approved collection arrangement. The system should retain the receiving details associated with that ID and the dates when they applied.

For instance, client C-104 might use one receiving IBAN until 31 October and another from 1 November. A payment arriving against the retired details still needs its historical mapping. Deleting that mapping creates a reconciliation problem.

The named-IBAN invoice collections workflow adds another practical check: invoice templates must use the receiving details and beneficiary name confirmed by the provider. Keep invoice references alongside the mapping. Allocation means assigning a receipt to a client and the debt it settles.

Run invoice proceeds reconciliation in the UK

Create one traceable allocation

Invoice reconciliation compares invoices with financial records. For incoming collections, it means matching a confirmed receipt to the amount owed and the client entitled to it. Matching the bank balance alone leaves that client-level question unanswered.

A useful record links:

• The client ID and invoice number.

• The payer name and available payer-account information.

• The receiving account details.

• The provider's unique transaction ID.

• The received amount and currency, with the booking date.

• The allocation decision and any later adjustment.

The database must support partial payments and combined settlements. Store the individual links so a single transfer can clear several debts, while instalments accumulate against one outstanding amount.

In an illustrative example, payer Northbridge Ltd sends £12,000 to settle two invoices for client C-104. Invoice A-301 is £8,000 and invoice A-302 is £4,000. The team records one receipt with two allocation entries.

These figures illustrate the method. They are not EQWIRE customer results.

Resolve exceptions before settlement

An £11,850 receipt against those same invoices leaves a £150 difference. Operations should identify whether it reflects a partial payment or another documented adjustment. The system must not silently mark £12,000 as received.

Unclear references need investigation. Staff can use remittance advice to investigate. This is the payer’s breakdown of the invoices being paid. Matching by amount alone becomes unreliable when several customers owe identical sums.

Automation also needs a duplicate check. If the provider delivers the same status notification twice, the transaction ID should prevent the system from creating a second receipt. A notification that a payment was submitted is not evidence that the funds arrived.

Give unresolved items an owner and a review date. Keep them out of settlement calculations until the team establishes the correct treatment. A daily check is a practical operating control; any formal safeguarding reconciliation has its own applicable rules.

[aa cta]

Prepare an account application around the actual collection flow

EQWIRE can review the documented business model and account requirements. Availability depends on eligibility and approval of the proposed use following compliance review.

[aa btn]Start an Application[/aa]
[/aa]

Control refunds and client settlements

Preserve the original receipt

A refund should create a new transaction linked to the original receipt. Deleting the incoming payment destroys the explanation of what happened.

Suppose client C-104 authorises a £1,000 refund against invoice A-302. Retain receipt R-880. Add a separate entry for the refund reason and payment status. Assuming no fees or other movements, the remaining cash is £11,000.

The invoice balance needs separate treatment. A credit note may reduce the amount owed; a payment reversal may leave the original debt outstanding. Finance should record the correct outcome under the underlying agreement.

Retain the client instruction and supporting evidence before releasing a refund. Check the beneficiary through the approved process, particularly if a request asks for payment to an unrelated account. Use an independent payment approver so that the person preparing the refund cannot approve it alone.

A submitted refund remains pending until the provider confirms its outcome. Record any failure. Finance should investigate whether the refund remains payable before preparing another instruction. The same principle applies to rejected client settlements.

Keep an accessible history

Bank exports and client statements should agree with the allocation records. Preserve corrections as dated entries identifying who made them. Staff need to reconstruct the position before a refund as well as the current balance.

GOV.UK's company accounting-record requirements cover contracts and the evidence of money received or spent. UK limited companies must normally keep records for six years from the end of the last company financial year they concern, with specified reasons to retain them longer.

Apply the retention requirements relevant to each record category. Six years is not a universal deletion date for every document a regulated collection arrangement may require.

Client money account: UK firm responsibilities

Different legal and accounting questions sit behind the label “client money account”. An unpaid invoice records a buyer’s debt. A balance due to a business customer is a liability in the platform’s books. Safeguarding protects funds under a specified regulatory duty. Naming a product “client money” does not establish which rules apply.

For payments and electronic money institutions in scope, the FCA's Supplementary Regime took effect on 7 May 2026. Software companies do not automatically fall within that scope.

The FCA’s CASS 15.8 rules require safeguarding institutions to distinguish relevant funds from other money and maintain accurate internal records. They must also perform the required safeguarding reconciliations. “Relevant funds” are funds the institution must protect under those rules.

The institution responsible for safeguarding must keep its own records even when the platform supplies payment-matching data.

EQWIRE is an EMI. Its published explanation of how customer funds are protected describes safeguarding and segregation from its own funds. Electronic money does not carry the Financial Services Compensation Scheme deposit protection associated with eligible bank deposits. Safeguarding does not guarantee full repayment. Returning funds after insolvency may take time.

The platform still needs the provider to confirm how protection applies to its proposed collection arrangement and to whom.

Choosing the best business bank account for receiving international payments

For a collections platform, account suitability starts with the accepted activity. Compare providers against the documented model before comparing transfer charges.

The review should answer five questions:

1. Does the provider accept these client collections and the proposed holding period?

2. Who holds the account, and whose balance does each receipt increase?

3. Can finance retrieve transaction IDs and export complete payment records?

4. Which currencies and payment routes support the actual payer base?

5. How do refunds and rejected settlements appear in reporting?

An exchange creates an additional record to match. Record both sides of each conversion and its applied rate. A GBP invoice and an EUR receipt cannot match solely because their numeric values look similar.

EQWIRE's business accounts provide multi-currency payments and access to transaction records for approved business uses. Applicants should provide contracts and a diagram for assessment; published features do not confirm acceptance of every third-party collection model.

A UK account for a corporate collections platform receiving invoice proceeds works best when the account terms match the contracts. Finance can trace the complete history. Test a split payment and a failed refund against the proposed reporting exports before launch. Confirm that operations can retrieve the evidence without reconstructing it from emails.

FAQ

How should a corporate collections platform document invoice proceeds and refunds?

Retain invoices and their collection terms alongside bank confirmations. Each refund needs a reason and an approval reference. Add the confirmed outcome when the transfer completes.

Can a collections platform receive customer payments into dedicated IBANs?

Provider approval and the required permissions are prerequisites. The terms must establish who holds the account and how funds are treated. Dedicated IBANs assist identification; they do not automatically establish legal segregation or authorise payment services.

What records prove which client an incoming invoice payment belongs to?

The evidence should connect the client agreement and invoice to the receiving details and confirmed transaction. Remittance advice can support the allocation when references are incomplete. A matching amount alone may be insufficient where several clients have similar invoices.

Do collected funds need holding separately from the platform operating balance?

Ownership and applicable law determine the answer. The collection agreement must reflect those obligations. Funds held for clients should remain identifiable and must not be treated as unrestricted operating cash. The provider and qualified advisers should confirm the required account structure and any safeguarding obligations.