Train the AI to auto-categorize bank transactions
Reading time: 8 minutes
Learn how Atlas's AI engine categorizes bank transactions, how to review its suggestions, create custom rules, and read its performance metrics. By the end of this tutorial you'll know how to clear the AI Review queue quickly and confidently. Every screen below is the actual product.
Atlas categorizes the pending transactions in your bank feed (reconciled and already-matched rows are excluded — categorize those manually from the bank account page). Each suggestion gets a confidence score, shown as a percentage on its row.
The auto-apply threshold is 70%. That single cutoff drives the queue tabs:
| Confidence | Tier | Queue tab |
|---|---|---|
| 90%+ | High | Auto-Categorized |
| 70–90% | Medium | Auto-Categorized |
| Below 70% | Low | Needs Review |
Suggestions at or above 70% can be applied in bulk with Accept High Confidence; anything below 70% lands in Needs Review for a human decision.
The AI Review Queue with metric cards across the top and four pending transactions, each with a suggested GL account and a confidence badge.
Each row shows the Date, Description, Vendor, Amount, the suggested Account (an inline dropdown you can change), and the Confidence badge. The tabs — All Pending, Needs Review, Auto-Categorized, Uncategorized — filter the queue by status.
Expand a row to read the AI's reasoning for its suggestion:
An expanded transaction row showing the AI's plain-language reasoning for the suggested account.
Tip: Use Accept High Confidence to clear the bulk of the queue, then work through the Needs Review tab by hand.
Rules give you deterministic control: when a transaction matches a rule, Atlas assigns the account you chose.
The AI Rules page under Settings, with the New Rule entry point and an empty-state prompt.
| Rule Type | Matches on… | Example match value |
|---|---|---|
| Vendor (Exact Match) | The normalized vendor name, exactly | STAPLES OFFICE SUPPLIES |
| Vendor (Fuzzy Match) | The vendor name, approximately | Comcast |
| Keyword | A keyword anywhere in the description | AWS |
| Regex Pattern | A regular expression against the description | AMZN.* |
The Create AI Rule dialog: Rule Type (Keyword selected), a Match Value field, and an Account selector.
| Rule Type | Match Value | Account |
|---|---|---|
| Keyword | AWS | Cloud Hosting Expense |
| Keyword | GUSTO | Payroll Expense |
| Vendor (Fuzzy Match) | Comcast | Utilities Expense |
| Regex Pattern | STRIPE.* | Merchant Revenue |
Atlas summarises how the AI is doing on the AI Review → Metrics page (open it from the Metrics link on the AI Review queue):
The AI Review Metrics page with Accuracy, Categorized, Rule Coverage, and Corrections cards.
Import → Run AI Categorization → You Review → AI Learns → Better Suggestions
Every correction teaches the engine. As Rule Coverage and Accuracy climb, more transactions land in Auto-Categorized and clear with a single Accept High Confidence click. For vendors the AI keeps getting wrong, add a rule (Step 3) for deterministic control.
| Issue | Solution |
|---|---|
| Queue shows no confidence/N/A | Click Run AI Categorization and wait for the background job to finish |
| AI not suggesting anything | Need more historical data — categorize transactions manually first |
| A transaction never appears | Only pending rows are categorized; reconciled/matched rows are excluded |
| Wrong suggestions repeated | Add a rule in Settings → AI Rules to override the AI for that pattern |
| Rule not applying | Check the Rule Type and Match Value against the transaction's vendor/description |
Now that your AI is working: