Brex purchase orders are built by hand, one line at a time, under Vendors.
PDF, JPG, PNG, BMP, HEIC, TIFF
Submit your purchase orders
Drop documents here, or choose a file
Up to 50 files per batch
Uploading...
Brex purchase orders are built by hand, one line at a time, under Vendors. When the order already exists as a PDF (an open PO from your old system, a supplier quote, a signed order form), upload it here and get every line with description, quantity, rate and total as a spreadsheet you can key from or check against.
The Brex help article on managing purchase orders describes two ways in: an admin creates the PO under Vendors, or an approved Wallet request becomes a draft PO the admin completes. It does not describe an import. Every line item is entered as description, quantity, rate and total.
Switching to Brex mid-year leaves a stack of open purchase orders in the old system. With no import described, each one is rebuilt by hand.
The supplier quote that justifies the spend request has the lines you need, but in the supplier layout, not as rows.
Brex suggests a PO for each bill based on vendor, amount and dates. A mistyped rate makes the totals disagree and the suggestion goes to the wrong PO or none.
Brex closes a PO once its total amount is reached. A total keyed too low closes the order before the last delivery is billed.
Upload the order, quote or old PO as it is. The AI reads the header and every line on every page and returns one row per line with the four values a Brex PO line uses.
Each line comes back in the same four values the Brex PO form asks for, plus the item number in its own column.
Order date and any expiry or delivery date are read into their own fields, ready for the issue and expiry dates on the Brex PO.
Line totals and the order total sit side by side, so a mismatch shows up in the sheet, not after a bill is matched.
Upload up to 50 open POs at once when you move from another system, and get one sheet per order or one combined file.
A 60 person company moves its card and bill pay to Brex in October with 40 purchase orders still open in its old accounting system. The average order has 9 lines. Rebuilding them means 360 lines of description, quantity and rate typed into Brex, at roughly 45 seconds a line once you count switching windows and checking, which is about 4.5 hours of admin time with real odds of a transposed digit.
Export the 40 open POs from the old system as PDFs, upload them in one batch, and review the rows on screen. The admin then keys each Brex PO from a sheet whose totals already match the original, or simply checks the Brex PO against the sheet before sending it. The keying does not disappear, but the reading, retyping errors and recalculation do. Teams still choosing a spend platform can compare plans in our Brex pricing guide, or see the same PDF to rows workflow for Ramp purchase orders.
Fields listed in the Brex help article on managing purchase orders, and the matching value we read from the document. Confirm the exact form in your own Brex account, since the feature is marked early access.
| Brex PO field | Read from the PDF | Note |
|---|---|---|
| Vendor name and contact | Supplier name, email, address | Pick the existing Brex vendor if there is one |
| Issue date | Order date | Use the original date for migrated POs |
| Expiry date (optional) | Valid until or delivery date | Blank when the PDF has none |
| Vendor memo (optional) | Notes and terms | Shipping or payment terms usually live here |
| Line description | Item number and description | Kept in separate columns |
| Quantity, rate, total | Quantity, unit price, line total | Check line totals add up to the PO total |
Four steps from a PDF order to a Brex purchase order you trust.
Drop in old POs, supplier quotes or signed order forms. Scans and multi-page files work.
Tip: Batch all open POs in one go for a migration.
Check vendor, dates and every line on screen, and compare the line totals with the order total.
Tip: Fix units of measure before you key anything.
Save as Excel or CSV with the same columns every time.
Tip: One tab per vendor keeps the Brex vendor profiles tidy.
Create the PO under Vendors from the sheet, or compare the draft PO from an approved request against it before you issue it.
Tip: Check the PO total last, since Brex closes the PO when it is reached.
Yes. Admins create purchase orders under Vendors, or turn an approved Wallet spend request into a draft PO, then email or download it for the vendor. The Brex help article marks the feature as early access and asks admins to contact Brex Support to turn it on.
The Brex help article describes a two-way match. When you pay a bill, Brex tries to match it to a PO by vendor, amount and dates, and warns when the bill is larger than the remaining balance. Receipts or goods received are not mentioned, so plan three-way checks yourself.
The Brex help article lists manual creation and draft POs from approved requests, and does not describe a file import or ERP sync. Ask Brex Support for your account. Until then, reading the PDF into rows first is the fastest way to rebuild open POs accurately.
Brex lists Essentials at $0 per user per month, Premium at $12 per user per month, and Enterprise with custom pricing. See our Brex pricing guide for what each plan includes and a worked yearly cost.
No. PurchaseOrders reads the purchase order PDF and returns Excel, CSV or JSON. It does not log into Brex or create POs there. You key the PO in Brex from the checked sheet or compare a draft against it.
Choose your plan