Suggest accounts for uncategorised ledger transactions

A draft coding suggestion table with a suggested account, confidence and similar past transactions for each line.

Choose one of three approaches. The steps for that option appear below.

Choose an option above. On a phone, swipe the tabs left or right to see all options →

ChatGPT: matches past codings and suggests accounts

ChatGPT matches uncategorised lines to past codings in one pass. You check every suggestion; nothing posts until you approve.

  1. You

    Get tables ready

  2. ChatGPT

    Suggest accounts

  3. You

    Check and approve

  1. Get the three tables ready

    Use: You

    Have ready: uncategorised transactions, chart of accounts and past coding examples.

  2. Suggest accounts and flag conflicts

    Use: ChatGPT

    Upload the tables. Ask ChatGPT for a suggested account, confidence and up to three similar past transactions per line; flag supplier conflicts and new-account needs.

    Details

    What to paste into the tool

    For each uncategorised transaction suggest one account from the chart, a confidence of high, medium or low, and the past transactions you relied on. If none is close, answer no suggestion. Suppliers are shown as codes; do not use the supplier code alone. List suppliers whose past codings conflict instead of averaging them, and transactions with no suitable account.

  3. Check the table, approve or hold each line

    Use: You

    Have ready: your ledger records. Check suggestions and conflict flags against them. Decide new accounts with the accountant. Approve or hold each line.

    Check

    A supplier alone does not decide the account. Low-confidence and conflicted rows get a decision, not an average. Coding corrections post in the ledger. Nothing posts from this table until you approve. Review the generated code and assumptions.

Before you paste into any AI tool, remove any confidential information. Put it back at the end.

Tools in this workflow

Deciding between ChatGPT and Claude for this? See the comparison.

Final check

Never paste credentials or full payment details.

Every transaction gets a suggestion or an explicit no-suggestion verdict. Suggestions cite similar past codings. The bookkeeper confirms or corrects each line before posting. Supplier coding conflicts are flagged, not averaged.

Nothing is posted to the ledger from the table.

Check the result against your original inputs. Approve it before sharing or acting.

What still needs checking
  • Pricing and plan limits beyond the quoted plan statements for the tools listed were not read for this proposal.

Share this page