JD Edwards EnterpriseOne / World as the system of record
Fin-Central imports the general ledger export from JD Edwards EnterpriseOne / World. Upload csv, xlsx, xls, or a plain-text / fixed-width report spool (.txt, .dat, .asc, .prn); the importer maps your column names to date, account, narrative, reference and the debit and credit sides, checks that debits equal credits, and writes the ledger behind cash flow, the trial balance, month-end close and the board pack. You keep JD Edwards EnterpriseOne / World as the system of record.
Nothing is installed in JD Edwards, no table is written to, and no BSFN is changed. Report Interceptor already saves your report as CSV or Text; that file is the integration.
Getting the file out of JD Edwards EnterpriseOne / World
- 1Run R09401 (Account Ledger - Detail), or R09401ZF for more than one company
- 2Set Ledger Type to A (Actual) - leave budget (B), plan (P) and offset (O) out of the file
- 3Set the date or the fiscal year / period range to the ledger you want in Fin-Central
- 4Send the output through Report Interceptor and save it as CSV or Text, or run the report to Excel
- 5Keep: Effective Date, Fiscal Year/Period, Company, Account, Sub, Document Type, Document, Journal Entry Number, Explanation, Amount, Ledger Type
CSV, XLSX, XLS, or a plain-text / fixed-width report spool (.txt, .dat, .asc, .prn). Nothing is installed in JD Edwards and nothing about your ERP changes: this reads the report you already run. JDE writes one signed Amount, compound Company-Account-Sub codes, Julian dates (124185 = 2024-07-03) and implied decimals (1250 = 12.50) - switch those on below if your report is set up that way. Page and object subtotals are dropped automatically.
What the export does, and what the importer does about it
Each of these is a real behaviour of JD Edwards EnterpriseOne / World report output. None of them should need fixing in a spreadsheet first.
Report Interceptor output starts with a title block
R09401 written as CSV or Text puts 'Account Ledger - Detail', the company, the date range and the ledger type above the column headings. Fin-Central finds the header row by matching your column names instead of assuming row 1, so the preamble is skipped rather than imported as a journal line.
Effective Date is a Julian number
JDE stores dates as CYYDDD: 124185 is 3 July 2024, and the century digit is added to 1900. Reading that as an Excel serial, or as text, puts every posting in the wrong year while the row count still looks correct.
Amounts are stored with two implied decimals
Unless the readable-amounts data option is on, 12.50 is written as 1250. Turn the implied-decimals switch on and Fin-Central divides it back. If you forget, it notices: whole-number amounts with a median in five figures get flagged before the import, because a ledger that is 100x too big still balances.
One signed Amount column, not debit and credit columns
JDE writes positive for a debit and negative for a credit, and older report formats append CR or wrap the figure in parentheses. Both are split into the correct side of the entry.
Company, Account and Subsidiary arrive as three columns
When there is no single Account column the segments are joined into one stable code (01000-4250-0100), and accounts are classified on the natural account segment - not the business unit, which would otherwise file every account in company 1000 or 1100 as an asset.
Budget, plan and offset ledger types
A report run without filtering the ledger type includes B, P and O rows. They are not postings and importing them doubles the apparent spend, so only ledger type A (Actual) is taken and the rest are counted and shown to you.
A subtotal after every page and every object
Rows like 'Subtotal for Object 4250' and 'Company Total' are report furniture. They are left out - and if the ledger would not balance without them, they are put back, because an Account Ledger SUMMARY report has nothing else.
One signed amount column
Where the export writes a single amount instead of separate debit and credit columns, positive is read as a debit and negative as a credit. A trailing CR or DR marker and parentheses around a credit are read too.
Account codes split into segments
When there is no single Account column, the segment columns are joined into one consistent code so the same account keeps the same identity across uploads, and classification uses the natural-account segment rather than the first one.
Julian CYYDDD dates
Effective dates written as a century digit, two year digits and a day of the year (124185 is 3 July 2024) are converted to real dates, so the ledger lands in the right month.
Fiscal periods written as numbers
Periods written as 12407 or 202407 are expanded to a calendar month. A period past 12 is a year-end adjusting period and is filed in December, with the line count reported so you can see it happened.
Only the actual-postings ledger
Rows whose ledger type is not one of A - budget, plan or clearing ledgers - are counted and left out, so a report run without filtering does not double the apparent spend.
Dates in the order that system writes them
This export writes month-first dates. The parser reads them that way, and a day past the 12th overrides the setting so a file that is actually day-first cannot be misread.
Columns are matched by name, not by position
The importer maps your headings - date, account, narrative, reference, debit and credit - onto what it needs, so a report that adds or reorders a column does not silently import the wrong figure. When a column it cannot place is missing, the upload is refused and names the headings it did read.
Title blocks and subtotal rows
A report spool often starts with run parameters and ends with page and company totals. The column row is found by matching the headings, and total-looking rows are held back unless the ledger only balances with them in.
Re-uploads, and what changed
Every upload can either replace the ledger, add only lines that are new, or refresh just the periods in the file. The result is compared with what was stored and summarised in plain English - including which earlier periods restated.
Uploading more than once
A JD Edwards EnterpriseOne / World ledger is rarely re-exported in full. Each upload chooses what it does to the ledger already stored: replace writes the whole ledger from the file, add keeps everything already there and takes only the journal lines it has not seen, and replace the periods in this file refreshes the months the file covers and leaves every other month alone. Whatever is chosen, the ledger that results has to balance before anything is written.
After each upload Fin-Central compares the stored ledger with the new one period by period and account by account, and writes the difference in plain English: which months moved, which accounts moved and by how much, and whether a period you have already reported from was restated. That comparison is arithmetic, not a model call, so it costs the same whether your ledger has a thousand lines or a million.
How to check it came in right
- ✓The debit and credit totals the result shows should equal your own report total - in JD Edwards, the Company Total line.
- ✓The count of rows left out should match the subtotal and header rows your report writes.
- ✓Every accounting period you asked for should be listed as covered.
- ✓The trial balance for a month should agree to the ledger report for the same month, account by account.
- ✓Anything you did not expect to change should be absent from the 'what changed' list.
If a file is refused, nothing already uploaded changes: the upload states the debit and credit totals it read, the column headings it found and the rows it could not use.
JD Edwards EnterpriseOne / World ledger import questions
Do we have to replace JD Edwards to use Fin-Central?
No. Fin-Central reads the ledger report you already run - R09401, R09401ZF for several companies, or the F0911 table exported to CSV - and nothing in JD Edwards is changed. Your ERP stays the system of record.
Which JD Edwards report should we run?
R09401 (Account Ledger - Detail) with Ledger Type A and the fiscal year or date range you want. Save the output through Report Interceptor as CSV or Text, or run it to Excel. Keep Effective Date, Fiscal Year and Period, Company, Account, Sub, Document, Journal Entry Number, Explanation, Amount and Ledger Type.
What if our amounts come through as 1250 instead of 12.50?
That is JD Edwards storing currency with two implied decimals. Tick the implied-decimals option on the upload and the figures are divided by 100 as they are read. If you upload without it, Fin-Central spots the pattern and tells you before importing.
Can we upload one month at a time instead of the whole history?
Yes. Uploads can add only the journal lines that are new, or replace just the accounting periods in the file and leave every other period alone. Both are checked against the ledger that results, so a corrected month cannot leave the books out of balance.
What happens when a period we already reported changes?
Every upload is compared with the ledger already stored and summarised in plain English. If a period older than your latest moves, the summary names it as a restatement, because that is the month your filed accounts and VAT return may no longer agree with.
Does JD Edwards World work as well as EnterpriseOne?
Yes, there is a separate JD Edwards World template for the older A73 and 8.1 menus (G09411 and the G09 Account Ledger reports). It handles the same Julian dates, compound account codes and implied decimals.
How do we check the import is right?
The upload result lists how many lines were stored, which rows were left out and why, the debit and credit totals, and each period it touched. Your report's own Company Total line is the number to compare against.
What you get once the ledger is in
The same figures your ERP holds, with the reporting it never had: a 13-week cash-flow forecast, a drillable trial balance, a month-end close checklist, board packs and statutory summaries.