Product Information
U.S Tax Reporter Year End 2022
Another Year with our U.S. Tax Reporter Year End blog. If you have questions about 2022 Year-End reporting, you can post it here. This blog will be updated with tips, best practices and, SAP Notes related to this subject.
Legal Changes for US
To review the planned Legal changes for US, start the Announcement of Legal Change application. You can find detailed information about the Announcement of legal changes on this blog.
Year End Notes
3226749 – U.S. Tax Reporter Year End 2022 Announcement
3231551 – Year End 2022 Phase I for U.S. Tax Reporter (This note can just be applied via Support Package, there isn´t any workaround)
3225735 – W-2 / 1099-R Forms, Envelopes and PR Approval letter for year 2022
3245908 – Year End 2022 Phase II for U.S. Tax Reporter3272039 – Prerequisite objects for SAP Note 3245908
3282510 – Year End 2022 Phase III for U.S. Tax Reporter
3293660 – TR: Form 940 Schedule A for 2022 not displaying the Total Credit Reduction amount
IMPORTANT: SAP Note for Phase II contains manual Pre-Implementation and SAP Note Phase III contains Post-Implementation steps.
To run Year End 2022 processes successfully and for SAP to provide support, you must have installed the minimum levels of the Sync. HRSP and CLC available in October, where applicable, as specified for your release. There is not any work around.
User Guides and Resources
1406971 – FAQ: Troubleshooting PDF Forms in US Tax Reporter
544849 – FAQ: Tax Reporter Note
In addition, detailed Tax Reporter documentation for EHP8 is available on SAP Help Portal. To get Tax Reporter documentation of an older release click in the portal on SAP ERP HCM, then change the version on the upper right corner, and search for “Tax Reporter (PY-US-TR)”.
KBAs (Knowledge Base Articles)
3081097 – KBAs (Knowledge Base Articles) for Payroll USA
2918093 – After upgrade issue with the position of text and alignment
Educational Videos
2480185 – TR: Tax Reporter – Online W-2 Enhancements videos
LIMITS 2023
3288050 – GARN: IRS Publication 1494 for tax year 2023
3265862 – BEN: Annual limits year 2023
3204104 – BEN: Limits for HSA in tax year 2023
ASUG Webcast: HCM U.S. Payroll and Tax Reporting 2022 Year End Update
ASUG Webcast for SAP HCM U.S. Payroll and Tax Reporting 2022 Year End Update was conducted on October 20, 2022.
Recording and slide deck for the ASUG webcast can be found at the event page on ASUG website
Important changes not related to Tax Reporter
Blog TaxFactory 11.0
Blog Reverse Tax Engine – Payroll USA
If you have questions about this topic, please use specific blogs to post it.
In case you have any questions/suggestion about Tax Reporter Year End you can post on the comments.
Kind regards,
Graziela
Thanks Graziela! FYI, the link for 3226749 is using the SAP-internal link, not accessible to customers. I realize that none of the new Notes/KBAs are actually available yet.
Cheers,
Matt
Hi Matt,
Yes, they are finishing it, I just posted the blog before, because they needed the official blogs link.
I Have put an observation on the blog.
The notes will be ready today, latter than tomorrow.
Cheers,
Grazi
Hello Community,
The Phase I note has just been released: 3231551 (Year End 2022 Phase I for U.S. Tax Reporter).
Thank you,
Carlos
Hello team - we recently upgraded our QA box to level B1 (608) and BSI level cyclic h TUBs 92 and noticing a change in the PA tax calculation for a bunch of associates. The associate lives in NY and works in PA, however there are no (withholding) taxes coming out for PA. In un-upgraded production box (SAP 608 A8; BSI cyclic g TUBs 89), taxes are withheld for PA and NY for the same associate. In the QA box, the BSI interface is not sending the PA tax type 001 for PA at all . This is happening for others working in PA but living outside. Anyone noticing this behavior?
Thanks
Chandra
10/20 Edit - just to put a closure to this - the issue was traced to a problem in the tax model due to a missing transport. Once the tax model was fixed, this issue resolved itself.
Hello Chandra,
I took over the case and I´m analyzing the scenario.
Please, keep the posts for BSI and taxes on the blog.
We still check this one on a Regular Basis.
Thank you,
Graziela
Hello community,
SAP note has just been released to include PR Approval letter
3225735 - W-2 / 1099-R Forms, Envelopes and PR Approval letter for year 2022
Kind regards,
Graziela
Hello All,
Has anyone had issues with W2C TemSe file for EFW2C form (HR_F_MMREF_2)?
We have applied the note 3218784 for 941 form updates - this is last update from tax reporter perspective. Our W2C file has below errror while submitting:
Description: Must be 1024 bytes for EFW2C files. This condition may also be generated if the previous record is greater than 1024 bytes or if there us a Carriage Return/Line feed within a record
When I checked and compared against the previously submitted file for differences, RCT record has space between the fields 03(total no.of records) and OT001(011 Total Org. Wages, Tips & OC.)
RCT record on error file
RCT on Successful file
Any help on this is much appreciated.
Thanks,
Jahnavi
Hi Jahnavi,
Just to confirm, you have not yet applied the Year End 2022 Phase I support package? That would be newer than the Q2 Note (and would in fact include it as part of the SP queue).
Cheers,
Matt
Hello Matt,
We haven't yet applied the support pack. We are in the process. We are on 608-99 at the moment and working towards B1.
Thanks
Jahnavi
Hi Jahnavi,
Have you applied the Q2/2022 and Q3/2022 Tax Reporter notes yet? There is a change to Oregon's EFW2 file format. Not sure if this is impacting you or not.
Also, I read Matt Fraser's question on the Phase I Year End note. There are other Tax Reporter OSS notes that will be applied with the Phase I note. Those additional notes may correct your issue, depending on if you have already applied HRSP 608-B1 (just released 10/06/2022).
Phase I note 3231551 must be applied with HRSP 608-B1 or 604-I3 or 602-L7 (I think I listed the HRSP's correctly -- we're on 608-99 currently and will be updating to 608-B1 or 608-B2).
Just my thoughts. Hope you get it figured out.
Beth Matthews
Hello Beth,
Same here we are on 608-99 and working on B1. The last successful file for W2C was in July,2022 Thanks for the suggestions. I'll update here once I have it figured out.
Thanks,
Jahnavi
Has there been any updates regarding Paid Leave for the state of Oregon?
https://paidleave.oregon.gov/Pages/default.aspx
Hello Cherylnita,
Please, use the BSI blog for Paid Family Leave topic, I´m copying and paste what I replied there:
I just talked to Product Owner and BSI is still analyzing the changes with the authorities.
Once they have all the changes in place SAP will evaluate if any note will be needed or just the update in the Regulatory Bulletin with this just the Sync tool and the Tax Model need to be updated, so there is not need for notes.
I recommend that you keep tracking of this through the legal change notification app, further information about the legal change app can be found on:
2917160 New legal change is under evaluation
Kind regards,
Graziela
Good morning,
Testing Tax Reporter in our QA client and notice PU19, W-2 for 2022, executing in test mode, if employee has selected on-line W-2 there is no PDF created, I know previous years in test mode we did see the form. Please advise if something change.
Thank you
Sandra Pelkey
Good morning
Did something Change on Tax Reporter? in our QA client executing W-2 for 2022, if employee selected online W-2, in test mode it is not being generated. previous years it was being generated in test. Please advise.
Hello Sandra,
I always set a few employees as opted out in order to test W-2. I don't remember that this ever worked before in test mode.
Thanks, Anna
Hi Sandra,
I agree with Anna. In our own testing, we've never seen Online W-2s created when PU19 is run in Test Mode, only Productive Mode.
Also, it looks like your previous question, 3 minutes earlier than this one, is a duplicate?
Cheers,
Matt
Hello Sandra,
Online W2 are not generated in test mode, this is the standard behavior.
Kind regards,
Graziela
This is how the solution is designed to avoid employees viewing / downloading the Test W-2 documents.
Kumar, that's the best explanation for why Online W-2s aren't generated in Test Mode I've seen yet. Thanks!
Hi Team,
Please let me know when SAP will release a note to store Standard Occupation Classification (SOC) for all employees who work in state of Washington?
I guess we aren't the only ones having issues with the SOC codes! We have a ticket open with SAP support about this.
Hi Matt,
Have you received any feedback on this yet?
Thanks,
Kim
Hi Kim,
See the comment thread below this one between Vamsi, Hemanth, and Chandra. (Vamsi is on my team). We currently have a support ticket open with SAP for this issue.
Cheers,
Matt
Hey Hemanth,
This seems to be an issue, we have updated the SOC data (T5U28_C) and the form (HR_F_UNEMP_WA_N) in the backend shows TSOC for position 108. We still see no SOC code populating in the file at position 108, hence raised a support ticket with SAP last Friday and SAP is currently checking this for us.
Regards,
Vamsi.
Hi Vamsi,
So the only way to store this is in Table T5U28_C which is same as "T5USO". Here we can define state and the corresponding SOC code.
SOC code will be linked to a position and not to a person number right, so in this case what kind of code change is needed for HR_F_UNEMP_WA_N to query the person then take his position, go to T5USO and pick the corresponding SOC code?
T5U28_C is not like T5USO but it is similar to T5U25 that deals with job IDs and WC code mapping. T5USO is only for storing the list of SOC codes with start and end dates and will be used while updating records in T5U28_C (SOC codes drop down list from T5USO) or while updating the SOC code mapping infotype. If your business team provides you with position and SOC code mapping list then you can mass upload data in T5U28_C or directly in the SOC code mapping infotype using a mass upload program. But if they provide you with job IDs and SOC codes then you have to put extra effort reading position IDs (referring job ID) and then SOC code and mass upload T5U28_C. Also, you have to make sure the file format HR_F_UNEMP_WA_N position 108 SOC code in the configurations should show TSOC and this field should reflect if you run the tax reporter. I see the SOC codes for couple employees showing up in our tax reporter but for few the SOC code is not populating, not sure why. (We are into concurrent employment if that matters) hence raised a support ticket with SAP.
FYI - this is what we have done - T5U28 (position) / T5USO for WA. We are already using this combination for Alaska occupational codes; we simply extended this to WA.
Hello Community,
I see some comments here about issues on printing the SOC Code on the WA file during the SUI execution.
Here's three items for you to check which should resolve the issue:
1) Make sure that note 3246223 is fully implemented on your system (including the pre-requisite notes and manual activities).
2) Maintain the SOC on view V_T5U28_C for the position of the employee (PA0001-PLANS) whose SOC should be printed on the form.
3) Ensure that the employee has a valid IT0209 for the given SUI execution.
Best Regards,
Carlos
Hi Carlos Accorsi,Accorsi,
Is the table V_T5U28_C maintained directly in PROD environment or should we move the entries by a TR from DEV->QA->PROD. The reason is the up-to-date position data will be not available in non-prod environments and makes maintaining the tables difficult in DEV/QA systems and also, we use ECP system for payroll. Please advise.
Thanks,
Sanjay
T5U28 entries are typically maintained in each boxes unless you are also transporting OM objects from DEV ->QA->Prod in your ECP.
Hi Sanjay,
We are maintaining the SOC codes directly in PRD (and in QAS and DEV). However, as there are a great many of them, we're using LSMW to do a mass upload. I'm not directly involved in this effort, so I don't have many more details for you than this.
Cheers,
Matt
Hello folks,
We have mapped our positions to the SOC codes and it is working okay for active employees. However, we are not seeing it for the Terminated employees. In our system, our terminated employees are put in the default position 99999999. I am thinking this is the reason. Are the SOC codes being pulled based on the current (time of run for the SUI report) position?
If yes, how do you deal with your terminated employees?
Thank you,
Ethel
Hello,
Does anyone notice Off-Cycle Workbench is working weird after SP installation? We've installed them all together upto I4, so I can't pinpoint where it happens, but it takes forever to open and to pull up the EE data if it opens.
We've applied Notes 3136920/3265766 afterwards. If anyone knows how to fix it, please share.
Regards,
Euna
Hello Euna,
I was able to locate note 3206964 which may address your scenario.
However, please note that this blog is reserved for US Tax Reporter for Year End 2022 topics, hence the Off-cycle Workbench is out of the scope.
Therefore, for further assistance on that, I recommend you in opening an incident on PY-XX-OC component, or posting a question on the SAP Community with the corresponding tag.
Best Regards,
Carlos
Thank you, Carlos. And sorry about posting the question here. As it was a part of our year-end process, I forgot where to address the question.
Regards,
Euna
Per SAP Note 3124528-W4 Legacy Data-Changes in IT210, the withholding format of the original record is no longer determined by the begin date of IT210 and user can elect the withholding format record by the Original/Redesigned check boxes added on IT210. This function was working fine until after we applied support packs for this year.
After applying support pack notes for 6.08(B1) we are receiving an error on the original withholding format when selecting any filing status from the dropdown menu showing both legacy and current statuses.
We think sap note 3150056 - TAX: W-4 federal 0161 and 0210 infotypes with partially or no filing status validation for original form format, may have reverted the functions rolled out with note 3124528.
Just wondering if anyone having this issue before we open a ticket with SAP ONE Support.
Thank you!
Are you referring to the issue with filing status 15 - Married, but withhold at higher Single rate? after note 3124528, only filing status 01 (single) and 02 (legacy married) are allowed in the original format 210. It is not allowing filing status 15.
Thanks
No, I'm not referring to that issue.
Last year, SAP Note 3124528 allows the ability to select the original format along with the old filing status only filing status 01 (single) and 02 (legacy married) regardless of the beginning date on IT210. This functionally is no longer working after applying support pack. We are receiving an error instead.
Hi Jennifer,
Would Note 3282477 - TAX: Married filing status (02) not allowed in the 0210 infotype for the allowance withholding original format be the fix for the problem?
Euna
Hello community,
SAP note has been released:
3245908 - Year End 2022 Phase II for U.S. Tax Reporter
Kind regards,
Graziela
Hi @Graziela- after applying phase II notes, and uploading new XML forms mentioned in the note, form is giving error saying 5 fields are not available in ALLFIELDS ( newly copied forms HR_F_W2_PR_LP_22 and HR_F_W2C_PR_LP22)
Hello, not sure if this is the right forum for this question, but does SAP have any programs or features that allow for 1099 form generating and printing? We currently use a 3rd party standalone software (Accountability). Wondering if SAP has anything that is built-in for this purpose. Thank you!
Hi Elizabeth,
If you mean Forms 1099-R, then yes, those are part of Tax Reporter and the Year End Legal Change Note. If you mean Forms 1099-MISC, NEC, etc, that are usually supplied to vendors, contractors, and so on, that question would be handled in a different topic area, as that's not part of HR/Payroll. However, the quick answer is yes, SAP absolutely handles printing 1099s, and you can find the latest legal changes to these forms in Note 3253925.
Cheers,
Matt
Hi Team,
We recently upgraded support pack from H1 TO 14 (we are in TUB level 93/CYCLIC I)
FROM SUPPORT PACK LEVEL:
TO SUPPORT PACK LEVEL:
After our upgrade we compare our payroll results (PRE-Support pack payroll results vs post support pack payroll results) we find a dollar differences in scenario given below.
An employee works in the state of Mississippi. This employee has wages from regular and supplemental in one pay period. MS taxes calculated on pre support pack was $39.00, after support pack upgrade from H1 to I4 calculate taxes was $40.00 with a $1.00 difference. Mississippi always gets rounded to the nearest dollar.
Since there are no upgrades to BSI during our support packs, what causes this rounding to go off and create $1.00 differences. Need your input.
The same happened to employees in West Virginia.
Please take a look and kindly share your thoughts on this.
Hi Team,
Please let me know if you have any suggestion for the above issue.
Hello Hermanth,
Carlos is already working on the case you have opened.
Kind regards,
Graziela
Hi Graziela Dondoni, we are not using the tax reporter functionality out of SAP, do you advise still we install these support packs or we can ignore, just trying to see if we get into un known issues without installing them. - Thank you and please let me know. - Appreciate your time.
(We are performing gross to net in SAP and outsourced to third party for the year end reporting).
Hello Kanuku,
I always suggest keeping the Support Package level updated. As this includes changes, not just for Tax Reporter, but for taxes as well. Additionally, after some time, if you don´t apply the Support Package, you will not be able to apply notes due the cut in the Support Package levels.
You don´t have the rush to apply your Support Package now but is strongly recommended keeping it updated.
Kind regards,
Graziela
thank you!, i realized after reviewing the impact of it. appreciate your time.
Hi Team,
We upgraded our system from SAPKE604H1 (Level 171) to SAPKE604I4 (Level 185).
when we run off cycle work bench through Transaction code PUOC_10. system generate payment number.
Payment number is usually the combination of personnel number + the sequence number of the payroll result (5-character) and the sequential number of the payment within the result (3-character).
Screenshot is given below for references.
PRE SUPPORT PACK
AFTER SUPPORT STACKS UPGRADE:
But after support pack upgrade, Payment number is combination of PRE DME run date - time stamp.
Screenshot of same employee off cycle workbench is given below (AFTER SUPPORT STACKS UPGRADE), where you see a different payment number and whole off cycle workbench layout is changed (Please refer to pre and post support stack screenshot). Please take a look and kindly let me know which note has changed this.
Does this help: https://launchpad.support.sap.com/#/notes/3278414
yes sir it does, Thanks a ton for your reply.
Do you know what the documentation change was? Our abap resource said the note cannot be implemented in our system.
Hemanth Krishnakumar We still see the F1 documentation referring the old way of pulling the Payment number.. However, the OFF Cycle workbench is pulling the DME information. Could you help in knowing how the note helped you to fix this issue?
We are having the exact same issue. We logged an incident with SAP but are waiting for a resolution. Did you find a solution?
Hi,
Do you have any update for this issue? Thanks.
We had the PUOC_10 being slowed down or not opening after upgrade is resolved by 3206964 shared by Carlos above.
But the Payment number part is still showing the same way with DME info. Is this a change to the functionality of how it will be showing going forward or would this be corrected and taken back to how it was displaying the EE number, Sequence number etc?
Is there any update on the Colorado Family and Medical Leave Act, is there a time frame on when the Notes should be expected ? Employers are supposed to start deducting from the first check in 2023
Thanks
Ejaz
Hello Ejaz,
The changes were delivered by BSI in Regulatory Bulletin 96.
SAP is finishing the notes that creates the new tax types.
Once they are released, I will post here.
Kind regards,
Graziela
Thanks Graziela. Does the regulatory bulletin/SAP note include both Colorado PFML and Oregon PFML?
Thanks
Chandra
Hi Chandra,
Yes, both CO and OR. 🙂
kind regards,
Graziela
Hi Graziela,
Do you know which Bulletin release number is this under ?
Thanks
Ejaz
Hi Ejaz,
TUB 96.
Regards,
Graziela
Thanks Graziela. Would you be able to tell when the 96 and the notes are getting released? just a ball park? this week or next? we are getting ready to apply up to 95; was wondering if we can wait to include the 96.
Thanks
Chandra
Hi Chandra,
From what I heard is this week, but this is not official. 🙂
I´m trying to get more info and once I have any news I will share.
Regards,
Graziela
Tub 96 is now available.
Thank you, Aman,
So I believe the SAP notes will be released tomorrow.
Kind regards,
Graziela
Note 3273042 - BSI: introduction of Tax Types 117, 118, 119, 120, 121 and 122 released.
Just curious if anyone has implemented these changes for CO and OR and it's working as expected? Also does anyone know if there are restrictions from withholding this as a retro if we don't get the changes applied by the time we run our first payroll?
I know we had restrictions with WA, but haven't seen any of those same restrictions mentioned for CO or OR.
Thanks!
Hello community,
SAP has just released note:
3273042 - BSI: introduction of Tax Types 117, 118, 119, 120, 121 and 122
This note includes the changes for CO and OR.
Kind regards,
Graziela
Hi Graziela,
I'm on Step 5 of the Manual Instructions and am running into an error. I put the values in from the PDF but I keep getting the error of "Target Key must be different from source key." I've confirmed the entries I am entering do not exist in the table already. Any suggestions on how to get past this error?
Kyle
Hello Kyle,
This error is usually raised when you are copying an existing an entry, and then trying to save it without changing it.
Here's the explanation the system brings to this error: "You have attempted to save a copied entry without changing the key".
In order to avoid it, I suggest you in creating each entry on view V_T51P1 using the "New Entries" button, ensuring that you are using the same data the note instructs, and that you haven't saved this entry on the table so far.
Thank you,
Carlos
That is not my problem as I have tried copying and creating new records.
Kyle
Hello, Graziela.
I am implementing note 3273042. When trying to Copy the existing wage types to the new wage types, Step 4, I am getting a Yellow warning message, "Copying to the reserved SAP name range /3B7 is not allowed". I cannot proceed any further.
I appreciate your assistance.
Nancy
Nancy Nichols that warning message is OK. Typically, these are provided via support pack; this being a manual implementation, you will get this warning message in all the steps (because you are creating standard wage types or standard mapping). You can click OK and continue with the manual steps.
Thank you! Figured that out.
Hello,
I have configured the new CO taxes per the SAP Note. I have also applied a Tax Combo, listed symbolic accounts and checked everywhere I can think of. I cannot get the new taxes to process. I can process a Colorado check but only the W/H tax is being taken. I am not getting any hard stops.
Any suggestions? I'm stumped.
Thanks!
Hi,
These taxes are effective from 01/01/2023, hope you are running first payroll period for 2023 correct?
Yes, that is correct. I even went as far as to run PP02 for 2023.
In BSI log which comes inside "USTAX" function under payroll schema. Can you please check if tax type 117/118 is in there?
Hello, Hemanth.
I confirmed the TT 117 and 118 are on the BSI log in the pay roll schema. Do you see anything that looks incorrect?
BSI Payroll Schema
Hi
iam talking about tax data, please refer to the screenshot below. Please make sure P/WT is not zero and total hours worked is not zero.
TAX DATA UNDER USTAX FUNCTION
looks like taxes are getting calculated. Please refer to the screenshot. taxes are caculated for that period
Hi Nicola,
In pay period 1 2023 i can see PW: $6619.57 and calculated tax is $29.79 which is correct.
in pay period 02 2023, i see PW: $6619.57 and YW: $6619.57 are sent to BSI by SAP but you say no taxes are getting calculated.
Can you please show me the screenshot of tax results/cumulated tax results which comes at last under UTAX functionality
Nancy Nichols looking at the screenshot, I'm intrigued. Are you saying the wage types /4B7 and /4B8 are not showing up on the pay statement or its not even getting calculated? asking because, in the screenshot you posted, I see the "YT" getting passed with a dollar (line ADD TE for 117 and 118) which indicates the tax is being calculated (YT Year-to-date tax) - $29.79 is the tax appears to have been deducted in the previous pay period which is 0.45% of the $6619.57 of YW (ytd wages). If the taxes were not calculated the YT section would pass as zero.
If it is not showing up on the remuneration statement, the remuneration statement would have to be configured. Could you post a screenshot of the whole processing section or just tax result segment. Alternatively, check the RT table to see if the wage type shows up.
Hello, Chandra and Hemanth.
Thank you, both, for your assistance with this. The wage types are showing up on the RT table so I believe the step I missed was to update the HR Pay form. I will update that and hopefully that resolves the issue.
Thanks again!
Nancy
How do we have to map T5UTM/T5UTY entries for PFML Tax Types 117, 118, 119,120, 121, 122
Implemented the BSI TUB 96, implemented all steps of NOTE 3273042, still PFML tax types are not getting generated. Do we need to enable something else for it to work?
MANISH MRIGANK Yes, you do have to set up the tax model for tax types that are applicable to you. Without the tax model set up, taxes wont get calculated. Thats what determines what taxes you want the system to calculate.
Thanks Chandra Veeramony - I meant to ask little more detail about will it be based on "Work state" or Residence state? Is it working for you after set up ?
These taxes are work/unemployment state based. And, yes, it is working.
Hi Chandra,
For Colorado and Oregon state we have 3 FMLA plan correct. first one is state level (Tax type 117/118), second one is tax equivalent (Tax type 119/120) and the third one is Tax Local government plan (Tax type 121/122). Our company is private sector so if i configure tax type 117/118 for my Colorado and Oregon tax modal then i should be good, correct? or do i need to configure Tax equivalent/Tax local government as well? Need your input.
Yes, that's correct, If the other tax types are not applicable, you shouldn't set them in the tax model. 117/118 would be the most common for many organizations.
Thanks
Chandra
Am I missing the note with the updates for Benefit Limits for the new year (i.e. 401k, HSA, FSA, etc.)?
Can you check this SAP Note:
The HSA limits for 2023 are in OSS note 3204104. If you've recently taken HRSPs, it may have already been implemented for you.
Beth Matthews
Is there a KBA on how to map local tax wages and tax on the W2? We have a requirement to add Sheridan Colorado to box 18/19 to the W2. We have lots of locals in other states and do not recall having to map those. Is this maintained by SAP?
Thanks,
Katherine
Hi Katherine,
I noticed you opened a case, a colleagues is already assigned to it.
Kind regards,
Graziela
Graziela,
We do have an open ticket but is there anything you can do to speed up a resolution? I was provided some guidance but unsure what tax form group to be used to add the local CO tax.
Thanks,
Katherine
Hi Chandra,
For Colorado and Oregon state we have 3 FMLA plan correct. first one is state level (Tax type 117/118), second one is tax equivalent (Tax type 119/120) and the third one is Tax Local government plan (Tax type 121/122). Our company is private sector so if i configure tax type 117/118 for my Colorado and Oregon tax modal then i should be good, correct? or do i need to configure Tax equivalent/Tax local government as well? Need your input.
Yes, that's correct, If the other tax types are not applicable, you shouldn't set them in the tax model. 117/118 would be the most common for many organizations.
Thanks
Chandra
I agree, 117/118 would be the most common. My understanding is, if the company decide to self-administer the PFML plan, they will use 119/120. If the employer is local Government, they will use 121/122. Bottom line, only one pair should be used.
Hi Chandra and Mohammed,
Thanks a ton for your quick response, then i will go with 117/118 tax type.
I have set up tax model for tax type 117/118. But these tax are still not getting generated. Am I missing any step to activate it?. I have installed BSI TUB 96 and sap note(all manual steps).
Hi Team,
We applied TUB 97 today and when we start running payroll for Colorado employees (test FMLA with TUB 97 for an employee with zero total gross), we are getting an error message under UTPRI function.
Screenshot of error message is given below. Again this happens for employees with Zero total gross, if total gross is greater than zero then system works like charm.
UTPRI
SAP note 2671295 - Payroll error missing entry in V_T5US0 should do the trick correct? can someone please confirm?
All tax deduction wage types (/4xx) must be set up in T5US0 for tax priority. That's what the error message and the note 2671295 is indicating. SAP generally does not include this step in their manual instructions of wage type creation and it doesnt copy over when you copy to create new. This is something you would have to do in all manual creation of tax wage types.
Hi Graziela,
Last year, there is a new legal change for TT 106 => /4A6 for Oregon TX EE Payroll Expense Tax Effective 01/01/2022.
Do you know which W2 Box in SAP does the tax name and value will be shown?
Thanks
Ta
Hello Ta,
I believe that you are referring to Tax Type 106 for Eugene (OR30), am I correct?
If so, you can refer to note 3085142 (Year End 2021 Phase I for U.S. Tax Reporter) for details on how this is handled on the W-2.
Best Regards,
Carlos
Hi Graziela,
We have applied the Tubs until 96 in the Production mode.
Upon checking, we are seeing the effective dates in the table V_T77PAYUS_SYNTX and V_T77PAYUS_SYNXC were created from the sync run which appears as per the SAP Note# 3243239 - BSI: Sync Tool Data Synchronization tables overwrites date information.
Table T77PAYUS_SYNTX with Dates
Table T77PAYUS_SYNXC with Dates
However, we are seeing the payroll run with messages listed below during the validation from the SAP Note. Do you know how we can stop the messages in payroll run?
Our business team are seeing these messages as some errors in the payroll, and are concerned that it would affect the payroll and tax calculations. Please advise.
Payroll log msgs:
Regards,
Shiva.
Hello Shiva,
I took over your case, as suggested there:
2193769 BSI: Regulatory Bulletin level validation in Payroll
By implementing this BAdI, you are able to adjust the messages that are displayed in the US Payroll Driver according to your needs. For example, you can implement this BAdI to hide all the messages, if you do not want to display them.
Kind regards,
Graziela
Hi,
What is the Federal expiration date for exemptions? According to V_T5UTZ it is set as 2/17. However, after researching, I see it is 2/15. Will this be updated in one of BSI updates?
IRS exemption date
Kristen Burd are you sure this was changed in the BSI TUBs? I dont see this in our system. Its still 2/15 (we just applied 96). I didnt see anything come through T5UTZ in the TUBs. Could you compare in other systems to check if this was changed by BSI updates?
We have 2/17 with TUB96 applied.
Sorry.. your comment was deleted as I removed my duplicated comments.
To answer your comment. I checked the other system (up to 90), it is 2/17.
Euna
Thanks for checking and providing the update. Looks like the 2/17 is something maintained manually in your system (probably in the year 2020 when 2/15 was a Saturday). You could update it back to 2/15.
I have T5UTZ contents dated 12/20/2019 and it already has 2/17 for FED. But, no earlier file to compare.
I didn't even think of it to check the date. Thank you. Euna
Thank you for verifying.
Hi Graziela, we have similar problem, I understand you said we can hide through BAdI, so my question, is this just message or this has any other side effects on the calculations. Also We upgrade up to B3 in Development and in Quality where this message does not show up, Our Prod is at EAHR 110 so we are seeing this message in production, Does this go away once we upgrade to B3 in Production too? - Please advise once you have a minute, Thank you!
Thanks, the issue is now resolved.
Hi Team,
Iam having issue when i run Time splitter program, as it does not run time evaluation for all employees.
When i run the same (time evaluation) through T-CODE PT60, time evaluation runs fine without any issues. Please let me know if there is a note to fix these issues. This issue started happening after upgrading our system with support stacks from SAPKE604H1 Level 171 to SAPKE604I4 Level 184.
Necessary Screenshot is attached below for references. Total number of JOBS is 40.
Time splitter program
Variant: $JBSZUST - ALL Screenshot.
Now upon executing the splitter program in foreground/background, Screenshot of complete JOB LOG is given below for references.
Though from screenshot above, Total number of jobs is 40, but i see only 1 job in there. Please refer to the screenshot below.
Time Eval runs with no PERNR being selected. Screenshot is given below for references.
Please take a look and let me know why we have this issue.
Applying SAP Note 3270208 - RPCSC000 and RPCS0000 do not select all PERNR will resolve this issue correct?
3270208 - RPCSC000 and RPCS0000 do not select all PERNR, will this note resolve the above issue?
Yes it will Hemanth
Thanks
Ejaz
Thanks EJ
Hello All,
Does anyone know when the 2023 Federal Withholding rates will be available? I've applied through Tub 096 and reviewed Tub 097 and they were not included.
Also, will the Phase III note be available this week?
thanks,
Juli
Hello Juli,
I have seen some changes in TUB 098, BSI will also release TUB 099 before the end of the Year.
Phase III is planned to be released this week, once it is available I will post here.
Kind regards,
Graziela
FYI, the 2023 Federal tax tables were released today as part of TUB 98. Happy holidays all! Jeff
Thank you,
Happy Holidays!
Jeff,
I only see changes for Non-Resident Alien Additional Withholding and Foreign Earned Income Exclusion Limit. Do we know if these are the only changes for Federal Withholding, or is there perhaps still more to come?
Cheers,
Matt
Hello Juli,
SAP Note 3282510 (Year End 2022 Phase III for U.S. Tax Reporter) has just been released.
Happy Holidays!
Carlos
Hello SAP team - do you have any information on when TUBs 99 will be released?
Chandra,
A week ago Graziela said it should be out before the end of the year, i.e. by the end of this week. I am curious to know if there are further Federal Withholding updates, as the ones in TUB 98 don't seem to me to cover the whole thing.
Cheers,
Matt
Hi Chandra/Matt,
Yesterday I received the BSI email with the API notification for Regulatory Bulletin 99.
I saw changes in FED Tax type 001. Minnesota, Michigan, Utah and Hawai.
Hope this helps.
Graziela
Bulletin 99 was just released moments ago. Unfortunately, I don't see anything in it for FED. Could there really be no changes to the Federal Withholding wage brackets? I guess I need to go to the source at IRS and find out.
TUB 98 had the federal rate changes 🙂
Hi Matt,
The federal wage brackets were updated with bulletin 98. If you look closely at the description for the bulletin you will see this noted. We have applied them and they seem to be working as expected.
Happy Holidays!
Brooke
Oh, my bad. It's a single line in the description with no detail. I read it as saying that the only changes were for Non-Resident Alien withholding and Foreign Earned Income Exclusion limits.
No worries, I almost missed it myself!
I am having an issue with our REG Rate Calculation once we applied the required YE support packs. One of our developers has reviewed functions RGRTE and determined that the change and the move from USDN to USD has changed the rounding which is we had prior to 4 decimals in USDN to 2 decimals in USD. I am wondering if anyone else is seeing this issue as well and what you may have done to fix. This change has impacted OT costs. I've submitted an incident but no resolution yet.
Hello Community,
Have updated our system to Level B2 for SAP_HR, the requirement was to be at B1 for Year End.
The issue we are facing is when we run - PC00_M99_URME - Evaluate remittance (New) . It creates the Evaluation run numbers, but when I look at the employees they are not evaluated, even though the URME ran and created the evaluation run number, that run number is not updated in the 3PR Tables .
I wanted to open a incident with SAP , but posting it here to check if anyone else is facing similar issue's and if there is a solution for this .
Thanks
Ejaz
Hello Ejaz,
Could you check the KBA?
3280936 RPURMP00 (Create Third-Party Remittance Posting Run) is not populating order number
I also found the notes:
3241253 3PR: Order Number and WBS Element data are not filled on Third Party Evaluation
3232982 3PR: Incorrect due date validation when reading payment rules for garnishments
3209183 3PR: Incorrect due date validation
3223298 3PR: EXPENSE_BUKRS field not filled in on posting process
Could you check if you have all of them? The issues I have seem from other customers were solved applying these.
Kind regards,
Graziela
Hi Graziela,
We have all these notes in our system.
Our issue is when we run the URME , I do see the evaluation run number. But these numbers are not getting updated in the 3PR tables , so the employee is not evaluated and then we have to run it multiple times to get the 3PR tables updated.
Thanks
Ejaz
Hello Community,
The Phase III Note has just been released: 3282510 (Year End 2022 Phase III for U.S. Tax Reporter).
Merry Christmas!
Carlos
Carlos,
The Phase III notes usually includes the Philadelphia Resident/Non-Resident rate for table V_T5UX9 Philadelphia Reconciliation Report. Is there a release date for these rates?
Thanks
Hello Cherylnita,
I've contacted the developer on that and they are checking it internally.
On the meanwhile, would you please confirm if you have the legal requirement from the Authority with the updated rates?
Best Regards,
Carlos
Carlos,
I reviewed the updated rates on the City of Philadelphia website. I have pasted the link below.
Thanks
https://www.phila.gov/services/payments-assistance-taxes/business-taxes/wage-tax-employers/
Hello Cherylnita,
I have been talking with the developer on that and their instruction is for customers to update table T5UX9 with the new rates. You can find details on that on note 903349 (TR: Instructions on using table T5UX9).
As per the developer update, the rates on the note are just informative, and they are only updated on the note as well in case there's a change on the layout itself, which is not the case so far as the new form is not yet out.
Best Regards,
Carlos
We are applying BSI Tubs 97-99 and on the Synchronization step we are getting the message "It was not possible to insert entry WA 3320211231 in table T5UTX"
But when I look in V_T5UTX I see an entry already exists for WA 033 from 01/01/2011 - 12/31/9999 of a ceiling of 9,999,999.99 and a tax Rate .01
It seems that the record is not being delimited properly. However, reviewing the Tub documents I am not seeing an update in these Tubs for WA.
Please see screen shots.
Not showing updates
We have never seen an error in the Synchronization. How do we now proceed to get Tubs updated.
Error Msg
Hello Christy,
Please, review KBA:
Kind regards,
Graziela
Hello SAP team - IRS Tax Levy publication 1494 for 2023 has been released. Can you provide an idea on when SAP will release the note?
Hello
Related question- Will the changes under 1494 be applied in ECP by SAP or do we need to apply those changes based on SAP note.
Thanks
Mandar
Hello Chandra and Mandar,
The SAP Note has just been released: 3288050 (GARN: IRS Publication 1494 for tax year 2023).
You may proceed performing its manual instructions on your systems.
Best Regards,
Carlos
do we have similar thread to Canada, we are facing tax issues after applying the B4 support pack, please advise. - thank you!
Hi Kanuku,
There have been "Year End" blogs and threads for Canada in the past, but it doesn't appear to be a regular thing like it is for the US. There is an "HCM Payroll Canada" tag, but there are only a handful of blog posts ever written for it. The questions part seems to be more active, so that would be a good place to ask, I think.
Cheers,
Matt
Hello,
We are generating the 1099R's first time from SAP and I see the Temse are getting generated only for FEDERAL, is there any alternative forms available to create for States? How can we report to the states for 1099R's ?
Thank you
Goutham
Hello team, have a question on Ohio W4. Per the Ohio W4 Withholding exemption certificate IT-4 form employees can claim tax "exempt" status. However, Infotype 210 Ohio subtype doesnt allow tax exemption. Is this something each customer has to set up as maintainable or is this something we can expect SAP to deliver as standard behavior?
Thanks
Chandra
Hey Chandra,
Did you get a response on this question?
Thanks,
Mitesh
I didn't see a response but that's probably because this can be controlled via T5UTZ for the tax authority.
Thanks
Chandra
Just got TUB 101 from BSI with changes to the state of Maryland. In reviewing information directly from the state, I see that local tax rates for the following counties (Allegany, Anne Arundel, Cecil, Frederick, St. Mary’s and Washington) have also changed. These don't appear to be part of TUB 101. Any news from BSI on when these updates will take place?
Hello community,
SAP note has been released:
3293660 - TR: Form 940 Schedule A for 2022 not displaying the Total Credit Reduction amount
Kind regards,
Graziela
Graziela Dondoni : When is SAP releasing note on this attached Arizona revised withholding form ?
Hello Shiva,
The AZ form updates were delivered in TF 11.0 BSI TUB 095. Please check table BTXFORM - BSIAUTH #00040000 with effective date of 1/1/2023.
Best regards, Anna
Washington published the file format for the Paid Family and Medical Leave & WA Cares Fund. One of the fields is the WA Cares Exemption. Are you planning on setting up a field that will read this? I was guessing it would be on IT0235. If you go to this link Paid Family & Medical Leave (wa.gov).
Choose .CSV instructions to see all of the fields. I couldn't find a way to map this last one.
Thanks,
Kim
Hi Graziela Dondoni Carlos Accorsi,
Could you please confirm if SAP will deliver this OR Paid Leave and CO FAMLI quarterly reports?
Thank you,
Sanjay
Hello Sanjay,
You can check what will be delivered on link:
Announcement of Legal Changes - SAP ONE Support Launchpad
The changes for Q1 are still under evaluation.
Kind regards,
Graziela
Hi Graziela,
Thank you for the link. Just one follow-up question: I do not see any update regarding CO FAMLI Quarterly file. Is there any plan to deliver that as well?
Best regards,
Sanjay
Hello Sanjay,
Do you have the legal document from CO FMLA for the Quarterly file saying this should be included?
Thank you,
Graziela
Hi Graziela Dondoni ,
I found the below PDF document from on Colorado government website(https://famli.colorado.gov/employers/my-famli-employer).
https://drive.google.com/file/d/1-4ZwTfyqtYw0vTvAgFWZ3ARHxhZv0pRo/view
Thank you,
sanjay
Hello Sanjay,
This requirement is not for SUI report.
Kind regards,
Graziela
Hi Team,
Support stack note 3278414 has changed the layout of OFF-CYCLE work bench by adding sequential number and payment number (which is run date and Pnumber from the BT table).
Question: is there a way that we can change the layout of the off cycle work bench (Example: removing sequential number or removing reason filed) is it possible? Need your input,
OFF CYCLE LAYOUT
Hi Team,
Has anyone implemented note :3285503 - OCWB: Change in order of columns in the payroll history table.
This allows us to change the order of column in payroll history (moved the amount and currency columns more to the left in the Payment History table).
They have also added a toolbar to the history grid so that users can edit the columns displayed and save variants of their layout configurations. Example like removing the sequence number or payment number from payroll history tab.
Screenshot is attached below for references.
Hi Graziela Dondoni
Can you please answer this question.
Hello Hemanth,
I don´t work with Off-cycle workbench, as this transaction is not US Country specific.
Kind regards,
Graziela
Hi Graziela Dondoni
TUB 105 has Reinstated Washington WA CARES FUND LTC TAX - EE: TAX TYPE 113 and WA CARES FUND LTC TAX - ER: TAX TYPE 114. we have applied TUB 105 to BSI and ran payroll but unfortunate system is not calculating taxes for tax type 113/114.
Please let me know when SAP will release a corresponding note to resolve this issue.
Thanks and Regards,
Hemanthkumar
Hi Team,
in T5UTX i see the start date as 01/01/2024 instead of 07/01/2023 for washington tax type 113. is this the reason why its not working for me when i run payroll for washington employees? need your input
Hello Hemanth,
With regards to the ZH30 Off-Cycle Workbench changes you mentioned you're experiencing after the year-end 2022 support packs, we are also seeing this issue and are in the process of implementing SAP note 3285503 as well since it appears to be resolving the issue in our test environment.
To date we have been unsure of which note or update changed the ZH30 display, so your mention of note 3278414 may help, although that note at first glance appears to be an update to the documentation only, and I haven't had an opportunity to delve into the specific changes that note brought in.
We likely missed it and any other related notes because they appear to be on the FI, not HR side.
Thank you,
-Casey Als
Business Systems Analyst
County of Sacramento, CA
SAP Support Team
Hi Graziela and/or others perhaps in the know on this topic for likely Year-end 2023,
The Secure Act 2.0 changed the rules for 50+ catch-up contributions effective 01/01/2024. The income amount will be indexed each year.
We understand that with this new regulation, that deferred compensation 50+ catch-up contributions for those who made more than $145,000 in 2023 must be post-tax (Roth). Those that made less than $145,000 in 2023 can still choose their 50+ catch-up contributions to be pre or post tax.
Please don't quote me on our early understanding of this new regulation as we are still doing our own research, but if this in fact is expected to be the case, we are in hopes that SAP will have a planned, SAP-standard release update perhaps by late this year that US Country customers will be able to implement.
Does anyone have any additional information you may be able to share with us here on this terrific and super-helpful year-end focused blog of Graziela's? Our team here at Sac County CA check in on it every year-end. If not, we'll consider reaching out to both the SCN Community in general, and will perhaps open an incident with SAP to inquire further.
Thank you,
-Casey Als
Business Systems Analyst
County of Sacramento, CA
SAP Support Team