What inter-entity procurement looks like in a financial services group
Inter-entity procurement is any purchase made by one entity in a corporate group for the use or benefit of another entity in the same group, with the cost later recharged through intercompany entries.
Financial services groups are built from separate legal entities for good reasons: a regulated bank, a broker-dealer, an NBFC or lending arm, a payments company, a technology services entity. Each has its own license, capital rules and books. Vendors do not care about that structure. One cloud contract, one fraud screening tool or one audit firm often serves all of them, so someone has to decide who pays and who gets charged. In a Deloitte webcast poll of more than 3,900 accounting and finance professionals, 40.6% said their organizations would increase the time and effort put into intercompany accounting.[1]
Here is how it usually plays out. The group technology entity signs a data vendor contract for the whole group. The invoice lands in its AP inbox and is booked in full. Three months later, finance opens a spreadsheet, estimates how much the bank, the card issuer and the lending arm each used, and posts recharges. The lending arm's controller disputes the share, the bank books its side a month late, and the intercompany balances no longer tie out before the consolidation deadline.
CFO / Finance Leader
Consolidation is held up by intercompany breaks that nobody can explain quickly, and regulators or auditors ask why charges moved between entities.
"Why do our own entities disagree about what they owe each other?"Group Controller
Spends the last week of every quarter matching recharges by email with entity accountants in different time zones.
"I have 40 open intercompany breaks and the close is Friday."Procurement Head
Negotiates group contracts but has no record of which entity asked for what, so allocation is guesswork.
"I bought it for the group. Nobody told me who it was really for."Entity CFO or Business Unit Head
Receives a recharge months later with no detail and cannot tell whether the share is fair.
"What is this charge, and why is it half of the total?"Are cross-charges between your entities still done by hand?
Tick every statement that is true today. Three or more means the problem is likely costing you real money.
Six root causes behind manual cross-charges
Reconciliation pain shows up in finance, but it usually starts much earlier, at the point where someone asks to buy something for more than one entity.
The beneficiary is never captured at request time
Requests name the buying entity and cost center but not who will use the service. Finance has to reconstruct that months later from memory and email.
Allocation keys are informal
Headcount, accounts, transaction volume or a fixed split: the basis for sharing each contract is rarely written down, approved or applied consistently across periods.
Group contracts are signed by one entity
A single legal entity holds the vendor contract for convenience, so every invoice flows through its AP even when it consumes a small share of the service.
Entities run separate ledgers and vendor records
The same vendor exists under different names and IDs in each entity's books, so matching spend across the group needs manual mapping.
Recharges are batched at quarter end
When cross-charges are raised once a quarter, the detail behind each purchase has gone cold and disputes take longer to resolve.
One side books, the other side waits
The charging entity posts its receivable, but the receiving entity books its payable only after review, so timing breaks appear every period.
What manual inter-entity charging costs a financial services group
Intercompany work is a known pressure point for finance teams, and data quality sits at the center of it.
The direct cost is finance time: controllers and entity accountants matching lines, chasing backup and reposting entries every quarter. The indirect costs weigh more in a regulated group. Late or disputed recharges distort entity results that feed capital and liquidity reporting, weak documentation invites questions from auditors and tax authorities about arm's length pricing, and consolidation deadlines slip while breaks are cleared.[2] Procurement also negotiates renewals blind because nobody can show true group volume by vendor.
Estimate the cost of reconciling cross-charges by hand
Enter your figures. Nothing is stored or sent anywhere.
The expert playbook: six practices that take the manual work out of cross-charges
These practices work with any ERP or even spreadsheets. The principle is simple: decide who benefits when the purchase is requested, and let the recharge follow from that record.
"At KPMG I worked on global procurement transformation for groups with many entities, and the pattern was always the same. The group signs once, the invoice lands in one entity, and finance spends the quarter guessing who benefited. If the request says which entities will use the service and on what split, the cross-charge writes itself."Md. Kafil, Co-founder and CEO, Zapro. Former senior product specialist on SAP Ariba Network and procurement transformation manager at KPMG.
Capture the beneficiary entity on every request
Write down and approve allocation keys
Keep one vendor record across the group
Raise recharges when the invoice is approved
Post both sides of each entry together
Reconcile monthly by counterparty pair
"At Voonik thousands of suppliers emailed invoices into one inbox and called to ask where their payment was. Intercompany charges have the same problem, only the supplier is your own sister entity. When the charge arrives late and without backup, people stop trusting it. Send the detail with the charge, the day it happens."Daniel Sagayaraj, Co-founder and CTO, Zapro. Previously built and ran supplier onboarding and payments for a 15,000-supplier marketplace at Voonik.
How Zapro links group purchases to the entities that use them
Zapro records the requesting and benefiting entities when a purchase starts, keeps shared vendors and contracts in one place across legal entities, and passes clean, entity-tagged data to each ledger through ERP sync.
| Root cause | Zapro capability | What changes |
|---|---|---|
| Beneficiary not captured at request | Procurement: purchase requests and "Prompt to buy" with Z1 | Requests carry the entities that will use the purchase, so allocation starts with facts instead of estimates. |
| Entities keep separate vendor records | Vendor Management: centralized vendor profiles | One profile per vendor across the group, with documents and conversations in one place. |
| Group contracts held by one entity | Contract Management | Shared contracts, versions and renewal alerts sit in one repository that every entity's finance team can see. |
| Ledgers out of step | Integrations: two-way ERP and accounting sync | Vendor and master data sync with legal entities and accounts aligned, so each ledger receives the same record. |
| No view of group spend by entity | Spend Analytics | Spend by vendor and category across entities in one dashboard, ready for allocation reviews and renewals. |
Zapro syncs vendor and master data two ways with your ERP or accounting system and keeps legal entities and accounts aligned, so intercompany postings stay in your general ledger where they belong. See Zapro integrations and Zapro for Financial Services.
A 30, 60, 90 day plan
Days 1 to 30: Map the flows
- List every vendor shared by two or more entities
- Pull last year's recharges and open breaks
- Document the current allocation basis per contract
- Agree entity owners for each counterparty pair
Days 31 to 60: Fix the inputs
- Add beneficiary entity fields to requests
- Approve allocation keys with entity CFOs
- Merge duplicate vendor records across entities
- Pilot monthly recharges on the top 10 shared vendors
Days 61 to 90: Run it monthly
- Extend to all shared vendors
- Post both sides of recharges in the same period
- Start monthly counterparty reconciliations
- Review allocation keys against actual usage
KPIs to track progress
| KPI | How to calculate | Review |
|---|---|---|
| Beneficiary capture rate | Shared-vendor requests with benefiting entities recorded divided by all shared-vendor requests | Monthly |
| Open intercompany breaks | Count and value of unmatched intercompany balances at month end | Monthly, by entity pair |
| Recharge lag | Average days from vendor invoice approval to recharge posting | Monthly |
| Disputed recharges | Recharges challenged by the receiving entity divided by recharges issued | Quarterly |
| Allocation key coverage | Shared contracts with an approved, current allocation key | Quarterly |
| Days to clear intercompany at close | Working days from period end until all intercompany balances agree | Each close |
Go deeper with our guide to procure-to-pay process.
What a Zapro customer saw after moving this work into one workflow
"Zapro's strategic sourcing tools have allowed us to negotiate superior contracts and realize significant cost savings."Frank Esmeijer, Vice President Development, Bob W
Why Zapro for this challenge
Cross-charges are hard because the facts behind them are lost at the moment of purchase. Zapro captures those facts in the request and carries them through the vendor, contract, invoice and ledger, so the recharge follows from records rather than reconstruction.
Entity context from the first click
Requests, approvals and POs carry the entities involved, so allocation is not rebuilt later from email.
One vendor and contract record for the group
Shared suppliers and their contracts live once, with entity-level visibility, instead of in five separate ledgers.
Two-way ERP sync with entities aligned
Vendor and master data flow to each entity's books with legal entities and accounts kept consistent.
Audit trail on every change
Approvals and edits are logged, which helps when auditors or tax teams ask how a charge was decided.
When Zapro may not be the right fit
- You operate a single legal entity or a group where entities never share vendors. Standard procurement and AP controls will cover you.
- Your main need is intercompany netting, settlement and elimination entries inside the ledger. That work belongs in your ERP or a dedicated close tool, which Zapro feeds rather than replaces.
- You need transfer pricing studies or benchmark documentation. That is specialist tax work, although Zapro's records can support it.
Frequently asked questions
What is an inter-entity or intercompany cross-charge?
A cross-charge is an entry in which one entity in a group bills another for goods or services it bought or provided on the other's behalf. In financial services it commonly covers shared technology, data vendors, office space, audit fees and outsourced operations used by several licensed entities.
Why do intercompany balances not match at quarter end?
The most common reasons are timing (one entity books before the other), disputed allocation shares, different vendor or account mappings in each ledger, and missing backup. Most of these start with information that was never captured when the purchase was requested.
How should shared vendor costs be allocated between entities?
Pick a basis that reflects how each entity uses the service, such as headcount, customer accounts, transaction volume or a fixed agreed split. Document it, have it approved by each entity's finance lead, apply it consistently and review it at least once a year. Your tax advisers should confirm the approach meets transfer pricing rules in each jurisdiction.
Should each entity sign its own vendor contracts instead?
Sometimes, especially where regulators expect a licensed entity to hold its own outsourcing agreements. Often a group contract with clear usage rights for named entities is cheaper and simpler. What matters is that the contract, the allocation basis and the recharge trail are recorded together.
Can procurement software handle intercompany accounting?
Procurement software handles the front end: who asked, who benefits, what was agreed and what was invoiced. Intercompany netting, eliminations and consolidation stay in the ERP. Tools like Zapro make the ledger work easier by sending entity-tagged, approved data into it.
About the experts behind this page
Sources
- Deloitte via PR Newswire, Intercompany Accounting to Get More Support From Many in Year Ahead, 2022
- Deloitte Center for Controllership, Managing intercompany: Navigating new challenges and tax complexities
Editorial note: this page is published by Zapro, which sells procurement software. Best practices are written to work with any tool, and figures are cited to their original publishers. Last reviewed 29 September 2026; next review due March 2027. See how the Procurement Challenges Directory is researched and reviewed.