Singapore-headquartered multinational enterprises (MNEs) meeting certain conditions are required to prepare and file CbC Reports to IRAS for financial years (FYs) beginning on or after 1 Jan 2017.

What is Country-by-Country Reporting (CbCR)?

Country-by-Country Reporting (CbCR) is a form of reporting by multinational enterprises (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 conditions are required to prepare and file CbC Reports to IRAS for financial years (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 ('MCAA CbCR'). The signing of the MCAA CbCR will enable Singapore to efficiently establish a wide network of exchange relationships for the automatic exchange of CbC Reports. View the press release.

The MCAA CbCR 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 MCAA CbCR, 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 AEOI relationships under the MCAA. At the present time, not all the 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

 Jurisdictions  Exchange relationship effective from
1. Andorra  FY2018
2. Anguilla FY2019
3. Argentina FY2017 
4. Australia  FY2016 
5. Austria  FY beginning 1 June 2016 
6. Bahamas FY2019 
7. Bahrain New! FY2021 
8. Belgium  FY2016
9. Belize FY2019 
10. Bermuda  FY2017 
11. Brazil FY2016 
12. British Virgin Islands FY2018
13. Bulgaria  FY2016 
14. Canada  FY2017 
15. Cayman Islands  FY2016
16. Chile  FY2017 
17. China FY2017 
18. Colombia  FY2016 
19. Costa Rica FY2017
20. Croatia  FY2017 
21. Curacao FY2018 
22. Cyprus  FY2017 
23. Czech Republic  FY beginning 1 October 2016 
24. Denmark FY2016 
25. Estonia  FY beginning 1 August 2016 
26. Finland  FY2016 
27. France  FY2016 
28. Germany  FY2016 
29. Gibraltar FY beginning 1 July 2019 
30. Greece  FY2016 
31. Guernsey  FY2016 
32. Hong Kong FY2019
33. Hungary FY2017
34. Iceland FY2017
35. India  FY2016 
36. Indonesia  FY beginning 1 May 2016 
37. Ireland  FY2016 
38. Isle of Man FY2017
39. Italy  FY2016 
40. Japan  FY2016 
41. Jersey  FY2016 
42. Kazakhstan FY2017 
43. Korea  FY2016 
44. Latvia  FY2017 
45. Liechtenstein FY2017
46. Lithuania  FY2016 
47. Luxembourg  FY2016 
48. Macau New! FY2019 
49. Malaysia FY2017
50. Malta FY2016 
51. Mauritius FY2018
52. Mexico  FY2016 
53. Monaco  FY2018
54. Netherlands  FY2016 
55. New Zealand  FY2016 
56. Nigeria  FY2018 
57. Norway  FY2016 
58. Oman FY2021 
59. Pakistan  FY2016
60. Panama FY2018
61. Peru FY2017
62. Poland  FY2016 
63. Portugal  FY beginning 1 August 2016 
64. Qatar  FY2017 
65. Romania  FY2016
66. Russia FY2017
67. San Marino FY2019
68. Saudi Arabia FY2018
69. Seychelles FY2019
70. Slovak Republic  FY2016 
71. Slovenia  FY2016 
72. South Africa  FY2016 
73. Spain  FY2016 
74. Sweden  FY2016 
75. Switzerland  FY2018
76. Turks & Caicos Islands FY2020
77. United Arab Emirates FY2019
78. United Kingdom  FY2016
79. United States FY2021
80. Uruguay  FY2017

FY2016 means FY beginning 1 Jan 2016.
FY2017 means FY beginning 1 Jan 2017.
FY2018 means FY beginning 1 Jan 2018. 
FY2019 means FY beginning 1 Jan 2019.
FY2020 means FY beginning 1 Jan 2020.
FY2021 means FY beginning 1 Jan 2021.

Updated as at 29 Apr 2021.

FAQs

  1. What is the MCAA on CbC Reports?

    The MCAA CbCR 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 MCAA CbCR rests in Article 6 of the Multilateral Convention on Mutual Administrative Assistance in Tax Matters ('the Convention') which provides for the Automatic Exchange of Information ('AEOI') between parties to the Convention, where 2 parties subsequently agree to do so. More information on the MCAA CbCR, including the text of the MCAA, can be found on the OECD website.

  2. Why did Singapore sign the MCAA CbCR?

    The signing of the MCAA CbCR reaffirms Singapore’s commitment to the international standards on tax cooperation. The MCAA CbCR 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 MCAA CbCR will enable Singapore to efficiently establish a wide network of exchange relationships for the AEOI of CbC Reports.

  3. Does signing the MCAA CbCR mean Singapore will exchange information with all MCAA signatories?

    No, signing the MCAA CbCR 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 unauthorized use; and
    • There is full reciprocity with the AEOI partner in terms of information exchanged.
  4. How will taxpayers know which jurisdictions have an effective exchange relationship with Singapore under the MCAA CbCR?

    The list of effective exchange relationships is available on the OECD and IRAS website.

CbCR Filing Requirements

Who needs to file the CbC Report

The ultimate parent entity of the Singapore MNE group will be required to file a CbC Report for all entities in the group. The MNE group is required to submit the CbC Report if it meets all of the following conditions:

  1. The ultimate parent entity of the MNE group is tax resident in Singapore;
  2. Consolidated group revenue for the MNE group in the preceding financial year is at least S$1,125 million; and
  3. The MNE group has subsidiaries or operations in at least one foreign jurisdiction.

When CbC Report should be submitted

CbC Report should be submitted to IRAS within 12 months from the end of the ultimate parent entity's financial year.

For the purposes of CbCR, FY 2018 refers to financial year beginning on or after 1 Jan 2018 but before 1 Jan 2019.

Examples

  • Ultimate parent entity's FY ends in Dec:
    The CbC Report relating to the financial period 1 Jan 2018 to 31 Dec 2018 (FY 2018) should be submitted to IRAS no later than 31 Dec 2019.
  • Ultimate parent entity's FY ends in Mar:
    The CbC Report relating to the financial period 1 Apr 2018 to 31 Mar 2019 (FY 2018) should be submitted to IRAS no later than 31 Mar 2020.

Information to be Included in the CbC Report

A CbC Report of the 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 report must be submitted based on the format specified in Paragraph 5 of the CbCR e-Tax Guide. You may refer to the e-Tax Guide on Country-by-Country Reporting (PDF, 712KB) for details on the report format and information to be submitted.

Notification of Filing Obligation

Each year, IRAS will issue notification letters to the Reporting Entities on their obligation to file a CbC Report to IRAS for the preceding FY. For example, IRAS will send the notification letters to the Reporting Entities for FY 2018 CbC Report by 31 Jul 2019.

If you are required to file a CbC report for a FY based on the conditions (in the paragraph on 'CbCR Filing Requirements' above) but have not received IRAS’ letter by 31 Jul of the following year, contact IRAS immediately via email to [email protected].

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 [email protected]:

  • Name and UEN 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 your reply)

A Singapore constituent entity of a foreign MNE Group is not required to notify IRAS of the foreign Reporting Entity that will be filing a CbC report in the foreign jurisdiction.

How to Submit the CbC Report

Reporting Entities will need to have processes in place to collate and prepare the required data 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.

VersionStatusXML SchemaUser Guide
2.0Current

CbCR XML Schema v2.0 (ZIP, 17KB)

(OECD’s publication date: Jun 2019)

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 Reporting Data File (XLXS, 221KB)

(Updated for CbCR XML Schema version 2.0)

Refer to the table below for the CbCR XML Schema version to be used for the different CbC reports:

VersionOriginal or Revised CbC Reports for FYDate of Submission
1.0.1FY 2018 and beforeBefore 1 Nov 2020
2.0FY 2018 and beforeOn or after 1 Nov 2020
2.0FY 2019 and afterOn or after 1 Nov 2020

Reporting Entities must submit their XML CbC reports via email to [email protected] with the following details:

  • Name of the ultimate parent entity (i.e. Reporting Entity)
  • Financial reporting period (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 your behalf, if the third party is different from the one you have authorised via Corppass

The XML CbC report must be zipped (file extension must be in zip format *.zip) 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, call 6351 2609 (Mondays to Fridays, 8 am to 5 pm) to provide us with the password to open the report.

^Note: Please use a strong password. It is recommended that the password should be:
- At least eight characters; and
- Alphanumeric with at least one upper and lower case alphabet, number and symbol (e.g. Pj57#uEw).

Penalties for Non-Compliance

Late Filing or Failing to File CbC Report

If a company required to file the CbC Report fails to do so by the due date, IRAS may take the following actions:

  1. Impose a fine of up to $5,000. If this fine is not paid, the person responsible for the offence may be imprisoned for up to 6 months.
  2. Impose a further fine of up to $100 for every day during which the offence continues after conviction.

False/ Misleading CbC Information

A company which provides false or misleading CbC information may face the following consequences:

  1. A fine of up to $10,000; and/or
  2. Person responsible for the offence may be imprisoned for up to 2 years.

For more details, refer to our e-Tax Guide on Country-by-Country Reporting (PDF, 712KB).

For enquiries, email us at [email protected].