JD Edwards World Month-End Close Procedure Template
A month-end close in JD Edwards World touches several subledgers, unposted batches and period controls. This template gives your team one document that shows what is done on which day, by whom, and who signed it off.
Fill in
JD Edwards World Month-End Close Procedure Template
Month-End Close Procedure: October 2026
Company: Acme Precision Ltd Close owner: Corporate Controller Close calendar: WD5 Ledger type: AA (actual amounts)
Scope
Subledgers in scope: Accounts payable, accounts receivable, inventory, fixed assets, payroll journal
Special items this period: Annual physical inventory adjustment, new tax code effective this month.
Close Steps
| Step | Task | Day | Owner | Done |
|---|---|---|---|---|
| 1 | Confirm all batches are posted and none remain in error or pending approval | WD1 | ||
| 2 | Close accounts payable cutoff and run the aging against the control account | WD1 | ||
| 3 | Close accounts receivable cutoff, apply unapplied cash | WD1 | ||
| 4 | Post inventory transactions and reconcile the inventory ledger to the general ledger | WD2 | ||
| 5 | Run depreciation and post fixed asset entries | WD2 | ||
| 6 | Book accruals, prepaid releases and recurring journals | WD3 | ||
| 7 | Run trial balance and review variances | WD3 | ||
| 8 | Complete bank and balance sheet reconciliations | WD4 | ||
| 9 | Lock the period and archive reports | WD5 |
Period Lock
Update the company fiscal period in the company constants and restrict posting to the next open period.
Exceptions Log
| Item | Description | Amount | Resolution | Owner |
|---|---|---|---|---|
Sign-offs
A starting point. Day numbers, tasks and the lock method vary by company and release; align them with your own calendar and controls. Verify menu paths and program names in your own environment.
Optional close automation review
Interested in read-only reports that prepare your close checks from live data?
Optional. The tool and every export work without this. No spam.
How to use the template
Fill in the period, owner and the close calendar you commit to. List the subledgers in scope and anything unusual about this month, such as a physical inventory or a tax change. Assign an owner to each step in the table, adjust the working day for your company, and print the document for the close meeting. Update the exceptions log during the close so that audit questions can be answered from one page.
- Keep the same step list each month and only change owners and dates
- Record unposted batches before locking
- Agree the subledger to general ledger control account tie-outs
- File the signed document with the period reports
The logic of the sequence
Close runs from the edges inward. Operational subledgers close first so no new transactions arrive, then reconciliations tie the subledgers to the general ledger control accounts, then accruals and adjustments are booked, and finally the trial balance is reviewed and the period is locked. Locking too early forces reopening and reposting, which is how most second-pass closes happen.
Reading the exceptions
An exceptions log with no entries is suspicious. Normal closes find timing differences, missing receipts, unposted batches and reconciling items. What matters is that each has an owner, an amount and a resolution before sign-off. Anything carried forward should appear in next month's scope list so that it does not become permanent.
Common mistakes
Frequent problems include posting batches into the wrong period, running depreciation before additions are complete, and reconciling inventory to the general ledger only at year end. Another is giving too many people access to reopen periods. Restrict that control and require an approval record every time a closed period is touched.
Frequently Asked Questions
Is this specific to one World release?
No. The sequence is a general finance close. Menu paths and program names differ between releases and modifications, so each company should adapt the step wording to its own environment.
How fast should a close be?
Many manufacturers aim for five to ten working days. The right target depends on the volume of transactions, the number of entities and how much is manual. Measure your current close first, then improve the largest delays.
Why reconcile subledgers to the general ledger?
Because differences usually come from unposted transactions, manual journal entries to control accounts or timing problems. Catching them before lock saves reopening the period.
Can I reuse this for other ERPs?
The structure works anywhere, but the lock method and subledger steps need to reflect the other system's own controls.
Netray can help build read-only checks that list unposted batches and control account differences automatically on the first day of close.
Related Tools
JD Edwards World to EnterpriseOne Data Conversion Mapping Worksheet
Editable worksheet that tracks every World file you convert to EnterpriseOne: source, target, cleansing rule, record counts, owner and status.
ERP OperationsIBM i Batch Job Schedule Documentation Worksheet
Editable run book of scheduled jobs with timing, dependency, owner, runtime and restart notes plus a total nightly batch window.
ERP OperationsJD Edwards World and IBM i Change Request Form Template
Fill-in change request form for program, PTF, system value or data changes with backout plan and approval lines, exported as a clean document.
More Costing & Finance tools
See all- SAP QM Inspection Effort and Cost Calculator
- SAP Standard Cost Estimate BOM Rollup Calculator
- Legacy ERP Retirement Cost and Payback Calculator
- Distributor Customer Credit Application Template
- Distributor Customer Profitability Worksheet
- Distributor GMROI and Inventory Turns Calculator
- Vendor Early Pay Discount Worksheet
- SyteLine Cost Rollup Variance Calculator
- SyteLine Month End Close Checklist