An intercompany sweep is, in principle, the simplest transaction in corporate treasury: move surplus cash from Entity A to cover a shortfall in Entity B, booked as an intercompany loan. In practice, a mid-market treasury team executing sweeps across a 10-entity structure in three currencies will tell you that "simple" is the wrong word. The mechanics work fine in the straightforward domestic case. The edge cases — regulatory jurisdictions, FX exposure, existing debt covenants, tax treatment — are where sweeps get complicated fast.
This article walks through the mechanical, regulatory, and operational dimensions of interco sweeps as a reference for treasury teams that manage them regularly. We'll cover the domestic mechanics first, then the complications that arise with cross-border and cross-currency transfers.
The Basic Mechanics: Domestic Sweep
A domestic interco sweep between two wholly-owned US entities follows a clean sequence. Treasury identifies the surplus entity and the deficit entity, determines the sweep amount (typically surplus minus target minimum balance), initiates a wire or ACH transfer between the two accounts, and books the transaction simultaneously in both entities' general ledgers as an intercompany receivable (in the lending entity) and an intercompany payable (in the borrowing entity).
The GL booking requires an intercompany loan agreement that specifies the interest rate. Under IRS Section 7872 and related transfer pricing rules, intercompany loans must carry an interest rate at or above the Applicable Federal Rate (AFR) for the applicable term. For short-term demand loans — callable within 30 days — the short-term AFR applies. For longer-term interco facilities, the mid-term or long-term AFR applies. Using a below-market rate triggers imputed interest income: a transfer pricing issue that becomes an audit exposure at scale.
Documenting each sweep with a promissory note or drawing against an established master intercompany facility agreement is best practice. A master facility agreement between parent and each subsidiary — establishing a credit limit, interest rate methodology, repayment terms, and netting rules — simplifies recurring sweeps to a drawdown entry rather than requiring new documentation each time.
Timing: The Wire Cutoff Problem
Sweep execution timing is more operationally constrained than it appears on paper. Domestic wires for same-day value must be initiated before the bank's Fedwire cutoff — typically 6:00 PM Eastern for most banks. ACH same-day credits must be submitted before 2:45 PM Eastern for same-day settlement. International wires have earlier cutoffs and additional correspondent bank routing considerations.
This creates a hard constraint: treasury must complete its daily cash position assessment, identify sweep needs, obtain any required approvals, and initiate the wire — all before 3:00-4:00 PM Eastern, depending on the bank. For a treasury team that manually aggregates position data from multiple portals starting at 9:00 AM, the window for analysis and execution is genuinely narrow.
The operations-level answer is to reduce data collection time so the decision window expands. A treasury team with intraday bank feeds and an automated position view can identify sweep requirements at 10:00 AM rather than 2:00 PM, providing five or more hours rather than one for analysis and approval routing.
Cross-Border Sweeps: Regulatory and Tax Considerations
Cross-border interco sweeps introduce regulatory complexity that varies significantly by jurisdiction. Several considerations apply broadly.
Currency Controls and Repatriation
Some jurisdictions impose controls on the repatriation of funds — requiring central bank approval for transfers above certain thresholds, imposing withholding taxes on interest paid to foreign parent entities, or restricting the timing of dividend-equivalent repatriation. US-based treasury teams primarily deal with relatively open capital account jurisdictions (Canada, UK, EU, Mexico), but even those have nuances. Canadian thin capitalization rules limit the deductibility of interest paid to a foreign parent where the Canadian subsidiary's debt-to-equity ratio exceeds 1.5:1 — a trap for mid-market companies that fund Canadian operations heavily through interco loans.
FX Exposure Transfer
When a USD-denominated parent sweeps cash to a EUR-denominated subsidiary to cover a shortfall, the transaction creates FX exposure: the interco receivable on the parent's books is denominated in EUR, and its USD value fluctuates with the EUR/USD rate. Unless that exposure is explicitly hedged — through an FX forward or cross-currency swap — the sweep has transferred currency risk from the subsidiary (which needed EUR liquidity) to the parent (which now holds a EUR-denominated receivable).
We're not saying that unhedged interco loans are always wrong — for small amounts with short tenors, the hedging cost may exceed the exposure. The point is that the decision to hedge or accept exposure should be explicit, not accidental. Many mid-market treasury teams make this choice implicitly by default rather than by policy.
Transfer Pricing Documentation
For cross-border sweeps, transfer pricing documentation requirements apply to the interest rate. The arm's-length rate for interco loans is established using the Comparable Uncontrolled Price method or cost-plus method, documented in a transfer pricing study or policy memo. A defensible approach for mid-market companies is to peg interco loan rates to the parent's cost of borrowing under its credit facility, with a spread reflecting the subsidiary's standalone credit quality. This documentation is typically prepared annually and reviewed when sweep volumes change materially.
Pooling vs. Manual Sweeps: The Right Tool for Each Situation
Zero-balance account sweeping — automated, same-bank — handles the high-frequency domestic case well. It runs daily without treasury intervention, clears subsidiary accounts to zero, and concentrates cash in the master account automatically. The limitation is that ZBA structures work only within a single banking relationship. When subsidiaries bank at different institutions — common for acquired companies that retained their prior banking relationships — manual sweeps fill the gap.
A practical multi-entity treasury structure often uses both: ZBA sweeping for core domestic entities with the primary bank, and manual weekly sweeps for subsidiaries at other institutions or in other currencies. The 13-week entity-level forecast is what enables treasury to execute manual sweeps on a planned schedule — pre-funding the Canadian entity before a known quarterly payment cluster — rather than reactively discovering a shortfall 48 hours before payroll.
Approval Controls and Audit Trails
For companies with dual-control requirements on treasury operations — standard for SOX-compliant finance functions — interco sweeps above specified thresholds should require two-person authorization: initiation by treasury staff and approval by the treasurer or CFO. The approval workflow and execution record (timestamp, amount, entities, GL posting reference) form the audit trail.
Banks increasingly support API-based wire initiation with separate authentication tokens for initiation and approval — a structural improvement over the prior model of a single signer logging into a portal. Treasury operations at growing mid-market companies that aren't yet using payment initiation APIs should evaluate the control improvement alongside the time savings. The control case is often more compelling to a CFO than the efficiency argument alone.
The mechanics of interco sweeps are learnable in an afternoon. The discipline to execute them consistently — with correct documentation, proper FX treatment, timely approval, and forward-looking forecast context — is what separates a treasury function that is ahead of its cash position from one that is perpetually catching up.