PUT
/BizEntity/Parent
Usage Notes
When
- Extend or terminate relationship date ranges
- Change parent entity following corporate restructuring
- Update dealer group assignments
Requirements
- Existing parent-child relationship must already be established
- Complete DTO required (retrieve current data first)
Notes
- PUT replaces entire relationship - include all fields to retain
- System validates against circular relationships when changing parents
- Cannot modify date ranges that would invalidate existing transactions
Description
Updates an existing parent-child relationship by complete replacement. Enables modifications for corporate restructuring and date range adjustments.
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
bash
# Extend relationship end date
curl -X PUT 'https://api.7g.com.au/BizEntity/Parent' \
-H 'Authorization: {accessToken}' \
-H 'Version: 2.0' \
-H 'Content-Type: application/json' \
-d '{
"bizEntityID": 12345,
"parentBizEntityID": 10001,
"dealerGroupBizEntityID": 20001,
"activeFrom": "2024-01-01",
"activeTo": "2026-12-31"
}'
# Change dealer group using external IDs
curl -X PUT 'https://api.7g.com.au/BizEntity/Parent' \
-H 'Authorization: {accessToken}' \
-H 'Version: 2.0' \
-H 'Content-Type: application/json' \
-d '{
"externalBizEntityId": "SUB-FUND-001",
"parentExternalBizEntityId": "MASTER-FUND-001",
"externalDealerGroupBizEntityId": "NEW-AFSL-HOLDER",
"activeFrom": "2024-01-01",
"activeTo": null
}'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"
}
}