on 09-10-2013 8:15 PM
Hello All,
The Master Note for Year End 2013 is already available:
1905573 YE13: Master Note for Canadian Year End - 2013
Further information about the year end will be posted in this thread.
Kind regards.
Matheus
Hi Arjoon.
This may be a hard one, and I understand SAP may have to do a big re-design.
However, with regards to irregular earnings (I refer to retro earnings here, as bonus in one pay period will have not such big impact) SAP tax engine is not following the formula.
About 3-4 year back SAP used the optional method to option 1 formula for bonus/irregular earnings.
Since SAP moved into using Option 1 to optional earnings, we run into several issues. The latter one was with one of my clients that had a large past retro.
Even if we have a new note, SAP tax engine is still not following the Option 1 method formula. It would have been better it optional method formula would have been used.
In a few words... A recent fix was released, and that fix is not compliant. The special circumstance should not limit what is implemented in the tax engine released by SAP. If SAP is compliant, then it should follow the tax formula, that is simple to me.
So... we had an issue, and we discussed with SAP and well and CRA. As per SAP, and mathematically, the formula is correct. However, SAP doesn't follow the formula as prescribed clearly in the CRA guide, which I will not tag in this message as everyone has access to this info.
So... We have an issue. The issue is related to how tax-exempt deductions are carried through Arrears table. That is all so fine with all of us as we avoid all the problems with it. However, in situations where the bonus/irregular earnings are really high (due to really high retro earnings), the short cuts that SAP took into the formula will not work.
When a large retro increase carries into the early payroll period of a new year, there is nothing that SAP can do with standard settings, to deduct close to appropriate tax. This, nothing to do with what the clients setup in their system, neither T511k constants, nor T51P1 settings for R1, R2, R4.
The problem is the mathematical assumption that was taken when the tax engine was changed from optional method to Option 1 to Option 1 method. But Option 1 method cannot be truly performed in a mathematical formula unless SAP changes completely how the tax-exempt items such as pension and union dues exemptions are carried forward to the current pay period.
So, Option 1 requires that if we have a retro portion of taxable income, that should be considered in the formula at item number B in the below formula
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, This is Nicoleta in continuation of the other message. I could not log all my message above.
Continued below...
So A1 formula says:
A1 = [(IYTD-FYTD-F2YTD-U1YTD)-(PR X ( I -F -F2 - U1)) - F1 - HD]* + (B - F3) ** + (B1-f4)**.
We do not care in math terms where A2 formula goes to at this point.
A1 formula is not really what CRA defines.
All pension and union dues tax exempt deductions carry via arrears table into the current pay, and they are applied in the formula in F in the above formula. However, that does not follow CRA guide. The is supposed to be only current period's pension/UD exemption. IN SAP terms, that is current just because of the mechanism of carrying all retro into current. But that SAP value represents current plus all retro portion that came from arrears table.
The portion that came from the retro which represents the deduction from irregular earnings is supposed to be plugged in F3 in the formula.
That is not achievable in SAP at this time, as this would represent a large re-design, possibly re-design of how tax exempt deductions are flowing cross-taxation period.
However, SAP not being able to follow this formula, does give grief to customers that use SAP for payroll, sometimes, at the last moment, such as not having proper tax deducted from large irregual r earninngs within a pay period, early in the year, although all SAP configuration to assigure that is in place.
I would like that I finally see a proper formula implemented to bonus/irregular tax in SAP. I struggled with that for year, and, as a programmer, I would think it is not that hard to do. All we need to do is just implement a formula in the code. I do understand some flow of tax exempt dedutions may have to be put in place, but hey... today is a better day to fix what is not working. Cause taxable earnings flow is NOT working. It is buried in one document and no one knows about it. Further more, it is driven by /101 which is not taxable.
It is time for SAP Canada to really review taxable flow of earnings as well as how tax is calculated in SAP.
It is all so simple... Just formulas...
I
Hello,
This is related to RL-1, we recently mapped 'pay in lieu of notice wt' to RL-1 box O, but when RL is generated it should also have shown 'RJ' in Code(case O) box, but it is not doing so.
Please let me know, how can this issue be reloved!
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am trying to generate the MRQ XML file but am getting following error. How can we resolve this
"
Error:
Line Number: 12926
Column Number: 11
SystemId: "file:///V:/Intrainter/af_jointis/Year%20End/2013-2013/MRQ%20Schema/Rel12.xml"
PublicId: ""
Description: minLength constraint failed.
The element: '{http://www.mrq.gouv.qc.ca/T5}Nom1' has an invalid value according to its data type.
Error Code: -1072897660
Error:
Line Number: 12928
Column Number: 14
SystemId: "file:///V:/Intrainter/af_jointis/Year%20End/2013-2013/MRQ%20Schema/Rel12.xml"
PublicId: ""
Description: minLength constraint failed.
The element: '{http://www.mrq.gouv.qc.ca/T5}Ligne1' has an invalid value according to its data type.
Error Code: -1072897660
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does anyone can guide as to where to access the MRQ XML Schema ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have noticed in our system that SAP removed the wage type from Footnote Code 43 (Canadian Forces personnel and police deduction) and re-mapped the wage type to Box 14 on the T4 in 2013.
Code 43 no longer appears and will now need to be re-mapped in our system.
CRA website indicates that Canadian Forces personnel and police deduction should be reported with Code 43 and in Box 14 ---> http://www.cra-arc.gc.ca/tx/bsnss/tpcs/pyrll/rtrns/t4/slps/cmpltng/cd43-eng.html
Does anyone else notice this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Following notes are released
With Regards,
S.Karthik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
This is the first year we are filing RL-1 electronically. When the XML file was submitted to MRQ we had a return message stating that the certification number is not correct. I see on the MRQ website a note that says: "You must use a software that we have authorized. For each tax year, the designer
software should provide you with a new issue of certification attesting that the software meets our requirements."
However I don't see a certification number in the notes. Can anyone tell me where this certification number comes from and is it unique to each organization, or the same number for all SAP customers?
Thank you,
Elizabeth
Hello Vivian,
Thank you for your reply, but I'm not sure we are talking about the same number. We have a transmitter's number. But there also seems to be something called a Certification Number that is not an input parameter on the SAP Magnetic Media - MRQ XML screen. Yet when I execute the program and produce the XML file I can see that there is a Certificate number:
<NoCertification>RQ-12-01-280</NoCertification>
When we try to transmit to MRQ they tell us that the certification number is not correct. Can anyone tell me where this certification number comes from and how it gets into the XML file?
It sounds to me like it should come from SAP and should be part of the file generation.
Thanks to anyone for help,
Elizabeth
Thanks for your reply Rémi, but it is not the approval number I am looking for. That is correctly showing on our slips. It seems to have the same format as the approval number (see above), but the only place I see this Certificate No. is in the XML file download. I'm not sure where it's coming from, how to change it, or what to change it to.
Any other thoughts?
Hi Srikanta,
These notes should not have been released for customers.
Mid January, I have reported a case, as a customer (Transat AT).
We requested a correction for specific case where an employee is moving into several provinces during a year and getting back into its original province (ON for 3 month, QC for 3 months, ON for 3 months and BC for 3 months).
Employee is paying EI and CPP contribution, in ON, QC and reach the maximum elligible when he returns in ON.
Currently, T4 is not correctly filling the boxes 24 and 26. Box G on R1 is also incorrect.
SAP is working on this issue but we still have some fine tuning to do.
If you are not having such case described above, my advice is to not apply notes 1971051 and 1973004
Regards,
Anthony
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
released for customer
With Regards,
S.Karthik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I suggest you check the notes in 2 ways :
a. Search notes with Application area as " PY-CA*"
*, Because, the notes with app area PY-CA-RP / PY-CA-YE will get missed, If you use PY-CA alone.
b. Pl. search the Master note 1905573 , as Versions keep changing for any update and recent version is 12, which was released on 28th.
Thanks,
Srikant
Hi,
My customer is wondering how come he does not get the correct Basic personnel amount of 11 138 when using the Tax update utility txn PC00_M07_UNTU for Federal Tax with the Indexing Factor. (They have to use the indexing factor for all employees)
When we take last year amount 11 038 * indexing factor
11 038 * 1.009 = 11 137.342 and the Tax update utility give the amount of 11 137 (it is rounded down)
But the RCA value for 2014 is 11 138.
There is also an option to use the indexing factor plus a constant, but adding a constant of 1 for everybody would not be correct as other amounts may not need to be adjusted.
Any advice would be appreciated.
Thanks,
Nathalie Ann
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Kindly review the note 1946608, you should use Option 3 for Federal with additional amount of 1$
"
As announced by CRA, the indexation factor for Federal is 1.009,00. In order to arrive at a basic personal amount of $11,138 execute the Tax Update Utility with Option 3, with the additional amount of $1.
Kindly use as mentioned above, this will solve your problem
With regards,
S.Karthik
Our customer bi-weekly pay period dates for first pay of 2014 are 12/15/2013 - 12/29/2013. When running the tax utility update program for Federal to have new effective begin date of 12/15/2013, using Option 3 with additional amount of $1, the basic personal amount of $11,260 is proposed which is incorrect. When 01/01/2014 date is used, the correct $11,138 is proposed. We need the 2014 basic personal amount to be applied to PP01.
Solution: The constants in T511K must be changed to the begin date of the pay period to be applied correctly. When this is done, the correct basic personal amounts are proposed when RPUTXUK0 is run.
Thanks,
Susan
I will second Susan. For monthly or semi-monthly payroll periods, the SAP delivered constants for Federal and Provincial Indexing Factor has the appropriate validity period (beginning on January 1st), but it is not adequate for those of us with bi-weekly pay periods.
Every year, after importing the Year-End Note, we modify the validity period of those constants so that their begin date coincides with the earliest "First day of Pay Period 01" of the new year (out of all our Payroll Periods).
Hi,
New note was release today 1938869: QHC 2014 changes
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Irina,
If you are dealing only with Ontario employees, as we are, you would not be required to apply it, but over the years, I have learned that it is better to apply all Year-End Notes in the sequence they are released since some unmentioned changes may be included in the Note, rendering it a prerequisite to a subsequent Note that you will require.
We may apply it tomorrow, before testing is done to the Year-End Note and associated Year-End configuration, or we may wait until there is an other Note that we must apply for the Year-End.
Hi Remi,
We are trying to apply the note 1938869 and my ABAPER got an issue as follows:
She created "Z" report which is ZUITILIY7273 as per the instructions in the note, when we run the program via SE38 it says status 1000 is missing for the report.
Do you have any clue on this? We already created transport for the changes, what if I donot run this programm, can I still send the transports to Test client.
Pelase advise.
Regards
Hello Irina,
We haven't applied that Note yet since all our employees work in Ontario and are reputed to live in Ontario. Since the changes mentioned seem to include manual intervention (copying WTs cumulating in /151 onto /171), the will not be included in the Delta Note, and we will have to study the change suggested since we use WT /171 as the Pensionable Earnings Cumulator for one of our Pension Plans (or should the document say "into /172" and "into /173" instead?
I believe that Note needs to be clarified since the first part of the solution mentions to "change the validity of the wagetypes /172 and /173 (delivered in the base CLC for YE 2013)" but does not mention /173 anywhere else in the correction instructions.
Hi,
/172 and /173 are credit for the Quebec Health Tax. If you don't deal with Quebec Employee, you don't have to run the utility. The utility is to convert wage types that are included in /156 and /161. There's a list in Jean-François Doré YE update that are in /156, /161 but should not be in /172, /173.
The utility is missing status bar(icons) for the screen. What you can do if needed, just modify the wage type that should be included in /172, /173 at the beginning of your first pay 2014.
Regards
Frederick
Hi,
The combo form will be on paper size legal this year. Check your printer en envelopes if your are printing from SAP.
Regards
Frederick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Note 1946674 includes the hyperlinks to the compressed SAR files, which are the Workbench and Customizing transports for Year-End Changes.
Note 1946608 details the Legal Changes for 2014 and includes 4 PDF documents for your information.
Note 1947304 should contain the changes to the Year-End forms and programs. Attached are 3 compressed files containing the Specifications for the Forms and the Validation Schemas for Canada and Quebec. In the "Steps to apply Note" section, it mentions to apply the YE transports (Note 1946674) first.
Hi,
We have apply the following sequence:
1) 1910905 - YE13: Unnecessary cancelled forms for RL1/RL2 : Note needed for 1896147
2) 1896147 - YE13: excessive RL-1/2 numbers assigned during amendments: Note needed for 1947304
3) 1946674 - YE13: Delivery of Year End Transports for 2013. This transport as workbench to be import in client 000 and customizing to be imported in client 000 and working clients.
4) 1946608 - TAX: Legal changes effective January 1, 2014. Just need to run tax utility update
I found the answer to our problem in the US Payroll Discussion Forum. SAP Note 1848094 mentions that when "applying a .SAR file that starts with L4H* in your system and you are receiving the error message ..." it is caused because "the transports are created in a DEV system tha has SAP_HR 6.04 and EA_HR 6.04".
The solution, which I also received from SAP in response to my OSS Incident, is to check the "Ignore Invalid Component Version" box.
Our Basis team did so and the Y-E transports were applied onto our DEV.
Hello Frederick
If you don't mind could you please clarify a bit more detail regarding item#4) note 1946608 Legal changes effective Jan 1. 2014. *Just need to run tax utility update
When we attempted to download this note marketplace indicates it is not yet available for download
two questions
1. do we just wait for note release? or are there instructions for this to be done now?
2. if we need to wait for the release does that mean we cannot proceed to step #5 , to apply note 1947304?
Your advise greatly appreciated
Maria
Another concern
When we applied Note 1896147 , no transports were created, can you please advise if we need to do anything special for this note. I recall situation from last year as well but could not remember how we corrected
I have noticed that this is version 3 of the note, not sure if this is relevant
Thank you and please advise
Maria
Thank You , however, We've applied the notes from the list according to the sequence.
1910905 note applied transport created
1896147 note applied no transport created
1946674 SAR files downloaded, transports applied to SYST and CUST accordingly
1946608 Client will run tax utility before testing (not done yet)
1947304 note applied no transport created
My questions were 2.
1. We are assuming that the tax utility is fine to be run after the notes are applied? please advise
2. for 1896147 and 1947304 if no transports are created , does this mean that we don't have to transport / apply to subsequent systems? QAS, Prodn? How will the changes from these notes be applied to other systems?
Thanks so much,
Please advise
Maria
Try t-code stms_import to see the Year-End Transports, as they are not "regular" transports, and they must be imported into each environment.
On our side (HR-Payroll), we still enter them into our "Transport Log" and document their approvals and dates of applications into QAT and PRD.
P.S. I don't think that we have implemented Note 1896147 yet as it was supposed to affect only Quebec, but our Basis team implemented Note 1947304 and it generated a Workbench transport. Further analysis showed that both transports include changes to program RPCYERKN, and I've mentioned it to our Year-End Lead.
For ASUG members, be advised that the Canadian Payroll Year-End Update Webcast has been scheduled :
For more information : http://www.asug.com/events and look on Oct. 31st.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Kindly find Link below for 'SAP Year end update for all customer' from Product manager
https://share.sap.com/a:wfnm7u/MyAttachments/f4d252b2-59a3-4a09-8eea-ed7a47a264b8/
With Regards,
S.Karthik
Hello,
Year end updates are also available in the Canada WIKI Page
http://wiki.scn.sap.com/wiki/display/ERPHCM/SAP+Canada+-+Year+end+2013+Update
With Regards,
S.Karthik
Hello,
Pre delivery for year end 2013 is released today
Note 1915952 - Pre-Delivery for YE13
Kindly apply the relevant support package to get the note changes.
With Regards,
S.Karthik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, I can see it under "Year End 2012" (or "Fin d'année 2012") on service.sap.com/hrcanada
It would also be useful to know when the documents (under "Documentation") were posted.
Message was edited by: Rémi Corriveau
Vivian Ying mentioned (in an other thread) that the release calendar can be found under: https://websmp104.sap-ag.de/ocs-schedules (or enter service.sap.com/ocs-schedules in the web address box) P.S. SAP has corrected the date shown on the left menu section, but the Master Note for Year End 2013 still mentions Year End 2012.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.