Monitor ERP + Adyen
Everything you need to connect Monitor ERP and Adyen: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- Connect in about 20 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 10 minutes
Prepare Monitor ERP
- Open the Monitor integration / API setup
- Generate or retrieve the API access key
- Confirm the technical integration user if relevant
- Note the correct company or database context
- Enter the values in Junipeer
- about 10 minutes
Prepare Adyen
- Log in to Customer Area
- Open API credentials
- Create or select the credential
- Generate the API key
- Copy the values securely
- Review roles and permissions
- Paste the credentials into Junipeer
Connect and test
Enter the details in Junipeer, switch on the flows you need and test with one order before you go live.
Getting started with Junipeer
2. Settings
The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.
In Junipeer every setting has a ? that opens the same explanation next to the form, right when you need it. With the Junipeer MCP your AI assistant can also propose the settings from your own data.
How the Junipeer MCP worksSettings for Monitor ERP (15)
| Setting | What it controls | Key |
|---|---|---|
| API URL | Enter the address of your Monitor API, for example https://host:8001 . | monitor_api_base_url |
| Company Number | Enter the number of the Monitor company to connect to, for example 001.1 . | monitor_company_number |
| Customer Levels | Choose which kinds of Monitor customers are fetched and sent on. | monitor_customer_levels |
| Default Monitor ERP Warehouse | Choose the Monitor warehouse that is treated as the default when stock is fetched from Monitor. | monitor_default_warehouse_id |
| Exclude Orders created before this date | Choose a date. Orders created before this date are not synced. | stdintegration_filter_monitor_erp_order_created_date |
| Find the Monitor Customer By | Decide how Junipeer finds the Monitor customer an order belongs to. | monitor_order_customer_lookup |
| Language Code | Enter the language code used when connecting to Monitor, for example sv . | monitor_language_code |
| Order Row Type | Choose the row type used for order lines in the Monitor order. | monitor_order_row_type |
Show all 15 settings
| Setting | What it controls | Key |
|---|---|---|
| Order Type | Optional. Choose the Monitor order type given to customer orders created in Monitor. | monitor_order_type_id |
| Password | Enter the password for the Monitor user above. | monitor_password |
| Project | Optional. Choose the Monitor project used on customer orders created in Monitor. | monitor_project_id |
| Sales Price List | Choose the Monitor price list that article prices are taken from. | monitor_article_price_list_id |
| Stock Order | Decide whether customer orders are created as stock orders in Monitor. | monitor_is_stock_order |
| Username | Enter the Monitor username Junipeer should log in with. | monitor_username |
| Warehouse | Optional. Choose the Monitor warehouse used on customer orders created in Monitor. | monitor_warehouse_id |
Settings for Adyen (5)
| Setting | What it controls | Key |
|---|---|---|
| Adyen Merchant Reference Number | Clean up the merchant reference from Adyen before Junipeer uses it when exporting payouts to your accounting system. | adyen_order_reference_manipulator |
| Choose Company | Choose the company in Adyen that this integration should use. | adyen_company_id |
| Reports API Key | Enter the API key Junipeer uses to read reports from Adyen. | adyen_report_api_key |
| Test Mode | Decide whether the connection to Adyen should run in test mode . | adyen_test_mode |
| Web Service API Key | Enter the API key for the Adyen Web Service . | adyen_webhook_api_key |
3. Troubleshooting
Choose what you see. Each case shows the cause and the solution.
MediumFor troubleshooting common errors, see the Error Codes page or your connector pa
For troubleshooting common errors, see the Error Codes page or your connector pair's troubleshooting section.
Refer to the platform setup guide for resolution steps.
MediumTransactions not matching
- Junipeer matches using reference numbers created during order sync. If an invoice was created manually in the ERP (not through Junipeer), it will not have the required reference and cannot be matched
See symptoms and resolution for details.
Junipeer matches using reference numbers created during order sync. If an invoice was created manually in the ERP (not through Junipeer), it will not have the required reference and cannot be matched automatically.
MediumWebhook not receiving data
- verify the webhook URL in the Adyen portal matches the endpoint shown on Junipeer's Webhooks page. Also check that the webhook is active (not paused) in Adyen.
See symptoms and resolution for details.
verify the webhook URL in the Adyen portal matches the endpoint shown on Junipeer's Webhooks page. Also check that the webhook is active (not paused) in Adyen.
MediumFee account errors
- make sure the fee account configured in your ERP and Junipeer's payment settings exists and is active. Missing fee accounts will cause payout processing to fail.
See symptoms and resolution for details.
make sure the fee account configured in your ERP and Junipeer's payment settings exists and is active. Missing fee accounts will cause payout processing to fail.
4. More guides
Did this page help you?