POST
/BizEntity/Parent
When to Use
- AFSL Compliance: Establish authorized representative hierarchies under dealer groups for Australian Financial Services License compliance
- Fund Families: Create master fund and sub-fund structures with proper parent-child relationships
- Corporate Groups: Define holding company structures with subsidiary relationships for consolidated reporting
- Dealer Networks: Set up dealer group relationships with subsidiary advisers and authorized representatives
- Trust Structures: Implement tiered trust arrangements with master trust and unit trust hierarchies
- Regulatory Reporting: Enable consolidated reporting for ASIC, AUSTRAC, and other regulatory submissions
Prerequisites
- Valid Bearer token with entity relationship management permissions
- Both parent and child BizEntity records must already exist in active status
- DealerGroup BizEntity must exist with valid AFSL credentials (critical for compliance)
- Understanding of Australian financial services regulatory requirements
- Confirmation that the relationship structure complies with relevant ASIC guidelines
- Proper authorization to create hierarchical relationships between the specified entities
Considerations
- Circular Prevention: System prevents circular relationships to maintain hierarchy integrity and avoid infinite loops in reporting
- Regulatory Impact: Relationship affects ASIC reporting, AUSTRAC submissions, and consolidated financial statements
- Date-Based Validity: Active date periods define when the relationship is valid - critical for accurate historical reporting
- AFSL Compliance: Dealer group assignment ensures proper authorized representative hierarchy is maintained
- Relationship Conflicts: System may prevent overlapping parent relationships for the same entity during identical time periods
- Entity Deletion Impact: Deletion of parent entities may require cleanup of all child relationships first
- Audit Trail: All relationship changes are logged for regulatory audit and compliance verification
Description
Creates a new parent-child relationship between two BizEntity records, establishing hierarchical corporate structures. This relationship enables consolidated reporting, fund family management, and dealer group hierarchies within the 7G platform.
Relationship Creation Process
- System validates that both parent and child entities exist
- Checks for circular reference prevention (entity cannot be its own parent)
- Verifies no conflicting active relationships exist for the same period
- Creates the hierarchical relationship with specified date ranges
- Returns the complete relationship record with assigned identifiers
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. Must reference existing active BizEntity. | |
externalBizEntityId |
string | External identifier for child entity. Alternative to bizEntityID. | |
parentBizEntityID |
integer | Native 7G identifier for parent entity. Creates hierarchical relationship for consolidation. | |
parentExternalBizEntityId |
string | External identifier for parent entity. Alternative to parentBizEntityID. | |
dealerGroupBizEntityID |
integer | Native 7G identifier for dealer group managing relationship. Critical for AFSL hierarchy. | |
externalDealerGroupBizEntityId |
string | External identifier for dealer group entity. Links to AFSL holder via external reference. | |
activeFrom |
string (date) | Start date when parent relationship becomes effective. Format: YYYY-MM-DD. | |
activeTo |
string (date) | Optional |
End date when parent relationship expires. Leave null for indefinite relationships. |
BizEntityID
Native 7G identifier for child entity. Must reference existing active BizEntity.
externalBizEntityId
External identifier for child entity. Alternative to bizEntityID.
parentBizEntityID
Native 7G identifier for parent entity. Creates hierarchical relationship for consolidation.
parentExternalBizEntityId
External identifier for parent entity. Alternative to parentBizEntityID.
dealerGroupBizEntityID
Native 7G identifier for dealer group managing relationship. Critical for AFSL hierarchy.
externalDealerGroupBizEntityId
External identifier for dealer group entity. Links to AFSL holder via external reference.
activeFrom
Start date when parent relationship becomes effective. Format: YYYY-MM-DD.
activeTo
End date when parent relationship expires. Leave null for indefinite relationships.
🏢 Australian Financial Services Structure Guidelines
When creating parent-child relationships, ensure compliance with these business patterns:
- AFSL Hierarchy: Dealer group (AFSL holder) → Dealer principal → Authorized representatives
- Fund Families: Master fund as parent, sub-funds as children for consolidated NAV reporting
- Corporate Groups: Holding company as parent, subsidiaries as children for ASIC reporting
- Trust Structures: Master trust as parent, unit trusts as children for tax reporting
- Investment Platforms: Platform operator as parent, investment options as children
⚠️ Critical: The system enforces regulatory compliance by preventing circular relationships and ensuring proper AFSL hierarchy alignment. All relationships must comply with ASIC RG 36 and related guidelines.
Example Requests
json
{
"bizEntityID": 12345,
"parentBizEntityID": 10001,
"dealerGroupBizEntityID": 20001,
"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": 20001,
"externalDealerGroupBizEntityId": "AFSL-123456",
"activeFrom": "2024-01-01",
"activeTo": null
}
}