The June 30 FAR deadline arrives at the same time every year. And yet, for a significant number of Cayman fund operators, it arrives as a surprise. Not because they forgot it — but because the preparation work was not started early enough, the data was not gathered in time, the auditors were not instructed until May, and by mid-June the whole exercise was being compressed into two frantic weeks.
This post lays out a realistic, field-tested month-by-month timeline for FAR preparation that starts in January and reaches June 30 with time to spare.
Why You Need to Start in January
The FAR is not a form you can complete in a week. Even a relatively straightforward fund requires:
- Gathering data from multiple service providers (administrator, custodian, investment manager, legal counsel)
- Waiting for audited financial statements (which themselves require an audit, which requires the books to be closed)
- Coordinating operator sign-off and the Operator Declaration
- Validating the form and resolving errors
- Submitting through REEFS and confirming acceptance
The audit timeline alone typically takes until April or May for most funds with a December year-end. Starting the FAR preparation process in parallel with the audit — rather than waiting for audited accounts before touching the FAR — compresses the total timeline and allows June to be used for final review rather than first draft.
January: Set Up
Entity register review. Confirm the list of every CIMA-registered entity with a filing obligation. Check for any new funds registered during the prior year, any funds in wind-down, any AIVs that may have been added or dissolved, and any changes in year-end.
Deadline mapping. Map each entity's filing deadline based on its financial year-end. Flag any entities with non-December year-ends — they may have earlier or later deadlines.
Service provider confirmation. Confirm that every entity has a designated submitter (auditor for mutual funds; auditor or service provider for private funds) and that the submitter's REEFS access is current and active.
Auditor instruction. Formally instruct auditors for every entity, confirming scope, timeline, and the expectation that draft financial statements will be available by a specific date (target: late March to mid-April).
February: Data Gathering
Issue data request templates. Send standardised data request forms to the investment manager, administrator, and other service providers for each fund. Request:
- Confirmed service provider details (any changes from prior year?)
- Updated investor information (types, jurisdictions, significant investor changes)
- Details of any new related fund entities (AIVs, parallel funds, co-investment vehicles)
- Side letter information (number and nature of side letters in place)
- Operator meeting information (number of meetings held during the year)
Begin FAR form population. Do not wait for financial data to start the FAR. All non-financial sections — legal structure, service providers, operators, investors, related entities — can be completed before the audited accounts are available. Populate these sections in February using the gathered data.
March: Non-Financial Sections Complete
Complete and review all non-financial sections. By end of March, the general, operating, and related fund entity sections of every FAR should be substantially complete, pending only final confirmation of a few data points.
Chase outstanding data. Follow up with any service providers who have not responded to the February data requests. The non-financial sections cannot be finalised without accurate service provider and investor data.
Monitor audit progress. Check in with auditors on timeline. Identify any funds where the audit is at risk of being delayed — these are the candidates for a potential extension request, which must be filed before the June 30 deadline if needed.
April: Financials Begin
Receive draft financial statements. For most December year-end funds, draft audited accounts should be available in late March or April. Begin populating the financial section of the FAR as soon as draft accounts are received — noting that the financial data should be updated to match final figures before submission.
Cross-reference early. Even at the draft stage, cross-referencing the FAR financial section against the draft accounts identifies any structural inconsistencies (e.g. a discrepancy in how distributions are categorised) before the accounts are finalised. Raising these issues in April is far less stressful than discovering them in June.
May: Validation and Review
Finalise financial sections. As audited accounts are signed off, update the FAR financial sections to reflect the final figures.
Run full FAR validation. Every form goes through a complete pre-submission validation — using a purpose-built tool — to check every field, every drop-down selection, and every cross-reference against the audited accounts. Document the validation output.
Operator review. Present the completed FAR to the fund operator for formal review and approval. Operators are legally responsible for the accuracy of the form — this review step is not a formality. Allow at least one week for operator review and any resulting amendments.
Operator Declaration. For private funds, the Operator Declaration must be signed by a director, general partner, or trustee. Coordinate this in May — not on June 28.
June: Submission
Submit by mid-June. Target submission date: 15 June. This gives a two-week buffer before the June 30 deadline for any REEFS technical issues, last-minute queries from CIMA, or administrative problems with fee payment.
Confirm acceptance. Do not assume that uploading the form to REEFS constitutes a completed filing. Confirm that the submission has been accepted, the fee has been recorded, and the fund's status in REEFS reflects "filed."
File extension requests if needed. If any entity is genuinely going to miss June 30 — for example, because the audit is significantly delayed — file the extension request before June 30. Do not wait until July 1 to apply for an extension that was needed in June.
Building This Into Your Annual Calendar
The most effective FAR project management practice is to treat June 30 not as the start of a project but as its final checkpoint. Everything above should be templated, scheduled, and triggered automatically at the start of each January — not reconstructed from scratch each year.
One step that belongs in every template, for every fund, every year, is the May validation gate. No matter how well the preceding months have gone — how organised the data gathering was, how smoothly the audit ran, how diligent the operator review — a FAR that has not been independently validated before it reaches REEFS is carrying avoidable risk. Errors that a validator catches in May are resolved in hours. The same errors caught by CIMA's system on June 29 can mean a rejected filing, a missed deadline, and an extension application filed under pressure.
Validate your FAR in seconds with our drag-and-drop FAR Validator →
All blog posts are for informational purposes only and do not constitute legal, regulatory, or compliance advice. Fund operators should always confirm current requirements with CIMA or their legal and regulatory advisors.