Skip to Content
Product Information

TaxFactory 11.0

Hello community,

BSI TaxFactory and TaxFactory SaaS released version 11.0 is available.

After our partner BSI has extended the maintenance for their offering/Product BSI TaxFactory 10.0 up to April 30,2021. SAP has also decided to provide support for BSI TaxFactory 10.0 up to April 30, 2021.

Regardless of the extended support period for BSI TaxFactory 10, SAP strongly recommends not to postpone your upgrade to BSI TaxFactory 11 and still plan to complete the upgrade during this year.

As announced on BSI website JAVA/Tomcat 32bits is not supported anymore by BSI after TaxFactory 11.0 cyclic C and TaxFactory 10.0 cyclic X.3. For any query about this, please contact BSI Support.

Upgrade 
your payroll system to the corresponding BSI TaxFactory 11.0 product way before the decommissioning of BSI TaxFactory 10.0 support.
There are NO options to extend the support for TaxFactory 10.0 after the decommissioning date.

If you have any questions about BSI TaxFactory 11.0, you can post it here. I´m going to keep this updated with tips, best practices, and, SAP notes.

Important SAP notes:

2760305 – BSI: Tax Factory 11.0 – Main Note

As a prerequisite, you must apply the following SAP Notes:

2760918– BSI: TaxFactory 11.0 – DDIC Changes

2763228 – BSI: TaxFactory 11.0 – Function Modules Changes

2770832 – BSI: TaxFactory 11.0 – General Technical Changes

2780204 – BSI: TaxFactory 11.0 – Changes required for TaxFactory SaaS

2868617 – BSI: Tax Profile Factory SaaS correction

2780716 – BSI: TaxFactory 11.0 – BSI Tools

2790902 – BSI: TaxFactory 11.0 – Payroll Driver Changes

2844516 – BSI: TaxFactory 10.0 – Additional Configuration Options While in Transition to BSI TaxFactory 11.0

2852878 – BSI: Technical Correction changes

2854888 – BSI: TaxFactory 11.0 – Configuration Option

2860747 – BSI: Tax Factory 11.0 – system not able to run TaxFactory SaaS

2864644 – BSI: Tax data synchronization error during transition from TaxFactory 10.0 to TaxFactory 11.0

2855926 – BSI: internat error US_UPDATE_TXIT_FROM_TAXES in BSI Tax Calculation

2865938 – BSI: Tax Factory 11.0 – system continues using TaxFactory 10.0 after upgrade – SaaS

2876817 – V_BTXRATE & V_BTXOVFR: not saving Experience Rate and incorrect number of digits for Tax Type

2853869 – TAX: Additional withholding not considered and Regular wages classified as Supplemental

2878074 –  BSI: Update to BTXRATE reader class usage

2904103 –  BSI: TaxFactory 11.0 – Missing Changes in Structures for Release 600

2915653 – BSI: Unemployment Override not Being Considered on TaxFactory

Important:

Before applying SAP note 2915653, you must apply note 2844646 – Ignore the local class definition, implementation, definition deffered, definition load , definition local friends changes this notes contains a fix to SNOTE transaction and without this you will get an error.

2919499 – TAX: Experience Rates Calculated Incorrectly in Tax Result Log

2920181 – TAX: TaxFactory Version Source in USVERS

2934419 – TAX: TaxLocator not proposing Tax Areas in TaxFactory 11

2944465 – TAX: Full refund of Unemployment tax when using BTXRATE override

Further irformation about the installation can be found on:

2844034 – TaxFactory 11.0 – On-Premise Installation

2843977 – BSI: TaxFactory 11.0 – SaaS Installation

2948446 – BSI: installation instructions for TaxLocator 11.0.

2977383 – BSI: Changes in Sync Tool Tax due to incorrect State

2988140 – IT0208: Performance issue when using Tax Locator

Frequently Asked Questions – FAQ

 

1) Which are the options for transition from TaxFactory 10.0 to TaxFactory 11.0?

  • In transaction SU3, define the user parameter BSI_TF_VERSION with value 11.
  • In transaction PE03, configure the BSI Tax Factory Version (10BSI) feature with value 11.
  • In transaction SM30, open table view Customer values for configuration options (V_T5F99K2) and set the value of constant BSI TAX FACTORY: CUSTOMIZING SWITCH (BSITF) to 11.Once your company switches to TaxFactory 11.0, you may no longer use TaxFactory 10.0, nor may you switch back to it later.

2) Which is the start date to be used in table V_T5F99K2 and constant BSITF?

The start date should be 01.01.1800, once you decide to upgrade the system to TaxFactory 11.0, as the system should use the version 11.0 for all the tax calculation, even in retroactive scenarios, where TaxFactory 10.0 where used.

 

3) When there is a negative value the system is not calculating taxes after the upgrade to TaxFactory 11.0, what is the cause?

Check if the Reverse Tax Engine is turned ON in your system, table V_T5F99K2, constant ADTMD, further information can be found on the KBA 2984562 – Reverse Tax Engine TaxFactory 11.0

4) Filing status/Marital status is missing or not updated in T5UTK. What should I do?

As T5UTK has delivery class C, you can update this table manually. To find the filling status that should be update in T5UTK you can go to MYBSI Portal (https://mybsiconnect.force.com/CustomLogin) with your credentials:

· Select Product Maintenance > TaxFactory ->  11.0
· Under Maintenance select Cyclic Bulletins -> BSI TaxFactory 11.0 Cyclic Bulletin
-> Bulletin Data nformation

 

5) There is a syntax error in LPBSUD01 after implementing SAP note 2915653, what is the cause and what are the steps fix it?

This is because SAP note 2844646 is not implemented in your system, or was applied after note 2915653.

To solve this SAP note 2844646 must be applied.

Detailed steps:

1) Perform the de-implementation of SAP note 2915653
2) Apply note 2915653
3) Retrieve the version of objects LPBSUD01 -> To do it go to transaction SE38 select LPBSUD01 -> Utilitiles -> version -> version management -> select version prior the note implementation
4) Re-apply note 2915653

 

6) Is it possible to extend the validity date of TaxFactory 10.0?

There is no extension to TaxFactory 10.0. Support for BSI TaxFactory 10.0 will be decommissioned on April 30, 2021.

7) How Local Reciprocity is working in BSI Tax Factory 11.0?
Detailed information is available on the KBA 2973907 BSI TaxFactory Local Reciprocity Process (Basic Local Reciprocity and Advanced Local Reciprocity)

 

8) I don´t see the WF parameter in BSI script, why?

The parameter WF: 0,0 is not being sent in all scenarios in the BSI script, as BSI considers it as WF: 0,0 if there isn´t this parameter in the BSI script. Parameter WF: 1,0 is always being sent in case the employee has IT0210 in 2020 onwards.


9) Parameter WF is not in the correct line in BSI interface in TaxFactory 11.0?

There is a change in TaxFactory 11.0 cyclic B the parameter WF should be placed in other line in BSI script. This change has been delivered in the W-4 notes for States, after you apply the notes this parameter will be send in the line BSI expects to do the calculation for FED taxes.

The change in the parameter has been delivered in SAP notes:
2895426 – Prerequisite objects for SAP Note 2878657
2878657 – 2020 State Withholding Tax Calculation – Based on the State (or State-equivalent) Withholding Certificate (SAP_HR) – Phase I

10) After the Support Package the system is calculating higher taxes when employee has IT0161, why?

After SAP notes 2888094 TAX: Lock-in letters override for W-4 exempt and 2880846 TAX: Lock-in letters not overriding New W-4 is now considering the values of IT0161 and now the system is calculating more tax, which is expected.

Refer to KBA for further details 2984188– Tax calculation for an employee with both IT0161 and IT0210.

Regards,

Graziela

231 Comments
You must be Logged on to comment or reply to a post.
  • Hello Graziela,

    I am getting the following error after applying all the pre-req notes mentioned in main note 2760305. I believe someone else on this forum has already mentioned this error and I am not sure if the error was ever resolved. We are currently on 608-72 (ECC on-premise).

    In include “RPC_PAYUS_BSI_BLR_CLIENT_CHECK “, in line 27 of program
    “RPCALCU0 “, the following syntax errors
    have occurred:
    Type “LCL_BAS_LOC_RECIP_VERS_CHECKER” is unknown.

    Now I have only applied notes mentioned in 2760305.

    I am going to apply notes 2852878, 2864644, 2855926, 2876817, 2853869, 2878074, 2915653, 2919499, 2920181 and 2944465.

    You mentioned above that I have to apply note 2844646 before applying note 2915653 which I will do. Someone followed this step and still got an error. Then you mentioned backing out and de-implementing 2844516.

     

    So what is the correct steps to follow to correct this error. Should I de-implement 2844516 first before applying 2844646 and 2915653? Please advise.

    Thank you.

    Thomas

     

  • Hi Team,

    We just upgraded to BSI 11.0, when we run payroll in quality i get an message that “Basis local reciprocity is activated in tax factory client” & i see /TR1 wage type in RT with a value 1.00. Screenshot from SAP quality is attached below for references.

    Now we moved our transport to PROD. when i run payroll i dont see ““Basis local reciprocity is activated in tax factory client” & /TR1 wage type is not there in RT anymore. Will this cause issue with reciprocity between states “Incorrect state calculation” when we have maintained custom nexus indicator in BSI 11.0. Screenshot from PROD is attached below for references.

     

  • Hi TEam,

     

    During my BSI 11.0 testing i kept FEATURE 10BSI to 10.0 and through user profile (SU3 TCODE) i maintained  “BSI_TF_VERSION” as 10.0/11.0 and i was doing my testing and comparing taxes between both BSI 10.0/11.0…. in both instance ie in both BSI 10.0 and BSI 11.0, system bought /TR1 wage type with a value 1.00 in employee RT.

    Once when we go live with BSI 11.0 in PROD. i changed the value of FEATURE “10BSI” to 11.0.

    now when i was doing some simulation payroll in production client which is connected to BSI 11.0… system stopped creating wage type /TR1 with a value 1.00 for all employees in RT.

     

    Is this a issue? because i have maintained custom nexus indicator for states in BSI for some particular company code???? will this cause incorrect payroll tax calculation…. need your input.

      • Hi Graziela,

         

        Yes it related to my last question and thanks a ton for releasing a KBA with all information.

        My question is with BSI 11.0, I don’t see /TR1 wage type in RT, will this impact payroll taxes when we run payroll??? do we have any significance to this wage type? will my reciprocity between taxes wont work according to custom nexus data configured in BSI 11.0????

         

        Need your input.

        • Hello Hemanth,

          Wage type /TR1 is to identify the employees that were affected by the Basic Local Reciprocity.
          The Basic Local Reciprocity should not be used anymore.

          This note also contains some information that can help you:

          2685179 – BSI: Changes in TaxFactory Local Reciprocity process – FAQ

          Kind regards,

          Graziela

           

          • Hi Team

            We have successfully updated to BSI 11.0… we have employee who reside in Hamilton ohio (OH81) and work in OHA6 (mason)… this employee has unemployment in ohio…

             

            in BSI 10.0 we have taxes calculated for both hamilton and mason… After BSI 11.0 we have taxes calculated only for MAson (OHA6) and no hamilton…

             

            Can you please identify and kindly let me know where the issue is…

  • Hi Graziela,

    SAP note 2917910 (We implemented this as part of BSI 11.0) has bought new wage types “/3K0 to /3K4” and “/3KA till /3KI”, “/4K0 to /4K4” and “/4KA till /4KI”, “/6K0 to /6K4” and “/6KA till /6KI” , “/7K0 to /7K4” and “/7KA till /7KI”.

    Now when we run payroll recon report for current year with wage type application “TURK”. i get error message “You must include the corresponding /4XX wage type” and recon report stops executing. After debugging i found that /4K0 and /4K1 wage type processing class 72 (employee or employer tax wage type) is missing a value as currently its blank in our development and quality. Screenshot of /4K0 is given below.

     

    Now when i maintain processing class 72 as “2” employer wage type, report run fine without any issues.

    QUESTION:

    Is it ok to maintain /4K0 wage type value as 2 for processing class 72… Please confirm as other wage type like /4K1, /4K2…etc has processing class 72 maintained and they dont error out.

    Need your input.

    /
      • Hello Graziela,

        We have applied note 2951336 (we’re currently on 608-85) and we’re still getting this error “You must include the corresponding /4XX wage type” when we run our payroll reconciliation report.

        We’ve checked with out Basis admin and they’ve confirmed that this note is applied. We are running the report with wage type appliction C941 and CCW2.

        I appreciate your response to this question.

        Thank you.

        Thomas

         

         

         

  • Hi Graziela,

     

    After upgrading to BSI TF11 in the BSI portal end, we need to run the HRPAYUS_SYNC_TAX_DT this transaction? we just want to know how below details will get updated?

    sap%20image

     

    Can you please help me on this one.

     

    Regards,

    Suryasai K

     

     

    /
    sap%20image
    • Hello Suryasai,

      Did you switch to BSI TaxFactory 11?

      1) Which are the options for transition from TaxFactory 10.0 to TaxFactory 11.0?

      • In transaction SU3, define the user parameter BSI_TF_VERSION with value 11.
      • In transaction PE03, configure the BSI Tax Factory Version (10BSI) feature with value 11.
      • In transaction SM30, open table view Customer values for configuration options (V_T5F99K2) and set the value of constant BSI TAX FACTORY: CUSTOMIZING SWITCH (BSITF) to 11.Once your company switches to TaxFactory 11.0, you may no longer use TaxFactory 10.0, nor may you switch back to it later.

      KInd regards,
      Graziela

  • when we creating webservice for SAAS not creating logical port.no error message. log showing green and created. but in soamanager not showing the logical port 0

    HR and CUS 608 patch 79

    • Hello Ajai,

      Have you performed the IMG steps as note 2843977 assists?

      To enable the integration of the SAP SuccessFactors Employee Central Payroll U.S. solution with BSI TaxFactory 11.0 SaaS, you must perform the following migration steps under Customizing for Payroll US -> Tax -> BSI TaxFactory SaaS Integration:

        1. Re-enter your credentials for datasets in the customizing activity Store the BSI TaxFactory SaaS Credentials. You may need to delete the existing credentials first. Choose Update to confirm.
        2. Please contact SAP Hosting to apply the necessary Support Package. These files are used by SuccessFactors Employee Central Payroll services to create the logical ports for consuming web services for BSI TaxFactory SaaS and to notify BSI eFormsFactory about changes.
        3. In the customizing activity Logical Ports: BSI taxFactory SaaS and communicating with BSI eFormsFactory, under BSI TaxFactory SaaS, choose BSI TaxFactory 11. Give the user name and password for the new Web service for BSI TaxFactory 11.0 SaaS for each system – development, quality assurance, and the production system.
        4. Edit the Specify Version of BSI TaxFactory for Customizing activity and, under Value, change the entry to V11. Give the appropriate start and end dates.

      Best Regards,
      Carlos

      • Hello Carlos,

         

        Thanks for reply

        Yes, we follow that note to create web services. Log showing created succesfully. but when we see in soamanager logical port is 0. Not creating the proxy. and logical port

        Patch level is 608  Patch 79

         

        Thanks,

        Ajai

  • We are getting the same message reported in an earlier post.  ‘Error while connecting to BSI TaxFactory:  Program error in remote function call of RFC_HRUS_TF_VERSION_10.

    • Feature 10BSI is set to 11.
    • Table V_T5F99K2 is set to version 11 from 1/1/1800 – 12/31/9999.
    • I have also set parameter BSI_TF_VERSION in SU3 to 11 and that has had no impact.

    I have looked through everything else and cannot see what is causing the issue.

    Any guidance you can share would be very helpful.

    Thanks,

    Kim

    • Hello Kim,

      It seems that there is some missing point regarding the configuration of the RFC connection on your system.
      Please review this configuration as per SAP Note 2844034 – TaxFactory 11.0 – On-Premise Installation.

      Kind Regards,
      Carlos

  • Hello Graziela,

    We are testing BSI TF11 in DEV system. We have to add two Employee Groups in BSI TF11, we are able to add the entry and save it. Once we save it we are not seeing the newly added Employee Groups in MYBSI.

    We checked the IMG config and we are seeing the employee groups in the SAP table.

     

    Thanks

    Kumar

    • Hello Kumar,

      Please reach out BSI to check on your issue.
      If you are able to see the update on SAP table, it seems that the configurations per our side are all ok.

      Best Regards,
      Carlos

  • Due to some issues, we are looking into BSI SaaS and SAP on-premise solution. As part of this evaluation, we would like to hear from other sap clients, who have this unusual setup. Please contact me if you or someone you know would be willing to share your experience ( such as performance or else..)

    Thank you;

    Judit

     

  • Hi Team,

    This is regarding California Disability limit

     

    which has Increased from the maximum wage base FROM $118,371 TO $122,909.(Attached the RB009)

     

    the /741 is capped at 104,378.00.  It should be capping at 122,909 but it is stopping early.

    The /441 for the tax should also be capping at 1229.09 but it capped early at 939.40

     

    It is using an old 2015 rate.

     

     

     

     

     

    T5UTX:

     

     

    BTXRATE:

     

     

    Can you please advise on this?

     

    Thanks

    SatyaPrakki

  • Hello Graziela

    We have upgraded to the BSI V11 in the Non-Production system and awaiting to move this to Production. While testing it is noticed that California Disability limit is incorrectly captured by the system. in Non-Prod environment. Which is capping at 104,378.00 a quite a older rate belongs to 2015. However it should be capped at 122909/- and calculated at 10%

    In V_T5UTX view it is seen that tax type 41 limit is 122909/- and percentage at 10%

    In BTXRATE there is NO latest change. can you advise of any fixes to this??

     

    Thanks

    Satya

    • Hello Satya,

      Please create an entry on table BTXRATE with the wished inputs.
      Then, kindly guarantee that the below notes are applied on your environment:

      I) 2877989 – PY-US: Technical changes for future development and corrections
      II) 2878074 – BSI: Update to BTXRATE read
      III) 2919499 – TAX: Experience Rates Calculated Incorrectly in Tax Result Log
      IV) 2876817 – V_BTXRATE & V_BTXOVFR: not saving Experience Rate and incorrect number of digits for Tax Type
      V) 2944465 – TAX: Full refund of Unemployment tax when using BTXRATE override
      VI) 2915653 – BSI: Unemployment Override not Being Considered on TaxFactory 11.0

      Afterwards, please retest the scenario and check the results.
      This should solve the case.

      Best Regards,
      Carlos

          • Hi Team,

            We are too facing the same issue “California Disability limit is incorrectly captured by the system”.

            Though, we have maintained the record in BTXRATE table & BSI, we are still getting the issue for some employees.

            Could you please advise on this.

             

            Thanks,

            Anand

          • Hello Anand,

            Please check the maintenance of this data on SAP and BSI side.
            It should be exactly the same on both sides.

            If that’s ok, I might say that you are facing the issue because of the configuration of your datasets.
            Each client on your system should be configured under a different and unique dataset, and the client number and the DataSet ID must be identical.
            If this is not accomplished, you might face some issues just like this one you are reporting.

            Further information about this client/dataset configuration can be found on the following note:
            2844034 – TaxFactory 11.0 – On-Premise Installation

            Best,
            Carlos

  • Hi Graziela,

     

    We have upgraded to 11

    Our tables are not getting updated V_T77PAYUS_SYNXC and V_T77PAYUS_SYNTX when we run the tool?

     

    Can you please help us!

     

    Thanks

     

    Sunil

    • Hello Sunil,

      Could you confirm the user that is running the Sync Tool has the required authorization?

      Also, is your system SaaS? If so, make sure you have note 2865938 – BSI: Tax Factory 11.0 – system continues using TaxFactory 10.0 after upgrade – SaaS.

      Regards,
      Graziela

  • Hi Graziela,

     

    The user has full authorization to run the tool. We are not on SaaS but On Premise system SAP ECC system( EHP7 SP14  and HRSPs on F4).

    Regards,

     

    Sunil

     

     

     

  • Hi Graziela,

     

    Yes there is an error – ” It is not possible to insert entry  PA4P01200012311998123110 in the table T5UTD”

     

    Thanks

    Sunil

  • Hi Graziela,

     

    Thanks for checking and refered to KBA 2550829. We are able to identify the issue. The table entires were incorrect and we adjusted.

    Everything is working as expected.

     

    Thank you once again for helping us.

    Regards,

    Sunil

  • Hi Team

    We have successfully updated to BSI 11.0… we have employee who reside in Hamilton ohio (OH81) and work in OHA6 (mason)… this employee has unemployment in ohio…

     

    in BSI 10.0 we have taxes calculated for both hamilton and mason… After BSI 11.0 we have taxes calculated only for MAson (OHA6) and no hamilton…

     

    Can you please identify and kindly let me know where the issue is…

  • Hi Graziela Dondoni / Team,

     

    We have upgraded our BSI to V11 today in our LIVE clients and to our surprise system is stopped calculating taxes after this upgrade activity. This was never a case in any of our Non-Productive environments. At USTAX function we are seeing all values as ZERO. Can you please help on this priority?? Simultaneously raised OSS 809406/2020

    Thanks

    SatyaPrakki

  • Hi Satya,

    We had the same issue.  I had to do the following.

    1. Log into BSI client and Map all the tax types (Just executed default mapping).
    2. There will also be a few unmapped Authorities.  Complete this mapping as well.
    3. Also, if the BSI client dataset is gone with the upgrade, you will have to restore the dataset from your backup.   (I think this second step was necessitated by some mistake by the Basis person.)

    Regards

    Paddy