
Compute Accounting Manager
- 29 installs
- 7 repo stars
- Updated May 20, 2026
- daemon-blockint-tech/agentic-enteprises-skill
Handles accounting for compute infrastructure: cloud COGS, capex vs OpEx, depreciation, GL mapping from billing exports, and chargeback models.
About
An agent skill for accounting of compute infrastructure, covering cloud COGS, prepaid commitments, depreciation, GL mapping from usage and invoices, and chargeback/showback. A finance operator uses it when classifying compute costs, capitalizing hardware, or closing compute-related accounts.
- Capex vs OpEx, RI/Savings Plan amortization, and fixed-asset registers
- Month-end reconciliation of compute spend to the ledger
Compute Accounting Manager by the numbers
- 29 all-time installs (skills.sh)
- Ranked #667 of 1,106 Finance & Trading skills by installs in the Skillselion catalog
- Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/daemon-blockint-tech/agentic-enteprises-skill --skill compute-accounting-managerAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 29 |
|---|---|
| repo stars | ★ 7 |
| Last updated | May 20, 2026 |
| Repository | daemon-blockint-tech/agentic-enteprises-skill ↗ |
What it does
Handles accounting for compute infrastructure: cloud COGS, capex vs OpEx, depreciation, GL mapping from billing exports, and chargeback models.
Files
Compute Accounting Manager
When to Use
- Classify capex vs OpEx for servers, GPUs, networking, and data center equipment
- Set up depreciation and asset register for compute fixed assets
- Map cloud provider bills and usage files to GL accounts and cost centers
- Amortize reserved instances, Savings Plans, committed use, and cloud prepaids
- Build chargeback or showback from compute meters to products or business units
- Accrue colo, hardware, and uninvoiced cloud usage at month-end
- Reconcile subledgers (cloud, asset, prepaid) to GL and explain flux
- Support audit PBCs for compute-related balances and capitalization memos
Operational cloud optimization, CUR analytics, and RI recommendations → finops-analyst. Multi-year TCO/NPV and commit portfolio business cases → cloud-economist.
When NOT to Use
- SaaS revenue recognition, deferred revenue, ARR →
senior-revenue-accountant - Rack utilization, stranded kW, refresh planning →
data-center-compute-supply-efficiency - Terraform, VPC, K8s platform design →
infrastructure-engineer - Order form, CRM-to-billing operational handoff →
deal-operations-administrator - MSA/contract redlines →
commercial-counsel - BI dashboards without ledger tie-out →
bi-analyst
Related skills
| Need | Skill |
|---|---|
| Cloud spend optimization and FinOps dashboards | finops-analyst |
| Cloud TCO, NPV, and commit economics | cloud-economist |
| Revenue and ASC 606 | senior-revenue-accountant |
| DC utilization and supply planning | data-center-compute-supply-efficiency |
| Capacity delivery and rack-ready | senior-data-center-capacity-delivery-manager |
| On-site asset install and serials | field-services-engineer |
| Cloud platform and networking | infrastructure-engineer |
| Deal desk and billing ops | deal-operations-administrator |
| SOX control evidence | compliance-engineer |
| Business requirements for finance systems | business-analyst |
| Capex policy, WIP/CIP, audit steering | director-infrastructure-capex-accounting |
| Hardware procurement and supplier SCM | supply-chain-manager |
Core Workflows
1. Cost classification (capex vs OpEx)
Policy, thresholds, useful life, project vs BAU.
See `references/cost_classification_capex_opex.md`.
2. Cloud cost to GL
CUR/billing mapping, credits, prepaid amortization.
See `references/cloud_cost_gl_mapping.md`.
3. Fixed assets and depreciation
Asset register, additions, disposals, impairments.
See `references/fixed_asset_compute.md`.
4. Chargeback and showback
Allocation keys, internal rates, stakeholder reporting.
See `references/chargeback_showback.md`.
5. Month-end close
Reconciliations, accruals, flux commentary.
See `references/month_end_reconciliation.md`.
6. Vendor and invoice controls
Colo, OEM, distributor; three-way match and accruals.
See `references/vendor_invoice_controls.md`.
Outputs
- Capitalization memo — facts, policy cite, asset life, in-service date
- Account mapping table — service/SKU/tag → GL, department, product
- Amortization schedule — prepaid cloud or capitalized implementation
- Reconciliation workbook — subledger to GL, reconciling items
- Flux narrative — drivers for MoM compute COGS or prepaid movement
- Chargeback statement — units, rate, allocated amount by consumer
Principles
- Substance over label — classify by nature (asset vs period cost), not vendor line names alone
- Single source of meters — align FinOps dashboards to the same tags used in GL allocation
- Document judgments — capitalization, useful life changes, and material estimates
- Not tax or legal advice — escalate ASC 842 leases, transfer pricing, and tax treatment to qualified advisors
- Coordinate with engineering — in-service dates and decommissions must match asset records
Chargeback and showback
Table of contents
1. Showback vs chargeback 2. Allocation keys 3. Rate design 4. Governance
Showback vs chargeback
| Mode | GL impact | Purpose |
|---|---|---|
| Showback | No internal JE; reporting only | Transparency, behavior change |
| Chargeback | Intercompany or management JEs | Full cost recovery to consumers |
Pick mode per company policy and system capability (ERP intercompany modules).
Allocation keys
For shared compute (K8s cluster, shared GPU pool, corporate networking):
| Key | Pros | Cons |
|---|---|---|
| CPU-hours / GPU-hours | Tied to usage | Requires metering |
| % of tagged cloud spend | Uses existing CUR | Tag quality dependent |
| Headcount or revenue | Simple | Weak causality |
| Fixed split by agreement | Stable | Can drift from usage |
Document hierarchy: direct tagged spend first → allocate remainder of shared pool.
Rate design
Internal rates may include:
- Variable — per vCPU-hour, per GPU-hour, per GB-month
- Fixed platform fee — amortized platform engineering and shared tools
- Pass-through — reserved capacity at amortized cost + uplift (policy)
Refresh rates quarterly or when unit economics shift materially.
Reconcile total charged to total compute GL expense ± intentional subsidy (document executive approval).
Governance
- Publish dictionary of cost pools and tags
- Freeze allocation rules before month-end close
- Escalate disputes to FinOps + accounting DRI
- Do not use chargeback to bypass capex approval for hardware purchases
Cloud cost to GL mapping
Table of contents
1. Data sources 2. Mapping dimensions 3. Prepaid and commitments 4. Credits and adjustments
Data sources
| Source | Use |
|---|---|
| Billing invoice (PDF/API) | Cash, AP accrual, vendor subledger |
| Cost and Usage Report (CUR) / cost export | Granular allocation, COGS by product |
| Cost management UI | Sanity check, anomaly detection |
| Internal tag compliance report | Find untagged spend |
Reconcile invoice total to sum of allocated CUR ± timing (enterprise support, tax lines).
Mapping dimensions
Build mapping rules in priority order:
1. Account / subscription — default GL by payer account 2. Tag — cost_center, product, environment (prod vs non-prod) 3. Service / SKU — e.g., EC2, GKE, Blob → natural account 4. Resource group or project — for committed structure
| Tag state | Fallback |
|---|---|
| Complete tags | Rule-based GL |
| Missing tags | Default “unallocated” + remediation owner |
| Shared platform | Allocation % from chargeback model |
Prod vs non-prod — separate R&D vs COGS where policy requires.
Prepaid and commitments
| Instrument | Accounting pattern |
|---|---|
| All-upfront RI / prepaid | Debit prepaid asset; monthly amort to COGS/expense |
| Partial upfront | Split cash; amortize prepaid portion |
| Savings Plan / CUD benefit | Amortize commitment over term; true-up usage benefit |
| Short-term reservation (<12 mo) | May expense per policy — document |
Track unamortized balance monthly; tie to cloud console commitment reports.
Credits and adjustments
- Provider credits — reduce expense or prepaid per nature (promo vs SLA credit)
- Enterprise Discount Program — allocate consistently with usage mapping
- Refunds — reverse AP and expense or adjust prepaid
- FX — invoice currency vs functional currency; document rate source
Log non-recurring items separately in flux commentary.
Cost classification (capex vs OpEx)
Table of contents
1. Decision framework 2. Common categories 3. Documentation
Decision framework
| Question | Capex (capitalize) | OpEx (expense) |
|---|---|---|
| Useful life | >1 year, identifiable asset | Consumed in period |
| Ownership risk | Company controls economic benefit | Pay-as-you-go service |
| Nature | Physical server/GPU, long-term license prepay for asset | Cloud usage fees, support without asset |
| Project vs BAU | Qualifying build / implementation (policy) | Maintenance, monitoring, small tools |
Cloud usage (compute hours, storage GB-month) → typically OpEx COGS or hosting expense.
Purchased servers/GPUs for owned or colo deploy → typically capex → fixed asset.
Implementation labor — follow company policy (capitalize eligible costs vs expense).
Common categories
| Item | Typical treatment | Notes |
|---|---|---|
| AWS/Azure/GCP on-demand usage | OpEx | Map by tag to COGS vs R&D |
| RI / Savings Plan upfront or commitment | Prepaid asset → amortize | Match benefit period |
| Server, GPU, storage array | Capex | Serial, in-service date |
| Colo monthly MRC | OpEx or lease (ASC 842) | Legal determines lease classification |
| Cables, rails, minor parts under threshold | OpEx | De minimis policy |
| Software subscription (SaaS) | OpEx | Unless capitalized software policy applies |
| Freight, installation for capital equipment | Capitalize as part of asset | If policy requires |
| Spare parts inventory | Inventory or OpEx | Per policy |
Documentation
Capitalization memo should include:
- Description and business purpose
- Invoice or PO reference
- In-service date and location (site/account)
- Useful life and depreciation method
- Policy paragraph or precedent
- Approver (controller or delegate)
Fixed assets and depreciation
Table of contents
1. Asset register fields 2. Lifecycle events 3. Depreciation methods 4. Disposal and impairment
Asset register fields
Minimum fields per compute asset:
| Field | Example |
|---|---|
| Asset ID | FA-2024-00123 |
| Description | Dell R750, 2×GPU |
| Serial number | From field-services-engineer handoff |
| Category | Server, GPU, network, storage |
| In-service date | When placed in production use |
| Cost basis | Invoice + capitalized freight/install |
| Useful life | 3–5 years (policy) |
| Depreciation method | Straight-line |
| Location | Site, rack, account |
| GL accounts | Asset, accum depr, depr expense |
| Custodian / owner | Engineering or platform team |
Lifecycle events
1. Pending — PO placed, not in service 2. In service — start depreciation 3. Transfer — site or cost center change; update tags and allocation 4. Partial upgrade — capitalize if new component meets threshold; else OpEx 5. Retired — stop depreciation; disposal workflow
Align in-service with engineering (not merely received at dock unless policy says otherwise).
Depreciation methods
| Method | When used |
|---|---|
| Straight-line | Default for servers/GPU |
| Units of production | Rare; only if policy and reliable meter |
| Group depreciation | Policy permitting pooled assets |
Run monthly depreciation journal; tie subledger to GL.
Disposal and impairment
Disposal:
- Remove cost and accumulated depreciation
- Record gain/loss on sale or scrap
- Retire serial from inventory/asset system
Impairment indicators:
- Long idle with no redeploy plan
- Obsolete generation (e.g., GPU end-of-life)
- Physical damage
Document impairment test per GAAP/IFRS policy; controller approval.
Month-end reconciliation
Table of contents
1. Close calendar 2. Standard reconciliations 3. Accruals 4. Flux analysis
Close calendar
Typical compute accounting tasks (align to company close day):
| Day | Task |
|---|---|
| T+1 | Pull final cloud invoice / CUR close |
| T+2 | Run allocation; post cloud JEs |
| T+3 | Depreciation run; prepaid amortization |
| T+4 | Reconcile subledgers to GL |
| T+5 | Flux and variance notes for controller |
Standard reconciliations
| Reconciliation | Tie |
|---|---|
| Cloud AP / invoice | Vendor statement ↔ GL AP ↔ cash |
| Prepaid cloud | Schedule ↔ console commitment balance |
| Hosting / COGS expense | CUR subtotal ↔ GL (by account) |
| Fixed assets | Register ↔ GL asset and accum depr |
| Accrued colo / hardware | Estimate ↔ subsequent invoice |
| Intercompany chargeback | Subledger ↔ elimination (if applicable) |
Each reconciliation: preparer, reviewer, threshold for investigation.
Accruals
Accrue when goods/services received but invoice not yet booked:
- Cloud usage after last invoice cut (usage accrual from CUR)
- Colo MRC for current month
- Hardware received not invoiced (GRNI)
- Estimated vendor credits not yet applied
Reverse automatically next period when invoice hits.
Flux analysis
Explain material MoM changes:
| Driver | Example narrative |
|---|---|
| Volume | GPU training hours +18% |
| Rate | On-demand mix vs reserved |
| New product launch | New account/subscription |
| One-time | Migration project capitalized |
| FX | USD invoice for non-US entity |
| Classification | Reclass from R&D to COGS |
Link flux to business metrics (nodes deployed, customers) when possible.
Vendor and invoice controls
Table of contents
1. Vendor types 2. Three-way match 3. Common issues 4. Controls
Vendor types
| Vendor | Accounting touchpoints |
|---|---|
| Hyperscaler (AWS, Azure, GCP) | AP, prepaid, usage accrual |
| Colocation | OpEx or lease; power pass-through |
| OEM / distributor (Dell, HPE) | Capex AP; asset creation |
| Maintenance / support | OpEx or prepaid |
| Network carriers | OpEx; may capitalize if part of build |
Three-way match
For hardware capex:
1. PO — approved amount, capex project code 2. Receipt — serials, quantity, in-service trigger 3. Invoice — match to PO; capitalize to asset or inventory
For cloud:
- Match enterprise agreement or account master to invoice
- Validate payer account list vs approved subscriptions
Common issues
| Issue | Resolution |
|---|---|
| Invoice in wrong entity | Rebill or intercompany recharge |
| Duplicate serial capitalized | Retire duplicate asset |
| Credits on separate line | Map to expense or prepaid reduction |
| Partial shipment | Accrue or capitalize only received units |
| Backdated colo rate change | Catch-up adjustment with memo |
Controls
- Segregation — approver ≠ preparer for capex over threshold
- Master data — GL and cost center on PO required
- Tag policy — block close on untagged prod spend above limit (if automated)
- Asset disposal — dual approval before GL retirement
- PBC retention — invoices, capitalization memos, reconciliation sign-offs
Route lease classification and sales/use tax on equipment to tax/legal per policy.