MuteroDocs

Sage Evolution (Sage 200 Evolution)

Fiscalise Sage Evolution / Sage 200 Evolution invoices and credit notes with Mutero Desktop — SQL Server ODBC connector with automatic SSL certificate trust, DSN auto-discovery, optional Freedom Service health check, offline queue, SE- numbering, shared FDMS preflight, and FRN writeback.

Local agent on localhost:18989
Mutero Desktop runs a local HTTP agent at http://127.0.0.1:18989. Evolution SQL Server and Freedom credentials stay securely on this PC. The agent polls processed sales documents, queues them locally with SE- / SE-CN- stubs, runs the ZIMRA preflight, and syncs to Mutero Cloud after browser sign-in.
Sage Evolution only (SQL Server on Windows)
This guide is for Sage Evolution / Sage 200 Evolution (on-premise Microsoft SQL Server company databases) — not Sage Pastel Partner (Pervasive PSQL) and not Sage One (Cloud API). Invoice polling uses SQL Server ODBC directly against InvNum and _btblInvoiceLines. Mutero Desktop automatically includes certificate trust handling for modern drivers (e.g. ODBC Driver 18 for SQL Server).

Download & install

Mutero Desktop for Windows

Automated Windows setup file (`Mutero-Setup.exe`). Install on the PC that can reach the Evolution company SQL Server.

1. Sign in with browser

Open Mutero Desktop and use Sign in with browser. Evolution never signs into Mutero Cloud directly — the desktop API key is used for fiscalisation.

2. Select one VFD device

Each desktop install supports one active registered VFD. Open a fiscal day before fiscalising.

3. Configure SQL Server ODBC for Evolution

Credentials & Settings

FieldDetails & Discovery
DSN auto-discoveryClick Discover DSNs in Mutero Desktop under the Sage Evolution connector. Mutero will scan all local System and User DSNs and render quick-select badges for detected data sources.
ODBC driver & encryptionSupports ODBC Driver 18 for SQL Server, ODBC Driver 17 for SQL Server, or the legacy SQL Server driver. Mutero Desktop automatically enables TrustServerCertificate=yes so local SQL Server instances without CA-signed SSL certificates connect effortlessly.
DSN / connection stringPoint at the Evolution company database (e.g. EvolutionCompany). Or enter a direct connection string (e.g. Driver={ODBC Driver 18 for SQL Server};Server=localhost;Database=EvolutionCompany;Uid=sa;Pwd=secret;TrustServerCertificate=yes;).
Username / passwordSQL Server login (SQL auth or Windows auth) with permissions to read InvNum, _btblInvoiceLines, Client, and TaxRate. Stored encrypted locally on this PC.
Freedom Service (optional)If Sage Freedom Service Host is running (standard port 5000), enter http://127.0.0.1:5000, company database name, and Evolution agent credentials. Click Test Freedom to verify the REST service. (ODBC is still used for primary invoice ingestion).
  1. In Mutero Desktop → Settings → Sage Evolution, click Discover DSNs.
  2. Select your Evolution company DSN from the badge list, or type the DSN or SQL connection string.
  3. Enter your SQL Server username and password (if required by your SQL instance).
  4. Toggle on Enable Evolution Listener and Auto-fiscalise.
  5. Click Test connection, then Sync now to begin polling.

4. Document types & how to issue a credit note

Easiest option: Mutero web app
If Evolution feels confusing, open the fiscalised invoice in the Mutero web app, then click Issue Credit Note. Use the Evolution steps below when you also want the credit note recorded in Evolution.

The poller watches processed InvNum documents (DocType 0 / 6 = invoice, 1 / 7 = credit note / POS return; DocState 4 = processed). Mutero numbers them as SE-… and SE-CN-….

Steps in Sage Evolution

  1. Process a Credit Note for the customer (Order Entry / AR).
  2. Link it to the original invoice (iLinkedDocID on InvNum) so Mutero can resolve the original SE- stub.
  3. Add a short reason / description.
  4. Process it. Mutero Desktop queues it once the original is fiscalised.

If the original invoice is not fiscalised yet, the credit note waits (WAITING_ORIGINAL) until it is.

5. ZIMRA FDMS preflight (shared)

Evolution uses the same desktop + cloud preflight as Excel, Odoo, and Pastel Partner:

  • Currency — USD or ZiG only.
  • Tax — mapped Evolution TaxRate codes, known labels, or clear rates. Unknown codes never default to 15% — the row is BLOCKED.
  • HS codes — zero-rated / exempt lines need a valid 8-digit HS code.
  • Buyer data — when the Evolution customer has a TIN, Mutero sends ZIMRA buyerData.
Queue status BLOCKED
Open Desktop → Queue and read the error. Map the tax under Dashboard → VFD → Settings → Tax mapping (platform sage_pastel_evolution), then Sync again.

6. Tax rates & mapping

Configure sales tax rates in Evolution that match ZIMRA. Mutero reads iTaxTypeID joined to TaxRate.Code:

Evolution TaxRate (examples)ZIMRA Tax ID
1, 15, 15%, VAT, VAT 15%, Standard, Standard Rated, S1 — Standard 15%
2, 0, 0%, Zero Rated, Zero-Rated, Z2 — Zero Rated
3, Exempt, E, N3 — Exempt

7. Writeback & PDF

After ZIMRA confirms, Mutero Desktop writes the FRN and verification URL back into Evolution (default: append to InvNum.Description; optional UDF / custom fields in Desktop Settings). The fiscal receipt PDF uses the shared Mutero Cloud path.

Troubleshooting

  • ODBC test failed — verify SQL Server credentials and permissions. Mutero Desktop automatically adds TrustServerCertificate=yes to handle modern driver encryption (ODBC Driver 18).
  • SSL / Certificate validation error — if using a custom connection string with ODBC Driver 18, ensure TrustServerCertificate=yes; is included, or use a named DSN discovered by Mutero Desktop.
  • Freedom 404 / Access Denied — verify that Freedom Service Host is running, that URL includes /SDK/Rest/ (e.g. http://127.0.0.1:5000), and that database name matches your Evolution company database. Note: Freedom is optional; ODBC handles document polling.
  • Nothing queued — only processed DocTypes (DocState = 4) after the AutoIndex watermark are polled. Use Reset watermark in Settings if needed.
  • Credit note skipped / WAITING_ORIGINAL — link the credit note to the original invoice in Evolution and fiscalise the original SE-… invoice first.
Other Sage Integrations
Mutero supports all three major Sage platforms:
  • Sage One (Sage Business Cloud Accounting): Direct cloud REST API sync with automatic company discovery — see the Sage One guide.
  • Sage Pastel Accounting (Partner & Express 50c): Desktop connector with dual 32-bit/64-bit Pervasive engine bridge — see the Sage Pastel Partner guide.