INTEGRATIONSTWINFIELD + SALESFORCEConnect Twinfield to Salesforce
Your account teams work in Salesforce, the financial administration runs in Twinfield, often across several operating companies. With an integration, a won opportunity becomes an invoice in the right administration, and the account team sees what a customer still owes. Finance no longer has to work out which BV should invoice what.
ISO 9001 & 27001
- Account as debtor per administration comes from Salesforce
- Opportunity and products to invoice comes from Salesforce
- Open items and ageing goes to Salesforce
- Invoiced revenue per customer goes to Salesforce
- Payment status per invoice goes to Salesforce
Built for clients including Tata Steel, M&G Investments, Digistore24, Toppers in Concert, Bar-le-Duc and Loogman
Salesforce is common at organisations with several teams, countries or operating companies. Twinfield fits because one organisation can have several administrations in it, for example one per BV (Dutch private limited company), managed together with an accounting firm. Between the two there is usually a spreadsheet or a weekly export.
The problem is rarely a single invoice. It's the question of which administration should invoice an opportunity, which customer entity in Salesforce belongs to which customer code, and why the account team only hears at the quarterly review that a major customer hasn't paid for months. An integration captures those agreements in rules instead of in someone's head.
For each item: which direction it goes, when, and why. This is the starting point; in the first conversation we fit it to your situation.
- 01Account as debtor per administrationSalesforce → Twinfieldon the first won opportunity for a BV
An account in Salesforce can be a customer (debtor) in several administrations. The integration creates the customer in the administration that invoices and stores the customer code per administration on the account.
- 02Opportunity and products to invoiceSalesforce → Twinfieldat Closed Won
The opportunity products become invoice lines. For each product, the revenue account and VAT code it's posted with are fixed, and a field on the opportunity determines the administration.
- 03Open items and ageingTwinfield → Salesforcedaily
For each account, the outstanding amount and ageing come back into Salesforce, totalled across all administrations where the customer is a debtor.
- 04Invoiced revenue per customerTwinfield → Salesforceafter each period
The revenue actually invoiced, next to the pipeline amount in Salesforce. That lets the account team compare expectations with reality.
- 05Payment status per invoiceTwinfield → Salesforceafter matching
The status of each invoice is added to the opportunity, so service or delivery knows when a customer has paid.
Not always. If an existing integration for Twinfield and Salesforce does exactly what you need, we'll tell you.
As far as we could establish, Salesforce and Wolters Kluwer don't offer an integration between the two themselves. Other parties do offer the combination. Because Wolters Kluwer requires certification for anyone integrating with Twinfield, it makes sense to ask whether a provider is certified and whether its integration can handle several administrations.
A standard integration works if you have one administration and every opportunity becomes one invoice. With several BVs, account hierarchies and subscription revenue, you almost always need your own rules.
- The BV that invoices depends on country, product line or contract.
- A group is in Salesforce with subsidiaries as separate accounts, while Twinfield only knows the entity that receives the invoice.
- Contracts with monthly or annual billing don't map one to one onto an opportunity.
- Cost centres or projects in Twinfield need to be linked to an opportunity or team.
AI reads, sorts and prepares a suggestion. Where it matters, a person decides.
Credit picture for the account team
For each account, AI summarises what is outstanding across all administrations and how that is developing, and adds it as a note in Salesforce. The account team knows where it stands before a negotiation. Decisions on credit limits stay with finance.
Suggestions for new products
If a new product appears in Salesforce without a revenue account or VAT code, AI suggests a classification based on similar products. Finance approves it before the first invoice with that product is created.
The administration per opportunity
Every call to Twinfield names the administration. Record in Salesforce which BV invoices, ideally as a required field at Closed Won. Otherwise an invoice ends up in the wrong administration.
One budget for the whole organisation
Twinfield also counts API credits per organisation: 1,000 per minute, shared by all of that organisation's integrations. If a bank or scanning integration is already running, the Salesforce integration shares that headroom. Schedule heavy syncs outside office hours.
Who leads for customer data
Salesforce leads for accounts, contacts and the opportunity. Twinfield leads for customer code, billing address once invoices have been issued, and payment status. Make the financial fields in Salesforce read-only, so nobody corrects them there.
Large invoices
A Twinfield transaction may have at most 1,000 lines, and Twinfield recommends no more than 500. An opportunity with hundreds of lines for usage or licences is better summarised per product.
What goes where
Which data moves, in which direction, and which system wins when two values differ. That is written down before anything gets built. For this integration, that means: Account as debtor per administration, Opportunity and products to invoice, Open items and ageing, Invoiced revenue per customer, Payment status per invoice.
Fields and rules
For every field, how it translates between the systems: statuses, VAT codes, general ledger accounts, item numbers. And what happens with a duplicate or a missing value. For this integration, that means: The administration per opportunity, One budget for the whole organisation, Who leads for customer data, Large invoices.
Testing with real cases
In a sandbox or test administration, with the exceptions you actually run into: credit notes, partial deliveries, changed customer details.
Live, with logging and monitoring
Every sync is logged, and when something fails, someone gets an alert. If a vendor changes its API, we update the integration.
No account manager. You talk to someone who builds integrations themselves, and who will tell you when a standard integration is enough.
- Office on the Duivendrechtsekade in Amsterdam
- ISO 9001 and ISO 27001, certified by Kiwa
- 500 projects delivered
- 4.8 from 127 reviews
Is there a standard integration between Twinfield and Salesforce?
As far as we know, Salesforce and Wolters Kluwer don't offer one themselves. There are other parties that offer the combination. Check whether their integration can handle several administrations and whether it has been certified by Wolters Kluwer.
How does the integration decide which administration an invoice goes into?
You record that in Salesforce, for example with a required field on the opportunity or a rule based on country or product line. The integration sends that administration's code with every Twinfield call. Without a rule like that, someone has to decide per invoice.
Can the account team see open items without Twinfield access?
Yes. The integration writes the outstanding amount and ageing per account back to Salesforce, totalled across all administrations. You decide which fields are visible and to whom.
What happens if a customer is a debtor in several BVs?
Then that customer has its own customer code in each administration. The integration stores those codes on the account in Salesforce and adds up open items across all administrations. That way you see one customer, while the books are right per BV.
How many requests can the integration make to Twinfield?
Twinfield allows 1,000 API credits per minute per organisation, and for certified integrations 500 per combination of client and organisation. A read request costs 1 credit, any other request 3. Salesforce has its own API limits, and both need to fit the volume you expect.
Related services
- Connect Twinfield to HubSpotConnect Twinfield to HubSpot: which data moves between CRM and accounting, which system leads, and where VAT, codes and API limits go wrong in practice.
- Connect Exact Online to SalesforceConnect Exact Online to Salesforce: opportunities to the right administration, payment status back, and a set-up that fits within the Exact API limits.
- Connect Business Central to SalesforceConnect Business Central to Salesforce: opportunities become sales orders, credit and invoices come back to sales, and API limits don't trip up the integration.
- Connect AFAS to SalesforceConnect AFAS to Salesforce: accounts, opportunities and invoices flow both ways, within the API limits and with AFAS as the financial source of truth.
- Connect Salesforce to ShopifyConnect Salesforce to Shopify: what data to exchange, which building blocks Salesforce provides, which system leads on what, and where things go wrong.
- Connect Claude to SalesforceConnect Claude to Salesforce through the hosted MCP servers or the Salesforce in Claude plug-in. What Claude can read and change, and what to set up first.
Sources
The technical facts on this page come from the vendors' official documentation, checked on 19 September 2026. Vendors change their APIs and limits; when we build an integration, we always check the current state.