---
module: transactions.processing-rules
title: Journal Processing Rules
tab: Customer
order: 10
audience: customer
---

This screen controls how HiveIQ reads the raw activity logs coming off your ATMs and turns them into recognizable transactions and system events. Use it when you want to add a new transaction type, fine-tune how activity is labelled, or teach HiveIQ to flag a specific machine event.

There are two lists on this page: **Transaction Types** and **System Events**. Both work the same way — the rules are checked from top to bottom, and the **first rule that matches wins**, so the order matters.

## 🧾 Transaction Types
Rules here decide how each customer transaction is labelled (for example WITHDRAWAL, DEPOSIT, or BALANCE).

**What you can do:**
1. Click **+ Add Type** to create a new transaction label.
2. Give it a **Type Name** (e.g. WITHDRAWAL).
3. Optionally set **JPR Contains** — a word or phrase that must appear in the journal text for the rule to apply.
4. Optionally set **Op Code Matches** — one or more operation codes (comma-separated) to match by code.
5. Use the **↑ / ↓** arrows to move a rule up or down and change its priority.
6. Use **Edit** to change an existing rule, or **Delete** to remove it.

> Leave **JPR Contains** blank to match any transaction content, and leave **Op Codes** blank to skip code matching.

## ⚙️ System Events
Rules here watch for machine-level activity outside of a transaction — things like the network dropping, power cycling, or a cassette running low. Each match raises an event of the type you choose.

**What you can do:**
1. Click **+ Add Event**.
2. Enter a **Pattern** — the text to look for in the log (you can list alternatives separated by a `|`, e.g. `HOST CONNECTED|HOST RECONNECTED`).
3. Pick an **Event Type** from the list (for example NETWORK_DISCONNECTED, POWER_OFF, ATM_OUT_OF_SERVICE).
4. Reorder, **Edit**, or **Delete** rules the same way as transaction types.

## What you're looking at
- **Order** — the priority of the rule; lower numbers are checked first.
- **Type Name** — the label applied to matching transactions.
- **JPR Contains** — the text that must appear for a transaction rule to match.
- **Op Code Matches** — the operation code(s) a transaction rule matches on.
- **Pattern** — the text HiveIQ searches for when detecting a system event.
- **Event Type** — the kind of event raised when the pattern is found.

## 💾 Saving changes
When you make a change, an **unsaved changes** notice appears. Click **Save & Apply** (in the header or at the bottom of the page) to put your rules into effect right away — no restart needed. Use **Reload** to discard your edits and load the last saved rules.

> Good to know: because rules are matched top to bottom, put your most specific rules near the top and your broad "catch-all" rules lower down.
