intercompany-eliminator
Automated intercompany transaction identification and elimination skill for consolidated reporting
Best use case
intercompany-eliminator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Automated intercompany transaction identification and elimination skill for consolidated reporting
Teams using intercompany-eliminator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/intercompany-eliminator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How intercompany-eliminator Compares
| Feature / Agent | intercompany-eliminator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Automated intercompany transaction identification and elimination skill for consolidated reporting
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Intercompany Eliminator ## Overview The Intercompany Eliminator skill automates the identification and elimination of intercompany transactions for consolidated financial reporting. It ensures accurate elimination entries and handles complex multi-entity structures. ## Capabilities ### Intercompany Matching - Trading partner identification - Transaction type classification - Amount reconciliation - Timing difference handling - Currency conversion alignment - Threshold-based matching ### Elimination Entry Generation - Revenue/cost of goods sold elimination - Intercompany receivable/payable netting - Dividend elimination - Management fee elimination - Interest income/expense elimination - Service charge elimination ### Currency Translation - Functional currency determination - Translation method application - Temporal method calculations - Current rate method application - Cumulative translation adjustment - Remeasurement gain/loss ### Minority Interest Calculation - Noncontrolling interest identification - Profit/loss allocation - Comprehensive income allocation - Changes in ownership treatment - Step acquisition adjustments - Deconsolidation accounting ### Investment Elimination - Cost method elimination - Equity method elimination - Acquisition accounting - Goodwill calculation - Push-down accounting - Basis differences ### Unrealized Profit Elimination - Inventory profit elimination - Fixed asset profit elimination - Upstream vs. downstream - Minority interest impact - Tax effect consideration - Realization timing ## Usage ### Monthly Consolidation ``` Input: Subsidiary trial balances, intercompany activity reports Process: Match transactions, generate eliminations, calculate minority interest Output: Consolidated trial balance, elimination entries, reconciliation report ``` ### Intercompany Reconciliation ``` Input: Intercompany balance reports from all entities Process: Identify mismatches, investigate differences, propose adjustments Output: Reconciled balances, adjustment entries, exception report ``` ## Integration ### Used By Processes - Intercompany Accounting and Consolidation - Financial Statement Preparation - Month-End Close Process ### Tools and Libraries - ERP APIs (SAP, Oracle) - Consolidation software (HFM, OneStream) - Custom matching algorithms ## Best Practices 1. Establish intercompany policies and procedures 2. Implement real-time matching where possible 3. Set materiality thresholds for reconciliation 4. Create standard intercompany transaction templates 5. Build escalation procedures for unmatched items 6. Maintain entity relationship mapping
Related Skills
dead-code-eliminator
Identify and safely remove dead, unused, and unreachable code from codebases
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.