Independent Singapore VCC guidance
Direct answer
Resolve an OTC derivative confirmation break by freezing the original instruction and execution evidence, identifying the correct VCC and sub-fund, and comparing the dealer ticket, counterparty confirmation, governing agreement, portfolio system and administrator books field by field. Classify whether the break affects legal terms, economics, ownership, valuation, collateral or reporting. Issue one controlled correction path, contain every downstream use of disputed data, and close only when both sides agree and all affected records reconcile.
At a glance
- Preserve the executed trade and dispute chronology before correcting any system.
- Confirm the contracting VCC and sub-fund before comparing economic fields.
- Separate legal-document, trade-economic, allocation and static-data breaks.
- Contain valuation, collateral, cash and reporting outputs that use disputed data.
- Close the case through matched evidence and downstream reconciliation, not email agreement alone.
Who this is for
- VCC managers, fund administrators, operations teams and directors overseeing OTC derivatives booked to a standalone VCC or an umbrella sub-fund.
Important exclusions
- Legal interpretation of a master agreement, confirmation or collateral document, or a recommendation that a particular VCC may use a derivative.
Fix the trade identity and sub-fund owner
Before debating economics, establish what transaction is being reviewed. Capture the dealer instruction, execution message, booking identifier, counterparty identifier, trade date, product, currency pair or reference asset, and the exact legal entity. For an umbrella VCC, identify the sub-fund whose assets and liabilities should bear the trade. A confirmation addressed only to the umbrella name can still leave an operational ownership problem if the sub-fund is missing or wrong. Stop automated downstream updates that would spread uncertain ownership into books, collateral or investor reporting.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- Preserve the original portfolio instruction, trader record, execution message and counterparty communication before any rebooking occurs.
- Confirm the contracting VCC name, registration identity, counterparty account and exact sub-fund allocation expected by the mandate.
- Identify every system and provider that consumed the trade, including portfolio, risk, administrator, valuation, collateral and accounting records.
- Mark disputed fields so users can distinguish confirmed economics from values that remain under investigation.
- Assign one exception owner and one authorised communication channel to prevent competing corrections reaching the counterparty.
Compare the records field by field
Build one comparison rather than circulating several annotated confirmations. Use the executed evidence as the starting point, then compare the counterparty draft, governing agreement and each internal booking. Key fields depend on the product but commonly include parties, direction, notional, currency, price or rate, effective and maturity terms, underlying reference, reset or payment conventions, settlement instructions, business-day treatment and termination provisions. The governing agreement provides the documentation context, while the execution record shows what was agreed. Neither should be silently rewritten to match a downstream booking.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of Singapore| Record | What it proves | Typical break | Control response |
|---|---|---|---|
| Portfolio instruction | Authorised strategy, size and sub-fund | Trade exceeds or differs from the instruction | Escalate mandate or approval issue separately |
| Execution evidence | Terms agreed when the trade was done | Voice, message and dealer ticket disagree | Reconstruct chronology and obtain dealer challenge |
| Counterparty confirmation | Counterparty’s proposed legal record | Direction, date, rate or entity differs | Issue a precise written dispute with supporting evidence |
| Governing agreement | Documentation and convention framework | Confirmation uses an unsupported template or election | Refer to authorised legal and documentation review |
| Books and systems | How economics flow into valuation and accounting | Static data or mapping changes the result | Correct through controlled entries and reconcile outputs |
Classify the break before choosing the remedy
A single discrepancy can have different consequences, so label the break precisely. A legal-entity or sub-fund error changes who appears to own the position. An economic error changes cash flows or exposure. A convention or static-data error can distort valuation even when the trade terms are otherwise agreed. A document-only error may not change economics but can weaken enforceability or evidence. An allocation error can create cross-sub-fund accounting and investor-reporting problems. The remedy, approval and downstream containment should follow the classification instead of using a generic cancel-and-rebook response.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- Entity or sub-fund breakStop downstream ownership use, confirm authority and obtain legal or documentation input before correcting the affected records.
- Economic-term breakReconstruct agreed terms, quantify affected cash flows and exposures, then issue a supported dispute to the counterparty.
- Convention or static-data breakCorrect the approved data source and rerun valuation, collateral and accounting outputs that depended on it.
- Evidence-only breakRepair the confirmation record without changing agreed economics, and preserve why no financial correction was needed.
- Authority or mandate breakEscalate outside ordinary operations because confirmation matching cannot cure an unauthorised or out-of-mandate trade.
Related guidance: failed-trade settlement workflow · VCC trading-error classification and correction
Work the exception across downstream processes
Consider a hypothetical umbrella VCC where the manager executes an interest-rate swap for its private-credit sub-fund. The dealer ticket and execution message show that the sub-fund receives fixed and pays floating, but the counterparty draft reverses the direction and omits the sub-fund reference. The administrator booked the dealer ticket correctly, while the collateral agent imported the draft. Operations should dispute both fields, flag the collateral calculation, prevent an unsupported margin instruction, preserve the correct administrator booking and obtain an agreed confirmation before releasing normal processing.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority- ContainFlag the confirmation, collateral output and affected reports while preserving the original execution and correct internal booking.
- ReconstructAlign dealer, counterparty and operations evidence to show the agreed direction and intended sub-fund owner.
- DisputeSend one field-specific challenge with supporting evidence through the authorised counterparty communication route.
- CorrectObtain the matched confirmation and repair only the systems or records that contain the verified error.
- ReconcileRerun valuation, collateral, cash, accounting and exposure outputs and retain evidence that they now agree.
Related guidance: sub-fund margin-call control workflow
Close with matched evidence and root-cause action
Closure requires more than a corrected PDF. Retain the final matched confirmation, counterparty acceptance, authorised internal correction, downstream reconciliations and impact assessment. Record whether the issue caused incorrect exposure, valuation, collateral, cash, accounting, limit monitoring or investor reporting, even if the final financial impact is nil. Then identify the control cause: template mapping, wrong account, manual entry, unclear instruction, interface defect or provider handoff. Test a later population after the fix, and report repeated or material breaks through the appropriate VCC and manager oversight route.
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Monetary Authority of SingaporeRelated guidance: custody position reconciliation
Frequently asked questions
What is an OTC derivative confirmation break?
It is a disagreement or mismatch between the trade understood by the parties and one or more records intended to evidence or process it. The break may concern the legal entity, sub-fund, direction, economics, dates, conventions, settlement details or documentation, and each type can affect different downstream controls.
Does the counterparty confirmation always control the answer?
No single record should be assumed to answer every dispute. Operations should reconstruct the agreement using the authorised instruction, execution evidence, governing documentation and counterparty communication. The confirmation is an important legal record, but a draft containing an error should be challenged rather than copied into internal books.
Why does the sub-fund name matter for an umbrella VCC trade?
The sub-fund determines which pool should bear the position, cash flows, valuation, collateral and investor impact. A confirmation that identifies only the umbrella or names the wrong sub-fund can create ownership, accounting and operational ambiguity even if the economic terms are otherwise correct.
When should valuation or collateral processing be held?
Contain outputs that depend on a genuinely disputed field, especially direction, notional, rate, dates, currency, entity, sub-fund or valuation convention. The hold should be specific, authorised and visible to affected providers. Preserve correct data where it is supported rather than deleting the whole trade from every system.
What evidence closes a confirmation exception?
Keep the final agreed confirmation, counterparty acceptance, approved correction record, impact assessment and reconciliations for valuation, collateral, cash, accounting and exposure where relevant. Add the root cause, corrective action, accountable owner and later test result so the case demonstrates both trade repair and control improvement.
Official sources and further reading
- Risk Management Practices for Fund Management Companies (Monetary Authority of Singapore)
- Notice SFA 04-N16 on Execution of Customers’ Orders (Monetary Authority of Singapore)
- Guidelines to Notice SFA 04-N16 on Execution of Customers’ Orders (Monetary Authority of Singapore)
- Code on Collective Investment Schemes, revised 2 July 2026 (Monetary Authority of Singapore)
- Understanding VCC Features, Eligibility and Requirements (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.