Enterprise ledger

Import your Epicor general ledger into Fin-Central

Read the Epicor ledger report as it comes out of your system - CSV, XLSX, XLS, or a plain-text / fixed-width report spool (.txt, .dat, .asc, .prn) - and keep Epicor as the system of record.

Accepted file types: CSV, XLSX, XLS, or a plain-text / fixed-width report spool (.txt, .dat, .asc, .prn). Layout Epicor is one of 27 ledger layouts the importer ships with.

Epicor as the system of record

Fin-Central imports the general ledger export from Epicor. 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 Epicor as the system of record.

Reporting out of an ERP should not require a project. There is nothing to install, nothing to upgrade and no licence to renegotiate.

Getting the file out of Epicor

  1. 1Financial Management → General Ledger → Reports → GL Transaction Detail
  2. 2Select the fiscal period(s)
  3. 3Export to Excel/CSV
  4. 4Map: Date, GL Account, Description, Debit, Credit, Document Reference

CSV, XLSX, XLS, or a plain-text / fixed-width report spool (.txt, .dat, .asc, .prn). Epicor fiscal periods may need mapping via the 'Period' column if dates are not populated.

What the export does, and what the importer does about it

Each of these is a real behaviour of Epicor report output. None of them should need fixing in a spreadsheet first.

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 Epicor 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.

Epicor ledger import questions

How do I get my Epicor 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 Epicor layout. Financial Management → General Ledger → Reports → GL Transaction Detail

Do we need to change or replace Epicor?

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 Epicor 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.

Other ledgers we read