Singapore-headquartered multinational enterprise (MNE) groups meeting certain requirements are required to prepare and file CbC Reports to IRAS for financial years (FYs) beginning on or after 1 Jan 2017 within 12 months from the end of their FY.
For FY beginning on or after 1 Jan 2022, these Singapore MNE groups are also required to notify IRAS of their obligation to file a CbC Report, within 3 months from the end of that relevant FY.
On this page:
What is CbCR?
CbCR is a form of reporting by MNEs initiated by the Organisation for Economic Co-operation and Development (OECD) in the Base Erosion and Profit Shifting (BEPS) Action 13 Report. In keeping with Singapore’s commitment to implement certain measures under the BEPS Project, Singapore-headquartered MNEs meeting certain requirements must prepare and file CbC Reports to IRAS for FYs beginning on or after 1 Jan 2017.
Qualifying Competent Authority Agreement
On 21 Jun 2017, Singapore signed the Multilateral Competent Authority Agreement on the exchange of CbC Reports (CbC MCAA). The signing of the CbC MCAA will enable Singapore to efficiently establish a wide network of exchange relationships for the automatic exchange of CbC Reports. View the press release.
The CbC MCAA is a multilateral framework agreement based on the Convention on Mutual Administrative Assistance in Tax Matters. It provides a standardised and efficient mechanism to facilitate the automatic exchange of CbC Reports. Under the CbC MCAA, signatories to the MCAA will automatically exchange CbC Reports with one another on a bilateral basis if both parties are mutually agreeable.
CbC Reports submitted to IRAS will be provided to tax authorities of jurisdictions with which Singapore has established bilateral Automatic Exchange of Information (AEOI) relationships under the MCAA. At the present time, not all signatories to the MCAA have provided full or complete notifications of their intended exchange relationships. Some jurisdictions may also increase their exchange relationships over time. The list of exchange relationships below is therefore not the final list of exchange relationships that Singapore will enter into. For more information, please visit the OECD webpage.
List of Jurisdictions
| Jurisdiction | Exchange relationship effective from |
|---|---|
| Jurisdiction 1. Albania | Exchange relationship effective from FY 2024 |
| Jurisdiction 2. Andorra | Exchange relationship effective from FY 2018 |
| Jurisdiction 3. Anguilla | Exchange relationship effective from FY 2019 |
| Jurisdiction 4. Argentina | Exchange relationship effective from FY 2017 |
| Jurisdiction 5. Aruba | Exchange relationship effective from FY beginning 1 May 2021 |
| Jurisdiction 6. Australia | Exchange relationship effective from FY 2016 |
| Jurisdiction 7. Austria | Exchange relationship effective from FY beginning 1 June 2016 |
| Jurisdiction 8. Azerbaijan | Exchange relationship effective from FY 2020 |
| Jurisdiction 9. Bahamas | Exchange relationship effective from FY 2019 |
| Jurisdiction 10. Bahrain | Exchange relationship effective from FY 2021 |
| Jurisdiction 11. Barbados | Exchange relationship effective from FY beginning 1 August 2021 |
| Jurisdiction 12. Belgium | Exchange relationship effective from FY 2016 |
| Jurisdiction 13. Belize | Exchange relationship effective from FY 2019 |
| Jurisdiction 14. Bermuda | Exchange relationship effective from FY 2017 |
| Jurisdiction 15. Brazil | Exchange relationship effective from FY 2016 |
| Jurisdiction 16. British Virgin Islands | Exchange relationship effective from FY 2018 |
| Jurisdiction 17. Bulgaria | Exchange relationship effective from FY 2016 |
| Jurisdiction 18. Canada | Exchange relationship effective from FY 2017 |
| Jurisdiction 19. Cayman Islands | Exchange relationship effective from FY 2016 |
| Jurisdiction 20. Chile | Exchange relationship effective from FY 2017 |
| Jurisdiction 21. China | Exchange relationship effective from FY 2017 |
| Jurisdiction 22. Colombia | Exchange relationship effective from FY 2016 |
| Jurisdiction 23. Costa Rica | Exchange relationship effective from FY 2017 |
| Jurisdiction 24. Croatia | Exchange relationship effective from FY 2017 |
| Jurisdiction 25. Curacao | Exchange relationship effective from FY 2018 |
| Jurisdiction 26. Cyprus | Exchange relationship effective from FY 2017 |
| Jurisdiction 27. Czech Republic | Exchange relationship effective from FY beginning 1 October 2016 |
| Jurisdiction 28. Denmark | Exchange relationship effective from FY 2016 |
| Jurisdiction 29. Dominican Republic [NEW!] | Exchange relationship effective from FY 2023 |
| Jurisdiction 30. Estonia | Exchange relationship effective from FY beginning 1 August 2016 |
| Jurisdiction 31. Faroe Islands | Exchange relationship effective from FY beginning 1 August 2021 |
| Jurisdiction 32. Finland | Exchange relationship effective from FY 2016 |
| Jurisdiction 33. France | Exchange relationship effective from FY 2016 |
| Jurisdiction 34. Georgia | Exchange relationship effective from FY 2025 |
| Jurisdiction 35. Germany | Exchange relationship effective from FY 2016 |
| Jurisdiction 36. Gibraltar | Exchange relationship effective from FY beginning 1 July 2019 |
| Jurisdiction 37. Greece | Exchange relationship effective from FY 2016 |
| Jurisdiction 38. Guernsey | Exchange relationship effective from FY 2016 |
| Jurisdiction 39. Hong Kong | Exchange relationship effective from FY 2019 |
| Jurisdiction 40. Hungary | Exchange relationship effective from FY 2017 |
| Jurisdiction 41. Iceland | Exchange relationship effective from FY 2017 |
| Jurisdiction 42. India | Exchange relationship effective from FY 2016 |
| Jurisdiction 43. Indonesia | Exchange relationship effective from FY beginning 1 May 2016 |
| Jurisdiction 44. Ireland | Exchange relationship effective from FY 2016 |
| Jurisdiction 45. Isle of Man | Exchange relationship effective from FY 2017 |
| Jurisdiction 46. Israel | Exchange relationship effective from FY 2021 |
| Jurisdiction 47. Italy | Exchange relationship effective from FY 2016 |
| Jurisdiction 48. Japan | Exchange relationship effective from FY 2016 |
| Jurisdiction 49. Jersey | Exchange relationship effective from FY 2016 |
| Jurisdiction 50. Kazakhstan | Exchange relationship effective from FY 2017 |
| Jurisdiction 51. Kenya | Exchange relationship effective from FY 2022 |
| Jurisdiction 52. Korea | Exchange relationship effective from FY 2016 |
| Jurisdiction 53. Latvia | Exchange relationship effective from FY 2017 |
| Jurisdiction 54. Liechtenstein | Exchange relationship effective from FY 2017 |
| Jurisdiction 55. Lithuania | Exchange relationship effective from FY 2016 |
| Jurisdiction 56. Luxembourg | Exchange relationship effective from FY 2016 |
| Jurisdiction 57. Macau | Exchange relationship effective from FY 2019 |
| Jurisdiction 58. Malaysia | Exchange relationship effective from FY 2017 |
| Jurisdiction 59. Maldives | Exchange relationship effective from FY 2023 |
| Jurisdiction 60. Malta | Exchange relationship effective from FY 2016 |
| Jurisdiction 61. Mauritius | Exchange relationship effective from FY 2018 |
| Jurisdiction 62. Mexico | Exchange relationship effective from FY 2016 |
| Jurisdiction 63. Monaco | Exchange relationship effective from FY 2018 |
| Jurisdiction 64. Montserrat | Exchange relationship effective from FY 2024 |
| Jurisdiction 65. Netherlands | Exchange relationship effective from FY 2016 |
| Jurisdiction 66. New Zealand | Exchange relationship effective from FY 2016 |
| Jurisdiction 67. Nigeria | Exchange relationship effective from FY 2018 |
| Jurisdiction 68. Norway | Exchange relationship effective from FY 2016 |
| Jurisdiction 69. Oman | Exchange relationship effective from FY 2021 |
| Jurisdiction 70. Pakistan | Exchange relationship effective from FY 2016 |
| Jurisdiction 71. Panama | Exchange relationship effective from FY 2018 |
| Jurisdiction 72. Papua New Guinea | Exchange relationship effective from FY 2024 |
| Jurisdiction 73. Peru | Exchange relationship effective from FY 2017 |
| Jurisdiction 74. Poland | Exchange relationship effective from FY 2016 |
| Jurisdiction 75. Portugal | Exchange relationship effective from FY beginning 1 August 2016 |
| Jurisdiction 76. Qatar | Exchange relationship effective from FY 2017 |
| Jurisdiction 77. Romania | Exchange relationship effective from FY 2016 |
| Jurisdiction 78. Russia | Exchange relationship effective from FY 2017 |
| Jurisdiction 79. San Marino | Exchange relationship effective from FY 2019 |
| Jurisdiction 80. Saudi Arabia | Exchange relationship effective from FY 2018 |
| Jurisdiction 81. Seychelles | Exchange relationship effective from FY 2019 |
| Jurisdiction 82. Slovak Republic | Exchange relationship effective from FY 2016 |
| Jurisdiction 83. Slovenia | Exchange relationship effective from FY 2016 |
| Jurisdiction 84. South Africa | Exchange relationship effective from FY 2016 |
| Jurisdiction 85. Spain | Exchange relationship effective from FY 2016 |
| Jurisdiction 86. Sweden | Exchange relationship effective from FY 2016 |
| Jurisdiction 87. Switzerland | Exchange relationship effective from FY 2018 |
| Jurisdiction 88. Thailand | Exchange relationship effective from FY 2023 |
| Jurisdiction 89. Tunisia | Exchange relationship effective from FY 2020 |
| Jurisdiction 90. Türkiye | Exchange relationship effective from FY 2020 |
| Jurisdiction 91. Turks & Caicos Islands | Exchange relationship effective from FY 2020 |
| Jurisdiction 92. Ukraine | Exchange relationship effective from FY 2023 |
| Jurisdiction 93. United Arab Emirates | Exchange relationship effective from FY 2019 |
| Jurisdiction 94. United Kingdom | Exchange relationship effective from FY 2016 |
| Jurisdiction 95. United States | Exchange relationship effective from FY 2021 |
| Jurisdiction 96. Uruguay | Exchange relationship effective from FY 2017 |
FY 20XX means FY beginning from 1 Jan 20XX. For example: FY 2016 means FY beginning 1 Jan 2016 while FY 2022 means FY beginning 1 Jan 2022.
Updated as at 05 Mar 2025.
FAQs
What is the CbC MCAA?
The CbC MCAA is a multilateral framework agreement that provides a standardised and efficient mechanism to facilitate the automatic exchange of CbC Reports. The legal basis for the CbC MCAA rests in Article 6 of the Multilateral Convention on Mutual Administrative Assistance in Tax Matters (the Convention) which provides for the AEOI between parties to the Convention, where 2 parties subsequently agree to do so. More information on the CbC MCAA, including the text of the MCAA, can be found on the OECD website.
Why did Singapore sign the CbC MCAA?
The signing of the CbC MCAA reaffirms Singapore’s commitment to the international standards on tax cooperation. The CbC MCAA has gained recognition internationally as a multilateral framework agreement for bilateral cooperation on AEOI of CbC Reports, with 57 signatories as at 1 Jun 2017.
Signing the CbC MCAA will enable Singapore to efficiently establish a wide network of exchange relationships for the AEOI of CbC Reports.
Does signing the CbC MCAA mean Singapore will exchange information with all MCAA signatories?
No, signing the CbC MCAA does not mean Singapore will automatically exchange CbC Reports with all the signatories.
Under the MCAA, each signatory has ultimate control over exactly which exchange relationships it enters into and that each signatory’s standards on confidentiality, data protection and appropriate use of information will always apply. Singapore will establish bilateral AEOI relationships with fellow signatories that can meet the following principles:
- The AEOI partner has the safeguards needed to ensure the confidentiality of information exchanged and prevent its unauthorised use; and
- There is full reciprocity with the AEOI partner in terms of the information exchanged.
Which jurisdictions have an effective exchange relationship with Singapore under the CbC MCAA?
The list of jurisdictions with an effective exchange relationship with Singapore is available on the OECD and IRAS website (see above).
CbCR Filing Requirements
Who needs to file the CbC Report
You will need to file a CbC Report with IRAS if you meet all of the following requirements:
- You are the ultimate parent entity of a Singapore MNE group;
- You are tax resident in Singapore;
- The consolidated group revenue for your MNE group in the preceding FY is at least S$1,125 million; and
- Your MNE group has subsidiaries or operations in at least 1 foreign jurisdiction.
When CbC Reports should be submitted
CbC Reports should be submitted to IRAS within 12 months from the end of the ultimate parent entity's FY.
For the purposes of CbCR, FY 2021 refers to FY beginning on or after 1 Jan 2021 but before 1 Jan 2022.
Examples
- Ultimate parent entity's FY ends in Dec:
The CbC Report relating to the financial period 1 Jan 2021 to 31 Dec 2021 (FY 2021) should be submitted to IRAS no later than 31 Dec 2022. - Ultimate parent entity's FY ends in Mar:
The CbC Report relating to the financial period 1 Apr 2021 to 31 Mar 2022 (FY 2021) should be submitted to IRAS no later than 31 Mar 2023.
Information to be Included in the CbC Report
A CbC Report of an MNE group will include information on the group’s global allocation of the income and taxes paid in different jurisdictions and other financial data. CbC Reports submitted to IRAS will be provided to tax authorities of jurisdictions with which Singapore has qualifying competent authority agreements for the automatic exchange of CbCR information. CbC Reports may be used by Singapore and other tax authorities in evaluating transfer pricing risks and other BEPS-related risks.
CbC Reports must be submitted based on the format specified in the ‘How to submit CbC Reports’ section below. You may refer to section 6 of the e-Tax Guide on Country-by-Country Reporting (PDF, 378KB) for details on the information to be submitted.
Notification of Filing Obligation
Before FY beginning on or after 1 Jan 2022
Each year, IRAS will issue notification letters to Reporting Entities on their obligation to file a CbC Report to IRAS for the preceding FY. For example, IRAS will send notification letters to Reporting Entities for the FY 2021 CbC Report by 31 Jul 2022.
If you are required to file a CbC Report for an FY (based on the CbCR filing requirements above) but have not received IRAS’ letter by 31 Jul of the following year, please email us immediately at ct_transfer_pricing@iras.gov.sg.
Reporting Entities which are required to file a CbC Report must provide IRAS with the following information at least 3 months before the filing deadline via email to ct_transfer_pricing@iras.gov.sg:
- Name and Tax Reference Number of the ultimate parent entity (i.e. Reporting Entity)
- Financial reporting period of the ultimate parent entity (DD/MM/YYYY to DD/MM/YYYY)
- Contact person’s name and contact number
- Email of contact person (if different from that used to provide the above information)
From FY beginning on or after 1 Jan 2022
With effect from from FY beginning on or after 1 Jan 2022, Reporting Entities must notify IRAS of their obligation to file a CbC Report via FormSG at https://go.gov.sg/cbcr, within 3 months from the end of their FY. The company director, principal officer or any person authorised by the company (including tax agents) can submit the notification via FormSG. IRAS will no longer issue notification letters to the Reporting Entities.
IRAS will verify the notifications filed by Reporting Entities and confirm their filing obligation within 2 months from the receipt of the notifications.
Entities Not Required to Notify IRAS
You are not required to notify IRAS if you are a Singapore Constituent Entity of a:
- Singapore MNE group and you are not the Reporting Entity
- Foreign MNE group
How to Submit the CbC Report
Reporting Entities will need to have processes in place to collate and prepare the data required in a CbC Report in accordance with the prevailing CbCR XML Schema set out in the table below. Data submitted to IRAS in any other format will not be accepted.
| Version | Status | XML Schema | User Guide |
|---|---|---|---|
| Version 2.0 | Status Current | XML Schema CbCR XML Schema v2.0 (ZIP, 17KB) (OECD’s publication date: Jun 2019) | User Guide CbCR XML Schema User Guide for Tax Administrations (PDF, 3.43MB) (For CbCR XML Schema version 2.0. OECD’s publication date: Jun 2019) IRAS Supplementary Instructions for Preparing CbCR Data File (XLXS, 310KB) (Updated for CbCR XML Schema version 2.0) |
Reporting Entities must submit their XML CbC Reports via email to ct_transfer_pricing@iras.gov.sg with the following details :
- Name and Tax Reference Number of the ultimate parent entity (i.e. Reporting Entity)
- Financial reporting period of the ultimate parent entity (DD/MM/YYYY to DD/MM/YYYY)
- If applicable, a letter of authority for a third party (e.g. a tax agent) to file on the Reporting Entity's behalf, if the third party is different from the one authorised by the Reporting Entity via Corppass
The XML CbC Report must be zipped (file extension must be in *.zip format) and password-protected^, with the Reporting Entity's name as the name of the file (e.g. ABC Ltd.zip). After you have emailed your CbC Report, please provide us with the password via FormSG at https://go.gov.sg/cbcrpw.
^Note: Please use a strong password. It is recommended that the password should be:
- At least twelve characters; and
- Alphanumeric with at least 1 upper and lower case alphabet, number and symbol (e.g. PCrj57#u6Ew!).
Penalties for Non-Compliance
Failure to Notify, File a CbC Report, or to Retain Documents and Information
Companies may face the following penalties in cases of non-compliance:
| Non-compliance | Penalties |
|---|---|
Non-compliance
| Penalties
|
| Non-compliance Failure to retain documents and information used to prepare a CbC Report for 5 years after the end of the FY | Penalties
|
False/ Misleading CbC Information
A company which provides false or misleading CbC information may face the following consequences:
- A fine of up to $10,000; and/or
- An imprisonment term of up to 2 years for the person responsible for the offence.
For more details, refer to our e-Tax Guide on Country-by-Country Reporting (PDF, 378KB).
For enquiries, email us at ct_transfer_pricing@iras.gov.sg.