JD Edwards World (A73 / 8.1) as the system of record
Fin-Central imports the general ledger export from JD Edwards World (A73 / 8.1). 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 World (A73 / 8.1) as the system of record.
World sites rarely have an API, and upgrading is a project nobody is budgeting for. A report spool is the oldest integration there is, and it is enough: read the file, write the ledger, change nothing in World.
Getting the file out of JD Edwards World (A73 / 8.1)
- 1Run G09411 (Account Ledger Inquiry) or the Account Ledger Detail report (G09A/G0941)
- 2Select ledger type A (Actual) and the fiscal year and period range you need
- 3Output the report to a flat file (Q<<>><< >><< >) or to Excel via the Print File Transfer / export queue
- 4Keep: Date, Fiscal Year, Period, Company, Account, Sub, Sequence/Document number, Description, Amount
CSV, XLSX, XLS, or a plain-text / fixed-width report spool (.txt, .dat, .asc, .prn). The same ledger data as EnterpriseOne, from the older World menus. Account is still Company-Account-Sub, dates are still Julian, and amounts are still stored without a decimal point - the options below handle all three.
What the export does, and what the importer does about it
Each of these is a real behaviour of JD Edwards World (A73 / 8.1) report output. None of them should need fixing in a spreadsheet first.
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 World (A73 / 8.1) 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 World (A73 / 8.1) ledger import questions
How do I get my JD Edwards World (A73 / 8.1) general ledger into Fin-Central?
Run the ledger or journal-detail report your finance team already runs, save it as csv, xlsx, xls, or a plain-text / fixed-width report spool (.txt, .dat, .asc, .prn), and upload it against the JD Edwards World (A73 / 8.1) layout. Run G09411 (Account Ledger Inquiry) or the Account Ledger Detail report (G09A/G0941)
Do we need to change or replace JD Edwards World (A73 / 8.1)?
No. Nothing is installed in your ERP and no table is written to. The export is read one way, which is also why an older system like JD Edwards World (A73 / 8.1) works as well as a modern one.
What if the file does not balance?
It is refused and nothing you already uploaded is changed. The message says what the debit and credit totals were, which columns were found and which rows were left out, so the report can be re-run rather than guessed at.
Can we upload the ledger monthly instead of all at once?
Yes. Uploads can add only what is new or replace only the accounting periods in the file, and either way the resulting ledger has to balance. Each upload is stored in the history with the periods it covered and what moved.
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.