A Twinfield integration lets other software exchange data with your administration. The main decision is which documents to process, in which administration and under which posting rules. An existing connector may cover that; bespoke logic may require custom development. Have both processing and error handling demonstrated. A technically successful connection doesn’t establish that every entry reached the right place.
Read connecting software for the general design approach. Our process automation checklist helps define the intended outcome with your bookkeeper.
What should you transfer to Twinfield?
Describe the document, not just the application. A webshop can provide orders, sales invoices, refunds and settlement statements. Which belong in Twinfield, and when? Establish what information will connect a later correction to its original transaction as well.
Keep the administration visible as a separate decision. A company may have several data flows; an accounting firm may serve several clients. The integration needs an agreed destination for each source. A customer name entered as free text is a weak arrangement when names can change.
Should you choose an existing connector or custom work?
First ask whether an existing solution supports your documents. Request a correction and a rejected input as well as an ordinary sale. Check that your maintainer understands where errors appear and how to resolve them.
| Choice | What should you investigate? | Where might extra work arise? |
|---|---|---|
| Existing connector | Supported source software, documents and administrations | Unusual fields or unsupported corrections |
| Workflow platform | Available actions and access to Twinfield | Process logic, monitoring and error handling |
| Custom API integration | Required operations and business rules | Development, testing, hosting and maintenance |
None of these routes guarantees correct entries on its own. An existing connector may have good checks; a poorly designed custom integration can repeatedly make the same mistake. Require evidence using your examples.
Our no-code versus custom comparison covers the wider decision. Ask who can change and test a revised posting rule, not only who builds the first version.
How does access to the Twinfield API work?
Twinfield’s authentication documentation describes OAuth and OpenID Connect. SOAP requests use an access token with a CompanyCode or CompanyId. Token validation identifies the cluster URL, and refresh tokens require the offline_access scope. Documentation checked on 2026-09-24.
For a buyer, this means testing access, administration selection and connectivity together. Ask what happens when permission is missing or revoked. The system should report the problem without marking documents as processed.
Consider the person granting access too. A changed role or an unused account may affect the arrangement. Include access management in the handover so another employee can act later without first locating the original developer.
How can you tell whether an entry was processed?
Twinfield’s XML web service documentation describes result fields in responses. result="1" indicates successful processing; problems can be reported through result="0", msg and msgtype. Require the integration to inspect the response contents instead of merely checking that a response arrived.
Consider a hypothetical import offering documents for a closed accounting period. The maintainer must see which documents need attention and why. Automatically retrying without changing the cause won’t resolve that kind of accounting issue.
Request an overview with source identifiers, destinations and processing status. A bookkeeper should be able to locate a problem without searching technical logs. Distinguish a rejected document from an uncertain outcome where the connection failed after submission.
How do you prevent mistakes between administrations?
Record the relationship between source and administration explicitly. Test more than the first administration: check how the same customer code is handled in another one. A contact code without context can mean something different elsewhere.
Review permissions for each intended user and application too. Someone processing client A’s records doesn’t automatically need client B’s data. Test that boundary with separate access and an example outside the permitted scope.
When mappings change, establish who may edit them. Adding an administration isn’t a harmless text change. Require a controlled trial before a new destination joins daily processing.
How do Twinfield bank connections work?
Wolters Kluwer’s Twinfield banking page distinguishes premium connections, additional PSD2 connections and access through partner Fleane. Assuming that every bank uses one PSD2 route is therefore too broad. Check support and terms for your particular account.
A bank connection doesn’t replace the complete sales integration. A received amount may be visible while discounts, delivery information or invoice corrections need another source. Decide which system is authoritative for each data type.
At launch, check the transition between historical statements and new transactions. Agree who investigates missing records. Give the bank connection and webshop connector clear owners, even when they feed the same administration.
How should you involve your accountant?
Have your accountant or bookkeeper review example entries before development. Discuss document types, periods, VAT codes, ledger accounts and corrections. That exposes technical assumptions before they appear during the month-end close.
Accountant user access and application access remain separate arrangements. Have the administrator configure suitable roles. A shared personal password shouldn’t replace that setup.
Agree a review during initial processing. Compare individual documents and exceptions as well as totals. Record which differences are explained and which need investigation. Retire the old entry route only when the new process has an understood checking procedure.
What does a Twinfield integration cost?
Request a quote covering the documents, administrations and exceptions you need. Compare initial configuration with recurring licences, hosting, monitoring and maintenance. A general price table for all accounting products doesn’t establish the work your process requires.
A trial with representative data reveals uncertainties. A field may be unavailable, the source may require extra requests, or historical records may need preparation. Have those findings reflected in the scope before committing to the complete implementation.
Our software cost guide helps with budgeting. Include your team’s time for checks and training too. Expected savings need to account for recovery work that remains after automation.
What must the next maintainer be able to take over?
Include mappings, access procedures, test examples and recovery arrangements in the handover. Have a maintainer investigate a failure and perform a controlled retry. Someone else should understand the operation without relying on memory or scattered messages.
The code TopDevs writes for your custom integration remains yours. Licences and access to Twinfield and other services are still required. Our explanation of code ownership and vendor lock-in distinguishes files, rights and practical transferability.
How do you actually get started?
Choose one source and one administration for the first trial. Collect ordinary documents, a correction and a failure case. Have the supplier demonstrate correct routing, accounting-result checks and recovery without duplicate documents.
For system integration development, book a call with your process description and the entries you want transferred.
