[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fvMIfCzQxd_QzOCz2KBd9nAcY9ehNywubWnU2zJMxxqM":3},{"item":4},{"id":5,"idKnowledge":6,"idDomain":7,"idCluster":7,"kindOverride":8,"slug":9,"title":10,"description":11,"bodyMarkdown":12,"bodyHtml":13,"author":14,"date":15,"createdAt":16,"topics":17,"image":25,"hasDownload":26,"fileName":7,"youtubeId":27},"459","206833DB-1EE3-B748-9293-4D1976AB6E12","","article","e-boekhouden-koppelen-aan-filemaker-zo-werkt-het","Connecting e-Boekhouden to FileMaker: how it works","How do you connect e-Boekhouden.nl to FileMaker without duplicate work? Practical approach, technique and pitfalls, including an AI-driven app for purchase invoices.","A sales order is already in FileMaker, but then gets retyped once more in e-Boekhouden.nl. A purchase invoice arrives as a PDF in the administration's mailbox, gets manually checked, and only then entered. A payment is visible in the bank transactions of e-Boekhouden.nl, but nobody in FileMaker knows that the order is financially complete with that payment. This article shows you how to solve that by **setting up the e-Boekhouden connection to FileMaker** properly, including an approach through which Loggix even automatically scans and processes purchase invoices.\n\ne-Boekhouden.nl is widely used by small and medium-sized businesses, accounting firms, and freelancers, precisely because the package is easy to use and offers a well-documented API. That makes it a suitable candidate to connect to a FileMaker environment where daily operations take place: quotes, projects, work orders, hours, or inventory. FileMaker remains the place where employees work, e-Boekhouden.nl remains authoritative for financial processing. The connection ensures that these two worlds automatically inform each other, without anyone having to enter data twice.\n\n## What should a connection with e-Boekhouden.nl concretely solve?\n\nThe question is not \"can we connect\", but \"exactly which manual work disappears because of this\". With e-Boekhouden.nl, it usually concerns one of these three flows:\n\n1. **Write off sales invoices.** FileMaker compiles an invoice based on an order, project, or work order and sends it via the API to e-Boekhouden.nl, including customer details, VAT code, and invoice lines.\n2. **Retrieve payment statuses.** e-Boekhouden.nl registers when an invoice has been paid. FileMaker retrieves that status, so the back office or planning immediately sees which jobs are financially complete.\n3. **Synchronize debtors and general ledger data.** New customers are automatically created or recognized, so no duplicate debtors are created.\n\nTake an installation company that records work orders in FileMaker. Once a technician completes an order, FileMaker bundles the material and hourly lines into an invoice proposal. After approval by the back office, FileMaker automatically sends that invoice to e-Boekhouden.nl. When the customer pays, that status comes back in FileMaker and planning immediately sees that the file is financially closed — without anyone having to search in two systems.\n\n## Which system is authoritative: FileMaker or e-Boekhouden.nl?\n\nA common mistake is wanting to synchronize everything in both directions. That feels complete, but makes the connection unnecessarily complex and error-prone. If a customer name can be changed both in FileMaker and in e-Boekhouden.nl, which system is right if they start to differ?\n\nTherefore, establish per data type who the source is:\n\n- **FileMaker is authoritative** for operational data: orders, projects, work orders, planning, internal statuses, and draft invoices.\n- **e-Boekhouden.nl is authoritative** for financial processing: final invoice numbers, VAT remittance, payment statuses, and general ledger entries.\n\nThe status of an invoice also deserves attention. In FileMaker, an invoice can still be a draft while a project manager reviews it. Once it has been sent to e-Boekhouden.nl, it is a financial document that should not be arbitrarily changed. Therefore, only send approved invoices, and process corrections via a credit note instead of adjusting the source document.\n\n### Start small: what is the minimal first version?\n\nStart with the flow that eliminates the most manual work. For most organizations, that is: verify or create debtor, send sales invoice to e-Boekhouden.nl, and save the external invoice number back in FileMaker. Retrieving payment statuses is usually a logical second step, and processing purchase invoices often follows as a third phase. By working in phases, [you test the process with real transactions](https:\u002F\u002Floggix.com\u002Fblog\u002Fhow-to-test-a-workflow-with-real-users\u002F) before you try to catch all exceptions at once.\n\n## How does the technical connection with the e-Boekhouden API work?\n\ne-Boekhouden.nl offers a REST API through which external systems can exchange debtors, invoices, transactions, and balances. Data is sent and received in JSON format, and authentication takes place via a secure session token that needs to be refreshed periodically.\n\nFileMaker can call this API directly via its built-in web service functions. For a clear connection — for example, only sales invoices and payment statuses — that is often sufficient and keeps management entirely within the existing FileMaker environment.\n\nIn more complex scenarios, such as high volumes, multiple connected systems, or automated processing outside business hours, an intermediate layer is wiser. That layer handles authentication, monitors queues, catches errors, and keeps logging outside FileMaker. That makes the solution somewhat more extensive to build, but considerably more stable in use and easier to expand.\n\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F188?w=700&f=webp\" alt=\"FileMaker and e-Boekhouden.nl connected by arrows with invoice and payment data\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n## How does Loggix use AI to automatically process purchase invoices?\n\nOne of the most time-consuming tasks around e-Boekhouden.nl is not sending sales invoices, but processing incoming purchase invoices: retyping a PDF from email, photographing receipts, verifying amounts, and manually booking them. To speed this up, Loggix has developed a **Claude Skill** that is completely based on the official API documentation of e-Boekhouden.nl.\n\nThis Skill gives the AI model exactly the knowledge needed to correctly communicate with the e-Boekhouden API: which fields are mandatory, how VAT codes and general ledger accounts are provided, and how a transaction or invoice is technically submitted correctly. Based on that Skill, Loggix has built a **mobile app** with which an employee simply photographs or scans an incoming invoice with their phone.\n\nThe app works in practice as follows:\n\n1. The employee takes a photo of the purchase invoice or scans a received PDF.\n2. The AI reads supplier, invoice date, amount, VAT, and invoice lines from the scan.\n3. The Claude Skill translates this data into the correct format for the e-Boekhouden API.\n4. The invoice is automatically created in e-Boekhouden.nl, linked to the correct creditor and general ledger account.\n5. In case of doubt or an unclear scanned invoice, the employee gets a check step before the invoice is actually booked.\n\nThe result: a purchase invoice that previously took five manual steps — opening, reading, retyping, checking, booking — is now processed in accounting within seconds of taking a photo. For companies with many suppliers or high volumes of purchase invoices, this is often the step that saves the most time, more than the connection for sales invoices.\n\n## What makes the connection reliable in practice?\n\nA connection only works well when exceptions are also thought through. What happens if the connection to e-Boekhouden.nl temporarily fails? What if an invoice is rejected because a VAT code is missing? Or if an employee accidentally clicks \"send\" twice?\n\nTherefore, keep a unique identifier for each shipment: the external invoice number, the sending date, and the technical status. This way FileMaker recognizes whether a record has already been processed and prevents you from double-posting.\n\nError messages should be useful for the administration, not just for a developer. \"HTTP 400\" gets nobody anywhere. \"Invoice 2026-104 is missing a VAT code on line 3\" does — including the ability to correct the source data directly and resend it.\n\nSecure the connection as seriously as you would secure the accounting itself. API keys and session tokens should not be lying around in scripts or visible fields. Work with limited user permissions and a process for renewing tokens, and document which employees are allowed to send invoices, correct them, or resubmit them.\n\n## How do you test the connection before it goes live?\n\nA test invoice with one line and a standard VAT rate tells little about reality. Test with realistic situations:\n\n- A new customer or supplier that does not yet exist in e-Boekhouden.nl.\n- An existing customer with a changed address or VAT number.\n- An invoice with a discount or multiple VAT rates on one invoice.\n- A credit note on a previously sent invoice.\n- A payment that comes in installments.\n- A scanned purchase invoice with an unclear or upside-down photo, to see how the AI processing handles it.\n\nAlso agree in advance on management: who checks daily whether invoices are in an error status in e-Boekhouden.nl? Who approves a new general ledger account or VAT code? And who periodically checks whether the e-Boekhouden API itself has changed? A connection is not a one-time project, but requires light ongoing management.\n\n## Checklist: is your organization ready to connect e-Boekhouden to FileMaker?\n\n- [ ] You know exactly which data is currently entered or checked twice.\n- [ ] Per data type, it has been established which system is authoritative.\n- [ ] Invoices are only passed on if they are internally approved.\n- [ ] There is an error handling plan that is understandable to the administration.\n- [ ] API keys are stored securely, not loose in scripts or fields.\n- [ ] It has been decided whether purchase invoices are processed via scan\u002FAI or remain manual.\n- [ ] Someone has been appointed to manage the connection after going live.\n\n## Frequently Asked Questions\n\n**Does e-Boekhouden.nl have a suitable API for a direct connection?**\nYes, e-Boekhouden.nl offers a REST API with JSON that is suitable for creating debtors, sending invoices, and retrieving payment statuses. The documentation is relatively accessible, which also makes it suitable as a basis for AI applications such as the Claude Skill that Loggix has developed.\n\n**Can the connection also process purchase invoices, not just sales invoices?**\nYes. In addition to sending sales invoices, a connection can also process purchase invoices. Loggix now does this with a mobile app: an employee scans the invoice, AI reads the data, and the invoice is automatically created in e-Boekhouden.nl.\n\n**Is an intermediate layer necessary, or can FileMaker talk directly to e-Boekhouden.nl?**\nWith a limited connection — for example, only sales invoices and payment statuses — FileMaker can communicate directly with the API. With higher volumes, multiple connected systems, or automated AI processing, an intermediate layer is more stable and easier to maintain.\n\n**When is this connection worth the investment?**\nEspecially when invoices are sent daily or weekly, many purchase invoices are processed manually, or when operational teams in FileMaker need to be able to see whether an order is financially complete. With very low volumes or a still-changing invoice process, it is often smarter to first stabilize the process itself.\n\nA successful connection with e-Boekhouden.nl ultimately does not feel like an additional system, but like the elimination of unnecessary steps: employees work where they already work, invoices come in automatically and correctly, and exceptions become visible before they become a problem. Loggix helps organizations with both the technical connection itself — via the FileMaker environment, an API integration, or a light intermediate layer — as well as with AI applications such as the scanning app for purchase invoices, and in a brief preliminary investigation gladly thinks along about which step yields the most for your situation.","\u003Cp>A sales order is already in FileMaker, but then gets retyped once more in e-Boekhouden.nl. A purchase invoice arrives as a PDF in the administration's mailbox, gets manually checked, and only then entered. A payment is visible in the bank transactions of e-Boekhouden.nl, but nobody in FileMaker knows that the order is financially complete with that payment. This article shows you how to solve that by \u003Cstrong>setting up the e-Boekhouden connection to FileMaker\u003C\u002Fstrong> properly, including an approach through which Loggix even automatically scans and processes purchase invoices.\u003C\u002Fp>\n\u003Cp>e-Boekhouden.nl is widely used by small and medium-sized businesses, accounting firms, and freelancers, precisely because the package is easy to use and offers a well-documented API. That makes it a suitable candidate to connect to a FileMaker environment where daily operations take place: quotes, projects, work orders, hours, or inventory. FileMaker remains the place where employees work, e-Boekhouden.nl remains authoritative for financial processing. The connection ensures that these two worlds automatically inform each other, without anyone having to enter data twice.\u003C\u002Fp>\n\u003Ch2>What should a connection with e-Boekhouden.nl concretely solve?\u003C\u002Fh2>\n\u003Cp>The question is not "can we connect", but "exactly which manual work disappears because of this". With e-Boekhouden.nl, it usually concerns one of these three flows:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Write off sales invoices.\u003C\u002Fstrong> FileMaker compiles an invoice based on an order, project, or work order and sends it via the API to e-Boekhouden.nl, including customer details, VAT code, and invoice lines.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Retrieve payment statuses.\u003C\u002Fstrong> e-Boekhouden.nl registers when an invoice has been paid. FileMaker retrieves that status, so the back office or planning immediately sees which jobs are financially complete.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Synchronize debtors and general ledger data.\u003C\u002Fstrong> New customers are automatically created or recognized, so no duplicate debtors are created.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Take an installation company that records work orders in FileMaker. Once a technician completes an order, FileMaker bundles the material and hourly lines into an invoice proposal. After approval by the back office, FileMaker automatically sends that invoice to e-Boekhouden.nl. When the customer pays, that status comes back in FileMaker and planning immediately sees that the file is financially closed — without anyone having to search in two systems.\u003C\u002Fp>\n\u003Ch2>Which system is authoritative: FileMaker or e-Boekhouden.nl?\u003C\u002Fh2>\n\u003Cp>A common mistake is wanting to synchronize everything in both directions. That feels complete, but makes the connection unnecessarily complex and error-prone. If a customer name can be changed both in FileMaker and in e-Boekhouden.nl, which system is right if they start to differ?\u003C\u002Fp>\n\u003Cp>Therefore, establish per data type who the source is:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>FileMaker is authoritative\u003C\u002Fstrong> for operational data: orders, projects, work orders, planning, internal statuses, and draft invoices.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>e-Boekhouden.nl is authoritative\u003C\u002Fstrong> for financial processing: final invoice numbers, VAT remittance, payment statuses, and general ledger entries.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The status of an invoice also deserves attention. In FileMaker, an invoice can still be a draft while a project manager reviews it. Once it has been sent to e-Boekhouden.nl, it is a financial document that should not be arbitrarily changed. Therefore, only send approved invoices, and process corrections via a credit note instead of adjusting the source document.\u003C\u002Fp>\n\u003Ch3>Start small: what is the minimal first version?\u003C\u002Fh3>\n\u003Cp>Start with the flow that eliminates the most manual work. For most organizations, that is: verify or create debtor, send sales invoice to e-Boekhouden.nl, and save the external invoice number back in FileMaker. Retrieving payment statuses is usually a logical second step, and processing purchase invoices often follows as a third phase. By working in phases, \u003Ca href=\"https:\u002F\u002Floggix.com\u002Fblog\u002Fhow-to-test-a-workflow-with-real-users\u002F\">you test the process with real transactions\u003C\u002Fa> before you try to catch all exceptions at once.\u003C\u002Fp>\n\u003Ch2>How does the technical connection with the e-Boekhouden API work?\u003C\u002Fh2>\n\u003Cp>e-Boekhouden.nl offers a REST API through which external systems can exchange debtors, invoices, transactions, and balances. Data is sent and received in JSON format, and authentication takes place via a secure session token that needs to be refreshed periodically.\u003C\u002Fp>\n\u003Cp>FileMaker can call this API directly via its built-in web service functions. For a clear connection — for example, only sales invoices and payment statuses — that is often sufficient and keeps management entirely within the existing FileMaker environment.\u003C\u002Fp>\n\u003Cp>In more complex scenarios, such as high volumes, multiple connected systems, or automated processing outside business hours, an intermediate layer is wiser. That layer handles authentication, monitors queues, catches errors, and keeps logging outside FileMaker. That makes the solution somewhat more extensive to build, but considerably more stable in use and easier to expand.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fapi\u002Fknowledge\u002Finline-image\u002F188?w=700&f=webp\" alt=\"FileMaker and e-Boekhouden.nl connected by arrows with invoice and payment data\" loading=\"lazy\" class=\"w-full sm:w-1\u002F3 sm:float-left sm:mr-7 mb-5 rounded-2xl border border-[#E8E8ED] bg-[#F5F5F7]\" \u002F>\n\n\u003Ch2>How does Loggix use AI to automatically process purchase invoices?\u003C\u002Fh2>\n\u003Cp>One of the most time-consuming tasks around e-Boekhouden.nl is not sending sales invoices, but processing incoming purchase invoices: retyping a PDF from email, photographing receipts, verifying amounts, and manually booking them. To speed this up, Loggix has developed a \u003Cstrong>Claude Skill\u003C\u002Fstrong> that is completely based on the official API documentation of e-Boekhouden.nl.\u003C\u002Fp>\n\u003Cp>This Skill gives the AI model exactly the knowledge needed to correctly communicate with the e-Boekhouden API: which fields are mandatory, how VAT codes and general ledger accounts are provided, and how a transaction or invoice is technically submitted correctly. Based on that Skill, Loggix has built a \u003Cstrong>mobile app\u003C\u002Fstrong> with which an employee simply photographs or scans an incoming invoice with their phone.\u003C\u002Fp>\n\u003Cp>The app works in practice as follows:\u003C\u002Fp>\n\u003Col>\n\u003Cli>The employee takes a photo of the purchase invoice or scans a received PDF.\u003C\u002Fli>\n\u003Cli>The AI reads supplier, invoice date, amount, VAT, and invoice lines from the scan.\u003C\u002Fli>\n\u003Cli>The Claude Skill translates this data into the correct format for the e-Boekhouden API.\u003C\u002Fli>\n\u003Cli>The invoice is automatically created in e-Boekhouden.nl, linked to the correct creditor and general ledger account.\u003C\u002Fli>\n\u003Cli>In case of doubt or an unclear scanned invoice, the employee gets a check step before the invoice is actually booked.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The result: a purchase invoice that previously took five manual steps — opening, reading, retyping, checking, booking — is now processed in accounting within seconds of taking a photo. For companies with many suppliers or high volumes of purchase invoices, this is often the step that saves the most time, more than the connection for sales invoices.\u003C\u002Fp>\n\u003Ch2>What makes the connection reliable in practice?\u003C\u002Fh2>\n\u003Cp>A connection only works well when exceptions are also thought through. What happens if the connection to e-Boekhouden.nl temporarily fails? What if an invoice is rejected because a VAT code is missing? Or if an employee accidentally clicks "send" twice?\u003C\u002Fp>\n\u003Cp>Therefore, keep a unique identifier for each shipment: the external invoice number, the sending date, and the technical status. This way FileMaker recognizes whether a record has already been processed and prevents you from double-posting.\u003C\u002Fp>\n\u003Cp>Error messages should be useful for the administration, not just for a developer. "HTTP 400" gets nobody anywhere. "Invoice 2026-104 is missing a VAT code on line 3" does — including the ability to correct the source data directly and resend it.\u003C\u002Fp>\n\u003Cp>Secure the connection as seriously as you would secure the accounting itself. API keys and session tokens should not be lying around in scripts or visible fields. Work with limited user permissions and a process for renewing tokens, and document which employees are allowed to send invoices, correct them, or resubmit them.\u003C\u002Fp>\n\u003Ch2>How do you test the connection before it goes live?\u003C\u002Fh2>\n\u003Cp>A test invoice with one line and a standard VAT rate tells little about reality. Test with realistic situations:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A new customer or supplier that does not yet exist in e-Boekhouden.nl.\u003C\u002Fli>\n\u003Cli>An existing customer with a changed address or VAT number.\u003C\u002Fli>\n\u003Cli>An invoice with a discount or multiple VAT rates on one invoice.\u003C\u002Fli>\n\u003Cli>A credit note on a previously sent invoice.\u003C\u002Fli>\n\u003Cli>A payment that comes in installments.\u003C\u002Fli>\n\u003Cli>A scanned purchase invoice with an unclear or upside-down photo, to see how the AI processing handles it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Also agree in advance on management: who checks daily whether invoices are in an error status in e-Boekhouden.nl? Who approves a new general ledger account or VAT code? And who periodically checks whether the e-Boekhouden API itself has changed? A connection is not a one-time project, but requires light ongoing management.\u003C\u002Fp>\n\u003Ch2>Checklist: is your organization ready to connect e-Boekhouden to FileMaker?\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> You know exactly which data is currently entered or checked twice.\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Per data type, it has been established which system is authoritative.\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Invoices are only passed on if they are internally approved.\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> There is an error handling plan that is understandable to the administration.\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> API keys are stored securely, not loose in scripts or fields.\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> It has been decided whether purchase invoices are processed via scan\u002FAI or remain manual.\u003C\u002Fli>\n\u003Cli>\u003Cinput disabled=\"\" type=\"checkbox\"> Someone has been appointed to manage the connection after going live.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Frequently Asked Questions\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Does e-Boekhouden.nl have a suitable API for a direct connection?\u003C\u002Fstrong>\nYes, e-Boekhouden.nl offers a REST API with JSON that is suitable for creating debtors, sending invoices, and retrieving payment statuses. The documentation is relatively accessible, which also makes it suitable as a basis for AI applications such as the Claude Skill that Loggix has developed.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Can the connection also process purchase invoices, not just sales invoices?\u003C\u002Fstrong>\nYes. In addition to sending sales invoices, a connection can also process purchase invoices. Loggix now does this with a mobile app: an employee scans the invoice, AI reads the data, and the invoice is automatically created in e-Boekhouden.nl.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Is an intermediate layer necessary, or can FileMaker talk directly to e-Boekhouden.nl?\u003C\u002Fstrong>\nWith a limited connection — for example, only sales invoices and payment statuses — FileMaker can communicate directly with the API. With higher volumes, multiple connected systems, or automated AI processing, an intermediate layer is more stable and easier to maintain.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>When is this connection worth the investment?\u003C\u002Fstrong>\nEspecially when invoices are sent daily or weekly, many purchase invoices are processed manually, or when operational teams in FileMaker need to be able to see whether an order is financially complete. With very low volumes or a still-changing invoice process, it is often smarter to first stabilize the process itself.\u003C\u002Fp>\n\u003Cp>A successful connection with e-Boekhouden.nl ultimately does not feel like an additional system, but like the elimination of unnecessary steps: employees work where they already work, invoices come in automatically and correctly, and exceptions become visible before they become a problem. Loggix helps organizations with both the technical connection itself — via the FileMaker environment, an API integration, or a light intermediate layer — as well as with AI applications such as the scanning app for purchase invoices, and in a brief preliminary investigation gladly thinks along about which step yields the most for your situation.\u003C\u002Fp>\n","Jeroen","2026-08-05",1785944804000,[18,19,20,21,22,23,24],"e-Boekhouden koppelen","FileMaker integratie","boekhoudkoppeling","API koppeling FileMaker","AI facturen scannen","Claude Skill","factuurverwerking automatiseren","\u002Fapi\u002Fknowledge\u002Fimage\u002F459\u002F?v=4cd00bd2575e",false,null]