Charges With a Reason: A Transfer-Price Discipline for Shared Services in Mid-Market Portfolios

Shared services are one of the most visible promises of a connected portfolio. A parent invests in finance, information technology, human resources, procurement, or compliance and expects portfolio companies to benefit from scale. Yet the moment those services are charged back through an internal invoice, the promise can become a source of friction. A company that cannot trace a charge to a service, a driver, and a decision will treat the invoice as a tax on belonging. Cooperation declines, and the synergy that justified the center begins to look theoretical.

The solution is not to stop charging. It is to make the charge legible. A management transfer-pricing model—separate from tax transfer pricing—should answer three questions for every portfolio company: what did I receive, how was my share calculated, and what can I do if the answer is wrong? The discipline below is designed for mid-market holdcos that need practicality more than perfection.

Begin With a Service Catalog, Not a Spreadsheet

Most internal-charge disputes begin before the invoice is issued. They begin when the center treats a general ledger as a service catalog. Finance teams then allocate whatever costs happen to sit in a department, including costs that have little to do with the portfolio company receiving the charge.

A workable model starts with a plain-language catalog. For each shared service, document the service owner, the unit of delivery, the service level, the eligible users, and the reporting frequency. Finance shared services might include accounts payable, payroll support, and management reporting. Information technology might include help-desk support, cybersecurity monitoring, and infrastructure hosting. Procurement might include category management and vendor negotiation.

The catalog should also separate three kinds of cost. Direct pass-through costs are tied to a specific company, such as a dedicated license or a one-off project. Shared platform costs support multiple companies and require an allocation driver. Center-only costs—parent strategy, investor relations, deal origination, and group-level legal work—should not be allocated to portfolio companies at all. If a cost cannot be tied to a service received by a portfolio company, it belongs above the line, not in the invoice.

This distinction does more than improve accuracy. It protects the credibility of the entire charge model. Portfolio leaders are often willing to pay for services they can see. They resist paying for the parent's own overhead when it arrives disguised as a shared service.

Choose Drivers That Match Consumption

Allocation drivers are where transfer pricing becomes either convincing or arbitrary. Revenue is a convenient driver, but it is rarely a fair one. A large portfolio company with a stable business may use very little help-desk support, while a smaller company in a growth phase may generate a disproportionate share of tickets and onboarding work.

The better approach is to match the driver to the service. Headcount may fit human resources administration. Ticket volume may fit information technology support. Invoice count may fit accounts payable. Procurement spend may fit category management. Seats or active users may fit software platforms. Where a single driver distorts behavior, use a blended driver with published weights rather than forcing every service into one metric.

Document the source of each driver, the refresh cadence, and any caps or floors. Caps are especially useful for mid-market portfolios because they prevent a single unusual year from producing a charge that feels punitive. A driver should be plausible to a plant manager, not only defensible to a finance theorist.

Publish a Rate Card and a True-Up Rule

Predictability matters as much as precision. Portfolio companies budget months in advance, and an internal charge that arrives without warning can disrupt capital plans and damage trust. The center should publish a rate card before the budget cycle begins. The rate card should show standard rates, expected volumes, and the method for handling variances.

A simple structure works well. Use a fixed fee for stable services such as core finance systems support. Use a variable charge for services that track consumption, such as transaction processing or help-desk tickets. Apply a quarterly estimate and an annual true-up, with a stated cap on supplemental charges. If the center expects a material overrun, it should raise the issue in the quarterly service review rather than waiting for a year-end adjustment.

As portfolio companies finalize 2027 plans in late 2026, the charge model should be part of the budget conversation, not an afterthought. A rate card that arrives after budgets are locked is not a pricing tool. It is a source of unnecessary conflict.

Give Disputes a Route and a Remedy

A charge model without a dispute process is an assertion, not a system. Portfolio companies need a defined way to question a charge without turning every question into a referendum on shared services.

Start with service-level agreements that make the charge meaningful. If the center commits to response times, close cycles, or reporting deadlines, the invoice should reference those commitments. When service levels are missed, the remedy should be proportionate: a service credit, a correction, or a documented improvement plan. The remedy does not need to be punitive. It needs to be real.

Disputes should have a short escalation path. The portfolio company raises the issue with the service owner. If unresolved, it moves to a shared-services review forum that includes portfolio finance leaders. That forum should have authority to correct errors, adjust drivers, and recommend changes to the rate card. It should not have authority to reopen the strategic case for shared services every month. The purpose is to resolve specific charges, not to relitigate the portfolio model.

Make Annual Transparency a Board-Level Deliverable

Once a year, the center should publish a shared-services report written for portfolio company chief executives, not only for the parent's finance team. The report should show total cost pools, allocation drivers, rates, variances, service-level performance, and a comparison with external benchmarks where credible benchmarks exist. It should also explain the synergy premium: what the portfolio gained from central coordination, what it paid for that coordination, and where the center intends to improve.

Transparency is not a gesture of goodwill. It is a control. When portfolio leaders can see the full picture, they are less likely to assume the worst about a line item. When the center must explain its costs annually, it is less likely to let unproductive overhead accumulate in shared-services budgets.

Run the Model on a Calendar

A transfer-price system fails quietly when it becomes an annual surprise. Put the model on a calendar. Issue monthly statements with enough detail to be checked. Hold quarterly service reviews with portfolio finance leaders. Conduct an annual reset of rates, drivers, and service levels before the next budget cycle. Assign one owner for data quality and one forum for dispute resolution.

The calendar matters because internal charges are not merely accounting entries. They shape behavior. A portfolio company that understands its invoice can make better decisions about service consumption, staffing, and investment. A center that understands its charges can make better decisions about capacity, pricing, and what it should stop doing.

The internal invoice is a governance instrument. Used carelessly, it turns collaboration into resentment. Used with discipline, it gives portfolio companies a reason to see shared services as a genuine source of value. At The Synergy Companies, the measure of a shared-services model is not whether the center can recover cost. It is whether portfolio leaders can defend the charge to their own teams and still see the value of connection.