Has anyone mapped ERP fields to GloBE income, covered taxes, and QDMTT/IIR ordering across multiple jurisdictions ahead of 2025 Q1 calculations, using the December 2024 OECD administrative guidance as the anchor? I can share a concise template (includes a country-by-country tie-out and a 30-point data map for groups with 10+ entities), but it’s general information only — please consult qualified legal counsel for jurisdiction-specific structuring or disputes.
But we anchored to the December 2024 admin guidance and built a small staging table that tags each entity’s current tax expense, cash taxes paid, and deferred movements from the ERP, plus a flag to drive the ‘QDMTT before IIR’ ordering; that made the country-by-country tie-out workable for 2025 Q1… Does your template go down to field-level (e.g., SAP ACDOCA/Oracle subledgers) or just categories? General information only — check specifics with your adviser.
We versioned the mapping by guidance date and added an ordering_key so QDMTT is consumed before IIR, plus a flag that splits P&L vs OCI deferreds to make the covered-tax tie-out stick. > template go down to field-level (e.g., SAP ACDOCA/Oracle subledgers) or just categories? General information only — check specifics I can share how we pulled ACDOCA doc types and tax GL ranges without custom ABAP — @davidson_06, did your staging handle that?
If you’re locking this “ahead of 2025 Q1,” add a credits layer: a QRTC flag plus a separate bucket for transferable-credit haircuts, keyed by jurisdiction and effective date. That feeds covered-tax mapping and keeps GloBE ETR/QDMTT ordering stable; also tag uncertain tax positions so they don’t slip in (general info only). @davidson_06 did you stage that off the ERP tax subledger or a separate view?