Categorize Brex Expenses Into the GL

For a controller who wants categorization done before close kicks off. One prompt pulls the week's Brex transactions, assigns GL codes based on vendor + amount patterns, and flags the uncategorizable for human review.

Brex logoBrex
Google Sheets logoGoogle Sheets
THE GRIND

Categorization eats the first day of close

Every Brex transaction needs a GL code. Most patterns repeat — but picking them out of 140 transactions still takes hours, and the edge cases always get mis-coded.

Manually matching vendor names to GL codes

New vendors get mis-classified as miscellaneous

The reviewable queue lives in someone's notes app

Composio collapses all of this into one prompt — here's what that looks like.

THE FLOW
5 steps · 2 toolkits

Your agent runs it end-to-end.

  1. 01
    List the week's Brex transactions with vendor + amount + category
    brex logo
  2. 02
    Apply GL codes based on vendor patterns and amount thresholds
  3. 03
    Append categorized rows to the Expense Ledger sheet
    googlesheets logo
  4. 04
    Flag anything ambiguous — new vendor, odd amount, mismatch
  5. 05
    Post the review queue to a second sheet tab
    googlesheets logo
THE PAYOFF

Close starts on day two, not day five

Categorization is done before the close meeting. Reviewers get a short list of edge cases, not 140 transactions — and the ledger ties out on the first pass.

Paste this into Claude, Cursor, or Codex. It'll install the CLI, connect your apps, and run the task — end to end.