Map receipts and invoices to your chart of accounts
untxt. proposes a chart-of-accounts mapping for each document as it reads it, drawing on the vendor, the document type, and the line detail. The suggestion lands in the review queue for you to confirm or change before anything posts.
A proposed mapping, ready to review
For each document, untxt. suggests where it belongs in your chart of accounts, so you are confirming a mapping rather than assigning every one from scratch. A fuel receipt comes up proposed as Motor Expenses, an office-supply invoice as Office Supplies, each shown in the review queue with the account it picked. The proposal is the starting point; the decision stays yours.
It reads the document to decide, not a rule you maintain
The suggestion comes from what the document is and what is on it, not a per-vendor rule you set up and keep alive. A new vendor gets a sensible proposed account the first time it appears, with nothing to configure.
You confirm, and you can change it
Mappings are proposals, not final posts. You confirm the ones that are right and correct the ones that are not, in the review queue, before it reaches QuickBooks or Xero. The account that lands is the one you approved.
Where your judgment still rules
Account choice often turns on client context untxt. cannot see: how a particular client treats a grey-area expense, a one-off reclassification, an internal convention. untxt. proposes a reasonable default and leaves those calls to you.