# Finalizing Orders Once a trade has been matched, the finalise button will become visible on the UX for both the counterparties to the trade, like so:

Similarly, users of the SDK will find that the "EventQListener" will detect when an order has been filled, and provide template transactions for "*FinaliseBid*" and "*FinaliseAsk*".\ \ Either user may then proceed to finalize the order. Upon clicking Finalize, the program logic checks that both the counterparties to the trade have enough tokens in their openorders accounts. If not, it attempts to transfer the appropriate amount of funds from the party to the program owned "vault". Once th\ If so, it proceeds with modifying the balances according to the trade terms, and then marks the trade as finalized (to prevent double spends). After finalization is completed, the user can instantly see their updated balances from their OpenOrdersPDA:

These funds will then available for withdrawal at any time. For a deeper dive into the logic executed at the `finalizeOrders` step, please see [just-in-time-liquidity](https://fermi-dex.gitbook.io/fermi-dex-docs/technical-overview/architecture/just-in-time-liquidity "mention").\ \ Example Finalise Transaction: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://fermi-dex.gitbook.io/fermi-dex-docs/fermi-dex-usage-guide/fermi-dex-how-it-works/finalizing-orders.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.