PUT

/BizEntity/Parent

When to Use

  • Extend or terminate relationship date ranges (activeFromDate, activeToDate)
  • Change parent entity following corporate restructuring
  • Correct incorrect relationship assignments

Prerequisites

  • Existing parent-child relationship must already be established

Considerations

  • System validates against circular relationships when changing parent entities
  • Cannot modify date ranges that would invalidate existing transactions
  • All modifications create audit records

Description

Updates an existing parent-child relationship, enabling modifications to relationship parameters for corporate restructuring and date range adjustments.

Required Headers - See Authentication

HeaderValueDescription
Authorization{accessToken}Bearer token for API access
Version2.0API version identifier
Content-Typeapplication/jsonContent type for request body

Request Body

Parameter Type Required Description
BizEntityID >
integer
Native 7G identifier for child entity in relationship update. Must match existing relationship.
externalBizEntityId >
string
External identifier for child entity. Alternative to bizEntityID for updates.
parentBizEntityID >
integer
Native 7G identifier for new parent entity. Updates hierarchical relationship.
parentExternalBizEntityId >
string
External identifier for new parent entity. Alternative to parentBizEntityID.
dealerGroupBizEntityID >
integer
Updated dealer group identifier. Changes AFSL hierarchy assignment.
externalDealerGroupBizEntityId >
string
External identifier for updated dealer group entity.
activeFrom >
string (date)
Updated start date for parent relationship. Format: YYYY-MM-DD.
activeTo
string (date)
Optional
Updated end date for relationship. Set to null to remove expiration.
BizEntityID
integer
Native 7G identifier for child entity in relationship update. Must match existing relationship.
externalBizEntityId
string
External identifier for child entity. Alternative to bizEntityID for updates.
parentBizEntityID
integer
Native 7G identifier for new parent entity. Updates hierarchical relationship.
parentExternalBizEntityId
string
External identifier for new parent entity. Alternative to parentBizEntityID.
dealerGroupBizEntityID
integer
Updated dealer group identifier. Changes AFSL hierarchy assignment.
externalDealerGroupBizEntityId
string
External identifier for updated dealer group entity.
activeFrom
string (date)
Updated start date for parent relationship. Format: YYYY-MM-DD.
activeTo
string (date)
Optional
Updated end date for relationship. Set to null to remove expiration.

🔄 Australian Financial Services Update Guidelines

When updating parent-child relationships, ensure regulatory compliance with these update patterns:

  • Date Extensions: Extend activeTo dates for ongoing fund families or corporate structures
  • Early Termination: Set activeTo dates to end relationships due to demergers or restructuring
  • AFSL Reassignment: Transfer dealer group oversight during license transfers or acquisitions
  • Hierarchy Changes: Reassign parent entities following mergers or spin-offs
  • Compliance Corrections: Fix relationship errors identified during ASIC audits
⚠️ Critical: All relationship updates create permanent audit trails and must comply with ASIC RG 36 requirements. Date modifications cannot invalidate existing transactions or distributions.

Example Requests

json
{
  "bizEntityID": 12345,
  "parentBizEntityID": 10001,
  "dealerGroupBizEntityID": 20001,
  "activeFrom": "2024-01-01",
  "activeTo": "2026-12-31"
}

Response Examples

json
{
  "result": true,
  "message": null,
  "recordCount": 1,
  "data": {
    "bizEntityID": 12345,
    "externalBizEntityId": "SUB-FUND-001",
    "parentBizEntityID": 10001,
    "parentExternalBizEntityId": "MASTER-FUND-001",
    "dealerGroupBizEntityID": 20002,
    "externalDealerGroupBizEntityId": "NEW-AFSL-HOLDER",
    "activeFrom": "2024-01-01",
    "activeTo": "2026-12-31"
  }
}