New Zealand has adopted CARF directly and reports to Inland Revenue. DAC8 does not apply; that is the EU's law. Your first report is due by 30 June 2027. The one detail to watch is the tax year: New Zealand's runs 1 April to 31 March, so your reporting period is not the calendar year. Kryptos sets the period correctly, builds the file, and files it.
A crypto provider with a New Zealand link reports to Inland Revenue. As with other CARF rules, that link follows where your business is based, so most providers register and file in one place. Your users' home countries decide where their data ends up, not where you file.
New Zealand's tax year runs 1 April to 31 March, not the calendar year. Your CARF reporting period has to match that. A file built to a calendar-year period can be rejected on the dates in its header, which is an easy mistake to make. Kryptos sets the period to what Inland Revenue expects.
You file with Inland Revenue, and the data for each user is passed to the country where they are tax resident through the OECD's exchange system. Your New Zealand link decides that you file here; your users' residences decide where the data goes.
The first report is due by 30 June 2027. Because the reporting period follows the 1 April to 31 March tax year, the data you need is already being collected, so onboarding and self-certification have to be right now, not near the deadline.
It runs on one system. You send your own transaction and account data, Kryptos collects self-certifications and checks tax IDs at onboarding, works out gains on the right basis, and builds the exact file the authority accepts, checked against the schema before you submit.
No. DAC8 is the EU's law. New Zealand adopts the OECD's CARF standard through its own rules and reports to Inland Revenue.
By 30 June 2027, to Inland Revenue. Because New Zealand's tax year ends 31 March, the reporting period follows that offset rather than the calendar year.
Yes. The reporting period must match the 1 April to 31 March tax year. A file built to a calendar year can be rejected, so the period has to be set correctly in the header.
Book a demo. We'll go through your obligations and show it working on your own data.