HELLO PEOPLE is an Australian Business Central integration company. We connect Microsoft Dynamics 365 Business Central to your online store, customer relationship management (CRM) system, payment providers, payroll and project tools, with posting groups and dimensions handled properly.
Get those two wrong once and the mistake repeats on every transaction, so we map them with your finance team before we quote a fixed price. Built and tested in a sandbox first.
Built here. Your data stays here.
Online stores, sales systems, payment providers, rostering, reporting and spend tools that businesses ask us to connect to Business Central. Click one to see its page.
The problem
Business Central is strict about where things land. Posting groups decide the accounts, dimensions decide how it reports. An integration that ignores either still posts entries that balance, and nobody notices until the monthly report makes no sense and somebody has to reconcile back to the source.
What you already run
Built on the Business Central API, its published connection point for other software, with every record mapped to your posting groups and dimensions. A record that cannot be placed correctly is held for a person instead of posted to a default.
Get a fixed-price scopeWhat changes
Five kinds of custom Business Central integration. Each one is mapped to your posting groups and dimensions before it is built.
Web orders arrive in Business Central as sales documents against the right customer and item, and stock levels flow back to the store so it never sells what the warehouse does not have.
Each order line lands through the posting groups you chose. A wrong posting group repeats its mistake on every order until somebody notices, so they are set and tested before go-live.
Won deals become customers and orders in Business Central, and invoice and payment status flows back to the sales team so they stop asking accounts whether a customer has paid.
The same customer has to be the same customer on both sides. Trading names and near duplicates are matched carefully, because a careless match does real damage.
In Business Central, payments post through bank accounts and posting groups. Payouts from Stripe, Square, Tyro and others are split back into the payments inside them and posted where your finance team expects.
Each provider settles differently, so each pairing has its own page.
Construction, trade and professional services businesses often run the work in one system and the finance in Business Central. Hours, materials and progress claims are carried into Business Central projects with the right dimensions attached.
Dimensions are the point here. Without them the entries still balance, but the project report tells you nothing.
Some rules belong inside Business Central itself: a custom posting rule, an approval step, an extra field. Those are built as AL extensions, AL being the language Business Central is extended in.
Reporting is built in Power BI on Business Central data, so finance and operations read from one set of numbers.
Your companies, posting groups, dimensions and licence come first. Then a fixed price covering build, sandbox testing and go-live.
Which companies, which posting groups and dimensions, and what licence you hold. These decide what the integration can reach and what it must get right.
Build, sandbox testing and go-live, all in one price. If the scope changes, we re-quote rather than let it drift.
Business Central updates itself on a schedule you can only delay a little. A support plan covers checking the integration after each one.
Why HELLO PEOPLE
For simple flows, Power Automate or an existing connector may be enough, and we will say so. The difference shows in posting groups, dimensions and what happens after each Microsoft update.
| Concern | HELLO PEOPLE | Zapier / Make | n8n / self-hosted | MuleSoft / Boomi |
|---|---|---|---|---|
| Posting groups | Set and tested before go-live | Whatever the default maps to | You work them out | Configured by a partner |
| Dimensions on every entry | Required, or the record is held | Often dropped | You add them | Configurable, needs specialists |
| Rules that belong inside Business Central | Built as AL extensions | Not possible | Not possible | Partner project |
| Microsoft updates | Checked in a sandbox after each one | Found out when it breaks | Your job | Covered by support contract |
| Ongoing cost | One-off build plus optional support | Charged per task, every month | Hosting and upkeep are yours | Enterprise licence |
| Who you talk to | The person who built it | Chat support | Community forum | Enterprise support desk |
An Australian business running on five disconnected platforms, accounting, CRM, field-service, eCommerce, and reporting, was spending hours each day re-keying the same data. We connected the systems through their APIs so contacts, invoices, orders and payments flow automatically. Errors are visible and recoverable.
Read the full case studySix steps. The second one, mapping posting groups and dimensions with your finance team, is where most of the risk is removed.
Dynamics 365 covers several different applications. We confirm you run Business Central, which companies are involved, and what your licence lets outside software reach.
Every record the integration writes is mapped to the posting groups and dimensions your finance team uses, and checked with them.
Access is granted through an app registered in Microsoft Entra ID, the Microsoft sign-in service. You own the registration and can switch it off at any time.
Everything is built and tested in a Business Central sandbox, a separate copy for testing, before it touches your live company.
Switched on from an agreed date, with the first period checked by your finance team against what they expected.
Business Central updates roll out automatically. The integration is rechecked in the sandbox after each one, before your live company takes it.
Today
After
Scoped and quoted before you commit. You own the code and the Entra ID registration.
Get a fixed-price scopeThrough an app registered in Microsoft Entra ID, which is the Microsoft sign-in service. Business Central offers an API, the published connection point other software uses, and the registration controls what an integration may do with it. Your licence also affects what can be reached, so we check both first. Our Dynamics 365 API guide covers it in more detail.
Your posting groups and dimensions. They decide where every entry lands and how it reports. A Business Central integration consultant who skips them builds something that balances but produces reports nobody can use.
HELLO PEOPLE is an independent integration company. We build the connections between Business Central and the rest of your software, and we work alongside your Microsoft partner if you have one.
Power Automate is the Microsoft tool for simple flows, and where it covers the job we will say so. A Business Central integration developer is worth it when records need checking, matching or holding for a person, when volume is high, or when a rule belongs inside Business Central as an AL extension.
A fixed price against a written scope, set once we know the companies, posting groups, dimensions and systems involved. One store into one company is a smaller job than several channels into a multi-company setup.
They can, which is why we plan for them. Business Central updates roll out automatically with only a short delay allowed. Under a support plan, the integration is rechecked in a sandbox after each update.
Before go-live. Every system that connected to the old ledger needs rebuilding for Business Central, and doing it during the migration avoids a gap. See our MYOB to Business Central and Xero to Business Central pages.
Sending your details…
You can stay on this page while we send it.
How many companies you run, which systems need connecting, and where finance still re-keys or reconciles by hand. We will come back with a plan and a fixed price.
Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.
Thanks for reaching out. We will get back to you within one business day.
See what else we do