SAP Knowledge Base Article - Public

3741302 - Error TAX_TXJCD 100 No unique tax jurisdiction code can be determined

Symptom

  • Error message TAX_TXJCD 100 is displayed during transaction processing
  • The error occurs when SAP S/4HANA Public Cloud validates the tax jurisdiction code sent by System A (Integrated 3rd Party System) against the jurisdiction code(s) returned by the Tax Partner
  • Transaction processing is blocked, preventing order creation, invoice posting, or other tax-relevant business processes
  • The system cannot reconcile the jurisdiction code provided by System A with the jurisdiction determination results from the Tax Partner
  • Error code reference: TAX_TXJCD 100

Environment

SAP S/4HANA Cloud Public Edition 

Reproducing the Issue

Prerequisites
  • SAP S/4HANA Public Cloud system with external tax calculation enabled
  • System A (3rd Party integrated) via External Sales and Use Tax Calculation API such as API_PURCHASEREQUISITION_2  
  • Tax Partner service configured and active
  • Test business partner master data with US addresses
Steps to Reproduce
  1. Initial Configuration: System A is configured to integrate with SAP S/4HANA Public Cloud for tax jurisdiction determination
  2. Transaction Creation: System A creates a sales order, purchase order, or invoice requiring tax calculation via API
  3. API Call Execution: System A sends the tax jurisdiction code API with the following payload structure:
    • Street/House Number: 1234 Oak Avenue
    • Street2: Suite 100
    • District: [empty] (County field not maintained)
    • Country: US
    • Postal Code: 12345 Springfield
    • Region: XX
    • Jurisdiction Code: 000000003 (sent by System A)
  4. Expected Behavior: SAP S/4HANA Public Cloud validates the jurisdiction code against the Tax Partner's determination results
  5. Actual Behavior: Error TAX_TXJCD 100 is raised, and the transaction cannot proceed
Test Scenario 1: Single Jurisdiction Without District (Mismatch)

Address Data Used:

  • Street2: Suite 100
  • Street/House Number: 1234 Oak Avenue
  • District: [empty]
  • Country: US
  • Postal Code: 12345 Springfield
  • Region: XX

Jurisdiction Code Sent: 000000003 (requires County A to be present)

Expected Result: Validation passes with jurisdiction code 000000003

Actual Result:

  • Tax Partner returns jurisdiction code: 000000001 (determined without District information)
  • Error TAX_TXJCD 100 is raised because 000000003 is not in the returned result list
Test Scenario 2: Multiple Jurisdictions With District (Success)

Address Data Used:

  • Street2: Suite 100
  • Street/House Number: 1234 Oak Avenue
  • District: County A
  • Country: US
  • Postal Code: 12345 Springfield
  • Region: XX

Jurisdiction Code Sent: 000000003

Expected Result: Validation passes with jurisdiction code 000000003

Actual Result:

  • Tax Partner returns jurisdiction codes: 000000002, 000000003
  • Validation succeeds because 000000003 exists in the returned jurisdiction list
Test Scenario 3: Multiple Jurisdictions Without District (Success)

Address Data Used:

  • Street2: Apt 5
  • Street/House Number: 5678 Maple Street
  • District: [empty]
  • Country: US
  • Postal Code: 98765 Riverside
  • Region: YY

Jurisdiction Code Sent: 000000004 (does not require District for determination)

Expected Result: Validation passes with jurisdiction code 000000004

Actual Result:

  • Tax Partner returns jurisdiction codes: 000000004, 000000005
  • Validation succeeds because 000000004 exists in the returned jurisdiction list

Cause

  • There is a missmatch between the Tax Jurisidiction sent to the tax partner and received from the tax partner.
  • The jurisdiction code provided by System A requires the District (County) field to be present for accurate determination
  • System A does not provide the District field in the API call
  • The Tax Partner processes the incomplete address and returns a different jurisdiction code based on available fields (Country, Region, Postal Code, City)
  • SAP S/4HANA Public Cloud validation fails because the sent jurisdiction code does not match any of the returned jurisdiction codes
Integration Flow
  1. System A Behavior: System A sends address data to SAP S/4HANA Public Cloud via API
  2. Data Transmission Details: The District (County) field is omitted from the API payload; only Country, Region, Postal Code, City, Street, and Jurisdiction Code are transmitted
  3. SAP S/4HANA Validation Process: SAP S/4HANA Public Cloud receives the jurisdiction code from System A and validates it against the Tax Partner's determination results
  4. Tax Partner Determination Logic: The Tax Partner determines jurisdiction codes based on the address information provided (without District field)
Validation Logic
  • Jurisdiction Code Validation: SAP S/4HANA Public Cloud compares the sent jurisdiction code against the returned jurisdiction code(s) from the Tax Partner
  • Comparison: If the sent jurisdiction code is not found in the list of returned jurisdiction codes, the system raises error TAX_TXJCD 100
  • Mismatch Detection Criteria: The validation fails when the jurisdiction code provided by System A requires the District field for precise determination, but the Tax Partner returns a different jurisdiction code based on the incomplete address
Why the Error Occurs
  • Specific Condition Causing Mismatch: The jurisdiction code 000000003 requires County A to be present for accurate determination
  • Missing Field Impact on Jurisdiction Determination: Without the District (County) field, the Tax Partner cannot determine the correct jurisdiction code and returns a different code (e.g., 000000001)
  • Tax Partner Response Behavior: The Tax Partner processes the incomplete address and returns jurisdiction codes based on available fields, which may differ from the jurisdiction code sent by System A
Why Some Cases Succeed
  • Conditions for Successful Validation: When the jurisdiction code does not require the District field for determination, the validation succeeds
  • Jurisdiction Codes That Do Not Require Complete Address Data: Jurisdiction codes like 000000004 can be determined based on Country, Region, Postal Code, and City alone
  • Comparison with Failing Scenarios: In successful scenarios, the returned jurisdiction list includes the code sent by System A, so the validation passes

 

Resolution

  1. Ensure that System A includes all required address fields, especially the District (County) field, in the API call to SAP S/4HANA Public Cloud
  2. Update System A's integration logic to transmit the District field in the API payload
  3. Verify that all address fields (Country, Region, Postal Code, City, District) are populated before making the API call
Required Address Fields
FieldRequiredDescriptionExample
Street/House NumberYesPrimary street address1234 Oak Avenue
Street2OptionalSuite, apartment, or additional address informationSuite 100
DistrictYesCounty information is critical for accurate jurisdiction determination in certain jurisdictionsCounty A
CountryYesMust be "US" for US tax calculationUS
Postal CodeYesFull postal code (e.g., 12345 or 12345-6789)12345 Springfield
RegionYesState code (e.g., XX, YY)XX

For Example when utilizing API_PURCHASEREQUISITION_2  include the above details in the "Delivery Address" API payload 

See Also

2528016 – External US Sales and Use Tax Calculation

2440096 – Internal US Tax Calculation Restrictions

External Sales and Use Tax Calculation

Keywords

US External Taxes, TAX_TXJCD100, Tax Jurisdiction Code, External Tax Calculation, Tax Partner, SOVOS, Vertex, Avalara, District Field, County Field, Address Validation, Jurisdiction Determination, API Integration, SAP_COM_0177, External Sales and Use Tax Calculation, Error TAX_TXJCD 100, Jurisdiction Code Mismatch , KBA , XX-PART-TIF , Tax Interface (USA) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions