---
module: transactions.reparse
title: Journal Reparse
tab: Overview
order: 10
audience: customer
---

Re-process uploaded journal files when transactions look wrong — for example duplicates, missing entries, or files that failed to read the first time. Use this after a fix has been applied so the affected files are read again and the transaction records rebuilt.

## 🗂️ Choose a Journal Type
1. Use the **ATM Journals** tab for standard ATM journal files.
2. Use the **TCR Journals** tab for teller cash recycler files.

> Each tab shows and re-processes only its own type of file.

## 📊 Check File Parse Status
1. (Optional) Type an **ATM ID** in the filter box to look at one machine, then click **Refresh**.
2. Review the coloured status pills for a quick count of how files stand, plus a **Total**.
3. Scroll the table for per-file detail.

**What you're looking at**

- **ATM** — the machine the file came from.
- **Date** — the journal date the file covers.
- **Status** — where the file is: *Parsed* (done), *Pending* (waiting), *Parsing* (in progress), or *Error* (failed).
- **Transactions** — how many transactions were read from that file.
- **Error** — a short note when a file failed to process.

## 🔄 Trigger a Reparse
1. (Optional) Enter an **ATM ID** to reparse just that machine. Leave it blank to reparse every ATM's files.
2. Click **Reparse All**.
3. Confirm in the pop-up — it tells you whether you're reparsing one ATM or all of them.
4. You'll see how many files were queued (for example "Queued 12 of 12 files").

> Reparsing removes the current transactions for the selected files and reads them again from scratch. Reparsing all ATMs can take several minutes.

## 🕐 Good to Know
- Processing runs in the background — files move through *Pending* → *Parsing* → *Parsed* on their own.
- Turn on **Auto-refresh** (top right) to have the status update every few seconds, or click **Refresh** to check progress yourself.