> 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.2-release-notes.md). # XYB Platform 2.2 Release Notes XYB Platform 2.2 is our biggest release to date. It's centred on three things: a much larger and more capable automation node library, the groundwork for automated bank reconciliation through composable workflows, and a new generation of dashboard widgets for treasury and operations users. Alongside this, we've introduced an AI-powered invoice assistant (early access), tightened anomaly detection on payments, and completed a platform-wide hardening pass covering permissions, observability, and dependency security. #### 1. Automation & Workflow Nodes **A Larger, More Flexible Node Library for the Workflow Builder** The composable workflow builder has been substantially expanded, giving you more building blocks to model complex processes without custom development. * **New node types:** Wait and Sync nodes join refreshed Task, HTTP Request, Webhook, Slack, Code, and Message nodes, alongside a new internal-event trigger. * **Better organisation:** Nodes can now be grouped by type and carry custom icons, making larger workflows easier to navigate. * **Cleaner configuration:** Node configuration fields are now driven dynamically, and input/output variable handling has been simplified across the board. * **Safer evolution:** Nodes can be deprecated cleanly over time without breaking workflows that are already running. #### 2. Automated Reconciliation — Backend Foundation **Laying the Groundwork for Automated Bank Reconciliation** This release delivers the backend foundation for automated bank reconciliation, built as a composable workflow rather than a fixed, hardcoded process — so reconciliation logic can be configured and extended over time rather than requiring a new release for every change. * **Configurable, not hardcoded:** Reconciliation can now be initialised with runtime configuration instead of relying on a single fixed profile. * **Annotated results:** Reconciliation output is written back as an annotated file showing each original row alongside its outcome (for example, matched or requiring attention). * **First user-facing step:** A new "run reconciliation automatically on upload" option is available on the bank statement upload screen. The full Reconciliation experience — a dedicated section for managing profiles and reviewing reconciliation runs — is still in development and will follow in a future release. #### 3. Dashboard Widgets **New Widgets for Treasury and Operations** The Console dashboard has been extended with new widgets, giving treasury and operations teams clearer, more focused visibility into platform activity. * **Payment Volume Overview:** A summary view of payment activity over time. * **Payment Success Rate:** Visibility into how payments are performing. * **Partner Adapter Health:** Status visibility into the health of connected payment partners. * **Refreshed entity and ledger widgets:** The previous entity and ledger cards have been split into more focused, individually customisable widgets. #### 4. Account Statements **Redesigned Statement Screens, with Retry Support** The account statements experience has been redesigned to align with our updated design system, and now includes a retry option for when generation doesn't succeed the first time. * **Redesigned generation flow:** The statement page and the single/multi statement generation dialogs have a refreshed look and feel. * **Retry failed statements:** If a statement fails to generate, you can now retry it directly from the statement page — no need to start over. * **Clearer scheduling:** Scheduled and manually generated statements are now clearly distinguished, and statement scheduling can target a specific wallet and template. #### 5. Treasury, Payees & Banking Coordinates **More Control Over Payee and Payment Details** Payee and banking coordinate management is now more flexible, with several improvements aimed at reducing risk and giving you more control. * **Deactivate and reactivate coordinates:** Banking coordinates can now be deactivated and reactivated as needed. Deactivated coordinates are automatically removed from the list of available payment destinations. * **Safer approvals:** If a payment's destination coordinate is deactivated while it's still pending four-eye approval, the payment is now automatically rejected rather than proceeding. * **No more per-payee currency limits:** The previous restriction limiting which currencies could be used per payee has been removed. * **Richer address details:** Beneficiary addresses now support apartment/suite information. * **Mandatory comment on block:** Blocking a payee now requires a comment, improving the audit trail behind that decision. #### 6. AI Invoice Assistant (Early Access) **A New Way to Process Invoices** We've introduced an AI-powered invoice assistant, available to early-access partners. A new "My invoices" view in the web app lets you upload invoices and have key details extracted automatically, reducing manual data entry. Access is currently gated while we roll this out gradually — reach out to your XYB contact if you'd like to be considered for early access. #### 7. Risk & Anomaly Detection **Sharper Detection, Clearer Signals** * **New off-hours detection rule:** Payments created outside of expected hours are now flagged as part of the risk engine's rule set. * **Refreshed anomaly badges:** Badges covering new payee, payee details changed, off-hours activity, multiple payments in a day, high amount, and cross-border payments have been refactored for clarity. * **More reliable high-amount detection:** A previously inconsistent trigger for the high-amount rule has been corrected. #### 8. Improvements and Fixes * **MFA:** Improved phone number handling, more consistent policy enforcement, and admin experience improvements; the magic-link email template has also been refreshed. * **Collateral:** Collateral value now updates automatically when product haircut configuration changes, and a foreign exchange reference rate can be configured to drive value recalculation. * **Interest:** Fixed and variable base-rate handling has been improved in the day-change process, and an issue where automatic variable interest changes could drop a principal payment from the schedule has been fixed. * **Product configuration:** Fixed cases where terminating a draft version could leave a product with no active version, and corrected how boolean and integer fields are saved. * **Web app & Console polish:** A range of smaller fixes, including more stable list behaviour while scrolling, a fixed "Back to account selection" link, resolved login screen flicker, fixed blank pages that could appear after a platform update, and a number of translation, tooltip, and button-placement corrections. --- # 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.2-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.