Sage 50 and Wise integration

What moves between them

Payment data flows from Sage 50 into Wise. When a vendor invoice in Sage 50 is marked for payment, ml-connector reads the vendor record and invoice details, creates or reuses the recipient in Wise, quotes the transfer, orders it, and funds it. Balance statements flow back from Wise into Sage 50 to reconcile the bank account, keyed by the Wise BalanceStatement and reconciled against Sage 50's bank transactions. Transfers are recorded as payment records in Sage 50 with the Wise transfer ID as the external reference.

How ml-connector handles it

ml-connector runs on a Windows machine or reachable via network with direct SDK access to Sage 50, logging in with the company data path and Windows credentials against Sage 50's user database. It polls Sage 50 on a 15-minute or hourly cadence and reads vendors, purchase invoices, and bank accounts using the .NET SDK or SDO layer depending on edition. For Wise, it authenticates using either OAuth2 client credentials or a Personal API Token, handles the 12-hour token refresh, and caches the Profile ID to reduce API calls. When a payment is triggered, ml-connector creates a Wise quote with the vendor's currency and amount, checks the quote expiry, creates or reuses the recipient in Wise, orders the transfer using the same quote, and funds it. Because Wise transfers require this four-step sequence and quotes expire, ml-connector must create a fresh quote if the recipient is not found or the previous quote has lapsed. Wise rate limits return HTTP 429 per second, so ml-connector implements exponential backoff. Wise webhooks can push payment state changes back to ml-connector if configured, but reconciliation with Sage 50's bank accounts relies on reading Wise balance statements and matching them against Sage 50's bank transaction log on each poll cycle. Every record carries a full audit trail.

A real-world example

A mid-sized services firm with UK headquarters and US operations uses Sage 50 for accounting and Wise for international payments between offices and to vendors in multiple currencies. Before the integration, the finance team exported vendor invoices from Sage 50, manually created Wise transfer requests each week, and then logged back into Sage 50 to record the transfer in the payment register and manually update bank balances from Wise statements, a process that surfaced currency conversion errors and created timing mismatches in the reconciliation. With Sage 50 and Wise connected, weekly vendor invoices marked for payment in Sage 50 automatically trigger Wise transfers to the correct recipients, and Wise balance statements flow back into Sage 50 so the bank account is automatically reconciled without re-keying. The finance team can now see all cross-border payments in one place and month-end bank reconciliation is complete in hours instead of days.

What you can do

• •Read vendor and customer records from Sage 50 and execute international transfers through Wise on a 15-minute or hourly schedule.
• •Create Wise transfer orders with quotes and recipients mapped from Sage 50 vendor data, handling quote expiry and recipient reuse.
• •Reconcile Wise balance statements back into Sage 50 bank accounts to keep cash position accurate across local and international accounts.
• •Authenticate Sage 50 via local Windows SDK with company path and credentials, and Wise via OAuth2 or Personal API Token with automatic token refresh.
• •Store all transfer records in Sage 50's payment register with Wise transfer IDs as external references and full audit trail.

Questions

How does ml-connector bridge the local SDK of Sage 50 with the REST API of Wise?

ml-connector runs on a Windows machine with direct access to Sage 50's SDK, reading vendors and payment records on a schedule. For Wise, it authenticates using OAuth2 or a Personal API Token, handles token expiry and refresh, and executes transfers via REST. Both authentication systems are kept encrypted and ml-connector maps Sage 50 vendors to Wise recipients so transfers happen automatically without re-keying.

What happens if a Wise quote expires before the transfer is funded?

Wise quotes expire after a certain time window. ml-connector detects this when attempting to order the transfer and creates a new quote with the current exchange rate before proceeding. If the quote has expired, ml-connector retrieves fresh pricing and retries the transfer order, ensuring the payment completes without manual intervention.

How are Wise balance statements reconciled back into Sage 50?

ml-connector reads Wise balance statements on each poll cycle and matches them against Sage 50's bank transaction log by amount, date, and Wise transfer ID where available. Reconciled transactions update Sage 50's bank account balance, and unmatched items are flagged in the audit log so the finance team can investigate timing differences or incomplete records.