Skip to main content

MODULE GUIDE

Sage Connection

From the client's Sage database to their accounting and HR files, without retyping

Start reading15 chapters
IntegraSys ERP2026 edition
MODULE GUIDESage ConnectionFrom the client's Sage database to their accounting and HR files, without retyping

Contents

  1. Chapter 1 — The Sage connection at a glanceYour client keeps their accounts or payroll in Sage. Rather than retyping everything, IntegraSys reads their Sage database, never writing to it, and brings their data into their accounting file or HR file.What the module does, and what it never doesThe whole journey, in six stepsWhat you need before you startThe menu and the Overview
  2. Chapter 2 — Installing the local agentThe agent is the small program that reads the Sage database at your client's. You create it in IntegraSys, install it on a computer of the client, and it goes Online as soon as you paste its token.Create the agent and copy its tokenDownload and start the agent at the client'sThe agent window and its status lightFollow, revoke or delete an agent
  3. Chapter 3 — Declaring the SQL serverThe SQL server is the computer hosting Sage's databases: each company has its own. You declare it once, linked to your agent, and you check that IntegraSys reaches it.Fill in the server formThe three connection modes and authenticationTest the connection and show the databasesWhat the Last test says
  4. Chapter 4 — Assigning each database to a clientOn the server, each Sage company has its own database. You tell IntegraSys which database belongs to which client, and which software it was kept in: that is what lets you run an extraction.List a server's databasesChoose the source softwareAssign a database to a clientRead a database's status
  5. Chapter 5 — Checking the mappingsA software stores its data in tables and columns. The Mappings screen says which ones IntegraSys reads. The starting values are those of a standard installation: checking them before the first extraction saves a failed one.Read a card: the source table and its columnsCorrect a mappingThe case of Sage PaieLet the AI propose the employee form
  6. Chapter 6 — Extracting the dataThe extraction reads a client's data in their Sage database, read-only, and puts it into files. For accounting, it also prepares the takeover of the entries into IntegraSys.Choose the database, the module, the years and the dataRun and follow the extractionThe five states of an extractionVery large volumes
  7. Chapter 7 — The check: are all the entries there?A read cut short, by the network or by the server, would give a truncated file. So every extraction counts the entries in Sage, then those it wrote, and tells you whether the count is right.What is counted, and whereThe green, red or orange checkReading the gaps boxWhy the sync is then refused
  8. Chapter 8 — Sync to AccountingOne click, and the entries extracted from Sage enter the client's accounting file, year by year, as validated vouchers. The work runs in the background: you can leave the screen, it carries on.What you need before you clickThe takeover in the background, in batchesOne fiscal year per year: create it, reopen itEach fiscal year's summary and the reconciliation
  9. Chapter 9 — The adjusted takeover and the takeover reportSage only requires balance per journal and per month; IntegraSys requires it voucher by voucher. Rather than refusing what does not balance on its own, the takeover takes everything, adjusts what it must, and tells you exactly what to regularise.Merged vouchers: same day, same number, same monthThe suspense account and the REPRISE journalWhat is still refusedThe takeover report, as PDF and Excel
  10. Chapter 10 — Re-running without duplicatingYour client keeps working in Sage. You can extract and sync again as often as needed: nothing is duplicated, and what you corrected in IntegraSys is never overwritten.How IntegraSys recognises a voucher already taken overUnchanged, updated or not overwrittenWhat a new takeover never doesFiscal years closed by the takeover
  11. Chapter 11 — Sage Paie into the HR fileA Sage Paie database is taken over like an accounting one: you extract it, then you import it. The employees, the payroll years and months, the payroll plan and the leaves land in the client's HR file, after a simulation that writes nothing.Extract a Sage Paie databaseSimulate, then import into the HR fileRead the summary, refusals and warningsWhat is taken over, and how
  12. Chapter 12 — Journal, exports and filesTwo screens keep track of everything: the Journal says what was run and how it ended, Exports keeps every file produced. And each format has its use.The Extraction journal and its filterThe Export filesWhat each format producesRecognising a file by its name
  13. Chapter 13 — When something gets stuckEach blockage has its message, and each message says what to do. Here are the ones you may meet, step by step, with their remedy.The agent and the serverThe extractionThe syncThe mappings and payroll
  14. Chapter 14 — From A to Z: taking over LUMEA DESIGNCabinet Méridien Conseil takes over the accounts of its client LUMEA DESIGN, kept in Sage 100. Here is the whole journey, with the figures of this book's screens.Prepare: agent, server, database, mappingsExtract and checkSync and verifyThe next month: run again
  15. Chapter 15 — The Sage connection memoThe whole module on a single page: print it, and keep it by the screen.