Start the close on day two, not day five

Email Carly and she'll pull the week's Brex transactions, assign GL codes based on vendor and amount patterns, and flag the ambiguous ones for human review — so close starts on day two, not day five.

Brex Google Sheets

What Carly does

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

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.

Email this to Carly to kick it off.

Hey Carly,

Can you categorize last week's Brex transactions into the GL for me? Pull every charge with vendor, amount, and category, then apply GL codes based on the vendor patterns and amount thresholds we usually use.

Append the categorized rows to the Expense Ledger sheet, and put anything ambiguous — new vendors, odd amounts, mismatches — on a second tab so I can review the edge cases instead of all 140 transactions.

Thanks!

More recipes for finance & ops teams

Reconcile Stripe payouts against the GL

Match payouts to Xero bank lines, calculate variance, post anything over $50 to #finance.

Read →

Route a PO to the right approver

Policy + threshold check, route to designated approver, ping in Slack with a 2-line summary.

Read →

Draft the monthly close memo

NetSuite + Stripe into a Notion memo with revenue, OpEx variance, runway, and open items.

Read →