Transaction categorization

Coding reads your own chart of accounts, your vendors, your classes and the way you have coded similar transactions before.

A generic model does not know that you split a particular supplier across two accounts, or that a recurring charge belongs to a class. Yours does, because it is reading your books.

Each transaction is matched to the bill or receipt that accounts for it, so the money and the paperwork land on the same record.

The usual arrangement — documents in one queue, transactions in another — is why missing paperwork is only obvious at close. Matching them as they arrive moves that discovery weeks earlier.

A duplicate, a coding mistake, an amount out of line with what that vendor normally charges, a transaction with no supporting document — each is raised rather than silently posted.

What counts as worth raising is set by your thresholds and rules.

By the time you reconcile, the coding is done, the documents are attached and the exceptions are already marked.

Reconciliation becomes a review of prepared work rather than the point at which you discover everything that went wrong.