Airbase vs Procurify When Every Cost Has to Trace to a Matter

Most spend platforms default to routing purchases by department: litigation, corporate, real estate. That works for a firm's own software subscriptions, but it doesn't work for disbursements, the filing fees, deposition costs and expert fees a firm advances on a client's behalf and later bills back. Those need to trace to a specific matter number, not a department, because two litigation matters can have wildly different reimbursement terms depending on the engagement letter.

A platform that only supports department-level tagging will leave your billing coordinator manually re-sorting disbursements by matter every month, which is exactly the reconciliation work a spend platform is supposed to remove.

Airbase's card-first model works well for the firm's own recurring costs: research database subscriptions, document management licenses, office supplies. An office manager or practice group lead gets a card with a category limit and buys what the firm needs without a request cycle. Custom fields can capture a matter number on a transaction, but nothing forces an attorney to fill it in before the card charge clears, so a rushed filing fee paid on a firm card can still land in the general ledger unlabeled unless someone catches it.

Procurify's request-first flow asks for the matter number before anything is approved, which fits a firm where most non-recurring purchases need to be traceable to a specific client engagement for billing purposes. An associate requesting an expert witness retainer names the matter and the billing partner approves it, so the disbursement is correctly tagged from the start rather than reconstructed at invoice time. The tradeoff shows up on urgent items: a court filing due in two hours doesn't wait well for an approval queue, so firms using any approval-based procurement tool typically plan a faster path for true emergencies.

A workable split for most firms: let recurring, non-billable firm overhead run through Airbase-style card controls, because speed matters more than matter-level tagging for a research database renewal. Route anything that could become a client disbursement, filing fees, expert costs, deposition transcripts, through a request-first flow that captures the matter number before the money moves, whether that's Procurify or a policy layered on top of Airbase's custom fields.

Firms with a high volume of small disbursements across many active matters tend to find the request-first model earns back the time it costs in slower approvals, because every dollar it captures correctly is a dollar the firm doesn't have to write off as an unbilled cost at matter close.

Say a firm applies the same approval chain to a $40 office-supply order and a $15,000 expert witness retainer, on the theory that consistency is simpler to explain to staff. In practice that either slows down routine purchases to the point that people avoid the system, or lets large disbursements slip through a fast-approval path meant for small recurring costs. A better approach sets a lower dollar threshold for automatic approval on categories that are never client-billable, and requires the matter number and partner sign-off only on the categories that actually get rebilled.

Start with the categories that are least ambiguous: filing fees and court costs are always client-billable and rarely urgent enough to need same-day card access, so they're a safe first category to route through a request-first flow. Firm overhead, legal research subscriptions, document management, office supplies, is almost never client-billable, so it's a safe first category to leave on fast card-based purchasing. The harder middle category, expert witnesses, e-discovery vendors, court reporters, is where most firms spend the first few months tuning the rule, because those costs are sometimes billable and sometimes absorbed depending on the engagement letter, and getting that default wrong in either direction either frustrates a billing partner or costs the firm real recoverable revenue.