--- name: cost-allocation-charging description: Design and execute cost allocation and internal charging mechanisms for shared services, corporate functions, and common resources. Use when allocating shared service costs, setting up internal service pricing, implementing showback/chargeback models, distributing overhead to cost centers, or creating internal transfer pricing for shared resources. Triggers on phrases like "allocate shared costs", "internal charging", "cost center allocation", "overhead distribution", "shared service pricing", "internal transfer pricing", "service charge allocation", "common cost allocation". --- # Cost Allocation & Charging Distribute shared and common costs across business units, departments, and products using defensible, transparent methodologies that drive accountability and informed decision-making. ## Workflow 1. **Inventory all shared costs**: Catalog every cost pool that needs allocation — IT, HR, Facilities, Finance, Legal, Corporate Executive, Shared Service Centers, R&D shared platforms. 2. **Classify cost pools**: Group costs by behavior (fixed vs. variable), traceability (directly traceable vs. common), and benefit pattern (proportional to a driver vs. equal benefit). 3. **Identify cost recipients**: Map which departments, business units, or products consume each shared cost — not all costs benefit all units equally. 4. **Select allocation bases (cost drivers)**: For each cost pool, choose the driver that best reflects actual consumption — headcount, revenue, square footage, transactions, compute usage, data volume. 5. **Choose allocation method**: Select the appropriate mathematical approach — direct method, step-down method, reciprocal method, or activity-based allocation — based on inter-service dependencies. 6. **Build calculation model**: Create the allocation engine with transparent formulas, documented assumptions, and version control. 7. **Determine chargeback vs. showback**: Decide whether to financially charge departments (chargeback) or merely report costs for visibility (showback). 8. **Publish allocation report**: Distribute monthly/quarterly allocation reports to cost center owners with drill-down capability. 9. **Establish challenge process**: Allow departments to dispute allocations with evidence; review and resolve within defined SLA. 10. **Annual methodology review**: Re-evaluate allocation bases and methods annually; adjust for organizational changes, new services, or stakeholder feedback. ## Cost Pool Classification ``` CLASSIFY EACH COST POOL BEFORE ALLOCATING: LEVEL 1: DIRECTLY TRACEABLE (No allocation needed) ─────────────────────────────────────────────── Costs that can be traced to a single department/unit without judgment. Examples: Department-specific software licenses, dedicated headcount, department-specific travel Treatment: Charge directly — no allocation methodology needed. LEVEL 2: DRIVER-BASED (Allocate using consumption metric) ──────────────────────────────────────────────────────── Costs where consumption can be measured per department. Examples: IT support tickets by department, HR onboarding count, printer pages by floor, cloud storage by team Treatment: Allocate proportionally to measured consumption. LEVEL 3: PROXY-BASED (Allocate using surrogate metric) ────────────────────────────────────────────────────── Costs where direct consumption isn't measured but a reasonable proxy exists. Examples: Facilities (square footage), HR (headcount), Finance (number of transactions or revenue) Treatment: Allocate using best available proxy; document rationale. LEVEL 4: COMMON COSTS (Allocate using judgment) ──────────────────────────────────────────────── Costs that benefit the entire organization with no clear driver. Examples: CEO/Board compensation, corporate branding, strategic planning, investor relations Treatment: Allocate by revenue, equally, or absorb as corporate expense. Disclose methodology and judgment explicitly. MUTUAL SERVICE COSTS (Special case): ────────────────────────────────── When service departments serve each other (IT supports HR, HR hires for IT). Treatment: Use reciprocal method or step-down method to resolve circular dependencies. ``` ## Allocation Methods Compared ``` METHOD 1: DIRECT METHOD (Simplest) ────────────────────────────────── Service department costs allocated ONLY to operating departments. Ignores service-to-service interactions. IT Cost: $500,000 → Allocated by headcount to Eng (40%), Sales (25%), Ops (20%), Finance (15%) HR Cost: $300,000 → Allocated by headcount to Eng (40%), Sales (25%), Ops (20%), Finance (15%) Pros: Simple, fast, easy to explain Cons: Ignores service-to-service consumption; distorts allocation METHOD 2: STEP-DOWN METHOD (Sequential) ────────────────────────────────────── Allocate service depts in order (most service to other services first). Once allocated, a service dept receives no further allocations. Order: IT → HR → Operating Depts (because IT serves HR more than HR serves IT) Step 1: Allocate IT ($500K + portion of other services) to HR + Operating Depts Step 2: Allocate HR (original $300K + IT allocation) to Operating Depts only Step 3: Done Pros: Captures one-way service interactions Cons: Order-dependent (results vary by allocation sequence) METHOD 3: RECIPROCAL METHOD (Most Accurate) ────────────────────────────────────────── Simultaneous equations capture all mutual service interactions. IT_total = $500,000 + 10% × HR_total HR_total = $300,000 + 5% × IT_total Solving: IT_total = $500,000 + 0.10($300,000 + 0.05 × IT_total) IT_total = $500,000 + $30,000 + 0.005 × IT_total 0.995 × IT_total = $530,000 IT_total = $532,663 HR_total = $300,000 + 0.05 × $532,663 = $326,633 Then allocate IT_total and HR_total to operating departments. Pros: Most accurate; captures full mutual dependency Cons: Complex; requires linear algebra or solver METHOD 4: ACTIVITY-BASED ALLOCATION (Most Granular) ─────────────────────────────────────────────────── Identify activities → measure consumption per department → allocate by activity. Example — IT Department: Activity 1: Help desk tickets — $200K — allocate by ticket count Activity 2: System administration — $150K — allocate by server count Activity 3: Software licensing — $100K — allocate by user count Activity 4: Network infrastructure — $50K — allocate by bandwidth Pros: Most precise; departments pay for what they consume Cons: Requires detailed tracking; high implementation cost ``` ## Allocation Base Selection Guide ``` SELECT THE MOST CONSUMPTION-ALIGNED DRIVER FOR EACH COST POOL: IT INFRASTRUCTURE: ───────────────── Primary: Cloud compute hours, storage TB, bandwidth GB Secondary: Number of named users, number of applications Fallback: Headcount (FTE) IT SUPPORT / HELP DESK: ────────────────────── Primary: Number of tickets raised by department Secondary: Help desk hours consumed Fallback: Headcount FACILITIES / REAL ESTATE: ──────────────────────── Primary: Square footage occupied by department Secondary: Headcount (if hot-desking) Fallback: Revenue (if space usage unmeasurable) HR SHARED SERVICES: ────────────────── Primary: Headcount (FTE) Secondary: Number of transactions (onboardings, benefits changes, payroll runs) Note: Recruitment costs → allocate to hiring department, not by headcount FINANCE / CONTROLLER: ──────────────────── Primary: Revenue generated by department (proportional to finance work) Secondary: Number of transactions or invoices Fallback: Headcount LEGAL / COMPLIANCE: ────────────────── Primary: Time tracking (actual hours spent per department) Secondary: Number of matters/cases by department Fallback: Revenue CORPORATE / EXECUTIVE: ───────────────────── Primary: Revenue (each revenue unit benefits from corporate leadership) Alternative: Equal allocation (each department equally benefits) Rationale: Pure judgment call — document the choice R&D SHARED PLATFORMS: ──────────────────── Primary: Platform usage hours / API calls consumed Secondary: Number of projects using the platform Fallback: R&D headcount ``` ## Showback-to-Chargeback Progression ``` PHASED ROLLOUT PLAN: PHASE 1: SHOWBACK (Months 1–3) ───────────────────────────── Purpose: Build transparency and trust Action: Publish monthly allocation reports — NO financial impact Output: Each department sees "your share" of shared costs Metric: Report open rate, challenge rate, satisfaction survey Sample report header: "SHOWBACK REPORT — Marketing Department — January 2025 Your share of shared costs: $248,000 (informational only — no charge applied) IT: $95,000 | Facilities: $78,000 | HR: $35,000 | Finance: $25,000 | Corporate: $15,000" PHASE 2: WHAT-IF P&L (Months 4–6) ──────────────────────────────── Purpose: Show financial impact without applying it Action: Publish department P&L with allocated costs included Output: "True cost" profitability view for each department Metric: Department head feedback, adjustment requests PHASE 3: PARTIAL CHARGEBACK (Months 7–9) ──────────────────────────────────────── Purpose: Begin financial accountability for variable costs Action: Charge only variable/directly traceable shared costs Output: Department P&L reflects variable shared cost charges Rule: Fixed shared costs remain in Phase 2 (showback only) PHASE 4: FULL CHARGEBACK (Months 10+) ──────────────────────────────────── Purpose: Full cost transparency and accountability Action: All shared costs (fixed + variable) charged to departments Output: Complete department P&L with full cost allocation Governance: Quarterly allocation review with CFO and department heads DECISION CRITERIA FOR PROGRESSION: ✓ Allocation model accuracy > 95% (audited) ✓ Challenge rate < 20% of departments ✓ Department head satisfaction > 3.5/5.0 ✓ CFO and all VP sign-off ✗ If any criterion not met → extend current phase by 3 months ``` ## Allocation Challenge Process ``` FORMAL CHALLENGE PROCESS: 1. SUBMISSION (within 5 business days of report receipt): • Department head submits challenge via finance portal • Must include: specific line item, proposed alternative, supporting evidence • Categories: Data error, wrong driver, timing mismatch, methodology dispute 2. REVIEW (within 3 business days): • Cost accounting team reviews challenge • Checks: Is the data correct? Is the driver appropriate? Is there a better alternative? 3. RESOLUTION (within 2 business days of review): • If challenge valid: Update allocation, reissue report • If challenge denied: Written explanation with evidence • If inconclusive: Escalate to CFO for decision 4. DOCUMENTATION: • All challenges logged with resolution and rationale • Model changes tracked with version control • Challenge rate tracked as model health KPI 5. ESCALATION (if unresolved within 10 business days): • CFO makes binding decision • Decision documented and communicated ``` ## Edge Cases - **Shared services that benefit external customers**: When a shared service also serves external clients (e.g., IT services sold to third parties), allocate costs proportionally to internal vs. external consumption; ensure arm's length pricing for external - **Loss-making departments**: Strategic departments (R&D, new market entry) may be intentionally loss-making; allocation should not create artificial losses that trigger unwanted budget cuts - **Interdepartmental services**: When Department A provides services to Department B (e.g., Design creates assets for Marketing), use internal transfer pricing at standard cost or cost-plus markup - **New or dissolved departments**: Prorate allocations based on months active; handle dissolution by redistributing unallocated costs proportionally - **Shared projects**: Joint projects between departments split costs based on pre-agreed benefit ratios; document the split at project kickoff - **Geographic allocation**: For multi-country organizations, allocate shared costs by local currency using appropriate FX rates (monthly average or period-end) - **Negative allocation scenarios**: Rare but possible when a department generates revenue for shared services (e.g., training department charges external clients); net against total shared cost pool ## Output ### Quarterly Allocation Summary ``` COST ALLOCATION SUMMARY — Q1 2025 =================================== TOTAL SHARED COSTS ALLOCATED: $5,640,000 ALLOCATION BY COST POOL: Pool Q1 Cost Primary Driver Method ────────────────────────────────────────────────────────── IT Infrastructure $2,100,000 Cloud hours + users Activity-based Facilities $1,200,000 Square footage Proxy-based HR Services $840,000 Headcount (FTE) Proxy-based Finance/Controlling $520,000 Revenue Proxy-based Legal/Compliance $480,000 Time tracking Driver-based Corporate Exec $500,000 Revenue Judgment ALLOCATION BY DEPARTMENT: Department Q1 Allocated % of Total $/FTE Trend ────────────────────────────────────────────────────────────────── Engineering $2,050,000 36.4% $5,125 ↗ +3% Sales $1,310,000 23.2% $4,367 → flat Operations $1,120,000 19.9% $3,733 ↗ +5% Marketing $740,000 13.1% $4,625 ↓ -2% Finance $240,000 4.3% $4,000 → flat HR $120,000 2.1% $3,000 → flat Executive $60,000 1.1% $3,000 → flat CHALLENGE TRACKING: Total challenges received: 3 (out of 7 departments = 43%) • Operations: Disputed facilities allocation → resolved (space measurement verified) • Sales: Disputed IT allocation → under review (IT gathering usage data) • Marketing: No challenge Model health score: 3.5/5.0 (improved from 3.0 last quarter) Recommended action: Add cloud usage tracking to reduce IT allocation disputes ``` ## Integration Points - ERP (SAP, Oracle, NetSuite): Cost center master data, allocation rules, GL posting - Service management (ServiceNow, Jira Service Management): Ticket counts, service usage - HRIS (Workday, BambooHR): Headcount data, employee cost center assignments - Facilities management (IoT sensors, CAFM systems): Space utilization data - IT monitoring (Datadog, New Relic): Compute usage, storage, bandwidth metrics - Budgeting tools (Anaplan, Adaptive Insights): Allocation model calculations - BI platforms (Tableau, Power BI): Allocation dashboards, department profitability views - Communication platforms: Monthly/quarterly allocation report distribution