> For the complete documentation index, see [llms.txt](https://docs.xyb.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyb.co/platform-release-notes/xyb-platform-2.0-release-notes/xyb-platform-2.5-release-notes.md). # XYB Platform 2.5 Release Notes #### 1. Reconciliation Console **Reconciliation Becomes a First-Class, Reviewable Workflow** This release delivers a full reconciliation experience in the Console, moving reconciliation from a background process into a first-class, reviewable workflow. * **Dedicated activity view:** Operators can now view reconciliation activity in a dedicated list. * **Drill into a run:** Each run can be reviewed across accounts and transactions tabs. * **Resolve exceptions directly:** Exceptions can be resolved in place — creating a missing account, creating a matching payment, or re-running matching. * **Reusable profiles and run sets:** Reconciliation is organised around reusable profiles and run sets, with per-profile display columns, coverage checks before a run, and clear exception counts throughout. #### 2. Enterprise SSO: SCIM Provisioning **Automated User and Group Management for Enterprise Customers** Enterprise identity management is significantly strengthened with SCIM 2.0 user and group provisioning, complementing existing SAML 2.0 single sign-on. * **Automated provisioning:** Identity providers can now automatically provision and de-provision users and groups. * **Role sync:** Role membership stays in sync automatically, with access managed centrally from your identity provider. * **Clear ownership:** SCIM-managed roles are shown as read-only in the Console, so it's always clear where a role is being controlled from. * **Broad compatibility:** Provisioning has been validated against major identity providers. #### 3. Payment Timeline & Failed Payment Handling **Full Visibility into Where a Payment Stands** Payments become far more transparent, with a full status timeline and clearer handling of failures. * **Detailed status timeline:** Payment history now includes a detailed timeline of status events, so you can see exactly where a payment is in its lifecycle — including payments that are stuck or delayed. * **Correct handling of failures:** Failed payments are now handled correctly in the ledger, ensuring postings do not remain pending when a payment fails. #### 4. Payment Rails: Wire, BAI2 & BTRS3 **Expanded Rail Coverage and Standards-Compliant Reporting** Payment rail coverage expands with wire file generation and standards-compliant reporting. * **Wire support:** Wire files can now be composed to the ISO 20022 pacs.008 standard. * **BAI2 and BTRS3 reporting:** Reporting files can now be generated from unified platform data, including full ACH addenda linkage. * **Two-step authorisation:** Two-step authorisation is now supported for partner payments. #### 5. Terms & Conditions Management **Manage, Version, and Track Acceptance of Customer Terms** A new terms-and-conditions capability lets banks manage, version, and capture acceptance of customer terms. * **Authoring and versioning:** Terms can be authored and versioned with four-eye approval. * **Template integration:** Terms integrate with the existing template system. * **Customer acceptance:** Terms are presented to customers for acceptance, with a full audit trail of who accepted which version and when. #### 6. Improvements and Fixes * **Redesigned payment activity screen** in the web app, with batches shown in activity and clearer payment detail. * **More reliable treasury workflows**, including fixes to scheduled payments, batch approvals, payee and account editing, and statement imports. * **More accurate money display**, with exact decimal handling on payment volume and posting search surfaces. * **Fixed a wide range of issues** across payments, beneficiaries, cards, policies, reconciliation, and the console — including card activation, top-up, policy visibility, and numerous treasury web app display and saving issues. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.xyb.co/platform-release-notes/xyb-platform-2.0-release-notes/xyb-platform-2.5-release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.