POST
/BizEntity/Parent
Usage Notes
When
- Create parent-child relationships for fund families or corporate groups
- Establish dealer group relationships for consolidated reporting
- Link master funds with sub-funds for hierarchical structures
Requirements
- Both parent and child entities must already exist
- ActiveFrom date required to define relationship effective date
Notes
- System prevents circular relationships (entity cannot be its own parent)
- Date ranges define relationship validity period
- Deleting parent entities may require removing child relationships first
Description
Creates a parent-child relationship between two entities for hierarchical corporate structures and consolidated reporting. Returns complete relationship with system-assigned references.
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
bash
# Create fund family relationship using native IDs
curl -X POST '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": null
}'
# Create relationship using external IDs
curl -X POST '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": "DEALER-GRP-AFSL123",
"activeFrom": "2024-07-01",
"activeTo": "2024-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": 20001,
"externalDealerGroupBizEntityId": "AFSL-123456",
"activeFrom": "2024-01-01",
"activeTo": null
}
}