Categorising transactions, and why we will not guess for you
You can categorise rows here, in bulk, before exporting. What you will not find is a model quietly assigning a category to every transaction — and that is a decision rather than a gap.
What you can do
Select any set of rows in the review grid and apply a category to all of them at once. Sort or filter first — by description, by amount, by whether the row reconciled — and the selection follows, so labelling every row from one merchant is two clicks rather than forty.
The label is written into exports that carry a category field, and shown against the row in the grid meanwhile.
Why automatic categorisation is not here
Because a wrong category is silent, and a missing one is not. A transaction posted to the wrong account looks completely normal in your books, is found weeks later during a review if it is found at all, and has to be traced back through a chart of accounts to fix. A transaction sitting in Uncategorised is visible in one report and reassigned in a single pass.
The same reasoning shows up in the exports themselves. An IIF file writes uncategorised rows to QuickBooks’ own holding accounts, and a Tally voucher posts to Suspense, precisely so nothing lands somewhere plausible and wrong.
This is a defensible position rather than a universal one. If your statements are repetitive and your tolerance for occasional misposting is high, a tool that guesses will save you time — and the closest competitors list auto-categorisation as coming soon rather than shipped, so the honest state of the art here is thinner than the marketing suggests.
Where categorisation belongs anyway
QuickBooks, Xero and Sage all have rule engines that categorise on import, learn from what you accept, and keep those rules in the place your chart of accounts already lives. That is a better home for the logic than a converter, which sees one statement and knows nothing about your accounts.
The useful thing a converter can do is get clean, verified rows into that engine. That is what this one tries to do.
No rules, no learning, no memory between statements
Categories applied here do not persist to the next statement, and there is no rule engine. If you need categorisation that remembers, it belongs in your accounting software, or in a tool built around it. We would rather say that than build a shallow version and let you find out.