Billing that closes the month without a spreadsheet beside it.
Utility and subscription billing on SAP breaks in the gaps: meter reads that arrive late, rate changes keyed by hand, and a contract accounting backlog that finance works off in Excel. We engineer those gaps first, then plan the move to S/4HANA.
Cohash builds and supports SAP billing for utilities and subscription businesses.
On IS-U that means device management, billing and invoicing, rate structures and the move to SAP S/4HANA Utilities. On BRIM it means Convergent Charging, Convergent Invoicing and Subscription Order Management. Both settle in contract accounting (FI-CA), so we treat dunning, payments and clearing as part of every billing change.
you probably need this if
Outsorted bills from each billing cycle are still open when the next one runs.
Every rate case means weeks of manual price key changes and comparison bills in Excel.
The custom billing schema code was written by a contractor who left years ago.
04 Feb 2020IS-U on ECC 6.0 leaves mainstream maintenance in 2027 IS-U still runs on SAP ERP 6.0. Mainstream maintenance ends with 2027; extended maintenance, optional, runs to the end of 2030. source ↗
13 Oct 2026Transition option to 2033, update to 2035 Get to SAP ERP, private edition on SAP HANA by 31 December 2030 and the transition option covers 2031 to 2033. A 13 October 2026 update says subscriptions may run to 31 December 2035, with further prerequisites. source ↗
today · Oct 22, 2026
no date yetS/4HANA 2025 for utilitiesSAP says S/4HANA 2025 builds market process management and prepayment into the core, so the add-ons for them go away.source ↗
the story · sap is-u, brim & fi-ca estate
From the first call to a setup your own team can run.
Here's what usually prompts a call about your SAP IS-U, BRIM & FI-CA estate, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · how it runs04 · where you end up
incident board · sap is-u, brim & fi-ca estate3 open
openOutsorted bills from each billing cycle are still open when the next one runs.
recurringEvery rate case means weeks of manual price key changes and comparison bills in Excel.
blockedThe custom billing schema code was written by a contractor who left years ago.
exposure
IS-U to S/4HANA UtilitiesBilling exception clean-upBRIM implementationFI-CA and collectionsMeter-to-cash integrationRun support and staffing
IS-US/4CC&B
startrehearsehandover
Billing health check
Fix the top causes
Conversion or BRIM design
Parallel billing and cut-over
we are here
ready to hand over
Bills outsort only for real exceptions, since the rules now fit interval reads.
One account, separate lines for charging sessions.
Outsort and implausibility analysis ranked by bill count and dollar value
Rate change test pack with automated comparison bills
chapter 01 · where it hurts
Why teams reach out
Outsorted bills from each billing cycle are still open when the next one runs.
Every rate case means weeks of manual price key changes and comparison bills in Excel.
The custom billing schema code was written by a contractor who left years ago.
chapter 02 · what we change
How we solve it
IS-U to S/4HANA Utilities
Billing exception clean-up
BRIM implementation
FI-CA and collections
Meter-to-cash integration
Run support and staffing
chapter 03 · how it runs
Our approach
Billing health check
Fix the top causes
Conversion or BRIM design
Parallel billing and cut-over
chapter 04 · where you end up
What changes
Bills outsort only for real exceptions, since the rules now fit interval reads.
One account, separate lines for charging sessions.
Outsort and implausibility analysis ranked by bill count and dollar value
Rate change test pack with automated comparison bills
what we do
Our SAP IS-U, BRIM & FI-CA work
6 kinds of SAP IS-U, BRIM & FI-CA work, each run by engineers who have done it on live tenants.
Conversion planning for IS-U on ECC 6.0, including the business partner model, device and installation data, and the custom billing schemas and function modules that usually sit inside variant programs.
We work the outsorted bills and implausible meter reads at the root: validation rules, estimation settings, rate determination and the jobs that feed mass billing.
Subscription Order Management, Convergent Charging and Convergent Invoicing set up for usage-based or recurring products, with billable items flowing cleanly into invoicing.
Payment lots, clearing rules, dunning procedures, installment plans and returns handled in contract accounting, with the posting to general ledger reconciled every period.
Interfaces from head-end and meter data management systems, market communication and customer channels into IS-U or S/4HANA Utilities, moved off PI/PO where it's due.
IS-U, BRIM and FI-CA consultants and ABAP developers for billing run support, on contract, contract-to-hire or permanent terms.
capability 01 / 06in production
IS-US/4CC&B
IS-U to S/4HANA Utilities
Conversion planning for IS-U on ECC 6.0, including the business partner model, device and installation data, and the custom billing schemas and function modules that usually sit inside variant programs.
We work the outsorted bills and implausible meter reads at the root: validation rules, estimation settings, rate determination and the jobs that feed mass billing.
Subscription Order Management, Convergent Charging and Convergent Invoicing set up for usage-based or recurring products, with billable items flowing cleanly into invoicing.
Payment lots, clearing rules, dunning procedures, installment plans and returns handled in contract accounting, with the posting to general ledger reconciled every period.
Interfaces from head-end and meter data management systems, market communication and customer channels into IS-U or S/4HANA Utilities, moved off PI/PO where it's due.
We pieced these together from SAP IS-U, BRIM & FI-CA situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
Twelve thousand outsorted bills a cycle after an AMI rollout
composite · not a client story
Beforethe situation
A smart meter rollout doubled interval read volume. Validation rules written for monthly manual reads now outsort thousands of bills each cycle, and the back office clears them by hand.
What we dothe work
We pull outsort reasons by rule and meter type, then retune the plausibility checks and estimation procedures for interval data in a test client. Comparison bills run against a sample of affected accounts before each rule change goes live.
Afterwhere you end up
Bills outsort only for real exceptions, since the rules now fit interval reads. The back office works a short list, and each item on it says why it's there.
case file 02
Launching usage-based EV charging billing next to the commodity bill
composite · not a client story
Beforethe situation
A utility wants to bill public EV charging by kWh and by time, on the same customer account as the electricity bill. The trouble is that IS-U can't rate the session data as it comes in.
What we dothe work
We model the charging offer in Subscription Order Management, rate sessions in Convergent Charging and create billable items for Convergent Invoicing. Invoices settle in the FI-CA contract account the customer already pays.
Afterwhere you end up
One account, separate lines for charging sessions. Collections and dunning don't care which line it is.
We don't start a step until the last one has produced something you can check.
step 01
Billing health check
We pull the outsort reasons, implausibility counts, billing job runtimes and FI-CA open items from the last few cycles. Then we rank each cause by how many bills it touches and how many dollars.
step 02
Fix the top causes
Validation rules, estimation procedures and rate determination get fixed in a test client. Then we run comparison bills on a sample of real accounts. Production only sees the change after that.
step 03
Conversion or BRIM design
IS-U: we go through your custom billing variants and enhancements first, and the conversion plan to S/4HANA Utilities comes out of that. BRIM: the product model, charge plans and billable item classes are designed together.
step 04
Parallel billing and cut-over
Old and new billing run side by side on the same reads for at least a full cycle. Every difference gets explained bill by bill before go-live. Collections stays on one system the whole time.
ai on sap is-u, brim & fi-ca
Where AI fits on SAP IS-U, BRIM & FI-CA, and where it needs guardrails.
SAP ships little AI aimed at IS-U, BRIM or FI-CA specifically. Joule Studio, Joule for Developers and the Integration Suite MCP Gateway apply here as on any SAP system. The useful AI work on billing sits around the platform: explaining old billing schema code, building comparison bills for rate cases and triaging outsorts.
AI agentasks for data or an action
Scoped identityonly the access it needs
MCP serverthe one door into the platform
Logged, approveda person signs off on writes
IS-USAP IS-U, BRIM & FI-CAdoes the work
SAP doesn't currently offer an MCP server specific to IS-U or BRIM. SAP's own route is publishing OData APIs as MCP tools through the Integration Suite MCP Gateway, with Agent Gateway handling principal propagation. We start with read-only tools, on technical users with narrow authorizations, and log every call. Billing and posting actions need a person's approval first.
Outsort and exception triage
Outsorted bills and implausible meter reads come with reason codes. So we group them by reason, meter type and rate, and have a model summarize the patterns and draft changes to the validation rules. Every rule change still gets tested with comparison bills in a test client.
Documenting custom billing code
Custom billing variants, schema steps and function modules often have no owner. So before a move to S/4HANA Utilities, we use code assistants to describe each enhancement. Joule for Developers ABAP AI capabilities are generally available on S/4HANA Cloud Private Edition. On ECC we use other code assistants.
Rate case test generation
Comparison bills for a new tariff have to match the filing. We build test accounts and expected amounts from the tariff tables, then run them against the new price keys and rate categories ahead of go-live.
Read-only agents on billing data
Open items, dunning history and payment lots are good material for an agent that answers collections questions. We point it at a replicated copy, such as billing analytics in Snowflake, instead of the production client, and keep every posting in SAP's own transactions.
Reads come out of meter data management into device management and billing, in IS-U or S/4HANA Utilities. BRIM picks up the usage and subscription charges. Everything posts to contract accounting, where payments, dunning and clearing happen, and only then do balances reach the general ledger.
01 · Usage and orders
Meter data managementinterval reads · validated usage → IS-U / S/4HANA Utilities · meter reads
Plant historianPI · IP.21 → Meter data management · interval data
What a SAP IS-U, BRIM & FI-CA engagement leaves behind
These are working documents, written against your configuration, so your team can run them without us.
report01
Outsort and implausibility analysis ranked by bill count and dollar value
yours to keep
tests02
Rate change test pack with automated comparison bills
yours to keep
inventory03
Custom billing variant and enhancement inventory for S/4HANA conversion
yours to keep
document04
FI-CA to general ledger reconciliation procedure
yours to keep
plan05
BRIM product, charge plan and billable item class design
yours to keep
document06
Parallel billing results with every difference explained
yours to keep
talent and delivery · sap is-u, brim & fi-ca
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Onsite
Engineers at your sites in the US
Nearshore
Overlapping hours with US teams
Offshore
Overnight progress on your backlog
All time zones
Coverage handed over across time zones
24-hour coverage · US Central time
OnsiteUS business hours
Nearshoreoverlapping US hours
Offshoreovernight progress
Combinedhandover, not hand-off
00:0006:0012:0018:0000:00
roles we staff
SAP IS-U billing and invoicing consultant
IS-U device management and meter read specialist
SAP BRIM Convergent Charging consultant
SAP Convergent Invoicing and FI-CA consultant
ABAP developer for IS-U billing enhancements
due diligence · sap is-u, brim & fi-ca
Questions to ask any partner, including us.
Put these to anyone bidding on your SAP IS-U, BRIM & FI-CA work. The ones who've done it answer differently from the ones who've read about it.
Q1
Which custom billing variants and schema steps of ours have a standard S/4HANA Utilities equivalent we could switch to?
Most of the conversion effort and risk sits in custom billing schema code. Every step you can return to standard is one less thing to test now and maintain later.
Q2
How will you prove new rates match the tariff filing before go-live?
Regulators expect bills to match approved tariffs. Automated comparison bills on real accounts catch rate determination errors that unit tests miss.
Q3
How many billing cycles will you run in parallel, and who signs off the differences?
A single cycle can hide seasonal swings and estimation edge cases. You know the new billing is right when parallel runs are signed off by a named person in the business.
Q4
How will FI-CA balances reconcile to the general ledger after cut-over?
Contract accounting posts summary documents to the ledger. If reconciliation isn't designed in, finance discovers the gaps at month-end close.
Q5
Where should usage rating live: IS-U, BRIM or the meter data system?
Put rating in the wrong layer and you end up with the logic in two places and arguments over which number is right. Where it belongs depends on your product types and data volumes.
01Should we move IS-U to S/4HANA Utilities now or wait?
It depends on your maintenance contract, your database and the regulatory calendar. ECC 6.0 leaves mainstream maintenance at the end of 2027. Utilities also schedule around rate cases and peak billing seasons, so we plan the conversion window against those first. The S/4HANA 2025 release brings market process management and prepayment into the core, which can retire add-ons you run today.
02What usually causes outsorted bills?
Implausible meter reads, missing or late reads that trigger estimation, rate determination gaps after a tariff change, and installation facts that don't match the device. We group the outsort reasons by count and fix the top causes in configuration before touching code.
03Is BRIM only for telecoms?
No. BRIM works for anyone billing on usage or subscriptions. That might be a utility selling services beyond the commodity, or a mobility, media or equipment-as-a-service business. If you only sell simple recurring charges, standard SD billing or IS-U is probably all you need.
04Do you work on Oracle Utilities as well?
Yes. Some utilities run Oracle Utilities CC&B instead of IS-U, and some are trying to choose between them. We put the two side by side on billing, devices and collections, using your processes. A feature list won't tell you much.
05How long does a rate change take to implement?
It depends on how many rate categories and price keys change and how your test set covers them. The slow part is rarely the configuration. It's building the comparison bills that prove the new rates match the tariff filing, so we automate that comparison first.
06Can you provide billing engineers for an existing support team?
Yes. We place IS-U, BRIM and FI-CA people onsite in the US, and nearshore or offshore in other time zones. When the billing batch runs overnight, it's good to have someone already at their desk.
services
Related services
Projects on SAP IS-U, BRIM & FI-CA usually end up touching one of these, so they're worth a look.
