Skip to main content

πŸš“ Future Dated Obligations

This page seeks to summarise all the Future Dated Obligations (FDOs) across the Data Adapter, Management API, CDR Rules, and Data Standards. We chose to incorporate the Data Adapter obligations within this page to provide a succinct view of all obligations across legislative instruments, binding Data Standards and the HaaS product. We also have a summary of Prospective Obligations to help keep you informed about changes that are under consideration and historical obligations for your reference.

What We're Doing

We are aligning the Biza Platform with the 2026 Consumer Data Right FDOs through a phased release approach. The next release, planned for early February 2026, will include support for all March and July 2026 FDOs, as well as selected changes required for November 2026. Some November FDO requirements will be delivered in later releases. Further guidance will be provided ahead of each release, including confirmation of supported obligations, testing windows, and release notes, to ensure customers have clear visibility of what is included at each stage.

tip

The status column in each table provides a quick reference to the current progress of each FDO. Each status tag indicates where an obligation sits in our implementation process, from initial planning through to completion, helping you track what's coming, what's in progress, and what's available for you to implement.

  • Scheduled: Planned but not yet implemented. The obligation has a future effective date and is in our queue for upcoming work.
  • Analysis: Currently under review. We are assessing the required changes and determining our approach for implementation.
  • Implementing: Work is underway to deliver any required changes for the relevant FDO.
  • Available or Implemented: Implemented and ready for use. The changes are complete on our end and customers can now update their data adapters if required.

General Obligations​

This section outlines general Future Dated Obligations required for Biza's products.

ObligationRequired BySummaryAdapter ObligationRelease
26Q20130-Apr-26Assignment of biza-au:haas:manager:write role to users. Without this role, users will be unable to publish Outages through HaaS ManagerN/AMagellan.12
26Q20230-Apr-26Assignment of biza-au:pm:changeset:approve role to users. Without this role, users will be unable to schedule changesets or publish immediate changes to product reference data in Product Manager.N/AMagellan.12
27Q10228-Feb-27Retirement of path-based multi-brand routing. Path-based (PATH_BASED) multi-brand routing is retired in the Nebula series. Data Holders using path-based multi-brand routing β€” where secondary brands share the primary brand's domain and are distinguished by a realm prefix in the URL path (e.g. api.holder.com.au/brand-a) β€” MUST migrate each brand to its own fully-qualified host (a custom domain or a Nebula subordinate domain) before taking up the Nebula series. Data Holders already using domain-based per-brand domains (DOMAIN_BASED) are not affected by this change. See Multiple Brand Support for full details.N/ANebula.02

Data Adapter Obligations​

This section outlines the obligations Data Adapter implementers must meet in order to complete a functional HaaS deployment.

Sector Agnostic Obligations​

ReferenceObligationRequired ByStatusSummaryRelease
26Q401Retire Adapter Profiles Phase 2:
  • Azure PrivateLink + TLS + Static API Key

01-Nov-26AVAILABLECustomers MUST implement a supported adapter security profile.N/A

Banking Sector​

ReferenceObligationRequired ByStatusSummaryRelease
26Q101Implement Adapter GetEndpointMetaV5 and AdapterBankingAccountV316-Mar-26AVAILABLEBanking sector customers MUST implement GetEndpointMetaV5 and AdapterBankingAccountV3 to ensure support for Get Account Detail v4.Magellan.12
26Q401Implement Adapter GetEndpointMetaV5 and AdapterBankingAccountV409-Nov-26AVAILABLEBanking sector customers MUST implement GetEndpointMetaV5 and AdapterBankingAccountV4 to ensure support for Get Account Detail v5. AdapterBankingAccountV5 is a recommended upgrade, adding optional bsb handling (e.g. non-bank lender accounts) and the instalment account fields (instalments, isInstalmentDetailAvailable).Magellan.12
26Q411Implement Adapter listBankingTransactions V209-Nov-26AVAILABLEBanking sector customers MUST implement listBankingTransactions V2 to ensure support for Get Transactions for Account v2 and Get Transaction Detail v3, which introduce instalmentPlanId.Magellan.14 and Nebula.02
26Q412Implement Adapter listBankingInstalmentPlans09-Nov-26AVAILABLEBanking sector customers with instalment products MUST implement listBankingInstalmentPlans to ensure support for Get Instalment Plans for Account v1 and Get Instalment Plans Bulk v1. A single adapter operation serves both Consumer Data Standards endpoints. Customers without instalment products are not required to implement this operation.Magellan.14 and Nebula.02

Energy Sector​

Note

There are currently no data adapter obligations specific to the energy sector.

PRD Obligations​

Banking Obligations​

ReferenceObligationRequired ByStatusSummaryRelease
26Q101PRD Adapter Customers MUST implement GetBankingProductDetail V6 in their PRD Adapter16-Mar-26AVAILABLEMagellan.12
26Q301PRD Adapter Customers MUST implement GetBankingProductDetail V7 in their PRD Adapter13-July-26AVAILABLEMagellan.12

Management API Obligations​

ReferenceObligationRequired ByStatusSummaryRelease
27Q101Retire Biza Management API28-Feb-27AVAILABLECustomers integrating with the Management API for Dashboard will need to upgrade to the in-flight Consent API.Nebula.01

Β  Β 


Data Standards Obligations​

This section outlines the Future Dated Obligations mentioned in the Consumer Data Standards: Future Dated Obligations, when and how these obligations will be met by HaaS and what customer actions will be required to meet the obligation.

Sector Agnostic Obligations​

ObligationRequired ByStatusSummaryAdapter ObligationRelease
27Q20110-May-27ANALYSIS[Redirect to App] Data holders and data recipients MUST implement these standards on and from May 10th 2027.N/ATBA
27Q20210-May-27ANALYSIS[Authentication Flows] Data holders and data recipients MUST implement these standards on and from May 10th 2027.N/ATBA

Banking Obligations​

ObligationRequired ByStatusSummaryAdapter ObligationRelease
26Q10116-Mar-26AVAILABLEData Holders MUST implement v4 of the Get Products endpoint by March 16th 2026. Data Holders MAY retire v3 of this endpoint from May 11th 2026.26Q101 OR 26Q401Magellan.12
v3 will not be retired until a future Series release.
26Q10216-Mar-26AVAILABLEData Holders MUST implement v6 of the Get Product Detail endpoint by March 16th 2026. Data Holders MAY retire v5 of this endpoint from May 11th 2026.26Q101 OR 26Q401Magellan.12
v5 will not be retired until a future Series release.
26Q10316-Mar-26AVAILABLEData Holders MUST implement v4 of the Get Account Detail endpoint by March 16th 2026. Data Holders MAY retire v3 of this endpoint from May 11th 2026.26Q101 OR 26Q401Magellan.12
v3 will not be retired until a future Series release.
26Q30113-Jul-26AVAILABLEData Holders MUST implement v5 of the Get Products endpoint by July 13th 2026. Data Holders MAY retire v4 of this endpoint from August 10th 2026.26Q101 OR 26Q401Magellan.12
v4 will not be retired until a future Series.
26Q30213-Jul-26AVAILABLEData Holders MUST implement v7 of the Get Product Detail endpoint by July 13th 2026. Data Holders MAY retire v6 of this endpoint from August 10th 2026.26Q101 OR 26Q401Magellan.12
v4 will not be retired until a future Series release.
26Q4029-Nov-26AVAILABLEData Holders MUST implement v3 of the Get Accounts endpoint by November 9th 2026. Data Holders MAY retire v2 of this endpoint from December 7th 2026.26Q401Magellan.12
v2 will not be retired until a future Series release.
26Q4039-Nov-26AVAILABLEData Holders MUST implement v5 of the Get Account Detail endpoint by November 9th 2026. Data Holders MAY retire v4 of this endpoint from December 7th 2026.26Q401Magellan.12
v4 will not be retired until a future Series release.
26Q4049-Nov-26AVAILABLEData Holders MUST implement v2 of the Get Bulk Balances endpoint by November 9th 2026. Data Holders MAY retire v1 of this endpoint from December 7th 2026.N/AMagellan.14 and Nebula.02
26Q4059-Nov-26AVAILABLEData Holders MUST implement v2 of the Get Bulk Direct Debits endpoint by November 9th 2026. Data Holders MAY retire v1 of this endpoint from December 7th 2026.N/AMagellan.14 and Nebula.02
26Q4069-Nov-26AVAILABLEData Holders MUST implement v3 of the Get Scheduled Payments Bulk endpoint by November 9th 2026. Data Holders MAY retire v2 of this endpoint from December 7th 2026.N/AMagellan.14 and Nebula.02
26Q4079-Nov-26AVAILABLEData Holders MUST implement v2 of the Get Transactions for Account endpoint by November 9th 2026. Data Holders MAY retire v1 of this endpoint from December 7th 2026.26Q411Magellan.14 and Nebula.02
26Q4089-Nov-26AVAILABLEData Holders MUST implement v3 of the Get Transaction Detail endpoint by November 9th 2026. Data Holders MAY retire v2 of this endpoint from December 7th 2026.26Q411Magellan.14 and Nebula.02
26Q4099-Nov-26AVAILABLEData Holders MUST implement v1 of the Get Instalment Plans endpoint for Account by November 9th 2026.26Q412Magellan.14 and Nebula.02
26Q4109-Nov-26AVAILABLEData Holders MUST implement v1 of the Get Instalment Plans Bulk endpoint by November 9th 2026.26Q412Magellan.14 and Nebula.02

Energy Obligations​

Note

There are currently no Data Standards Obligations specific to the Energy Sector.

Β  Β 


Rules Obligations​

Sector Agnostic Obligations​

Note

There are currently no sector agnostic Rules obligations.

Banking Obligations​

ObligationObligation DateReleaseSummary
Non-Bank Lenders (NBL) – Product Data (Initial and Large Providers)13-Jul-26N/ANBLs are required to share product information
Non-Bank Lenders (Initial Providers) – Consumer Data09-Nov-26N/AInitial NBL providers are required to commence supporting consumer data requests (non-complex accounts).
Action for NBLs to determine their classification as an Initial or Large Provider (see details here)
Non-Bank Lenders (Large Providers on/before 13 July 2025) – Consumer Data10-May-27N/ALarge NBL providers are required to commence supporting consumer data requests (non-complex accounts).
Action for NBLs to determine their classification as an Initial or Large Provider (see details here)
Non-Bank Lenders (Large Providers after 13 July 2025) – Product DataQualification + 12 monthsN/AWhere an NBL qualifies as a Large Provider, they must meet product data requirements within 12 months.
Where an NBL qualifies as a Large Provider, they must meet product data requirements within 12 months.
Action for NBLs to determine their classification as an Initial or Large Provider (see details here)
Non-Bank Lenders (Large Providers after 13 July 2025) – Consumer DataQualification + 15 monthsN/AWhere an NBL qualifies as a Large Provider, they must meet non-complex requirements within 12 months.
Action for NBLs to determine their classification as an Initial or Large Provider (see details here).

Energy Obligations​

ObligationObligation DateReleaseSummary
Accredited Small Retailers - non-complex requestsAcc + 12 MonthsN/ASmaller retailers that become accredited must meet non-complex requirements within 12 months of accreditation
Accredited Small Retailers - complex requestsAcc + 18 MonthsN/ASmaller retails that become accredited must meet complex requests requirements within 18 months of accreditation