Pillar Two Workflow helps tax teams generate workplans, manage GIR filing routes, track local returns and notifications, apply QDMTT jurisdiction-specific tailoring, assess safe harbours, collect evidence and control review/sign-off.
Account required. Beta access is intended for in-house tax teams, advisers and Pillar Two project leads.
Pillar Two Workflow
BetaWhat it does
Use the beta to convert Pillar Two filing obligations, local registrations, safe harbour positions, QDMTT differences and evidence requirements into a practical workplan.
Create Pillar Two workplans from a reporting year, fiscal year-end, UPE jurisdiction, constituent entity jurisdictions and GIR filing strategy.
Model central filing by a UPE or Designated Filing Entity, local GIR filing, foreign lodgment notifications, exchange monitoring and fallback review.
Show jurisdiction-specific QDMTT local-rule summaries, scope/design facts, review points, warnings and selected workflow items.
View safe harbour profiles, start assessments, document reliance decisions and link review points to GIR, QDMTT, IIR, UTPR and payment workflows.
Manage core and conditional evidence, reviewer sign-off, filing receipts, authority correspondence and evidence archive indexes.
Assign owners, request reviews, add comments, manage documents and create controlled adviser/client request workflows.
Why this exists
Tax teams need to know what is due, who owns it, what evidence is needed, which filings are local or central, which safe harbours are being assessed, and what still needs approval before submission.
Workflow coverage
The beta uses obligation-specific templates rather than treating every filing as a generic return.
Central GIR filing, local GIR filing, GIR notification, foreign lodgment notification, exchange monitoring and fallback filing assessment.
QDMTT/DMTT returns, IIR returns, UTPR returns, combined local top-up tax returns and generic local top-up tax returns where the mechanism is fact-dependent.
Registration and portal access, payment and instalment workflows, local additional information reports and post-filing monitoring.
GIR filing strategy
The tool lets users determine the GIR filing route and then generates the related workflows without duplicating local filings where central filing applies.
Select whether the GIR is filed centrally by the Ultimate Parent Entity or by a Designated Filing Entity.
Source-driven double filing relief/foreign lodgment notifications are used where available and route-generated notifications fill gaps only where needed.
Where a jurisdiction is covered by central filing, the workflow tracks exchange status and fallback local filing risk.
QDMTT V2 tailoring
QDMTT V2 separates source-profile facts from active review points. It shows the local-rule position while avoiding long generic checklists unless the jurisdiction value creates a real action.
A standard QDMTT/DMTT return workflow covers applicability, filer and CE scope, data request, calculation, reconciliation, review, filing and monitoring.
Local rule profiles add key scope/design facts, review points, source references and selected checklist/evidence items only where value-aware logic supports it.
Safe harbours
Safe harbour availability is treated as profile data. Reliance is a user-controlled assessment decision. Filings and payments are not removed automatically.
View safe harbour availability, restrictions, domestic implementation status and workflow impact by jurisdiction.
Start an assessment, collect evidence, document conditions, record review and approve or reject reliance decisions.
Safe harbour positions create review, disclosure, evidence and payment-position tasks. They do not automatically remove filings or payments.
Safe harbour workflow impact
Safe harbour impact is shown as Direct, Disclosure, Review, Indirect/Review or No direct impact so users understand where a safe harbour needs to be considered.
| Safe harbour type | Typical workflow impact | Product treatment |
|---|---|---|
| Transitional CbCR Safe Harbour | GIR disclosure/review, QDMTT review where domestic DMTT includes it, IIR/UTPR review and payment-position review. | Assessment and cross-reference. No filing/payment suppression. |
| QDMTT Safe Harbour | Direct QDMTT review, GIR disclosure/review, IIR/UTPR residual exposure review and payment-position review. | Assessment, QDMTT component review and evidence. No automatic payment conclusion. |
| Transitional UTPR/NMCE/simplified safe harbours | Review and evidence depending on safe harbour type and jurisdiction profile. | Generic assessment workflow unless bespoke mapping exists. |
Evidence and review
Evidence is grouped by obligation and requirement level so users can focus on core items first, then add conditional or full-control support where needed.
Filed returns, receipts, approvals, calculation workbooks, source data packs and key reconciliations.
Safe harbour support, local adviser memos, fallback assessments, corrections, restricted-status acknowledgements and jurisdiction-specific support.
Request reviews, track sign-offs, preserve audit trail and document approved reliance decisions or changes in position.
How it works
Select reporting year, fiscal year-end, UPE jurisdiction, constituent entity jurisdictions and GIR filing route.
The tool creates filing, notification, exchange, fallback, return, registration, payment and safe harbour workflows.
QDMTT V2 tailoring and safe harbour profiles add review points and source detail without flooding the workplan with generic tasks.
Assign owners, upload evidence, document conclusions, request review and maintain a defensible record.
Capture technical review, filing approval, safe harbour reliance decisions, payment review and final evidence archive.
Use workplan exports, evidence indexes and status reports to manage deadlines, open items and filing progress.
Confidentiality and beta use
Pillar Two workflows can include sensitive group, entity, tax and filing information. The beta is designed around account login, controlled workspaces and explicit user actions.
Workplans, evidence, comments, exports and external packages are associated with authorised users and controlled workspaces.
Generated workflows, QDMTT tailoring and safe harbour profiles support review. They do not replace professional judgement.
Users should start with test or non-production data where possible and upload real data only where authorised.
FAQ
Beta access is available to selected users while the workflow, QDMTT tailoring, safe harbour and evidence features are tested. Account access is required.
No. The tool supports workflow generation, compliance tracking, evidence management and review. Outputs should be reviewed by qualified tax professionals before reliance.
Yes. The workflow supports central GIR filing by a UPE or Designated Filing Entity, with covered jurisdictions receiving foreign lodgment, notification, exchange monitoring or fallback workflows where relevant.
QDMTT V2 tailoring shows jurisdiction-specific QDMTT status, accounting standard treatment, domestic deviations, currency provisions, safe harbour/AG status, scope/design facts and selected review points.
No. Safe harbour availability creates assessment and review workflows. Reliance requires user review and approval. Filings and payments are not automatically removed.
No. Pillar Two Workflow is an independent workflow and compliance management tool from OECDPillars.com. It is not affiliated with the OECD or any tax authority.
Try the beta
Test the workflow with selected jurisdictions, GIR filing strategies, QDMTT local-rule tailoring, safe harbour assessments, evidence packs, task ownership and exports.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |