How to automate expense management in Priority

Key takeaways

• Priority's general ledger supports analysis by cost center, department, project, region and geography.
• Priority offers mobile time and expense capture with approval flows, positioned for professional services firms.
• Priority's site does not describe a corporate card feed or receipt reading for card spend.
• Vergo codes card spend by inference and records AP invoices through the Priority REST API, with employees set up as suppliers for reimbursements.

Where should you go next?

• Vergo's Priority integration
• What expense management software integrates with Priority?
• Get started with Vergo

How do you automate expense management in Priority, step by step?

1. Connect Priority. Vergo connects through Priority's public OData REST API; nothing is needed from the vendor.
2. Bring your existing cards. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
3. Text for receipts. Employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report.
4. Confirm the coding. Vergo proposes the account and the reporting dimensions for each line, showing which earlier transactions it learned from.
5. Record in Priority. Confirmed spend is written as AP invoices with their lines; reimbursements go to the employee as a supplier.

What does Priority need on each expense?

• GL account for the cost.
• Cost center or department, when management reporting is cut that way.
• Project, for services and project-based businesses.
• Supplier: the card issuer, the merchant, or the employee for reimbursements.

Where does Priority stop and automation start?

Priority's time and expense capture is designed around people logging their own costs and routing them for approval, which suits consultants billing hours. Company card spend is different: it happens whether or not anyone logs it, and the statement arrives with merchant names and nothing else. Someone still has to match each charge to a receipt, work out which cost center or project it belongs to, and key it. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought, then proposes the account and dimensions together.

A practical example

An engineering services firm on Priority has consultants on two client projects. One consultant books a hotel for the first project and buys test equipment for the second on the same card. Vergo texts for both receipts, proposes the travel account with the first project and the equipment account with the second, and cites how similar charges were coded last quarter. The project controller confirms, and both are recorded in Priority already analysed.

How Vergo handles this

Vergo proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. For Priority, the history Vergo learns from includes which cost centers and projects your team has used for each kind of purchase, so a consultant's hotel lands on the client project without anyone looking it up. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project — or skip approval flows entirely and let policy flags catch only what breaks a rule. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use.