- A break is not an error, but an unresolved break can become one. In its CP130 consultation, the Central Bank proposed treating errors of 0.50% of NAV or more as material, or 0.10% for money market funds, in line with long standing Irish Funds industry guidance.
- Most breaks come from a short list of causes: trade and settlement timing, corporate actions, pricing and FX sources, fees and accruals, and capital activity from the transfer agent.
- The EU moves to T+1 settlement on 11 October 2027, with new allocation and confirmation rules from 7 December 2026. That leaves less time to find and fix breaks.
Breaks versus errors
A break is a mismatch between two sources. A NAV error is a mistake in the NAV that was struck. Good reconciliation stops the first from turning into the second.
The Central Bank set out its thinking on fund errors in Consultation Paper 130 (CP130) in 2019. It described four types of error:
- NAV error: an error in calculating the NAV
- Investment breach error: a breach of the investment restrictions that apply to the fund
- Fee error: the overpayment of a fee
- Control breach error: any other error, such as a redemption paid to the wrong account
CP130 proposed quantitative materiality thresholds of 0.50% of NAV for most funds and 0.10% for money market funds. It also said an error below the threshold can still be material for qualitative reasons, such as weak controls, an error that keeps recurring, or a series of small errors that add up. The fund management company is responsible for making sure errors are put right, with the depositary checking that they are.
Industry practice in Ireland has long followed Irish Funds Guidance Paper 6, which also uses 0.50% of NAV as the materiality threshold for pricing errors. Check the current position on the Central Bank framework with your legal advisers. Either way, the practical point is the same: a recurring break, even a small one, is evidence about your control environment.
Where breaks come from
| Break type | Typical causes | Records that disagree |
|---|---|---|
| Cash | Unsettled trades, late wires, fees and expenses, FX conversions | Administrator cash ledger and depositary or bank statement |
| Positions | Missed corporate actions, late or amended trades, transfers | Administrator, depositary or custodian, and investment manager order management system |
| Pricing | Stale prices, wrong price source, FX rate timing | Administrator price file and vendor or investment manager prices |
| Accruals and fees | Wrong rates, day count conventions, fee basis | Administrator and investment manager or expense budget |
| Capital activity | Subscription and redemption timing, unmatched investor cash | Transfer agent register, administrator and bank |
| Derivatives and collateral | Margin calls, valuation differences, collateral movements | Prime broker or counterparty and administrator |
Why the same breaks keep coming back
- Nobody records the root cause when a break is closed, so there is no way to see the pattern.
- Tolerances are not written down, so each analyst decides what is worth chasing.
- Matching happens in spreadsheets, so the logic lives in one person and one file.
- Sources have different cut off times, so timing breaks appear every day and get cleared by habit.
- Identifiers are mapped by hand between systems, so a new share class or instrument creates breaks for weeks.
- Ageing is invisible until a break is old enough to matter.
- The conversation with the delegate happens by email, so there is no audit trail of who asked what and when it was fixed.
How to build reconciliation that catches breaks before NAV review
1. Ingest every source daily into one controlled store
Administrator, depositary or custodian, prime broker, investment manager, transfer agent and bank data should land automatically in one place, with a copy of each delivery and its arrival time.
2. Normalise identifiers and mappings
Map ISINs, internal security codes, share classes, accounts and currencies once, in a maintained reference table, so the same item means the same thing in every source.
3. Match with rules and tolerances
Define matching rules and tolerances for each break type and fund, and keep them under change control. Auto clear the items that match within tolerance, so people only see real differences.
4. Age and escalate
Give every open break an age and an escalation path. For example, a cash break still open on the day after trade date goes to a supervisor, and one still open after three days goes to the oversight team.
5. Record the root cause at close
Make the root cause a required field when a break is closed. A monthly view of breaks by cause, source and fund tells you which upstream fix will remove the most work.
6. Show NAV readiness, not only open items
Before the NAV is reviewed, the team needs to see which open breaks could affect the NAV for the day, their value against the materiality threshold and who owns them.
7. Produce oversight evidence from the same data
Designated Persons, the depositary and the board should see break trends, ageing and any errors from the same records the operations team uses. That is the evidence of control the Central Bank looks for.
What T+1 means for breaks
The EU, together with the UK and Switzerland, moves from T+2 to T+1 settlement on 11 October 2027. New requirements for electronic, standardised allocations and confirmations apply from 7 December 2026. With one day less between trade and settlement, trade and SSI problems have to be caught on trade date. Batch processes that only surface breaks the next morning will struggle. Earlier matching, validated standing settlement instructions and clear ownership of exceptions become operational necessities.
Where AI helps, and where it should not
AI can shorten the time spent on each break. It can suggest likely matches for unmatched items, read broker confirmations and corporate action notices, propose a root cause based on similar past breaks and draft the commentary for a break report. The decision to clear a break or adjust a NAV should stay with a person, and every AI suggestion should show the source it relied on.
How HST can help
HST Solutions builds the ingestion, matching and exception workflows behind fund reconciliation. For Waystone we built PPM, which automates the retrieval, cleansing and loading of provider files from SFTP, email and S3 with configurable mapping rules. We work alongside your existing accounting and reconciliation platforms, so you fix the data and the workflow without replacing systems that work. We are ISO 27001 and ISO 22301 certified.
If your team spends the morning clearing the same breaks, talk to an engineer, or see how we work with fund managers, ManCos and administrators.
FAQ
Sources
- Central Bank consults on treatment, correction and redress of errors in investment funds, McCann FitzGerald
- CP130: treatment, correction and redress of errors in investment funds, Dechert
- CP130 consultation paper, Central Bank of Ireland
- Regulation to shorten settlement cycle to T+1 published in OJ, A&O Shearman
- EU T+1 settlement and fund managers, Rankia Pro
