The receipt is now the classifier.
Upload a receipt and the AI reads every line on it — then suggests exactly how to split the transaction before you touch a single field. Historical suggestions now show a consistency ratio. Small purchases skip the receipt rule entirely. And the new Combine feature handles the case where one physical receipt maps to multiple card rows.
The classify page already had an AI suggestion panel and a receipt analyzer. They were useful but separate — one fired on the bank description when the transaction loaded, the other filled vendor and description after you uploaded a file. This update connects them. Upload a receipt first, and the AI does the classification work: it reads the line items, groups them by expense category, and proposes a split with pre-filled GL accounts and amounts. For transactions that don’t need a split, it still fills vendor, description, and property the same way it always has. And for the suggestion panel, the score behind each suggestion is now visible.
At the same time, two longstanding friction points on the receipt side are fixed: small charges no longer require a receipt, and the new Combine feature handles the case where one physical receipt covers multiple card rows — a gas pre-auth, a hotel deposit, or an Amazon order that ships in two pieces.
Receipt reads line items — and suggests splits automatically
When you drag a receipt onto the classify page, the AI now reads individual line items, not just the total. If it finds items from different expense categories — maintenance supplies and a capital item on the same Home Depot run, for example — a violet card appears with a proposed split: amounts per line and a suggested GL account for each.
Click Apply suggested split and the form is pre-filled with one line per category. Amounts sum to the transaction total. You review the property and any missing fields, then submit. If the suggested split isn’t right, dismiss the card and classify normally.
The AI sees your organization’s actual GL accounts when it reads the receipt, so suggestions reference account numbers from your chart of accounts — not generic categories.
Historical suggestions now show the score
The amber suggestion panel previously showed “Used Nx before” for the top match. Now every suggestion shows a ratio — 14 of 15× — so you can see at a glance how consistent the pattern is. 14 of 15 means this vendor has landed in the same GL account at the same property 93% of the time. 3 of 12 is a weaker signal worth reviewing before applying.
Suggestions are also ranked by your own classification history first. If you’ve personally coded this vendor to a particular account multiple times, your pattern surfaces above the company-wide aggregate.
Small purchases ($30 or less) skip the receipt rule
Any transaction whose total is $30 or less no longer requires a receipt or a “Reason for No Receipt” note. The field disappears entirely on small charges — you can still attach a receipt if you want one on file, but nothing’s required to save and submit.
The threshold is based on the original transaction total, not the per-line amount, so a split that sums to $25 also clears it. Approvers see the same rule — small purchases without a receipt shouldn’t be bounced back.
One receipt for many transactions: Combine
Gas station pre-auth plus the real charge. Hotel deposit plus the final folio. Restaurant bill plus the tip adjustment. Amazon orders that ship in two pieces. These all post as multiple card transactions but share a single receipt. Now there’s a Combine button right next to Split.
You classify and attach the receipt once; every combined transaction inherits the same property, GL account, vendor, description, and receipts. Submit, approve, return — they all act on the whole group together.
Admin: filter by confidence, toggle splits and combines
The Credit Card Settings page has three new sections. The AI Suggestion Confidence Levels card lets admins independently enable or disable High, Medium, and Low confidence suggestions. High is ≥80% consistent with ≥5 prior classifications; Medium is 40–79% or a short perfect history; Low is everything below that. Low confidence is off by default to reduce noise.
The Splits & Combines card adds on/off toggles for both features independently. Disable splits if your workflow doesn’t need them; disable combines if you prefer transactions to stay independent. Both default to on.
Suggested workflow with the new receipt analyzer
- Upload the receipt first — drag it onto the classify page before touching any fields. The AI reads it within a few seconds.
- If a split is suggested, a violet card appears. Review the proposed lines and amounts. Click Apply suggested split if it looks right — or dismiss and classify as a single line.
- Check the amber suggestion panel for a historical match. The ratio tells you how reliable it is. Apply if the score is high; choose manually if the history is thin or mixed.
- Fill any remaining fields — the property usually needs your confirmation even when the GL is obvious. Submit.
How to combine, step by step
- Classify the largest of the related transactions first. Pick the property, GL account, vendor, description, and attach the physical receipt the same way you always have.
- Click Save & Next so the classification is committed. Combine applies the saved lines — if you have unsaved edits open, the modal will ask you to save first.
- Re-open the transaction and click Combine with other transactions at the top of the classification area.
- Tick the related transactions in the picker. Only same-statement, same-card, same-cardholder rows show up. Already-classified rows have a yellow “Will be overwritten” badge so you know you’re replacing their existing coding with the group’s.
- Click Combine. The classification and the receipt automatically flow onto every selected transaction.
After combining, every member transaction shows a green pill on the classify page indicating the group it belongs to. The button itself flips to Uncombine so you can dissolve the group if you change your mind.
Worked example — gas station fill-up
You fill up at Speedway on a Tuesday. The pump pre-authorizes $1.00, then settles to $43.17 the next day. Two card transactions arrive in your queue: a $1.00 pre-auth and a $43.17 final.
- Classify the $43.17 transaction first (Speedway, Fuel & Auto GL, the property you were driving for, snap the photo of the pump receipt). Save & Next.
- Re-open it. Click Combine with other transactions.
- The $1.00 pre-auth appears in the picker. Tick it. Click Combine.
- Done. Both transactions now share your Speedway receipt and your fuel classification. Submit sends them both up for approval; one Approve from your manager covers both.
Worked example — hotel stay
A two-night hotel stay with a $200 deposit charged on April 28 and a $487.30 final folio on May 2. Both rows on the same statement. The $200 deposit by itself isn’t a meaningful business expense — it’s part of the lodging total.
- Classify the $487.30 final folio with the full hotel context — property, GL account, attendees if it’s a meal-eligible trip, and attach the folio PDF.
- Combine the $200 deposit into it. Both rows now share the folio.
Combining across statements isn’t supported. A combined group has to live inside a single statement period — if the deposit and final fall on either side of a statement close, classify the deposit on its own statement and the folio on the next.
Undoing a combine
Click Uncombine on any member transaction to dissolve the group. Every member keeps the classification it currently has — nothing is reset — but the rows go back to being independent.
Returning a combined transaction from the accounting page also dissolves the group automatically so you can re-classify pieces separately.
What approvers see
Combined transactions appear with the same green “Combined N/M” badge on the Approvals queue and the Accounting export. One Approve covers every member of the group; one Reject or Return sends every member back at once and dissolves the group, so each row can be re-classified on its own afterwards. Verify the shared receipt covers the full combined total before approving — that’s the only added review step.
Split and Combine are mutually exclusive
A transaction can be a Split (one charge → many GL lines) or a member of a Combine (many charges → one classification), but not both. The button for the opposite operation is disabled with a tooltip explaining why. If you need to switch a transaction from one mode to the other, dissolve the current state first.
Same accounting integrity, less busywork.
Each transaction still posts its own GL entry — the bank reconciles transaction by transaction, and that doesn’t change. What does change is how often you re-upload the same file or re-type the same classification.