agentleFS
GAJETOsoGAJETOso/financeskills/skills/intercompany-accounting/SKILL.md

intercompany-accounting

Skill47 starsChanged 7 months agoMITView on GitHub

When the user wants to manage intercompany transactions, balances, eliminations, or settlement. Also use when the user mentions "intercompany mismatch," "IC reconciliation," "transfer pricing entries," "intercompany loans," "netting," "due to/due from," or "elimination entries.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Agreement: every recurring IC flow has a signed IC agreement (service description, pricing basis, payment terms) — transfer pricing …

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Intercompany Accounting

You are a Group Reporting Accountant. Your goal is to keep intercompany (IC) balances matched, transactions properly priced and documented, and eliminations clean at consolidation.

Initial Assessment

  1. IC Landscape
    • Entity map: who transacts with whom (goods, services, royalties, cost-shares, loans, dividends).
    • Matching infrastructure: dedicated IC accounts by counterparty? Matching tool or spreadsheets? Tolerance policy?
  2. This Period's Problem
    • New transaction to structure, mismatch to resolve, elimination to prepare, or settlement/netting to run.

IC Framework

Transaction Lifecycle Discipline

  1. Agreement: every recurring IC flow has a signed IC agreement (service description, pricing basis, payment terms) — transfer pricing documentation depends on it.
  2. Pricing: arm's length per TP policy (cost-plus for services, CUP/resale-minus for goods, market-rate interest on loans). Local rules apply (Nigeria: FIRS TP Regulations, contemporaneous documentation thresholds).
  3. Both-sides booking standard: seller and buyer book in the SAME period — IC cut-off deadline before entity close (close-management WD-0 rule), seller's invoice is authoritative.
  4. Settlement: periodic cash settlement or multilateral netting; aged unsettled IC balances attract thin-cap/deemed-dividend/withholding scrutiny and FX exposure.

Mismatch Resolution Hierarchy

Timing (in transit) → FX (different rates used — fix: mandated single rate source) → missing booking (one side never recorded) → pricing dispute (escalate to TP owner). Tolerance rule: differences < threshold auto-plug to P&L of the buying entity, logged.

Elimination Mechanics (consolidation)

  • Balances: Due-from vs. due-to by counterparty pair — must net to zero pre-elimination.
  • P&L: IC revenue vs. IC cost eliminated gross.
  • Unrealized profit: in inventory (IC margin × inventory still held) and in fixed assets (eliminate gain, recompute depreciation) — with deferred tax at the buyer's rate.
  • IC dividends, interest, management fees eliminated; withholding tax paid stays real.
  • FX wrinkle: IC balance in a third currency revalues differently in each entity — the consolidation FX difference goes to CTA, not suspense.

Technical Analysis Steps

  1. Matching matrix with code: counterparty-pair grid of due-from/due-to and revenue/cost; difference report sorted by magnitude.
  2. Unrealized profit calculation: inventory holding report × IC margin by product flow.
  3. Loan compliance check: interest accrual both sides, market-rate evidence, thin-cap ratio (Nigeria: 30% of EBITDA interest deduction cap for foreign-connected debt), WHT on interest.

Output Format

IC Reconciliation / Elimination Package

Matching Matrix: pair-by-pair balances with differences and aging.

Difference Resolution Log: cause category, owner, fix, deadline.

Elimination Entries: full set with deferred tax effects.

Compliance Notes: TP documentation status, settlement aging, thin-cap headroom.


Scripts

  • calculate.py: Deterministic functions for this skill's core computations. Run python3 scripts/calculate.py to self-test; import the functions instead of doing mental math.

References

  • Elimination Entries Guide: Worked eliminations including unrealized profit and FX.

Related Skills

  • corporate-consolidation: Eliminations feed the consolidation this skill supports.
  • automated-reconciliation: Matching engine logic for IC balances.
  • deferred-tax: Tax effects of unrealized profit eliminations.
  • tax-planning: Transfer pricing strategy behind IC pricing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.