The SAP Utilities (IS-U) component is a sales, billing, and customer information system that supports all business processes for utility companies. It allows companies to manage residential, commercial, and industrial customers and bill for services. Utility companies can customize IS-U to meet their individual needs. Key functions include billing, accounts receivable, customer service, device management, and work order management.
This document lists SAP transaction codes related to SAP IS-Utilities modules, including general IS-U codes, contract billing, intercompany data exchange, invoicing, master data, customer service, device management, energy data management, and waste management. Over 50 transaction codes are included covering areas such as account determination, billing document creation, mass processing, display of contracts and installations, number range maintenance, profile management, and container management.
Deepak Mahle -SAP IS U Billing & InvoicingDeepak Mahle
Deepak Mahle has over 11 years of experience implementing SAP IS-U billing and invoicing solutions for utility companies. He has led projects for clients in the UK, US, Europe, Gulf, and India. His expertise includes business process design, configuration, testing, and support for SAP IS-U billing, invoicing, master data, payments, and integration with other SAP modules. He provides technical leadership and mentors team members to maximize productivity.
For Real time SAP IS Utilities Projects and Online Training in
- Device Management
- Billing and Invoicing
- FICA
- EDM
- BPEM
Please contact Rohit at rohitkapoor7766@gmail.com / sapisumentor@gmail.com with a note on your SAP Background.
This document provides an overview of SAP IS-Utilities and the Customer Interaction Center. It discusses how the Customer Interaction Center provides an integrated platform for customer service agents to process transactions, access customer information, and handle common processes. It also reviews how the Customer Interaction Center is configured, including mapping business processes, defining master data, and allocating CIC profiles in the organizational plan.
This document lists key tables used in SAP IS-U (Industry Solution for Utilities) for billing, invoicing, device and installation master data, profiles, settlements, and data exchange. It includes tables for business partner, contract, product, installation, device, and meter reading master data as well as billing documents, invoices, settlements, and pricing.
This document provides guidance on configuring fleet management in SAP R/3 Enterprise. It discusses setting up master data, units of measure, consumption calculation, the reference object screen, fuel entry transactions, and performance management using transaction S114. Configuring units of measure and consumption calculation correctly is key. The fuel entry transaction allows recording fuel levels and posting costs. Transaction S114 facilitates performance analysis and reporting.
This document lists SAP transaction codes related to SAP IS-Utilities modules, including general IS-U codes, contract billing, intercompany data exchange, invoicing, master data, customer service, device management, energy data management, and waste management. Over 50 transaction codes are included covering areas such as account determination, billing document creation, mass processing, display of contracts and installations, number range maintenance, profile management, and container management.
Deepak Mahle -SAP IS U Billing & InvoicingDeepak Mahle
Deepak Mahle has over 11 years of experience implementing SAP IS-U billing and invoicing solutions for utility companies. He has led projects for clients in the UK, US, Europe, Gulf, and India. His expertise includes business process design, configuration, testing, and support for SAP IS-U billing, invoicing, master data, payments, and integration with other SAP modules. He provides technical leadership and mentors team members to maximize productivity.
For Real time SAP IS Utilities Projects and Online Training in
- Device Management
- Billing and Invoicing
- FICA
- EDM
- BPEM
Please contact Rohit at rohitkapoor7766@gmail.com / sapisumentor@gmail.com with a note on your SAP Background.
This document provides an overview of SAP IS-Utilities and the Customer Interaction Center. It discusses how the Customer Interaction Center provides an integrated platform for customer service agents to process transactions, access customer information, and handle common processes. It also reviews how the Customer Interaction Center is configured, including mapping business processes, defining master data, and allocating CIC profiles in the organizational plan.
This document lists key tables used in SAP IS-U (Industry Solution for Utilities) for billing, invoicing, device and installation master data, profiles, settlements, and data exchange. It includes tables for business partner, contract, product, installation, device, and meter reading master data as well as billing documents, invoices, settlements, and pricing.
This document provides guidance on configuring fleet management in SAP R/3 Enterprise. It discusses setting up master data, units of measure, consumption calculation, the reference object screen, fuel entry transactions, and performance management using transaction S114. Configuring units of measure and consumption calculation correctly is key. The fuel entry transaction allows recording fuel levels and posting costs. Transaction S114 facilitates performance analysis and reporting.
Profit Center Accounting enables structuring a company according to strategic business units (SBUs) to provide full income statements and selected balance sheet items by business line and sector. It reflects material movements between SBUs at commercial transfer prices rather than cost. Master data must be organized by assigning objects to profit centers. Actual values flow through the profit centers in parallel to business transactions. The information system provides reports on profit centers, including interactive and list-oriented reports.
Overcoming the Top 7 Intercompany Accounting Challenges in SAP ERP FinancialsSAPinsider Events
View this session from Financials 2015 in Las Vegas. Coming to Europe! www.Financials2015.com
Overcoming the Top 7 Intercompany Accounting Challenges in SAP ERP Financials by David Cohen, EY
This session will outline and provide resolutions for the seven most common intercompany accounting challenges that companies face within the areas of sale of products, charge of services, AP/AR reconciliation, profit elimination, assets transactions, and month-end closings. By attending you will receive:
- Practical examples on the most effective ways to use standard functionality of SAP ERP, SAP BusinessObjects BI, and SAP HANA to alleviate these issues
- Examples of overcoming difficulties in implementing asset transactions across borders, such as purchase and leasing
- Alternatives to performing inter-company profit elimination
- Lessons for configuring and running your month-end close
The document discusses the differences between intercompany reconciliation in SAP ECC versions compared to SAP R/3 version 4.7. It notes that in ECC versions, intercompany reconciliation is a multi-step process compared to the single step process in 4.7. It also outlines the different transaction codes used to access intercompany reconciliation in the two systems and highlights changes to the screens and additional functionality available in ECC versions.
This presentation covers the basic modules of Financial accouting of SAP FICO module.This is for presentation purpose and doesn't serve as a full fledged presentation on SAP FI
This document provides instructions for configuring various settings in SAP's Project System module, including:
1. Defining special characters, coding masks, and validation rules for project numbers.
2. Creating and maintaining project profiles to store default values and control parameters for new projects.
3. Configuring network types, profiles, numbering, and other settings for managing project networks.
4. Setting parameters for timescales, evaluation periods, and other options used in project planning boards and graphics.
The steps describe technical customizing activities like specifying length limits, indicator settings, default profiles, and other configuration options required to set up the Project System according to an organization's needs and processes.
This document discusses period end billing in SAP, specifically the checkboxes in the Rate Category screen related to period end billing. It explains the options for integrated period end billing, where a separate billing document is added to the last periodic bill of a period, and separate period end billing, where a separate billing document is generated. It provides examples demonstrating how period end billing works when set to integrated vs. separate and discusses fields like the number of periods and delay between bills.
Blogs on Document Splitting at www.veritysolutions.com.au
Document Splitting is a very powerful feature delivered by SAP ECC.
Previous to SAP ECC, if new fields were required to General Ledger SAP had to deliver these new fields in Special Purpose Ledger tables. Profit Centre Accounting in R3 was Special Purpose Ledger table 8*, Joint Venture Accounting was ledger 4*. This essentially meant that data had to be copied from General Ledger table GLT0 to special ledger tables so these could be reported upon. However, technical glitches in code and incorrect usage of functionalities caused imbalances between the main ledger GLT0 and the special purpose ledgers.
SAP customers who wanted to expand the functionality of General Ledger to cater to special business requirements (like reporting General Ledger with another fiscal year variant) had to create custom Special Purpose Ledger tables. For example, if a customer wanted to report by two fiscal year variants, they could report one variant using General Ledger and the other variant using Special Purpose Ledger.
All this disparate ledgers reported the same source information in different views. Customers had to execute several month end jobs to ensure synchronisation of data across all these ledgers. Differences in balances and information between ledgers led to delays in month end close and reporting.
With SAP ECC new GL, SAP Customers can add new fields (which SAP calls “scenarios”) into General Ledger. This allows customers to perform, for example, Profit Centre Accounting and Reporting within General Ledger.
With SAP ECC new GL, SAP Customers can add new ledgers (which SAP calls “parallel accounting”) into General Ledger. This allows customers to report, for example, the same General Ledger data in multiple fiscal year variants.
This replication of data happens in real-time. SAP customers no longer need to execute month end jobs to synchronise data between different ledgers.
The document provides an overview of SAP's Controlling (CO) module, which handles management accounting and cost accounting functions. It describes key CO concepts like cost centers, controlling areas, cost elements, and how CO integrates and shares data with other SAP modules like FI, SD, MM, and PP. It also explains components of CO like cost center accounting, product cost controlling, and profitability analysis and how they are used.
This document provides an overview of SAP Controlling (CO) functionality and implementation. It discusses the main components of CO including cost center accounting, profit center accounting, internal orders, and product costing. It also covers integration with other SAP modules, the three phase implementation approach, and organizational structure setup. Profitability analysis is differentiated from profit center accounting. Cost planning, allocation, and budgeting are described for cost centers. Internal orders are explained for managing projects. Product costing integration with procurement and production is outlined.
Presentation on resource related billingAmlan Sarkar
Resource-related billing involves invoicing customers based on resources consumed. It is common in industries like airlines, defense contracting, engineering, consulting, and public sector. Billing can be complex depending on contract type and calculations that consider resources, overheads, and fees. SAP allows building invoices by linking project systems with controlling, finance, sales, and materials management modules. Dynamic item processors generate invoices by processing financial and cost accounting documents from project postings.
The document provides an overview of SAP's financial modules, including Financial Accounting (FI), Controlling, and FSCM. It describes the key sub-modules and functions of FI such as General Ledger, Accounts Receivable, Accounts Payable, and Asset Accounting. It also explains the processes, master data, transactions, and reporting involved in each sub-module.
This document provides an overview of key concepts in SAP Project Systems (PS) including:
- Project structure using work breakdown structures (WBS), activities, and networks
- Time, cost, and revenue planning
- Budgeting, budget control, supplements, returns, and transfers
- Procurement, commitments, and actual posting
- Project execution, closure by changing statuses to TECO and Closed
- Key reports on budget, actual, commitments, and variances
SAP HANA and SAP Controlling – New Opportunities and New ChallengesJohn Jordan
You've heard the buzz about SAP HANA, but what does it mean to you? This presentation will introduce the technical concepts behind in-memory data management and how those concepts impact SAP Controlling. This session will cover:
*Basic SAP HANA architecture including column vs. row storage and how this impacts how data can be stored and accessed in CO
*Insight into how (and why!) SAP is gradually removing aggregates from CO so that only line items remain
*How partitioning worked in the past and how SAP CO will potentially change to accommodate new opportunities
*Changes on the horizon for SAP HANA and their relevance for Controlling users
Gain a solid understanding of how you can apply SAP HANA functionality to simplify your access to and analysis of controlling data.
The document provides an overview of SAP's Controlling module and its sub-modules. Controlling provides information for management decision making and integrates with other SAP modules. It includes sub-modules like cost element accounting, cost center accounting, internal orders, profit center accounting, product cost controlling, and profitability analysis. Cost center accounting is used for controlling overhead costs and assigns them to locations. Internal orders collect and control costs according to jobs. Profit center accounting evaluates profit/loss of independent organizational areas. Product cost controlling calculates manufacturing and service costs. Profitability analysis allocates costs and revenues to market segments.
Dynamic period control (DPC) allows flexible billing periods and advance or back billing. It manages correction and periodic billing periods. DPC executes billing for simulated periods to generate extrapolated billing information. The user can choose to correct whole periods or just partial periods. DPC requires configuring billing schemas, rate categories, and installations for dynamic period control and estimation of meter readings in billing. Variant programs execute dynamic backbilling for different document periods.
This document provides an overview of SAP PS configuration including defining project structures, time profiles, budgeting and controlling parameters, and scheduling types. It discusses configuring special characters for project coding, project coding masks, field selection for work breakdown structures, and other parameters. The configuration enables structuring projects, planning, monitoring and controlling project progress according to business needs.
A presentation on Payment Management in SAP. It includes Manual and Automatic payment, Process of Automatic Payment Run and Major Blocking points on payment management.
The document provides an overview of the accounts payable process in SAP, including master data, invoice processing, payments, account analysis and reconciliation, and reporting. Key steps include maintaining vendor master records, entering invoices, processing payments, reconciling accounts, and generating reports. Special processes like foreign currency transactions, reversals, and intercompany billing are also summarized.
Automatic Vendor payment advice notes by email with attachment when a payment is made via APP (Automatic payment program by using T-code F110 and email a sap script form as a PDF attachment along with the mail body in the desired language.
This document provides configuration steps for setting up basic funds management functionality in SAP, including maintaining FM areas, assigning company codes and fiscal year variants, activating account assignment elements, defining business areas, configuring general ledger and financial accounting settings, and more. The detailed steps cover areas like public sector management configuration, financial documents, grants management, and funds management master data.
This document discusses the three types of activation for RTP Components in the RTP Interface:
1. Use and activate generally: activation and parameter definition at the RTP interface level for all installations.
2. Use and activate individually: activation at the installation level only, with parameter definitions possible at the RTP interface or installation level using parameter templates.
3. Use individually and activate generally: activation at both the RTP interface and installation levels, with parameter definitions possible at both levels or using parameter templates.
The different activation types provide flexibility in modeling component usage and parameters for individual installations depending on tariff changes or activation times.
This document provides an overview of real time pricing (RTP) basics. It discusses RTP billing, which is based on evaluating energy requirements over time intervals using rate models. Formulas define the calculations used in RTP interfaces. RTP components structure parameter allocations between inputs, outputs, and results. The RTP interface enables using profiles from interval metering in billing by executing processing steps based on the profiles. Screenshots demonstrate various aspects of configuring RTP components, interfaces, rates, and analyzing billing documents.
Profit Center Accounting enables structuring a company according to strategic business units (SBUs) to provide full income statements and selected balance sheet items by business line and sector. It reflects material movements between SBUs at commercial transfer prices rather than cost. Master data must be organized by assigning objects to profit centers. Actual values flow through the profit centers in parallel to business transactions. The information system provides reports on profit centers, including interactive and list-oriented reports.
Overcoming the Top 7 Intercompany Accounting Challenges in SAP ERP FinancialsSAPinsider Events
View this session from Financials 2015 in Las Vegas. Coming to Europe! www.Financials2015.com
Overcoming the Top 7 Intercompany Accounting Challenges in SAP ERP Financials by David Cohen, EY
This session will outline and provide resolutions for the seven most common intercompany accounting challenges that companies face within the areas of sale of products, charge of services, AP/AR reconciliation, profit elimination, assets transactions, and month-end closings. By attending you will receive:
- Practical examples on the most effective ways to use standard functionality of SAP ERP, SAP BusinessObjects BI, and SAP HANA to alleviate these issues
- Examples of overcoming difficulties in implementing asset transactions across borders, such as purchase and leasing
- Alternatives to performing inter-company profit elimination
- Lessons for configuring and running your month-end close
The document discusses the differences between intercompany reconciliation in SAP ECC versions compared to SAP R/3 version 4.7. It notes that in ECC versions, intercompany reconciliation is a multi-step process compared to the single step process in 4.7. It also outlines the different transaction codes used to access intercompany reconciliation in the two systems and highlights changes to the screens and additional functionality available in ECC versions.
This presentation covers the basic modules of Financial accouting of SAP FICO module.This is for presentation purpose and doesn't serve as a full fledged presentation on SAP FI
This document provides instructions for configuring various settings in SAP's Project System module, including:
1. Defining special characters, coding masks, and validation rules for project numbers.
2. Creating and maintaining project profiles to store default values and control parameters for new projects.
3. Configuring network types, profiles, numbering, and other settings for managing project networks.
4. Setting parameters for timescales, evaluation periods, and other options used in project planning boards and graphics.
The steps describe technical customizing activities like specifying length limits, indicator settings, default profiles, and other configuration options required to set up the Project System according to an organization's needs and processes.
This document discusses period end billing in SAP, specifically the checkboxes in the Rate Category screen related to period end billing. It explains the options for integrated period end billing, where a separate billing document is added to the last periodic bill of a period, and separate period end billing, where a separate billing document is generated. It provides examples demonstrating how period end billing works when set to integrated vs. separate and discusses fields like the number of periods and delay between bills.
Blogs on Document Splitting at www.veritysolutions.com.au
Document Splitting is a very powerful feature delivered by SAP ECC.
Previous to SAP ECC, if new fields were required to General Ledger SAP had to deliver these new fields in Special Purpose Ledger tables. Profit Centre Accounting in R3 was Special Purpose Ledger table 8*, Joint Venture Accounting was ledger 4*. This essentially meant that data had to be copied from General Ledger table GLT0 to special ledger tables so these could be reported upon. However, technical glitches in code and incorrect usage of functionalities caused imbalances between the main ledger GLT0 and the special purpose ledgers.
SAP customers who wanted to expand the functionality of General Ledger to cater to special business requirements (like reporting General Ledger with another fiscal year variant) had to create custom Special Purpose Ledger tables. For example, if a customer wanted to report by two fiscal year variants, they could report one variant using General Ledger and the other variant using Special Purpose Ledger.
All this disparate ledgers reported the same source information in different views. Customers had to execute several month end jobs to ensure synchronisation of data across all these ledgers. Differences in balances and information between ledgers led to delays in month end close and reporting.
With SAP ECC new GL, SAP Customers can add new fields (which SAP calls “scenarios”) into General Ledger. This allows customers to perform, for example, Profit Centre Accounting and Reporting within General Ledger.
With SAP ECC new GL, SAP Customers can add new ledgers (which SAP calls “parallel accounting”) into General Ledger. This allows customers to report, for example, the same General Ledger data in multiple fiscal year variants.
This replication of data happens in real-time. SAP customers no longer need to execute month end jobs to synchronise data between different ledgers.
The document provides an overview of SAP's Controlling (CO) module, which handles management accounting and cost accounting functions. It describes key CO concepts like cost centers, controlling areas, cost elements, and how CO integrates and shares data with other SAP modules like FI, SD, MM, and PP. It also explains components of CO like cost center accounting, product cost controlling, and profitability analysis and how they are used.
This document provides an overview of SAP Controlling (CO) functionality and implementation. It discusses the main components of CO including cost center accounting, profit center accounting, internal orders, and product costing. It also covers integration with other SAP modules, the three phase implementation approach, and organizational structure setup. Profitability analysis is differentiated from profit center accounting. Cost planning, allocation, and budgeting are described for cost centers. Internal orders are explained for managing projects. Product costing integration with procurement and production is outlined.
Presentation on resource related billingAmlan Sarkar
Resource-related billing involves invoicing customers based on resources consumed. It is common in industries like airlines, defense contracting, engineering, consulting, and public sector. Billing can be complex depending on contract type and calculations that consider resources, overheads, and fees. SAP allows building invoices by linking project systems with controlling, finance, sales, and materials management modules. Dynamic item processors generate invoices by processing financial and cost accounting documents from project postings.
The document provides an overview of SAP's financial modules, including Financial Accounting (FI), Controlling, and FSCM. It describes the key sub-modules and functions of FI such as General Ledger, Accounts Receivable, Accounts Payable, and Asset Accounting. It also explains the processes, master data, transactions, and reporting involved in each sub-module.
This document provides an overview of key concepts in SAP Project Systems (PS) including:
- Project structure using work breakdown structures (WBS), activities, and networks
- Time, cost, and revenue planning
- Budgeting, budget control, supplements, returns, and transfers
- Procurement, commitments, and actual posting
- Project execution, closure by changing statuses to TECO and Closed
- Key reports on budget, actual, commitments, and variances
SAP HANA and SAP Controlling – New Opportunities and New ChallengesJohn Jordan
You've heard the buzz about SAP HANA, but what does it mean to you? This presentation will introduce the technical concepts behind in-memory data management and how those concepts impact SAP Controlling. This session will cover:
*Basic SAP HANA architecture including column vs. row storage and how this impacts how data can be stored and accessed in CO
*Insight into how (and why!) SAP is gradually removing aggregates from CO so that only line items remain
*How partitioning worked in the past and how SAP CO will potentially change to accommodate new opportunities
*Changes on the horizon for SAP HANA and their relevance for Controlling users
Gain a solid understanding of how you can apply SAP HANA functionality to simplify your access to and analysis of controlling data.
The document provides an overview of SAP's Controlling module and its sub-modules. Controlling provides information for management decision making and integrates with other SAP modules. It includes sub-modules like cost element accounting, cost center accounting, internal orders, profit center accounting, product cost controlling, and profitability analysis. Cost center accounting is used for controlling overhead costs and assigns them to locations. Internal orders collect and control costs according to jobs. Profit center accounting evaluates profit/loss of independent organizational areas. Product cost controlling calculates manufacturing and service costs. Profitability analysis allocates costs and revenues to market segments.
Dynamic period control (DPC) allows flexible billing periods and advance or back billing. It manages correction and periodic billing periods. DPC executes billing for simulated periods to generate extrapolated billing information. The user can choose to correct whole periods or just partial periods. DPC requires configuring billing schemas, rate categories, and installations for dynamic period control and estimation of meter readings in billing. Variant programs execute dynamic backbilling for different document periods.
This document provides an overview of SAP PS configuration including defining project structures, time profiles, budgeting and controlling parameters, and scheduling types. It discusses configuring special characters for project coding, project coding masks, field selection for work breakdown structures, and other parameters. The configuration enables structuring projects, planning, monitoring and controlling project progress according to business needs.
A presentation on Payment Management in SAP. It includes Manual and Automatic payment, Process of Automatic Payment Run and Major Blocking points on payment management.
The document provides an overview of the accounts payable process in SAP, including master data, invoice processing, payments, account analysis and reconciliation, and reporting. Key steps include maintaining vendor master records, entering invoices, processing payments, reconciling accounts, and generating reports. Special processes like foreign currency transactions, reversals, and intercompany billing are also summarized.
Automatic Vendor payment advice notes by email with attachment when a payment is made via APP (Automatic payment program by using T-code F110 and email a sap script form as a PDF attachment along with the mail body in the desired language.
This document provides configuration steps for setting up basic funds management functionality in SAP, including maintaining FM areas, assigning company codes and fiscal year variants, activating account assignment elements, defining business areas, configuring general ledger and financial accounting settings, and more. The detailed steps cover areas like public sector management configuration, financial documents, grants management, and funds management master data.
This document discusses the three types of activation for RTP Components in the RTP Interface:
1. Use and activate generally: activation and parameter definition at the RTP interface level for all installations.
2. Use and activate individually: activation at the installation level only, with parameter definitions possible at the RTP interface or installation level using parameter templates.
3. Use individually and activate generally: activation at both the RTP interface and installation levels, with parameter definitions possible at both levels or using parameter templates.
The different activation types provide flexibility in modeling component usage and parameters for individual installations depending on tariff changes or activation times.
This document provides an overview of real time pricing (RTP) basics. It discusses RTP billing, which is based on evaluating energy requirements over time intervals using rate models. Formulas define the calculations used in RTP interfaces. RTP components structure parameter allocations between inputs, outputs, and results. The RTP interface enables using profiles from interval metering in billing by executing processing steps based on the profiles. Screenshots demonstrate various aspects of configuring RTP components, interfaces, rates, and analyzing billing documents.
This document discusses using an RTP interface in SAP to create an electricity rate with different rates for on-peak, off-peak, and maximum demand. The RTP interface uses two components, one to divide consumption into on and off-peak periods using time-of-use groups, and another to determine the maximum demand. Screenshots show the configuration of the RTP interface, components, operands, rate, profile, and billing documents.
1. The payment scheme is a statistical budget billing procedure that prorates consumption amounts from past and current billing periods across the next billing period.
2. Payment schemes allow payments at intervals like weekly, monthly, or quarterly and are not limited to a specific period. When a periodic bill is created, the payment scheme is adjusted rather than ended.
3. Payment schemes can include or exclude credit and receivables items from the same contract and cannot be used with collective bills.
This document discusses budget billing procedures for utility companies. It describes four budget billing procedures: 1) statistical procedure, 2) debit entry (partial bills) procedure, 3) payment plan procedure, and 4) payment scheme procedure. It provides details on how budget billing amounts are calculated and distributed over monthly periods to maintain steady cash flow for the utility company and steady monthly payments for customers.
SURE! Subscription Billing & Relationship Management for IaaS providers SURE!
Learn how SURE! end to end Subscription Billing and Relationship Management can become a right solution for IaaS providers to streamline their business models.
SURE! is a Magnaquest product. SURE! is an end-to-end Subscription Lifecycle Management Platform from Magnaquest. SURE! supports different domains like Cloud (IaaS, SaaS, Unified Communication) Broadband (FTTX, WiMAX, Wi-Fi, Cable, ADSL) , Dual Play, Triple Play Telecom, MVNO & M2M, Pay TV (Cable, DTH, DTT, Broadcaster, IPTV, OTT) and Home Utilities. SURE! has been redefining and catalyzing ROI of our clients, spread globally, in verticals like Media & Entertainment, Broadband and Cloud businesses, with a product suite spanning Billing and Revenue Management, CRM, Session Control, OSS and Campaign management.
Advanced recurring and subscription billing for Netsuite. Built on the NetSuite platform and fully compatible with NetSuite's advanced revenue management.
Invoice and accountancy system
We created a new system to improve invoicing and accounting process management in seamless integration with the existing enterprise information system.
Pegasus Business Software - Opera 3 Upgrade GuideRichard Common
Protect the future of your business by moving to Opera 3, our multi-award-winning flagship solution.
We’ve added lots of new features and enhanced many areas to help you improve the way you work.
Improved reporting is a key benefit, with over 60 reports you can export directly to Excel®. Opera 3 also offers open period accounting, error correction functionality in the ledgers, the ability to connect with your Opera 3 data remotely and a whole host of other features, designed to
help you increase your visibility of the business and improve
efficiency and decision-making.
What’s more, if you upgrade to Opera 3, you’ll have the option of deploying it in the Cloud, so your entire business solution will be accessible at any time, from any device, and you’ll save on hardware infrastructure and maintenance costs.
Upgrading is easy with the help and support you’ll receive from your Pegasus Partner - PCI Services. The implementation process is straightforward and minimal training is required, so you can start reaping the benefits straight away.
http://www.pciservices.co.uk/business-software/pegasus-opera-3
In this live webinar we will review all the steps to performing a Sage 300 (Accpac) Year-End Closing, followed by a Q&A Session at the end.
- Year-End Closing Preparation
- Timing
- Back Up Procedures
- Creating New Fiscal Year
- Year-End for A/R and A/P
- W-2 & 1099s
- Year-End Reports
This document describes billing plans in SAP. It discusses the different types of billing plans including periodic billing which is used for rental contracts, and milestone billing which is used to distribute amounts over billing dates based on project milestones. It describes how billing plans are controlled through billing plan types, date categories, and assigning billing plan types to items. Key functions of billing plans are also summarized such as automatic creation of dates, pricing, billing blocks, and document flow.
The document describes billing plans in SAP. Billing plans allow companies to schedule billing dates for items in sales documents. There are two main types of billing plans:
1. Milestone billing distributes the total amount over multiple billing dates based on project milestones or percentages of completion.
2. Periodic billing schedules regular, periodic payments such as monthly rental fees. The system can automatically generate periodic billing dates based on start/end dates and billing frequency defined in the contract.
Billing plans are controlled through billing plan types, date categories, and item categories defined in customizing. This allows standardizing billing rules and date determination for different business cases.
- The document provides a summary of Pallavi Shrivastava's work experience including over 5 years working on SAP implementations, upgrades, and support projects for clients in various industries.
- Pallavi has experience delivering projects for Centrica (British Gas Business) and Consumer Energy involving configuration and support of SAP FI, CO, and IS-U modules.
- Her responsibilities have included functional testing, interface development, issue resolution, enhancement configuration, and ensuring adherence to SLAs.
Cloud Computing encompasses a broad range of services that are available upon subscription. With several significant developments, evolution and revolution; cloud technology has evolved to encompass Software as a Service (SaaS), Platform as a Service (PaaS), Infrastructure as a Service (IaaS), Security as a Service, and On Demand Services over the Internet, among others. Apart from this, many vendors have seized the term ‘Cloud’ and are using it for products that sit outside of the common definition of cloud. The cloud marketplace is progressively becoming more diverse, and incoherent, at the same time.
The Aptitude Revenue Recognition Engine is a software solution that helps companies comply with IFRS 15 and ASC 606 accounting standards for revenue recognition. It addresses the five-step revenue recognition process through rules-driven data preparation, contract and performance obligation modeling, transaction price calculation and allocation, and revenue recognition automation. The product is designed specifically for telecommunications companies to handle their complex revenue streams and contracts.
- The document describes billing plans, which define schedules of billing dates for items in sales documents. There are two main types of billing plans: periodic billing, which bills a total amount on set dates, and milestone billing, which distributes amounts over dates linked to project milestones.
- Billing plans are controlled through billing plan types, date categories, and date descriptions defined in customizing. These determine how dates are automatically set and what data is associated with each date.
- Periodic billing typically uses monthly or quarterly intervals between set dates. Milestone billing links dates to percentages of project completion or amounts upon reaching project milestones.
The Accounts Receivable process begins when goods are shipped to a customer. This triggers SAP to automatically send an invoice by integrating customer and shipment data, posting to the Accounts Receivable subsidiary ledger and reconciliation account. When payment is received, the remittance advice applies the cash to open items on the customer account.
The Accounts Receivable module is organized using clients, company codes, and reconciliation accounts. Master data for customers is maintained at different levels, with general data at the client level and accounting/sales data at the company code level. Reconciliation accounts link subledgers like Accounts Receivable to the general ledger.
Customer master records contain key identification and contact information as well as account settings that control billing,
The document discusses how CO-PA (SAP's Profitability Analysis tool) and SAP BW (Business Warehouse) work together as a powerful combination for profitability reporting. CO-PA provides consistent profitability data while SAP BW allows for advanced reporting and analysis of this data across multiple systems. Some key benefits include separating transactional and reporting tasks to optimize performance, consolidating data from various R/3 systems, and integrating data from non-SAP legacy systems.
Microsoft Dynamics 365 Business Central Capability GuideDynamics Square
Microsoft Dynamics 365 Business Central Capability Guide, Get in Touch for Business Central Pricing, Demo & Implementation: https://www.dynamicssquare.com.au/business-central-implementation/
TimelyBill is a SaaS based solution for communications service providers and subscription billers. TimelyBill enables companies to introduce products, generate invoices, collect payments, offer bundles, share profit with partners, detect fraud and many other revenue related functions.
Accounting Information System Financial Reporting DesignCharlie Congdon
This document describes the design of a financial reporting system for a wireless telecommunications company in the Philippines. It includes details on the company's operations, accounting processes, reports, and controls. The telecom derives income from postpaid plans, prepaid subscriptions, and internet connections. It also generates revenue from selling SIM cards and modems. Transaction records are stored electronically. The financial reporting system involves updating the general ledger, posting adjustments, preparing financial statements, and generating managerial reports. It includes both general controls over IT resources and application controls to ensure accurate financial reporting.
The document discusses SAP CRM middleware which ensures configurable business object data is distributed from source systems to receivers. It controls data flow and adapters. The middleware consists of a central component and R/3 plugins. Business data in messages refer to business objects like customers and are distributed using Bdocs.
The document also discusses how CRM middleware connects SAP R/3 and IS-U systems using RFC destinations. It provides links on how to create RFC destinations and sites for middleware. Technical objects can be created and changed in IS-U and replicated to CRM. Contracts can be created in CRM and replicated to IS-U, updating master data. Status of CRM contracts is updated following replication success
AVReporter is an intelligent reporting and data visualization tool with the following key features:
1. It can be installed as both a desktop and web-based solution for flexibility.
2. It includes localization options for global and local settings.
3. It has a modular structure allowing for flexible extensions.
4. Modules include desktop management, basic reporting, energy management summaries, business intelligence calculations, cost allocation, and connection centers for data integration.
1. SAP Industry Solution Utilities (IS-U) Overview
Mike Davis
Program Director
The SAP Utilities (IS-U) component is a primarily a sales and information system that supports all
business processes and utility services of a utility company. The SAP Industry Solution Utilities (IS-
U) can be used for managing and billing residential, commercial and industrial, and prospective
customers. This SAP solution also allows utility companies to manage and bill customers who
receive services, purchase goods, or pay fees and taxes.
It supports a varied range of divisions and business partners and provides a large number of
functions. Furthermore, IS-U processes all business transactions and activities with a central
business partner jointly, and it offers account management, which integrates all of a business
partner’s payment transactions.
In addition, utility companies can take advantage of powerful customising functions and the
flexibility of the SAP R/3 System to customise the IS-US system processes to meet individual
requirements. This means that it can be deployed in utility companies of various sizes and shapes
– each with its own individual corporate and market strategy.
Utility companies use SAP IS-U to bill all the traditional divisions:
❑ Electricity
❑ Gas
❑ District heating
❑ Water and waste water
Within SAP IS-U the Billing and Invoicing module starts with meter readings and finishes with Bill
print out. This document provides an outline of all IS-U master data and functions relevant to
Billing Process.
The following list outlines the core business processes that can be handled by SAP IS-U:-
Billing Process Scheduled Billing,
Billing Process Produce Invoice Statements,
Joint Invoicing,
Process Invoice Printing,
Billing Process Bill Inserts And Messages,
Billing Process Send Sms For The Month,
Process Send E-bill For The Month,
Billing Process To Send More Than One Bill Copy For A Month,
Billing Process Display Latest Bill For The Month On The Web,
Billing Process Category Change,
Billing Create Maintain Installation Facts,
Billing Process Individual Reversal Or Adjustment.,
Billing Process Mass Reversal Adjustment,
Billing Process Produce Invoice Statements,
Billing Process Display Latest Bill For The Month On The Web,
Billing Process Mass Reversal Adjustment,
Billing Process Duplicate Invoice Statement.,
Billing Process Bill Batching,
Billing Create Maintain Rate Tariff Structure,
Billing Create Maintain Price,
Billing Create Maintain Discounts Surcharges Prices,
2. Billing Process Bill Simulation,
Billing Process Bill Exceptions And Errors,
Billing Process Unscheduled Bill
The key functional areas are as follows:
Billing Master Data
Billing Class
Rate type
Price
Operand
Variant Program
Rate
Fact Group
Schema
Rate Category
Invoicing
Invoicing Functions
Account Maintenance
Due Dates
Credit Processing.
Joint Invoicing / Integration
Outsorting in Invoicing
Invoice Reversal
Billing
Billing overview
Billing reversal and Adjustment
Manual Billing
Billing Exception
Billing Outsort
Billing Exception
IS-U is integrated with the SAP Service Management (PM-SMA) and Sales and Distribution (SD)
application components of the R/3 System, it can also bill service orders and service contracts for
services of all types, plus the sale of goods, such as meters, heat pumps, and consumption
devices.
IS-U jointly invoices (if desired and appropriate in terms of time) all the services that a utility
company provides to customers. It combines them into a single bill and processes them for
accounts receivable via Contract Accounts Receivable and Payable.
In addition SAP IS-U can include the billing results from external billing systems into the invoicing
process (via an interface). This allows IS-U to collectively create bills and process accounts
receivable with the billing results.
Of particular significance in IS-U is the collective billing of services from more than one company.
This includes convergent billing and inter-company billing.
With convergent billing, a utility company can manage the services of a third party and include
them in its own bill.
Examples include:
❑ Waste disposal in behalf of the city sanitation department
❑ Cable charges for telecommunications companies
❑ Drainage charges on behalf of the municipality.
3. With inter-company billing, several independent companies (each with their own separate balance
sheets) can combine their services into a single bill. The services are based on contracts with
different company codes.
Integrating services from more than one company provides advantages to both consumers and
utility companies. Integration is also the foundation for future forms of billing in a deregulated utility
industry where the services of any one division consist of service components from more than one
company.
Functions and Special Features
Basic Functions and Tools
With the basic functions of IS-U, utility companies can manage the addresses and regional
structures and generate scheduled dates for meter readings, budget billings, and regular billings.
The print workbench gives you the capability for flexible layout of bills and other customer letters
using SAPscript, the word processing system of the standard R/3 System. A utility company can
either edit the data in SAPscript and pass it to the printer, or it can make the data available for
mass printing at the raw data interface (RDI).
Other functions allow:
❑ Legacy system data migrations
❑ Configure screens with tab strips
❑ Enter non-standardised additional information as notes
❑ Store time-dependent data as information in a history
❑ Maintain number ranges to assign unique sort features
❑ Set up flexible access protection
❑Log changes
Master Data
The master data in IS-U includes:
❑Business partners
❑Contracts and contract accounts
❑Connection objects (such as buildings or land) and the premises, utility installations, and device
locations they contain
Device Management
For managing utility company devices, meters, and equipment, IS-U offers the following functions:
❑The capability to divide devices into device categories
❑Meter and device procurement, warehousing, and stock movements using integration with the
Materials Management (MM) component
❑Maintain installation structures with their existing relationships between meters, devices,
registers, and rate data
❑Maintain rate reference values and other information about the purchase of power
❑Installation, removal, and replacement of meters and devices
❑Device inspection and certification based on a sampling procedure or individual certification
In addition, device management allows you to create meter-reading orders and enter consumption
and demand. In this area, IS-U offers the following functions:
❑ Create meter reading orders and documents in printed or machine-readable form
❑ Enter meter reading results manually or automatically
❑ Conveniently connect external entry systems
❑ Validate meter reading results
❑ Correct or post-process meter reading results
❑ Monitor meter reading
❑ Valuate at flat rates consumption and demand on the basis of various replacement values (such
as the number of cable television connections or the energy intake of streetlights)
4. Contract Billing
Billing is the core of IS-U/CCS. It covers the billing of supply categories and ser- vices. In addition,
you can incorporate the services that you processed and billed with the Service Management and
Sales and Distribution components and the meter reading results from external billing systems in
IS-U/CCS invoicing
A contract is billed as follows:
1. The necessary data is collected.
2. The data is prorated. The system accounts for price and tax changes during the billing period.
3. The system converts the readings into billable quantities (such as register fac- tors or thermal
gas billing).
4. The quantities are valued using rates in which the utility company has stored its billing rules.
5. The meter reading results are validated and form the basis for invoicing.
IS-U supports the following forms of billing:
❑ Periodic billing
❑ Floating back-billing
❑ Period-end billing
❑ Interim billing
❑ Final billing
❑ Budget billing and average monthly billing or equalised billing
The most important functions of contract billing are as follows:
❑ IS-U supports as billing cycles both annual consumption billing and monthly billing cycles for
less than a year.
❑ The system bills nonresidential and residential customers in the same data structures with the
same functions. The two types of customer are differentiated only by the data.
❑ All forms of billing can me reversed and credit memos and back-billings can be initiated.
❑ In addition to automated billing, you can use manual billing
❑ IS-U/CCS supports many division-specific types of billing. Some examples are:
❍Thermal gas billing procedures
❍ Billing of public lighting using electricity or gas
❍Waste disposal
❍ Company and plant consumption of the utility
❍Billing for employees
Invoicing
❑Generates accounting documents for receivables and credit memos from billing documents
❑ Offsets accounting documents against down payments made, particularly paid budget billings
❑ Formats data for bill printout
❑ Creates new budget billing plans
❑ Supports the calculation of taxes
With bill printout you can flexibly design and display your bills according to your needs. You can
print bills using the IS-U/CCS print workbench or make them available to external print systems for
mass printing. In addition, you can insert individual notification texts or flyers with printed
documents.
Contract Accounts Receivable and Payable
Because of their large numbers of customers and generally monthly billing or budget billing
request, utility companies create large volumes of requests for payment. So that you do not have
to maintain this mass data under General Ledger Accounting, IS-U offers an integrated sub-ledger
called contract accounts receivable and payable. Contract accounts receivable is especially
designed to meet the needs of mass processing. At specific intervals, the system transfers the
accumulated individual postings to the general ledger of the Financial Accounting (FI) component
5. or to the general ledger of a third-party system. You can also transfer sales or service invoices from
the Sales and Distribution component to contract ac- counts receivable and payable.
The objective of contract accounts receivable and payable is to automate all trans- actions as far
possible. You only need to manually intervene when a transaction requires a decision.
The most important characteristics of contract accounts receivable and payable are the following:
❑You can individually customise account and open-item displays.
❑ In response to certain business transactions, the system automatically creates printed
documents (such as checks, account statements, and returns correspondence) and
correspondence with user-defined text.
❑ Using a neutral interface, the system can transfer and automatically perform postings that
result from automated incoming payments (from front-end systems, financial institutions, or
agencies), from collection procedures, credit refunds, or returns processing.
❑ The system can process and include in invoicing down payments for energy consumption
(budget billings) and for services to be performed in the future.
❑ You can impose payments in advance or security deposits on customers with a negative
payment history or a bad credit rating.
❑ Flexible dunning is based on dunning levels that you can define for each receivables item.
Every utility company can define the individual steps of the dunning proceedings itself. The
system maintains all information relevant to dunning in a history that is the basis for a credit
rating.
❑ You can calculate interest on debit and credit items at the line-item level. You can determine
rates of interest individually depending on the business partner or transaction concerned (so far
as legal requirements, for example, exist).
❑ You can defer receivables items or transfer them to instalment plans.
❑ You can send documents relating to different accounts or business partners jointly to a
collective bill recipient, for example, a housing construction company).
❑ You can identify receivables as good, doubtful, and irrecoverable and then process them
accordingly.
❑ You can manage and process unelectable incoming payments.
❑ Receivables items are included in financial accounting.
SAP Business Workflow
The SAP Business Workflow component of the standard R/3 System allows you to coordinate
business-process flows across applications. Underlying the workflows is a model of the various
business processes that you define.
A workflow consists of individual steps performed by a single person, possibly time-delayed, or by
a number of different people. The system can execute certain steps automatically, such as initiating
a confirmation letter after a rate change or logging changes (such as change in the contract, bank
data, or budget billings) that result from a customer contact. The SAP Business Workflow
component pro- vides technologies and tools for automatic control and processing of workflows. It
allows you to adapt IS-U/CCS and the standard R/3 System to meet the needs of your utility
company.
It makes sense to map a business process as a workflow if it:
❑ Keeps occurring in the same or in a similar form
❑ Consists of a number of possibly cross-application processing steps that have to be executed
as a structured whole
❑ Consists of a number of processing steps involving more than one person or departments or
that are time delayed
IS-U/CCS contains predefined reference workflows for some of the more important business
processes. These include processes for disconnecting and reconnect- ing a utility installation and
installing a service connection. These workflows are discussed in the chapter titled Business
Processes.
The organisational plan of the utility company determines which staff members are involved in a
workflow. You can define this organisational plan using the Organisational Management
6. component of the standard R/3 System. The system assigns tasks automatically to the appropriate
staff members. The system processes the assignment of work via the integrated inbox, which
supports staff members as they work. The workflow also ensures that required actions, such as the
notification, are not overlooked. A log allows you to trace exactly the steps executed for each
process. In addition, you can trace the status of any workflow.
If deadlines are missed, the system can automatically notify a supervisor. A flexible information
system allows you to analyse the runtimes of individual steps and processes. With this data you
can identify weak points in the application flow and optimise the relevant processes.
Customer Service
Every year, larger utility companies deal with several hundred thousand direct customer contacts.
In light of this large number, efficient processing of contacts is an important performance
characteristic of IS-U/CCS. In particular, entering business transactions places considerable
demands on the user interface, service flow, and response time of the system.
The front office is the most important part of customer service. This is where customers can obtain
information on all the important data and start all the processes that are important to their work
centres. Depending on the content of the business processes, it uses R/3 workflow management to
support the flow of those processes.
You can configure the front office to your requirements in Customising. These configurations allow
you to set up a work environment specifically suited to a particular staff member and to define
which data and transactions that the staff member is allowed to access.
In its customer information IS-U/CCS offers various ready-made views with which staff can provide
customers with information on, for example, their data and accounts. Workflow management
contains predefined transactions with which staff can handle such jobs as:
❑ Creating a new premise
❑ Processing a move-in
❑ Changing a contract
❑ Entering a fault report.
The initial step in any customer contact in the front office is the identification of the customer, which
is supported by a powerful search function, the Data Finder. You define in Customising which data
the system uses as search criteria. You can automate this step by integrating a computer
telephone integration (CTI) system and display an initial information screen that contains
information on the customer.
Once the customer has been identified, your staff can call up information screens and then branch
from there to additional, detailed views. If changes are required, you can make them on the spot.
For example, you can change bank details or process a move-in.
If you cannot complete the transaction because required data is unavailable or if detailed
processing is required, you can:
❑ Initiate a workflow
Depending on the definition of the workflow, you continue the transaction in
the back office when the necessary events have occurred
❑ Create a follow-up for the appropriate person
In this case, you can enter customer information in a note and attach it to the follow-up.
IS-U automatically logs the customer contact. You can enter notes on a customer contact. You can
quickly obtain an overview of prior contacts and sort them according to various criteria, such as
prior dunning events or field service operations. The log record for the customer con- tact
references the relevant object or documents. This means that you can display the dunning letter
sent for a dunning event, for example, directly from the log.
Work Management
The efficient performance of services is increasingly important for utility compa- nies in times of
growing competition and increased customer orientation. Utility companies consequently plan and
cost such services as work orders. Examples include:
❑ Setting up service connections
❑ Maintaining technical equipment, performing periodic device replacement
7. ❑ Processing repairs and reports of damage
❑ Creating collection and disconnection orders
❑ Performing energy consulting
In IS-U, Work Management processes those work orders. Work Management uses functions from
the standard Plant Maintenance and Service Management component and integrates them with
industry-specific functions from IS-U to form cross-component business processes.
In many cases you can bill customers for work orders. Where this is the case, the system executes
the Inquiry ® Quotation ® Order transaction before the work order and the Billing ® Invoicing
transaction after the work order. The system handles these transactions based on the integration of
the Plant Maintenance and Service Management and the Sales and Distribution components.
You can combine the billing results for services from Sales and Distribution with the results for
energy billing from IS-U in invoicing and show them on a single bill.
Information System
The Information System enables you to analyse the data resources underlying IS-U. Like other
components of R/4 IS-U offers a variety of analytics:
❑ Statistics
Thew statistics are based upon a statistical dataset, which the system updates continuously or
monthly from dialog or batch functions. IS-U distinguishes between three different statistics
applications:
❍ Stock
❍ Transaction
❍Sales
The Logistics Information System (LO-LIS) component of the standard system enables you to
evaluate the statistical dataset The LIS system offers many different options for evaluating,
analysing and presenting data
❑ IS-U Navigator
With the IS-U navigator you can get a quick overview of how the data interrelates within IS-U.
starting from any given object such as a customer you can use graphics to navigate through the
entire data environment of an object.