Which direction does data move between Visma.net ERP and Amazon Seller Central?

The main flow is from Amazon into Visma. Orders and shipments flow into Visma as customer invoices, and Amazon financial settlement events post into Visma journal transactions and accounts. Visma can also push order returns and credit notes back to Amazon, though this is less common. The integration is designed to keep Visma's customer invoices and settlement accounts in agreement with Amazon's order and financial records.

What is the Restricted Data Token and why does Amazon require it?

Amazon restricts direct access to buyer addresses, phone numbers, and payment methods for privacy and compliance. When your integration needs this data, ml-connector calls the Amazon Tokens API to obtain a Restricted Data Token (RDT) for that specific request, keeping PII data access audited and time-limited. The RDT expires in one hour, so ml-connector refreshes it only when needed.

How does the integration handle Amazon's lack of webhooks for financial events?

Amazon does not push financial settlement events; they must be polled. ml-connector polls the Amazon Finances API on a daily schedule or on a cadence tied to your settlement calendar, and deduplicates entries using the financial event group ID and event ID. EventBridge or SQS webhooks are used for order change notifications to reduce latency, supplementing polling for other data.

VismaAmazon Seller Central

Visma and Amazon Seller Central integration

Visma.net ERP runs your accounting and financial management. Amazon Seller Central manages your merchant operations and order fulfillment. Connecting the two keeps your customer invoices and settlement accounts in agreement with your Amazon sales. New orders placed on Amazon flow into Visma as customer invoices, and Amazon's financial settlement events post into your general ledger without manual re-entry. ml-connector bridges the very different OAuth 2.0 flows and the Restricted Data Token requirement that Amazon enforces.

How Visma works

Visma.net ERP is a cloud-based accounting and financial management platform covering financial management, AP/AR, purchasing, inventory, and project accounting. It exposes suppliers, supplier invoices, purchase orders, customers, customer invoices, accounts, and journal transactions through REST APIs over HTTPS, documented in the Visma API reference. Authentication uses OAuth 2.0 client credentials through Visma Connect with a client_id, client_secret, and tenant_id, and all API calls require an ipp-company-id header. Visma supports both webhooks with one-time delivery and polling via the lastModifiedDateTime query parameter on list endpoints to detect changes. Webhook enablement is required at the company level and events must be explicitly enabled on each entity.

How Amazon Seller Central works

Amazon Seller Central exposes orders, order items, financial events, financial event groups, shipment events, refund events, service fee events, and adjustment events through the Selling Partner API, a REST service available across North America, Europe, and Far East regions. Authentication uses OAuth 2.0 with a refresh_token grant for seller-authorized operations and client_credentials grant for grantless operations; access tokens expire after one hour. Amazon does not offer direct HTTP webhooks; instead, it sends push notifications through Amazon EventBridge or Amazon SQS for order changes and inventory updates, while financial settlement events must be polled. Orders older than two years are not returned. Restricted data operations such as buyer address and phone require a separate Restricted Data Token obtained from the Tokens API.

What moves between them

The main flow is from Amazon Seller Central into Visma.net ERP. When orders are placed and shipped on Amazon, ml-connector reads the order and shipment events and posts customer invoices into Visma, mapped to the correct customer account and revenue account. After each seller settlement on Amazon, ml-connector polls the financial events and posts adjustment, refund, service fee, and settlement entries into Visma's general ledger, allocated to the accounts designated for e-commerce revenue and adjustments. Reference data such as Amazon order source codes and fulfillment channels are cached to tag Visma invoices and journal lines consistently. Visma can also push order returns and credit notes back to Amazon, though the primary flow is inbound from Amazon to Visma.

How ml-connector handles it

ml-connector stores both credential sets encrypted and manages the OAuth 2.0 token refresh for both platforms separately. On the Amazon side, it obtains a Restricted Data Token (RDT) when buyer address, phone, or payment method data is needed, respecting Amazon's data residency and PII constraints. Visma requires the ipp-company-id header on every call and the tenant_id in the token request, both stored per customer. Because Amazon's financial events are not available via push, ml-connector polls the Finances API on a schedule tied to your settlement cadence, typically daily, and deduplicates entries using the financial event group and event ID. Visma webhooks, if enabled, supplement polling for order-placed events to reduce latency. On failure, records carry the full audit trail and can be replayed. ml-connector maps Amazon's fee structures and refund reasons to the Visma journal transaction templates your finance team has defined.

A real-world example

A small to mid-size e-commerce seller operates an online store on Amazon across North America and Europe, using Visma.net ERP to manage accounting and financial reporting. Before the integration, the seller's finance team downloaded Amazon settlement reports manually each week, mapped order totals to customer invoices, and posted refunds and fee adjustments into Visma by hand. Month-end reconciliation took days because Amazon order counts and settlement totals had to be manually cross-checked against the invoices in Visma. With Visma and Amazon Seller Central connected, each order automatically posts as a customer invoice when it ships, and settlement events flow into the general ledger on the day they post to the seller's bank account. Reconciliation is immediate and the manual data entry is gone.

What you can do

Sync orders from Amazon Seller Central into Visma.net ERP as customer invoices, mapped to the correct customer and revenue account.
Post Amazon financial settlement events, refunds, and service fees into Visma journal transactions and accounts automatically after each settlement period.
Handle Amazon's Restricted Data Token flow to access buyer address and payment method data where required by your integration rules.
Manage OAuth 2.0 token refresh for both Visma and Amazon, and poll Amazon's Finances API on a schedule tied to your settlement calendar.
Maintain a full audit trail on every order and financial event, with error replay and reconciliation support.

Questions

Which direction does data move between Visma.net ERP and Amazon Seller Central?: The main flow is from Amazon into Visma. Orders and shipments flow into Visma as customer invoices, and Amazon financial settlement events post into Visma journal transactions and accounts. Visma can also push order returns and credit notes back to Amazon, though this is less common. The integration is designed to keep Visma's customer invoices and settlement accounts in agreement with Amazon's order and financial records.
What is the Restricted Data Token and why does Amazon require it?: Amazon restricts direct access to buyer addresses, phone numbers, and payment methods for privacy and compliance. When your integration needs this data, ml-connector calls the Amazon Tokens API to obtain a Restricted Data Token (RDT) for that specific request, keeping PII data access audited and time-limited. The RDT expires in one hour, so ml-connector refreshes it only when needed.
How does the integration handle Amazon's lack of webhooks for financial events?: Amazon does not push financial settlement events; they must be polled. ml-connector polls the Amazon Finances API on a daily schedule or on a cadence tied to your settlement calendar, and deduplicates entries using the financial event group ID and event ID. EventBridge or SQS webhooks are used for order change notifications to reduce latency, supplementing polling for other data.

Connect Visma and Amazon Seller Central

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started