Key takeaways
- In PeopleSoft, an expense line is only finished when its ChartFields are right: account plus whichever of department, operating unit, fund, program, product and project your ledger uses. Business unit sits alongside them, not inside.
- PeopleSoft Expenses loads card supplier files into each employee's My Wallet, and supplier expense types have to be mapped to PeopleSoft expense types. The coding itself still falls to a person.
- Vergo proposes the ChartField coding from how your team coded similar spend before, shows why, and chases the receipt by text message.
- Coded spend is posted as voucher and Journal Generator entries through PeopleSoft's Integration Broker services, so nobody re-keys it.
Where should you go next?
- Vergo's PeopleSoft integration
- What expense management software integrates with PeopleSoft?
- Get started with Vergo
How do you automate expense management in PeopleSoft, step by step?
- Connect PeopleSoft. Vergo connects through PeopleSoft's documented Integration Broker services and reads your ChartField values, business units and suppliers, so every proposal is a combination PeopleSoft will accept.
- Connect the cards you already have. Connecting your existing cards involves no card applications, no re-issuing and no banking change. The card program your treasury team negotiated stays in place.
- Capture the receipt at the moment of spend. The cardholder gets a text, replies with a photo, and Vergo matches it to the transaction. Nobody logs into a portal to do it.
- Code every line to ChartFields. Vergo proposes the account, department, operating unit and project for each line from your own history, and a reviewer confirms instead of typing.
- Deliver to PeopleSoft. Vergo reads your ChartField values through PeopleSoft's documented Integration Broker services and posts coded spend as voucher and Journal Generator entries through those services.
What does PeopleSoft need on each card transaction?
PeopleSoft's general ledger is built on ChartFields, and Oracle's documentation is specific that business unit is not one of them. A card line that is ready to post typically carries:
- Account: the natural expense account, and an alternate account where statutory reporting uses one.
- Department and operating unit: who spent it and where, which drives budget checking and management reporting.
- Fund, program and product: used heavily by public sector, higher education and nonprofit PeopleSoft ledgers.
- Project: for spend that belongs to a capital project or a grant.
PeopleSoft Expenses can default these from the employee profile, which is right for the traveller's home department and wrong for the conference booked on behalf of another team. That gap is where review time goes.
Where does PeopleSoft Expenses stop and automation start?
Oracle documents a solid card path: supplier files load into My Wallet, employees pull wallet lines into an expense report, and receipts can be attached from a phone through the Fluid interface. What it does not do is decide the coding for a line it has never seen. A new supplier, a split purchase or a charge that belongs to a project still waits for someone to pick ChartField values. Vergo takes that decision on: it reads the receipt line by line, proposes the values, and explains each proposal so the reviewer confirms rather than researches.
A practical example
A university research administrator buys lab supplies on a department card. The card file lands in PeopleSoft overnight with the merchant name and amount, and nothing else. Vergo texts the cardholder for the receipt, reads the lines, and proposes the research department, the grant project and the supplies account, because that is how the last three purchases from the same supplier were coded. The reviewer sees the reason, confirms, and the entry is posted to PeopleSoft with the ChartFields already set.
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 PeopleSoft that means proposals built from the ChartField combinations your ledger already uses, not from a generic category list, and every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Transactions are ready to code the moment they happen — no waiting for clearing — and once they clear, they sync into PeopleSoft.
Frequently Asked Questions
Does Vergo replace PeopleSoft Expenses?
It can sit alongside it or in front of it. Some organisations keep PeopleSoft Expenses for travel reports and use Vergo for card spend; others run all card spend through Vergo. Either way PeopleSoft stays the system of record.
Which ChartFields can Vergo code to?
The ones your PeopleSoft ledger uses. Vergo reads your ChartField values and proposes account, department, operating unit, fund, program, product and project where they apply, with the reason for each.
How do coded transactions get into PeopleSoft?
Through PeopleSoft's documented Integration Broker services. Vergo posts coded spend as voucher and Journal Generator entries through those services. Details are on the PeopleSoft integration page.
Do we need to change our corporate card program?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
Can reimbursements run through the same process?
Yes. In Vergo, 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.
