DELETE
/BizEntity/Parent
When to Use
- Fund Independence: Dissolve fund family structures when sub-funds become independent entities
- Corporate Demergers: Remove parent-child relationships after business separation or spin-offs
- AFSL Termination: End dealer group oversight when entities move to different licensed dealers
- Entity Dissolution: Clean up relationships when subsidiary entities are dissolved or wound up
- Compliance Corrections: Remove incorrect relationship assignments identified during ASIC audits
- Regulatory Restructuring: Terminate relationships that no longer comply with current regulations
Common Scenarios
- Fund Family Restructuring: Remove sub-fund relationships when funds become independent or change management
- Corporate Spin-offs: Dissolve parent-child connections after business demergers or subsidiary sales
- Dealer Group Changes: End oversight relationships when advisers move between licensed dealers
- Entity Closure Dependencies: Remove parent relationships before dissolving subsidiary entities
Prerequisites
- Valid Bearer token with entity relationship deletion permissions
- Existing parent-child relationship must be established in the system
- No dependent child relationships exist under the entities being disconnected
- No active transactions, distributions, or reporting processes rely on the relationship
- Legal authorization to dissolve the corporate or fund structure
- Confirmation that ASIC notification requirements have been met (where applicable)
Considerations
- Permanent Deletion: Removal is irreversible and requires recreation if relationship is needed again
- Regulatory Impact: Affects consolidated reporting, ASIC submissions, and compliance structures immediately
- Dependency Validation: System prevents deletion if dependent relationships or active processes exist
- Audit Compliance: Deletion creates permanent audit trail for regulatory review and compliance verification
- Entity Preservation: Only the relationship is removed - underlying BizEntity records remain intact
- Reporting Continuity: Ensure alternative reporting structures are in place before deletion
- Transaction Impact: Verify no pending transactions depend on the parent-child relationship
Description
Permanently removes a parent-child relationship between BizEntity records, enabling corporate restructuring, fund independence, and compliance corrections. This endpoint dissolves hierarchical structures while preserving underlying entities and maintaining regulatory audit trails.
🗑️ Australian Financial Services Deletion Process
- Relationship Identification: System locates the specific parent-child relationship using entity identifiers
- Dependency Validation: Validates that no dependent child relationships exist in the hierarchy
- Business Process Check: Verifies no active transactions, distributions, or consolidated reporting depend on the relationship
- Regulatory Compliance: Ensures deletion complies with ASIC requirements and doesn't violate regulatory structures
- Audit Trail Creation: Logs the deletion permanently for compliance verification and regulatory review
- Atomic Removal: Permanently removes the relationship record while preserving all underlying BizEntity records
Required Headers - See Authentication
| Header | Value | Description |
|---|---|---|
| Authorization | {accessToken} | Bearer token for API access |
| Version | 2.0 | API version identifier |
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
BizEntityID |
integer | Native 7G identifier for child entity in relationship deletion. Fastest deletion path using primary index. | |
ParentBizEntityID |
integer | Native 7G identifier for parent entity in relationship deletion. Optimal performance with native IDs. | |
ExternalBizEntityId |
string | External identifier for child entity. Enables relationship deletion via external references. | |
ExternalParentBizEntityId |
string | External identifier for parent entity. Supports dual-ID relationship dissolution. |
BizEntityID
Native 7G identifier for child entity in relationship deletion. Fastest deletion path using primary index.
ParentBizEntityID
Native 7G identifier for parent entity in relationship deletion. Optimal performance with native IDs.
ExternalBizEntityId
External identifier for child entity. Enables relationship deletion via external references.
ExternalParentBizEntityId
External identifier for parent entity. Supports dual-ID relationship dissolution.
🔗 Relationship Identification for Deletion
DELETE operations require precise identification of the parent-child relationship:
- Dual Identification: Both child and parent entity identifiers must be provided to uniquely identify the relationship
- ID Flexibility: Use native 7G IDs (BizEntityID, ParentBizEntityID) or your external IDs interchangeably
- Mixed ID Support: Can combine native ID for one entity with external ID for the other
- Precision Required: Wrong combination will result in 404 Not Found - relationship must exist exactly as specified
⚠️ Critical: Deletion is permanent and irreversible. Ensure the correct relationship is identified before proceeding. The system will validate dependencies and prevent deletion if business rules are violated.
Example Requests
json
# Dissolve fund family - sub-fund becomes independent
curl -X DELETE "https://api.7g.com.au/BizEntity/Parent?BizEntityID=12345&ParentBizEntityID=10001" \
-H "Authorization: {accessToken}" \
-H "Version: 2.0"Response Examples
json
{
"result": true,
"message": null,
"recordCount": 0,
"data": null
}