All about AFAS
AFAS: Get payments from AFAS
Get payments from AFAS: when an invoice is paid in AFAS, APIcenter can pass this on, for example to mark the order as paid in your webshop.
Updated November 9, 2026
This flow gets the payment status from AFAS. When an invoice is marked as paid in AFAS, APIcenter receives that the invoice is settled. APIcenter can then pass this on to another application, for example a webshop where the order is then marked as paid.
How it works
- APIcenter gets the payment transactions from AFAS that changed since the last run, based on the modification date.
- You choose the date from which APIcenter starts getting payments.
- Each payment is passed on to the other application of the integration.
What you need first
- Check that the target application supports receiving payments.
- The connector set is imported and the GetConnectors are added to the App connector. See Connect AFAS to APIcenter.
Tips
In the GetConnector for payments, you can set which journal (dagboek) is used. Make sure the payments of your webshop or CRM are booked in that journal. That way APIcenter does not send payments that are bound to fail in the target application.
You find all settings for this flow below, each with its own explanation.
Settings
The settings you see in the dashboard, with what each one does.
Enable URL Encoding of data in the endpoints of the source application
General flow settingEnable URL Encoding of data in the endpoints of the target application
General flow settingEnable URL encoding of data in endpoints
General flow settingUse administration mapping table
General flow settingWhat to do with a value that cannot be mapped using the mapping table
General flow settingNotifications Email address
NotificationsNotifications Slack webhook
NotificationsNotifications frequency
NotificationsReceive Notifications
NotificationsAmount to process
Run behaviourLast execution time
Run behaviourOffset
Run behaviourRun at specific times
Run behaviourThe date and time from which the flow retrieves records from AFAS, based on their modification date: for example articles, debtors, price lists, stock, payments or shipments that changed after this moment. APIcenter moves this date forward automatically after each run, so the next run continues where the last one stopped. Set it back in time to send records again, for example all stock after a stock count, because AFAS does not register a stock correction as a change. For AFAS the default is 1 January 2025.