Independent Singapore VCC guidance
Direct answer
Control VCC market-data use by translating each contract into an entitlement map: data set, permitted user, legal entity, sub-fund, system, location, purpose, derived output and redistribution rule. Reconcile that map to actual feeds, accounts, reports and provider access. Treat shared umbrella infrastructure as a technical fact, not automatic permission to reuse data across sub-funds. Investigate mismatches, restrict excess access, and retain evidence of correction and end-of-use deletion.
At a glance
- A paid feed does not automatically permit every user, system, output or sub-fund use.
- Map raw, delayed, reference and derived data separately because their rights may differ.
- Include administrators, delegates, recovery systems and downloaded files in the entitlement population.
- Reconcile contracts to actual technology and reports at onboarding, change and termination.
Who this is for
- Pricing, reference, index, benchmark, corporate-action and other licensed data used by a VCC or its providers.
Important exclusions
- A legal interpretation of a specific vendor contract; obtain advice where licence language or rights are disputed.
Translate contract terms into data objects
List each feed, field set, index, benchmark, identifier, document and file obtained from the vendor. Record whether it is real time, delayed, end of day, reference or calculated. Then capture the contracting party, covered affiliates, named users, applications, sites, devices, storage and permitted purposes. Do not reduce the contract to a single licence count. The operational question is whether a specific data object may move through a specific route to a specific person or output. Where language is ambiguous, mark it for legal or vendor clarification instead of letting a convenient technical design become the assumed right.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority| Field | Record | Why it matters |
|---|---|---|
| Data object | Feed, field, index, document or derived value | Different objects may carry different rights |
| User and entity | Named person, team, provider, VCC and sub-fund | Shared operations do not prove shared permission |
| System and location | Application, storage, device and recovery copy | Technical replication can expand use |
| Output | NAV, report, model, display or onward file | Distribution and display rights may differ |
Related guidance: VCC pricing and market-data provider review
Map the umbrella and sub-fund boundary
An umbrella VCC may use common technology and providers while its sub-funds pursue different strategies and produce separate records. Map which sub-fund needs each data set, who bears the cost and which outputs cross the boundary. A shared terminal used by one operations team may be permitted differently from a feed replicated into several valuation engines. Likewise, a benchmark approved for one portfolio should not silently become available for unrelated investor reports. Connect the licence map to expense allocation and provider scope so entitlement, operational use and charging follow the same population.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory AuthoritySub-fund boundary checks
- Each data use is linked to a named VCC, sub-fund, strategy, process and accountable owner.
- Shared systems expose only the feeds and functions needed for each approved sub-fund use.
- Reports and dashboards do not reveal licensed data to unrelated investors, providers or sub-funds.
- Licence charges and shared infrastructure costs use an approved allocation basis that matches actual benefit.
- New sub-funds and strategies trigger entitlement review before copying an existing feed or configuration.
Control derived data and redistribution
Identify outputs that transform vendor data: calculated prices, risk measures, performance series, index-relative returns, classifications and investor-report tables. Record the inputs, transformation, refresh frequency, users and recipients. Do not assume that changing a format or combining fields removes contractual restrictions. Separate internal decision use from display, external reporting and machine-to-machine redistribution. Where an administrator or risk provider receives the output, confirm whether it acts as a service provider to the licensed entity or becomes another recipient. Keep approved examples so report developers know what can be shown without exposing raw or reconstructable data.
Sources: Monetary Authority of Singapore · Monetary Authority of SingaporeOutput decision
- Internal calculation onlyConfirm the covered entity, user and application, then restrict export and retain the transformation record.
- Investor-facing displayCheck display, attribution, delay and recipient terms before approving the report or portal output.
- Provider handoffConfirm service-provider status, purpose, access, retention and onward-use restrictions before transfer.
- Unclear derived rightHold release, ask the vendor or obtain advice, and document the approved interpretation before reuse.
Related guidance: VCC report data lineage from source to sign-off · portfolio risk model validation for a VCC
Reconcile the entitlement population
Build the actual population from vendor accounts, identity systems, feed configurations, application inventories, cloud storage, shared drives, recovery environments and provider connections. Compare it with the approved entitlement map. Investigate orphaned users, generic accounts, feeds enabled for unused modules, copies retained outside approved locations and reports sent to broader groups than intended. Review privileged and bulk-download rights separately. Use evidence from the systems rather than relying solely on manager attestations. Every excess right should have a removal record or a bounded exception with an owner, safeguard and expiry.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory AuthorityReconciliation cycle
- ExtractCollect current accounts, feeds, systems, storage locations, provider connections and report recipients from live sources.
- MatchCompare each actual use with the approved data object, entity, sub-fund, purpose and output right.
- ChallengeInvestigate generic access, unused modules, broad exports, recovery copies and unexplained provider entitlements.
- CorrectRemove excess rights, update configurations and preserve the ticket or system evidence proving completion.
- CertifyHave accountable owners confirm the remaining population and record every time-bounded exception.
Control change, renewal and termination
Trigger review when a sub-fund launches, strategy changes, provider joins, report expands, system migrates, vendor terms change or data use ends. Before renewal, compare contracted rights, invoices and actual populations so unused rights can be removed and unlicensed growth is not carried forward. At termination, disable accounts and feeds, revoke provider access, identify retained raw and derived copies, apply contractual return or deletion steps, and preserve evidence. If data must remain in books or reports, document the permitted retained form and access route rather than keeping a live feed indefinitely. Feed recurring exceptions into procurement, architecture and access design.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeRelated guidance: new investment instrument approval for a VCC mandate
Frequently asked questions
Can every sub-fund use a feed bought by the umbrella VCC?
Not automatically. Check the contracting entity, covered funds, applications, users, purposes and redistribution terms. Shared infrastructure does not by itself establish that every sub-fund or strategy has the same licensed right.
Does a calculated value stop being vendor data?
That depends on the contract and transformation. Record the inputs and output, then assess whether recipients could reconstruct or receive restricted content. Do not assume that a formula, new label or delayed display removes restrictions.
Should fund administrators appear in the entitlement map?
Yes. Include every provider user, service account, interface and storage location that receives or can access the data. Confirm purpose, retention, onward use and removal when the provider role changes or ends.
How often should market-data access be reconciled?
Use a risk-based cycle and event triggers. New sub-funds, system migrations, provider changes, report expansions, contract renewals and terminations should prompt review even when the regular recertification date has not arrived.
What evidence supports licence closure?
Keep account and feed disablement, provider access removal, data-return or deletion evidence, retained-copy decisions and a final comparison against the entitlement map. An expired invoice alone does not prove that access or copies ended.
Official sources and further reading
- Risk Management Practices for Fund Management Companies (Monetary Authority of Singapore)
- Technology Risk Management Guidelines (Monetary Authority of Singapore)
- Governance and Management of Variable Capital Companies (Monetary Authority of Singapore)
- Legal Obligations of a VCC Director (Accounting and Corporate Regulatory Authority)
- Overview of Managing a Variable Capital Company (Accounting and Corporate Regulatory Authority)
Discuss a Singapore VCC structure
For help coordinating a Singapore VCC setup or corporate administration, contact Raffles Corporate Services.
General information only. This article is not legal, tax, regulatory or investment advice and does not imply affiliation with or endorsement by ACRA, MAS or IRAS.