Episode Transcript
[00:00:00] Speaker A: Foreign.
And welcome to A and M Tax Talks Tax Policy Updates, where we bring you practical insights into the latest developments in global tax policy.
This is Adraza. I'm a Senior Director in A and M Tax Accounting Services practice based in Hong Kong and I'm joined today by Tom Lobb, a Managing Director within our UK Tax practice.
[00:00:26] Speaker B: Thanks Ed. I'm very happy to be here.
[00:00:28] Speaker A: Thanks, Tom.
So today we are focusing on a narrow but an increasingly practical pillar two issue, the use of Local Financial Accounting Standards or LFAs, as we use as a quick acronym under a QDMTT where fiscal periods do not align.
This mismatch does create some complications and was addressed in the September Admin guidance by the oecd. We'll speak through this today.
Tom so let's start off with a question that many clients are asking me and I'm sure you're getting the same question as well.
If a company has a December 31st calendar year end for group reporting purposes, but it's operating within a jurisdiction where the subsidiary has a Fiscal year end September 30th year end, does that mismatch mean the subsidiary cannot use LFAS for the qdmtt?
[00:01:23] Speaker B: Thankfully, there's a few questions to kick off and the answer is no, not necessarily so. And that's the key clarification that the OECD issued earlier this year. So the fact that subsidiaries got a 30th of September fiscal year end, which differs from the parent's 31st December year end, doesn't automatically prevent use of LFAs.
That's an important question. And then the key thing is what fiscal period does the group actually use but BAS subsidiary when preparing the consolidated accounts for some briefs, Mitris take the subsidiary 30th of September accounts for consolidation subject to any required adjustments for significant transactions or events during the three month lag to 31 December. Other groups Matra bearish separate January to December reporting package for the subsidiary. Those two situations produced different results under the OECD guidance.
[00:02:10] Speaker A: That's interesting. So if the group genuinely uses the subsidiaries using your example October to September accounts and preparing the December 31st year end consolidated accounts, the local accounting period and the period used for that entity in the cfs, the consolidated financials are the same.
So that three month lag does not by itself force the entity to use the financial accounting standards of the upe.
But if the group uses January through December numbers for the subsidiary and the period used in the consolidated financials is different from the subsidiary's local October Through September period.
[00:02:53] Speaker B: Exactly. So in that second case, the QEMCT jurisdiction must generally require the UPD's accounting standard, subject to specific sections in the guidance. The test is not simply whether the locum and parent year ends differ. The group needs to identify the exact period of financial information used for that entity in preparing for consolidated financial statements.
[00:03:15] Speaker A: Thanks, Tom.
What if the constituent entity's local accounting period is different from the period actually used for that constituent entity in the consolidated financial statements?
[00:03:30] Speaker B: In that case, a PNTT jurisdiction applying the LFAS rule is generally going to have to require the UPE's Financial Accountancy Standard to be used. There is an important restructuring inception date. So the mismatch surprises because the entity became or ceased to be a constituent entity during that fiscal period or the immediately preceding fiscal period. That could be foreign acquisition, disposal, dissolution, merger, or similar sort of restructuring, including setting up a pe. That mismatch itself doesn't require the use of the UPE financial accounting standard.
[00:04:04] Speaker A: Interesting. So kind of like for many of our clients that are serial transactors. So if they acquire a company partway through the year, the group may consolidate it only from the acquisition date while the company continues to maintain its normal financial accounts. The OECD recognizes that that this may happen and naturally leaves us comparing different periods.
[00:04:27] Speaker B: That's right. So a period mismatch is created by the entity entering or leaving the group should not, on its own, force that QVMT calculation to be based on the UBS accounting standard. And that's what Bayes, as I said earlier, referred to as the restructuring exception.
[00:04:42] Speaker A: All right, so now that we've dealt with the accounting standard question, and Tom, you've helpfully walked us through the restructuring exception as well, another question for you. What if the local jurisdiction itself prescribes the fiscal period that must be used for the QDMTT calculations?
[00:05:03] Speaker B: But a concept of a required QDMT fiscal period brought in. So a jurisdiction using the local FAS or the LFAS rule prescribe the period that the group must use to calculate the qtmtt. That local QMTT period may be the same or different from the UPE's fiscal year.
[00:05:22] Speaker A: So potentially we have the parent's fiscal year, the local entity's own accounting period, and the period the local jurisdiction requires it for QD MTT purposes.
[00:05:33] Speaker B: Yeah, that's right. So where the conditions for using LFAs are satisfied, the QWTT can be calculated under LFAs.
If an entity's own accounts don't align with the required QWT fiscal period.
The local accounting rules determine which amount of information feeds into the QDMCC calculation and there's some examples in the OC guidance that go through that.
[00:05:55] Speaker A: Thanks Tom, that's helpful.
Now let's assume the local jurisdiction has prescribed a QDMTT period that differs from the parent's fiscal year.
So now we have a situation where we have two different clocks running. How does that affect the QDMTT safe harbor?
[00:06:15] Speaker B: Okay, so let's assume the parents got a 31 December 2026 year end.
The local QDMT is calculated to 30 September. So the parents 2026 year overlaps with two local QWTT periods.
The first one ends on 3 September 2026 and the next starts on 1 October 26 and ends on 30 September 27.
[00:06:37] Speaker A: So from perspective, the December 2026 group year in nine months fall into one QDMT period and three months fall into the next.
[00:06:49] Speaker B: Exactly. So for the Q and a C parba to reduce the jurisdictional top up tax to zero for the whole of the 2026 UPE fiscal year, the SAPAB must apply to every required queued MCT fiscal period that begins and every such period that ends during that UPE year.
[00:07:06] Speaker A: Interesting. So I think for our clients the key message is really to, you know, you cannot just look at the QAD MTT period and ending September 2026, confirm that it qualifies and it says that I am finished. I also need to consider QDMT periods beginning in October 2026 because it's the first three months falling within the 2026 group reporting year end.
[00:07:31] Speaker B: Yeah, that's right Ed. And so if both the relevant QDMT periods qualify, then the jurisdictional top up tax for the UP fiscal year is reduced to zero if either period does not qualify, including the switch off rule, safe ARC doesn't qualify for the UP fiscal year. And I just one point to add, you know there's a to do all those tests in time for the compliance for your 31st December 26th year you've got quite a bit of you've got a short time there for that period ending in September 27th. So this is all, you know, trying to keep it going out to the prasmill side say how it works. But it could be quite hard for groups to get the data ready I suppose for the UPES fiscal year in that situation.
[00:08:13] Speaker A: No, no, absolutely. Just in terms of practicality does create some complications.
I'll throw another complication into my example right now. Tom, what happens if one of those peers do not does not qualify?
I don't think we're saying that the local QDMT disappears, does it?
[00:08:33] Speaker B: No. So the group might still have paid or be liable for QWTT locally while they lose the safe harbor treatment that would otherwise deem the jurisdictional top up tax to be zero for UP's fiscal year. So we need to determine how much of the QWTT relates to the parent's fiscal year. So the appropriate amount is then taken into account under the GLOBE rules for calculating an IIR rules.
[00:08:58] Speaker A: So we are matching the QDMTT calculated on the September year end back to the December group year end to ensure that we're not double counting or miss any top up tax simply because the periods do not align with each other.
[00:09:17] Speaker B: Exactly. So the first QDMCT period is allocated. Sorry, the QDMCT is first allocated to the relative months based on the income arising in those months. If that's not reasonably practical, you can allocate pro rata over the period.
[00:09:34] Speaker A: Maybe just a very simple example and going through the guidance that was released by the oact, this example is given in there and I'll just speak through it at a high level and then Tom, I'll look to you for some comments.
The QDMTT for The period ending September 30, 2026 is 1200 and the QDMTT for the following period ending September 2027 is $2400.
The second period is subject to the switch off rule. So the safe harbor does not apply for the UP's 2026 year. How does that allocation work on
[00:10:10] Speaker B: we assume it's not reasonably practical to allocate based on the actual monthly income. Then the first amount is 100 per month.
So the nine months all over the calendar 2026 gives us 900 and the second period is 200 per month. So the three months from October through to December in 2026 give us another 600.
So that would mean the queued NTT attributable to the UPE's fiscal year for 2026 is $1,500. So it's a 900 plus the 600.
[00:10:38] Speaker A: So if the safe harbor applies across both relevant periods, the jurisdictional top up tax for the UP year is reduced to zero.
If it does not, the group must determine how much of the local QDMT belongs to the UPE year and take that into amount into account under the GLOBI calculation. Is that correct?
Another point too, as Tom, as we were going through the admin guidance, there's also specific transitional rule for a UPE fiscal year beginning on December 31, 2023 or during 2024.
[00:11:14] Speaker B: Yeah, so that's right. So broadly the jurisdictional top up tax can be deemed zero where the safe harbor applies to a required queued MTC fiscal period beginning during that 2024 UPD fiscal year even if the queued NCC did not come in full year for the ube. So that's the first period and then the second part is. But actually the switch offer will applies to rolling period. The same part remains elevated.
[00:11:37] Speaker A: Thanks om, that's helpful. So for fiscal year 26 and beyond the normal rule of testing all the required QAD MTT periods beginning or ending in the UP fiscal year needs to be the key focus. Thank you. Let's move on.
What does this mean for groups more broadly? Right. The guidance I think Tom does provide clarity but it also highlights a practical compliance issue which you also highlighted at the beginning of the podcast.
Many groups have built in their Pillar 2 process centrally around the consolidated accounts. How do you manage this best now?
[00:12:14] Speaker B: Yeah, that's right. I think I'll probably just reiterate that point. So this gives clarity but it also ends up with a a diversion away from perhaps a centralized process where you're just using you originally maybe thought we were going down to way of using the the upside financial statements and that's where the majority of your data comes from. The way we're going to end up I think is with more divergence from that and it's less, it'll be more often you won't be able to use a completely centralised approach which I think will absolutely cost for some groups. And so why is that? Well in an ELF bash jurisdiction that's got a required QFTC fiscal period, the local QUTC might be calculated using a different accounting standard, a different fiscal period or both compared with that central globe calculation that requires local standard financial data, jurisdiction specific data request and then a reconciliation between the QDMTT periods and the UPE fiscal year.
So then if the safe harbour doesn't apply, the group may also need to do a monthly income based allocation or evidence to support using a pro raster allocation where it's not reasonably practical to do it, you know, based on monthly income. So what groups need to do is then need to map four argents by jurisdiction. So the UPE fiscal year, the local entities local accounting period, the periods used for the institution entity, the consolidated financial statements and then any required QMCC fiscal year period fiscal period. So that's quite there's four things to map there. And they also need to identify potential switch off triggers and flag as we talked about earlier, acquisitions, disposals, mergers and other restructurings need to flag those early because those events can change the rental periods of the data required.
[00:13:55] Speaker A: There's a lot happening in this guidance over here, Tom, but there are three practical questions that I think we can all take Takeaway right? And this is the key message to our clients that you want to take a step back and think about right as you go through this. First, what accounting standard am I using? Compare the constituent entity's local accounting period with period that is actually used for the constituent entity for consolidated financial statement reporting purposes. Have that mapped out. Number two, what period of my test tank Determine whether the jurisdiction has a prescribed a required QDMT fiscal period.
Number three, does a QDMTT safe harbor apply for the UP fiscal year?
And where periods do not align, there's a bit of a mismatch. Identify every required QDMT period beginning or ending in that UPE year.
One final reminder for me as well, the OECD guidance is not necessarily the same as the enacted domestic law.
Companies need to assess how and when each relevant jurisdiction adopts the guidance into the local QDMT framework. Please keep that in mind.
Tom, Anything from you. In closing,
[00:15:15] Speaker B: like I said, that's been a really good discussion. As you say, lots of people taking hopefully this is a brown out.
[00:15:22] Speaker A: Thank you Tom. And thank you for all of you for listening in to our A and M tax talks. Tax policy updates. Enjoy the remainder of your week. Thank you.