[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fJoOZL2Xf8CIKAToBQhLd6t1aE3k6Cc10_m8YO0mO8-o":3},{"item":4},{"id":5,"idKnowledge":6,"slug":7,"title":8,"description":9,"bodyMarkdown":10,"bodyHtml":11,"author":12,"date":13,"createdAt":14,"topics":15,"image":20,"hasDownload":21,"fileName":22,"youtubeId":23},"90","4BAA36F2-93EE-2244-948C-8619C423500A","exact-online-koppelen-aan-filemaker-zo-automatiseer-je-facturen-veilig-en-foutloos","Connecting Exact Online to FileMaker: how to automate invoices securely and without errors","Learn how an API integration between FileMaker and Exact Online makes invoice processing faster, safer, and more accurate — without manual retyping.","An API integration between FileMaker and Exact Online eliminates manual retyping, reduces the risk of errors, and ensures financial data is always up to date. This article explains how such an integration works, what the benefits are for IT and finance managers, and what to watch out for.\n\n## Why an integration between FileMaker and Exact Online?\n\nMany organisations manage their operational data (orders, projects, clients) in FileMaker, but enter financial transactions manually in Exact Online. This creates three problems:\n\n- **Duplicate work** — the same data is entered in two places.\n- **Errors** — manual retyping introduces mistakes in amounts, VAT codes, or relation numbers.\n- **Delays** — invoices become available later, slowing down cash flow and reporting.\n\nAn API integration solves this by allowing FileMaker and Exact Online to communicate directly with each other.\n\n## How does the Exact Online API integration work technically?\n\nExact Online offers a REST API that allows external systems — such as FileMaker — to read and write data. The integration works broadly as follows:\n\n1. **Authentication via OAuth 2.0** — FileMaker obtains a secured access token through the Exact Online OAuth flow. Tokens are refreshed automatically, without users needing to share login credentials.\n2. **Retrieving data** — FileMaker sends a GET request to the Exact API to retrieve, for example, relations, general ledger accounts, or outstanding items.\n3. **Writing data** — When creating an invoice, FileMaker sends a POST request with the invoice lines, VAT codes, relation ID, and due date to Exact Online.\n4. **Status feedback** — Exact Online returns a transaction ID and status, which FileMaker stores. This makes it always traceable which records have already been processed.\n5. **Error handling** — If a request fails, FileMaker logs the error code and notifies the user, so nothing gets silently stuck.\n\n## Which processes can you automate?\n\n- **Creating sales invoices** — post an invoice directly in Exact Online from a FileMaker order or project.\n- **Synchronising customer and supplier data** — new relations in FileMaker are automatically created in Exact, and vice versa.\n- **Retrieving payment status** — FileMaker periodically retrieves the payment status, so account managers always see whether an invoice is open or paid.\n- **Processing bank statements** — payments received in Exact are fed back to the correct project or order in FileMaker.\n\n## What about security?\n\nSecurity is a top priority for financial integrations. The Loggix integration applies the following measures:\n\n- **OAuth 2.0 with short-lived tokens** — no passwords are stored or transmitted.\n- **HTTPS for all communication** — data is encrypted in transit.\n- **Role-based access** — only authorised FileMaker accounts may call the API scripts.\n- **Audit log in FileMaker** — every API request (including timestamp, user, and result) is logged for auditing and compliance.\n- **No sensitive data in scripts** — client secrets are stored in secured FileMaker value lists or external vaults, not in readable script steps.\n\n## What does it deliver in practice?\n\n| Situation | Before integration | After integration |\n|---|---|---|\n| Creating an invoice | 5–10 min. manually | \u003C 5 seconds automatically |\n| Error rate | 2–5% (manual entry) | Near 0% |\n| Viewing payment status | Manual check daily | Real-time in FileMaker |\n| Audit trail | Fragmented | Centrally logged |\n\n## What should you watch out for during implementation?\n\n1. **Exact Online subscription** — check whether your subscription includes API access (Standard or higher).\n2. **Division ID** — Exact Online works with divisions; ensure FileMaker always includes the correct division in every API request.\n3. **Mapping VAT codes** — FileMaker VAT codes must correspond exactly to the Exact Online general ledger structure. Set up a translation table.\n4. **Rate limiting** — Exact Online enforces a limit of 60 requests per minute per token. Build a queue in FileMaker for bulk processing.\n5. **Use a test environment** — Exact Online provides a sandbox. Always test with dummy data first before going live.\n\n## Ready to integrate?\n\nA well-implemented API integration between FileMaker and Exact Online saves hours per week, reduces errors, and gives finance managers real-time insight. Loggix builds these integrations on a custom basis, tailored to your processes and security requirements. Get in touch for a no-obligation conversation.","\u003Cp>An API integration between FileMaker and Exact Online eliminates manual retyping, reduces the risk of errors, and ensures financial data is always up to date. This article explains how such an integration works, what the benefits are for IT and finance managers, and what to watch out for.\u003C\u002Fp>\n\u003Ch2>Why an integration between FileMaker and Exact Online?\u003C\u002Fh2>\n\u003Cp>Many organisations manage their operational data (orders, projects, clients) in FileMaker, but enter financial transactions manually in Exact Online. This creates three problems:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Duplicate work\u003C\u002Fstrong> — the same data is entered in two places.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Errors\u003C\u002Fstrong> — manual retyping introduces mistakes in amounts, VAT codes, or relation numbers.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Delays\u003C\u002Fstrong> — invoices become available later, slowing down cash flow and reporting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>An API integration solves this by allowing FileMaker and Exact Online to communicate directly with each other.\u003C\u002Fp>\n\u003Ch2>How does the Exact Online API integration work technically?\u003C\u002Fh2>\n\u003Cp>Exact Online offers a REST API that allows external systems — such as FileMaker — to read and write data. The integration works broadly as follows:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Authentication via OAuth 2.0\u003C\u002Fstrong> — FileMaker obtains a secured access token through the Exact Online OAuth flow. Tokens are refreshed automatically, without users needing to share login credentials.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Retrieving data\u003C\u002Fstrong> — FileMaker sends a GET request to the Exact API to retrieve, for example, relations, general ledger accounts, or outstanding items.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Writing data\u003C\u002Fstrong> — When creating an invoice, FileMaker sends a POST request with the invoice lines, VAT codes, relation ID, and due date to Exact Online.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Status feedback\u003C\u002Fstrong> — Exact Online returns a transaction ID and status, which FileMaker stores. This makes it always traceable which records have already been processed.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Error handling\u003C\u002Fstrong> — If a request fails, FileMaker logs the error code and notifies the user, so nothing gets silently stuck.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Which processes can you automate?\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Creating sales invoices\u003C\u002Fstrong> — post an invoice directly in Exact Online from a FileMaker order or project.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Synchronising customer and supplier data\u003C\u002Fstrong> — new relations in FileMaker are automatically created in Exact, and vice versa.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Retrieving payment status\u003C\u002Fstrong> — FileMaker periodically retrieves the payment status, so account managers always see whether an invoice is open or paid.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Processing bank statements\u003C\u002Fstrong> — payments received in Exact are fed back to the correct project or order in FileMaker.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What about security?\u003C\u002Fh2>\n\u003Cp>Security is a top priority for financial integrations. The Loggix integration applies the following measures:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>OAuth 2.0 with short-lived tokens\u003C\u002Fstrong> — no passwords are stored or transmitted.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>HTTPS for all communication\u003C\u002Fstrong> — data is encrypted in transit.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Role-based access\u003C\u002Fstrong> — only authorised FileMaker accounts may call the API scripts.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Audit log in FileMaker\u003C\u002Fstrong> — every API request (including timestamp, user, and result) is logged for auditing and compliance.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No sensitive data in scripts\u003C\u002Fstrong> — client secrets are stored in secured FileMaker value lists or external vaults, not in readable script steps.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>What does it deliver in practice?\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Situation\u003C\u002Fth>\n\u003Cth>Before integration\u003C\u002Fth>\n\u003Cth>After integration\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Creating an invoice\u003C\u002Ftd>\n\u003Ctd>5–10 min. manually\u003C\u002Ftd>\n\u003Ctd>< 5 seconds automatically\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Error rate\u003C\u002Ftd>\n\u003Ctd>2–5% (manual entry)\u003C\u002Ftd>\n\u003Ctd>Near 0%\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Viewing payment status\u003C\u002Ftd>\n\u003Ctd>Manual check daily\u003C\u002Ftd>\n\u003Ctd>Real-time in FileMaker\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Audit trail\u003C\u002Ftd>\n\u003Ctd>Fragmented\u003C\u002Ftd>\n\u003Ctd>Centrally logged\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Ch2>What should you watch out for during implementation?\u003C\u002Fh2>\n\u003Col>\n\u003Cli>\u003Cstrong>Exact Online subscription\u003C\u002Fstrong> — check whether your subscription includes API access (Standard or higher).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Division ID\u003C\u002Fstrong> — Exact Online works with divisions; ensure FileMaker always includes the correct division in every API request.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mapping VAT codes\u003C\u002Fstrong> — FileMaker VAT codes must correspond exactly to the Exact Online general ledger structure. Set up a translation table.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rate limiting\u003C\u002Fstrong> — Exact Online enforces a limit of 60 requests per minute per token. Build a queue in FileMaker for bulk processing.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Use a test environment\u003C\u002Fstrong> — Exact Online provides a sandbox. Always test with dummy data first before going live.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch2>Ready to integrate?\u003C\u002Fh2>\n\u003Cp>A well-implemented API integration between FileMaker and Exact Online saves hours per week, reduces errors, and gives finance managers real-time insight. Loggix builds these integrations on a custom basis, tailored to your processes and security requirements. Get in touch for a no-obligation conversation.\u003C\u002Fp>\n","Jeroen","2026-06-30",1782825233000,[16,17,18,19],"FileMaker","Exact Online","API","ERP","\u002Fapi\u002Fknowledge\u002Fimage\u002F90\u002F?v=08dd008c9df1",false,"",null]