> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.28/voyage-management-system/step-by-step-guides/finance/opex-transactions.md). # Opex Transactions OPEX costs are not invoiced to a counterpart — they are internal accounting transactions that record the operational costs of running a vessel against the appropriate accounts in the accounting system. The **Opex Transactions** module handles the posting, reviewing, and reversal of these transactions, structured analogously to the existing Bunker Transactions module. *** ### How OPEX Posting Works Each OPEX posting produces a set of accounting documents: * One **document** per posting, referencing the **stock account** (document type: ACC). * One **document line** per OPEX line, referencing the **cost account** for that line. Documents and document lines are generated in both company currency and voyage currency. Postings are generated from voyage-level OPEX data. *** ### Pending Opex Transactions The **Pending** grid shows OPEX lines that are ready to be posted. Lines appear here once the voyage has OPEX data and are awaiting accounting posting. Columns shown in the pending grid mirror the voyage OPEX lines. From this grid, lines can be selected for posting. *** ### Posting OPEX Transactions **To post a single OPEX transaction:** 1. Open the Opex Transactions module. 2. Select the voyage or OPEX line to post. 3. Click **Post**. The Post Opex Transaction modal opens. 4. Confirm the details and submit. A document and document lines are created in the accounting system. **To batch-post multiple OPEX transactions:** 1. Select multiple lines in the pending grid. 2. Click **Post All** (or the batch post action). All selected lines are posted in a single operation. > **Note:** OPEX lines with existing posted document lines cannot have their Opex Type changed. The Opex Type field is locked once a document line is posted against it. *** ### Posted Transactions The **Posted** grid shows all OPEX transactions that have been successfully posted. Posted transactions are auditable and show the document reference, accounts used, amounts in company and voyage currency, and posting date. The posted grid refreshes automatically after a reversal is processed. *** ### Reversing an OPEX Transaction Reversing a posted transaction generates an inverted document and document lines to zero out the original posting. This follows the same reversal logic used for Bunker Transactions. **To reverse a posted transaction:** 1. Locate the transaction in the Posted grid. 2. Click the three-dot menu on the transaction row. 3. Select **Reverse**. After reversal, the reversed document's status is set to POS. The pending OPEX lines are regenerated and appear again in the pending grid. > **Important:** Voyage status must permit reversal. If the voyage status prevents the transaction from being reversed, the voyage status must be updated first. *** ### Bunker Reclassification for Offhire Periods When bunkers are consumed during an offhire period and the offhire record carries a deduction flag, those bunker costs are reclassified as OPEX in the accounting system. This is a separate Account compared to Voyage Opex. A transfer posting moves the cost from the bunker account to the OPEX account, reflecting that the cost is operational rather than voyage-related bunker consumption. *** ### Print The Print Invoice option is not available for OPEX documents. OPEX transactions are internal accounting postings, not invoices. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.dataloy.com/release-8.28/voyage-management-system/step-by-step-guides/finance/opex-transactions.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.