Introduction to Invoice Method – Japan TAX Reform effective on October 1st 2023
This blog provides you the main notes regarding Japan FY 2016 Tax Reform Invoice Method valid from October 1st, 2023
Remark: Japanese Emperor’s era REIWA started from May 1st, 2019. Even if the source documents, websites say HEISEI, to easily understand the year, on this blog itself, HEISEI is replaced with REIWA accordingly.
On December 16th, 2015, Japanese Government published Outline of FY 2016 Tax Reform:
It mentions that VAT legal change will occur in Japan.
(1) Standard VAT rate would become 10%, effective on April 1st, 2017 (HEISEI 29).
(2) Reduced VAT rate, which would be 8%, would be applied for transfers of a certain goods only.
(3) Regarding separate accounting (KUBUN KEIRI), “TEKIKAKU SEIKYUSHO TOU HOZON HOUSHIKI” (equal to Invoice Method in Europe) would be finally introduced into Japan from April 1st, 2021 (REIWA 3). Until there, an easy method, “KUBUN KISAI SEIKYUSHO TOU HOZON HOUSHIKI” was introduced.
On HEISEI 28 (2016) November 18th, in House of Councilors Plenary Session, the amendment law to postpone raising VAT rate to 10% to REIWA 1 (2019) October 1st from HEISEI 29 (2017) April 1st was approved and passed.
As a result, the schedule on raising VAT rate to 10% and introducing the reduced VAT rate system was postponed to REIWA 1 (2019) October 1st, which is 2.5-years shift. Nevertheless, it was confirmed that “Specified Date” of transitional measures on VAT rate for the contracted constructions, etc, was HEISEI 31 (2019) April 1st.
Finally, the schedule to introduce TEKIKAKU SEIKYUSHO TOU HOZON HOUSHIKI (so-called, Invoice Method) is changed to REIWA 5 (2023) October 1st.
Observation: This information is based on legislation and regulations that could be subject to change at any time by the respective authorities, and are therefore not binding. This blog will be updated if necessary.
SAP KBAS & Notes Available
For further understanding of the requirements on Invoice Method (TEKIKAKU SEIKYUSHO HOZON TOU HOUSHIKI) and SAP’s understanding to it, please refer to the Main note:
After understanding the context of this legal requirement change, if you want to understand how this impact on S/4HANA Cloud System in contrast, please check:
Disclaimer: The information offered here is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. The referred information is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this information source, or to develop or release any functionality mentioned therein. This information source and SAP’s strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information offered here is not a commitment, promise or legal obligation to deliver any material, code or functionality. This information source is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This information source is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this information source, except if such damages were caused by SAP´s willful misconduct or gross negligence. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.