Celebrating 31 Years of Client ServiceCelebrating 31 Years of Client Service in 2026
Call610-992-9287
Consulting
From a CSSI customer engagement
CSSI's published Axys-to-Orion engagement covers a conversion with sleeve structures, complex billing, and dependent reports. Review the project context when defining what your own system change needs to preserve.
Read the Axys-to-Orion project storyService fit
Accounting checklist
Scroll across to review all three columns.
| Accounting requirement | Demonstrate with source records | Accept when |
|---|---|---|
| Account and group structure | Accounts, households, entities, sleeves, reporting groups, and their effective dates. | The target structure represents the intended population and dependent reporting or billing views. |
| Historical transactions and actions | Required history, corrections, transfers, corporate actions, and transaction-type mappings. | Representative history is usable and differences or unavailable records have a documented resolution. |
| Holdings, cash, and valuations | Approved source balances, pricing dates, currency basis, and reconciliation comparisons. | The sample agrees with the reference within agreed tolerances and exceptions have named owners. |
| Tax lots and cost basis | Lot-level source detail, acquisition dates, adjustments, and required exports or reports. | Required lot detail survives the conversion or has an explicitly agreed reconstruction scope. |
| Performance, billing, and reports | Source calculations, periods, fee or billing rules, custom layouts, and required client output. | The firm approves the figures and dependent output; a successful import alone is not the acceptance test. |
| Cutover and the first close | Final refresh, operating sequence, open items, archived history, support, and fallback responsibilities. | Users can complete the agreed close and report cycle with approved records and a clear escalation path. |
Example decision
Project outputs
First project
Connected services
Product context
Questions
Compare the account structure, transaction and corporate-action history, cash and holdings, valuations, tax lots, performance, billing, reports, and operating close. Use representative records and approved source output so the comparison tests the work your firm needs.
CSSI supports portfolio data conversion, mapping, historical validation, reporting dependencies, and transition work. Supply the source and target systems and required output so the team can confirm the available data and project responsibilities.
It specifies the investment view a firm needs and which source supplies it, including holdings, cash, transactions, timing, and approval rules. Define how that view relates to the accounting records and confirm the required functionality with the software provider.
It proves one comparison. Required history, tax lots, calculations, account groups, billing, reports, user workflows, and the first close also need acceptance checks. Document what must work before the firm approves cutover.
Next step
