Translating Job Cost, Contract and Service Billing into project management and accounting

How JD Edwards Job Cost — where a Job is literally a Business Unit, and the Cost Code/Cost Type axes live inside the Object and Subsidiary segments of the account key — maps onto D365 Project management and accounting, including budgets, projected final cost, commitments, Contract and Service Billing, revenue recognition, and the Project Operations decision.

What you will be able to do

• Explain why a JD Edwards Job is a Business Unit, and what that means for D365 project, cost-centre and dimension design
• Decompose a Job Cost account key into Cost Code, Cost Type and the D365 constructs each becomes
• Map original, revised and projected final cost budgeting onto D365 project budgeting and forecasting
• Distinguish Contract Billing from Service Billing and place the F4812 workfile against D365 billing rules and on-account transactions
• Reproduce percentage-of-completion revenue recognition and WIP behaviour in D365
• Decide between Project Operations and Project management and accounting for a Job Cost site

Introduction

JD Edwards EnterpriseOne organises project accounting differently from almost every other ERP in this series, and the difference is not cosmetic. Job Cost, the module that tracks project cost, does not have its own master record for a project.

The Job Cost spine: when the project is the business unit

Every JD Edwards Business Unit lives in F0006, carrying a description, company, and up to thirty category codes used for roll-up reporting — by region, by business line, by responsibility.

Cost Code and Cost Type: the account key as work breakdown structure

JD Edwards has no separate work-breakdown-structure table for a job. The breakdown lives inside the account key itself, in the Object and Subsidiary segments of the Business Unit.Object.Subsidiary account.

Budgets, forecasts and the projected final cost

Job Cost tracks several cost "buckets" side by side for every account: Original Budget, Budget Changes (approved revisions), a running Revised Budget, Actual cost (ledger type AA), Committed cost, and a calculated Projected Final Cost, alongside a Percent Complete figure.

Commitments and encumbrances

Job Cost's Committed Cost figure comes from open purchase orders and open subcontract change orders raised against the job — amounts that are not yet actual cost but that reduce what is genuinely still available against the revised budget. This is on by default for every job; nobody has to opt into it.

Contract Billing and Service Billing: rules, markup tables and the F4812 workfile

Contract Billing and Service Billing share a billing engine but solve different problems. Contract Billing is built for long-running contracts with a schedule of values, progress billing, and retention — the shape of a construction pay application.

Revenue recognition: percentage of completion and WIP

Job Cost recognises revenue using standard construction-accounting methods — most commonly percentage of completion, cost-to-cost, where earned revenue is contract value multiplied by the ratio of actual cost to projected final cost.

Change management and the Project Operations decision

Change Management is a distinct JD Edwards module, not a manual process bolted onto Job Cost. Owner Change Orders and Subcontract Change Orders carry their own approval routing and, on approval, adjust the job's budget and the relevant contract value together, keeping cost and revenue expectations in step as scope moves.

Knowledge check

Summary

JD Edwards Job Cost, Contract Billing, Service Billing and Change Management form a tightly integrated construction- and project-cost suite built directly into Financial Management. The principal translations to D365 are: