NeoXam: investment data, accounting and operational control software

NeoXam supplies financial software for institutions that need consistent investment data, portfolio and accounting records, reconciliation and reporting. The brokerage use case is primarily the data and operational infrastructure behind trading and client servicing: maintaining instrument records, checking positions and cash against external records, and producing controlled reports. Its catalogue also serves asset managers, institutional investors, fund administrators and custodians, so a product’s investment-operations scope matters more than a generic trading-platform label.[1]

GP uses separate position-keeping, valuation and accounting engines. Its multi-book design can reflect one transaction in several accounting books, each with its own chart of accounts, fiscal settings and valuation treatment. This is useful when an institution needs local and consolidated views of the same portfolio. The workflow combines automated tasks with assigned human actions and preserves their history; it does not require every book to use an identical accounting interpretation. Optional add-ons and client-specific changes can be deployed separately from a complete platform replacement.[4]

Within PMS, Manager organises recurring production tasks, deadlines, escalations and completion evidence. Tracker concentrates on reconciliation, thresholds and exception resolution. Density consolidates portfolios across entities and custodians for wealth managers, family offices and smaller institutions, with dashboards, statements and digital client/adviser access. These distinctions help an operations team identify whether the required change concerns daily production control, data breaks or the client-facing portfolio view.[5]

DataHub’s MDM documentation lists CSV, JSON, XML, Excel, FIX and SWIFT formats, with REST/HTTP, S3, SFTP, messaging and direct database routes. Its mapping layer translates incoming feeds into the data model; field-level source ranking and survivorship determine the selected record. Governance includes approval workflows, scoped access rights and bi-temporal history, preserving both when a fact applied and when it became known. Distribution can use REST services, files, messaging, SQL or native Snowflake sharing.[8]

Market & Risk Data Management adds controls for pricing, history and risk inputs. It validates both incoming data and values produced by derivation rules, supports exceptions around calculated results, and schedules distribution to downstream consumers. Published use cases include independent price verification, portfolio valuation, risk scenarios and historical data used in FRTB processes. A broker’s implementation therefore needs to preserve the origin and transformation of a price or risk factor, not merely pass a final value into the trading or risk application.[9]

Impress separates report data from templates and production workflow. It supports document-level checks, multilingual layouts, draft/final version storage and delivery of outputs such as PDF, XML, CSV and spreadsheets. Client-report creation includes Excel and PowerPoint integration; digital reporting adds interactive performance and allocation views. The workflow can expose data reports to other applications or websites and deliver files through SFTP. The chosen report template and output format remain part of the implementation scope.[6]

NeoXam uses a business enquiry and scoping process. The reviewed product and contact material does not provide a universal numeric licence tariff or a common minimum contract value. Several products disclose how charges are structured, which is useful when comparing proposals, but a quotation is still needed for the selected modules and service scope.[17]

The consultancy model permits NeoXam to lead the project, an approved partner to lead, the customer to do most of the work, or a combined team to deliver it. Services cover data models, connectors, screens, report calculations and templates. The documented test phase includes release management and monitoring of incoming and outgoing feeds; the run phase includes periodic support, improvement and upgrades. Knowledge transfer is part of the offering, which matters when the customer will own configuration and operations after launch.[11]

Deployment is product- and contract-specific. The managed-services page offers containerised on-premises installations, hosted environments and NeoXam-operated SaaS. It describes European private-cloud hosting for relevant residency requirements and public-cloud regions for other locations, with standard examples in northern Virginia, Frankfurt and Singapore. DataHub includes feed-monitoring services; Aro can combine the application with additional business services. Hosting software and taking responsibility for the operational process are separate service choices.[10]

In its 4 August 2026 hosting statement, NeoXam describes segregated customer instances, exportable data and the option to move the same product between public cloud, European private cloud and customer-operated infrastructure. That provides a useful basis for an exit design. The public statement does not supply a customer-specific export specification, transition timetable or fee schedule; those details belong in the service agreement and migration plan.[18]

GP’s hosted NeoXam-as-a-Service description includes software, hosting, monitoring and upgrades, with service-level commitments and advertised 24/7 client support. This statement applies to that service proposition; the page does not publish severity-specific acknowledgement or resolution targets for every licence and deployment. The contract should identify the applicable support package and escalation route.[3]

Recon as a Service combines a hosted reconciliation platform with an operating team. NeoXam’s October 2025 Chennai announcement describes acquisition of data from brokers, custodians and trustees, checks on data timeliness and quality, SLA management and delivery of completed reconciliations. This service is broader than technical incident support: the agreed operating model must specify who investigates breaks and who approves their resolution.[13]

GP supports accounting and regulatory reporting workflows. Customers remain responsible for selecting the applicable rules, validating outputs and establishing their own permission to provide financial services. The software and operating-service agreement should identify the reporting formats and updates included, alongside the customer’s approval and submission responsibilities.[3]

The legal notice identifies the French website publisher as NeoXam, registered in Paris under number 798 287 926, at 46 rue Notre-Dame des Victoires, 75002 Paris. It also states that products and services are governed by their own agreements and may differ by country. The contracting supplier for a particular deployment should therefore be taken from the order and service agreement.[14]

NeoXam’s published history dates the group’s formation to 2014, when it acquired GP3 and Decalog from SunGard and added Density Tech. Nexfi and SmartCo followed in 2015; 100M was acquired in 2019. The same history records Eurazeo becoming majority shareholder in 2023. These origins explain why older system names can remain relevant to an institution’s migration and product-support discussions.[15]

NeoXam announced the completed acquisition of EZOPS on 3 December 2024, adding reconciliation, data-control and workflow-automation technology. The announcement described integration with its front-, middle- and back-office software and deployment through SaaS, private cloud or on-premises arrangements. The current Aro and managed-reconciliation propositions should be assessed in that broader product context.[16]

Operator

NeoXam group; the French website publisher is NeoXam, Paris registration 798 287 926.

Service scope

Institutional data management, portfolio operations, accounting, reconciliation, reporting and related managed services.

Customer types

Banks; Asset managers; Institutional investors; Fund administrators; Custodians; Wealth managers; Family offices

Delivery

SaaS; Hosted; On premises; API; Managed service; Hybrid

Pricing publication

Quote only

Platforms

DataHub; GP; PMS; Manager; Tracker; Density; Impress; Aro; Structure; NeoXam Agents

Integrations

REST APIs; SFTP; S3; JMS; Kafka; FIX; SWIFT ISO 15022/20022; Snowflake data sharing; Excel; PowerPoint

Pricing scope

Aro discloses modular usage pricing; managed reporting advertises an inclusive model. Numeric rates and service limits require agreement.

Implementation

Client, NeoXam, partner or mixed delivery teams; configuration, feed testing, training and operational handover.

Support

Scoped hosted-service support and operating services, with public business contact routes; exact incident targets are contractual.

Permissions and regulatory scope

Technology and operating-service scope. Reporting and accounting functionality is not treated as financial-services authorisation.

Provider metadata checked 21 Oct 2026Source 1Source 14Source 2Source 3Source 5Source 6Source 7Source 8Source 10Source 11Source 12Source 15Source 16Source 20Source 19Source 13

Reporting as a Service and Recon as a Service use a similar abbreviation but deliver different outcomes. The reporting service takes supplied data through processing, report generation and delivery, with visible production status and an audit trail. It can produce factsheets, portfolio statements, pitchbooks and regulatory documents. Its published model accommodates daily, monthly or quarterly reporting, while the exact deadline, validation responsibility and included report set depend on the service arrangement.[12]

The 24 June 2026 NeoXam Agents announcement distinguishes three stages: specialised agents already in preview, a stated September 2026 general-availability target, and an early-adopter programme with testing through the fourth quarter and a path to production in early 2027. It describes an approved-agent catalogue, action records, human approvals for sensitive decisions and choice of underlying AI model. The announcement alone does not confirm that every agent subsequently met its target; availability should be established for the particular product and customer deployment.[19]

Structure’s documented workflow ingests documents, extracts fields, assigns confidence scores and routes uncertain values for review before exporting data. Broker-statement use cases include transaction identifiers, quantities, prices, fees and settlement dates. Its advertised accuracy and timing figures are vendor claims tied to document types and conditions; the operational control is the validation step and retained audit trail. They should remain visible when a broker connects extraction to accounting or reconciliation.[20]