Xceptor: data automation, reconciliations and post-trade workflows

Xceptor supplies data and workflow automation for financial institutions. It ingests information from operational systems and documents, applies transformations and validation, then routes results and exceptions through configured processes. Its product catalogue covers reconciliations, confirmations and tax, alongside client lifecycle and post-trade use cases. For a brokerage, the practical role is the processing and control layer around trading records, counterparty documents and downstream operations.[1]

Reconciliation is more than a final comparison of two files. Xceptor first captures and transforms records, checks completeness and enriches data from internal or external sources. Users configure rolling, snapshot, multiway or other reconciliation styles, with formulas and tolerances determining a match. Ageing models and user-defined assignment rules then organise unresolved items. Reporting can remain inside the application or feed external reporting tools, so matching logic and exception ownership are separate configuration decisions.[4]

Confirmations combines inbound and outbound processing. The documented sequence includes trade capture, affirmation, legal drafting, delivery, matching of economics and legal language, chasing and dispute resolution. Status changes can update internal systems and initiate later settlement or reporting steps. A confirmation that matches automatically and one requiring legal-language review therefore need different paths through the operating workflow, even when both started from the same booking system.[5]

The connector catalogue distinguishes general building blocks from packaged integrations. Base options include email, SFTP, REST APIs, files and SQL Server. Named business-system examples include Murex, Aladdin, AxiomSL, DTCC GTR, SimCorp and Fenergo, but those examples describe integration capability rather than a blanket entitlement to every application. The actual connector, supported operation and customer licence determine the connection available for a deployment.[3]

Document Intelligence handles the extraction step within a larger process. Published examples include loan notices and credit agreements for lenders, capital calls and distributions for fund administrators, OTC confirmations and standing settlement instructions for banks, and tax documents for custodians. Extracted fields then enter validation and downstream integration. That separation matters when a document is readable but its economic meaning, counterparty identity or required field still fails a business check.[7]

Xceptor uses a sales enquiry and demonstration process. Its public sales pages do not set out a universal numeric licence tariff, standard user minimum or transaction allowance. A proposal needs to define the product and deployment scope, integrations and service package; the published contact route is the starting point for that commercial discussion.[15]

Standard and Premium access can require approval through the Client Success Manager, user whitelisting and term-limited licence keys requiring renewal. Separately agreed connector licences remain distinct.[12]

The public website terms govern access to xceptor.com and explicitly exclude Connect, which has separate terms. They describe website case studies and other content as general information. These website conditions do not supply the production software’s order scope, data-processing schedule, service credits or exit provisions; those need to be established in the applicable customer agreements.[17]

The platform supports Xceptor-operated SaaS, customer-cloud deployment and on-premises installation. SaaS places infrastructure maintenance and software updates with Xceptor; customer-cloud deployment uses the institution’s infrastructure. The platform describes Kubernetes-based deployment, role-based controls, audit logs and OAuth2/SAML access mechanisms. Those capabilities support an operating design, while the selected hosting arrangement determines the practical division of maintenance and infrastructure work.[2]

Xceptor’s partner network covers implementation, integration, custom development and ongoing support. It includes system integrators, resellers, technology providers and managed-service providers, with the latter able to combine hosted delivery and operational ownership. Partner implementation and an outsourced operating service therefore represent different engagements. The project needs an agreed handover for configuration, exception handling and subsequent changes, rather than treating every delivery partner as responsible for the same tasks.[14]

Training is organised through Foundation and Practitioner learning paths, practical exercises and a sandbox. Clients and partners can access the Academy with their work email; blended programmes add coaching for operational teams and centres of excellence. Advanced Practitioner and Expert certification are described as partner-only, and certificates are valid for two years. Training access supports user enablement, but it does not itself grant production rights to every product or connector.[13]

Connect’s Sandbox is restricted to internal training with redacted dummy or supplied sample data. Labs is for expressly authorised nonproduction use. Their terms prohibit personal or sensitive unredacted content and permit uploaded-file deletion without notice. These restrictions concern the learning and proof-of-concept environments.[12]

The platform page advertises 24/7 global support, monitoring, health checks and customer-success teams. It refers to commitments for uptime, response and resolution but publishes no common numerical targets. The customer agreement must identify the applicable package, incident priorities and measured service commitments.[2]

Xceptor Connect provides routes to documentation, Academy training, the Huddle community, Sandbox, Marketplace and support. The public landing page is a navigation point for these customer resources; access to individual services is governed separately. A training or community account should not be treated as evidence that a particular production support entitlement has been purchased.[16]

Xceptor’s governed-AI description combines probabilistic extraction and proposed matching rules with deterministic validation. Extracted confirmation fields can be checked against term sheets, pricing supplements and booking or risk systems. Field confidence is linked to the relevant document location, and low-confidence results, corrections and overrides go to authorised reviewers through maker-checker controls. The company states that customer data is not used to train the underlying models and that client databases are separated by tenant. These are its published design commitments; configured thresholds and approval paths determine how the controls operate in a particular workflow.[8]

The post-trade offering includes settlement-status monitoring and routing exceptions to operational teams. Those are software functions within the institution’s processing environment. They do not establish an investment-services, custody or client-money authorisation for Xceptor, and this profile does not attribute such permissions to the software vendor.[11]

Connect’s terms grant broad continuing rights over submitted content and do not promise to retain or return it. This Connect-specific licence must be distinguished from the data rights negotiated for a production deployment.[12]

The website identifies its operator as Xceptor Limited, company number 04825384, with its principal trading office at 1 Lackington Street, London EC2A 1AL. That legal identity is distinct from an individual product or portal name. The contracting supplier and the applicable deployment agreement should be identified in the order documentation.[17]

Xceptor traces its origins to 2003, when co-founder Dan Reid and former financial-services colleagues began building a platform to put enterprise data automation into business users’ hands. Its current account of that history emphasises configurable processes with audit and control, which explains the combination of operations-user configuration and technology oversight in its product positioning.[19]

Astorg’s current portfolio includes Xceptor and records its entry in 2021 through Astorg VII. The investor describes the business as financial data ingestion, transformation and process digitisation software, headquartered in London. The portfolio entry establishes the investment relationship but does not publish a full current shareholder breakdown or ownership percentage.[20]

Operator

Xceptor Limited, England and Wales company 04825384

Service scope

Financial data ingestion, transformation, reconciliation, confirmations, tax processing and workflow automation.

Customer types

Banks; Asset managers; Hedge funds; Custodians; Securities-services firms

Delivery

SaaS; On premises; Hosted; API

Pricing publication

Quote only

Headquarters

London, United Kingdom

Platforms

Data Automation Platform; Reconciliations; Confirmations; Tax; Document Intelligence; MiKaDiv; Xceptor Connect

Integrations

REST API; SFTP; SQL Server; AWS S3/SQS; Azure storage; Google Cloud storage/Pub/Sub; Snowflake; SWIFT; Kafka; RabbitMQ

Pricing scope

Scoped software pricing; connector entitlements can require separate agreements.

Implementation

Xceptor or partner implementation, integration, configuration and training.

Support

Advertised 24/7 global support; numeric service targets and package coverage require agreement.

Permissions and regulatory scope

Operational software for financial institutions; workflow functionality does not establish investment-services authorisation.

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

On 18 February 2026, Xceptor announced a preconfigured Tax SaaS offering and a MiKaDiv module. The module gathers beneficial-owner information, transactions and documents, checks discrepancies and produces standardised reports for the German tax authority or other endpoints such as a local tax agent. The announcement concerns an available product option; its discussion of future reporting obligations is not evidence that every customer has implemented it or completed a filing.[21]

Tax processing is modular. Documentation management covers gathering, producing, renewing and soliciting forms; relief at source uses the documentation held for the beneficiary. Reclaim management follows income payments through identifying opportunities to reconciling the eventual payment. Rate determination supplies tax data and calculations to other systems, while electronic filing transmits tax data to an authority or intermediary. Those functions can be combined, but they address different operational stages.[6]

EUC remediation addresses end-user applications such as locally maintained operational tools. Xceptor describes moving their business functions onto a hosted, controlled platform, with configuration-driven workflows, security and an enterprise audit trail. The product proposition is therefore a change in how the process is operated and governed; migrating the logic still requires establishing the intended rules and checking that the replacement produces the required operational result.[10]