Reconciliation for Fund Administrators

Each administered fund can introduce different custody relationships, share classes, fee structures, investor records, reporting calendars, and source formats. The operating challenge is to apply consistent controls while preserving each fund's accounting basis, cutoff, ownership, and approval requirements.

The daily cycle is punishing. Custodian files arrive at different times, in different formats — some via SFTP, some through portals, some as email attachments. Position breaks from yesterday's corporate actions cascade into today's NAV if they are not caught early. Trade settlement mismatches create phantom P&L that distorts investor allocations.

Most administrators have built internal tools or rely on vendor platforms that handle the matching but not the investigation. When a break appears, a human still needs to determine whether it is a timing difference, a booking error, a missing trade, or a genuine discrepancy. That investigation step is where the hours accumulate — and where mistakes happen under deadline pressure.

The regulatory environment compounds the problem. Auditors expect documented evidence of how each break was identified, investigated, and resolved. Rebuilding that narrative after the fact — from emails, chat messages, and spreadsheet annotations — is expensive and unreliable.

Your operations team shifts from assembling and comparing files to reviewing supported exceptions and authorizing actions. Aetherix handles controlled ingestion, normalization, matching, investigation support, evidence assembly, and open-item follow-up across the agreed fund population.

Position, trade, cash, valuation, accrual, fee, and capital-activity differences are organized before the final NAV bridge. Valid timing items remain visible with owners and expected clearing evidence; accounting, valuation, materiality, and final NAV decisions remain with authorized administrator and client teams.

When a new fund enters scope, its sources, calendars, identifiers, mappings, matching rules, review controls, and escalation paths are configured as a documented operating process rather than added to an unmanaged spreadsheet chain.