Business system connector
Private betaConnect Twinfield to ChatGPT and Claude with MCP
Give ChatGPT, Claude and other MCP clients governed, read-only access to your Twinfield accounting data through one Zynosure connection.
Availability: Private beta
The Twinfield connector is implemented as a read-only beta. Live provider qualification and the hosted OAuth rollout must finish before general availability.
Which customer invoices are more than 30 days overdue?
Zynosure returns the matching Twinfield open items by currency, including invoice reference, customer, due date, outstanding amount and age bucket. The result retains the office and provider source.
Illustrative response. Results remain isolated by currency.
get_aged_receivables
Illustrative answer shape
- Invoice
- VRK:202600421
- Customer
- Example Trading B.V.
- Outstanding
- EUR 8,450.00
- Age
- 31-60 days
- Source
- Twinfield open items, office 001
- Observed
- 2026-07-15 14:32 UTC
- Freshness
- Live current-state read
- Operation
- get_aged_receivables
Reviewed operations, one REST and MCP contract
Every published operation uses the same schema, policy check and handler through both interfaces.
| Accounting data | List or search | Detail | MCP | REST |
|---|---|---|---|---|
| Customers and suppliers | Search | Get | Yes | Yes |
| GL accounts, cost centres and projects | Search | Get | Yes | Yes |
| Sales and purchase invoices | List | Get + lines | Yes | Yes |
| GL, bank and cash transactions | List | Get entry | Yes | Yes |
| Receivables and payables | Current items | Age bucket | Yes | Yes |
| Trial balance and ageing | Report | By currency | Yes | Yes |
Questions you can prepare to ask
Examples are illustrative until the connector completes live qualification.
“Which customer invoices are more than 30 days overdue?”
“Show this month's bank transactions for this company.”
“Compare costs by cost centre and project.”
“Which supplier invoices are still unpaid?”
“Show the current trial balance and its source date.”
How the connection works
- 01
Authorise Twinfield
An administrator signs in and selects approved Twinfield companies through the provider OAuth flow.
- 02
Apply company policy
Zynosure determines which people, companies and reviewed read operations are available.
- 03
Connect your AI client
ChatGPT or Claude receives a policy-filtered MCP catalogue and calls the same reviewed operations as the REST API.
Read-only and policy controlled
- Read-only accounting and provider-native scopes
- OAuth credentials are never returned to the AI client
- Company access is checked for every operation
- Twinfield reads are bounded by reviewed filters and periods
- Responses retain source provenance, observation time and freshness
AI client and API compatibility
Availability remains gated per client until its user-visible OAuth qualification is complete.
| Client | Interface | Status |
|---|---|---|
| ChatGPT | Remote MCP + OAuth | Qualification pending |
| Claude | Remote MCP + OAuth | Qualification pending |
| OpenAI and Claude APIs | Remote MCP | Private beta |
| Business applications | REST API | Private beta |
Why use Zynosure instead of a raw provider connection?
Zynosure preserves provider detail while adding a governed layer that can extend across the rest of the business.
Provider fidelity
Canonical accounting layer
Policy-filtered catalogue
What happens after you request access
You know the next step before sharing any provider credentials.
- 01
Short fit check
We review the connector, AI client, administration count and intended use without requesting provider credentials.
- 02
Agree qualification
Together we select an approved test administration, read-only scope and the questions that must be validated.
- 03
Guided onboarding
After provider and client qualification, we activate the connection and verify the first answers with provenance.
Frequently asked questions
What is a Twinfield MCP server?
A Twinfield MCP server presents reviewed accounting capabilities as typed tools for authorised AI clients. Zynosure translates those operations into bounded Twinfield reads and returns structured accounting results.
Can Zynosure post transactions in Twinfield?
No. The first release is read-only. It does not create, change or delete invoices, bank transactions, dimensions or other Twinfield records.
Does it support more than one Twinfield company?
The connector discovers authorised Twinfield offices. Company access remains explicit and is checked against Zynosure policy on every operation.
Which Twinfield data can an AI assistant read?
The reviewed beta covers parties, ledger accounts, dimensions, invoices, financial transactions, open items and balance reports. Availability is gated independently per operation during qualification.
Is there a REST API as well as MCP?
Yes. Reviewed data operations have matching REST and MCP bindings over the same schema, policy checks and handler. Raw SOAP, Finder, Browse or ProcessXML calls are not exposed.
Join the connector beta
Tell us which accounting system and AI client you want to connect. We will contact you when the relevant private-beta place is available.
Book a technical walkthrough
For security reviews, multiple administrations or a planned API integration, discuss the architecture and qualification path directly.
Book a technical walkthroughBack to all connectors