Bill pay: invoices that should not go on a card

How this layer fits

Bill pay is for vendor invoices that are a poor fit for cards: rent, payroll-adjacent vendors, large one-off professional fees, suppliers who will not take cards. The workflow is intake → code → approve → schedule → pay → reconcile.

When a card is the wrong rail

If the vendor charges a surcharge, if the amount is large enough to distort card limits, or if the invoice needs PO matching, use AP. Virtual cards remain useful for the vendors who will take them.

Approval chains

Match the chain to dollar thresholds and cost centres, not to job titles copied from another company. A three-step chain on a $40 domain renewal is how invoices sit untouched.

Handoff to the ledger

The same coding taxonomy should cover cards and AP. Split taxonomies are how month-end becomes a mapping project. See accounting.

Frequently asked questions

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.

1. Brex — official websitePrimary source for current product names, availability and terms.
2. Brex Support CenterOfficial help documentation, including account access and card administration topics.
3. Visa — commercial payment solutionsNetwork-level background on commercial card products and data levels.
4. Consumer Financial Protection Bureau — credit card resourcesBackground on card terminology, billing cycles and consumer-vs-commercial distinctions.
5. FDIC — deposit insurance and pass-through coverageReference for how deposit insurance applies, including through third-party arrangements.