The Payroll Control Center (PCC) is a fully automated system that leverages SAP’s promise of “run simple”. It represents the next generation of payroll processing automation. With the recent Feature Pack 4 delivery, PCC adds new functions to further simplify and optimize the entire end-to-end payroll process.


The Idea Behind Payroll Control Center


During a payroll cycle, there are certain deadlines that must be met. The employees must receive the payment not later than a specific or the tax declaration statement has to be at the tax authority not later than another specific date. Based on these deadlines, the entire payroll processing window is defined in a kind of “backward termination way”. In almost all cases various iterations have to be done in order to get to a correct result and typically those iterations happen to be over-night batch jobs. So what we see are payroll processes that is heavily influenced by a kind of “batch thinking mentality”. What makes this way of processing really time consuming is the following: The later in the process a problem is found the worse it gets as far as the timeline goes. In this case, one has to go all the way back to start, fix the problem and re-run the whole thing.


Pic1.png

The question is, does it have to be that way? Can we find new ways where we can significantly reduce the processing time? Can we move away from “batch thinking” to something like “real time”, “online”, “interactive”, “on demand”. The answer is, “yes we can”.

The basic and simple idea behind this is: Let’s verify the data quality whenever there’s a change to employee data. Such a “change event” can happen through an HR person changing master data or data is being uploaded/imported through some other programs, etc. A so-called “policy” contains all the validation rules that tell us “Data quality for a specific payroll process is good or not”. Whenever employee data is changed, PCC finds out a change has happened and validates the policy for exactly those employees.

For example, to say if an employee’s data is good for payroll, we may check if all the necessary master data information is available, if the master data is consistent (check field values, combinations of field values), etc. We even can go further and look at the payroll result itself (even at an very early stage) and run checks to see if there’s anything wrong or if the result would be as we expect it. And this exactly brings us to the point of real insights into what we can expect from a payroll run in terms of data quality and accuracy even before we produce it. The production payroll is now just a smal time window as compared to the long one in the “old way”.

Pic2.png

Since the policy is the one and only document that defines in what cases someone needs to get active, we do have suddenly an exception based process. The PCC will let people know when they have to do something (e.g. fix a problem if master data is missing or if the calculation for a wage type is incorrect due to some strange master data constellations, etc.) and will point them to the right solution. In all other cases, people will not be bothered.

You can now include your expert teams into your payroll process even in very early stages. The teams look after the data quality for their specific area of expertise whenever data changes happen. And they make sure that you have a perfect payroll data quality prior to your productive payroll.


Pic3.png

And this exactly brings us to the point where there is real innovation happening:

  • We decouple the process of verifying the data quality for payroll (we call this “one-click monitoring”) from the production payroll.
  • We allow users real-time insights into what we can expect from a payroll run in terms of data quality and accuracy even before we produce it.
  • We allow users to interact with the payroll system rather than sitting and waiting for the results of a batch run.
  • There are no longer the lists that people have to scan to find out what’s going on, whether things are good or bad; there are no longer the tons of tools to double-check the system results.
  • Through using the idea of policies, all know how about “when is a payroll perfect” is kept inside PCC and so is consistently used by everybody (including automated root cause analysis and error resolutions).
  • And, we bring this all together in a new, modern and fresh user experience, which is simple, easy to use and focuses on the absolute necessary things.

With “one click monitoring” you achieve now full transparency of all your end-to-end HR and payroll activities at any time, not just during the critical path of production payroll processing. And finally, your production payroll is just three clicks away.


Payroll Control Center in Action

Let’s have a closer look how PCC works for you during a typical payroll cycle. In the following we will discuss the main elements of PCC (one click monitoring, automated root cause analysis and error resolution, payroll production).

One-Click Monitoring

As a “Payroll Process Manager” you are responsible for the overall process, you ensure correctness and timeline (sign that all steps are executed correctly) and you trigger others to resolve issues. With PCC you now have a fast overview of how good you are doing with your entire end-to-end payroll process. This number tells you how many policy deviations and errors your teams still have to work on in order to get to a perfect payroll. This information is retrieved from the system real time. Whenever there’s a key stroke, Payroll Control Center can validate the impact of that key stroke and let you know instantly whether this is a good key stroke or a bad one.

Pic4.png

The Payroll Control Center offers you analytics for benchmarking and meaningful process improvements. During the process you can easily check how good and healthy you are doing. Here, you can see for example, your difference in gross salary is caused by a bunch of new hires. So you know, there’s nothing wrong with this, nothing to worry about.

And whenever there’s something wrong with the data of your employees, the problems are automatically and immediately assigned to the responsible individuals. You have full transparency of who is working on what.

Pic5.png

Automated Root Cause Analysis and Error Resolution

As a “Payroll Administrator” you are responsible that payroll data quality and payroll calculation for employees is accurate according to defined policies. In case of policy deviations, PCC finds the right “Payroll Administrators” to handle and solve them.

Good validation rules within a policy are designed in such a way that they can give you on the same screen enough context information to solve the problem or even point you to the right solution.

Pic6.png

In this example, the validation rule checks whether an employee receives some extra money through a retro calculation. On one screen you can see what this extra money is and which wage types had caused that extra money. In case the extra money is correct here, you can simply mark this error as “resolved”. If the extra money is not correct (e.g. if the amount of one wage type is incorrect or a specific wage type should not be there), you can choose a solution which takes you to the right place in the system to carry out the corresponding change.

If you need more information to come up with the right solution (in case there are more than one), you can click on the error and access more detailed information.

Pic7.png

Three-Click Production Payroll

After all errors have been taken care of during the “One-Click Monitoring” phase, you can run your productive payroll. This is now just about execution since your payroll data are already accurate.

Pic8.png

To report this post you need to login first.

10 Comments

You must be Logged on to comment or reply to a post.

  1. Rakesh Kumar

    Hi Michael,

    It is nice document related to Payroll employee center (SF),

    We are looking for more deep & technical document.

    Thanx a Tonnnnn!

    (0) 
  2. Kenneth Moore

    Looks promising…with caveats (gotchas!).  You have to be on HANA and decluster your payroll results into transparent tables.  You can decluster your payroll on ECC 6.0, but it is not recommended due to potential performance issues from what I’ve read.  So the waiting game begins until the masses can upgrade to HANA.

    (0) 
    1. Jarret Pazahanick

      Hey Kenneth

      I am currently deploying this for a customer using Employee Central Payroll (SAP Payroll Hosted) and its on EHP7 FP4 but ECP customers are NOT on HANA yet. Havent started any broad performance testing but ping me end of next month and I will let you know how it looks just using the declustered functionality.

      On a side note one of the great pieces of functionality is to be able to do detailed “monitoring” and reporting on simulated payroll results so customers can run many of their audit well in advance of “live” payroll.

      Regards,

      Jarret

      (0) 
      1. Imran Sajid

        Hi Jarret,

        That is very interesting and sounds like a fun project. I am definitely interested to hear about how it goes with the declustered payroll without HANA. How big of a population are you dealing with?

        I know one of the other things that was mentioned about declustering payroll without HANA was database size, but I suppose if your population is not too big then it may be feasible. I guess it is also reasonable if you don’t have someone who has been live with Payroll for many years with a lot of past payroll results.

        Very interesting topic. Let us know how it goes!

        Regards,

        Imran

        (0) 
        1. Jarret Pazahanick

          Population is only 1,500 employees and so far no major performance issues.  Go-live is in October so ping me then and I will be able to provide more specifics on the good, bad and ugly 🙂

          (0) 
  3. Edgar Valverde

    I am currently implementing PCC for a company in Mexico, the entire process is working ok for me, but I have problem running the policies, check the configuration is correct, Someone can help me with any comments or hint for check this problem, the error in the instance of PCC is “not execute instance found” “Stop Execution” 

    (0) 

Leave a Reply