Disclosure document and client agreement
Field and workflow control page for PM/client.
Portfolio ManagersPM/client
Finin2min Summary — in 2 Minutes
Disclosure document and client agreement under the Portfolio Managers framework. Strategy, risk, fee, custody and termination.
Official source and legal ownership
Paragraph-wise Finin2min interpretation
Purpose
Strategy, risk, fee, custody and termination
Owner
PM/client
Validation
Check current regulation/master circular/exchange format, field taxonomy, signatory and filing channel.
Evidence
Approved source data, signed/XBRL filing, acknowledgement, error report, correction and retained version.
Practical example
The preparer builds the filing from controlled source systems, obtains required approvals, validates totals and cross-references, files through the prescribed channel and retains the acknowledgement plus any correction trail.
Implementation and evidence controls
- Freeze the applicable entity class, product, transaction date and official instrument version.
- Map every control to its legal owner, enabling provision, responsible function, evidence and escalation route.
- Retain Board/committee approval, policy version, system configuration, maker-checker evidence, exception approval and regulatory filing acknowledgement.
- Re-test the control after an amendment, product change, outsourcing change, merger, customer-risk reclassification or supervisory observation.
Practical Q&A
Can an old template be reused?
Only after comparing the current regulator/exchange format and amendment date.
Who should sign?
The exact Regulation/circular/form determines the authorised signatory; document delegated authority.
What should be retained?
Source data, workings, approvals, filed version, acknowledgement, validation errors and resubmission.