The OPS-COM system provides three primary methods for modifying or reversing financial transactions: cancellations, adjustments, and refunds. Understanding the differences between these options helps administrators accurately manage user accounts, correct billing errors, and maintain proper inventory levels. This article is intended for OPS-COM administrators responsible for financial processing and user account management.
## Setup and Configuration Managing reimbursements, adjustments, and cancellations are core administrative functions. They require no special system setup and are accessed directly through the individual user's profile within the administrative portal. ## Using this Feature Administrators must choose the correct financial action based on whether the transaction has been paid and what should happen to the associated items. ### [Cancel Transaction](https://opscom.wiki/books/the-opscom-admin-portal/page/cancel-transaction) Use this action to void a transaction **before** a payment is processed. - **When to use:** A user decides not to follow through on a promise to pay. - **System Impact:** The promise to pay is removed from the account, meaning the user no longer owes the money. The items associated with the transaction are immediately released back into the system inventory. ### [Adjustments](https://opscom.wiki/books/the-opscom-admin-portal/page/adjustments) Use this action to alter the cost of an item **before** it is paid for, or to alter the value of a transaction **after** it has been paid for. Adjustments can be positive (charging more) or negative (reimbursing a portion of the cost). - **When to use:** A user was charged too much or too little for an item, or they require a partial/pro-rated reimbursement because they are no longer using an item. - **System Impact:** The financial value of the transaction changes, but **items are not released back into the system**. ### Refunds For a detailed look at this process, see [What does a refund look like in the system?](https://opscom.wiki/books/the-opscom-admin-portal/page/what-does-a-refund-look-like-in-the-system). Use this action to return funds and cancel a transaction **after** it has been paid for. - **When to use:** A user has decided against a completed purchase, or the original transaction is completely incorrect and it is easier to reverse it and start over. - **System Impact:** The transaction is reversed, and **all transaction items are released back to the system**. --- ## Best Practices and Considerations - **Organizations should establish clear policies outlining when to use full refunds versus pro-rated adjustments** to ensure consistent financial reporting and customer service. - **Always verify the payment status of a transaction** before attempting to alter it, as this dictates whether a cancellation (pre-payment) or a refund (post-payment) is the appropriate action.**If there is more than one item in a transaction, processing a refund will reimburse and release ALL items associated with that purchase.** If you only need to reimburse a single item within a multi-item transaction, you must process an adjustment for the financial value and manually release the specific item separately.