Recharges in accounting are journal entries that shift shared costs from the department or legal entity that paid the invoice to the departments or entities that actually used the service. Within a single company, a recharge moves cost between cost centers so each manager’s profit-and-loss statement reflects real consumption. Between separate legal entities under common ownership, a recharge creates a receivable on one balance sheet and a payable on the other, and it pulls the transaction into transfer pricing rules, sales tax rules, and related-party disclosure requirements. The mechanics look similar. The consequences are not.
Departmental Recharges and Intercompany Recharges Are Not the Same
The first question to answer on any recharge is whether the provider and the consumer sit inside the same legal entity. Treating the two the same way is the most common setup mistake.
A departmental recharge stays inside one company. IT pays the cloud hosting bill, then pushes a share to marketing, operations, and sales based on usage. Nothing leaves the legal entity. No receivable or payable is created. The exercise nets to zero on the general ledger and exists purely to give unit managers accurate P&Ls.
An intercompany recharge moves cost between two legally separate subsidiaries. When a U.S. subsidiary provides centralized accounting to a Canadian subsidiary, the transaction creates a real receivable and a real payable. Those balances get eliminated in consolidation, but while they exist they carry tax weight. Intercompany recharges fall under transfer pricing rules, require arm’s length pricing, and demand documentation that departmental recharges never need.
Building the Shared Cost Pool
Before you allocate anything, you need a clean pool of costs to allocate. Costs that trace directly to one department stay there. The recharge mechanism exists for indirect costs: expenses shared across units that can’t be assigned to a single consumer without a formula.
Typical pool candidates are IT infrastructure (servers, networks, cybersecurity, help desk), facilities (rent, utilities, janitorial, security), and centralized corporate functions (HR, payroll, legal, internal audit, finance).
Not everything belongs. Costs that don’t benefit the receiving department, or that relate to the parent’s own governance obligations rather than services consumed by subsidiaries, should be excluded. Shareholder-related costs like annual report preparation, board expenses, and stock exchange listing fees are classic examples. Fines, penalties, and lobbying expenses generally stay out. Including non-allocable costs inflates the recharge and, in the intercompany context, creates transfer pricing exposure by charging subsidiaries for services they never received.
Choosing an Allocation Method
The allocation method is the formula that divides the pool. The right choice depends on what actually drives the cost.
Usage-Based Allocation
Usage-based allocation ties the recharge to measured consumption. If the print center spent $50,000 last quarter and your department printed 30% of the pages, you absorb $15,000. Cloud costs split by storage consumed or processing hours used follow the same logic. This is the most accurate method, but it needs reliable tracking. If you can’t measure consumption, you can’t use it.
Activity-Based Allocation
When direct usage data isn’t available, tie the cost to an activity that correlates with the expense. Payroll processing allocated by employee count per department is the textbook case. HR recruiting costs allocated by open positions filled per unit is another. Activity-based allocation works well for administrative functions where workload scales with a countable driver.
Proportional Allocation
This is the fallback when neither usage nor activity data exists. Distribute costs by a general measure of size: square footage for facilities, headcount for general administration, or revenue share for something broader. It’s easy to run and blunt in its results. A department occupying 20% of the floor space absorbs 20% of the facilities cost whether it uses the building heavily or barely at all.
Many organizations combine methods, using usage-based allocation where systems support it and proportional allocation for everything else. Two rules apply either way. The allocation base has to have a logical connection to the cost. Allocating legal department costs by square footage makes no sense because floor space doesn’t drive legal work. And the method has to stay consistent period over period. Switching mid-year distorts trend analysis and draws questions from auditors and tax authorities.
Recording a Departmental Recharge
Inside a single legal entity, the journal entry moves cost between cost centers using an interdepartmental clearing account.
The providing department credits either its original expense account or a designated cost-recovery account. That reduces its reported expenses, reflecting the fact that it incurred the cost on behalf of others. The receiving department debits an allocated expense account with a descriptive name like “Allocated IT Services” or “Shared Facilities Charge,” so anyone reading the P&L can distinguish recharged costs from expenses the department incurred directly.
Both sides flow through a clearing account. If IT is recharging $10,000 to marketing, the entry debits “Allocated IT Expense” in marketing’s cost center for $10,000 and credits “IT Cost Recovery” in IT’s cost center for $10,000, with the clearing account bridging the two. At the end of any reporting period, the clearing balance should be zero. If it isn’t, one side posted and the other didn’t, and the difference needs to be found before close.
The whole recharge exists only in the management reporting layer. On external financial statements, the expense still sits in whatever line item it originally belonged to. Departmental recharges reshuffle internal P&Ls without changing total reported expenses.
Recording an Intercompany Recharge
When the recharge crosses legal-entity lines, the accounting gets heavier. Instead of a clearing account, you create balance sheet positions on both sides.
The providing subsidiary debits an intercompany receivable (“Due From Subsidiary B”) and credits either the original expense account or an internal services revenue account. The receiving subsidiary debits its allocated expense account and credits an intercompany payable (“Due To Subsidiary A”). These reciprocal balances must match exactly. A $25,000 receivable on one set of books has to correspond to a $25,000 payable on the other.
They often don’t. Intercompany reconciliation is one of the most tedious parts of the close for a reason. Timing differences are the usual culprit: one entity posts in March, the other doesn’t record until April. Currency conversion creates small but persistent gaps in multinational groups. Coding errors send charges to the wrong intercompany partner. Any unresolved difference means the accounts won’t eliminate cleanly in consolidation.
Under U.S. GAAP (ASC 810-10-45-1), all intra-entity balances and transactions must be eliminated in consolidated financial statements. The consolidated entity is treated as a single economic unit, so intercompany receivables, payables, revenues, and expenses disappear from the combined statements. A recharge that doesn’t eliminate cleanly inflates both assets and liabilities on the consolidated balance sheet, which is the kind of error auditors find fast.
Transfer Pricing Rules Apply to Every Intercompany Recharge
The moment a cost recharge crosses from one legal entity to another within a controlled group, transfer pricing rules attach. The IRS has authority under Internal Revenue Code Section 482 to reallocate income and deductions between related entities whenever necessary to prevent tax avoidance or clearly reflect income.1Office of the Law Revision Counsel. 26 U.S. Code 482 – Allocation of Income and Deductions Among Taxpayers
The governing standard is the arm’s length principle: every controlled transaction must produce results consistent with what unrelated parties would have agreed to under comparable circumstances.2GovInfo. 26 CFR 1.482-1 – Allocation of Income and Deductions Among Taxpayers A U.S. subsidiary can’t overcharge a foreign affiliate for shared accounting services to shift profit out of a higher-tax jurisdiction. If the IRS decides the price doesn’t reflect what an independent provider would have charged, it adjusts the income of both parties and assesses penalties.
Methods for Pricing Intercompany Services
The Treasury regulations set out specific methods for pricing service transactions under 26 CFR 1.482-9. These are distinct from the methods used for tangible property transfers, and pulling from the wrong set is a common error. The principal options are the comparable uncontrolled services price method (benchmarking against what independent parties charge for similar services), the cost of services plus method (total cost plus an arm’s length markup), and the comparable profits method (evaluating profitability of comparable uncontrolled companies).3eCFR. 26 CFR 1.482-9 – Methods to Determine Taxable Income in Connection With a Controlled Services Transaction
For routine back-office support, a simplified option exists: the Services Cost Method. Qualifying services can be charged at total cost with no markup.3eCFR. 26 CFR 1.482-9 – Methods to Determine Taxable Income in Connection With a Controlled Services Transaction To qualify, the service must be a “covered service,” meaning either it appears on the IRS’s specified list of common support services or it’s a low-margin service where the median comparable markup on total costs is 7% or less. The taxpayer must also reasonably conclude that the service doesn’t contribute significantly to the controlled group’s competitive advantages or core capabilities. Payroll processing, basic accounting, and data entry are typical candidates. Manufacturing, R&D, financial transactions, and engineering services are explicitly excluded.
The Services Cost Method is underused. Many multinational groups default to applying a markup on every intercompany service charge when some would qualify for a cost-only approach. That unnecessary markup creates taxable income in the providing entity and an inflated deduction in the receiving entity, drawing scrutiny from both sides’ tax authorities.
Documentation and Penalties
Documentation is the single most important defense when the IRS challenges an intercompany recharge. The regulations require transfer pricing documentation to exist when the tax return is filed, not to be assembled later during an audit.4Internal Revenue Service. Transfer Pricing Documentation Best Practices Frequently Asked Questions If the IRS requests it, you have 30 days to produce it.5Internal Revenue Service. The Section 6662(e) Substantial and Gross Valuation Misstatement Penalty
Required documentation includes an overview of the business, a description of the organizational structure, the transfer pricing method selected and the reasons for choosing it, the methods considered and rejected, a description of comparable transactions used for benchmarking, and the economic analysis supporting the pricing. The documentation must demonstrate that the method selected provides the most reliable measure of an arm’s length result.5Internal Revenue Service. The Section 6662(e) Substantial and Gross Valuation Misstatement Penalty
The penalties are substantial. A 20% accuracy-related penalty applies when the transfer price on the return is more than double or less than half the correct arm’s length price, or when the net Section 482 adjustment for the year exceeds the lesser of $5 million or 10% of gross receipts. The penalty doubles to 40% for gross valuation misstatements, where the price is off by a factor of four or the net adjustment exceeds the lesser of $20 million or 20% of gross receipts.6Office of the Law Revision Counsel. 26 U.S. Code 6662 – Imposition of Accuracy-Related Penalty on Underpayments Adequate contemporaneous documentation is the primary way to establish the reasonable cause and good faith exception that avoids these penalties.
Sales and Use Tax on Intercompany Recharges
Transfer pricing gets the attention. Sales and use tax can hit just as hard and often catches companies off guard. Unlike income tax, where intercompany transactions wash out on consolidation, sales tax treats each legal entity as a separate taxpayer. A service recharge from a parent to a subsidiary is a taxable transaction in states that tax the underlying service category, common control notwithstanding.
State rules vary. Some states exempt services between entities that meet a common-ownership threshold. Others tax all taxable services with no related-party exception at all. Whether a management fee, IT charge, or equipment lease between affiliates triggers tax depends on the specific service category, where the service is performed or received, and the ownership relationship. Companies that build intercompany recharge structures without consulting their indirect tax team frequently discover the exposure years later during a state audit.
Extra Rules for Government Contractors
Organizations with federal contracts face a separate layer of allocation rules under the Federal Acquisition Regulation. FAR 31.201-4 defines an allocable cost as one that is assignable or chargeable to a cost objective based on relative benefits received or another equitable relationship.7Acquisition.GOV. FAR 31.201-4 – Determining Allocability A cost qualifies if it was incurred specifically for the contract, if it benefits the contract and other work in a proportion that can be reasonably measured, or if it’s necessary to the overall operation of the business.
FAR 31.203 imposes strict rules on how indirect cost pools are built and distributed. Costs must be accumulated in logical groupings, and the allocation base must be common to all cost objectives the grouping serves and distribute costs by benefits received. Once an allocation base is set, the contractor cannot strip out individual elements. Every item properly in the base, allowable or unallowable on the contract itself, must bear its share of indirect costs.8Acquisition.GOV. FAR 31.203 – Indirect Costs The Defense Contract Audit Agency audits these systems closely, and a poorly documented allocation methodology can jeopardize future contract eligibility.
Related-Party Disclosure in Financial Statements
Intercompany recharges largely disappear on consolidation. But ASC 850 requires disclosure of material related-party transactions whenever separate or carve-out financial statements are prepared. If a subsidiary is being spun off, taken public, or reported on individually, the nature and dollar amounts of intercompany recharges must be disclosed, along with the terms and manner of settlement. Amounts due from or to related parties belong on separate balance sheet lines, not buried in general receivables or payables.
One disclosure trap surprises many preparers. Financial statements cannot represent that related-party transactions occurred on arm’s length terms unless the claim can be substantiated. “Management believes the allocations are reasonable” is acceptable. “These transactions were conducted at arm’s length” is a representation that requires actual evidence, like a transfer pricing study or benchmark analysis. Auditors will test the claim, and getting it wrong can lead to a restatement.
Even without transactions, if common ownership or management control exists and could materially affect operating results, the existence of the control relationship itself must be disclosed. This catches holding company structures where the parent provides no services but exercises control that shapes subsidiary results.
Write the Allocation Policy Down
A written allocation policy is the backbone of a defensible recharge system. Without one, allocation decisions become ad hoc, inconsistent across periods, and hard to explain to auditors or tax authorities.
At minimum, the policy should document which costs sit in each pool, the allocation method used for each pool, the data source for each allocation base, how often recharges are calculated, and how allocation rates are reviewed and updated. Bases go stale. If IT costs are allocated by headcount and a department doubled six months ago, the base needs to reflect that.
Documenting exclusions matters as much as documenting inclusions. If certain corporate costs aren’t allocated because they relate to the parent’s governance rather than subsidiary operations, say so. This is especially important for intercompany recharges, where transfer pricing documentation overlaps with internal policy.
Review the policy at least annually, and revise it whenever the business changes significantly through restructuring, acquisitions, or major shifts in how shared services are delivered. Any change to the methodology should reach affected department managers before implementation, not after they see an unexpected spike in their recharged costs.