Intercompany transactions may look straightforward from a business perspective, but in SAP S/4HANA they can involve multiple indirect tax touchpoints.
When one group company sells goods or services to another, SAP must determine the appropriate tax treatment based on the transaction details, master data, locations, tax registrations and configured tax rules. That tax information then flows through invoicing, reporting, tax recovery and intercompany reconciliation.
This article explains the process step by step and highlights why accurate master data is critical to getting indirect tax right in SAP S/4HANA.
What is an Intercompany Transaction?
Imagine a group has two companies:
Company A – India → sells goods → Company B – Germany
Even though both companies belong to the same corporate group, they are separate legal entities.
Therefore, from an accounting and tax perspective, this is treated as a business transaction between two companies.
SAP S/4HANA records:
Company A = Seller
Company B = Buyer
An invoice is created between them, and indirect tax may apply depending on the countries, transaction type and tax rules.
2. Business Flow — What happens first?
The top portion of the diagram shows the physical/business movement.
Step 1 — Sales Order / Intercompany Agreement
Company A receives an order or has an agreement with Company B.
For example:
Company A (India)
↓
sells 1,000 units
↓
Company B (Germany)
In SAP, this could involve sales-order and intercompany processes depending on the business scenario.
Step 2 — Goods or Services Move
The goods are physically shipped from Company A to Company B.
For example:
India → Germany
SAP needs to know:
- Who is selling?
- Who is buying?
- What is being sold?
- Where is it being shipped?
- Where is the goods physically located?
- Which plant is supplying it?
- Which tax registration is involved?
This information becomes very important for indirect tax.
3. Where Does Indirect Tax Come In?
This is the most important part of the diagram.
There are six major touchpoints:
Tax Determination
This is where SAP asks:
“What tax should I apply to this transaction?”
SAP looks at the relevant transaction information and master data.
For example:
- Seller
- Buyer
- Country
- Plant
- Ship-to location
- Place of Supply
- Material
- HSN/SAC or equivalent classification
- Tax classification
- Tax code
- Tax registration
- Transaction type
Based on these inputs, SAP determines the appropriate GST/VAT treatment.
Simple example
If:
India → Germany
SAP needs to determine whether the transaction is:
- domestic,
- export,
- intra-EU,
- cross-border,
- taxable,
- exempt,
- zero-rated, etc.
The exact treatment depends on the applicable tax jurisdiction and facts.
This is why master data is so important.
4. ② Intercompany Invoice Creation
Once SAP knows the tax treatment, it creates the invoice.
The invoice contains things such as:
Goods value
- Applicable tax
= Invoice value
The seller records revenue.
The buyer records the corresponding purchase/cost.
So essentially:
Company A
“I sold these goods to Company B.”
Company B
“I bought these goods from Company A.”
5. ③ Tax Reporting
Now the seller has to report the transaction to the relevant tax authority.
For example, Company A may need to report:
- Sales value
- Taxable value
- VAT/GST
- Export transaction
- Tax registration
- Other required tax information
The important point is:
The tax transaction doesn’t stop when the invoice is created.
It also needs to reach the appropriate tax reporting process.
6. ④ Input Tax Credit — Buyer Side
The buyer may be entitled to recover the tax paid, depending on the local tax rules.
For example:
Company A → charges eligible tax → Company B
Company B may potentially use that tax as Input Tax Credit (ITC) or VAT recovery.
But this is not automatic.
The buyer must satisfy the applicable country’s rules.
So SAP needs to correctly capture the tax information so that the buyer’s tax reporting and credit process can work correctly.
7. ⑤ Intercompany Reconciliation
This is essentially the “Do both sides agree?” check.
Company A says:
“I billed Company B €100,000.”
Company B should generally have a corresponding transaction:
“I received an invoice from Company A for €100,000.”
SAP/accounting teams reconcile:
- Invoice number
- Amount
- Currency
- Tax amount
- Customer/vendor
- Accounting document
- Tax codes
- Posting dates
- Intercompany balances
The objective is:
Seller’s books = Buyer’s books
8. ⑥ Cross-Border Compliance
If Company A and Company B are in different countries, additional requirements may apply.
For example:
India → Germany
The transaction could involve considerations such as:
- Export/import rules
- VAT/GST
- Customs
- Tax registrations
- Place of Supply
- Documentation
- Local reporting requirements
Therefore, cross-border transactions usually require more master data and tax checks than a simple domestic transaction.
9. Now Look at the Right Side — Master Data
This is probably the most important part of the diagram from an SAP perspective.
Think of master data as the information SAP uses to make the tax decision.
If the information is wrong, the tax determination can also be wrong.
Company Code
Tells SAP:
“Which legal company is doing this transaction?”
Example:
Company Code 1000 = India Company
Company Code 2000 = Germany Company
Customer / Vendor
SAP needs to know who the other company is.
For example:
Company A’s system
→ Company B is maintained as a customer.
Company B’s system
→ Company A is maintained as a vendor.
Depending on the S/4HANA business model and process, Business Partner master data is central to this setup.
Material / Service Master
SAP needs to know:
“What are we selling?”
For example:
- Laptop
- Machine
- Spare part
- Consulting service
Tax classification and product/service classification can influence tax determination.
Tax Code
The tax code helps SAP identify the applicable tax treatment configured for the transaction.
Think of it simply as:
“Which tax rule should SAP use?”
Tax Classification
This helps SAP understand whether the material/customer/business transaction is:
- taxable,
- exempt,
- zero-rated,
- or subject to another treatment,
depending on the jurisdiction and configuration.
Place of Supply / Location
This is extremely important for indirect tax.
SAP needs to understand:
“Where is the supply considered to take place for tax purposes?”
It may depend on:
- Seller location
- Buyer location
- Ship-to location
- Plant
- Movement of goods
- Service location
- Applicable tax rules
Plant / Location
The plant tells SAP:
“Where are the goods coming from or being processed?”
For example:
Plant 1000 – India
or
Plant 2000 – Germany
The plant’s country and associated tax information can be important inputs into tax determination.
Tax Registration
SAP may need to know the relevant:
- GST registration
- VAT registration
- Tax number
- Country-specific registration
This becomes particularly important when one legal entity has multiple tax registrations.
Shipping / Delivery Data
SAP also needs information such as:
- Ship-from
- Ship-to
- Country
- Delivery location
- Incoterms
- Movement type
- Transportation details
These can influence the tax determination and reporting requirements.
10. The Key Relationship
The whole diagram can actually be reduced to this:
Business Transaction
↓
SAP Master Data
↓
Tax Determination
↓
Invoice
↓
Tax Reporting
↓
Buyer Tax Credit / Recovery
↓
Intercompany Reconciliation
And if the transaction crosses borders:
↓
Cross-Border Compliance
11. Why Master Data Is So Critical
Imagine Company A sells goods to Company B.
The material master says:
Product = taxable
But the customer master has the wrong country.
Or the plant is assigned to the wrong tax registration.
Or the ship-to address is incorrect.
Or the tax classification is wrong.
Then SAP may determine the wrong tax treatment.
That can result in:
Wrong master data → Wrong tax determination → Wrong invoice → Wrong tax reporting → Possible tax exposure
This is why indirect tax in SAP is not just a tax configuration problem.
It is also a:
Master Data + Transaction Data + Tax Configuration + Process Governance problem.
12. One Simple Real-Life Example
Let’s take:
Company A – India
Company B – Germany
Company A sells machinery worth €100,000 to Company B.
SAP checks:
Who sells?
→ India Company
Who buys?
→ Germany Company
What is sold?
→ Machinery
Where does it ship from?
→ India
Where does it go?
→ Germany
What is the Place of Supply?
→ Determined according to the applicable tax rules
Which tax registration is relevant?
→ SAP checks the relevant registration/master data
What tax treatment applies?
→ SAP determines it based on configured rules and transaction data
Then:
Invoice → Tax reporting → Buyer recovery/credit if eligible → Reconciliation
13. The Main Message of the Diagram
If I had to explain this diagram to a non-SAP or non-tax person in one sentence, I would say:
“SAP S/4HANA uses information about the companies, customers, materials, plants, locations and tax registrations to decide the correct indirect tax when one group company sells to another, then carries that tax information through invoicing, reporting, recovery and reconciliation.”
And the golden rule is:
Correct Master Data + Correct Tax Rules + Correct Transaction Data = Correct Tax
