Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
What was sold and what arrived in the bank are two different figures, so Shopify orders and the payout behind them reach AFAS separately rather than as a single net figure for somebody to unpick.
A Shopify shop takes a hundred euros and receives rather less, because the provider deducts its fee before the money moves. AFAS posts through ledger accounts that expect revenue, cost and cash to be distinguishable, so a single net deposit forces somebody to work backwards from a settlement report each month and journal the difference by hand. It is an hour that never gets shorter and a figure nobody can explain at a moment's notice. Connecting Shopify and AFAS separates the parts on the way through, so revenue, the cost of taking it, and the cash are each posted where they belong.
DATA THAT FLOWS BETWEEN THEM
Orders
Order lines
Payments
Provider fees
Payouts
Customers
A Shopify sale, the provider's fee and the money that actually arrived post to separate AFAS accounts, so the cost of taking payment is visible rather than buried in a net figure.
Because the split happens as the payout settles, nobody in finance rebuilds it from a settlement report, and the hour that took each month is returned to the team.
What the provider deposited and what AFAS expects are reconciled as the payout arrives, so the statement is checked rather than investigated at the end of every period.
A Shopify refund posts against the original sale in AFAS rather than as a fresh cost, so the revenue figure moves and the picture of what the shop earned stays true.
When a Shopify order is paid, Alumio posts the sale, the provider's fee and the net amount to the AFAS accounts you nominate for each, so the ledger carries three facts rather than one figure somebody has to take apart later.
When the payout settles, Alumio matches it against the Shopify orders it covers and posts the deposit in AFAS, so the amount arriving in the bank ties back to specific sales instead of landing as a lump sum nobody can attribute.
A returning Shopify shopper is matched to the AFAS record they already have, so repeat business builds one relationship in the ledger rather than a near-duplicate each time somebody spells their address differently.
Alumio sits between sales channels and fulfillment systems as a governed integration backbone. Orders are routed, transformed, and validated, while status updates return to every channel.
Authenticate your systems using Alumio's pre-built connectors. Choose from 200+ connector packages in the marketplace, plus unlimited custom integrations.
Define how data fields map between systems in a visual interface. Adjust formats, enrich records, and apply business logic, no custom code required.
Configure flows to run in real time on events, on a schedule, or both. Reduce manual data entry and let Alumio handle movement and transformation between systems.
.svg){kind=icon}
Once your first integration is live, adding your ERP, PIM, WMS, or CRM connects to the same hub. Existing flows keep running. No rebuilding from scratch.
Start with whatever is still being keyed in on a Friday, and for most shops that is the settlement side of a second payment method. AFAS is the ledger and Shopify is the shop, and the provider sitting between them has its own view of what was taken and what was deducted. Alumio holds that connection alongside this one, so the reconciliation covers every way the business gets paid.
It can, and they travel as two flows rather than one. A paid Shopify order posts as the sale and the fee as it happens, so revenue is recognised on the day it was earned, while the payout posts separately when the money moves. Keeping them apart is what lets AFAS show both what the shop sold and what the bank received, without either one being inferred from the other. Posting the sale, the fee and the deposit stays within what AFAS accepts.
No, this is configured rather than coded. The weekly batch somebody keys in is what goes, along with the settlement report they work from. Which Shopify amount posts to which AFAS account, and how a payout is matched to the sales it covers, are entries in Alumio. Where a Dutch reporting requirement needs a value derived rather than read, the Code Transformer takes that step.
In the cost account you nominate, and not inside the revenue line, which is the decision worth making before the first order posts. AFAS reports from the accounts it was given, so a Shopify fee deducted before the money moved simply becomes less revenue unless it is posted on its own. Separating it is what turns the cost of taking payment into something the business can look at and decide about.
A settlement that matched nothing is the failure worth catching, because the money is in the bank and the ledger has no home for it. Alumio watches each posting live and records the Shopify payout reference with the AFAS entry it produced, so an amount that cannot be matched raises an alert naming both and the reason. Retries run where configured, so nothing is left unreconciled.
Talk to an Alumio integration specialist. We'll map the right architecture for your systems, at the right scale, so your operations stay reliable through every change.
.svg)
