Line 500 (Sage / IP Software) as the system of record
Fin-Central imports the general ledger export from Line 500 (Sage / IP Software). 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 Line 500 (Sage / IP Software) as the system of record.
Line 500 has no API to integrate with, which is exactly why the report route matters.
Getting the file out of Line 500 (Sage / IP Software)
- 1Financial Management -> General Ledger -> Transaction Ledger (or the Nominal Activity report)
- 2Set the period range and select all nominal accounts
- 3Print to file / export the listing to CSV, or use the ODBC view of the GL transaction table
- 4Keep: Date, Nominal / Account Code, Account Name, Narrative, Reference, Debit, Credit
CSV, XLSX, XLS, or a plain-text / fixed-width report spool (.txt, .dat, .asc, .prn). A 30-year-old package with the same 4-code nominal structure it always had: export the listing, do not change the system.
What the export does, and what the importer does about it
Each of these is a real behaviour of Line 500 (Sage / IP Software) 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 Line 500 (Sage / IP Software) 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.
Line 500 (Sage / IP Software) ledger import questions
How do I get my Line 500 (Sage / IP Software) 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 Line 500 (Sage / IP Software) layout. Financial Management -> General Ledger -> Transaction Ledger (or the Nominal Activity report)
Do we need to change or replace Line 500 (Sage / IP Software)?
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 Line 500 (Sage / IP Software) 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.