Page 1

Contents
1.

Introduction ................................................................................................................................................................ 3

2.

Branch code flow from master data to SD, MM and FI postings ................................................................................ 4

2.1.

Master Data Extension. ........................................................................................................................................... 4

2.2.

Branch code field in Sales Order. ............................................................................................................................ 6

2.2.1.

Posting rules ........................................................................................................................................................ 7

2.3.

Branch code field in MM ......................................................................................................................................... 7

2.4.

Branch code field in FI [enjoy and classical transactions] ....................................................................................... 8

2.4.1.

Enjoy screen ........................................................................................................................................................ 8

2.4.2.

Classical screen [ FB01 ] ...................................................................................................................................... 8

2.4.3.

Display of Branch code in FB03 [for postings of FI, MM and SD]........................................................................ 9

3.

Display of Branch code in VAT report ....................................................................................................................... 10

Page 2

1. Introduction
The announced legal change will impact customer systems and operation because valid tax invoices must contain
additional information such as branch code and tax number. In effect, a buyer has to request for full tax invoice from
vendors, and must provide the vendor a valid tax ID number (13 digits) and branch number of respective affiliates
entitled for VAT credit. Besides this, the seller is required to put tax ID number and branch number of the customer into
the sale tax invoice as well. In other words, tax ID number/branch information has to be included in both purchase and
sales tax invoices. From SD point of view, to keep billing an automatic process, branch code should be visible and
changeable already on Sales Order along with Billing.[ process details are available in section 3 ].
TH Branch Code Definition
A branch in TH is defined as a customer/vendors tax registered entity, which is linked to a unique
customer/vendor tax ID. A customer/vendor has one or many branches, depending on how many separate locations a
company is operating from. In practice, all branches of a given company are linked to the same Tax ID, with each branch
carrying a different 4- or 5-digit branch code that is assigned by the TH Revenue Department. In all cases, the head office
branch carries the branch code 00000.
The number of branches per customer/vendor can be high, so we cannot expect that our customers create
separate master data (vendor/customer) per partner branch. And also, its not related or has a 1 to 1 mapping with
partner functions ( bill to / ship to and so on ) or linked to plant / sales office, because, in the real world scenario, bill to
and ship to can be anywhere hence what matters is, the receiver of the VAT which can be any branch of the customer.
Note: Branch in this context is not to be confused with address/location. It is merely a tax entity only.
Example of Companies with 1 Branch and Multiple branches.

SAP Thailand 00000

Page 3

2. Branch code flow from master data to SD, MM and FI postings

Master Data

Update master data with head

office or main branch code

Sales Order step 1

SD

Show the default value of the

branch code maintained in
customer master in the sales order
[ item data : based on Bill to party ]

MIRO step 1
MM

2.1.

Show the default value of the

branch code maintained in Vendor
master in the MIRO screen [Basic
data tab]

Billing & FI

Sales Order step 2

User shall decide to edit or use the
default value.
Note: It has to be unique per
Branch code

After posting of Sales order,

Branch code shall be transferred to
billing and FI document.

MIRO step 2
User shall decide to edit or use the
value fetched show from master
data

MIRO Copy to FI
User to post the MIRO document,
the automatic generated FI
document shall be copied with
branch code updated in MIRO

Master Data Extension.

A company can have business with customers/vendors having one or multiple branches. Customers/Vendors
with single branch shall enter only head office branch code 0000. Companies with multiple branches can wish to create
separate master data for each branch or create one master data and maintain other branch codes of the respective
branches.
Steps to maintain branch codes :
Step 1: Execute FD03/FK03 and select the respective customer / vendor number.
Step 2: Click Thailand Branch Details button from the application toolbar.
Step 3: System will show branch code entry screen.

Page 4

Previously only one Tab was available to maintain Branch details ( as shown above ), as an extension of
this, one more Tab is added ( as shown below ) , to maintain multiple branch codes.

Page 5

Step 5: Start entering branch codes of customer / vendor master. To enter a new branch, click insert and to remove the
branch, select the entry and click delete.
Step 6 : To make the maintenance easy, system will copy the first branch code from branches list to Default branch, if
default branch is not maintained already, else user can change it using the F4 option, which in turn contain the values
maintained in Maintain branches tab.
Rule of deletion: if user wants to delete a branch code which is maintained as default, system will show a warning
message and if Yes is selected, system will delete the entry, both from the list as well as from default branch.
Rule of non-registered customer/vendor: If the customer or vendor is not registered for VAT, specify key word NVAT
under branches tab and save the entry, system will then show the same value in all the postings and in the VAT report
no branch code value will be shown under head office field or Branch code field. This is the requirement from Thailand
revenue department.
Step 7: Save the entries.
During the postings of FI/MM/SD documents, system will show default branch thats maintained under Default branch
tab of the master data and also it will provide an F4 option to select relevant branch code to be posted for related
documents. .

2.2.

Branch code field in Sales Order.

In VA03 transaction, a new tab called country is available (under line item) to enter country specific
information.

Page 6

A new field is introduced in sales order under country tab. By default, system will show the default branch
value maintained in master data. If users dont want to use the default branch code suggested by the system,
they can change the branch code using F4 help (values will be fetched from Maintain branches tab).

2.2.1. Posting rules

-

System will show the Bill to party thats configured as a partner function of Sold to party, If user changes
the bill to party in the sales order line item, system will show the default value and F4 of the selected Bill
to party.
If all the line items have the same bill to party, user should make sure branch code is chosen in all the line
items of the sales order.
Invoice will split if there are different bill to parties selected in the sales order line item.

2.3.
-

Branch code field in MM

A new field is introduced in Basic data tab of MIRO posting screen [as shown below].
Branch code field will appear after user specified the purchase order and press enter.
By default, system will show the default branch value maintained in the vendor master data. If users dont
want to use the default branch code suggested by the system, they can change the branch code using F4
help (values will be fetched from the Maintain branches tab).

Page 7

2.4.
-

Branch code field in FI [enjoy and classical transactions]

A new field is introduced in Basic data tab of FB60/70/65.75 posting screen [as shown below].
Branch code field will appear after user specifies the vendor / customer number and press enter.
By default, system will show the default branch value maintained in the vendor master data. If users dont
want to use the default branch code suggested by the system, they can change the branch code using F4
help (values will be fetched from Maintain branches tab).

2.4.1. Enjoy screen

2.4.2. Classical screen [FB01]

-

A new field is introduced in More data button of FB01 posting screen [as shown below].
Branch code field will only appear after entering Vendor and Customer line item, users shall click More
data button to see the branch code filed.
System will show the default value of the branch code as well as F4 help.

Page 8

2.4.3. Display of Branch code in FB03 [for postings of FI, MM and SD]
-

Users can configure Branch code in line item using layout configuration else its also shown in More data
of customer / vendor line item.
In the FI Documents posted from SD and MM will also get copied with Branch code.

Page 9

3. Display of Branch code in VAT report

-

Report shows branch code data in 2 different fields: Head office number and Branch office number.
If the branch code value is 0 / 00 / 000 / 0000 / 0000, a text Head office will be shown in the field Head office
number otherwise respective branch code value will be shown in Branch office number field.

If any customer / vendor are not registered, nothing will be shown under Head office number and Branch office
number. This will be determined using branch code value NVAT [refer master data for more details on NVAT] .

In SD postings, if payer and bill to party are different, report will fetch the bill to party from Sales order and show it
in the output list field Bill to party.

Page 10