FousTwinfield
Pull your Twinfield receivables into your own systems
Read the Openstaande postenlijst per debiteur, the Ouderdomsanalyse and a Debiteurenkaart from each Twinfield administratie with one API call each. A workflow can run the aging analysis for every administratie on Monday morning and email you the late debtors.
Works with your own Twinfield account. Fous is an independent product.
What you can build on Twinfield
Get open items per debtor
Build thisReads the Openstaande postenlijst per debiteur (open items per debtor) under Rapporten > Rapporten > Debiteuren for one administratie.
- Takes
- Administratie, debtor (optional), up to period (optional)
- Returns
- Debtor code, debtor name, invoice number, invoice date, due date, currency, invoice amount, open amount
Get the aging analysis per debtor
Build thisRuns the Ouderdomsanalyse per debiteur (aging analysis), which splits each debtor's open items into up to 30, 31 to 60, 61 to 90 and over 90 days.
- Takes
- Administratie
- Returns
- Debtor code, debtor name, up to 30 days, 31 to 60 days, 61 to 90 days, over 90 days, total open
Get a debtor's account card
Build thisReads the Debiteurenkaart (debtor card) for one debtor: every entry posted to that debtor in the period you choose.
- Takes
- Administratie, debtor, from period, to period
- Returns
- Date, journal, entry number, invoice number, description, debit, credit, balance
Assign a bank line to an invoice
Build thisIn the Bankenmodule, opens Toewijzen bankregels (assign bank lines), matches one bank line to an open sales invoice and leaves the statement unposted for review.
- Takes
- Administratie, bank account, bank line date, amount, invoice number
- Returns
- Bank line, invoice number, debtor, assigned amount, unassigned amount
Automate Twinfield with a workflow
A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.
Debtors over 90 days, every administratie
Build this- Starts
- Every Monday at 7:00
- Step 1
- For each administratie you name, get the Ouderdomsanalyse per debiteur.
- Step 2
- Keep the debtors with an amount in the over 90 days column.
- Step 3
- Email you the list, one section per administratie, with the total open per debtor.
New open items, posted to your collections system
Build this- Starts
- Every weekday at 8:00
- Step 1
- For each administratie, get the open items per debtor.
- Step 2
- Keep the items that were not there on the last run.
- Step 3
- Post each one, with debtor, invoice number, due date and open amount, to your webhook.
Month-end receivables summary for your team
Build this- Starts
- Monthly on the 3rd at 9:00
- Step 1
- For each administratie, get the open items per debtor up to the period that just closed.
- Step 2
- Have an AI step summarize the total open and the five largest debtors per administratie.
- Step 3
- Email you the summary.
You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.
Once built, one call from your code
Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get open items per debtor” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "login.twinfield.com/get_open_items_per_debtor",
"input": {
"administratie": "Acme Holding B.V.",
"debtor": "1003"
}
}'
{
"status": "completed",
"data": {
"administratie": "Acme Holding B.V.",
"report": "Openstaande postenlijst per debiteur",
"items": [
{
"debtor_code": "1003",
"debtor_name": "Northwind Trading B.V.",
"invoice_number": "20260418",
"invoice_date": "2026-09-30",
"due_date": "2026-10-30",
"currency": "EUR",
"invoice_amount": 4235,
"open_amount": 4235
}
],
"total_open": 4747.5,
"count": 1
}
}
An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.
Twinfield’s own options
Wolters Kluwer documents the Twinfield API, made of webservices and REST APIs, for importing sales, purchase, cash and journal transactions and for retrieving customers, suppliers, transactions and open invoices. A client ID that is not yet certified gets 5% of the normal rate limits, and Wolters Kluwer does not support higher limits.
| Option | What it covers | What it takes |
|---|---|---|
| Twinfield API (webservices and REST) | Imports sales, purchase, cash and journal transactions. Retrieves customers, suppliers, transactions and open invoices per office. | A client ID with OAuth2 / OpenID Connect sign-in. Uncertified clients get 5% of the rate limits until the connection is certified. |
| Rapport ontwerpen | Adapted versions of the standard reports, made in Twinfield itself. | A Compleet Boekhouden subscription (Level 1 user). |
| Twinfield by hand | The reports under Rapporten > Rapporten > Debiteuren and the Bankenmodule, one administratie at a time. | A Twinfield user whose role (LVL1 to LVL9, SD) gives access to those reports and modules. |
Read on November 12, 2026: Twinfield API: Fair Use Policy and Limitations, API Best Practices: Introduction, Welke functies zijn er per Twinfield abonnement beschikbaar?.
Signing in to Twinfield
You sign in to Twinfield at login.twinfield.com with your own Twinfield user, and your role, from LVL1 to LVL9, decides which modules and reports you see. With Fous you sign in once through Twinfield's own sign-in with that account: the login is sealed with AES-256, never returned by the API or written to logs, and code and AI agents never see it.
Worth knowing
- Your role decides which reports you get
- The role of a user sets the reports and modules it reaches. An LVL4 user can request the Openstaande postenlijst debiteuren, while an LVL5 user only enters journals and requests the Invoerverslag.
- One administratie at a time
- An accountant's environment holds many administraties, and the API identifies each one by its office code. Reports run inside one administratie, so a method takes the administratie as an input.
- Two bank modules side by side
- The Classic bankenmodule, the orange tiles Bankafschriften and Boekingsinstructies, stays available: its phase-out planned for 31 October 2026 is postponed until further notice. Say which module a method should use.
- Service Desk entries wait for approval
- A Basis Boekhouden (SD) user can save transactions only as potloodboekingen (pencil entries), which are offered to the superuser for authorization before they count.
More in Accounting, tax and ERP software
- CONTPAQi
- Comarch ERP Optima
- Cegid Loop
- Domínio Sistemas
- Xero Practice Manager
- a3innuva
- Confirmation
- MyCodabox
- Xero bank feeds
- Exact Online
- Sage Intacct
- CCH Axcess
- TallyPrime
- TaxDome
- Drake Tax
- Dext Prepare
- Lexware Office
- MYOB Business
- 弥生会計
- SAP Concur
Other industries: Meta Business Suite and Ads Manager, PartsTrader, Dealertrack DMS, Gusto, Payapps, MWI Animal Health.
Frequently asked questions
Yes. Wolters Kluwer documents webservices and REST APIs for importing transactions and retrieving customers, suppliers, transactions and open invoices. A client ID that is not yet certified gets 5% of the normal rate limits, and Wolters Kluwer does not support higher limits than the normal ones.
Under Rapporten > Rapporten > Debiteuren. There you find the Debiteurenkaart, the Openstaande postenlijst per debiteur, the same list up to a chosen period, and the Ouderdomsanalyse per debiteur with buckets up to 30, 31 to 60, 61 to 90 and over 90 days.
For reading, yes. The Meekijken role (LVL6) gives real-time data, drill-down and the reports, which is what read methods need. A free Meekijken user for the accountant is available under conditions Wolters Kluwer sets.
1,000 API credits per minute per IP address, per client ID and per organisation, and 500 per client ID and organisation together. A query costs 1 credit and any other request 3. Uncertified client IDs get 5% of these numbers, and a request over the limit returns 429 Too Many Requests.
No. Fous is an independent product. You use it with your own Twinfield user, and a method reads and does only what that user's role allows.
Put Twinfield behind an API call
Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextSage IntacctCCH AxcessTallyPrimeMeta Business Suite and Ads ManagerHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Twinfield (Wolters Kluwer). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.