Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
Square takings, fees and refunds post into Microsoft Dynamics 365 Business Central per location, so each individual store's day reconciles against the bank deposit that it actually generated.
Every Square location produces a day of sales, a card settlement that arrives net of fees, and a deposit that rarely matches either. Business Central needs postable entries per store, and without a connection somebody keys in totals from the Square dashboard, posts fees as a lump sum, and cannot explain why store three is out by a few euros. Multi-site retail makes that worse every time a location is added. Connecting Square and Microsoft Dynamics 365 Business Central through Alumio settles it per location: takings post by payment type, fees are separated, and refunds reverse against the sale.
DATA THAT FLOWS BETWEEN THEM
Location takings
Payment types
Processing fees
Refunds
Settlements
Item sales
Customer records
Takings post to Business Central per Square location, so a discrepancy is traced to one store's day rather than hunted across a combined figure for the whole estate.
Processing fees post to their own account instead of being netted into takings, so the real cost of card acceptance per location stays visible on the profit and loss.
Settlements are matched to the sales they cover, so the bank deposit ties to posted entries without somebody reconstructing the link from two separate dashboards.
Adding a Square location is a configuration step rather than another daily entry task, so growing the estate does not grow the finance team's workload alongside it.
When a Square location closes its day, Alumio posts the takings to Business Central split by payment type and coded to that store, so the accounts show each site's trading without anyone entering totals from a dashboard.
A Square settlement is matched to the sales it covers with the fee posted separately, so the deposit reconciles exactly and finance can explain the difference between gross takings and cash received on any given day.
A refund processed in Square creates the reversing Business Central entry against the original sale and location, so the store's figures and the customer record agree without a manual journal to bridge the difference later.
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.
More can be connected, and inventory or an e-commerce channel is the usual addition, because Square records the sale while stock for the same products may be committed online too. Alumio connects them, so a store sale reduces the availability the webshop is willing to offer instead of the two channels selling the same unit twice.
Yes. Alumio reads takings, payment types, fees, refunds and settlements from Square and posts them into Business Central coded to the matching location, as days close or as settlements arrive. Payment types stay separated through the flow, which is what makes the resulting entries reconcilable against the bank rather than merely correct in total.
Location mapping, account coding, fee posting and settlement matching are all set up in the Alumio interface, which takes the place of the manual daily entry retailers usually rely on. Adding a store becomes configuration rather than another task. Should a tipping, surcharge or multi-currency rule need handling of its own, the Code Transformer covers it.
As many as the business runs, provided each one maps to something Business Central can report on, which is the part worth designing up front. Locations usually map to dimensions rather than separate companies, so a single company can carry the whole estate while still reporting per site. Alumio applies that coding as entries are posted, so the structure holds as locations are added.
No store's takings post twice, and none get skipped. Alumio records each message with its content, monitors both links in real time, and notifies finance immediately when Business Central refuses an entry, naming the location, the date and the cause. Unattended retries clear transient posting locks, and an unposted day sits in the exception queue instead of vanishing.
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)
