PF Contribution - Proration

This is related to India Payroll PF Calculation.
Here PF Basis = Basic Pay & Eligible Pay = Rs 6500/-.
Eligible pay or PF basis, whichever is less, standard system
considers that as the PF contribution.
For Ex:
If Basic Pay <= Rs 6500, PF wud be 12% of actual Basic
If Basic Pay > Rs 6500, PF wud be 12% Rs 6500
This is working fine in the standard system.
Current Requirement is:
When there is a loss of pay for an emp, the Basic is prorated
accordingly. But the twist in the story is The Eligible Pay also
needs to be prorated. And then, the lesser of the prorated basic
& prorated eligible pay is to be considered for the PF
calculation.
For Ex:
An emp with basic pay of Rs8000, has 3 day's loss of pay in a
month. The prorated basic becomes Rs7200 for that month
deducting 8000*3/30 as loss of pay from basic pay, which is
still higher than the eligible pay. In such a scenario, the
system should not calulate PF based on the eligible pay of
Rs6500. Instead it has to prorate the eligible pay accordingly
and then consider the lesser of prorated basic and prorated
eligible pay for PF calc. i.e;
Prorated eligible pay = Rs5850 [deducting 6500*3/30 as loss of
pay from eligible pay]
How to prorate this Eligible Pay ?

Rajesh did u checked with the PF office
does the acts say same
please let us know generally it shd get Prorated
The proration as mentioned by you happens only when the employee joined/left in the middle of the month. However, in case of LOP, PF is calculated on the earned basic (reduced) and eligible pay, whichever is less. Please check with your legal counsel for getting legal opinion on the matter.
However, if you still need to prorate the eligible pay based on LOP days, then write a rule which will check the value of /111 and limit it to eligible pay (prorated in case of LOP) before function INEPF is called in the schema. This way the value passed on to INEPF in WT /111 will be the prorated value and your requirement will be met.
But, I would still ask you to get legal opinion on the same as it may lead to statutory default in case the standard calculation is correct. It is always better and legally safe to deduct and contribute more PF.
inputs given by VK (Vivek)
Edited by: Sikindar on Jun 18, 2009 4:42 PM

Similar Messages

  • Problem with prorata calculation of pf contribution

    Hello
    I have an issue in employee pf calculation on selecting the eligible pay or pf basis whichever is less in infotype 587. When i select this option in IT-587 the pf contribution gets restricted to Rs.780
    Now in case the employee is absent for a couple of days in a month then this calculation gets reduced.eg if one day absesnce is there it becomes 755(780/31*30). Here the employee pay is more than the pf basis which is Rs.6500
    I need to the system to continue deducting 780 till the employee receives more than 6500, even though he may be absent.i.e prorating should not take place in such cases.
    regards
    sameer
    Message was edited by:
            sameer k

    Hi
    You can do at two ends
    1 INEPF.
    2 By rule.
    I will prefer the INEPF.
    Now jsut do one thing ask the ABAPer to debugg it , in INEPF it is calulating dont know exact code.
    it is easy to find out .
    And add the codings after the calculation.
    It will be very easy.
    Manoj Shakya.
    Close the thread.

  • Proration of ER Pension Contribution - GB Payroll

    Hi Experts,
    My client requirement is that the ER pension contribution (based on full pay) should be calculated till the EE gets Statutory payment ie if an EE goes on maternity leave the ER Pension contribution should be calculated till the EE gets SMP Pay.
    So i passed on the Pension elements to a notional Wage type (9000), and wrote a PCR on proration and assigned it to the notional WT. The ER contribution gets calculated till the EE goes on maternity leave. The calculation get stopped from the first month the EE goes on maternity leave.
    I checked the Schema, i can see my notional WT in IT table and OT Table of GPEN, but the calculation is not happening.
    kindly suggest me how should i proceed on this.

    Did you check the specification of the Evaluation Class 02 for the wagetype under concern (used for pension type) in table V_512W_D? This controls the printing on the rem statement.

  • Pension Contribution

    Hi
    I am working on International Payroll.
    When an employee is hired in the mid-month, the Employee and Employer pension contribution is not getting calculated and not getting deducted in the payroll.
    Kindly resolve this issue.
    Thanks
    vish

    Hi sunny,
    The system is not throwing any error.
    The system is not calculating and deducting the pension contribution for employees in the payroll who are hired in mid-month.
    For Eg: Employees who are hired on 10th or 15th or 20 th of  a month.
    Actually the pension contribution has to be calculated on prorata basis.
    Thanks
    Vish

  • Employees PF contribution exceeds employees salary

    Dear All,
    In April month test payroll run i am getting this message"Employees PF contribution exceeds employees salary for some of the employee";Can anybody tell what is the reason behind this.There basic pay also showing negative in the log.
    We have just applied SAP Note 1568264
    regards
    Surajit Chanda

    Hello
    Under the normal scenario,Employee PF contribution should be 12% of his eligible pay or PF basis , based on the manner in which IT0587 is mainatined
    Can you check what is the value under /111 EPF Basis ?
    In the case of mid month joining/leaving or transfer scenarios, the PF Basis will be correspondingly prorated and so the contribution calculated will also be prorated  .
    Thanks and Kind Regards
    Ramana

  • Employees Pension Contribution -EPF

    Hi,
    For one of the employee we have maintained Info Type 587 with the below conditions
    Employees PF Contribution -   PF Basis
    Employer's PF Contribution -  PF Basis
    Employer's Pension Contribution - Eligible Pay or  PF Basis whichever is less
    The Employee has joined newly in the current month, but when we run the Payroll, the following Deductions are happening in RT.
    /111     EPF Basis     6,780.80
    /3F1     Ee PF contribution     814-  This is correct
    /3F3     Er PF contribution     381-(supposed to be 3.67% of PF basis)
    /3F4     Er Pension contribution     433-(supposed to be 8.33% of PF basis)
    I could not understand on what basis /3F3 & /3F4 amount is getting calculated. Experts  please  provide your input.

    The proration as mentioned by you happens only when the employee joined/left in the middle of the month. However, in case of LOP, PF is calculated on the earned basic (reduced) and eligible pay, whichever is less. Please check with your legal counsel for getting legal opinion on the matter.
    However, if you still need to prorate the eligible pay based on LOP days, then write a rule which will check the value of /111 and limit it to eligible pay (prorated in case of LOP) before function INEPF is called in the schema. This way the value passed on to INEPF in WT /111 will be the prorated value and your requirement will be met.
    But, I would still ask you to get legal opinion on the same as it may lead to statutory default in case the standard calculation is correct. It is always better and legally safe to deduct and contribute more PF.
    From SAP India
    In the case of mid month joining/leaving/absences or transfer
    scenarios, the Pension/PF Basis will be correspondingly prorated and
    so the contribution calculated will also be prorated. In case of LWP
    the PF basis is not prorated.
    If the pension basis is eligible pay which is maintained in T511P in theconstant PFBAS and currently having the value as 6500 then, in the case
    of mid month joining 6500 gets prorated for the number of days employee was in the trust.
    If the customer doesn't want this pension basis to be prorated then a
    User Exit: Override Employer Pension Basis has been provided in payroll
    function INEPF. The name of the exit is EXIT_HINCALC0_002. This exit is
    in the enhancement HRINCEPF. We request you to go through the
    documentation of this user exit at
    Payroll India > Statutory Social Contribution > Provident Fund >
    User Exit: Override Employer Pension Basis
    Please keep in mind that above user exit is only for Pension not for
    PF..
    Edited by: Sikindar on Oct 9, 2009 2:14 PM

  • Pension Contribution not deducting correctly and Arrears

    Dear Experts!
    I am facing with a big problem with calculation Pension Contribution in India Payroll.
    First, the issue with employee join into company in middle month, i have modified EXIT_HINCALC0_002 and it's right.
    However, the problem when a employee has an arrears of last month, so my customer requires that: base on /111 + arrears to decide the amount of Pension Contribution.
    If /111 + arrears >= 6500 so assigning /3FC = 6500
    Else /3FC = /111 + arrears.
    But I don't know, how to calculate arrears in FUINEPF to choose the suitable value for /3FC.
    Please help me. Thank a lot.

    Thank for your reply.
    I have read the note and see that: this is the problem when employee joined in the middle month <not from 1st of month>. However, I have fixed this problem. And the result is OK.
    The issue now is to decide value of /3FC not only base on /111 but also amount of Arrears. I don't know how to calculate Arrears, especially in FUINEPF.

  • Can an annual subscription be upgraded mid year at a prorated rate?

    Does anybody know this?  Adobe doesn't appear to.  

    Correct you'll be prorated for the plan difference for the remainder of your existing subscription. 
    When upgrading the price plan for a yearly paid site within the paid period, you only pay the corresponding difference to the higher plan for the period between the upgrade date and the end of the paid period. The cycle does not restart. The difference is prorated for the remaining period.
    Hope this helps explain. 
    -Sidney

  • Help Needed !!!!! in New Hire Proration and Carryover (PTO Accruals)

    Dear All,
    We are facing a problem in Accrual formula where
    Accrual Term is 1-July to 30 June
    Accruing Multiplier is 'M'
    Accruing Frequency is 3 Months
    Accrual Rate is 5 Days
    Employee gets Leave at the end of each quarter
    1st Quarter (July-Aug-Sep) - 5 Days
    2nd Quarter (Oct - Nov - Dec) - 5 Days
    3rd Quarter (Jan - Feb - Mar) - 5 Days
    4Th Quarter (Apr - May - Jun) - 6 Days
    Total 5+5+5+6 = 21 Days
    This accrual Plan is working fine for employees joining before the accrual start date of 1-Jul or employees joining on the first date of the first month of any quarter.
    But for any employee joining after 1-Jul we should get the prorated leave entitlement
    We have identified and developed the logic for the number of days a new joinee would accrue if he joins in the middle of a Accrual period. I am detailing out the following logic
    The SQL for this is as follows
    SELECT (ROUND((21/365*(fffunc.days_between(:Hire_date,:Current_accrual_Period_End_Date)+1))/5,1)*5)*-1 FROM DUAL
    My query to all Fastformula Gurus is that how can i incorporate this leave proration logic for employees joining in the middle of the accrual period into my Accrual Fastformula.
    Any help is appreciated guys.
    If anyone wants to look at the code for the Accrual fastformula, you guys can Message me on the forum
    Cheers
    Sachin

    To achieve your requirement, you need to change the accrual sub formula PTO_PAYROLL_PERIOD_ACCRUAL. Follow the below steps.
    A.Create a pl/sql function :
    1. Create a new Pl/Sql Function in similar lines with parameters as p_assignment_id, p_date_earned, p_plan_id and p_number_of_years;
    2. The new function should call the pl/sql function per_utility_functions.Get_Accrual_Band passing values of p_plan_id and p_number_of_years.
    3. After the above function call, invoke your custom procedure to get the accrual value based on grade (passing p_assignment_id and p_date_earned as parameters).
    4. call the procedure per_formula_functions.set_number to set the ceiling value.
    So overall your function should like this
    FUNCTION <function name>(p_assignment_id NUMBER,p_date_earned DATE,p_plan_id NUMBER, p_number_of_years NUMBER ) RETURN NUMBER IS
    < variables declaration>
    l_ceiling number;
    BEGIN
    l_return := per_utility_functions.Get_Accrual_Band(p_plan_id,p_number_of_years);
    IF l_return = 1 THEN
    return l_return;
    ELSE
    l_return := <your custom function>(p_assignment_id,p_date_earned,l_ceiling);
    l_error := per_formula_functions.set_number('CEILING' ,l_ceiling);
    END IF;
    END <function name>;
    l_error := per_formula_functions.set_number('CEILING' ,l_ceiling);
    B. Create a Formula Function with the above pl/sql function with p_assignment_id, p_date_earned, p_plan_id as context usages and p_number_of_years as parameter.
    C. Copy the Formula PTO_PAYROLL_PERIOD_ACCRUAL and replace the entry of Get_Accrual_Band with your custom formula function defined in step B.
    D. Copy the formula PTO_PAYROLL_BALANCE_CALCULATION and replace the entry of PTO_PAYROLL_PERIOD_ACCRUAL with your custom formula defined in step C.
    Hope this helps.
    Regards,
    Sharath

  • No discount, no prorate when switched to "more everything plan" mid month?

    I have switched to the "more everything" plan in the middle of the month. When I received a bill, it turned out that
    - they backdated the change to the beginning of the billing cycle (I did not ask for it)
    - they did not give me $25 Edge discount for the first month
    I called customer service twice, and both times I was stonewalled, but with two completely different theories.
    Lady #1 (Lolita) told me that I would incur data and minute overages if I started the new plan in the middle of the month (actually, I would not). Then she said she was able to prorate my plan and gave me some discount. As for the lack of $25 edge discount for the first month, she declared that I can get it only if I give up my employee discount (21%), which is a total **. I requested to talk to a supervisor, and I was told he will call me within an hour, but he did not.
    Lady #2 (Ashley) told me that there are no traces of the change Ashley has allegedly made, and if I do plan change in the middle of a cycle (a.k.a. "on demand change"), I would have to pay for BOTH plans for this month . So they did me a favor by backdating the switch for me. She also told me that I am not getting the Edge discount for the first month, because they refunded the money I paid for my previous plan for this month and "it's a wash" (whatever that means). She was unable to explain how refunding the money for the old plan bears any influence on the presence or lack of a discount in the new plan. She also indicated that lady #1 was incorrect in telling me that first month discount is incompatible with the employee discount (of course she was). I demanded to talk to a supervisor and was told that I will get a call back in 72 hours.
    What a mess! I've been using Verizon for 14 years, and I don't recall such an abysmal customer service.
    I also tried to find a way to start a billing dispute in writing, so I get some material evidence of the ludicrous "explanations" I am being given, but I did not find any way to contact Verizon Wireless in writing - all the avenues I explored on the web site ended up with "call the customer service number". Is there a way to send them an e-mail, or a snail mail letter?

    I recently switched to the 10gb more everything plan, I have 3 lines that weren't under contract with smartphones we own and they got the $25 discount. I have 1 new line that we added with an old smartphone that we own and they get the $25 discount. Also have several other lines on the edge program and they get the $25 disocunt, along with the charge for the new phone.

  • How to prorate mid month emp termination

    hey all,
    i have some employees that are being terminated as of 15th Jan 2009 some as of 20th Jan 2009. How can one handle such situations in the basic salary calculation formulas in payroll.
    all your comments are welcomed!

    There was no proration logic.
    So i went thru the R12 Help and i came across a sample formula that has given me some idea now this formula is working only when the employees join in the mid-month and it doesn't work for mid-month termination.
    Please note the salary is not hourly its daily computation but payroll is callander month.
    We have International HRMS (i.e. XX_LEGISLATION)
    Following is the formula:
    ALias ASG_GRADE as Emp_Grade
    ALIAS BASIC_PAY_IN_USD_AMOUNT_IN_USD_ENTRY_VALUE AS BASIC_US
    ALIAS EXCHANGE_RATE_USD_PAY_VALUE_ENTRY_VALUE AS EXCHANGE_RATE1
    default for BASIC_US IS 0
    default for Emp_Grade is 'A'
    default for actual_salary is 0.0
    default for EXCHANGE_RATE1 is 0
    default for prorate_end is '01-JAN-1900' (date)
    default for prorate_start is '01-JAN-1900' (date)
    default for PAY_PROC_PERIOD_END_DATE IS '01-JAN-1950' (date)
    default for PAY_PROC_PERIOD_START_DATE IS '01-JAN-1950' (date)
    inputs are Pay_amt(number),Pay_amt_TZS(number),Pay_amt_USD(number),prorate_start (date), prorate_end (date), actual_salary (number),day_in_Month(number)
    if (Emp_Grade='S1' OR Emp_Grade='S2' OR Emp_Grade='S3' OR Emp_Grade='S4' OR Emp_Grade='SA' OR Emp_Grade='SB' OR
    Emp_Grade='SC' OR Emp_Grade='SD' OR Emp_Grade='SE' OR Emp_Grade='SS') then
    if not(BASIC_US was defaulted) then
    actual_salary =(BASIC_US)
    l_amount = (BASIC_US)
    message = 'Proration Start Date ' || TO_CHAR(prorate_start, 'DD-MON-YYYY')
    IF (prorate_start was defaulted) then
    prorate_start date is defaulted when no pro ration occurs. Therefore we
    should just return Salary.
    l_amount = l_amount
         Pay_amt=(l_amount)
         Pay_amt_USD=(l_amount)
         Pay_amt_TZS=(l_amount*EXCHANGE_RATE1)
    else
    l_days = days_between(prorate_end , prorate_start)+1
    day_in_Month=days_between(PAY_PROC_PERIOD_END_DATE,PAY_PROC_PERIOD_START_DATE)+1
    l_amount = (l_amount * l_days) / day_in_Month
         Pay_amt=(l_amount)
         Pay_amt_USD=(l_amount)
         Pay_amt_TZS=(l_amount*EXCHANGE_RATE1)
    return l_amount, message,Pay_amt,Pay_amt_TZS,Pay_amt_USD
    Appreciate all your responses/help/assistance!

  • Quota credit on 1st of calendar year for existing employees and for new joinees on prorata basis

    Dear All,
    we are having an issue in quota generation, where casual leave quota should get credited on 1st of every calendar year and for mid month joiners on prorate basis. If we select calendar year it is crediting on 31st of calendar year, but we need it to be credited on 1st  of January and also checking the prorate condition for new joiners.
    So please guide on whether it is possible through standard or any work around solution. If so how can it be achieved.
    Thanks
    Vijaya

    Hi,
    check this one prorate basis -
    http://scn.sap.com/docs/DOC-52928
    for you quota on 1st day of calender year, check the settings in the table V_T559L
    - Validity/deduction interval
    - Validity period for default values
    Best Regards.

  • My client current process shift amount is prorating.   Now my client requirement  employee change shift (SE20321D)   to normal (NSO70012) in the mid of the month employee will get shift  full amount,

    Hi Experts,
    Please help me to solve this two issues
    I will give you clearly about my client requirement
    in the current system (existing)  already configured  for shift allowance.
    shift allowance for executive
    Shift Allowance Rates
    2 shift
    3 shift
    RM  240
    RM 330
    shift allowance for non executive
    Shift Allowance Rates
    Category 1
    Category 2
    2 shift
    3 shift
    2 shift
    3 shift
    RM  180
    RM 280
    RM 95
    RM 130
    they are not maintained (there is no any key)   in info type 0014 or info type 0015  they earliest hr consultant  copied to  the Shift Allowance wage types :- 5533, 5534,5535,5536,5537,5538and 5559
    Note : 5533 & 5536 are for Payment.
    Other wage types are for calculation purposes only.
    And they modified (standard LAP9)  YAP9 (copied)  schema written pcr  for shift allowance
    The pcrs are YSH1,YSH2,YSH3,YSH4,YSH5,YSH6,YSH7,YSH8,AND YSHF
    1) So my actual my client requirement (Issue 1)
        In my client current process shift amount is prorating.   Now my client requirement  employee change shift (SE20321D)   to normal (NSO70012) in the mid of the month
    employee will get shift  full amount
    2) client requirement (Issue 2)     Shift Allowance become prorate if the Action (Info type 0000)  in the same month have changes. (Depand the action type)
    Actions are
    WA,WB,WC,WD,WE,WF,WG,WH,WI,WJ,WK,WL,WM,WN,WO,WP
    XO,X1,X2,X3,X4,X5,X6,X7,X8,X9.
    XA,XB,XC,XD,XE,XF,XG,XH,XI,XJ,XK,XL,XM,XN,XP,XQ,XR,XS,XT,XW,XX,XY,XZ.
    Y0,Y1,Y2,Y3,Y4,Y5,Y6,Y7
    YA,YB,YC,YD,YE,YF,YG,YH,YI,YJ,YK,YL,YM,YN,YP,YQ,YU,YV,YW,YX,YY,YZ
    Z9,ZY
    Example
    in same month employee changed action on 20.07.2014
    Kindly help me to solve this issues  feel very happy for your help.and if you need any information about issue please let me know i will share to you.
    Thank you
    Raamarao

    Try this, it works very well for me.
    import XMonad.Hooks.ManageHelpers (composeOne, isFullscreen, isDialog, doFullFloat, doCenterFloat)
    myManageHook = composeAll. concat $
    [ [ className =? c --> doCenterFloat| c <- floats]
    , [ resource =? r --> doIgnore | r <- ignore]
    , [ resource =? "gecko" --> doF (W.shift "net") ]
    , [ isFullscreen --> doFullFloat]
    , [ isDialog --> doCenterFloat]]
    where floats = ["sdlpal", "MPlayer", "Gimp", "qemu-system-x86_64", "Gnome-typing-monitor", "Vlc", "Dia", "DDMS", "Audacious", "Wine"]
    ignore = []
    myLayout = tall ||| Mirror tall||| Full ||| tab ||| float
    where
    tall = named "Tall" $ limitWindows 4 $ minimize $ Tall 1 (3/100) (1/2)
    tab = named "Tab" simpleTabbedBottom
    float = named "Float" simpleFloat
    main = do
    myStatusBarPipe <- spawnPipe myBar
    conkyBarProc <- spawnPipe conkyBar
    trayproc <- spawnPipe myTrayer
    xmonad $ ewmh $ withUrgencyHook NoUrgencyHook $ defaultConfig {
    terminal = "urxvt"
    , manageHook = manageDocks <+> myManageHook <+> manageHook defaultConfig
    Last edited by helloworld1 (2012-08-14 05:20:56)

  • Proration in payroll

    Hi all,
    When there is a mid-month change in work schedule rule (WPBP split), the porition before the change is only prorated.  The second part is taken as full month pay.  Hence the Basic pay becomes more than what is supposed to be.  But if it is a change in Basic pay, it prorates in both portions properly.
    Another proration issue, if there is an organizational change, recurring pay (IT14), takes only one portion of the split and skip the other portion.  Hence only a portion of the amount is coming in the pay.
    Please advise on this two cases to rectify.
    Regards

    Please refer this link ,it may help you
    Proration of IT 0014 when basic pay split in the middle of the month
    Search SDN for this there are numbers of links regarding the mentioned
    Courtesy: SAP SDN

  • How to handle mid month proration in a calendar to month payroll

    Appreciate if some 1 can help in handling the mid month proration in a calendar to month payroll.
    i.e if an employee desides to quit his job by giving a 24 hours notice say in the middle of the month, then how can one handle such cases in monthly payroll calculations?
    Plz help me......!
    regards

    1. Create a Proration Event Group grouping all the events (here date track update on assignment_status_id of per_all_assignments_f). Attach the event group to elements that you want to prorate.
    2. Write a Proration Formula (Formula Type Payroll Run Proration) sth like this.
    inputs are pay_value,
    proration_start(date),
    proration_end(date)
    l_days = days_between(prorate_end,prorate_start) + 1
    pay_value = pay_value * l_days / 31 /* instead of hardcoding 31 u can get the days_between period start and period end db items */
    return pay_value.
    3. Attach the above proration formula to the elements that you want to prorate ( element screen > proration tab)
    Hope this helps.
    Regards,
    sharath

Maybe you are looking for