Key takeaways
- JD Edwards job cost accounts are job, cost code and cost type; a header account (job and cost code only) is for rolling up, not for coding a receipt.
- Expense Entry lets an employee charge an expense to job cost, but someone still has to pick the right cost code and cost type.
- Vergo proposes the full account per receipt line and delivers it through Orchestrator.
- Crews text receipts; nobody fills out a report at the end of the month.
Where should you go next?
- Vergo's JD Edwards integration
- What expense management software integrates with JD Edwards?
- How to automate expense management in JD Edwards
- Get started with Vergo
Where do construction expense reports break in JD Edwards?
JD Edwards Expense Management lets an employee set the Charge To on each expense to a business unit, a job cost account with cost code and cost type, or a work order. That flexibility is the problem on a jobsite: a foreman knows the job but rarely knows whether the cost code for a rented trench box is excavation or shoring, or which cost type your estimators set up for small equipment.
The result shows up in Job Status Inquiry. Oracle describes it as the place to compare actual amounts against original and revised budgets, commitments and projected final cost. Every charge on the wrong cost code or cost type puts two lines of that view out of step with the field.
How do you automate it, step by step?
- Enable Orchestrator. IT enables access once. Vergo reads jobs, cost code structures and accounts, so it only proposes combinations that exist on the job.
- Connect the cards already in use. Vergo receives card transactions directly, so there is no F09E150 loader to build or keep running.
- Text the receipt. A superintendent sends a photo by text message. No app, no portal, and Vergo chases missing receipts itself.
- Propose the detail account. Vergo codes each line to job, cost code and cost type, or to a business unit and object for overhead spend, and shows why.
- Review the exceptions. Route by job, amount or GL account, or rely on policy flags alone.
- Deliver. Approved lines go in through orchestrations wrapping journal entry and voucher entry (P0411); reimbursements go as employee-as-supplier vouchers.
How is this different from general JD Edwards expense automation?
Outside construction, the hard part is the business unit, object and subsidiary. On a job, the object and subsidiary relationship is reversed and the cost code structure is copied onto each job from a chart type, so two jobs can carry different cost codes for similar work. Vergo learns from how each job was coded, so a proposal for the school job reflects the school job's structure, not the warehouse job next door.
A practical example
An electrical foreman buys wire, connectors and a rented lift on one card swipe for a tenant improvement job. Vergo proposes the job with the rough-in cost code and material cost type for the wire and connectors, and the same job with the equipment cost type for the lift, citing last month's rental from the same supplier. The project accountant confirms, and the split entry is delivered through Orchestrator.
Frequently Asked Questions
Does Vergo use the JD Edwards credit card interface table?
No. Vergo receives transactions from your existing cards and delivers coded entries through Orchestrator, so the F09E150 program is not needed for these cards.
Can one receipt go to two cost codes?
Yes. Vergo reads each line on the receipt and proposes a separate job, cost code and cost type where the lines belong to different work.
What about work orders and equipment?
Where spend belongs to a work order rather than a job, Vergo proposes that charge-to instead, based on how similar spend was coded.
Do foremen have to learn cost codes?
No. They text the receipt; Vergo proposes the coding and a reviewer confirms it.
