PUT
/BizEntity/Parent
When to Use
- Relationship Extensions: Extend activeTo dates for ongoing fund family or corporate structures
- Early Termination: Set activeTo dates to end relationships due to corporate restructuring or demergers
- AFSL Reassignment: Transfer dealer group oversight to different licensed entities during acquisitions
- Hierarchy Restructuring: Change parent entities following mergers, spin-offs, or organizational changes
- Compliance Corrections: Fix incorrect relationship assignments discovered during audits
- Date Corrections: Adjust activeFrom dates to match legal effective dates or regulatory approvals
Prerequisites
- Valid Bearer token with entity relationship management permissions
- Existing parent-child relationship must be established (cannot create new relationships)
- All referenced entities (child, parent, dealer group) must exist and be active
- Authorization to modify corporate structures and regulatory relationships
- Understanding of ASIC compliance implications for relationship changes
- Confirmation that changes align with corporate legal documentation
Considerations
- Reporting Impact: Changes affect consolidated financial reporting and regulatory submissions to ASIC/AUSTRAC
- Audit Trail: All modifications create permanent audit records for compliance verification
- Active Relationship Rules: Cannot modify date ranges that would invalidate existing transactions or distributions
- Circular Prevention: System validates against circular relationships when changing parent entities
- AFSL Compliance: Dealer group changes must maintain proper authorized representative hierarchy
- Timing Coordination: Date modifications should align with accounting periods and regulatory reporting cycles
- Business Continuity: Changes during active trading periods may require stakeholder notification
Description
Updates an existing parent-child relationship between BizEntity records, enabling modifications to relationship parameters while maintaining regulatory compliance and hierarchy integrity. This endpoint is essential for corporate restructuring, AFSL transfers, and relationship lifecycle management.
🔍 Relationship Update Process
- Relationship Identification: System locates existing relationship using child/parent entity identifiers
- Business Rule Validation: Validates all new parameters against ASIC compliance requirements
- Circular Reference Prevention: Checks for circular relationships when parent entities are modified
- Transaction Impact Assessment: Verifies that date changes won't invalidate existing transactions
- Atomic Update: Updates relationship record with all new values in a single transaction
- Audit Trail Creation: Logs all changes for regulatory compliance and historical tracking
Required Headers - See Authentication
| Header | Value | Description |
|---|---|---|
| Authorization | {accessToken} | Bearer token for API access |
| Version | 2.0 | API version identifier |
| Content-Type | application/json | Content 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
Native 7G identifier for child entity in relationship update. Must match existing relationship.
externalBizEntityId
External identifier for child entity. Alternative to bizEntityID for updates.
parentBizEntityID
Native 7G identifier for new parent entity. Updates hierarchical relationship.
parentExternalBizEntityId
External identifier for new parent entity. Alternative to parentBizEntityID.
dealerGroupBizEntityID
Updated dealer group identifier. Changes AFSL hierarchy assignment.
externalDealerGroupBizEntityId
External identifier for updated dealer group entity.
activeFrom
Updated start date for parent relationship. Format: YYYY-MM-DD.
activeTo
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"
}
}