SAP FICO is often treated as a single, standardized module: set up the chart of accounts, configure cost centers, activate Asset Accounting, and the finance function is covered. In practice, that approach breaks down fast once you move into oil & gas or telecom. Both industries run financial processes that classic FICO configuration, built with manufacturing and trading businesses in mind, doesn’t handle cleanly out of the box.
After more than 20 years working across telecom, oil & gas, construction, IT, and finance, the pattern is consistent: implementations that go over budget and over timeline are almost always the ones where a generic SAP FICO template was dropped into an industry with genuinely different financial mechanics. This guide walks through where oil & gas and telecom actually diverge from standard FICO configuration, and what to check before you build.
Why Industry Context Changes SAP FICO Configuration
FICO is really four things working together: General Ledger (FI-GL), Accounts Payable/Receivable (FI-AP/AR), Asset Accounting (FI-AA), and Controlling (CO) for cost and profitability tracking. Each has assumptions baked into its “standard” configuration: goods move through inventory, costs sit on cost centers tied to departments, and assets depreciate on fairly predictable schedules. Oil & gas and telecom both break those assumptions, in different, specific ways.
SAP FICO for Oil & Gas: What’s Actually Different
Oil & gas finance is shaped by three things standard FICO wasn’t built around: shared ownership of assets, capital-intensive long-life assets, and global pricing exposure.
Joint Venture and Partner Cost Sharing
Most upstream and midstream assets are owned by multiple partners under a joint operating agreement, not a single legal entity. Every cost posted needs to be split by ownership percentage and billed to non-operating partners through joint interest billing. Standard FICO cost objects don’t carry ownership-percentage logic; you’re either configuring SAP’s Joint Venture Accounting (JVA) component or building the equivalent logic through custom cost objects and validation rules. Skipping this step is one of the most common reasons oil & gas FICO projects need expensive rework.
Asset Accounting for Long-Life, High-Capex Assets
Wells, platforms, and pipelines don’t depreciate like factory equipment. Depletion is usually calculated on a units-of-production basis tied to reserve estimates, not a straight-line schedule. Asset Accounting configuration needs custom depreciation areas and, frequently, integration with reserve-estimation data that sits outside SAP entirely.
Currency and Global Pricing Exposure
Crude and gas are priced in US dollars globally, but operating costs are usually incurred in local currency. That mismatch has to be handled deliberately in the currency configuration for cost centers and profitability segments, or margin reporting quietly becomes wrong for a few quarters before anyone notices.
SAP FICO for Telecom: What’s Actually Different
Telecom finance is shaped by transaction volume and how revenue is actually earned: through ongoing service contracts, not one-time goods sales.
Revenue Recognition for Subscription and Usage-Based Billing
A postpaid mobile contract, a bundled device-plus-service package, and a usage-based enterprise contract all recognize revenue differently under IFRS 15 / ASC 606. Standard FI-GL revenue posting assumes revenue is recognized at the point of a goods issue or billing document. Telecom needs FICO integrated with a dedicated revenue accounting engine, commonly SAP Revenue Accounting and Reporting (RAR), that can defer and recognize revenue against contract performance obligations instead of against invoices.
High-Volume, Low-Value Transaction Processing
A telecom operator can generate millions of billing line items a month. FICO configuration has to be built for volume from day one: summarization strategy, batch posting windows, and archiving strategy all need deciding before go-live, not retrofitted after the general ledger starts timing out.
Intercompany and Network Cost Allocation
Network infrastructure is frequently shared across business units or legal entities (fixed, mobile, enterprise). Cost allocation cycles in CO need to reflect actual network usage, not a flat headcount or revenue split, or internal profitability reporting stops being trustworthy.
SAP FICO Configuration Priorities by Industry
| Financial Area | Oil & Gas Focus | Telecom Focus | Generic Manufacturing (Baseline) |
|---|---|---|---|
| Revenue Recognition | Joint interest billing, cost recovery agreements | Contract-based deferral (IFRS 15 / ASC 606) via RAR | Recognized at goods issue / delivery |
| Cost Object Structure | Ownership-% based, joint venture aware | Network/usage-based allocation cycles | Department-based cost centers |
| Asset Accounting | Units-of-production depletion, long asset life | Standard depreciation, high asset turnover in equipment | Straight-line depreciation |
| Intercompany Processing | Partner cash calls, JIB statements | Shared network cost recharges | Standard intercompany billing |
| Currency Management | USD pricing vs. local operating currency | Usually single-currency domestic operations | Single or limited currency exposure |
| Transaction Volume | Moderate, high-value transactions | Very high volume, low-value transactions | Moderate volume |
Common Pitfalls When a Generalist SAP FICO Template Meets a Specialized Industry
- Cost center hierarchies copied from a manufacturing template, with no way to reflect joint-venture ownership splits or network-sharing arrangements
- Revenue recognition rules built for goods sales applied to service or subscription contracts, creating recurring manual adjustments every close
- Depreciation areas built for standard useful-life assets, missing units-of-production or regulatory-specific depletion methods
- Currency configuration that doesn’t separate pricing currency from operating currency, quietly corrupting margin analysis
- No integration plan between FICO and the industry-specific system of record: reserve engineering data for oil & gas, mediation and billing platforms for telecom
When to Bring in an Industry-Experienced SAP FICO Consultant
If your FICO configuration is being scoped by a team that’s only worked manufacturing or retail implementations, expect the industry-specific gaps above to surface as post-go-live “surprises,” typically during the first quarter-end close, when reconciliation and reporting problems can no longer be avoided. Bringing in industry-specific experience during blueprint and design, rather than after go-live, is consistently cheaper than remediation.
Frequently Asked Questions
Does SAP FICO have a built-in module for joint venture accounting?
Yes. SAP offers a dedicated Joint Venture Accounting (JVA) component that handles ownership-percentage cost sharing, cash calls, and partner billing. It needs to be scoped and configured deliberately; it isn’t part of standard FICO configuration and is frequently skipped in generic implementations.
How is telecom revenue recognition different in SAP FICO?
Telecom contracts typically bundle multiple performance obligations, such as a device and a service plan, that recognize revenue on different schedules. Standard FI-GL posting doesn’t handle that natively; most telecom SAP landscapes integrate FICO with SAP Revenue Accounting and Reporting (RAR), or an equivalent engine, to manage deferral and recognition against the contract.
Can the same FICO configuration template be reused across oil & gas and telecom entities in the same group?
Not directly. Both industries need genuinely different cost object design, asset accounting logic, and revenue treatment. A shared corporate chart of accounts and reporting structure is realistic; a shared, detailed configuration template usually isn’t.
If you’re scoping an SAP FICO implementation, or troubleshooting one that’s already live, in oil & gas or telecom, these are exactly the kinds of industry-specific configuration gaps I work through.
