# How to use a Righthand with Brex

Prepare a reviewed receipt-and-transaction exception packet from approved Brex inputs, with a worked example, complete brief, access checks, and reconciliation.

By Righthand Team · 2026-10-10

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-brex

## Quick answer

Use Righthand to organize an approved Brex transaction slice and receipt register into a review packet. The useful first task is finding mismatched evidence, not assigning accounting treatment or changing spend controls.

Start with a **receipt-and-transaction exception packet** that the finance reviewer can check against the original records. Righthand prepares the review artifact; the source application remains the operational record.

## Establish the input route

Brex documents date-range transaction downloads separately from PDF statements; transaction reports can be downloaded in spreadsheet formats. [Official Brex reference](https://www.brex.com/support/documents-for-your-account), checked October 6, 2026.

Have the finance owner select one account and download a bounded transaction report. Supply only the fields needed for this review plus an approved receipt register; omit complete card credentials and unrelated employee information.

Check the current [integration directory](/integrations) and [Righthand setup documentation](https://docs.righthand.ai/introduction). A listed app does not establish every read or write action. For a connected route, verify the assigned account, available operation, object scope, and one permitted sample read. This guide also works from an explicitly supplied, approved extract; it does not require an unverified native operation. Keep credentials out of the article brief.

## Worked input and output

These three records are synthetic illustrations, not customer results or a hands-on integration test.

| Approved input | Proposed review output |
| --- | --- |
| B-101: USD48.00 posted; receipt shows USD48.00 | Link receipt to transaction; retain reviewer confirmation |
| B-102: USD76.00 posted; no supplied receipt | Request missing support from the named finance owner |
| B-103: EUR30.00 transaction; USD30.00 receipt | Flag currency mismatch; do not treat equal digits as a match |

The packet should have separate columns for transaction evidence and supporting-document evidence. B-102 is not automatically an invalid expense: it is a missing-document question. B-103 needs the original currency context before any reviewer can explain the difference.

## A complete first-run brief

> Use an approved Brex transaction report and receipt register for October 12–16, 2026. Fields: transaction ID, account reference, merchant, posting date, amount, currency, receipt ID, receipt amount. At Monday 9 AM America/Los_Angeles, prepare a receipt-and-transaction exception packet as source-linked Markdown in my private review thread. Preserve record identities and the extract timestamp. Group unresolved items by next action and responsible owner. Reviewer: finance reviewer. Do not approve expenses, post journal entries, change limits, issue cards, or move money. Result check: Compare transaction count and totals by currency with the supplied report; independently inspect all receipt links.

A permitted preparation step does not authorize a consequential write or an external send. Resolve proposed changes through the app's supported process after the responsible owner approves their exact scope.

## Reconcile before widening the task

Keep posting date separate from purchase date. A pending card entry and its later posted entry can represent the same underlying purchase, so do not double-count them without the source identities. Missing receipt access should remain a visible gap.

Run the packet before one finance review meeting. Ask the reviewer to resolve B-103 using the actual source, then record the accepted explanation in the approved finance workflow. Expand to another account only after the first packet preserves its currency and account boundaries.

For the first acceptance review, keep the original input slice beside the result and mark which items were checked. If access or evidence is incomplete, return that gap with its record identity rather than a confident completion statement. Review [Pricing](/pricing) using the actual preparation workload and correction effort.