IC Activity (Intercompany)¶

Overview¶

Intercompany (IC) activity encompasses cash flows between entities within the same corporate group, including cash pooling, intercompany loans, dividend payments, and internal settlements. This is distinct from external cash flows and requires special handling in forecasting and visibility.

For treasury teams managing multi-entity structures, IC activity is critical because it represents the internal plumbing of cash management - how money moves between subsidiaries and the parent, how pools are funded, and how internal balances are settled.

For detailed ICP context and terminology, see fundamentals.md

Top Jobs & Desired Outcomes¶

Full history: jobs.md

1. Differentiate automatic pool sweeps from intentional IC payments ✓¶

Desired Outcomes: - Minimize confusion between automatic cash pooling and liability settlements - Increase clarity in transaction history about why money moved - Reduce confusion between ZBA sweeps and other IC transaction types

Sources: ON, Palm Internal (Confirmed)

2. Accurately categorize IC transactions by type ⚡¶

Desired Outcomes: - Minimize time spent manually reviewing and correcting IC categorization - Increase accuracy of IC type identification (cost plus, dividend, loan, equity) - Reduce misclassification between similar IC types

Source: Palm Internal (Emerging)

3. Understand entity funding needs vs incoming settlements ⚡¶

Desired Outcomes: - Minimize unnecessary funding transfers by surfacing upcoming cost plus settlements - Increase visibility into AP-driven intercompany payments treasury doesn't control

Source: Palm Internal (Emerging)

4. Monitor IC payments across global entities ⚡¶

Desired Outcomes: - Minimize missed/failed IC payments going unnoticed - Reduce time to detect payment exceptions across regions

Source: ON (Emerging) - $8M Canada payment failure story

5. Separate capex funding from operational IC ⚡¶

Desired Outcomes: - Increase visibility into capex-specific IC funding amounts - Reduce confusion between short-term operational IC and long-term capex funding

Source: ON (Emerging)

Key Pain Points¶

Full history: pain-points.md

IC categorization fails on transaction type - Misidentifies as FX or ZBA instead of proper IC type (Sources: ON, Palm Internal)
Two-level categorization problem - Is it IC? What TYPE of IC? Both challenging (Source: Palm Internal)
Transaction descriptions lack sufficient data - Can't determine if tax, interest, dividend, loan (Source: Palm Internal)
Treasury lacks visibility on AP-driven cost plus - Large settlements ($5-20M/mo) kicked off by AP (Source: Palm Internal)
Cash pool accounts show misleading negatives - Pooled accounts always negative but funded by sweeps (Source: ON)
"Internal transfer" vs "intercompany" confusion - Terminology causes misclassification (Source: Palm Internal)
Failed IC payments go unnoticed - $8M Canada payment failure only discovered when cash doubled (Source: ON)
Can't distinguish capex funding from operational IC - Need separate view for IC loan setup (Source: ON)

Key Opportunities¶

Counterparty account connection - If sender/receiver is known entity, auto-flag as IC
Rule-based + LLM hybrid - Narrow category options once IC is identified
Cost plus visibility - Surface upcoming AP-driven settlements for funding decisions
ZBA calculated categories - Treat as calculation, not forecast

Open Questions¶

[ ] How to display cash pool positions without alarming users about expected negatives?
[ ] Should IC sweeps be forecast or treated as automatic netting?
[ ] How opinionated should we be about IC category granularity best practices?

Last updated: 2026-02-04 | Sources: 6 transcripts (view all)