UK Multi-Currency Account for a UK Procurement Group with Separate Entity Billing

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

Three UK companies buy from the same suppliers, and one supplier statement covers all of them. When €30,000 leaves the bank, the line shows an amount and a date but never says which company owes it. A UK multi-currency account for procurement group with separate entity billing fixes that gap by giving every related company its own payment details and its own record of what moved. The sections below cover the account models on offer, the way virtual IBANs route money, and the records finance teams keep for HMRC.

[aa key-takeaways]

Key Takeaways

1. Separate billing begins with structure: each legal entity gets its own payment details, so every payment has an owner from day one.

2. Groups choose between three account models, and each model strains at a different size.

3. A virtual IBAN gives an entity its own number while balances sit in one underlying account, which shortens month-end matching.

4. Shared supplier invoices are split by a fixed key before payment, for example 50/30/20.

5. UK companies keep separate accounting records, so intercompany payments carry a reference naming both sides.

[aa btn]Book a Call[/aa]
[/aa]

UK Multi-Currency Account for a Procurement Group: How the Model Works

Every group payment answers one question: which company does it belong to. Currency adds a second layer, because a supplier may invoice in GBP one month and EUR the next.

What Is a Multi Currency Account

A multi-currency account holds balances in several currencies side by side, so a business can receive euros and pay a euro invoice without converting to sterling first. Conversion happens only when the holder chooses it. For one company, that removes an FX step from each payment. A group faces a new problem: several firms share currencies, and every balance needs an owner.

Most providers here are electronic money institutions (EMIs) authorised by the Financial Conduct Authority. The FCA sets safeguarding requirements for them, which keep client funds apart from the provider's own money. EQWIRE operates under this FCA regime for electronic money.

Onboarding follows the same logic. Each subsidiary passes its own checks and holds its own balance, which means a group with six firms handles six separate files.

Best Multi Currency Business Account UK: What a Group Should Check

Searches for the best multi currency business account UK return lists written for single companies. Groups need a different checklist, built around five questions:

• Does each entity get its own statement and payment details?

• Can one finance user see every entity while permissions limit who can pay?

• Which currencies stay in their original form, and which convert on receipt?

• Who sets the rail limits?

• Do references survive into the statement?

Answers to these matter more than headline fees. A cheap product that mixes three companies in one statement costs more in accountant hours than it saves.

Multi Entity Business Account UK: Structure Options

A multi entity business account UK setup takes one of three shapes, chosen by headcount of entities and shared suppliers.

One Account per Entity

Each company opens an account with its own IBAN and statement. Separation is complete, and one entity's records never touch another's. Administration pays for that clarity: three companies mean three logins and three onboarding files. Every balance also needs its own top-up. Groups with two or three entities often accept the load.

A common question is whether a business may hold more than one bank account. It may. UK law sets no general limit on the number a company opens, although each provider applies its own onboarding rules.

Parent Structure with Entity-Level Details

Here a main account sits on top, and the parent controls funding and access. Each entity receives its own reference or IBAN for incoming payments, and finance teams filter the group total by company.

Provider support varies, so terms need checking early. Owners based outside the UK add extra checks, and groups with non-UK owners should expect a longer file review.

Where the Multi Entity Model Breaks

Models fail at scale and at legal boundaries. Beyond roughly ten entities, manual reference codes slip because somebody forgets one. Shared balances add a second risk. Money that belongs to one firm can settle another firm's supplier bill, and nothing on the statement reveals the loan.

Virtual IBAN Account for Business and Entity Billing

A virtual IBAN account for business hands each company a personal IBAN while all funds land in one underlying account. Suppliers and customers pay whichever number fits the counterparty, and the provider credits the matching balance.

[aa fast-fact]
Fast Fact: An IBAN starts with a two-letter country code and two check digits, followed by a national account number of up to 30 characters. The number alone identifies the receiving party.
[/aa]

Named IBAN vs Virtual IBAN

A named IBAN carries the holder's own name in the payee details. A virtual IBAN works as a routing number pointing to a main account, and it may show a different name. Some suppliers check the payee name before they release goods, and a mismatch delays the order.

A named IBAN account puts the company name on the payee line. Customers pay the right party at once. Invoice collections then run with far fewer queries to finance, since nobody has to guess who a transfer was meant for.

How Incoming References Map to Entities

Take a group whose trading arm holds its own virtual IBAN, and picture a customer sending £12,400 there with an invoice number attached. The IBAN routes the credit to the trading arm, and the quoted text ties it to one bill. Sister firms see nothing. Their statements stay untouched, which is the whole point of the setup, and month-end matching shrinks to a filter on one statement.

Setup follows four steps:

1. Every entity onboards and receives payment details.

2. The group agrees a reference format, for example entity code plus invoice number.

3. Suppliers and customers receive the IBAN of the company that owes or is owed money.

4. Finance exports statements per entity at month end.

Groups holding euro and sterling balances repeat these steps once for each currency.

[aa cta]

Separate details for every entity in the group

EQWIRE multi-currency accounts give each onboarded entity an IBAN and a statement of its own, so payments never land in a shared pile.

[aa btn]Open a Group Account[/aa]
[/aa]

Currencies and Rails Inside a Group Setup

Each currency runs on its own payment rail, and every rail has limits and hours. A supplier payment that misses a cut-off lands a day late, so groups plan around those windows.

GBP via Faster Payments and CHAPS

Faster Payments carries most UK sterling transfers, and Pay.UK raised the limit to £1 million per payment. Providers set lower ceilings of their own, so a large supplier run starts with a limit check.

CHAPS, operated by the Bank of England, settles large-value sterling payments in real time during operating hours. Property completions and other high-value transfers go this way.

EUR via SEPA and USD via SWIFT

SEPA, the Single Euro Payments Area, gives euro transfers common rules across the EU and several neighbouring countries. The European Central Bank describes it as one standard for euro payments. Where a supplier accepts instant euro payments, funds arrive within seconds, though availability varies by bank.

Dollars and most other currencies move over SWIFT, where a correspondent bank may sit between sender and receiver. Fees and timing depend on that chain, so a group asks for the cost of a dollar payment before its first supplier run.

Rails also decide how much detail travels with the money. SEPA transfers carry a structured reference field. SWIFT messages can truncate long references, which makes a short entity code safer than a full sentence.

Allocating Shared Supplier Costs Between Entities

Shared supplier costs cause more reconciliation errors than any other item in a group. One invoice covers goods for several firms, and somebody must decide who pays what.

Allocation Before Payment vs After

Finance teams looking for the cleanest way to allocate shared supplier costs between entities agree a key before the invoice arrives. Purchase volume, headcount or revenue can drive the key. Timing matters most.

Splitting after payment carries a price. One company pays the full bill, then the team books intercompany balances to recover the other shares. Every balance turns into a debt between two legal entities.

An illustrative example, not real data: a €30,000 invoice split 50/30/20 gives €15,000, €9,000 and €6,000. Fix the key first, and each entity settles its own share from its own balance. Settle it later, and one entity pays €30,000 and books €15,000 of receivables.

Currency adds a wrinkle. When a sterling entity pays a euro share, conversion happens at payment. At an illustrative 1% margin, converting €15,000 costs €150. Entities that hold euros already avoid that charge, which favours a separate euro balance per company.

Keeping the Audit Trail per Entity

An audit trail joins four records: the invoice, the allocation key, the payment and the statement line. If each company pays only its own share, all four sit in that company's file, and the auditor follows one path.

When one company pays the full invoice, a fifth record appears, the intercompany agreement. It states the amount and the settlement date, and it names the currency.

Onboarding and Controls for a Multi-Entity Setup

Opening several accounts at once takes planning. Compliance teams at the provider review each firm separately, so the slowest file sets the launch date.

Documents Each Subsidiary Prepares

Expect a request for the certificate of incorporation, the registered address, a list of directors and details of anyone who owns 25% or more. Ownership charts save time here. A subsidiary held through a holding company needs the full chain drawn out, down to the individuals at the top.

Trading details come next. Providers ask what the company sells, which countries its payments touch and the monthly volume it expects. Procurement groups often forget to state the supplier countries, and a vague answer triggers follow-up questions that add days.

Build one folder for the group and one sub-folder per entity. Then an updated shareholder register reaches the provider within minutes, with no search through email.

Permissions and Approval Limits

Separate billing only helps if the wrong person cannot pay the wrong entity, so access rules matter as much as IBANs. Most business platforms let the account owner set roles: a viewer sees balances, a preparer drafts payments, an approver releases them. Groups map these roles to the finance structure.

A typical layout gives the group controller viewing rights on every entity and approval rights on none. Local finance managers approve payments for their own company only. Dual approval above a set amount, for example £25,000, adds a second pair of eyes to large supplier runs. Ask the provider whether approval rules can differ per entity, since some platforms apply a single rule to the whole account.

The Month-End Routine

A working close takes four passes. Export the statement for each entity and each currency. Match every line to an invoice or an intercompany agreement. Flag anything without a match and chase it within two working days. Post the group-level view last, once each entity ties out on its own.

Teams that follow this order rarely hit surprises, because errors surface at entity level where the context is fresh. A missing reference on a €4,000 payment takes minutes to solve on day one and hours to solve after the ledgers lock.

Automation helps with volume. Many providers offer statement exports in CSV or through an API, so an accounting package can pull entries by entity overnight. Check the export format early, because a file with a combined reference column can force manual splitting.

Choosing a Provider for a Group

Feature lists look alike, so a group tests the details that affect daily work. Five questions separate suppliers of group-ready accounts from the rest:

• How many entities can sit under one login, and does each keep its own onboarding record?

• Can a new IBAN be issued without a fresh application?

• What happens to a payment that arrives with a wrong or missing reference?

• Which currencies can a company hold, and what is the conversion margin when it swaps?

• Can support staff answer questions about a specific entity without the parent calling in?

Ask for a demonstration with three dummy entities. Watching a provider set up sample IBANs shows more than a brochure does, and it exposes hidden steps such as manual approvals on the provider's side that can stretch a launch from days into weeks.

Intercompany Payments and HMRC Traceability

Every UK limited company must keep books of its own. GOV.UK guidance on company and accounting records explains what those records cover and how long a company holds them.

Payments between related parties deserve extra care. HMRC's International Manual covers transfer pricing, the rules for pricing dealings between connected businesses. Whether a given payment falls inside those rules depends on the facts, so a qualified tax adviser should review it.

Traceability rests on three routines.

• The reference on each intercompany payment names the sender and the receiver.

• Every payment links to an invoice or a written agreement.

• Statements are stored per company, not per group.

A UK multi-currency account for procurement group with separate entity billing supports them from the first transfer, since every statement already names its owner. Without it, someone rebuilds the trail at year end by hand, and gaps appear.

FAQ

How can a group separate billing between related UK companies and currencies?

A group separates billing by giving each company its own payment details and its own statement per currency. In practice that means one IBAN per company and a fixed reference format, with statements exported entity by entity. Each balance then appears on one statement only.

Suppliers pay the firm that owes the money. Finance staff match every credit or debit to a single legal entity, without cutting a shared statement apart by hand.

Can one account provide separate IBANs for each group entity?

Yes, if the provider supports virtual or named IBANs per entity. Incoming money reaches the main account, and the number tells the provider which company it belongs to.

Every entity still onboards on its own. Provider terms decide how many IBANs one account holds, so ask for that limit first. Then check the statement format, and look at the name shown on the IBAN before any supplier receives it.

What is the cleanest way to allocate shared supplier costs between entities?

The cleanest way is a fixed key agreed before the invoice arrives, with each entity paying its share from its own balance. A key tied to purchase volume, headcount or revenue stays defensible in an audit.

Paying the whole invoice from one company and recovering shares later creates intercompany debts. Each debt needs paperwork. A group with many shared suppliers documents the key once and reuses it.

Does HMRC expect intercompany payments to be traceable per entity?

Yes, in practice. Each limited company keeps its own records, so an intercompany transfer lands in two sets of books, and HMRC applies transfer pricing rules to dealings between connected businesses.

A reference naming both sides and pointing to an invoice or agreement makes the trail easy to follow. Requirements differ from group to group. A qualified adviser should confirm the details before the first payment goes out.

Early choices shape every later close. A group that gives each firm its own IBAN and one reference format, then fixes an allocation key, spends its finance hours on analysis. Groups that skip this work spend them on repairs, and auditors notice the difference. A UK multi-currency account for procurement group with separate entity billing turns those choices into daily routine. Firms weighing providers can compare what EQWIRE's business account offers to groups, and then test it with two or three entities before rolling it out to the rest.