Independent Singapore VCC guidance

By Variable Capital Companies Actworked scenario

Direct answer

Reconcile custody positions by comparing independently obtained custody evidence with the administrator ledger for the same VCC or sub-fund, valuation point and security population. Normalise identifiers without erasing the original records, classify every difference by cause and economic effect, and assign a named owner. A position break closes only after the supported correction appears in custody or the fund books, related cash and valuation effects are checked, and the final control totals agree.

At a glance

  • Fix scope, entity, account and valuation time before comparing quantities.
  • Preserve original identifiers while maintaining a controlled translation map.
  • Separate true economic breaks from timing and presentation differences.
  • Assess cash, income, valuation and investor effects alongside the position.
  • Require evidence of the correcting entry before marking a break closed.

Who this is for

  • Controllers, managers, operations teams and directors reviewing custodied assets of a standalone or umbrella VCC.

Important exclusions

  • A substitute for custody terms, fund accounting policies, valuation rules, audit procedures or advice on legal ownership.

Define comparable reconciliation populations

A reconciliation fails before it starts if the sources describe different populations. Record the VCC or sub-fund, custody account, administrator book, statement type, valuation point, base and local currencies, and included asset types. Obtain custody evidence through an appropriately controlled route instead of relying only on a file forwarded by the administrator. Preserve the source timestamp and completeness indicators. Independent custody and credible manager oversight are central to the current governance focus for VCCs.

Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority
Population alignment record
DimensionCustody sideFund-book sideControl response
EntityAccount legal name and numberVCC or sub-fund ledgerResolve mapping before quantity comparison
TimeStatement or file timestampNAV or accounting cut-offIdentify unsettled and late-posted activity
ScopeCustodied and non-custodied assetsFull investment ledgerSeparate expected scope differences
Quantity basisSettled, trade-date or available unitsAccounting quantity conventionCompare like with like
CurrencyLocal and settlement currenciesBook and reporting currenciesKeep quantity and value tests distinct
Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Inland Revenue Authority of Singapore

Maintain control totals for record count and aggregate quantities where meaningful, but do not let a net total hide offsetting errors. Two sub-funds can each be wrong while the umbrella total agrees. Similarly, one security may show an equal and opposite difference across accounts. Reconcile at the lowest level that matches legal ownership and accounting attribution, then roll upward. For assets outside conventional custody, state the alternative ownership evidence and review route rather than inserting them into an unrelated custody population.

Sources: Accounting and Corporate Regulatory Authority · Monetary Authority of Singapore · Inland Revenue Authority of Singapore

Normalise identifiers without losing lineage

Create a controlled security and account map containing each source identifier, the chosen reconciliation key, effective dates and approval for changes. A security can appear under an international identifier, local code, internal administrator code or custodian code. Normalisation is necessary, but it should not overwrite the raw source. Keep corporate-action changes, maturities, reorganisations and share-class conversions visible because an apparently stale code may explain a genuine timing difference or an incomplete booking.

Sources: Monetary Authority of Singapore · Monetary Authority of Singapore · Inland Revenue Authority of Singapore
  • Preserve the raw custodian and administrator identifiers beside the normalised key.
  • Map custody accounts to the correct VCC and sub-fund with an effective-date history.
  • Separate security quantity, nominal amount, units and face-value conventions.
  • Identify positions intentionally outside custody and the alternative evidence owner.
  • Review manual mappings, one-to-many links and recently changed identifiers independently.
Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority · Inland Revenue Authority of Singapore

Changes to the map should be controlled like changes to a calculation model. Record the reason, source evidence, affected periods and reviewer. If a one-to-many relationship exists after a reorganisation, do not force both sources onto a single code until the economic conversion is understood. The goal is a reproducible bridge, not a cleaner-looking report. A reviewer should be able to move from the reconciliation line back to both original records without using personal memory.

Sources: Inland Revenue Authority of Singapore · Monetary Authority of Singapore

Work through a position-break scenario

Consider a hypothetical umbrella VCC where the custodian shows a listed holding in one sub-fund, while the administrator ledger shows the same total split between two pools. The umbrella quantity agrees, so a high-level check would pass. The sub-fund records do not. The controller should preserve both files, compare trade and transfer instructions, trace the account map, and isolate whether the break arose in custody booking, administrator allocation or reference data. Until ownership is supported, valuation and dealing outputs for both pools need an explicit impact decision.

Sources: Accounting and Corporate Regulatory Authority · Monetary Authority of Singapore · Monetary Authority of Singapore
  1. ContainFlag both affected sub-funds and prevent the umbrella total from masking the attribution difference.
  2. TraceCompare original trade, transfer, custody and administrator records using preserved source identifiers.
  3. ClassifyDetermine whether the cause is timing, booking, allocation, identifier mapping or unresolved ownership.
  4. AssessMeasure effects on valuation, cash, income, fees, investor dealing and financial reporting outputs.
  5. CorrectPost the supported entry in the responsible system and re-run linked reconciliations before closure.
Sources: Monetary Authority of Singapore · Inland Revenue Authority of Singapore · Accounting and Corporate Regulatory Authority

The scenario shows why break resolution and break closure are different. An administrator explanation can identify the likely cause, but closure needs evidence that the relevant source changed or that a supported timing item subsequently matched. If the custodian corrects the account, retain the revised statement and provider reference. If the administrator corrects the books, trace the journal into positions, cash, income and NAV. Do not close on a promise that the item will reverse in the next period.

Sources: Monetary Authority of Singapore · Inland Revenue Authority of Singapore

Classify impact and assign the right owner

Use a break taxonomy that distinguishes source incompleteness, unsettled activity, failed settlement, corporate action, identifier mismatch, wrong account, wrong sub-fund, quantity error, stale position and unsupported manual adjustment. Then assess economic impact separately. A timing break may still affect a published NAV if the accounting cut-off was applied incorrectly. A zero-value position can still affect ownership records or future income. Assign the owner that can change the responsible record and a reviewer who can test the result.

Sources: Monetary Authority of Singapore · Inland Revenue Authority of Singapore · Monetary Authority of Singapore
Break classification and release decision
Break classPrimary evidencePotential effectClosure evidence
TimingTrade and settlement statusQuantity or cash at the cut-offSubsequent matched records
Wrong accountCustody instruction and account mapSub-fund ownership and reportingCorrected custody statement
Book errorAdministrator journal and source tradeNAV, income, fees or reportingApproved journal and rerun outputs
Identifier mismatchSecurity master and event historyFalse or duplicated breakReviewed mapping with lineage
Unresolved ownershipContract, instruction and custody evidenceLegal, valuation and investor effectsAuthorised conclusion and corrected records
Sources: Monetary Authority of Singapore · Inland Revenue Authority of Singapore · Accounting and Corporate Regulatory Authority

Define what stops the NAV or another output before the close begins. The decision should consider magnitude, affected investors, possibility of offsetting errors, liquidity, reporting and whether ownership is uncertain. Avoid treating every break as equal or using a fixed amount without context. Record the decision, authority, affected outputs and any condition. If a break is held open across a reporting date, show it transparently in the control record and include it in the next review population.

Sources: Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority · Inland Revenue Authority of Singapore

Prove closure and monitor recurring causes

A complete file contains the two source populations, account and identifier maps, comparison output, break classification, investigation evidence, impact assessment, decision, correction and rerun. Retain who prepared and reviewed each stage. Records should support financial statements and tax work without requiring an undocumented spreadsheet transformation. Where the reconciliation depends on a provider, preserve service tickets and response evidence, but keep the VCC or manager conclusion separate from the provider description.

Sources: Inland Revenue Authority of Singapore · Monetary Authority of Singapore · Accounting and Corporate Regulatory Authority
  • Confirm the corrected custody and administrator quantities agree at the same valuation point.
  • Reconcile related cash, income, expenses, valuation and investor outputs after the correction.
  • Verify the fix was applied to the correct VCC, sub-fund, account and reporting period.
  • Record the root cause, responsible system, owner and preventive action with an evidence date.
  • Trend reopened, aged, repeated and post-release breaks for provider and process review.
Sources: Monetary Authority of Singapore · Inland Revenue Authority of Singapore · Accounting and Corporate Regulatory Authority

Frequently asked questions

Should the manager obtain custody data independently?

The control should avoid relying only on the producer of the fund books for the comparison source. The practical route depends on the custody model and access arrangements, but the reviewer should authenticate the custody evidence, retain its timestamp and understand any transformation. If the administrator delivers both sides, add controls that prove the custody file is complete and unchanged.

Can the umbrella VCC reconcile only at total level?

No high-level total can prove correct attribution between sub-funds. Reconcile at the ownership and accounting level that determines each pool’s assets and liabilities, then aggregate for oversight. Equal and opposite errors can disappear at umbrella level while still affecting investors, performance, fees, financial statements or tax records in the individual sub-funds.

Is every unmatched trade a custody break?

Not necessarily. It may be an expected timing difference between trade-date and settlement-date records, but that conclusion needs evidence. Compare the accounting convention, trade status, settlement instructions and cut-off. If the item remains unmatched beyond the expected cycle, changes economic ownership or affects an output, reclassify and escalate it under the documented process.

Who should approve a manual identifier mapping?

Use a reviewer with enough knowledge and independence to verify the source records, economic identity and effective dates. The preparer should not approve a mapping solely to clear a break. Preserve both original identifiers, the normalised key, supporting event or security-master evidence, affected periods and any one-to-many relationship that limits automated matching.

What metrics make reconciliation oversight useful?

Track aged breaks, repeated causes, reopened items, unsupported adjustments, late source files, corrections after NAV release and breaks hidden by aggregation. Counts alone can mislead because a low number may reflect weak matching or broad netting. Add economic impact, ownership level, root cause and closure quality so the board and manager can assess provider and control performance.

Official sources and further reading

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.

An independent website by Raffles Corporate Services Pte Ltd. Not affiliated with or endorsed by ACRA, MAS or IRAS. General information only.