Meter readings, move-ins, budget billing and held bills each have their own steps in SAP IS-U, and each utility sets them up its own way. Outcomer shows each step on your agents' own screen, from your own procedures.
Book a 10-minute demoAfter the demo, we’ll set up your department free of charge. A small trial confirms it’s accurate, then a larger trial measures the drop in support queries.
We check every step works before your staff see it.
Outcomer isn’t a library of ready-made SAP IS-U guides. We build your guides from your own procedures, on your own SAP IS-U set-up, and test each one before your staff use it.
Your billing and customer service agents get the answer on screen, in SAP IS-U and the systems around it, instead of interrupting a colleague or raising a ticket.
SAP IS-U training covers the standard billing and customer processes, but each utility sets its own rules. Outcomer answers agents' questions while they are on the call or working the queue.
General answers for the standard product. Your own set-up may differ, and that’s what Outcomer follows.
Use single entry for the customer's contract, installation or device. You don't need to create a meter reading order first: the system uses an existing one or creates one. Enter the reading, the date and the reading type your process uses. The system then checks the reading.
An implausible reading can be corrected, released without correction, or marked for estimation. If you correct it, the system shows the expected reading and consumption, then runs the remaining checks. Releasing it marks it as plausible. Your firm's rules say which option to use and when.
Implausible readings can be listed, for example by meter reading unit or portion. On the overview screen they are highlighted, and only those can be processed. From there you can correct, release or estimate them, or defer them for later.
Yes, plausible readings can be corrected, for example to replace an estimated reading with the customer's actual one. You can change the reading, its date and the reading type. The changed reading is checked again after you save it.
A reading that has already been billed is locked. It can't be changed until the bill that used it has been reversed. Follow your firm's bill correction process before changing the reading.
If no actual reading was received for the period, the system estimates one, based on the customer's previous consumption. Readings can come from meter readers, uploads from external devices or the customer. If the customer later gives an actual reading, it can be used to correct the estimate.
Enter the move-out date and the meter reading at move-out. You can also update the customer's address and payment methods. When you save, the system first creates a parked document, then the move-out itself. Your set-up may differ, for example if move-outs start from a contract end in CRM.
The final reading can be estimated during billing, or a meter reader can be sent to read the meter. Your firm's move-out procedure says which to use.
In the interaction centre, open the customer's budget billing plan. The system proposes an amount. You can enter a meter reading and consumption, then the new budget billing amount, and save the plan. This applies to certain budget billing procedures only, so your set-up may differ.
A bill is outsorted (held back for checking) when it fails a check, such as an amount limit or an estimation check, or when it has been set for manual outsorting on the contract. You need to check the outsorted document on screen, then either release it for invoicing or reverse the billing. Your firm sets the checks and limits.
If your billing and customer service agents ask questions like these every week, Outcomer answers them on their own screen, using your own SAP IS-U set-up and procedures.
See which SAP IS-U tasks staff ask about most, which procedure answered each question, and whether it was finished or passed to your support desk. Your IT team can export it at any time.
Outcomer never reads, uses or keeps the data in your systems. It finds each box and button by its label, never what’s typed in it, takes no screenshots, and works from your procedures, not your records.