Key takeaways
- In PeopleSoft, a job cost is only a job cost if it reaches Project Costing with a PC business unit, project and activity attached.
- Vergo ranks first for contractors on PeopleSoft because it proposes those project ChartFields per line and keeps your existing card program.
- Travel suites such as SAP Concur and Emburse fit programs driven by travel booking rather than jobsite purchasing.
- Ramp and Brex bundle expense software with a move to their own cards.
Where should you go next?
- Vergo's PeopleSoft integration
- What expense management software integrates with PeopleSoft?
- What is the best expense management software for PeopleSoft users?
- Get started with Vergo
Which expense tools rank best for PeopleSoft contractors?
- Vergo: best overall for construction on PeopleSoft. Proposes project ChartFields and the GL string from your own history, collects receipts by text message, works on your existing cards, and posts coded spend as voucher and Journal Generator entries through PeopleSoft's documented services.
- SAP Concur: best where corporate travel drives the program, with bank card feeds and 300+ pre-built connectors.
- Emburse: best for large travel and expense programs, with Emburse Spend running alongside existing Amex, Mastercard or Visa programs.
- Ramp: best for contractors ready to replace their card program with the Ramp Visa card.
- Brex: best for companies that want Brex Mastercard cards, bill pay and banking in one place.
How do they compare on job cost coding?
| Option | Cards | Project ChartFields | Route into PeopleSoft |
|---|---|---|---|
| Vergo | The cards you already have | Proposed per line from your own coding history, with the reason shown | Voucher and Journal Generator entries posted through Integration Broker services |
| SAP Concur | Existing cards through bank card feeds | Ask how project, activity and source type are captured | Pre-built connectors; confirm PeopleSoft coverage |
| Emburse | Existing programs or Emburse cards | Ask how project ChartFields are captured | Ask how entries reach PeopleSoft |
| Ramp | Ramp Visa card | Ask how project ChartFields are captured | Ask how entries reach PeopleSoft |
| Brex | Brex Mastercard cards | Ask how project ChartFields are captured | Ask how entries reach PeopleSoft |
What makes construction different in PeopleSoft?
Most PeopleSoft expense content is written for universities, hospitals and government. Contractors use the same ledger differently. The spend that matters is not travel; it is fuel, small tools, equipment rental, permits and materials bought at the supply house by a foreman who is on the job, not at a desk.
PeopleSoft's own documentation describes how Expenses feeds Project Costing: expense lines are charged to project-related ChartFields such as PC business unit, project, activity, source type, category and subcategory; approved and posted expenses land in the Expenses Accounting Line table; and the PC_EX_TO_PC process pulls them into Project Costing. Payables works the same way for vouchers: a distribution line that carries a project needs, at minimum, the project business unit, project ID, activity ID and resource type. If any of those are missing or wrong, the cost never shows up against the job.
What should a contractor on PeopleSoft look for?
- Activity-level accuracy. Charging the right project but the wrong activity still distorts cost-to-complete. The tool should propose the activity, not leave it for the reviewer.
- Line-level splits. One supply-house receipt often serves two jobs. The tool has to split the charge across projects before it reaches PeopleSoft.
- Field-first receipts. Superintendents will not log into a portal at the end of a shift. Receipt capture has to work where they already are.
- Your card program intact. Many PeopleSoft organisations run negotiated purchasing card programs whose rebates fund real money; switching is a treasury decision.
Why does Vergo rank first here?
Vergo reads each receipt line by line and predicts the coding from what was bought: the account and department, and on job spend the PC business unit, project, activity and source type your team used for similar purchases. No rule library, no keyword lists; a new vendor is coded on first sight, and every proposal shows why it was chosen. Vergo reads your ChartField values through PeopleSoft's documented Integration Broker services, so proposals stay inside the projects and activities that are open. Coded spend is posted as voucher and Journal Generator entries through those services. Vergo does not issue cards: connecting the cards you already have involves no card applications, no re-issuing and no banking change.
Frequently Asked Questions
Can Vergo code card spend to PeopleSoft Project Costing?
Vergo proposes the PC business unit, project, activity and source type for each job-related line, based on how your team coded similar spend, and includes them in the voucher and Journal Generator entries it posts.
Do we need to change our purchasing card program?
No. Vergo works on the corporate and purchasing cards you already have, so rebates and credit terms stay where they are.
How do field crews submit receipts?
By text message. There is no app to download and no portal login, and Vergo chases missing receipts itself.
Can one receipt be split across two projects?
Yes. Vergo reads the receipt line by line and proposes a separate project and activity for each line, so the split is done before anything reaches PeopleSoft.
Does Vergo replace PeopleSoft Expenses?
It can sit in front of it or replace the card-coding work entirely; either way PeopleSoft stays the system of record for Project Costing.
