---
title: "Delete TJM Transactions On The Fly"
slug: "delete-tjm-transactions-on-the-fly"
updated: 2026-05-29T06:26:29Z
published: 2026-05-29T06:26:29Z
canonical: "zenoplesupport.aqore.com/delete-tjm-transactions-on-the-fly"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://zenoplesupport.aqore.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete TJM Transactions On The Fly

When a Temp Job assignment is ended, the system now automatically removes eligible transactions for the current and upcoming accounting periods in real time without waiting for the overnight batch job to run.

Previously, the system created transactions in advance for the current and next two accounting periods. When an assignment ended, those pre-created transactions remained visible and required manual cleanup. With this enhancement, transactions that are no longer needed are removed automatically as part of the assignment-end action, helping maintain accurate time and billing records with no additional effort from the user.

**How It Works**

- **Automatic Cleanup on Assignment End**

When a user ends a Temp Job assignment, the system immediately evaluates and removes eligible transactions automatically. No separate action is required.

- **Transactions Removed**

The system only removes transactions that were automatically created by the system, are not included in any batch, and belong to the current open or future accounting periods.

**Transactions That Are Always Kept**

- Transactions manually created or copied by a user
- Transactions already added to a batch, regardless of whether hours were entered
- Transactions in a closed accounting period
- Transactions linked to an invoice or payment batch

**End Date Logic**

| End Date Scenario | Result |
| --- | --- |
| End date is in the past (before the current work week) | Eligible transactions in the current and all future periods are removed |
| End date falls within the current work week | Eligible transactions in future periods are removed while current-period transactions are kept |
| End date is a future date (beyond the current accounting period) | No transactions are removed immediately; the nightly batch job continues managing future transaction creation |

**Confirmation Messages**

| Outcome | Message Displayed |
| --- | --- |
| Eligible transactions were found and removed | "Assignment ended successfully. Non batch transactions deleted." |
| Only batch-tagged transactions existed | "Assignment ended successfully. Batch tagged transactions not deleted." |
| No eligible transactions were found or all transactions were manually created | "Assignment ended successfully." |

**Additional Notes**

- **All-or-nothing operation:** If an error occurs during transaction cleanup, the entire assignment-end action is reversed. The assignment remains active and no data is changed.
- **Reopened assignments:** If an ended assignment is reopened or its end date is updated, previously removed transactions are not automatically recreated. The nightly batch job will generate new transactions during the next scheduled run.
- **Temp Job only:** This enhancement applies exclusively to Temp Job (TJM) assignments. Direct Hire and Scheduled Job transaction flows are not affected.
- **End Reason setup unchanged:** The existing configuration and management of end reasons remain unchanged.
- **Copy Assignment:** When copying an assignment that has already been ended, transactions linked to the original assignment are also removed as part of the process.