Sales tax and VAT software for SAP S/4HANA

Partly, and the part matters. SAP Document and Reporting Compliance lists seven compliance tasks for the United States. Six are withholding reports: 1099-MISC, 1099-NEC, 1099-K, 1099-INT, 1099-G, and 1042-S. The seventh is Sales and Use Tax Reporting, which SAP describes as generating tax forms for each jurisdiction, and SAP notes the format and submission mode depend on the tax authority's requirements. So S/4HANA can produce the form. It does not register you with the state, it does not decide which states you owe, and its documentation covers submission rather than payment. Commenda files across all 50 states on each state's required frequency, tracks remittance per jurisdiction, and files amendments where a period needs correcting.

No. In S/4HANA a tax jurisdiction is configuration. SAP states that under the internal US procedure you manually enter the required jurisdiction codes and their corresponding tax percentages, and that jurisdiction codes are defined against master records such as company codes, plants, customers, and suppliers. Registration is the input to determination. Anything you sold into a state you never configured is taxed at zero and counted nowhere. Commenda measures the same posted documents against economic and physical thresholds in all 50 states, every EU member state, and 70+ countries, and notifies you at 80% of a registration threshold, before you cross it. A short questionnaire covers physical presence, because a warehouse or a remote employee never appears on an invoice.

It depends which tax procedure your system is on, and SAP tells you how to check. If the US is assigned TAXUSJ you are on the internal solution, where you maintain the jurisdiction codes and percentages yourself, up to four jurisdiction levels. If it is assigned TAXUSX, or 0TXUSX in S/4HANA Cloud Public Edition, you are on the external solution, where SAP passes your data to an external tax system that determines jurisdictions, calculates the tax, and returns the result, up to six levels. SAP also notes that certain tax scenarios are not currently supported by the external solution. Commenda works from the documents S/4HANA has already posted, so it does not matter which procedure you are on and you are not choosing between two engines.

A real amount, and less than the headline suggests. SAP lists 594 compliance tasks across 60 countries and regions. 197 of them submit through a web service, and 44 of the 60 countries have at least one. The UK VAT return goes to HMRC under Making Tax Digital. The remainder is 267 tasks that generate a file you submit yourself and 125 that SAP labels manual filing, where you enter the data in the authority's portal. Canada is a good example: GST and HST give you an electronic format, while the Quebec, Manitoba, British Columbia, and Saskatchewan returns are manual. Commenda files VAT, GST, and sales tax across 70+ countries from one platform, including EU VAT with OSS and IOSS.

No, because Commenda reads posted documents rather than sitting inside your pricing procedure. That is worth knowing, because tax in S/4HANA sales is calculated within pricing, and SAP's own US external template only works once the tax condition finds a record you created in advance. Enterprise S/4HANA instances accumulate years of those records and the reasons for them are usually good. Commenda does not ask you to unwind any of it. Every S/4HANA landscape is configured differently, so which documents and which company codes are in scope gets mapped during implementation instead of assumed.

Not as certificates. SAP documents that for sales transactions the jurisdiction is determined from indicators on the customer and the material record, so an exempt sale is a classification the system applies. That records the decision. It is not the signed form with a validity date that a state auditor asks for, and it does not tell you which of your B2B customers never sent one. Commenda collects them through a self-service portal that can carry your branding, validates each certificate at upload against signature, dates, ID format, and state-specific fields, stores it against the customer, applies it automatically in the states where it is valid, and chases expiries. Multi-state SST and MTC forms are accepted alongside single-state ones.

Both, and you choose which one you are looking at. Each entity gets its own registrations, thresholds, and filing calendar, because that is how the obligation works. You switch between entities on a single dashboard with consolidated visibility of registrations, exposure, and filings across all of them. Access and roles can be assigned per entity and per function, so the person handling EU VAT and the person handling US sales tax each work in their own area while leadership keeps the group view. New entities from an acquisition join the same workspace and inherit the same monitoring and filing workflow.

Through a scoped connection to your instance, and we are direct about what that means. Commenda's native connectors cover NetSuite, Xero, QuickBooks, and Sage Intacct among others, and SAP sits in the broader set of 100+ supported integrations rather than in that named list. For an S/4HANA landscape the extract covers transactions, customers, and the product catalogue, and the field mapping is agreed during implementation rather than assumed. A REST API and a mapped monthly CSV both work as well, including for a warehouse or a channel that no connector reaches. No engineering work is required on your side.