Accounts payable 101 for multi-entity owners

What is the accounts payable process, step by step?

The accounts payable process is the sequence of purchase request, commitment, invoice receipt, verification, coding, approval and payment, plus the record of each step.

Most guides describe it as a workflow inside one company with departments. If you own several companies, that description is missing the dimension that causes most of your pain: every step has to resolve to a specific legal entity, and nothing on the invoice reliably tells you which one.

Where the purchase starts, and whether it needs a PO

Payables problems are almost always purchasing problems that have aged badly. By the time an invoice reaches you the money is committed, and everything AP does afterwards is verification. If you want fewer bad invoices, you intervene at the request.

A purchase request does not need software. It needs three facts written down before the order goes out: who is asking, which entity the spend belongs to, and roughly what it will cost. The entity should be chosen by the person who knows, at the moment they know it, rather than by a bookkeeper guessing three weeks later.

A purchase order is the next step up: a commitment record created before the invoice arrives, which earns its keep on repeatable, quantity-based spend.

Use POs where you buy quantities at negotiated prices and where a vendor bills you repeatedly. Skip them for one-off professional services, utilities, insurance and rent, where there is no quantity to check and the contract or renewal notice is the commitment record. Forcing POs everywhere just teaches people to route around the process. Without a PO, verification falls to a human who remembers what was agreed: fine at low volume, expensive at high volume.

Invoice receipt: one inbox, not eleven

Every invoice should arrive at one address that no individual owns.

This is the cheapest improvement available to a group. When invoices land in the operator's inbox at one location and the bookkeeper's at another, nothing can be measured, duplicates go undetected, and a vendor billing two of your entities gets two different treatments.

Paper is a shrinking part of the problem but not a solved one. The AFP Digital Payments Survey 2025, published via Nacha, found only 26% of U.S. and Canada B2B payments are now made by check, down from 81% in 2004.

What is three-way matching, and when does it earn its keep?

Three-way matching compares the invoice against the purchase order and the receiving record before payment is released.

Quantity invoiced matches quantity received, price invoiced matches price agreed. If either fails you have an exception, and exceptions are where the cost lives.

Ardent Partners, in its AP Metrics That Matter 2025 and State of ePayables research, puts the exception rate at 9% for best-in-class AP functions against 22% on average. An exception means an email to a vendor, a wait, a follow-up, a partial credit and a re-approval. A group running 22% exceptions spends most of its AP effort on a fifth of its invoices.

Coding to the right entity is the step that breaks groups

In a single company, coding means choosing an expense account. In a group it means choosing an entity first, and that decision is the one nobody documents.

The test is consumption, not convenience. Which entity received the benefit? Not which one has cash, not which one the card was issued to. If two entities consumed it, the invoice needs splitting on a basis you can defend and repeat: headcount, square footage, revenue share, seat count, whatever fits. Write it down once per shared cost and apply it identically every month, because allocations that drift are indistinguishable from errors.

Approval thresholds: who can commit which entity to what

An approval threshold is a dollar limit tied to a named person and a named entity, and in a group it needs both halves.

Most small groups have the dollar part and skip the entity part. The result is a manager at one location approving spend that lands on another entity's books, which is not an approval but a suggestion.

A workable ladder: routine spend under a few thousand approved by whoever runs that entity, larger amounts by that person plus whoever holds group finance, and anything creating a multi-year commitment by the owner regardless of monthly size. Vendor onboarding and any change to vendor bank details sit outside the ladder and require two people, always.

That last rule is not paranoia. Payment detail changes are the most reliably exploited gap in small-group AP, and the ACFE's Occupational Fraud 2024 report, built on 1,921 cases, found that over half of frauds trace to weak or overridden internal controls. See internal controls for a small business.

The payment run

A payment run is a scheduled batch of approved invoices released per entity, and running it on a schedule beats running it on request.

Two runs a week is enough for most groups. A fixed schedule converts a stream of interruptions into a block of work. Each run is per entity, from that entity's account, in that entity's name. That sounds obvious and is violated constantly, which brings us to the wrinkles.

Three multi-entity wrinkles nobody warns you about

The same vendor billing three entities

One broker, one software vendor, one landlord, three entities, three invoices, sometimes on one statement. If the vendor record is set up once at group level, these invoices get coded by whoever opens them and the split varies.

Treat the vendor as three relationships that share a name: separate vendor records per entity, separate account numbers where they will provide them, and a note saying which entities they bill and on what cadence. Consolidated statements get split at intake, before approval, not at the close.

Shared services allocated across entities

Group-level costs are real: the bookkeeper, the group insurance policy, the head office lease, the shared software estate.

Pick one entity as payer of record per category. Have it pay the full invoice, then recharge the others on a fixed basis with a documented intercompany entry each month. Splitting the payment itself across four bank accounts looks tidier and is worse: it breaks vendor statement reconciliation and produces four partial audit trails instead of one.

The invoice paid from the wrong entity's account

This is the everyday one. An approved invoice for Entity B gets paid from Entity A's account because Entity A is where the cash was.

The moment that happens, Entity A has lent Entity B money. That is an intercompany balance: a receivable on A's books, a payable on B's, and the two sides need to agree. Left alone it surfaces months later as an unexplained difference during consolidation, which is a common cause of a late close. Record it the day it happens, and if it keeps happening, the real problem is that one entity is short of cash. See multi-entity consolidation challenges.

A worked example

A group of twelve entities renews one insurance program covering all twelve. The broker issues a single invoice to Entity A, the original holding company, because that is who signed the first policy years ago.

Handled badly: Entity A pays the whole thing and codes it to its own insurance account. Margin by entity is then wrong for twelve months, with eleven entities looking better than they are.

Handled well: the invoice is coded at intake as a shared cost with Entity A as payer of record, on a basis documented as insured payroll by entity, taken from the broker's own pricing schedule. Entity A pays the full amount in the Thursday run, and a recharge posts monthly at one twelfth of each entity's share. Twelve months later the balances net to zero and entity margins are defensible.

How long should the accounts payable process take?

Ardent Partners puts best-in-class invoice processing at 3.1 days from receipt to ready-for-payment, against an average of 17.4 days, and cost per invoice at $2.88 best-in-class against $12.88 average.

The spread is mostly exception handling, chasing approvers, and re-keying data that already existed in machine-readable form. For perspective, PYMNTS Intelligence found in 2024 that only 5% of mid-sized firms have fully automated AP and AR. If your process is manual you are not behind the field, you are the field. Fix the sequence and the entity discipline first.

Can QuickBooks or Xero do this?

Both handle the mechanics of accounts payable well inside one entity, and neither was designed for the entity dimension.

What they do well: vendor records, bills with due dates, aging reports, basic approval, attached source documents, payment recording. For a single company processing a few hundred invoices a month that is genuinely sufficient.

Where the gap opens. Each entity is a separate file, so a vendor billing three entities is three unrelated records with no shared history and no group view of what you buy from whom. Approval thresholds are configured per file, so your authority matrix lives in as many places as you have companies. Intercompany balances from cross-entity payments are yours to track by hand. Three-way matching against POs is thin, and receiving records are usually absent.

That is not a criticism; they are ledgers, and good ones. It does mean the discipline has to live in your process, and it is why AP mess is such a reliable cause of a slow close. See why your month-end close takes so long.

Where to start

If you change one thing this month, make it single-point intake. If you can change two, add an entity-coding rule at intake rather than at the close.

Then, in order: write down the approval ladder with entities attached, move to a fixed payment run, document the allocation basis for each shared cost, and reconcile intercompany balances monthly. That takes a quarter to bed in. Software helps after it, not before.

If what makes all of this hard to see clearly is the state of your books, that is what cruisr works on: current ledgers and a fast close on top of the QuickBooks Online or Xero files you already have. Get in touch.