Source: https://joinfinn.com/integrations/sap-utilities

# SAP S/4HANA Utilities

## SAP S/4HANA Utilities + Finn.

SAP S/4HANA Utilities integration with Finn. SAP S/4HANA Utilities connects utility customer accounts, contracts, billing, and service processes.

Business function: Utilities.

## What you can do with SAP S/4HANA Utilities.

SAP S/4HANA Utilities connects utility customer accounts, contracts, billing, and service processes.

### Handle the account work for a home move

Finn takes a verified customer's moving request through the SAP customer, premise and contract records, then confirms the completed account changes and next steps.

**Typically handled by:** Utility move-in and move-out service team

**Starts when:** A customer supplies a move date and their old or new service address.

#### What Finn handles

1. Identify the customer, premise, existing contracts and requested dates; collect final or opening meter readings.
2. Obtain the utility's service decision, including any existing occupant or supply restrictions, before changing contracts.
3. Complete the move transaction and forwarding-contact updates through the utility's SAP process; check the resulting contract status.
4. Send the effective dates and final-bill information, recording any physical connection work separately.

**The result:** The customer receives a documented move confirmation tied to completed SAP account changes.

### Collect and record a usable meter reading

Finn follows a meter-reading request from customer contact through SAP's validation result, leaving billing teams with a usable reading or a specific exception to resolve.

**Typically handled by:** Meter-reading administration team

**Starts when:** A scheduled read is missing or a customer submits an interim reading.

#### What Finn handles

1. Find the premise, meter and register, then ask for the reading date, value and units or a clear photograph.
2. Match the submission to the correct register and submit the reading through the utility's SAP entry process.
3. Follow SAP's validation result; request a corrected value when the customer supplied the wrong register or date, without overriding an unexplained exception.
4. Confirm an accepted reading or record the precise reason a field visit or specialist review remains necessary.

**The result:** An accepted reading reaches the account, and unresolved readings have a documented next action.

### Explain a utility bill from its source records

Finn answers a customer's bill question with their actual billing period, consumption and account entries, then records the explanation in the connected service case.

**Typically handled by:** Utility billing support team

**Starts when:** A customer asks why a bill changed or what a particular charge covers.

#### What Finn handles

1. Verify account access and retrieve the SAP contract, bill line items and invoicing history for the disputed period.
2. Compare the period with the previous bill, separating usage, billing days, estimates, rate changes and prior adjustments that appear in the records.
3. Explain the differences in plain English and send the bill through the customer's verified service channel.
4. Record the answer in the connected service desk, keeping any unexplained charge open for billing investigation.

**The result:** The customer receives a traceable bill explanation and a completed inquiry record.

### Complete an authorized bill correction

Finn follows a substantiated billing error through the utility's correction process, checks the replacement documents and explains the result to the customer.

**Typically handled by:** Utility billing corrections team

**Starts when:** The billing owner authorizes correction of a specific meter, period or charge error.

#### What Finn handles

1. Collect the original bill, affected billing documents, corrected source data and the billing owner's reason and decision.
2. Run the selected SAP reversal and correction process for the affected documents, preserving unrelated utility charges.
3. Follow the replacement billing and invoicing results; verify the new bill and corresponding contract-account entries.
4. Deliver the corrected bill and explanation, linking original, reversal and replacement documents in the service case.

**The result:** The financial correction is recorded in SAP and the customer receives the resulting bill.

### Set up the payment arrangement the customer accepts

Finn handles the paperwork and SAP account updates for an installment agreement after the utility determines eligibility and the customer accepts the terms.

**Typically handled by:** Utility payment arrangements team

**Starts when:** A customer accepts an installment proposal for specified outstanding account items.

#### What Finn handles

1. Retrieve the eligible open items and the utility's arrangement decision, including dates, interest and any charges.
2. Generate the SAP installment proposal and present its amounts and dates to the customer for acceptance.
3. Create the accepted plan, then verify the plan number, included receivables and saved installment schedule.
4. Send the confirmation and record the arrangement in the connected customer-service case.

**The result:** The accepted arrangement is active in SAP with the same schedule the customer received.

### Correct the customer details behind returned correspondence

Finn resolves an address or contact-data problem from the original returned notice through a verified SAP update and delivery of the affected correspondence.

**Typically handled by:** Utility customer-records team

**Starts when:** A bill is returned or a verified customer reports incorrect contact details.

#### What Finn handles

1. Identify the business partner and contract accounts affected by the returned notice or correction request.
2. Confirm the new contact information through the utility's verification process, keeping bank-account and ownership changes on their separate authorization paths.
3. Update the SAP business-partner contact record and check the saved values used for correspondence.
4. Resend the affected notice through the correct channel and close the records case with the delivery result.

**The result:** The customer record is corrected and the missing correspondence is sent to the verified destination.

### Finish a billing run after its exceptions are resolved

Finn works through billing-run exceptions, follows the responsible owners' corrections and takes released documents through invoicing and customer delivery.

**Typically handled by:** Utility billing operations team

**Starts when:** A scheduled billing cycle leaves documents waiting for correction or release.

#### What Finn handles

1. Collect the affected contracts, billing documents and check messages; group missing readings, source-data problems and billing-review decisions.
2. Request the specific missing information and apply corrections assigned to the billing operations workflow.
3. After the billing owner releases the affected documents, run the invoicing process and check the print and contract-account documents it creates.
4. Send the resulting bills through the utility's correspondence channel and report any documents still unresolved.

**The result:** Completed bills reach customers, with a precise exception list for the remaining accounts.

### Produce a commercial customer's monthly utility account pack

Finn assembles a site's monthly consumption and billing records into the account pack a commercial customer normally requests from a relationship team.

**Typically handled by:** Commercial utility account-management team

**Starts when:** A business customer needs its monthly bills and usage summary across authorized locations.

#### What Finn handles

1. Identify the customer's contract accounts, premises and billing periods in SAP without combining unrelated legal account holders.
2. Retrieve bill line items, contract consumption and invoicing history, identifying missing or reversed documents.
3. Build the location-by-location summary in connected Microsoft Excel, using the customer's agreed cost-center mapping and retaining source references.
4. Deliver the pack through connected SharePoint with the customer's access permissions, and record outstanding invoice questions.

**The result:** The customer receives a complete, sourced account pack for its covered locations and period.

### Trace a payment that still appears overdue

Finn investigates a customer's payment report across SAP contract-account entries and the connected payment provider, then closes the inquiry with the result.

**Typically handled by:** Utility payment investigation team

**Starts when:** A customer provides a payment reference but the utility account still shows an unpaid amount.

#### What Finn handles

1. Collect the amount, date and reference through the verified service channel and retrieve the matching SAP account items.
2. Compare those items with the settlement status from the connected payment provider, distinguishing a pending payment from a cleared or unmatched entry.
3. For a posting mismatch, send the evidence to the financial owner and follow the authorized correction through its resulting account entry.
4. Explain the confirmed status to the customer and record the settlement or correction reference in the service case.

**The result:** The payment inquiry ends with a verified account explanation or a recorded financial correction.

## Connection setup

Contact Finn to discuss the records your workflow needs and the actions you want it to perform.

Your team chooses what Finn can access, what agents can change, and when a person must approve the work. The connection needs the appropriate account access and permissions from SAP S/4HANA Utilities.

## Industries

- [Utilities](https://joinfinn.com/industries/utilities): Billing cycles, payment follow-ups, service, and accounts.

## Explore Finn

- [Agents](https://joinfinn.com/agents): Help customers. Work with your team. Finish the job.
- [Systems](https://joinfinn.com/systems): Business apps for the work behind the conversation.
- [AI Gateway](https://joinfinn.com/ai-gateway): Control connected AI apps, models, access, and spending.

[All integrations](https://joinfinn.com/integrations)

[Discuss this integration](https://joinfinn.com/contact)

[Discuss your workflow](https://joinfinn.com/contact) · [How it works](https://joinfinn.com/demo/app/#/w/borough/overview) · [Get started](https://joinfinn.com/app/#/signup)