Practical guide to Wiise ERP upgrades, Business Central wave updates, Australian localisation management, and growth planning for SMBs.
Business owners, finance managers, and IT managers running Wiise who are dealing with upgrades, growth constraints, or customisation needs.
How do we manage Wiise updates, handle customisations, and plan for growth beyond Wiise?
Wiise is an Australian-focused cloud ERP built on Microsoft Dynamics 365 Business Central. Developed by KPMG Australia and Microsoft, it's designed for small-to-mid-market Australian businesses that want the power of Business Central with local features baked in.
The Australian-specific features are the selling point: Single Touch Payroll, BAS reporting, Australian chart of accounts templates, local bank feeds, and AU-formatted reports. It saves the configuration work that vanilla Business Central requires for Australian compliance.
Because it's built on Business Central, Wiise inherits everything BC offers — including its update cycle, customisation model, and integration architecture. That's mostly a good thing, but it means you're in Microsoft's cloud update ecosystem whether you like it or not.
Dual update cycles. Wiise users have two update streams: Microsoft's Business Central wave updates (twice yearly plus monthly) and Wiise-specific feature updates (on Wiise's schedule). Both can introduce changes that affect your environment.
Growth constraints. Wiise targets SMBs with straightforward requirements. As businesses grow, they commonly hit limits around multi-entity structures, complex manufacturing, advanced warehousing, and high-volume transaction processing.
Support layers. With Wiise, support comes through Wiise (for Wiise-specific features), Microsoft (for Business Central platform issues), and potentially your implementation partner. Navigating multiple support channels can be frustrating.
Australian compliance changes. STP updates, BAS changes, and superannuation requirements change regularly. Wiise generally handles these well, but timing of compliance updates relative to ATO deadlines can be tight.
Stay on Wiise and extend. If the core ERP functions work, build around it. Custom web applications, integrations, and automation can address many limitations without changing your ERP. This is often the most cost-effective path for growing businesses.
Move to full Business Central. If Wiise-specific features are limiting you or you need a broader partner ecosystem, moving to standard Business Central is straightforward. It's a licencing and configuration change, not a platform migration.
Move to Dynamics 365 Finance & Operations. If you've genuinely outgrown Business Central's capabilities (complex manufacturing, multi-country operations, advanced supply chain), D365 F&O is the step up. This is a platform migration.
Move to an alternative ERP. NetSuite, SAP Business One, or industry-specific ERPs may fit better depending on your requirements. Less common from Wiise but worth evaluating if the Microsoft ecosystem isn't working.
AL extension model. Wiise customisation uses the same AL extension model as Business Central. You can add custom fields, pages, reports, and logic. But AL development requires specialist skills — this isn't Power Platform territory.
AppSource extensions. The Business Central AppSource marketplace has extensions for many common needs. Check here before building custom — it's often cheaper to buy than build.
Integration options. Wiise/Business Central supports:
Common integrations. Australian Wiise users typically integrate with: Xero or MYOB (for practices switching mid-stream), e-commerce platforms (Shopify, WooCommerce), CRM systems, POS systems, and warehouse/logistics providers.
If you're approaching Wiise's limits, plan the next step before you're forced to move in a rush.
Third-party AppSource extensions need version compatibility with every BC update.
Power Automate flows are easy to create and hard to manage at scale.
Three support layers (Wiise, Microsoft, partner) can create confusion during incidents.
Partly. Wiise runs on Microsoft Dynamics 365 Business Central but includes Australian-specific features — Single Touch Payroll, BAS reporting, Australian chart of accounts, and local bank feeds. Think of it as Business Central pre-configured for Australian SMBs.
Yes. Because Wiise runs on Business Central, it receives Microsoft's wave updates. Wiise-specific features are updated by the Wiise team on their own schedule. This means you're managing two update cycles, not one.
Absolutely. Wiise targets small-to-mid businesses. If you're hitting 50+ users, need complex manufacturing, advanced warehousing, or multi-entity structures, you may be outgrowing what Wiise handles well. At that point, full Business Central or Dynamics 365 F&O may be more appropriate.
Wiise customisation uses the same AL extension model as Business Central. We provide a fixed-price quote after scoping — simple customisations sit at the lower end of project size, complex ones are larger.
Yes, and it's relatively straightforward because Wiise IS Business Central underneath. The main work is replacing Wiise-specific features with standard BC equivalents or Business Central licencing. It's not a platform migration — it's a licencing and configuration change.
Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.
