Home
Knowledge
IC Activity
IC Activity - Current Solutions & Workarounds
Kyriba Cash Pool Setup
What it is: Cash pooling configuration in TMS
How they use it: Define master and participant accounts
Limitations: Doesn't forecast sweeps, doesn't filter view for pool accounts, no proper category
Used by: ON
Manual Account Naming
What it is: Naming convention to identify pool membership
How they use it: Named accounts as "Cash Pool Master" or "Participant" in Kyriba
Limitations: No system-level classification, just visual indicator
Used by: ON
Manual Workarounds
Knowing the Pool Structure
What they do: Treasury team mentally knows which accounts are pooled and ignores their negatives
Why: No system filter to show only non-pooled account balances
Source: ON (2025-11-17)
Description-Based Classification
What they do: Use transaction descriptions to differentiate sweep types (automatic vs manual, interest vs principal)
Why: Different IC transactions have different descriptions
Source: ON (2025-11-17)
Proposed Approaches (from Palm Internal Discussion, 2026-02-02)
Counterparty Account Connection
Concept: If sender/receiver account is known internal entity, automatically flag as IC
Benefit: Solves "Is this intercompany?" question definitively
Requirement: Need account-to-entity mapping in place
Note: Also enables FX vs non-FX IC distinction (if currencies differ, it's FX IC)
Rule-Based + LLM Hybrid Approach
Concept: Use rules to identify IC transactions, then narrow LLM categories
How: If counterparty = internal entity, only show IC category options to the LLM
Benefit: More accurate categorization by reducing category search space
Source: Giannis: "Trigger the LLM to say you don't have to filter to a big list of categories, but only to these four intercompany categories"
Merchant Field Leverage
Concept: Merchant field often contains counterparty info that could help identify IC
Status: Not currently being leveraged for IC identification
Source: Jennifer: "The merchant field... is quite helpful for intercompany"
Influencing Payment Details
Concept: Encourage treasury teams to add better details in payment descriptions
Rationale: Treasury teams control most non-cost-plus IC payments; they can add keywords
Quote: "We should be able to influence the treasury teams to change the details in the payments to capture some word that allows our models to say this is intercompany dividend." - Gurjit
Back to top