Skip to main content

Different Billing processes in SAP- Transformation from Product Based Billing to Subscription based

In SAP while dealing with Customer, we have to Bill Customer for different goods and services we offer to him

When selling goods from SAP SD, we create Commercial Invoice on the quantity sold

When dealing with Services , we bill the customer for Repair Hour, Accommodation, Travel Hours , Training

When dealing with Projects offered to Customer, Billing similar to services is used

When dealing with Utility sector, we use Consumption based billing to customer

When dealing with Subscriptions we used, Convergent Invoicing to Customer

Altogether the billing process depends on the industry sector and type of goods/Services being offered to the customer

Lets discuss in Detail each process

Commercial Billing for Goods

We normally use this process of billing for Goods we sell to the customer, and billing generally depends on the quantity sold to the customer. This normally takes Sales and Billing route. This is required for Legal process as well, depending on rules and Regulation prevailing in the Sales area

Below figure show basic Sales and Distribution flow with Main Components


 Resource Related Billing:

This process is used in SAP Customer Service and In SAP Project Systems,, while we offer services to the customer.
In this kind of Billing, we bill the customer on Actual hours utilized for the service. This service can be Repair, Maintenance, Travel, Installation, Accommodation and Training or support

Normally we use this billing when we have planned some Activities and executed them with different hours. For example, we have planned an 8 hours of Activity  while performing the task it is realized for 10 hours or 6 hours ( different than Plan) which is actual hours. In such scenario where there is always a discrepancy between Plan and Actual is called to billing using Dynamic Items and in SAP CS and in PS it is called as Resource Related Billing.



Consumption Based Billing:

This is used mostly in Utility sector. Assume a scenario of Water and Power Consumption.  Customer is billed based on the usage of utilities. Usage is calculated based on Meters or Network Elements
We use Contract Account as Customer for Billing and it is slightly different to SD Billing

Here we use Contract Account Concept instead of Customer and Billing is based on the Usage


Subscription Based Billing.

This is mostly Commonly Known and has gained a very significance in recent times.  Netflix, Amazon Prime , Microsoft, Adobe, Retail are best examples of such billing. Here we are not selling customer any products, instead we are selling subscriptions .

Customer Pays a recurring fee at the end of the Period  for using services offered by the company.

I will discuss in detail about Consumption and Subscription based Process in next article



Comments

  1. Your work is very good and I appreciate you and hopping for some more informative posts.
    call center software in Nigeria

    ReplyDelete

Post a Comment

Popular posts from this blog

SAP PM/CS / EAM : Refurbishment Process

Refurbishment A refurbishment order is a standard Maintenance Order type. In customizing for order, we first create an order type ( such as PM04) In the configuration we have to create a new order type in OIOA and activate this for Refurbishment process. Process flow: Business process steps 1. Damaged equipment/ spares if can be repaired will be done by the PM order of type PM04 2. Equipment/Spares needs repairing should have the item code if it is serialized item then with the serial number. 3. Item should have the valuation type for repair category too. 4. Create PR through refurbishment order for repair of the item with split valuation type of repair. Proper G/L codes and order for the repair indent should be provided in the indent 5. After approval of the requisition, the requisition and item should be send to the stores/Purchase section for further actions. 6. Stock will get updated after MIGO of the item 7. The activity type cost ...

SAP SD/CS/PS /PM : System status and User Status a differentiation

In SAP, Master Data and Transaction data is controlled by system status.  But there are certain limitation where system status cannot be used, In such instances a User status can be used. We will see how a system status and User status functions in a particular transaction. Let's understand what is "SYSTEM STATUS" and  "USER STATUS" from system perspective. SYSTEM STATUS:-                                                       A system status is set by the system automatically upon executing a function. It                            Specifies that a particular function was carried out on an Object, be it a                            Transaction ( like Service Order) or a master Data ( serial Nu...

S4HANA/ SD/PP/PS/CS---- Requirements Type and its determination in Sales Order

This Article focuses on Requirement Type and how it is determined in Sales Order. Also  the strategy of Requirement and its Usage Definition of Requirements Type:                Requirement Type Identifies different Requirements like Sales Order, Delivery Requirements,  individual Customer Requirements, Make To Order  or Assembly to Order. Requirements Type uses Planning strategy which has specific strategy for specific Process Requirements Type along with Requirements Class plays a Significant role in determining relevant Functions like, Costing, Settlement, Result analysis, Accounting Indicators,  Special Stock  Indicators, Valuation settings Determining the Requirements Type: To determine  Requirements Type at Sales Order, a sequence of Strategies are defined in Standard Let us check these Strategies 1.  At First, system will check the MATERIAL MASTER--> MRP  3 View-->Strategy...