Skip to content
Discuss your first workflow

Twin / Field note / 5 min read

Giving Copilot and Claude Read-Only Access to SunSystems and Dynamics GP (Without Replacing Your ERP)

Most enterprise AI connectors assume every system is modern cloud SaaS. Here is how UK finance teams connect legacy ERPs and operational spreadsheets safely — strictly read-only.

Every week we speak with UK Finance Directors and CFOs running Infor SunSystems, Microsoft Dynamics GP, or an established on-premise SQL ledger. They have already bought Microsoft 365 Copilot licences (or their leadership team uses Claude), and they want one practical thing:

"Let account directors check overdue balances, project margin and open invoices in Copilot or Teams — without emailing finance for a spreadsheet export, and without letting an AI touch our live ledger."

Almost every vendor tells them the same unhelpful story: migrate your ERP to a modern cloud suite first, spend twelve months building a data warehouse, and then plug in AI.

You do not need to rip out a working finance ledger to give your team governed AI answers.

Why legacy ERPs trip up standard AI tools

Off-the-shelf Copilot connectors and generic MCP servers are designed for clean, modern cloud APIs. Legacy finance estates fail on four very specific realities:

  1. No modern REST API or OAuth flow. SunSystems (SOAP/SSC or SQL views), Dynamics GP (SQL Server tables with decades of custom account segments), and multi-entity trial balances do not plug neatly into consumer AI connectors.
  2. Chart-of-accounts logic lives in finance's head. Which nominal codes count as recognised revenue versus pass-through disbursements? Which intercompany eliminations apply? Which periods are closed versus still posting? If you point a language model at raw SQL tables, it guesses those rules differently every time.
  3. Currency and period traps destroy CFO trust. Blending GBP, EUR and USD overdue rows into a single total, or comparing 22 days of the current month against a complete prior month, immediately makes a finance director shut the tool down.
  4. The full answer rarely lives in the ERP alone. The overdue invoices sit in SunSystems or Dynamics GP, the account owner sits in HubSpot or Salesforce, and the delivery status sits in a project tracker or Excel sheet.

How a read-only Company Twin bridges legacy ERPs safely

A Company Twin adds a strictly read-only governed knowledge graph over your existing estate — with zero writes back to your ERP and zero migration of source records.

1. Fixed-egress, read-only ingestion

For SQL Server, Azure SQL, Postgres, SunSystems SOAP/SQL, and operational spreadsheets, we wire a dedicated read-only connection (with fixed egress IP and least-privilege views on Dedicated and UK-hosted plans). Your accounting system stays the sole system of record.

2. Reconciled entities and agreed accounting rules

Ahead of any user prompt, your Company Twin links counterparties across your ERP, CRM, and project systems, and encodes your exact accounting rules inside its model-free Rust graph engine:

  • Complete-period rules: Month-on-month and rolling-12-month comparisons automatically use closed or complete periods unless a user explicitly asks for month-to-date.
  • Strict currency separation: GBP, USD and EUR balances are never silently summed together.
  • Explicit distinction between invoiced and recognised revenue: If someone asks for "last month's revenue," the Twin returns your agreed P&L figure and clearly distinguishes it from gross invoiced billings rather than blending the two.
  • Deterministic arithmetic: Totals are pre-computed by the graph engine, never estimated by an LLM.

3. Role-based governance that follows the user everywhere

Through Microsoft Entra sign-in, an account manager asking inside Microsoft 365 Copilot or Microsoft Teams can see overdue sales invoices and open delivery projects for their clients, while payroll journals, supplier bank details, and group management accounts remain strictly restricted to finance. If a user asks for a figure outside their role or outside verified coverage, the Twin refuses plainly rather than guessing.

Dedicated and UK-hosted isolation for regulated finance teams

Finance leaders rightly ask where ledger data sits and how models process it. On Dedicated (from £3,000/month) and UK-hosted (from £6,000/month, with dedicated UK data residency and private UK model processing) plans:

  • Your organisation gets its own isolated application, database, and Rust graph engine — no shared multi-tenant database.
  • Connections to legacy ERPs, SQL databases, and SSO are included.
  • Graph reads from Microsoft 365 Copilot, Teams, Slack and Claude consume zero AI credits.
  • Mercury Labs holds whole-organisation Cyber Essentials Plus certification and is a Crown Commercial Service supplier.

Start with one ledger question in two weeks

You do not need to boil the ocean or model every historic nominal code on Day 1. Most finance teams start with a focused two-week staged rollout:

  1. Week 1: Wire your ERP (SunSystems, Dynamics GP, or SQL ledger) read-only alongside your CRM or project tracker, reconcile key customers/entities, and verify 10 real finance questions against your latest management pack.
  2. Week 2: Enable the read-only Microsoft 365 Copilot federated connector and/or Teams agent for a 5-person pilot group (finance + commercial leads), verify Entra role boundaries, and review click-through provenance on every figure.

Bring us one question from your last board pack

Show us one recurring question that currently takes your finance team an hour of VLOOKUPs across your ERP and CRM. We will walk through how Company Twin answers it identically in Copilot and Claude — read-only, with source links — in 20 minutes.

A few practical questions.

Does Company Twin ever write to or modify our SunSystems or Dynamics GP database?

No. Connections to legacy ERPs, SOAP endpoints and SQL databases are strictly read-only. The Twin reads reconciled extracts into your isolated knowledge graph and never alters ledger postings or accounting controls.

Do we need to migrate off Dynamics GP or SunSystems before using Copilot or Claude on finance data?

No. You keep your existing ERP, chart of accounts and month-end close workflow intact. Your Company Twin bridges your legacy ledger, CRM and operational spreadsheets into one clean read-only surface for Copilot, Teams and Claude.

How do you prevent non-finance staff from querying payroll or restricted nominal codes?

Each colleague signs in with Microsoft Entra (or organisation SSO) and inherits a granular Company Twin role. Restricted accounts, payroll journals and management accounts are excluded at the graph layer before any answer or total is formed.

Put it to work

Keep exploring the Twin.

Read the practical guides to business context, connected tools and working with evidence.