BSI TUBS for US Payroll taxes - Tips and Tricks & Best Practices
Pre-requisites: BSI system should be connected via the ODBC connection to SAP and should be linked with the network for Online downloads of TUBS. BSI should be always be updated with the latest internal levels within the same version within the6 BSI . For instance currently the release version is BSI xx l which is compatible with SAP so that it does not error out in any tax calculation which is brought in TUBs.
The TUB bulletin number which the client needs to update their taxes should always be downloaded otherwise the specific tax changes and requirements will not be met with.
Benefits to Clients: Get latest tax updates and calculations affecting the payroll so that the respective payroll taxes are correctly deducted and calculated as required for the effective dates. For W-2 processing also if any changes have come in TUBS gets downloaded in BSI and thus calculates the correct reportable wages (taxes) for the year end processing and submission to IRS.
Possible Problems in Update: Check the audit report after each TUB download process and if any inconsistencies are reported and the report does not show correct calculations, report the same to BSI support for further help. If
Tips and Tricks
To make sure that the required number of TUBS are downloaded always click the update button to check for the latest level of TUB in the BSI system. It makes sure that extra TUBS are not downloaded and no TUB sequence is missed.Check for the next TUB bulletin number when we click on download for the next TUB. Always run a payroll in SAP after TUBS and check in BSI message viewer tab that the correct version of BSI is getting picked for tax calculations. Always use the test tab to make sure for any correct calculation of taxes,the TUB is downloaded in outin out of sequence, it will disrupt the entire TUB downloads and we need to start form scratch for the TUB download in that version of BSI. Always remember to download the TUBS in a sequential manner of sequence, it will disrupt the entire TUB downloads and we need to start form scratch for the TUB download in that version of BSI. Always remember to download the TUBS in a sequential manner
In SAP HR box we do the table adjustments as explained in the earlier screenshots and we create a transport request for the tables adjustments we do to compare the HRD000 & HRD010 clients. The BASIS team follow the TUB bulletins to apply their part of table adjustments to create a list of sequential requests starting with LBDK......series. These transports will have to be applied initially on the Base client 000 and also in client which is meant to to be transported to quality(test) client HRQ, and Production client HRP etc..
Always make sure the BASIS team sends their list of transport requests to HRQ and followed by HRDK.... Transport request.
Once the transport is in HRQ , subsequent steps needs to be performed in BSI HRQ instance for TUBS download and table mapping in BSI for the corresponding SAP provided tax authority numbers. Once the testing is done successfully in HRQ the process is repeated in HRP before we execute the payroll.
Important Note: Please make sure before we do the download of TUBS in HRP instance of BSI all no one is logged to HRP and executing payroll , otherwise it can impact the TUBS and ultimately incorrect tax downloads in HRP which will result in wrong tax calculation.
BSI PASSWORD CHANGE Process:
1) We get email notifications from Basis/DBA team for the proposed dates for password resets, usually it's every quarter.
2) Finalize a date with them and the timeline.
3) Get into conference call initiated by BASIS
4) Once they do the password resets (by DBA and BASIS respectively) , then logon to the BSI-HRQ, BSI-HRP datasets and check with the new passwords.
5) If it works , logon to SAP SE38 , use program RPTBTCU0 and execute the transaction in each clients HRQ, HRP to make sure the taxes are calculated correctly without error.
6) Once done communicate to HRIS -Payroll users about the change notifications and share the password with the intended team.