- The ledger stays the system of record; the spend platform is a feeder system.
- Mapping should be agreed before launch and tested with a real period.
- Cost centres and categories must be consistent across cards, expenses and payables.
- Sync direction and error handling matter more than sync frequency.
- Accruals still require judgement — no integration removes that.
Where the boundary sits
A spend platform captures transactions and enriches them with documentation and coding. The accounting system records them in double entry, applies accounting policy and produces financial statements. The boundary between them should be explicit and stable.
Blurring it is a common and expensive mistake. When two systems both claim to be the source of truth for a number, reconciliation becomes a negotiation and audit becomes difficult.
Mapping the chart of accounts
Mapping is a one-time design decision with a long tail of consequences. Every category in the spend platform must correspond to exactly one ledger account, and every cost centre must correspond to a real dimension in the accounting system.
Where the mapping is ambiguous, the platform will guess, and someone will spend the first week of every month correcting those guesses.
- One category, one account — never a category that could reasonably map to two.
- Cost centres mirrored exactly, including the ones nobody uses yet.
- Tax codes mapped explicitly, including the zero-rated and exempt cases.
- A documented default for anything that does not match, so nothing silently disappears.
Questions to ask about any integration
| Question | Why it matters |
|---|---|
| Which direction does data flow? | One-way feeds are simpler; two-way sync creates conflict resolution problems |
| What happens when a sync fails? | Silent failures are the worst outcome — you need visible, actionable errors |
| Can a synced entry be corrected? | Determines whether fixes happen in the ledger or upstream |
| How are periods closed? | The integration must respect a closed period rather than posting into it |
| What identifiers are used? | Stable identifiers make reconciliation and audit trails possible |
| Is there an audit trail? | You need to show who changed what, and when, after the fact |
Accruals and cut-off
Card transactions post when they settle, which is not always the period in which the expense belongs. Cut-off handling — deciding which period a transaction falls into — remains a judgement call informed by the transaction date, the invoice date and accounting policy.
The practical approach is to define a cut-off rule, apply it consistently, and document material exceptions. An integration can supply the data but cannot make the policy decision.
What close-ready actually means
“Close-ready” is used loosely in product marketing. In practice, an export is close-ready only if a controller can post it without editing anything.
- Every transaction has an account, a cost centre and a tax code.
- Every transaction above the documentation threshold has a receipt attached.
- No transaction is in an unresolved or pending review state.
- Totals agree with the card statement and the account statement.
- Any manual adjustment is documented with a reason.
Frequently asked questions
No. It feeds the general ledger with coded, documented transactions. The accounting system remains the system of record and produces the financial statements.
Daily is comfortable for most companies. Frequency matters far less than error visibility — a weekly sync you trust beats a real-time sync that fails silently.
The controller or whoever owns the chart of accounts. Mapping decisions made by an implementation team without accounting input are the most common cause of a messy first close.
Fix it before integrating. Mapping a disorganised chart of accounts into a new system reproduces the disorder with more automation behind it.
Keep reading
Sources and further reading
Every factual statement on this page is checked against primary documentation. Terms change frequently, so confirm details with the provider before acting on them.
- Brex — official website Primary source for current product names, availability and terms.
- Brex Support Center Official help documentation, including account access and card administration topics.
- FASB Accounting Standards Codification Reference point for accrual, expense recognition and close-process statements.
- IRS Publication 463 — travel, gift and car expenses Used for statements about expense substantiation and record keeping in the United States.
- FASB Accounting Standards Codification Reference point for accrual, expense recognition and close-process statements.