Skip to content
FINIO

Multi-company groups

Accounts payable across your Xero companies.

A group running several companies is not a vertical we picked from a list. It is a shape, and the problems below come with it whatever you sell. Written by someone who has done a group month-end.

For UK groups with several Xero companies, or one company with several sites kept apart by tracking categories. Not built for a single site running one company.

A quiet London street at dawn with three small restaurant and cafe fronts side by side, chairs stacked outside.

Structure

Your current company structure.

Five sites, five companies, five Xero organisations: to FINIO that is one group. Every site and every ledger in one place, one close, with cross-charges posted between the companies. Many sites inside one company works the same way, on one Xero organisation with the sites kept apart by tracking categories and costs moved between them as departmental transfers.

How several Xero companies connect →Running restaurants? The hospitality version →

Across entities

Spend and exceptions across entities.

Six things that are true in almost every group, and what finance sees instead once every site's documents land in one place.

One group, several ledgers

Each site or company runs its own Xero organisation, and the group-wide view lives in a spreadsheet somebody rebuilds every month. Consolidation is a person, not a system.

The Xero connection →

Delivery notes that never arrive

The delivery note stays on site. The invoice arrives at the office weeks later with nothing to check it against, so it gets approved on the strength of the supplier being a supplier you use.

Delivery note capture →

Credit notes nobody chases

Short deliveries, rejected stock, damaged goods. Each one is worth chasing on the day and worthless to chase a month later, so a group writes off a recurring cost it never sees on a report.

Credit notes →

Price drift between order and invoice

A price agreed in a supplier negotiation, and a price on the line four months later. Nothing compares the two unless someone opens both, and nobody opens both.

Purchase orders →

Per-site P&L that arrives too late to act on

A site P&L in week three of the following month tells a GM about a problem they can no longer do anything about. It is a report rather than a control.

Cost tracking →

GP that moves without an explanation

Gross profit drops two points and the group knows it dropped. Finding out which line item did it means going back through invoices by hand, which is why it usually gets attributed to waste and left there.

Line-item extraction →

How delivery notes and invoices are matched →Spend and GP per site →

Between companies

Cross-charges.

Goods or a cost moved from one company to another is an intercompany charge. FINIO raises it the minute it happens, the receiving company agrees it, and the journals post in both Xero files. Nothing is reconstructed at month-end.

How a cross-charge posts in both →

The month

Reconciled supplier records.

Where the first week of a group month actually goes, and the part FINIO takes.

  1. 01Days one to three go to statementsEvery supplier's statement, against every site's ledger, by hand. This is where a multi-site close diverges from a single-site one.
  2. 02Days four to six go to queriesThe gaps the statements exposed. Missing invoices, unapplied credits, duplicates, each one a phone call about something that happened five weeks ago.
  3. 03Reporting gets what is leftThe part the business actually needs runs last, in the time remaining, by the person who has spent a week on data entry.

Statement reconciliation moved from around two days to one to two hours, measured in a sandbox entity at live volume.How reconciliation works →

Labelled

Supported and planned structures.

  • One company with several sites

    Sites kept apart by tracking categories on one Xero organisation.

    Live
  • Xero tracking categories

    Sites and departments posted with their tracking category.

    Live
  • Cross-charges between companies

    Raised in one company, agreed by the other, posted in both Xero files.

    Live
  • Ordinary supplier-bill approvals

    Routing every supplier bill for approval before it posts. The approval loop exists for cross-charges and transfers today; keep your existing approval tool for ordinary bills until this ships.

    Planned
  • Paying suppliers from FINIO

    FINIO shows what is ready to pay. The bank still makes the payment.

    Planned

Commercial

Pricing and fit.

Per document

You pay for each invoice, credit note and supplier statement FINIO reads, however many lines it has.

Unlimited users

Every manager, site team and accountant on the account. Adding people never costs more.

No fee per site

A new site costs nothing until it sends its first document.

How pricing works →Security and trust →

Questions

Asked before the call.

Can FINIO handle several companies with separate Xero organisations?

Yes — that is the setup it is built for. Five sites, five companies and five Xero organisations are one group in FINIO: every site and every ledger in one place, one close, with cross-charges posted between the companies.

The Xero connection →

Does FINIO work for many sites inside one company?

Yes. One company with several sites runs on one Xero organisation, with the sites kept apart by tracking categories and costs moved between them as departmental transfers. Groups where each site is its own company are supported too, with cross-charges posted between the companies.

Xero tracking categories →

Why does month-end take longer in a multi-company group?

Mostly supplier statements. A group buys from the same suppliers at every site, so one reconciliation becomes one per site, all landing in the same few days — and the gaps they expose turn into days of queries before reporting can start.

Month-end benchmark →

If any of that reads like your month, we should talk.