> 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.3-release-notes.md). # XYB Platform 2.3 Release Notes #### 1. Batch, Scheduled & Backdated Payments **A Richer Toolset for Initiating Payments** This release significantly expands what you can do on the payment initiation side, with support for batch payment files, scheduled and postponed payments, backdated payments, and reusable payment drafts and templates. * **Batch payment upload:** Import and submit batch payment files — including payroll-style runs — via CSV upload. * **Scheduling:** Schedule individual and batch payments for a future date, or postpone a payment as needed. * **Backdated payments:** Create backdated payments where your business process requires it. * **Drafts & templates:** Save payments as drafts to finish later, and store frequently used payment setups as reusable templates. * **End-to-end traceability:** Batch identifiers are stored and displayed in payment history, so grouped payments remain traceable from submission through to completion. #### 2. Approvals & Rejection Handling **More Control Over How Approvals Are Configured and Resolved** The four-eye approval experience has been extended with per-operation approver configuration, a clearer rejected-approvals flow, and the ability to cancel an approval request. * **Per-operation approvers:** Approval policies can now be bound to specific operations, with approvers configured per operation for beneficiary approvals. * **Rejected-approvals view:** When a payment or payee is rejected, you can now review, discard, or resubmit it through a dedicated rejected-approvals screen. * **Cancel a request:** Initiators can now withdraw an approval request before it's actioned. * **Full audit trail:** The four-eye approval flow now carries a complete audit trail from submission through to resolution. #### 3. Treasury Web App & Console **Broad Usability and Consistency Improvements** The treasury web app and operator console receive a wide set of usability and consistency improvements. * **Asset position view:** A new view for tracking asset positions. * **Rejected approvals & unfinished payments:** Dedicated views for reviewing rejected approvals and payments left in an unfinished state. * **Source account visibility:** The source account is now shown on the Activity screen. * **Maintenance-mode banner:** A banner now appears during scheduled maintenance windows. * **Clearer access control:** Navigating directly to an area you don't have access to now shows a proper "Access Denied" page instead of a blank screen. * **Consistent language:** Text casing and wording have been standardised across the console. #### 4. Automations & Reconciliation **Safer Workflow Management and Improved Reconciliation** The workflow automation studio and reconciliation tooling have been substantially improved. * **Safer import/export:** Automation workflows can now be imported and exported more safely, with a dry-run preflight check that validates a workflow before it runs. * **Graceful version handling:** Node version mismatches are now handled gracefully instead of causing failures. * **Advanced node section:** Nodes are now organised into a recategorised, easier-to-navigate advanced section. * **Automated, annotated reconciliation:** Reconciliation runs can now be automated and produce annotated output, with a new results-and-details page for reviewing outcomes. #### 5. Credit, Collateral & Entities **Continued Maturity Across Lending and Entity Management** * **Automatic pledgee updates:** Pledgee status now updates automatically as loans approach maturity. * **Scheduled invoicing:** Principal, interest, and fee invoices can now be generated automatically on a schedule based on product parameters. * **Refined maturity handling:** Contract maturity and termination logic has been refined for greater accuracy. * **Redesigned entity experience:** The entity picker and business detail views have been redesigned as part of an underlying rework of our entity data model. #### 6. Improvements and Fixes * **Stronger authentication:** Added passcode and biometric sign-in support, plus step-up verification on sensitive payment and beneficiary operations. * **More reliable payments and payees:** Stricter session validation, more accurate payee approval status, and correct handling when a new account is added to an existing payee. * **Improved automations:** Fixes to condition nodes, message-template selection, and workflow editing states. * **Fixed a wide range of issues** across payments, approvals, credit and collateral, the treasury web app, ledger, access management, and the console — including server errors on payment creation, duplicate company and user entries, broken date-range filters, pagination defects, and several display and layout 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.3-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.