# Auboros: full blog content > Auboros is Brisbane's ERP & AI agency. Odoo Silver Partner and MYOB Acumatica Partner delivering ERP implementation, integration, custom development and AI automation across Australia & New Zealand. Canonical site: https://www.auboros.com. Each section below is one blog post; the canonical URL is given per post. --- # The AI Lead Qualification Agent: How It Works in Odoo and MYOB Acumatica - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-lead-qualification-agent-erp-australia - Category: AI & ERP - Published: 2026-08-21 - Description: What an AI lead qualification agent reads from your CRM and ERP, the scores and first replies it drafts, and why a rep approves every send in Australia. An AI lead qualification agent reads each new enquiry, checks it against your CRM and ERP history, scores it against criteria you wrote down, and drafts the first reply. Then it stops and waits for a salesperson to approve. That last part is the whole design, and it's the part most vendor demos skip. With [12% of Australian businesses now using AI](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25), and 22% of medium-sized ones per the ABS, sales teams are a common starting point, because lead handling is repetitive, time-sensitive and mostly reading. We've already covered how [calls and meetings become CRM records](/blog/ai-erp-australia-8/ai-crm-call-logging-agent-erp-australia) and how [emailed purchase orders become draft sales orders](/blog/ai-erp-australia-8/ai-sales-order-agent-erp-australia). This post is about the step before both: deciding which of this morning's enquiries deserve a salesperson's attention, and in what order. ## What an AI lead qualification agent actually does The agent has four jobs, and none of them involves sending anything. - **Read.** The web form, the email thread, the trade show list, the missed-call transcript. It pulls out who's asking, what they're asking for, and how urgent they sound. - **Check your own records first.** Before it looks anywhere else, it queries your CRM and ERP. Is this an existing customer? What have they bought? Are they on credit hold? Half of qualification is history you already own, sitting in systems your reps don't have time to cross-reference at 7am. - **Score against explicit criteria.** Your rules, written down: industry, region, order size signals, product fit. Not a vibe. If you can't explain why a lead scored 80, the score is noise. - **Draft.** A first-touch reply in your voice, a routing recommendation, and a one-paragraph note on why. All of it lands in a queue. Then a person opens the queue, approves, edits or bins. The agent proposes. The rep decides. That split matters more here than almost anywhere else, because the thing being handled is a stranger's first impression of your business. ## Scoring already shipped. Qualification is the judgement layer If you run Odoo, part of this already exists and has for years. [Predictive lead scoring](https://www.odoo.com/documentation/19.0/applications/sales/crm/track_leads/lead_scoring.html) is always active in Odoo CRM: a statistical model that learns from your historical won and lost opportunities and assigns each new lead a probability of success. It's useful, it's free with CRM, and you should switch on the optional variables that fit your pipeline. But it's statistics, not judgement. Predictive scoring won't read the enquiry, won't notice the sender is an existing debtor sixty days overdue, and won't draft a reply. It ranks what's in the pipeline based on what fields the record carries. An agent sits on top of that layer and does the reading. The two stack well: the model supplies a probability, the agent supplies the context and the draft, and a person supplies the decision. ## What's shipped today in Odoo and MYOB Acumatica Here's the current state, labelled honestly. **Odoo 19, shipped.** We verified this in the v19 Enterprise source code. Odoo ships an AI lead-creation topic for its agents: the website or livechat assistant can collect a visitor's name, email and phone, confirm the details, and create a CRM lead, with strict instructions to do it exactly once and never to promise follow-up until the record actually exists. That's inbound capture with sensible guardrails, live today. Odoo's documentation also confirms [agents act within the signed-in user's access rights](https://www.odoo.com/documentation/19.0/applications/productivity/ai/agents.html), which is the permission model you want. What Odoo doesn't ship yet is the outbound half: scoring against your written criteria and drafting replies is wiring you add through its agent tools or an external agent over the API. **MYOB Acumatica, preview.** The CRM handles lead records, assignment rules and pipeline today, all deterministic. The AI layer, [AI Studio, is in technology preview in the 25 R2 release](https://www.myob.com/au/press-releases/myob-acumatica-launches-new-ai-studio-in-collaboration-with-aws), built with AWS and Anthropic with data processed in local data centres. In the preview, agents run when a user asks and can't create records on their own. General availability is planned for 26 R1 with no committed ANZ date, and globally, Acumatica's 2026 R1 shipped its [AI Assistant under managed availability](https://community.acumatica.com/acumatica-news-updates-2/acumatica-ai-assistant-2026-r1-managed-availability-and-faq-34846) in March 2026. Global features typically reach the ANZ product 6 to 9 months later. **The fair comparison.** Microsoft is ahead of both here. The [Sales Qualification Agent in Dynamics 365](https://learn.microsoft.com/en-us/dynamics365/sales/sales-qualification-agent) reached general availability in October 2025 and runs in two modes: research-only, and research-and-engage, where the agent contacts prospects itself. It's a capable product. We'd still tell you to run the first mode and not the second, for reasons the next two sections cover. ## A Monday morning, worked through This is the pattern as we'd build it for a Queensland wholesaler, drawn from what actual prospects keep asking us for. Twenty-two leads arrived over the weekend: web forms, a trade show spreadsheet, four plain emails. By 7:30am the agent has matched six to existing accounts in the ERP. Two are current customers asking about a product they already buy, so it flags them for the account manager rather than the new-business queue. One is a customer on credit hold, flagged with a note to sort the account before anyone quotes them something new. The rest get scored against the written criteria, and eleven get a drafted reply. One enquiry the agent can't confidently read, so it escalates with "a human should look at this" instead of guessing. At 8am a rep opens the queue with coffee. Nine drafts approved as-is, two rewritten because the tone missed, one binned because the agent scored a student research project far too generously. Nothing was sent before a person hit approve, and the rep's whole part took less time than the first two leads would once have. > "The agent is good at the reading and the arithmetic, and it never gets bored on lead eleven. What it doesn't own is your reputation. The moment drafts start sending themselves, you've handed a stranger's first impression of your business to a system that can't be embarrassed." > > **Josh Craig, Director, Auboros** ## The Australian rules your first-touch drafts have to follow This is where the approval gate stops being a preference and becomes protection. Commercial emails and SMS in Australia sit under the Spam Act, and the [ACMA's rules](https://www.acma.gov.au/avoid-sending-spam) are specific: you need consent, express or reasonably inferred, you must identify your business, and every message needs an unsubscribe that works, actioned within five business days. Someone who emailed you asking about a product has plainly invited a reply. A trade show list from two years ago is a different story, and it's exactly the kind of list an over-eager automation will happily work through. The ACMA is also [clear that you can't outsource the obligation](https://www.acma.gov.au/telemarketing-and-e-marketing-common-issues-and-mistakes): if your agent sends it, your business sent it. Privacy runs alongside. A lead's name, email and behaviour are personal information under the [Australian Privacy Principles](https://www.oaic.gov.au/privacy/australian-privacy-principles), and that doesn't change because an agent did the collecting or the enriching. We covered the broader control set, permissions, audit trails and the December 2026 disclosure deadline, in our guide to [AI agent governance](/blog/ai-erp-australia-8/ai-agent-governance-australia). ## Failure modes worth designing for We run agents over our own operations, drafts-first, and the failure modes are predictable enough to plan around. Research errors are the big one: two businesses share a name, and the agent confidently attributes the wrong size and industry to your prospect. That's why the draft carries its reasoning, so a rep can see the error before it shapes a reply. Score inflation is the quiet one: agents reward enthusiasm rather than fit, and a keen student can outscore a terse procurement manager. Written criteria and a monthly look at what the agent got wrong keep the scores honest. Language models make mistakes. The design assumes it, which is why nothing sends itself. ## Where to start Start read-only. Two weeks of the agent scoring and drafting into a queue nobody sends from, while your reps work normally. Compare its calls with theirs. If it earns trust, switch on approved sends. If a vendor suggests skipping straight to autonomous outreach, ask them who answers to the [ACMA](https://www.acma.gov.au/avoid-sending-spam) when it goes wrong, because it won't be them. Odoo users should also look at what [Odoo CRM already does out of the box](/blog/odoo-erp-australia-6/odoo-crm-australia-features-guide-104) before adding an agent to it, and our [AI agent services](/solutions/ai-agents) page covers how we scope this pattern, drafts-first, with role-scoped permissions. --- **Thinking about pointing an AI agent at your lead queue?** Auboros builds drafts-first qualification agents over Odoo and MYOB Acumatica from Brisbane, with the scoring criteria written down and a rep approving every send. If you'd like to see what the pattern looks like on your pipeline, [**book a free consultation**](/appointment). We'll tell you honestly whether your lead volume justifies it. --- # Odoo Price Increase 2026: Has Australia Been Hit Yet? (AUD Numbers) - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-price-increase-australia - Category: Odoo ERP Australia - Published: 2026-08-21 - Description: Odoo raised US Custom pricing 30% in Jan 2026. Australia is still A$65/user, but the 25% legacy fee and 7% clause already apply. What to check before renewing. If you run Odoo in Australia, you have probably heard that prices are going up. Some of that talk is accurate, some is a year late, and some is guesswork dressed up as news. Here is what has actually happened, what the rumours circulating in the Odoo community are based on, what is already written into your subscription agreement, and what a US-style increase would look like in Australian dollars if it arrives. Figures below are the Australian pricelist as at 22 August 2026, per user per month, excluding GST. We wrote this because the questions we're getting from clients are the same three: has the price gone up, will it, and what do I do about it. We'll take them in that order. ## What Odoo did in the US in January 2026 On 5 January 2026 Odoo raised the list price of its Custom plan in the United States and Canada from US$46.80 to US$61.00 per user per month on yearly billing, a rise of about 30%. The first-year promotional price moved from US$37.40 to US$49.00. The Standard plan was left alone. Customers heard about it from their account managers by email in the last week of November, roughly five weeks before it took effect, and [the reaction on r/Odoo](https://old.reddit.com/r/Odoo/comments/1p83mf6/) was about what you'd expect from businesses that had migrated a year earlier on the old numbers. Two details from that rollout matter for Australia. First, Odoo did not announce it publicly; there was no press release or blog post, only account manager emails and a changed pricing page. Second, Odoo later told partners the increase had [no measurable effect on conversion rates](https://muchconsulting.com/blog/odoo-2/odoo-news-april-2026-154) and improved its mid-market positioning. A vendor that raises prices 30% and loses no customers has learned something, and it would be naive to assume the lesson stays in North America. ## Has Odoo raised prices in Australia? No. As of August 2026 the Australian pricelist on [odoo.com/pricing](https://www.odoo.com/pricing) is unchanged from what partners were publishing in late 2023: - **Standard, yearly billing:** A$34.40 per user per month for the first 12 months, then A$43.00. - **Custom, yearly billing:** A$52.00 per user per month for the first 12 months, then A$65.00. - **Monthly billing:** A$43.20 then A$54.00 for Standard, A$64.80 then A$81.00 for Custom. All figures exclude GST and hosting on Odoo.sh. The number most people miss is the second one in each pair. The price you see advertised is a 12-month discount on the users you order at signing, and Odoo's own pricing page footnote says so. From month 13 you pay list, which is 25% more. That is not an increase; it is the price you agreed to. It just doesn't feel that way when the renewal invoice lands. Nothing has been announced for Australia, and the last Australian pricelist change was in 2022. What has changed is the conversation around it, which is the next section. ## Why the rumours of an Australian increase are not idle Four reasons, in rising order of weight. The exchange rate has done Odoo no favours. After the January rise, an American Custom user pays US$61. An Australian Custom user pays A$65, which at current rates is about US$42 to US$44. Before January, Australian pricing sat at roughly 1.39 times the US figure in nominal terms; it now sits at about 1.07. The same software is 30% cheaper here than in the US, and vendors notice gaps like that. Odoo has invested in Australia and says so. It [opened its first Australian office on the Gold Coast](https://www.wallonia.com.au/en/news/odoo-opens-its-first-australian-office-gold-coast-leading-new-era-smes) in 2023 and has since put real work into the Australian localisation. The commercial logic of "we've invested, the market is growing, prices follow" is not hidden. Europe is openly expecting to be next. Since the US change, European partners have been [predicting a price rise for their region](https://www.linkedin.com/in/simon-stappen/en/) in 2026 or 2027, pointing to the US precedent, the new contract wording on renewals, and the pattern of Odoo's past pricing cycles. If Europe moves, it is hard to see Australia being left on a 2022 pricelist. And the Odoo 20 code now contains a new, lower-access user tier. A cheaper seat is what vendors tend to introduce just before the full seat gets dearer, because it softens the headline for businesses with a lot of light-touch staff. More on that below, with the caveat that nothing about its price has been announced. > "Nothing is scheduled for Australia, and we'll tell clients the moment something is. But the US has moved, Europe expects to, and a new user tier is sitting in the Odoo 20 code. That's a pattern, not a rumour." > > **Josh Craig, Director, Auboros** ## Why does the pricing page look like it went up 25%? (the monthly toggle) A steady stream of people arrive at Odoo's pricing page, flick the billing toggle, see A$65 with A$81 struck through, and conclude the price has just jumped. It hasn't. A$81 is the monthly-billing list price for Custom and A$64.80 is the monthly first-year price; on yearly billing the pair is A$52 and A$65. The same confusion played out in the US in January, where the "new price" of US$76.20 circulating on Reddit was the monthly figure and the yearly list was US$61. Before you react to a number, check which toggle you're on. ## Is the 7% cap per year or per renewal? Per year of the term just ended, since December 2025. Before that the agreement allowed a single increase of up to 7% at each renewal, however long the term. That is why advice from early 2025 ("it'll take eight years to reach a 30% increase") is now wrong for anyone on a multi-year term: three years in, the allowable step is 21%, not 7%. For a one-year term the two readings give the same answer, 7%. A question that comes up repeatedly in the community is whether the cap applies to one-year contracts at all; on the wording of the clause, a one-year subscription has a Term, and the cap applies to it. ## The costs already in your Odoo contract Before any list price changes, the [Odoo Enterprise Subscription Agreement](https://www.odoo.com/documentation/19.0/legal/terms/enterprise.html) already contains four mechanisms that move your renewal price. Most Australian customers have never read them. **The promotional cliff.** Covered above: 25% at month 13, on the users you started with. Users added during the year are charged at the list price of the day. **The 7% per year renewal clause.** Clause 5.2 says that if your current charges are below the list price at renewal, Odoo may increase them by up to 7% for each year of the term just ended. That wording changed in December 2025. It used to be a flat 7% per renewal. Under the new wording a three-year contract can step up 21% at the end of it, because three years have passed. Customers comparing renewal options have reported the yearly plan being illustrated with a 7% rise every single year, which tells you how the clause is expected to be applied. **The 25% legacy version surcharge.** Clause 5.1 lets Odoo charge an extra 25% of your annual price, once a year, if your database is running a version older than the three most recent major releases. It applies no earlier than six months after a new major version ships. Odoo 19 arrived in September 2025, so from April 2026 anyone still on version 16 or older has been liable. When Odoo 20 ships after the September keynote, version 17 drops out of the covered window and becomes liable from around April 2027. Our guide to [Odoo version support in Australia](/blog/odoo-erp-australia-6/odoo-version-support-australia) covers the timing in detail. **The monthly billing premium.** Monthly plans cost about 25% more than yearly, and reducing users on a monthly plan now requires 30 days' notice, which caught out [at least one business that tried to trim users](https://old.reddit.com/r/Odoo/comments/1qv2gcy/) straight after the US increase. Stack them and the picture for an unlucky customer looks like this. A business that signed a three-year Custom contract in 2023 at A$52, stayed on version 16, and renews this year can face the move to A$65 list, a further rise of up to 21% under clause 5.2, and a 25% surcharge on top of that, before Odoo touches the Australian pricelist at all. ## What a US-style increase would look like in Australian dollars This is a model, not a leak. Odoo has not announced an Australian increase. But if Odoo repeated the US playbook here, a 30% rise on the Custom plan only, the Australian list would land at roughly A$85 per user per month on yearly billing and about A$105 on monthly billing, with the first-year price at about A$68. Restoring the pre-January ratio between Australian and US pricing produces almost exactly the same number. What that means in annual licence cost on the Custom plan at list price, yearly billing: - **10 users:** A$7,800 today, about A$10,140 after a 30% rise, A$2,340 more per year. - **20 users:** A$15,600 today, about A$20,280 after, A$4,680 more. - **50 users:** A$39,000 today, about A$50,700 after, A$11,700 more. - **100 users:** A$78,000 today, about A$101,400 after, A$23,400 more. Add the 7% ladder over the following two renewals and the three-year cost for 50 users moves from about A$125,000 to about A$163,000. A 50-user business still on version 16 pays another A$10,000 to A$12,700 a year in surcharge until it upgrades. None of this includes implementation, which as our [Odoo pricing guide for Australia](/blog/odoo-erp-australia-6/odoo-pricing-australia) explains is usually the larger number anyway. ## Who is protected and who isn't If you are mid-term, your price is fixed until the end of the term. The agreement is explicit that pricing is set in writing at signing, and a list change doesn't reach you until renewal. At renewal, clause 5.2 caps the increase at 7% per year of the term just ended, provided Odoo applies the clause as written. There is a view circulating that the cap only protects multi-year contracts and that single-year renewals can be repriced to list. That isn't what the clause says, and it's worth getting Odoo's position in writing before you sign a one-year renewal. Users you add during the term are charged at the list price on the day you add them. A growing business therefore feels a list increase immediately, and ends up with two prices on one invoice. New customers, and existing customers who change plan, pay the new list from day one. In the US, the customers who were angriest were those who had signed in November and were told in December that the January price applied to them. ## Is Odoo 20 going to change how users are priced? Partly confirmed, partly not. The code is real: a [commit to the Odoo 20 development branch](https://github.com/odoo/odoo/commit/818614c0099897efa9c389f20f91d94b7e06ba00) adds a new Light User role alongside the existing regular user and admin roles. A light user gets a small default set of rights: their own employee profile, their own attendance records, lunch ordering and basic point of sale. The moment you grant them anything beyond that they become a regular user. The commit also adds an invite, deactivate and reactivate workflow on the employee form, which is a long-overdue fix for businesses with a lot of staff who only ever clock in and check a payslip. What the commit does not say, and what nobody outside Odoo has said on the record, is what a light user costs. There is no pricing in the code, no mention in the subscription agreement, and no announcement. The LinkedIn posts describing it as a change to the pricing model are partner inference, not Odoo statements. It could be free, it could be a lower per-user tier, or it could be priced the same as a regular user and exist purely for access control. The reason it matters for this article is the pattern it fits. The US has already moved. European partners are openly predicting a rise for their region on the back of it and the clause 5.2 change. A cheaper employee-level seat is exactly what a vendor introduces when it is about to raise the price of the full seat, because it softens the headline for businesses with many light-touch staff. That is a reading, not a fact, and we'll say so until the keynote on 24 September 2026 in Brussels, where the [Odoo Experience programme](https://www.odoo.com/event/odoo-experience-2026-9099/) will settle it. If Australian pricing changes this year, that is the likely window, and we'll publish the numbers the same day. One more detail worth knowing: when US customers asked why their price rose 30%, some were told it was an exchange rate adjustment because Odoo sets its base prices in euros. The Australian dollar has weakened against the euro over the same period. Draw your own conclusion. ## Why is Odoo so expensive, and why is it so cheap? Both questions get searched, and both are fair. Per seat, Odoo is cheap: A$65 a month for the whole suite on Custom, against A$140 to A$310 per full user for MYOB Acumatica and roughly A$144 to A$198 for Business Central in Australia. What makes Odoo feel expensive is everything that sits around the seat: every approver and viewer needs a full internal user, Studio pushes you onto Custom at 51% more than Standard, Odoo.sh hosting is extra, implementation is usually the largest number, and the mechanisms above mean the price you signed at is not the price you keep. The licence is the cheap part; user account creep and the renewal mechanics are where the money goes. ## What to do 60 days before your Odoo renewal Odoo subscriptions renew automatically unless either side gives 30 days' written notice, so the useful work happens before that window closes. - **Check your version.** If you're on 16 or older, price the upgrade against the 25% surcharge you'll keep paying. Our [Odoo version upgrade guide](/blog/odoo-erp-australia-6/odoo-version-upgrade-australia) sets out what an upgrade actually costs. If you're on 17, the surcharge reaches you around April 2027. - **Check your plan.** Custom costs 51% more than Standard. If you aren't using Studio, multi-company or the external API, you may not need it, and we'll be publishing a guide to moving from Custom to Standard shortly. - **Count your users.** Archive anyone who has left. Check whether any internal users could be portal users, who are free. - **Read clause 5.2 and ask your account manager, in writing,** whether the 7% cap applies to your renewal and what the renewal price will be. - **Decide on term with your eyes open.** A prepaid multi-year term locks today's price and caps the eventual renewal at 7% per year of term, which for five years is up to 35% at the end. The discount for that is modest, typically in the 5% to 10% range depending on length, and it is paid upfront. For a two-user business that can be a reasonable trade. For a fifty-user business it is a large cheque to a vendor that repriced the US with five weeks' notice, and it deserves a proper cash flow conversation rather than a reflex. - **Get the quote in writing** before the 30-day notice window, not after. For the record, we're a partner for both Odoo and MYOB. Licence revenue isn't our business; making the system work for your company is. If we can make it work with one user, that's what we'll set up. **Worried about what your next Odoo renewal will cost?** Auboros is an Odoo partner based in Brisbane working with businesses across Queensland and the rest of Australia. We'll read your subscription agreement and renewal proposal with you, tell you which of these mechanisms actually apply, and show you the options in dollars. If you have a renewal in the next six months, [**get a second opinion on it**](/appointment). Thirty minutes, no pitch, and you keep the spreadsheet. --- # Odoo Renewal Price Australia: Why Month 13 Costs 25% More (A$52 to A$65) - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-renewal-price-australia - Category: Odoo ERP Australia - Published: 2026-08-21 - Description: Odoo subscription renewal in Australia: promo to list (+25%), the 7% a year clause and the 25% legacy fee can stack at once. The AUD maths and the prepay offer. An Odoo renewal proposal is a short document. Typically it shows your current plan and user count and a table comparing a one-year renewal with multi-year prepaid terms, sometimes with a note about why prices might rise. What it won't show you is the four clauses in your subscription agreement that decide what you actually pay, or the assumptions buried in that table. This guide walks through both, with Australian dollar examples, so you can read the next one properly. Figures are the Australian pricelist as at 22 August 2026, per user per month, excluding GST. We see a lot of these subscription renewal proposals. What follows is based on the current [Odoo Enterprise Subscription Agreement](https://www.odoo.com/documentation/19.0/legal/terms/enterprise.html), version 12, dated December 2025, which is the contract every Enterprise customer is on whether or not they have read it. ## What an Odoo renewal proposal looks like in 2026 The pattern customers are describing in 2026 is consistent. The proposal sets out the current subscription, then offers multi-year prepaid terms at a modest discount, framed as protection against future price rises. With the US increase in January, European partners predicting a rise for their region, and a new user tier appearing in the Odoo 20 code, that framing is landing on more receptive ears than it used to. Two things about the comparison table in these proposals are worth knowing before we get to the clauses. The yearly column is commonly illustrated with the price rising 7% every single year, compounding, with no list price change at all. And the "savings" figures for the multi-year options are calculated against that assumption, not against the price you pay today. Keep both in mind; we come back to them. ## Clause 5.2: the 7% per year rule, and the one-year question Clause 5.2 of the agreement covers renewal charges. In substance it says that if the charges you paid during the previous term are lower than the current list price, Odoo may increase them at renewal by up to 7% per year of the previous term. That last phrase changed in December 2025. Until then the clause allowed a single increase of up to 7% at each renewal regardless of term length. Under the current wording, the allowable increase scales with the term just ended: up to 7% after a one-year term, up to 14% after two years, up to 21% after three. The change removed the old advantage of a long contract, which was that you only faced one 7% step at the end of it, and it is why the multi-year proposals now talk about renewal rising by "a maximum of 7% per year of contract length, compounded". Now the one-year question. A view circulating in the community is that the 7% cap applies only to multi-year contracts and that single-year renewals can be repriced to list without limit. We cannot find support for that in the agreement. The clause refers to the previous Term, and a one-year subscription has a Term of one year. If you are told otherwise at renewal, ask for the clause being relied on, in writing, before you sign. If yearly customers are meant to be uncapped, that is material information and you are entitled to it before signing. Two further points on 5.2. It only applies if your price is below current list, so a customer already paying list has nothing to index from unless the list itself moves. And "up to" means Odoo may apply less; in our experience it usually applies the full amount. ## The prepay maths, without the sales framing Back to the comparison table. Multi-year options are presented as saving money against the yearly plan. They do, if you accept the assumption that the yearly price rises 7% every year. Against the price you pay today they save far less, and they require the whole term paid upfront. Take a two-user Custom customer paying A$1,560 a year at list. A five-year prepaid term at a 10% discount is A$7,020. Against a yearly column that compounds 7% every year, that shows as a saving of about A$1,950 over five years. Against a flat A$1,560 a year, the saving is A$780, and it costs A$7,020 on day one. For a two-user business that is a small cheque and a reasonable hedge. Scale it up. A 50-user Custom customer at list pays A$39,000 a year. A five-year prepay at 10% off is roughly A$175,000 upfront. What you get for it is a fixed price for five years and, at the end, a renewal that can rise by up to 7% for each of those five years, so up to 35% in one step. What you give up is A$175,000 of working capital and any ability to reduce users, change plan, or leave if the software stops fitting, with a vendor that repriced the US market by 30% on five weeks' notice in January. Our view, for what it is worth, is that prepaying three to five years of software rarely suits the A$2 million to A$20 million businesses we work with, who usually need that cash for stock, staff and equipment and prefer to budget software annually. But it is a cash flow decision, not a software one, and it belongs with your accountant rather than your account manager. What the proposal should not do is make the decision for you by comparing the prepay to a yearly column that already assumes the worst. > "The prepay offer isn't a trick, but the comparison table does a lot of work. Compare it to what you pay now, not to a column that has already added 7% four times." > > **Josh Craig, Director, Auboros** ## Clause 5.1: the 25% legacy version surcharge Clause 5.1 allows Odoo to charge, once a year, an extra fee equal to 25% of your annualised subscription if your database is running a version older than the three most recent major releases. The fee can be charged no earlier than six months after a new major version is released. In practice: Odoo 19 shipped in September 2025, which made versions 17, 18 and 19 the covered set. From April 2026, anyone on version 16 or older has been liable for the surcharge. Odoo 20 is due after the keynote on 24 September 2026, at which point version 17 leaves the covered set and becomes liable from around April 2027. The trade-off Odoo offers for the fee is that old versions now receive official support rather than being cut off entirely. Partners covered the mechanics in detail when the clause arrived in July 2025, including [some of the tricky cases](https://ventor.tech/odoo/will-your-odoo-enterprise-contract-be-surcharged-25-percent/) around contracts renewed before the change. The surcharge is calculated on your current price, not list, and it sits outside clause 5.2, so it stacks on top of any renewal increase. For a 20-user Custom customer at A$65 per user, it is A$3,900 a year for as long as you stay on the old version. Set that against the cost of upgrading, which our [Odoo version upgrade guide](/blog/odoo-erp-australia-6/odoo-version-upgrade-australia) breaks down, and the decision is usually clear within a year or two. ## The promotional cliff nobody mentions at signing The prices on [odoo.com/pricing](https://www.odoo.com/pricing) are first-year prices. The footnote says the discount is valid for 12 months and applies to the users ordered initially. In Australia that means Custom moves from A$52.00 to A$65.00 per user per month on yearly billing at your first renewal, and Standard from A$34.40 to A$43.00. That is a 25% step before any clause in the agreement comes into play. It also interacts with clause 5.2 in an unhelpful way. Your first-year price is by definition below list, so the first renewal can involve both the end of the discount and a 7% indexation on top, depending on how Odoo applies the clause. Ask which you are getting. Users added during the first year don't get the discount. They are charged at the list price of the day, which is why a growing business can find two different per-user prices on one invoice, and why the [Odoo forum](https://www.odoo.com/forum/help-1/unexpected-subscription-cost-increase-when-adding-users-272931) has a steady stream of questions titled some variant of "why did my subscription cost go up when I added a user". ## Three questions nobody answers **Does a user who has never logged in count?** Yes. The agreement counts any active user account with create or edit access, whether or not they have ever signed in. Archive the accounts you created for people who never started. **Is the 25% legacy fee pro-rated if I upgrade mid-year?** No. The fee is assessed once a year against your annualised price when Odoo runs its check, about six months after a major release. Finish an upgrade two months after the check and, on the cases partners have reported, you still wear the full 25% for that year, which is why upgrade timing matters more than most people mention. **Can I mix Standard and Custom users on one subscription?** No. The plan applies to the database, not the person, so one Studio user puts every user on Custom. That is the whole argument for asking whether you need Custom at all. ## Monthly plans: the 30-day notice trap Monthly billing costs about 25% more than yearly in Australia (A$81.00 against A$65.00 for Custom at list), and it comes with a catch that has caught out customers trying to manage cost: reducing your user count on a monthly plan now requires 30 days' notice. Archive a user today and you keep paying for them for another month. If you are on monthly billing for flexibility, check that the flexibility you are paying for is real. ## Five questions to ask your Odoo account manager before you sign Ask them in writing, and keep the answers with the agreement. - **What will my per-user price be at this renewal, and which clause is it calculated under?** You want to see the promotional cliff and any clause 5.2 indexation stated separately. - **Does the 7% per year cap in clause 5.2 apply to my renewal?** If the answer is no for a one-year term, ask for the basis. - **Am I, or will I be, liable for the clause 5.1 surcharge, and from what date?** Get the date in writing if you are on version 17. - **If I add users during the term, what price will they be charged?** The answer is list price of the day; confirm it. - **If I prepay a multi-year term, what is the maximum my price can rise at the end of it?** You are looking for 7% multiplied by the number of years. If the answers don't match the agreement, that is worth knowing before you sign rather than after. For the record, we're a partner for both Odoo and MYOB. Licence revenue isn't our business; making the system work for your company is. If a one-year term, a lower plan or fewer users is the right answer, that's what we'll recommend. If you're weighing whether Enterprise is still the right edition at all, our comparison of [Odoo Community and Enterprise for Australian businesses](/blog/odoo-erp-australia-6/odoo-community-vs-enterprise-australia) is the place to start, and our [Odoo pricing guide for Australia](/blog/odoo-erp-australia-6/odoo-pricing-australia) covers the full cost picture beyond the licence. **Got an Odoo renewal proposal on your desk?** Auboros is a Brisbane-based Odoo partner working with businesses across Queensland and Australia, and reading renewal proposals against the agreement is something we do for clients whether or not we built their system. If you'd like a second opinion on yours before the 30-day notice window closes, [**book a free consultation**](/appointment), no pitch. We'll tell you which clauses apply and what the options cost, in plain numbers. More on how we work with Odoo clients is on our [Odoo services page](/solutions/odoo). --- # The AI Agent Register: How to Stay in Control When Your Business Runs More Than One Agent - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-agent-register-australia - Category: AI & ERP - Published: 2026-08-20 - Description: What an AI agent register records, the 10 December 2026 privacy deadline that makes it matter, and how Australian businesses can start with just one page. An AI agent register is a single record of every AI agent your business runs: what each one does, who owns it, which systems it can touch, what it costs, and who approves its work. It sounds like admin. It is admin. It's also the difference between running agents and being run by them, and with [12% of Australian businesses now using AI](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25) (22% of medium-sized ones, per the ABS), plenty of teams are about to find that out. We've covered [what AI agents can do inside Australian businesses](/blog/ai-erp-australia-8/ai-agents-for-australian-businesses-what-actually-works-in-2026-132) and the controls that make a single agent safe. This post is about the next problem, the one that arrives quietly: what happens when there's more than one. ## One agent is a tool, five agents are a fleet Nobody plans agent sprawl. It happens one useful idea at a time. The sales team gets an agent that drafts orders from emailed PDFs. The buyer wants the same treatment for replenishment. Meanwhile someone in accounts has built a Copilot flow nobody else has seen, and a manager is pasting debtor lists into a chatbot because it's faster than asking for a report. Each might be fine on its own. Together they raise questions that get harder every month. What's actually running? Who owns the one that touches pricing? What did they cost last month? Which ones can write to the ledger, and who approves what they write? Auboros runs research, content and QA agents over our own operations, drafts-first with a person approving the output, and even at that scale we lost track of one for a fortnight. It kept working. That was the unsettling part. An agent that fails loudly gets fixed; one that hums along unwatched is the real risk. > "The first register we build with a client is never surprising because of the agents IT knows about. It's the two nobody wrote down. You can't govern what you haven't listed." > > **Bill Alvarez, Practice Manager, Auboros** ## What goes in an AI agent register The good news is that the fix is a table, not a platform. Ours has seven columns, and it fits on a page: - **Name and job.** What the agent does, in one sentence a non-technical director would understand. "Reads emailed purchase orders and drafts sales orders for approval." - **Owner.** A named person, not a department. The owner answers for the agent's output. - **Systems and scope.** Which systems it connects to, whether access is read-only or write, and whose permissions it acts under. An agent should act with a real user's data scope, never a shared super-user. - **Model and data path.** Which AI model or vendor sits behind it, and where your data goes. If customer records leave Australia, this is where that gets written down. - **Approval gates.** What it's allowed to draft, and who approves each draft before anything posts. Ledger, tax, pricing and stock write-backs need a human on the gate, every time. - **Cost.** The subscription plus last month's usage. Agent costs drift, and the register is where drift becomes visible. - **Escalation and review.** Who can switch it off, what it should do when it's unsure, and the date of the next review. You don't have to invent the format. The National AI Centre publishes a free AI register template as part of its [Guidance for AI Adoption](https://www.industry.gov.au/publications/guidance-for-ai-adoption/guidance-ai-adoption-foundations), which condensed Australia's earlier ten voluntary guardrails into six essential practices in October 2025. The guidance expects approved AI systems to be recorded in a register. For agents that touch an ERP, we'd add the approval-gate and cost columns; the template covers the rest. ## The two dates that make a register worth having The register pays for itself operationally, but two dates give it teeth. The first has passed: 21 October 2025, when the National AI Centre released the guidance above. It's voluntary, and Australia still has no general AI Act. It is, though, the standard a customer, insurer or board member will reach for when they ask how you govern AI, and "we follow the national guidance, here's our register" is a short, convincing answer. The second is coming: 10 December 2026. From that date, businesses covered by the Privacy Act must say in their privacy policies what kinds of personal information they use in [automated decisions that could significantly affect people, and what kinds of decisions those are](https://www.oaic.gov.au/engage-with-us/consultations/consultation-on-guidance-for-transparency-in-automated-decision-making). The OAIC consulted on draft guidance over May and June 2026 and says it intends to publish the final version by September 2026. You cannot write that disclosure without knowing what your agents do. The register is where the answer comes from. We covered the wider control set in our guide to [AI agent governance for Australian businesses](/blog/ai-erp-australia-8/ai-agent-governance-australia); the register is the page that makes the rest of it auditable. ## What Odoo and MYOB Acumatica already track for you If your agents live inside your ERP, part of the register already exists. In Odoo 19, every AI agent is a record in the system: its name, its instructions, which model it uses, which tools it's allowed to call and which knowledge sources it can read. Odoo's own documentation confirms that [agents act within the signed-in user's access rights](https://www.odoo.com/documentation/19.0/applications/productivity/ai/agents.html) and that the default Ask AI agent can't create or alter data. That's shipped today. One telling detail from the source code: the call summariser agent ships switched off. A human decides to turn it on. We've written up [what Odoo's AI agents can do today](/blog/ai-erp-australia-8/odoo-ai-agents-australia) in more depth. MYOB Acumatica is earlier in the same journey. The current ANZ release is 25 R2, which includes [AI Studio in technology preview](https://www.myob.com/au/press-releases/myob-acumatica-launches-new-ai-studio-in-collaboration-with-aws), built with AWS and Anthropic with data processed in local data centres. In the preview release, agents run when a user asks and can't create records or documents on their own; general availability is planned for the 26 R1 release, and MYOB hasn't committed an ANZ date. Globally, Acumatica's 2026 R1 shipped in March 2026 with its [AI Assistant under managed availability](https://community.acumatica.com/acumatica-news-updates-2/acumatica-ai-assistant-2026-r1-managed-availability-and-faq-34846), and global features typically reach the ANZ product 6 to 9 months later. Label your register entries accordingly: shipped, preview or roadmap. What neither platform can see is everything outside itself: the Copilot flow in accounts, the chatbot project a manager runs from a browser, the automation a contractor left behind. That gap is why Microsoft now sells [Agent 365](https://www.microsoft.com/en-us/security/blog/2026/05/01/microsoft-agent-365-now-generally-available-expands-capabilities-and-integrations/), a control plane for discovering and governing agents that reached general availability in May 2026. For a large organisation deep in Microsoft 365 it's worth a look; for most mid-market businesses it's more platform than the problem needs. The one-page register comes first either way, because no tool can govern agents you haven't decided to own. ## A Tuesday morning in mission control Here's the register alive, drawn from patterns we build for wholesale clients. A Queensland distributor runs three agents over its ERP. At 7:20am the operations manager opens the approval queues. The [replenishment agent](/blog/ai-erp-australia-8/ai-replenishment-agent-erp-australia) proposed eleven purchase orders overnight; the buyer approves nine and sends two back because a supplier has changed its minimum order quantity. The sales order agent read fourteen emailed purchase orders and drafted thirteen; the fourteenth was an unreadable scan, so it escalated to a person instead of guessing. The credit agent drafted six payment reminders; the credit controller approves five and holds one because that customer is mid-conversation about a payment plan. Then the cost column earns its place. Usage on the sales order agent doubled last week. The register names an owner, the owner looks, and the cause is a supplier now attaching a 300-page catalogue to every order email. The fix takes ten minutes. Without the register, that cost drifts until someone spots it in the P&L, with no name attached. Twenty minutes, one page, three humans making every decision that matters. That's mission control at mid-market scale. ## Start with a page, not a platform If you run even one agent against live business systems, start the register this week. List everything that runs, including the unofficial ones; an amnesty gets better answers than an audit. Name an owner for each. Write down scope, gates and last month's cost. Book a monthly half-hour review, and give new agents a sandbox before they touch production. Our [AI agent services](/solutions/ai-agents) page describes how we design these patterns, drafts-first with role-scoped permissions, and the register is the first artefact we build on every engagement. **Running more than one agent, or about to?** Auboros designs, governs and runs AI agents over Odoo and MYOB Acumatica for Australian businesses, from our base in Brisbane and the Gold Coast. We'll help you build the register, set the approval gates and wire the agents in safely. If you'd like a second pair of eyes on what's already running in your business, [**book a free consultation**](/appointment). Bring the unofficial agents too. We've seen worse. --- # ERP for Food and Beverage Wholesalers in Australia: What to Look For - Canonical URL: https://www.auboros.com/blog/insights-5/erp-food-beverage-wholesalers-australia - Category: Insights - Published: 2026-08-20 - Description: What ERP for food and beverage wholesalers must cover in Australia: batch tracking, FEFO picking, recall readiness and how MYOB Acumatica and Odoo compare. The worst week in food wholesale starts with a phone call. A supplier has found a problem with a batch, the product is already sitting in your customers' cool rooms, and someone needs a list of exactly who received it. Not by Friday. Now. How that week goes depends almost entirely on your software. Food Standards Australia New Zealand coordinated [92 food recalls in 2025](https://www.foodstandards.gov.au/news/2025-food-recall-statistics-released), above the ten year average of 87, with undeclared allergens behind 38% of them. A recall is a routine event in this industry. Software that treats stock as one undifferentiated pile turns a routine event into a very expensive one. ## Why food and beverage wholesale breaks generic software Most ERP advice for the food industry is written for manufacturers, so it talks about recipes, yields and production lines. Wholesale is a different business. You don't make the product. You buy it, store it at the right temperature, break it into customer orders and move it on before it expires. That last word is the whole problem. A pallet of yoghurt is really a product plus a batch number plus a use by date, and two pallets with different dates aren't interchangeable. Generic inventory software counts cartons. A food wholesaler needs software that counts cartons of batch 4471 expiring on 12 October, because that's the level at which stock gets bought, rotated, sold and recalled. Margins sharpen the problem. The Australian Bureau of Statistics counted [2.8 million actively trading businesses](https://www.abs.gov.au/statistics/economy/business-indicators/counts-australian-businesses-including-entries-and-exits/latest-release) in the year to June 2026, and wholesale trade was one of the slowest growing divisions at 0.5%. Growth in this sector rarely comes from a rising market. It comes from wasting less stock, and from clawing back the hours lost to re-keying data between systems. MYOB's [ERP Trends report](https://www.myob.com/au/insight/post/erp-trends) found 45% of Australian businesses say disconnected systems limit their growth. A wholesaler running separate stock, accounting and delivery run software feels that every single morning. ## What ERP for food and beverage wholesalers has to cover Strip away the brochures and the list is short. If a platform can't do these five things well, it doesn't belong on your shortlist. - **Batch tracking on every stock movement.** Every receipt, putaway, transfer and dispatch should carry the lot number without anyone typing it twice. Barcode scanning at the dock is what makes this stick in practice. - **Expiry dates that drive picking.** First expired, first out (FEFO) picking means the system tells your team which pallet to take based on date codes, instead of relying on whoever stacked the racks last. - **Recall reports in minutes.** Given a lot number, the system should list where it came from, which customers received it, how much shipped and what's still on the shelf. If that report takes longer than a coffee, it will fail you during a real recall. - **Customer specific pricing.** Cafes, independent grocers and food service groups all pay different prices, often with rebates or promotional deals on top. Price lists have to live in the system, not in a sales rep's head. - **GST that copes with a mixed basket.** Most basic food is [GST-free](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst/when-to-charge-gst-and-when-not-to/gst-free-sales), while soft drinks, confectionery and plenty of prepared items attract the standard 10%. One invoice can mix both, so tax needs to be set per item and flow correctly through to the Business Activity Statement (BAS). Temperature adds a quieter layer. Chilled, frozen and ambient stock typically map to separate zones or locations in the warehouse setup, and if a 3PL runs your cold chain, visibility of stock sitting in their shed matters as much as your own. ## Recall readiness: one step back, one step forward The regulatory floor is clear. Under the Food Standards Code, food businesses need to be able to [trace product one step back and one step forward](https://www.foodstandards.gov.au/business/food-safety/food-traceability): who supplied it, and who you supplied it to. Wholesale suppliers are also required to keep a [written food recall plan](https://www.foodstandards.gov.au/food-recalls/faqbusiness). Plenty of businesses meet the letter of these rules with paper and spreadsheets. Meeting them at speed is another matter. > "Every wholesaler we meet says the same thing after their first recall scare: the product problem was manageable, the information problem nearly killed them. When stock is batch tracked in one system, 'who received carton X' is a two minute report instead of a weekend of phone calls." > > **Josh Craig, Director, Auboros** A recall drill is a fair test to run during ERP selection. Pick a batch at random and ask the vendor to show you the full trace, both directions, live in the demo. The platforms below pass that test when they're set up properly. Plenty of ad hoc setups don't. ## How MYOB Acumatica and Odoo handle food wholesale MYOB Acumatica tracks stock with [lot and serial classes](https://help.acumatica.com/Help?ScreenId=ShowWiki&pageid=1974b7c0-4995-4a2a-8002-53757f98e090) that control how numbers are assigned, whether expiry dates apply and how stock is issued, including automatic issue of the earliest expiring lot. Wholesale distribution is the platform's home ground: purchasing, warehouse management, customer pricing tiers and financials in one mid-market system, with multi-entity support when a group runs more than one company. For smaller distributors, the [MYOB Acumatica FastStart Wholesale Distribution program](/solutions/myob-acumatica-faststart-wholesale-distribution) delivers a fixed scope implementation in around 12 weeks, and it's the program we run in Queensland. Odoo covers similar ground for growing wholesalers at a lower entry point. Its inventory app tracks [expiration dates on lots](https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/product_management/product_tracking/expiration_dates.html), including best before, removal and alert dates, and its [FEFO removal strategy](https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/shipping_receiving/removal_strategies/fefo.html) picks stock with the nearest removal date automatically. Add barcode scanning and multi-warehouse support, covered in our guide to [Odoo inventory management](/blog/odoo-erp-australia-6/odoo-inventory-management-australia-106), and the platform handles date coded stock properly while also running your accounting, purchasing and online ordering. Reordering is where the next gain usually lives. Perishable stock punishes over-ordering and stockouts with equal enthusiasm, which is why replenishment is the first place we point AI at for wholesale clients. Our post on [the AI replenishment agent](/blog/ai-erp-australia-8/ai-replenishment-agent-erp-australia) explains the drafts-first pattern, and the appetite is already there: MYOB's [research](https://www.myob.com/au/insight/post/erp-trends) found 78% of wholesale distribution businesses plan to use AI in their ERP. ## Where the other platforms fit Some honesty helps here. Pronto Xi has a long history in Australian food distribution and remains a credible option, particularly for larger operations already in its ecosystem. NetSuite suits distributors with international parents, though Australian payroll typically needs a third party add-on. Dedicated fresh produce systems still win in narrow niches like market floor trading. We compared the wider field in our guide to the [best ERP for wholesale distribution in Australia](/blog/insights-5/best-erp-wholesale-distribution-australia), and our [wholesale distribution industry page](/industries/wholesale-distribution) covers how we scope these projects. The short version: a mid-market distributor with multiple entities or heavier volumes usually lands on MYOB Acumatica. A growing wholesaler that wants stock, accounting and ordering in one system without mid-market licensing usually lands on Odoo. Both pass the recall drill. --- **An ERP your food safety auditor will actually like** Auboros implements MYOB Acumatica and Odoo for wholesalers from Brisbane, working across Queensland and beyond, and we've sat through enough recall drills to know where they go wrong. If batch tracking, FEFO picking or recall reporting is on your shortlist criteria, [**book a free consultation**](/appointment). Bring your current recall procedure and we'll tell you which platform fits, or whether your current setup just needs tightening. --- # MYOB Acumatica for Importers and Exporters: Landed Costs, Deferred GST and Multi-Currency - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-importers-exporters-australia - Category: MYOB Acumatica Australia - Published: 2026-08-20 - Description: MYOB Acumatica for importers and exporters: multi-currency, landed costs, deferred GST and the 60 day export rule, explained for Australian businesses. Selling into the US and buying out of Vietnam looks great on the margin sheet, right up until the accounting starts. Every shipment brings a foreign currency purchase order, a freight bill, a customs entry and a goods and services tax (GST) question, and most small business accounting packages handle maybe half of that. It's a common wall to hit: the Australian Bureau of Statistics counted [56,274 goods exporters](https://www.abs.gov.au/statistics/economy/international-trade/characteristics-australian-exporters/latest-release) in 2019-20, the most recent release of that series, and the accounting behind that trade is the same whether you ship one container a quarter or twenty. So this guide looks at MYOB Acumatica for importers and exporters in practice: multi-currency that follows the whole transaction, landed costs that tell you what stock really cost you, and the two GST rules that decide your cash flow, deferred GST coming in and the 60 day rule going out. ## How MYOB Acumatica works for importers and exporters The useful difference from entry level accounting packages is that the whole trade workflow lives in one system. A purchase order raised in US dollars flows through goods receipt, customs costs, warehouse putaway and on to a sale in Australian dollars, with the general ledger picking up every step. The platform's [currency management tools](https://enterprisesupport.myob.com/knowledge/help-with-currency) cover multicurrency invoices and payments, funds transfers between foreign currency bank accounts, and revaluation of foreign currency balances, so month end reporting reflects current rates rather than the rate on the day you booked the invoice. For groups, this extends across companies. Plenty of importers run an Australian entity and a New Zealand one, and our guide to [MYOB Acumatica multi-entity accounting](/blog/myob-acumatica-australia-7/myob-acumatica-multi-entity-australia) covers how consolidations and intercompany transactions work when the two sides trade in different currencies. ## Landed costs: what your imported stock really costs An imported carton has a supplier price, and then it has the truth: supplier price plus ocean freight plus duty plus insurance plus the broker's fee. MYOB Acumatica records these as [landed costs allocated to inventory](https://help.acumatica.com/Help?ScreenId=ShowWiki&pageid=682b3203-18ed-4258-821a-61a82117d65f), spread across the items on a shipment by value, quantity, weight, volume or a custom split, with the adjustments posted into inventory value automatically. Why care? Because every report downstream depends on it. If freight and duty sit in a general expense account, your gross margin by product is fiction, and pricing decisions get made on that fiction. > "The importers we meet usually know their exchange rate to four decimal places and their true landed cost not at all. Getting freight and duty onto the item is the one change that makes their margin reports believable." > > **Bill Alvarez, Practice Manager, Auboros** ## Deferred GST, the scheme importers keep leaving on the table By default, imports attract GST that is generally payable to the Australian Border Force before the goods are released. The [deferred GST scheme](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst/in-detail/rules-for-specific-transactions/international-transactions/gst-and-imported-goods) lets approved importers pay that GST through their monthly Business Activity Statement (BAS) instead, where it usually nets against the matching credit on the same statement. The conditions are simple enough: apply to the ATO, lodge your BAS monthly, and lodge it electronically. In MYOB Acumatica the deferred amount itself needs no special handling, because the ATO fills it in when processing the BAS. What does need care is any GST you actually pay to customs, and MYOB's [support guide for deferred GST](https://enterprisesupport.myob.com/knowledge/deferred-gst-for-imported-goods) walks through that setup: the customs invoice is booked with a dedicated import GST tax code so the full amount lands as a GST credit in the right BAS label. Your implementation partner maps those codes once, and the monthly process becomes routine. ## Exports, the 60 day rule and GST-free invoicing Exports run the other way. Sales of goods are [GST-free if exported within 60 days](https://www.ato.gov.au/businesses-and-organisations/international-tax-for-business/australians-doing-business-overseas/exports-and-gst) of the earlier of receiving payment or issuing the invoice, and you can ask the ATO for an extension if shipping schedules blow that window out. In the system this is more discipline than configuration: export sales carry a GST-free tax category, invoices go out in the buyer's currency where that's what the contract says, and the paper trail proving the goods left the country stays attached to the transaction. Wholesale distributors do a lot of this trade, which is why import and export handling sits inside the scoping conversation for the [FastStart Wholesale Distribution program](/solutions/myob-acumatica-faststart-wholesale-distribution), and why the platform features so heavily in our comparison of the [best ERP for wholesale distribution in Australia](/blog/insights-5/best-erp-wholesale-distribution-australia). ## Where to start If your import costing lives in a spreadsheet next to the accounting file, you already know the failure mode: the spreadsheet is right up until the week nobody updates it. Moving the trade workflow into [MYOB Acumatica](/solutions/myob) is a scoped project rather than a leap, and appetite for that move is broad. MYOB's [2025 Mid-Market Survey](https://www.myob.com/au/insight/post/mid-market-survey-results-2025) found 36% of Australian mid-sized businesses are looking to upgrade their ERP, and the ones trading across borders have the most to gain from doing it. --- **Import and export accounting that survives an audit** Auboros implements MYOB Acumatica from Brisbane for importers, exporters and distributors across Queensland and beyond. If your landed costs, deferred GST or multi-currency reporting need to come out of spreadsheets, [**book a free consultation**](/appointment). We'll walk through one of your real shipments end to end and show you what it looks like in the platform. --- # Best ERP for Wholesale Distribution in Australia: How to Choose in 2026 - Canonical URL: https://www.auboros.com/blog/insights-5/best-erp-wholesale-distribution-australia - Category: Insights - Published: 2026-08-19 - Description: The best ERP for wholesale distribution in Australia depends on your size and channels. An honest look at MYOB Acumatica, Odoo, NetSuite and Pronto Xi. Type "best ERP for wholesale distribution" into Google and most of page one is written for American distributors. The pricing is in US dollars, the payroll advice does not apply here, and nobody mentions BAS. If you run a wholesale business in Australia, you need a shortlist built for the market you operate in. This guide covers the platforms Australian wholesalers most often compare, and a practical way to match one to your operation. A disclosure before we start: we implement two of them, Odoo and MYOB Acumatica. We will be upfront about where the others win, because they sometimes do. The backdrop makes the choice matter more, not less. [Wholesale trade business numbers grew just 0.5% in the year to June 2026](https://www.abs.gov.au/statistics/economy/business-indicators/counts-australian-businesses-including-entries-and-exits/latest-release), one of the slowest rates of any industry division in the ABS counts. In a sector growing that slowly, the distributors that grow are taking share from someone else, and they usually do it with tighter operations. That helps explain why [45% of Australian businesses say disconnected systems are limiting their growth](https://www.myob.com/au/insight/post/erp-trends) and [36% of mid-sized businesses are looking to upgrade their ERP](https://www.myob.com/au/insight/post/mid-market-survey-results-2025). ## What a wholesale distribution ERP needs to cover Before you compare brands, agree on the checklist. We work through a longer version of this with distributors on our [wholesale distribution industry page](/industries/wholesale-distribution), but the core list is consistent: - **Inventory across locations.** Live stock by warehouse, batch and expiry tracking where your products need it, and a costing method (FIFO or average cost) that holds up when your accountant reconciles the BAS. - **Purchasing and replenishment.** Reorder points, supplier lead times and draft purchase orders raised before you run out rather than after. - **B2B sales and pricing.** Customer specific price lists, trade discounts, credit limits and backorder handling without spreadsheet workarounds. - **Landed costs.** Freight, duty and insurance allocated to inventory so your margin reports tell the truth. - **Australian financials and payroll.** GST coding, BAS reporting, Single Touch Payroll, and [Payday Super, which applies from 1 July 2026](https://www.ato.gov.au/businesses-and-organisations/super-for-employers/payday-super/about-payday-super) and requires contributions to reach funds within 7 business days of payday. - **Integrations.** Ecommerce platforms, 3PL and freight carriers, and EDI if you supply the major retailers. If a platform cannot cover most of that natively, you end up rebuilding the disconnected stack you were trying to escape. ## The ERP platforms Australian wholesalers shortlist ### MYOB Acumatica MYOB Acumatica (formerly MYOB Advanced) is built on the Acumatica cloud platform with MYOB's Australian payroll and compliance layer on top. Its distribution capability runs deep: sales order workflows, purchasing, warehouse operations and [replenishment driven by reorder points, safety stock and demand forecasts](https://www.acumatica.com/cloud-erp-software/inventory-management/). Licensing is per named user with different access tiers, so cost depends on your user mix rather than a flat headcount figure, and quotes come through partners. For wholesalers under roughly $10 million revenue, the [FastStart Wholesale Distribution program](/solutions/myob-acumatica-faststart-wholesale-distribution) is worth serious consideration. It is a fixed scope implementation designed to go live in 12 weeks, which removes much of the cost uncertainty that keeps smaller distributors on outgrown software. ### Odoo [Odoo](/solutions/odoo) covers more functional ground than anything else on this list: inventory, purchasing, accounting, CRM, ecommerce and manufacturing in one system with published per user pricing. Its [reordering rules generate draft purchase orders automatically when forecast stock falls below your minimum](https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.html), and the replenishment report shows forecast stock, lead times and order deadlines in a single view. Odoo's particular strength for distributors is the sales channel side. If you sell wholesale and direct online, the native ecommerce and website apps draw on the same inventory as your B2B orders, so there is no stock sync to babysit. The Australian localisation handles BAS and STP. The trade off is that Odoo is a framework as much as a product, and the quality of the implementation partner shapes the result more than the licence does. ### NetSuite, Business Central and Pronto Xi Three other platforms appear on serious Australian shortlists, and all three are credible. NetSuite is strong for groups running multiple entities or trading internationally, with mature consolidation and reporting. It typically carries a higher total cost than the mid-market platforms above, and Australian payroll typically runs through a third party add-on. Microsoft Dynamics 365 Business Central suits businesses committed to the Microsoft stack and has a large partner ecosystem in Australia. Pronto Xi is Australian developed and has a long track record in inventory heavy industries; for some complex distribution operations it remains a strong fit. Where these three tend to lose smaller wholesalers is implementation weight and cost predictability. They are built for complexity, and you pay for that whether you need it or not. ### When inventory software is enough Not every wholesaler needs an ERP yet. If your operation is one warehouse, one sales channel and an accounting file that still copes, a dedicated inventory tool in front of Xero or MYOB Business may be the right call for now. We covered the crossover point in our [Odoo vs Cin7 Core comparison](/blog/odoo-erp-australia-6/odoo-vs-cin7-core-australia-121). The short version: the ERP conversation starts when handoffs between systems begin costing you orders, stock accuracy or days at month end. ## How to choose the best ERP for wholesale distribution in Australia Feature lists will not make this decision for you, because every platform above covers the core checklist to a reasonable standard. The better questions are operational. > "Every wholesale ERP demo looks the same because the demo data is clean. The real test is your messiest workflow: the customer on contract pricing with a rebate, the supplier who ships short, the stocktake that never balances. Pick the platform that survives that conversation." > **Bill Alvarez, Practice Manager, Auboros** A rough sizing guide from the projects we see: - **Under about $10 million revenue.** Fixed scope programs make sense. FastStart on MYOB Acumatica, or a tightly scoped Odoo implementation, keeps the timeline near 12 weeks and the budget contained. - **Roughly $10 million to $50 million, single entity.** MYOB Acumatica and Odoo both compete hard here. The decision usually turns on payroll depth, how much of your revenue comes through ecommerce, and which local partner you trust to deliver. - **Multi-entity or international.** NetSuite and Business Central enter the conversation, and Pronto Xi where inventory complexity is extreme. MYOB Acumatica also handles multi-entity structures well within Australia and New Zealand. In the [same MYOB research](https://www.myob.com/au/insight/post/mid-market-survey-results-2025), 48% of mid-sized businesses named operational efficiency as the main driver for upgrading. That is the right lens. Rank each platform against your five most painful processes today, not against a features matrix. ## Where AI fits in distribution [78% of wholesale distribution businesses told MYOB they plan to use AI within their ERP](https://www.myob.com/au/insight/post/erp-trends), the highest of any industry in the survey. The pattern that works today is drafts first: an agent reads sales velocity, supplier lead times and stock levels, then drafts replenishment orders or flags margin drift for a human to approve. Nothing posts without sign off. We explain the approach on our [AI agents for ERP page](/solutions/ai-agents). Treat AI capability as a tiebreaker rather than the headline. It amplifies a well implemented ERP and does nothing for a badly implemented one. ## Questions to ask every vendor before you sign - **Show me landed costs on a real shipment.** Freight, duty and currency, allocated to stock, with the journal it creates. - **Show me a customer with contract pricing and a credit limit.** Then show what happens when they order past the limit. - **Walk me through BAS and STP.** In the product, with Payday Super timing, and not on a slide. - **What does the integration to my ecommerce platform or 3PL cost to build and to keep running?** - **Who does the implementation, and how many Australian wholesale projects have they delivered?** The platform matters. The people configuring it for your warehouse matter at least as much. **Building a wholesale ERP shortlist?** We are a Brisbane based consultancy that implements both Odoo and MYOB Acumatica for wholesalers across Queensland and the rest of Australia, and we will tell you if the right answer for your size is neither of them yet. If you want a second opinion on your shortlist, [**book a free consultation**](/appointment). Bring your messiest workflow and we will talk through how each platform would handle it. --- # The AI Channel Sync Agent: How It Catches Price and Stock Drift in Odoo and MYOB Acumatica - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-channel-sync-agent-erp-australia - Category: AI & ERP - Published: 2026-08-19 - Description: What an AI channel sync agent does about price and stock drift across your ERP, Shopify and marketplaces, and why a person approves every fix it drafts. Your ERP says three units in stock. Shopify says fourteen. A marketplace listing is still showing a promo price that ended a fortnight ago. Nobody changed anything on purpose, and every system involved is working exactly as it was configured to. This is channel drift, and if you sell through more than one channel, you have some of it right now. An AI channel sync agent is a monitoring agent that reads prices, stock levels and product content across your ERP, your online store and your marketplaces, flags anything that doesn't match, and drafts corrections for a person to approve. It doesn't replace your connectors. It checks their work, and yours. [MYOB's ERP research](https://www.myob.com/au/insight/post/erp-trends) found 45% of Australian decision-makers say disconnected systems limit growth, and channel drift is that problem in its most public form. It's the version of your data your customers can see. ## Why price and stock drift happens even when your connector works Connectors move data on a schedule or in response to events, and they do it the same way every time. That predictability is the whole point. In our experience the drift almost never starts inside the connector. It starts at the edges: - **Edits made directly in the storefront.** Someone fixes a price in the Shopify admin at 5pm to close a sale, means to update the ERP tomorrow, and doesn't. The two systems now disagree, and the next sync may or may not put them back in step depending on which direction it pushes. - **Promotions that outlive their end date.** A sale price gets loaded on the channel, the end date passes, and the full price never comes back because the promo was never in the ERP to begin with. - **SKU mismatches.** Odoo's [Amazon Connector matches orders to products by internal reference](https://www.odoo.com/documentation/19.0/applications/sales/sales/amazon_connector/features.html), which is your SKU. Rename a SKU on one side and the matching quietly breaks for that product. - **Sync windows.** MYOB's eCommerce Connector pushes product, price and inventory updates [manually or on a schedule](https://www.myob.com/au/insight/post/ecommerce-for-myob-acumatica). Between runs, the channels disagree by design. That's fine, as long as someone knows how wide the window is. - **Fields no connector carries.** Every integration has a scope. Whatever sits outside it, often product descriptions, images or channel-specific pricing, is maintained twice by hand, and hand-maintained data drifts. - **Warehouse corrections.** A stocktake writes inventory down in the ERP after the morning sync has already told the marketplace there's plenty available. None of these are bugs. They're the normal texture of running one product catalogue across three or four systems, which is why checking for drift is a standing job rather than a one-off cleanup. ## How an AI channel sync agent actually works The agent runs on a schedule, reads from each system through its API under its own limited credentials, and compares. Price in the ERP against price on each channel. Free-to-sell stock against displayed availability. SKU mappings against the product master. Where everything matches, it says nothing. Where something doesn't, it flags the difference, proposes a correction, and waits. Here's a concrete morning from a setup like the ones we build. At 6:30am the agent compares a wholesale distributor's ERP against their Shopify store and marketplace listings. It finds three exceptions. A promo price is still live on one SKU nine days after its end date. A product the stocktake wrote down to three units still shows fourteen available on the marketplace. And one SKU stopped matching entirely after a rename last week, so nothing has synced for it since. The agent drafts a summary with a proposed fix for each, sized in dollars: the promo SKU has sold 41 units below list since the end date. The channel manager reads it with coffee, approves the price restore and the stock correction, and holds the SKU rename for a quick check with the warehouse. The approved fixes go out through the normal connector, and every step is logged. > "The connector is almost never the thing that's broken. Drift comes from the edges. A promo that never ended, a SKU renamed on one side, a stocktake that landed after the sync ran. The agent's job is to notice fast and put a correction in front of a person, not to fire updates at three sales channels on its own." > > **Josh Craig, Director, Auboros** Most of the tools marketed in this space promise the opposite: agents that detect mismatches and fix them automatically. We'd urge caution there. An agent with unattended write access to your prices and stock is a new way to be wrong at scale, and when it misreads a situation it will misread it on every channel at once. Drafts first, a person approves, always. It's the same pattern we use for [replenishment agents that draft purchase orders](/blog/ai-erp-australia-8/ai-replenishment-agent-erp-australia), and it costs you minutes a day. ## Wrong prices online are a compliance problem in Australia Drift isn't just untidy. The ACCC requires businesses to [display clear and accurate prices as a single total figure](https://www.accc.gov.au/consumers/pricing/price-displays), including GST (Goods and Services Tax). If different prices for the same item are displayed in different places, the multiple pricing rules apply: sell at the lowest displayed price or withdraw the item until it's corrected. And advertising a special price on stock you can't actually supply in reasonable quantities can amount to [bait advertising](https://www.accc.gov.au/publications/advertising-selling/advertising-and-selling-guide/advertising-selling-and-promotional-techniques/advertising-techniques). Notice that every one of those risks is exactly what drift produces. A promo price lingering on one channel is a multiple pricing problem. A marketplace showing availability the warehouse doesn't have is an availability claim you can't back. None of this is legal advice, and edge cases belong with your lawyer. The practical point is simpler: a daily drift check is cheap insurance against problems that are expensive to have. ## Where Odoo and MYOB Acumatica are up to ### Odoo Odoo ships its own e-commerce platform, and for external channels the picture is connector by connector. The Amazon Connector (Enterprise) [synchronises confirmed orders into Odoo and pushes available quantities back for merchant-fulfilled products](https://www.odoo.com/documentation/19.0/applications/sales/sales/amazon_connector/features.html), with a dedicated stock location tracking inventory in Amazon's fulfilment centres. Shopify and WooCommerce run through third-party connectors, which vary widely in what they carry and how often; we covered the detail in our [Shopify and WooCommerce integration guide](/blog/odoo-erp-australia-6/odoo-shopify-woocommerce-integration-australia-114). One thing worth saying plainly, because we checked the v19 Enterprise source code: none of this synchronisation involves AI. There is no AI module touching stock or channel sync in Odoo 19. The connectors are deterministic, which is what you want from plumbing. The agent layer that watches for drift is something you add on top, reading through Odoo's APIs under its own permissions. ### MYOB Acumatica MYOB's eCommerce Connector brings [Shopify and BigCommerce into MYOB Acumatica](https://www.myob.com/au/insight/post/ecommerce-for-myob-acumatica): product, price and inventory changes made in the ERP flow out to the storefront, and orders, customers and payments flow back in, with B2B features like customer-specific pricing supported. Globally, Acumatica offers [native connectors for Amazon, Shopify and BigCommerce](https://www.acumatica.com/cloud-erp-software/commerce-connectors/) with real-time inventory synchronisation. As always with this platform, global Acumatica features typically reach the ANZ product 6 to 9 months later, so confirm what your MYOB Acumatica build includes before planning around it. For what the platform's AI can and can't do today, see our [MYOB Acumatica AI guide](/blog/ai-erp-australia-8/myob-acumatica-ai-australia). On both platforms the honest summary is the same. The sync plumbing exists and works. The integrity checking layer, the thing that notices when reality and the storefront have parted ways, is not in the box. That's the agent's job. ## How to run a channel sync agent safely The [Australian Bureau of Statistics found 12% of Australian businesses used AI in 2024-25](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25), up from 1% two years earlier, and 22% of medium-sized businesses. Most of that adoption is still chatbots and content. Wiring an agent to your sales channels deserves more care: - **Start read-only.** Run the agent for a fortnight with no write path at all. You'll learn how much drift you actually have, and the reports build trust before anything can go wrong. - **Gate every write.** Price changes and stock corrections are drafted, never fired. A named person approves each one, and the approval is part of the audit trail. - **Give it its own credentials.** The agent reads through API keys scoped to exactly the data it needs, so you can see everything it touched and switch it off in one place. - **Log the misses too.** When the agent flags something that turns out to be fine, record it. False positives are how you tune the thresholds. We run agents on this pattern in production, for ourselves and for clients, and the governance is most of the work. The comparison logic is the easy part. Deciding who approves what, and proving afterwards what happened, is where an [AI agent build](/solutions/ai-agents) succeeds or fails. --- **Selling through Shopify, BigCommerce or a marketplace alongside Odoo or MYOB Acumatica?** Auboros builds drafts-first AI agents over both platforms from Brisbane, working with businesses across Queensland and Australia. We can audit how much drift your channels are carrying today and scope an agent to keep it caught. If your storefront and your ERP don't always agree, [**book a free consultation**](/appointment). We'll look at your channel setup together and tell you honestly whether an agent is worth it yet. --- # The AI Replenishment Agent: How It Drafts Purchase Orders in Odoo and MYOB Acumatica - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-replenishment-agent-erp-australia - Category: AI & ERP - Published: 2026-08-18 - Description: What an AI replenishment agent reads from your ERP, the purchase orders it drafts in Odoo and MYOB Acumatica, and why a buyer approves every one it proposes. Most wholesale and distribution businesses live with a strange contradiction: too much stock of some products and not enough of others, at the same time, in the same warehouse. The reorder report says one thing, the sales team says another, and the buyer spends Monday morning reconciling both in a spreadsheet. This is the job an AI replenishment agent is built for, and it's one of the capabilities Australian businesses ask us about most. An AI replenishment agent is software that reads sales velocity, stock levels, supplier lead times and minimum order quantities from your ERP, then drafts purchase recommendations for a human buyer to review. It doesn't place orders on its own. It does the analysis a good buyer would do if they had three spare hours per product line, and it presents the result as a draft with its reasoning attached. The appetite is real. [MYOB's ERP Trends research](https://www.myob.com/au/insight/post/erp-trends) found 78% of wholesale distribution businesses plan to use AI in their ERP, and the [Australian Bureau of Statistics reports](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25) that 12% of Australian businesses used AI in 2024-25, up from 1% two years earlier. Most of that adoption is still chatbots and document drafting. Replenishment is where it starts touching real money, which is exactly why the design matters. ## What an AI replenishment agent actually does The pattern has four verbs, and only three of them belong to the agent. - **It reads.** Sales orders by product and period, current and incoming stock, supplier lead times as quoted and as actually delivered, minimum order quantities, carton multiples, landed cost and margin. All of it already lives in your ERP. - **It flags.** Lines trending toward a stockout inside the supplier's lead time. Slow movers tying up cash. Lines where the quoted lead time and the last six receipts no longer agree. - **It drafts.** Purchase recommendations grouped by supplier, with quantities that respect MOQs and pack sizes, and a short note explaining each suggestion. - **A person approves.** The buyer reviews the draft, edits quantities, rejects lines, and only then does a request for quotation or purchase order go anywhere. That last step isn't a training-wheels phase to grow out of. It's the design. ## What Odoo and MYOB Acumatica already do without AI Here's the part most AI content skips: both platforms already ship serious replenishment logic, and none of it is AI. Odoo 19 handles this through [reordering rules](https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/reordering_rules.html): set a minimum and maximum per product, and Odoo either creates the purchase or manufacturing order automatically or lists the line on a replenishment report for a person to action. Its [just in time logic](https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/warehouses_storage/replenishment/just_in_time.html) schedules orders using forecasted stock and the combined lead times on the product. It's deterministic. We've been through the v19 Enterprise source code, and there is no AI in the replenishment path. The v20 roadmap is more AI-forward, but nothing agentic has shipped for purchasing yet. MYOB Acumatica, built on the Acumatica platform, goes further on the statistics. Its [replenishment engine](https://www.acumatica.com/cloud-erp-software/inventory-management/) supports reorder points, safety stock, seasonality factors and demand forecast models built on historical sales, and [Distribution Requirements Planning](https://www.acumatica.com/cloud-erp-software/distribution-management/distribution-requirements-planning-drp/) plans across locations. These are statistical models rather than machine learning, which is no criticism: they're predictable, explainable and cheap to run. For what the platform's actual AI features cover today, see our guide to [MYOB Acumatica's AI capabilities](/blog/ai-erp-australia-8/myob-acumatica-ai-australia). If you haven't configured these built-in tools yet, start there, not with an agent. An agent reasoning over wrong lead times and missing MOQs will draft confident nonsense. We covered the groundwork in our guides to [Odoo's purchasing module](/blog/odoo-erp-australia-6/odoo-purchasing-module-australia-purchase-orders-rfqs-and-what-you-can-automate-119) and [Odoo inventory management](/blog/odoo-erp-australia-6/odoo-inventory-management-australia-106). ## Where the agent adds judgement the rules can't A reordering rule evaluates one product at a time, against parameters someone typed in months ago. It works until the world drifts away from the parameters. The agent's job is noticing the drift. Rules can't tell you that a supplier's last four receipts averaged twelve days late, so the quoted lead time is fiction and the reorder point is too low. They can't weigh whether topping up a low-margin line is worth the freight. They won't spot that you're simultaneously out of stock in Brisbane and overstocked in Melbourne on the same SKU, where the right move is a transfer, not a purchase. And they can't read context, like the doubling of sales on three lines that might be a trend or might be one customer's one-off project. Here's what that looks like in practice. Monday, 6am, the agent runs against live ERP data with read-only access. By 7am the buyer has a draft in their inbox: fourteen lines need attention this week. Nine are routine top-ups, grouped into three supplier orders that respect each supplier's MOQ. Two are early orders because of that supplier with the drifting lead times, with the receipt history attached as evidence. Three are flagged as questions rather than orders, because sales velocity doubled last month and the agent can't tell whether that's repeatable, so it presents both order quantities and asks. The buyer approves nine, adjusts one, rejects one, and answers the three questions. Total elapsed time: about twenty minutes, most of it on the three lines that deserved human thought. > "The reorder point tells you one number went below another number. It can't tell you the supplier has been shipping late for three months, or that the margin on a line no longer covers the freight to restock it. That judgement layer is what the agent drafts, and it's exactly why a buyer still signs off on every order." > > **Bill Alvarez, Practice Manager, Auboros** ## Why a buyer approves every order Language models make errors. They misread a spreadsheet column, treat a spike as a trend, or hallucinate a pack size. On a chatbot that's an annoyance. On a purchase order it's a container of stock you didn't need, paid for with real cash and stored in real racking. The approval gate is what makes the agent safe to run at all, and in practice it means three things. The agent's access is read-only and scoped to the data a buyer could see anyway, never a shared super-user login. Everything it produces lands as a draft, and the ERP's own workflow handles release. Odoo Enterprise even ships an Approvals app that generates the RFQ from an approved purchase request, so the gate is native to the platform rather than bolted on. And every recommendation carries its reasoning and sources, so when the buyer disagrees, you can see why the agent got it wrong and fix the data or the prompt. This is the same drafts-first pattern we apply across [our AI agent work](/solutions/ai-agents): agents propose, humans approve, and everything is auditable. ## How to start without betting the warehouse Don't switch this on across your whole catalogue. Pick one category or one supplier group, ideally one with steady demand and a co-operative supplier. Check the data first: real lead times, current MOQs, correct costs. Then run the agent's recommendations alongside your existing process for a full ordering cycle and measure the gap between what it drafted and what the buyer actually ordered. Where they differ, work out which one was right. If the agent earns trust, widen the category coverage. If it doesn't, you've lost nothing except a few weeks of parallel running, and you've usually found data problems worth fixing anyway. For wholesale distributors starting from scratch, this pairs naturally with a platform foundation like the [MYOB Acumatica FastStart program](/blog/myob-acumatica-australia-7/myob-acumatica-wholesale-distribution-faststart-australia-103), which gets the underlying purchasing and inventory data structured properly in the first place. --- **Thinking about a replenishment agent for your warehouse?** We're a Brisbane-based ERP consultancy that implements Odoo and MYOB Acumatica across Queensland and beyond, and we run drafts-first AI agents over both platforms. If you want to know what a replenishment agent could draft from your own sales and supplier data, [**book a free consultation**](/appointment). We'll tell you plainly whether your data is ready for one. --- # Odoo for Exporters: How Australian Businesses Handle Multi-Currency Sales and GST-Free Invoices - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-exporters-australia - Category: Odoo ERP Australia - Published: 2026-08-18 - Description: What Odoo for exporters looks like in Australia: multi-currency invoicing, GST-free exports and the 60 day rule, incoterms and pro forma invoices explained. Selling overseas changes the shape of your admin. Quotes go out in US dollars, the ATO expects the goods gone within 60 days if you're not charging GST, and your freight forwarder keeps asking for documents your accounting file has never heard of. The scale of this is bigger than most people assume: the most recent ABS [Characteristics of Australian Exporters](https://www.abs.gov.au/statistics/economy/international-trade/characteristics-australian-exporters/latest-release) release counted 56,274 goods exporters, and well over half were small businesses. That release covers 2019-20, the last full census of the exporter population the ABS published, but the pattern it captured still holds. Most Australian exporters are small teams doing export admin on the side. This guide covers what Odoo does well for export sales, the settings that matter, and the jobs that stay with your customs broker no matter what software you run. ## Setting up Odoo for exporters: where to start Getting Odoo export-ready is mostly configuration, not custom development. Four pieces do the heavy lifting: - **Currencies and pricelists.** Activate the currencies you sell in and build a pricelist per market. Your US distributor sees USD prices on every quote without anyone converting figures on a calculator. - **A dedicated GST-free export tax.** Export sales still appear on your Business Activity Statement (BAS), they're reported as GST-free rather than left out. A separate 0% tax for exports keeps them visible and easy to reconcile. - **Default incoterms.** Odoo lets you set a [default incoterm](https://www.odoo.com/documentation/19.0/applications/finance/accounting/customer_invoices/incoterms.html) that fills itself in on every new invoice, so FOB or CIF terms stop depending on someone's memory. - **Delivery connections.** Carrier integrations and stock traceability are covered in our [Odoo inventory guide](/blog/odoo-erp-australia-6/odoo-inventory-management-australia-106), and everything there applies double when the carton is crossing a border. Why bother pulling this into one system? MYOB's [2025 ERP Trends research](https://www.myob.com/au/insight/post/erp-trends) found 45% of Australian decision makers say disconnected systems are limiting their growth. Exporters feel that pain earlier than most because a single order touches sales, the warehouse, a forwarder, an overseas bank and the BAS. ## Multi-currency sales without the spreadsheet Odoo's [multi-currency system](https://www.odoo.com/documentation/19.0/applications/finance/accounting/get_started/multi_currency.html) lets you set a currency per sales order or invoice, and the whole document follows it. You can hold bank accounts in foreign currencies, register payments in the currency they arrived in, and run reports on your foreign currency activity. The part that saves real time at month end: when the exchange rate moves between invoice and payment, Odoo posts the exchange difference to a dedicated journal automatically. Nobody calculates the gain or loss by hand. We've gone deeper on rates, revaluation and keeping the BAS in AUD in our [multi-currency accounting guide](/blog/odoo-erp-australia-6/odoo-multi-currency-accounting-australia). ## GST-free exports and the 60 day rule Exports are one of the main categories of [GST-free sales](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst/when-to-charge-gst-and-when-not-to/gst-free-sales), which means you don't charge GST on the sale but you can generally still claim credits on the costs of making it. The catch is timing. Under the [ATO's export rules](https://www.ato.gov.au/businesses-and-organisations/international-tax-for-business/australians-doing-business-overseas/exports-and-gst), goods need to leave Australia within 60 days of the earlier of receiving payment or issuing the invoice. Paid by instalments? The clock runs from the final one. If production or shipping delays will blow the window, you can ask the ATO for an extension through Online services for business, but you have to ask before assuming the sale stays GST-free. This is general information rather than tax advice, so check your specific arrangements with your adviser. > Most export problems we untangle aren't system problems, they're sequencing problems. The invoice went out in USD, the goods shipped six weeks later, and nobody checked whether the 60 day clock started at payment or invoice. Set the workflow up once so the paperwork follows the goods, and BAS time stops being an archaeology exercise. > > **Bill Alvarez, Practice Manager, Auboros** In Odoo terms: your quotation, invoice and delivery order live on the same record, so the dates you need to prove the timeline are already in one place. ## Incoterms and the paperwork your buyer expects Overseas buyers and their customs agents expect documents in a particular shape. Odoo covers the commercial side of that trail. Incoterms print on invoices once configured, and the [pro-forma invoice feature](https://www.odoo.com/documentation/19.0/applications/sales/sales/invoicing/proforma.html) lets you send a preliminary invoice straight from a quotation or sales order. Pro-forma invoices are commonly used for customs purposes before the commercial invoice exists, which is exactly the gap exporters need filled. One quirk worth knowing: Odoo won't send a pro-forma once a down payment invoice has gone out on that order. ## Where the broker takes over Some jobs stay outside your ERP, and it's better to know that up front. Export declarations to the Australian Border Force, certificates of origin under free trade agreements, and quarantine paperwork are typically prepared and lodged by your freight forwarder, customs broker or chamber of commerce. Odoo's job is to be the reliable source they work from: product weights, customs descriptions, values and dates that don't contradict each other. And if you import components to make what you export, the flow works in reverse too. Our guide to [landed costs and deferred GST](/blog/odoo-erp-australia-6/odoo-landed-costs-deferred-gst-australia) covers that side of the border. If you're weighing up whether Odoo fits your operation more broadly, our [Odoo services page](/solutions/odoo) explains how we scope and deliver implementations. --- **Exporting from Australia on Odoo, or planning to?** We're a Brisbane based Odoo Silver Partner and we set up multi-currency sales, GST-free invoicing and export workflows for Australian businesses selling offshore. If your export admin currently lives in spreadsheets bolted onto your accounting file, [**book a free consultation**](/appointment). We'll map what Odoo can take over and give you a straight answer on what it can't. --- # MYOB Acumatica Employee Onboarding: From Invitation to First Pay Run - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-employee-onboarding-australia - Category: MYOB Acumatica Australia - Published: 2026-08-18 - Description: How MYOB Acumatica employee onboarding works: invitations, TFN and bank details entered once, automatic payroll sync, and the Fair Work steps you still own. A new starter's first week generates more paperwork than most whole months. Tax file number (TFN) declaration, super choice, bank details, signed policies, the Fair Work Information Statement, and someone in payroll retyping all of it before the first pay run. It's a big part of why MYOB's [2025 Mid-Market Survey](https://www.myob.com/au/insight/post/mid-market-survey-results-2025) found 36% of Australian mid-sized businesses looking to upgrade their ERP, with 48% naming operational efficiency as the main driver. New starter admin is exactly the kind of repeating process that either runs itself or eats hours. MYOB Acumatica ships onboarding tools that move most of this into one flow: the business sends an invitation, the employee fills in their own details, and payroll receives them without rekeying. Here's how it works, and which compliance steps still belong to you. ## What MYOB Acumatica employee onboarding covers The workflow starts with an [onboarding invitation](https://enterprise-support.myob.com/awfm/sending-and-monitoring-an-onboarding-invitation). Whoever does the hiring enters the new starter's name and contact details, then sets their location, position, permission group and manager, their start date, and their pay, either from a pay level or a manually entered salary or rate. You can flag a probation end date to track, attach an agreement to prefill employment details, add a personal welcome message, and even include a one-off custom document for that person. The invitation goes out by email or SMS. Cost is the question everyone asks first, and the answer is unusually good. Per the [implementation guide](https://enterprise-support.myob.com/awfm/advanced-employee-onboarding-implementation-guide), Employee Onboarding is available to MYOB Acumatica Payroll customers at no additional subscription cost, provided you're on Payroll version 2022.1.2 or later and not already running the full Workforce Management product. If you do run full Workforce Management, onboarding is part of that package anyway. ## What your new employee sees The new starter clicks the link, creates an account and accepts the privacy policy. They land on a Job Details screen showing their start date, pay rate and manager, then work through the form entering their own personal, bank, tax and superannuation details. MYOB's [onboarding feature page](https://www.myob.com/au/erp-software/features/employee-onboarding-software) lists the compliance details captured, including TFN and Medicare levy declarations. The difference from the folder-of-PDFs approach is who does the typing. The employee enters their own BSB once, correctly, instead of writing it on a form for someone else to misread. ## How the details land in payroll Once the [payroll integration](https://enterprise-support.myob.com/adv/integrating-with-advanced-workforce-management) is set up, employees created through onboarding are matched with employee records in MYOB Acumatica Payroll automatically. The Pay Distribution tab picks up the bank account details the employee entered, and for Australian companies the Taxation tab is populated from their TFN declaration. Employee profiles let you apply the right payroll settings for the role at invitation time rather than fixing them later. > The first pay run is where onboarding shortcuts surface. When the TFN declaration and bank details come through the employee's own form and payroll just checks them instead of retyping them, day one paperwork stops being the reason pay week runs late. > > **Josh Craig, Director, Auboros** From there the same platform runs the rest of the employment lifecycle. Our guides to [timesheets and workforce management](/blog/myob-acumatica-australia-7/myob-acumatica-timesheets-australia) and [leave management](/blog/myob-acumatica-australia-7/myob-acumatica-leave-management-australia) cover what happens after week one. ## The compliance steps onboarding doesn't do for you Software collects the forms. It doesn't discharge your obligations, and three of them are worth pinning to the wall: - **The Fair Work Information Statement.** Every new employee must receive the [Fair Work Information Statement](https://www.fairwork.gov.au/employment-conditions/information-statements/fair-work-information-statement) before they start or as soon as possible afterwards, and casuals must also get the Casual Employment Information Statement. A document template in your onboarding flow is a tidy way to deliver it, but the obligation sits with you. - **The super choice form.** Eligible new employees need a [superannuation standard choice form](https://www.ato.gov.au/forms-and-instructions/superannuation-standard-choice-form) within 28 days of starting. - **Stapled super fund checks.** If a new employee doesn't choose a fund, you must request their [stapled super fund](https://www.ato.gov.au/businesses-and-organisations/super-for-employers/setting-up-super-for-your-business/offer-employees-a-choice-of-super-fund/stapled-super-funds-for-employers) details from the ATO before paying contributions anywhere else. Getting super details right at onboarding matters more now that Payday Super is live. Our [Payday Super checklist](/blog/myob-acumatica-australia-7/myob-acumatica-payday-super-australia) covers what to verify in payroll itself. ## Documents, probation and keeping track Beyond the initial form, the document tools let you distribute, sign and manage employee documentation, and templates can be sent to groups of employees by location and position, useful when a policy update needs to reach every store manager but not the warehouse. Probation dates set at invitation can be tracked through to their end date. And the Employees screen shows exactly where each new starter is up to, with filters for people who've been invited but haven't started the form and people partway through, plus a resend option for the invitation that vanished into a spam folder. If you're weighing up the platform more broadly, our [MYOB Acumatica services page](/solutions/myob) covers how we scope implementations, including payroll and workforce management. --- **Setting up MYOB Acumatica onboarding in Queensland?** We implement MYOB Acumatica payroll and workforce management for mid-market Australian businesses from our base in Brisbane. If your new starter process is still a folder of PDFs and a prayer, [**book a free consultation**](/appointment). We'll look at what you're running now and tell you whether the built-in onboarding covers it. --- # The AI Call Logging Agent: How Calls and Meetings Become CRM Records in Odoo and MYOB Acumatica - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-crm-call-logging-agent-erp-australia - Category: AI & ERP - Published: 2026-08-14 - Description: What an AI call logging agent does with sales calls and Teams meetings in Odoo and MYOB Acumatica, Australia's recording rules, and who approves each note. Sales managers rarely complain that the CRM holds too much information. The usual problem is the opposite. Calls happen, deals move, and the record shows a one-line note from three weeks ago that says "spoke to the customer, going well". When the rep leaves, the pipeline leaves with them. An AI call logging agent is a program that takes a recorded call or meeting, drafts the CRM record for it (a summary, the follow-up tasks, an update against the right opportunity) and waits for the person who was on the call to approve it before anything saves. The typing disappears. The responsibility doesn't. This is one of the most requested agent patterns we hear about from Australian businesses, and one of the easier ones to run safely, because everything it writes is a draft until someone confirms it. Here's how it works over Odoo and MYOB Acumatica, what each platform already ships, and the recording rules Australian businesses need to sort out before any of it runs. ## How an AI call logging agent works Four steps, the same shape as most of the [agent patterns we design](/solutions/ai-agents): - **Capture.** The transcript comes from wherever the conversation happened: the phone system, a Teams meeting recording, or a call recorded inside the ERP itself. - **Draft.** The agent reads the transcript and drafts the CRM entries: a summary note on the lead or opportunity, follow-up activities with dates, and any field changes it thinks are justified, like a pushed-out expected closing date. - **Confirm.** The rep sees the draft, fixes anything the agent misheard, and approves it. Nothing posts until they do. - **Audit.** The saved record links back to the transcript, so anyone reviewing the deal later can check what was actually said. A worked example. A rep finishes a 40-minute Teams demo with a wholesale customer. The agent drafts: a six-line summary against the opportunity, a task for the rep ("send revised pricing for the 500-unit tier by Friday"), a note that the customer asked twice about delivery timeframes to WA, and a suggested change to the expected close date, pushed out a month because the decision now needs board sign-off. The rep scans it, deletes the WA note (wrong customer, that was this morning's call, the agent matched the wrong opportunity), and approves the rest. Ninety seconds instead of fifteen minutes, and the mistake got caught at review rather than discovered in month three. That wrong-opportunity error is worth pausing on, because it's the most common failure in this pattern. Same contact at two companies. One customer with three open deals. A mobile number that matches nobody. A human filing their own notes makes the same mistake, but the agent makes it confidently and at volume, which is exactly why the confirm step is not optional. ## What Odoo 19 already ships More than most people expect. Everything in this section is shipped today in Odoo 19 Enterprise, checked against the current documentation and the v19 source code. The VoIP module became the [Phone app](https://www.odoo.com/documentation/19.0/applications/productivity/phone.html) in v19, and calls made through it land in the chatter of the [lead or opportunity](/blog/odoo-erp-australia-6/odoo-crm-australia-features-guide-104) they belong to. On top of that sits an AI layer: [Odoo 19's voice features](https://www.odoo.com/documentation/19.0/applications/productivity/ai/voice.html) transcribe recorded meetings, produce an editable AI summary, and then discard the audio once processing finishes. That last part is a sensible default you'd otherwise have to build yourself. Two details from the source code are worth knowing before you plan a rollout. Call transcription runs on a scheduled job that processes recordings one at a time, so summaries aren't instant. And the call summariser ships as a system agent that is switched off by default; an administrator has to enable it deliberately. We'd call both of those features rather than gaps. A transcription queue you can see, and an AI capability that needs an explicit decision to turn on, is what governance looks like in practice. What Odoo doesn't do natively is the full loop: reading the transcript and drafting follow-up activities and field updates against the right records. That's the layer we wire in with external agents over Odoo's API, scoped to the rep's own permissions, drafts only. Our [Odoo AI agents guide](/blog/ai-erp-australia-8/odoo-ai-agents-australia) covers how that wiring works. ## Where MYOB Acumatica sits A different shape. MYOB Acumatica has no native call transcription today. What the platform gives you is the plumbing around the conversation: [Acumatica's Microsoft Teams integration](https://www.acumatica.com/cloud-erp-software/customer-management/microsoft-teams-integration/) lets staff start a Teams chat or call from lead, contact and case screens and post activities to Teams channels, and the [2025 R2 release](https://www.acumatica.com/cloud-erp-software/2025-r2/) redesigned the activity form those call notes live on. MYOB's ANZ releases track behind global Acumatica by six to nine months, so always check which release a claim refers to. The honest limit sits in Acumatica's own [AI Studio FAQ for 2025 R2](https://community.acumatica.com/configuration-and-installation-114/faq-acumatica-ai-automation-with-ai-studio-2025-r2-32843): AI Studio is an experimental feature, its automation is user-initiated, and creating new documents, records or line details is not supported. So a meeting-to-CRM agent for MYOB Acumatica runs outside the platform, reads the Teams transcript, and drafts activities and notes through the API for a person to approve. It's the same drafts-first shape as [the sales order agent](/blog/ai-erp-australia-8/ai-sales-order-agent-erp-australia) that reads emailed purchase orders. We covered the platform's wider AI position, including what's shipped versus preview for ANZ, in [our MYOB Acumatica AI guide](/blog/ai-erp-australia-8/myob-acumatica-ai-australia). ## Recording the call is the legal question, not the technical one The technology is the easy half. Two Australian legal layers apply before any of it runs. First, recording itself. Call recording is governed by state and territory surveillance device laws, and they differ: some states allow a participant to record a conversation they're part of, others expect every party to be told. For a business dealing with customers across state lines, the safe design is to announce recording on every call and give people the chance to object. If your phone system or meeting tool records by default, the announcement is a configuration task in the phone system, and it takes minutes to set up. This isn't legal advice; check your own footprint with your adviser. Second, privacy. The Office of the Australian Information Commissioner's [guidance on commercially available AI products](https://www.oaic.gov.au/privacy/privacy-guidance-for-organisations-and-government-agencies/guidance-on-privacy-and-the-use-of-commercially-available-ai-products) deals directly with AI meeting transcription: collect only the personal information reasonably necessary for the job, destroy or de-identify anything the recorder caught that wasn't necessary (the personal chat before the meeting proper, someone's medical appointment), and get consent where sensitive information is involved. In practice that means retention rules for transcripts, role-scoped access so a transcript is no more visible than the deal it belongs to, and an exclusion list of calls the agent never touches. HR conversations are the obvious first entry. None of this is a reason to skip the pattern. It's a reason to set it up deliberately, and it's the part that most overseas-built note-taking tools leave for you to work out on your own. ## Why the drafts still need a person Transcription quality is good now, but the failure modes haven't gone away. Agents mishear numbers, and a quote logged at $15,000 instead of $50,000 will surface at the worst possible moment. They attribute commitments to the wrong side of the conversation, so the CRM says the customer agreed to a timeline the rep actually proposed. And they summarise with full confidence even when the audio was poor. > "The transcript isn't the point. The point is that your pipeline stops depending on whether the rep felt like typing on a Friday afternoon. The agent drafts, the rep checks and approves, and deal reviews stop being archaeology." > > **Josh Craig, Director, Auboros** The approval step costs each rep a minute or two per call. What it buys is a CRM where every record was confirmed by the person who was in the room. That's the difference between a pipeline you can trust and one you have to re-litigate every quarter. --- **Want call notes that write themselves, without writing fiction?** We design drafts-first agents over Odoo and MYOB Acumatica from Brisbane, with the consent, retention and permission settings sorted before anything records. If you'd like your calls and meetings landing in the CRM as reviewed records instead of memories, [**book a free consultation**](/appointment). We'll look at your phone and meeting setup and tell you what's realistic. --- # MYOB Acumatica Expense Claims: From Receipt Photo to Pay Run - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-expense-claims-australia - Category: MYOB Acumatica Australia - Published: 2026-08-14 - Description: How MYOB Acumatica expense claims work: mobile submission with receipt photos, manager approvals, payment through payroll, and the ATO reimbursement rules. Every business has an expense drawer. Fuel receipts, parking stubs, a Bunnings docket from three weeks ago, all waiting for someone to type them into something. [45% of Australian decision-makers say disconnected systems limit their growth](https://www.myob.com/au/insight/post/erp-trends), and the expense drawer is usually the most visible symptom staff ever see. MYOB Acumatica closes it with a claims workflow that starts with a phone camera and ends in the pay run. This guide covers how expense claims work in MYOB Acumatica Workforce Management, what managers see on the approval side, how payment happens, and the ATO rules that decide whether a payment is a reimbursement or something the tax office wants reported. ## Where MYOB Acumatica expense claims live MYOB Acumatica splits expenses into two streams, and knowing which one you are in saves confusion later. Employee out-of-pocket claims, the fuel and parking variety, run through the Workforce Management module. They are submitted by the employee, approved by a manager and paid through payroll, alongside the rosters and timesheets we covered in [our timesheets and workforce management guide](/blog/myob-acumatica-australia-7/myob-acumatica-timesheets-australia). Billable project costs are a different stream. Expenses that need to land against a job or contract for client billing belong in [project accounting](/blog/myob-acumatica-australia-7/myob-acumatica-project-accounting-australia-123), where they flow into work in progress and invoicing. This post covers the first stream. ## Submitting a claim: web and mobile Employees [submit expense claims](https://enterprise-support.myob.com/awfm/claiming-your-expenses) from the My Profile section of the web app or from the MYOB Advanced Team mobile app. A claim needs an expense type, the date, the amount and any notes, plus a supporting document. On mobile, the employee can attach a file or photograph the receipt with their camera on the spot. Claims then move through four statuses: Pending while they wait for a manager, Accepted or Rejected once actioned, and Paid once payroll has processed them. Employees can edit or cancel a claim while it is still Pending, and they get an email when the decision lands. That transparency alone removes most of the "did my claim go through?" conversations. ## Approving and managing the team's claims Managers action claims from the [Expense Claims screen](https://enterprise-support.myob.com/awfm/managing-your-team-s-expense-claims) on the web or from the mobile app, and an email notification with a link arrives whenever an employee submits one. On the web, pending claims can be filtered into one list and approved or declined in a couple of clicks. Declining a claim requires a reason, which the employee sees, so the feedback loop is built in. The mobile side is quicker again: swipe right to approve, swipe left to decline. Managers can also submit or edit claims on behalf of their employees, which covers the field worker whose phone died and the receipt that surfaces a week late. ## From approved claim to pay run Approved claims go to payroll to be paid, and the claim status flips to Paid once the pay run processes it. One system carries the claim from receipt photo to payment, with no export file in between. Because every claim keeps its receipt and its approval history attached, the paper trail your accountant asks for at year end is already sitting in the system rather than in a drawer. The ATO angle matters here. A reimbursement repays an actual, verified business expense, and the ATO [treats reimbursements differently from allowances](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/payg-withholding/payments-you-need-to-withhold-from/payments-to-employees/allowances-and-reimbursements). Allowances are paid regardless of what was spent, generally have PAYG withheld and are reported through Single Touch Payroll. Genuine reimbursements are generally not treated as wages, though fringe benefits tax can arise in some cases, so the classification is worth a conversation with your adviser. If your pay items need a tidy-up before that conversation, start with [our MYOB Acumatica payroll guide](/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97). ## Setup: expense types do the heavy lifting The workflow above only runs as well as its configuration. Expense types are [set up by the business](https://enterprise-support.myob.com/awfm/how-to-set-up-expense-types), and they are the choice the employee makes on every single claim. A short, specific list beats a long, clever one. Expense types work best when they mirror the way your pay items and expense accounts are already structured, and when the names match the words your staff actually use on site. Ten types that map cleanly will beat thirty that need a policy document to interpret, and payroll will spend far less time recoding what comes through. > Most expense problems are setup problems. If the expense types match the way the business actually spends money, approvals take seconds. If they force people to guess, every claim turns into a conversation. > > **Bill Alvarez, Practice Manager, Auboros** The adoption warning applies here too. [Fewer than 1 in 3 Australian businesses successfully adopt new software](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/), and an expense workflow nobody was shown in week one quietly loses to the drawer. Ten minutes in the site induction showing the camera workflow is the cheapest change management you will ever buy. **Ready to retire the expense drawer?** We implement and support [MYOB Acumatica](/solutions/myob) for mid-market businesses across Brisbane, Queensland and beyond, and expense claims are one of the fastest pieces to get right. If your claims still travel by spreadsheet and shoebox, [**book a free consultation**](/appointment). We will map the workflow to how your teams actually spend. --- # Odoo Expenses in Australia: Receipts, Approvals and Payroll Reimbursement - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-expenses-australia - Category: Odoo ERP Australia - Published: 2026-08-14 - Description: How the Odoo Expenses app handles receipt capture, approvals, payslip reimbursement and customer reinvoicing, plus the ATO rules employers need to know. Expense claims are rarely anyone's favourite job. The amounts are small, the receipts go missing, and finance spends month end chasing people for paperwork that should have taken thirty seconds on a phone. [45% of Australian decision-makers say disconnected systems limit their growth](https://www.myob.com/au/insight/post/erp-trends), and a standalone expense app that never talks to your accounting system is a textbook example. Odoo handles expenses inside the same platform that runs your [accounting and operations](/solutions/odoo), which changes the workflow more than you might expect. This guide covers how the [Odoo Expenses app](https://www.odoo.com/documentation/19.0/applications/finance/expenses.html) works in version 19, the three ways reimbursements reach employees, and the Australian tax rules worth understanding before you switch it on. ## What the Odoo Expenses app covers Odoo gives employees four ways to get an expense into the system: type it in manually, upload a receipt file, drag and drop a receipt onto the Expenses dashboard, or email it to a preconfigured address. The last two matter most in practice. An employee who photographs a receipt and emails it from the car park has done their admin for the day. Enterprise subscriptions also include receipt digitisation. Odoo scans the uploaded receipt and creates a draft expense record with the total and date filled in, using the same credit-based digitisation service that reads vendor bills. The employee checks the draft rather than typing from scratch, and each scan uses one credit. Behind the scenes, expense categories do the accounting work. Each category maps to an expense account and a tax setting, so an approved claim lands in the right place on the profit and loss without anyone in finance recoding it. ## From claim to approved report Individual expenses are grouped into an expense report and submitted for approval. A manager reviews the report, approves or refuses it, and accounting then posts the journal entries. The approval step is the control point: nothing hits the ledger until someone with authority has looked at it. That sequence sounds obvious, but it is exactly what a shoebox of receipts does not give you. Every claim in Odoo carries its receipt, its approver and its posting date, which makes audits and BAS reviews far less painful. ## Three ways to pay people back Once a report is approved and posted, [Odoo supports three reimbursement routes](https://www.odoo.com/documentation/19.0/applications/finance/expenses/reimburse.html): pay each report individually, pay multiple reports in one bulk payment, or add the amount to the employee's next payslip. The payslip route deserves attention. Odoo's Expenses in Payslips feature adds approved expense totals to the employee's regular pay, so there is one payment instead of two and no separate bank transfer to reconcile. Businesses paying reimbursements as bank payments instead will register them in accounting alongside the vendor payments we covered in [our Odoo accounts payable guide](/blog/odoo-erp-australia-6/odoo-accounts-payable-in-australia-vendor-bills-3-way-matching-and-aba-payments-128). > The whole game is capture at the moment of spend. A receipt photographed in the car park is thirty seconds of admin. The same receipt at month end is a mystery transaction, a follow-up email and a slower BAS. > > **Josh Craig, Director, Auboros** ## Charging expenses back to customers If you bill clients for travel, accommodation or materials, Odoo can [reinvoice expenses to customers](https://www.odoo.com/documentation/19.0/applications/finance/expenses/reinvoice_expenses.html) automatically. The employee selects the relevant sales order in the Customer to Reinvoice field when logging the expense. Once the report is approved and posted, the expense appears on that sales order, and the next invoice charges it to the customer. For consultants, engineers and trades businesses, this closes a real leak. Billable expenses that live in a spreadsheet have a habit of never reaching the invoice. ## The Australian rules: GST credits, allowances and reimbursements Two ATO rules shape how you should run expenses in any system, Odoo included. First, tax invoices. To claim a GST credit on a purchase of more than $82.50 including GST, you need a [valid tax invoice](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-taxes/gst/tax-invoices), the same threshold that applies to the purchase workflows in [our Odoo purchasing guide](/blog/odoo-erp-australia-6/odoo-purchasing-module-australia-purchase-orders-rfqs-and-what-you-can-automate-119). Because every Odoo expense carries its receipt as an attachment, the evidence for those credits is stored against the journal entry rather than in a drawer. Second, the ATO draws a firm line between [allowances and reimbursements](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/payg-withholding/payments-you-need-to-withhold-from/payments-to-employees/allowances-and-reimbursements). An allowance is paid regardless of what the employee actually spends, and generally has PAYG withheld and gets reported through Single Touch Payroll. A reimbursement repays an actual, verified business expense and is generally not treated as wages, though fringe benefits tax can apply in some situations, so check the detail with your adviser. Odoo Expenses is built for reimbursements. Allowances belong in payroll as pay items, and the GST side of both flows into the BAS setup we covered in [our Australian localisation guide](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98). ## Where it fits and where it doesn't Odoo Expenses earns its place when employees regularly spend their own money on fuel, tools, travel, parking or client meals. It is not the right tool for contractor invoices, which belong in accounts payable, and company credit card programs need their own design conversation before you assume claims are the answer. The honest caveat is adoption. [Fewer than 1 in 3 Australian businesses successfully adopt new software](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/), and expense tools live or die on whether capture is easier than the shoebox. If the phone camera workflow is not shown to every employee in week one, the shoebox wins. **Want expense claims that land in the right accounts without the chasing?** We implement and support Odoo for businesses across Brisbane, Queensland and the rest of Australia, and expense workflows are one of the quickest wins in most rollouts. If you want receipts, approvals and reimbursements running through one system, [**book a free consultation**](/appointment). We will tell you if your current setup is already close enough. --- # The AI Virtual CFO Agent: How It Works Over Odoo and MYOB Acumatica - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-virtual-cfo-agent-erp-australia - Category: AI & ERP - Published: 2026-08-13 - Description: What an AI virtual CFO agent reads from Odoo and MYOB Acumatica, the analysis it drafts for Australian owners, and the tax advice line it never crosses. Search for "virtual CFO" in Australia and you'll find two things: accounting firms offering fractional finance directors, and a growing pile of AI products borrowing the title. Both miss the version that matters most for a business already running an ERP. If your ledgers, debtors and stock live in Odoo or MYOB Acumatica, the most useful virtual CFO is not another subscription. It's an agent that reads the finance data you already have, every morning, and tells you what a finance director would notice. This is the capstone of the finance agent series we've been publishing: the [reconciliation agent](/blog/ai-erp-australia-8/ai-reconciliation-agent-erp-australia) keeps the data clean, the [credit management agent](/blog/ai-erp-australia-8/ai-credit-management-agent-erp-australia) watches the debtors, and the [month-end close agent](/blog/ai-erp-australia-8/ai-month-end-close-agent-erp-australia) gets the books locked on time. The virtual CFO agent sits on top of all three. It's also the easiest of the four to govern, because it doesn't post anything at all. ## What a virtual CFO agent actually is A virtual CFO agent is an AI agent with read-only access to the finance data in your ERP. On a schedule, or when you ask it a question, it reads cash balances, debtors, creditors, margins and upcoming commitments, then drafts plain-language analysis: what moved, why it matters, and what to ask about next. It makes no decisions, posts no entries and gives no tax advice. Every number in its output comes from a ledger record it can point to. That is a different thing from a human virtual CFO, the fractional finance director many Australian accounting firms provide. Those engagements bring judgement, industry experience and professional accountability that software does not have, and the agent doesn't replace them. It's the analyst layer underneath: it does the daily reading so the humans, internal or external, spend their limited hours on decisions rather than assembly. The gap it closes is mostly a size gap. [ABS figures](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25) show around 12% of Australian businesses used AI in 2024-25, against around 35% of large businesses. Large businesses also employ the analysts who read the numbers daily. Mid-market firms have the same data and almost none of the reading time. An agent doesn't fix strategy, but it does fix attention. ## What Odoo and MYOB Acumatica already tell you Before adding anything, be honest about the baseline, because both platforms already produce most of what a virtual CFO agent works from. Odoo 19 ships accounting dashboards and reporting out of the box, and its AI agents on the Enterprise plan operate inside the same [access rights](https://www.odoo.com/documentation/19.0/applications/general/users/access_rights.html) that govern every user. An agent given no task topics can only provide information, not change records, which for CFO-style work is exactly the setting you want. MYOB Acumatica has role-based dashboards, inquiries you can build without a developer, and feeds into Excel and BI tools. MYOB has shipped anomaly detection in the current ANZ release, and its AI Studio remains in preview, which we covered in detail in [our MYOB Acumatica AI post](/blog/ai-erp-australia-8/myob-acumatica-ai-australia). So the missing ingredient is rarely data. In [MYOB's ERP Trends research](https://www.myob.com/au/insight/post/erp-trends), 78% of wholesale distribution businesses said they plan to use AI in their ERP. Most of those businesses already own dashboards that nobody opens on a normal Tuesday. The problem worth solving is attention, not reporting. If nobody in your business reads the reports you already have, start there before you start here. ## What the agent layer adds With read-only access wired up through [our AI agent services](/solutions/ai-agents), the pattern we build has four jobs: - **A scheduled brief.** Monday morning: cash position, movement against last week, debtor and creditor totals, and the BAS, super and payroll obligations coming up. Business Activity Statement (BAS) dates come from a calendar, not from the model's memory. - **Exception narratives.** Days sales outstanding creeping up over six weeks, margin drifting on one product line, a customer ordering outside its usual pattern. Each flag links to the specific invoices or orders behind it. - **Answers to real questions.** "Can we afford the second warehouse lease from November?" becomes a scenario built on actual cash flow history, with every assumption stated so a human can disagree with it. - **Board and bank pack drafts.** Commentary drafted around statements the ERP produced. A person edits it, checks it, and puts their name on it. One rule sits under all four. The model writes prose around numbers the ERP produced; it never supplies a figure from its own memory. Large language models make things up when they're allowed to. The fix is not hoping they won't, it's a design where every number is fetched from the system, not generated by the model. ## A worked example: the Monday morning brief Here's the shape of a build we'd scope for a Queensland equipment importer on MYOB Acumatica. At 7am the agent signs in with its own read-only credentials, scoped to finance data only. It reads the bank balances, the aged receivables and payables, open purchase orders and the FX exposure on US dollar supplier invoices due this month. It drafts a 400-word brief: cash covers 9 weeks at current burn, three customers have drifted past their usual payment pattern, the USD payments due on the 28th are 11% larger than last month, and the quarterly BAS is due in a fortnight. The bookkeeper opens the brief at 8:30, clicks through two of the flagged figures to confirm they trace to the ledger, adds one line of context the agent couldn't know, and forwards it to the owner. Twenty minutes of reading replaced the half day it used to take to assemble the same picture, and no software made a single decision. That checking step isn't overhead. It's the design: the agent drafts, a person verifies before anything acts on it. > The owners we work with don't need another dashboard. They need someone to read the dashboards every morning and say: these two things moved, here's why they matter, and here's the question for your accountant. That's the job the agent does, and it never gets bored of doing it. > > **Bill Alvarez, Practice Manager, Auboros** ## The line it cannot cross: tax advice In Australia, providing tax agent services for a fee requires registration with the Tax Practitioners Board under the Tax Agent Services Act 2009. The [penalties for unregistered advice](https://www.tpb.gov.au/risks-using-unregistered-preparers) can reach $82,500 for individuals and $412,500 for companies. An AI agent is not a registered tax agent, and neither is your ERP consultancy. This isn't a footnote, it's a design constraint. A well-built virtual CFO agent produces management information: what moved, when obligations fall due, and which questions to take to your registered agent. We write that boundary into the agent's instructions, so instead of "you should restructure this as X", it drafts "the instalment position has changed, ask your accountant whether the PAYG variation still holds". Your accountant stays in the loop by design, and typically ends up better briefed than before. Privacy runs alongside. Finance records contain staff and customer personal information, so access needs to fit your obligations under the [Australian Privacy Principles](https://www.oaic.gov.au/privacy/australian-privacy-principles), which is another reason the agent gets scoped, read-only credentials rather than a database dump. ## Guardrails before you switch anything on The controls are the same ones we apply across every agent in [our governance approach](/blog/ai-erp-australia-8/ai-agent-governance-australia), with one simplification: this agent never writes. - **Its own read-only user.** Least-privilege access under its own named credentials, never a shared admin login, so the audit trail shows exactly what it read. - **Ledger-traceable numbers.** Every figure in every brief links back to the record it came from. If a number can't be traced, the brief doesn't ship. - **Stated limits.** No tax advice, assumptions listed, and "the data doesn't show this" as an approved answer. - **Sandbox first.** Run it against a test company for a few weeks and let your accountant mark its homework before anyone relies on it. Start it after the other finance agents, not before. An analysis agent reading messy books produces confident nonsense faster than any human could. Clean reconciliation and a disciplined close are the prerequisites that make the brief worth reading. **Thinking about a virtual CFO agent over your ERP?** Auboros designs and runs drafts-first AI agents over Odoo and MYOB Acumatica for businesses across Brisbane, Queensland and beyond, with the accounting background to know where the boundaries sit. If you want to know what your finance data could be telling you every Monday, [**book a free consultation**](/appointment). No obligation, and we'll tell you plainly if your books aren't ready for it yet. --- # Odoo Version Support in Australia: How Long Each Version Lasts and When to Plan Your Upgrade - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-version-support-australia - Category: Odoo ERP Australia - Published: 2026-08-13 - Description: Odoo version support explained: which versions are supported in 2026, when v17 support ends, and how Australian businesses should time the move to Odoo 20. Odoo supports its three most recent major versions, and a new major version arrives roughly once a year. That simple policy has a hard edge to it. When Odoo 20 is unveiled at Odoo Experience this September, Odoo 17 drops out of the supported window. If you're running v17 or anything older, the next few months are your chance to plan the move on your own schedule instead of someone else's. This post explains how Odoo version support works, which versions are supported right now, and how Australian businesses should time an upgrade around it. ## How Odoo version support works Odoo's policy is published in its [supported versions documentation](https://www.odoo.com/documentation/19.0/administration/supported_versions.html): the three most recent major versions receive support, bug fixing and security updates. Because a new major version ships each year, that works out to roughly three years of coverage per version. A few details matter in practice: - **The policy applies across hosting types.** Whether you run Odoo Online, Odoo.sh or on-premise, the same three-version window applies to major releases. - **Odoo Online also gets intermediary releases.** Databases on Odoo's own cloud receive smaller updates between major versions. Odoo.sh and on-premise installations only move between major versions. - **Support means more than bug fixes.** A supported version gets security patches and access to Odoo's helpdesk. An unsupported one gets neither. You can always upgrade from any version, however old. Support ending doesn't strand you; it just means the clock is running. ## Which Odoo versions are supported in 2026 As of August 2026, the supported versions are Odoo 17 (released late 2023), Odoo 18 (released October 2024) and Odoo 19 (released September 2025). The next change is already on the calendar. [Odoo Experience 2026](https://www.odoo.com/event/odoo-experience-2026-9099/page/oxp26-be-introduction) runs from 24 to 26 September in Brussels, and Odoo 20 will be unveiled there. On Odoo's usual pattern, once v20 ships, v17 leaves the supported window. That gives v17 users a clear deadline. It also gives v18 users a preview of their own: v18 becomes the oldest supported version from October, which puts it next in line when v21 arrives in 2027. We covered what's expected in the new release in our [Odoo v20 roadmap post](/blog/odoo-erp-australia-6/odoo-v20-australia-features-roadmap-115). ## What happens when your version leaves support Nothing breaks on day one. Your database keeps running exactly as it did. What changes is what sits behind it: - **No more bug fixes.** Issues you hit stay unfixed unless you pay someone to patch them locally. - **No more security updates.** For a system holding your customer data, invoices and payroll records, this is the risk that matters most. It compounds quietly the longer you wait. - **No helpdesk.** Odoo's support team works on supported versions. Odoo does offer a paid [extended support option](https://www.odoo.com/documentation/19.0/administration/standard_extended_support.html) for businesses that need more time on an older version. It's a bridge, not a destination, and it costs money that could otherwise fund the upgrade itself. The better news is that the upgrade itself is free for Enterprise subscribers. Odoo's [upgrade service](https://upgrade.odoo.com) converts your database to the new version at no charge, and you can request test upgrades before committing to anything. > The businesses that struggle are never the ones that upgrade a year late. They're the ones still on v14 with no test upgrade, no budget line and a server nobody wants to touch. Book the test upgrade early and the rest is routine. > > **Bill Alvarez, Practice Manager, Auboros** ## When Australian businesses should schedule the move Upgrade appetite is high across the market. MYOB's [Mid-Market Survey 2025](https://www.myob.com/au/insight/post/mid-market-survey-results-2025) found 36% of Australian mid-sized businesses looking to upgrade their ERP. The harder question is timing, and [Capterra's Australian research](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/) is a useful caution: fewer than 1 in 3 Australian businesses successfully adopt new software. Rushed cutovers are a big part of why. Our advice for timing an Odoo upgrade in Australia: - **Cut over just after a BAS quarter closes.** A fresh quarter on the new version keeps GST reporting clean and gives your bookkeeper one system per BAS, not two. - **Avoid the EOFY crunch.** June and July are the worst months to change systems. Finance teams are closing the year and finalising STP; they don't need a new interface as well. - **Start test upgrades 2 to 3 months out.** Standard databases upgrade quickly. Customisations, integrations and third-party modules are where the work hides, and each needs testing against the new version before production moves. - **Budget partner time for customisations, not for the upgrade itself.** The database conversion is free. Adapting custom code and retesting integrations is where a partner earns their keep. The process itself, including what the free upgrade service covers step by step, is in our guide to [how Odoo version upgrades work](/blog/odoo-erp-australia-6/odoo-version-upgrade-australia). If you'd rather have it handled end to end, that's what our [Odoo upgrade service](/solutions/odoo-upgrades) exists for, alongside our broader [Odoo consulting work](/solutions/odoo) for Australian businesses. **Running an Odoo version that's about to leave support?** We're a Brisbane-based Odoo Silver Partner, and version upgrades are routine work for us: test upgrade first, customisations adapted, production moved when the timing suits your BAS cycle. If you want to know exactly what an upgrade from your version involves, [**book a free consultation**](/appointment). Twenty minutes will tell you whether it's a quick job or a project. --- # MYOB Acumatica Leave Management: Requests, Approvals and Accruals from Roster to Payslip - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-leave-management-australia - Category: MYOB Acumatica Australia - Published: 2026-08-13 - Description: How MYOB Acumatica leave management works: requests, approvals, forecasted balances and accruals that flow to payroll, plus the Fair Work rules behind it. Leave looks like a small piece of a payroll system until you watch it go wrong. A request approved in a spreadsheet but never entered in payroll. A roster built around someone who booked holidays three weeks ago. An annual leave balance that doesn't match what the employee was told. Each one is a conversation nobody enjoys having. MYOB Acumatica handles leave across two connected pieces: Workforce Management, where requests, approvals and rosters live, and Payroll, where accruals, balances and payments are calculated. This post covers how MYOB Acumatica leave management works from request to payslip, and the Australian rules your setup has to respect. ## What MYOB Acumatica leave management covers The [Workforce Management leave module](https://enterprise-support.myob.com/awfm/managing-leave) handles the day-to-day workflow: - **Employees submit leave requests** from the mobile app or browser, and can check their current and forecasted balances before they ask. - **Managers review and approve requests** in one queue, with visibility of who else is off over the same dates via the leave calendar. - **Leave can be lodged on an employee's behalf**, which matters for field crews and anyone who doesn't sit at a desk. - **Leave types are controlled through entitlements**, so employees only see the categories that apply to them: annual, personal, long service and whatever else your setup defines. - **Approved leave flows through to rosters**, so the person building next week's shifts sees the absence before it becomes a gap. - **Blackout periods** let you close request windows around peak trading, stocktakes or go-lives, rather than rejecting requests one at a time. Australian public holidays are handled as part of the same setup, including processing holidays not worked, which keeps ordinary hours and holiday pay separated correctly. ## How leave flows through to payroll This is the part that separates an ERP from a standalone leave app. Approved leave in Workforce Management creates the matching pay items in [MYOB Acumatica Payroll](/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97), so what was approved is what gets paid, without re-keying. On the payroll side, annual leave accrues proportionally as part of each pay run. Balances appear on payslips and entitlement reports, and the same figures drive your total leave liability in the general ledger. Cashing out untaken leave is handled as its own payment type, kept distinct from leave actually taken, which is exactly how your accountant wants it recorded. Because leave carries cost information, approved requests also show up in job costing and business intelligence views. If you're running projects, that connects absence to the [job costing picture](/blog/myob-acumatica-australia-7/myob-acumatica-job-costing-australia) rather than leaving labour budgets to guess who's away. ## The Fair Work rules your setup has to respect Leave configuration isn't a blank canvas. The National Employment Standards set the floor, and the [Fair Work Ombudsman's annual leave guidance](https://www.fairwork.gov.au/leave/annual-leave) is specific: - **Four weeks of paid annual leave per year** for full-time and part-time employees, and five weeks for shiftworkers covered by an applicable award or agreement. - **Leave accrues on ordinary hours worked**, continuously, from the first day of employment. Probation doesn't delay it. - **Accrual continues during paid leave**, including annual and personal leave, but generally not during unpaid leave. - **Records must be kept for seven years** under Fair Work [record keeping rules](https://www.fairwork.gov.au/pay-and-wages/paying-wages/record-keeping-and-pay-slips), and leave records are on the list. Awards and agreements layer extra conditions on top: leave loading, cashing-out limits, notice requirements. The system can hold the rules, but someone has to configure them to match your instruments, and that configuration is worth checking at implementation rather than at audit. > Most leave disputes we see aren't about bad intent. They're about two systems disagreeing: the spreadsheet said one balance, payroll said another, and the employee planned a holiday on the wrong number. One system, one balance, and the argument disappears. > > **Josh Craig, Director, Auboros** ## Where leave fits in the bigger workforce picture Leave management completes a chain we've covered piece by piece: [timesheets and workforce management](/blog/myob-acumatica-australia-7/myob-acumatica-timesheets-australia) capture the hours, leave shapes who's available, and payroll pays it all under [Payday Super timing rules](/blog/myob-acumatica-australia-7/myob-acumatica-payday-super-australia) that now move super with every pay run. The value shows up when the pieces stop being separate products. MYOB's [ERP Trends research](https://www.myob.com/au/insight/post/erp-trends) found 45% of Australian decision-makers say disconnected systems limit their growth, and leave is one of the most commonly disconnected pieces: requested in one tool, rostered in another, paid from a third. Bringing it inside [MYOB Acumatica](/solutions/myob) removes two of those handoffs outright. **Sorting out leave management in MYOB Acumatica?** We implement and support MYOB Acumatica for businesses across Brisbane, Queensland and beyond, including Workforce Management setups where leave, rosters and payroll finally agree with each other. If your leave balances live in spreadsheets, or your current setup isn't matching your award, [**book a free consultation**](/appointment). We'll tell you what a clean setup looks like for your team. --- # The AI Sales Order Agent: How Emailed Purchase Orders Become Draft Orders in Odoo and MYOB Acumatica - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-sales-order-agent-erp-australia - Category: AI & ERP - Published: 2026-08-11 - Description: What an AI sales order agent does with emailed PDF purchase orders in Odoo and MYOB Acumatica, why a human approves every order, and how to start safely. Every wholesale distributor and manufacturer we talk to has the same inbox. Customer purchase orders arrive as PDF attachments, sometimes as a photo of a printed page, sometimes as a spreadsheet nobody asked for. Someone on the sales desk retypes each one into the ERP, line by line, and the first data entry error of the day is usually waiting in row three. An AI sales order agent removes the retyping without removing the judgement. The agent reads the inbound purchase order, extracts the customer, products, quantities and prices, matches them against your ERP's live records, and drafts a sales order. A person reviews the draft and confirms it. The agent never posts an order on its own. That last sentence is the whole design, and it's how we build this pattern at Auboros through our [AI agent services](/solutions/ai-agents). The demand is real. In MYOB's [ERP Trends research](https://www.myob.com/au/insight/post/erp-trends), 78% of wholesale distribution businesses said they plan to bring AI into their ERP. Meanwhile the [Australian Bureau of Statistics](https://www.abs.gov.au/media-centre/media-releases/business-use-artificial-intelligence-rise) reports about 12% of Australian businesses were using AI as of the latest survey, rising to around 35% of large businesses. The gap between intent and adoption is exactly where order intake sits: it's high volume, repetitive, and the cost of an error is visible on the loading dock within days. ## What an AI sales order agent does An AI sales order agent in an ERP context is software that watches an intake channel, reads whatever arrives, and turns it into a draft transaction a person can approve. In practice it has five jobs. - **Watch the intake channel.** Usually a dedicated email address or shared inbox where customers already send orders. Nothing about the customer's habits has to change. - **Read the document.** PDFs, scans, spreadsheets and photos all carry the same information in wildly different layouts. The model's job is extraction: customer, purchase order number, delivery address, line items, quantities, prices, dates and any free-text instructions. - **Match against ERP records.** Extracted text is only useful once it's tied to your actual customer record, your product codes and your price list. The customer writes their part number; the agent has to find yours. - **Validate.** Does the price match the customer's agreed pricing? Is the unit of measure sensible? Has this PO number been seen before? Is the customer on credit hold? Our post on [AI credit management agents](/blog/ai-erp-australia-8/ai-credit-management-agent-erp-australia) covers that last check in detail. - **Draft and wait.** The agent creates a sales order in draft, attaches the source document, writes a note about anything it wasn't sure of, and stops. A person approves, edits or rejects. Everything before the last step is mechanical. The last step is the control, and it stays human. ## What Odoo gives you today Odoo 19 ships [document digitisation](https://www.odoo.com/documentation/19.0/applications/finance/accounting/vendor_bills/invoice_digitization.html) as a native, working feature: upload a document or email it to a journal alias and Odoo's OCR and AI create a draft record with the fields filled in. That's shipped today, and it runs on prepaid IAP credits, roughly one credit per document. Here's the honest catch: it's built for the purchasing side. The documented targets are vendor bills, refunds and, with a settings change, customer invoices. There is no native switch that turns an emailed customer purchase order into a draft sales order. The intake pattern Odoo proves on vendor bills, an email alias feeding drafts into a journal, is exactly the pattern you want on the sales side, but getting it there means either a third-party module from the Odoo app store or an agent built against Odoo's API. We build the agent version, with the model reading the PO and writing a draft order through role-scoped credentials. Odoo's own v19 AI agents are also worth knowing about here, because they operate within the signed-in user's access rights, a design we unpacked in our guide to [AI agents in Odoo](/blog/ai-erp-australia-8/odoo-ai-agents-australia). ## What MYOB Acumatica gives you today On the Acumatica platform the shipped piece is again on the payables side: AP document recognition reads supplier invoices and drafts bills, and it has been in the product for years. The newer piece is AI Studio, which arrived with Acumatica 2025 R2 as an experimental feature. It connects the ERP to large language models and automates field-level updates inside documents. Read Acumatica's own [AI Studio FAQ](https://community.acumatica.com/configuration-and-installation-114/faq-acumatica-ai-automation-with-ai-studio-2025-r2-32843) closely, though: in 2025 R2 it cannot create new documents, records or line details. It can update fields on a sales order screen; it cannot create the order. Two practical consequences for Australian businesses. First, the global-to-ANZ release lag applies, typically 6 to 9 months, so what Acumatica announces globally and what's in your MYOB Acumatica instance are usually different versions. We track what's shipped locally in our review of [MYOB Acumatica's AI features](/blog/ai-erp-australia-8/myob-acumatica-ai-australia). Second, an order intake agent for MYOB Acumatica today is an integration build: the agent reads the PO, then creates a draft or on-hold sales order through the REST API, and your team releases it. That's not a limitation to apologise for. It's the same drafts-first shape we'd recommend even if a native feature existed. ## A worked example: from inbox to approved order Tuesday, 7:40am, at a fictional but familiar Queensland distributor. Twenty-eight purchase orders arrived overnight to orders@company address the agent watches. By 8am the agent has processed all of them. Twenty-three were clean: every line matched a product record, prices agreed with each customer's price list, and the agent drafted each sales order with the PDF attached. Five got flagged. On one, the customer ordered "6 x FLX-240" and the agent matched the product but noticed the customer's last eight orders were in cartons of 24, so a quantity of 6 might mean 6 cartons. It drafted the order at 6 units and wrote a note recommending someone confirm. On another, line 12 used a customer part number with no cross-reference in the system, so the agent left the line unmatched and said so. One PO number had been seen three days earlier, a likely duplicate. Nothing was confirmed, nothing was reserved, nothing hit the warehouse. At 8:30 the sales coordinator opens the draft queue, approves the clean ones in a few minutes, rings the customer about the carton question, adds the missing cross-reference, and deletes the duplicate. Every confirmed order was confirmed by her. > Nobody buys this because the agent types faster than a person. They buy it because the sales desk stops retyping the twenty-three clean orders and spends the morning on the five that needed a decision. > > **Josh Craig, Director, Auboros** ## Where it goes wrong, and the guardrails that catch it Language models make errors, and order intake has sharp edges. The recurring failure modes are worth naming: customer part numbers that don't map to your SKUs, unit-of-measure confusion between eaches and cartons, superseded or contract pricing the model can't know about, duplicate POs sent by email and portal, free-text instructions like "part shipment OK" that never make it onto the order, and occasionally an extracted line that isn't on the document at all, because models can hallucinate plausible text. The guardrails are the same ones we apply across every agent pattern, and they're covered in depth in our [AI agent governance guide](/blog/ai-erp-australia-8/ai-agent-governance-australia). Drafts-first, always: no agent-confirmed orders. Match, don't trust: extracted values only enter the order once they've been tied to real ERP master data, so a hallucinated product can't survive matching. Confidence routing: anything below a threshold goes to a person with the reason stated. Duplicate checks on customer PO numbers. A full audit trail from source PDF to draft to approver. And role-scoped permissions, so the agent holds the access of a sales clerk, never an administrator. There's a privacy job too. Purchase orders carry personal information: names, direct phone numbers, delivery addresses. Sending them to an AI model makes the [Australian Privacy Principles](https://www.oaic.gov.au/privacy/australian-privacy-principles) part of your design conversation: where the model processes data, what's retained, and what your privacy policy says about it. ## Where to start Data hygiene first, because matching is only as good as what it matches against. Tidy product codes, build the customer part number cross-reference for your biggest accounts, and confirm price lists in the ERP reflect what you've agreed. Then start narrow: one intake inbox, your top ten customers by order volume, running in a sandbox against copied data before it touches production. Measure minutes per order and error rate for a fortnight before and after. A drafts-only pilot at this scope is a matter of weeks, not months, and the first fortnight is mostly tuning matching rules rather than anything exotic. **Drowning in emailed purchase orders?** Auboros designs drafts-first order intake agents for Odoo and MYOB Acumatica from Brisbane, working with businesses across Queensland and beyond, and order drafting is the first pattern we usually build because the payback is quick and the risk is controlled. [**Book a free consultation**](/appointment) and we'll look at your order intake together, with no obligation either way. --- # MYOB Acumatica Timesheets and Workforce Management: From Roster to Pay Run - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-timesheets-australia - Category: MYOB Acumatica Australia - Published: 2026-08-11 - Description: How MYOB Acumatica timesheets work from clock-in to pay run: workforce management, approvals, job costing links and Fair Work record keeping in Australia. Payroll errors rarely start in payroll. They start upstream, where hours get written on paper, typed into a spreadsheet, then retyped into the pay run. Every handoff adds a chance to get it wrong, and disconnected tools carry a measurable cost: [45% of Australian decision-makers say disconnected systems limit their growth](https://www.myob.com/au/insight/post/erp-trends). MYOB Acumatica timesheets close that gap by capturing time once and letting payroll, project costing and compliance all read from the same record. Here is how the pieces work, and how to tell how much of it you need. ## Where time gets captured in MYOB Acumatica There are two layers. The core system includes [time and expense management](https://enterprisesupport.myob.com/knowledge/help-with-time-and-expenses): employees record time cards and expense claims inside the ERP, with approval steps before anything posts. For businesses that bill time or track it against jobs, this is often the natural starting point. The second layer is [MYOB Acumatica Workforce Management](https://enterprise-support.myob.com/awfm), a companion module built for shift-based teams. It covers rostering, timesheets, onboarding, leave management and compliance reporting, with clock-in and clock-out policies that record who was on site and when. Employees use the mobile app to check rosters, swap shifts, request leave, view payslips and clock in and out. Neither layer locks you in. Payroll can also [import timesheets from external systems](https://enterprise-support.myob.com/adv/importing-timesheets), so a field crew on a third-party time tool still lands in the same pay run. ## How MYOB Acumatica timesheets get into payroll The point of capturing time inside the platform is what happens next: nothing gets retyped. When Workforce Management is integrated with payroll, employees created in one are matched automatically in the other, and approved timesheet data flows into the pay run, where pay items are created or updated from the hours themselves. Clock-in and clock-out data feeds the timesheet approval screen, so a manager approves what the device recorded, not what memory reconstructed at the end of the week. That approval step is where control lives. Hours that look wrong get queried before the pay run, not after payday. The stakes on timing have risen too: since [Payday Super went live on 1 July 2026](/blog/myob-acumatica-australia-7/myob-acumatica-payday-super-australia), super follows each pay day rather than each quarter, so hours need to be right the first time, not corrected at reconciliation. ## Time that feeds job costing, not just payroll For services and construction businesses, hours are cost data as much as pay data. Time entered against a project flows into [job costing](/blog/myob-acumatica-australia-7/myob-acumatica-job-costing-australia), so labour appears on the job while the work is happening rather than after month end. [Project accounting](/blog/myob-acumatica-australia-7/myob-acumatica-project-accounting-australia-123) splits billable from non-billable time and carries approved hours through to client billing and WIP, which is the difference between knowing a job made money and discovering it did not. [Professional services firms](/blog/myob-acumatica-australia-7/myob-acumatica-for-professional-services-firms-in-australia-88) run this loop hardest: utilisation, recoverability and margin all start from the same timesheet entry. ## Fair Work record keeping: the floor you have to clear Time records in Australia are not optional paperwork. Under [Fair Work record keeping rules](https://www.fairwork.gov.au/pay-and-wages/paying-wages/record-keeping), time and wage records must be kept for 7 years, must be accurate, legible and in English, and cannot be altered except to correct an error, with the correction itself documented. Employees can ask to see their records, and a Fair Work Inspector can inspect them at any time. Digital timesheets clear this bar comfortably, and usually better than paper: every entry, edit and approval carries a timestamp and a user, which is the audit trail an inspector wants to see. The risk sits with the spreadsheet in between, where numbers change without history. ## Time cards or the full Workforce Management module? An honest sizing guide. If your team is salaried or office based and the goal is project costing and billable time, the core time and expense features may be all you need. If you roster shifts, employ casuals, pay by the hour or need to prove who was on site, Workforce Management earns its keep: rosters, clock-in policies and leave sit in one place and payroll reads straight from it. Adoption is the real risk either way. Fewer than [1 in 3 Australian businesses adopt new software successfully](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/), and time capture fails first when the tool does not match how people work. Rolling out clock-in policies to a team that has never used them is a change project, not a setting. > "The question we ask is where the hours are born. If time starts on paper and gets retyped twice, no payroll system will fix the errors that arrive with it. Capture it once, at the source, and everything downstream gets easier." > **Bill Alvarez, Practice Manager, Auboros** Either way, the platform grows in the same direction. Start with time cards against projects, add Workforce Management when headcount or roster complexity demands it, and [our MYOB Acumatica services](/solutions/myob) cover the configuration at both ends. **Still retyping hours between systems?** Auboros implements and supports MYOB Acumatica from Brisbane, working with services, construction and distribution businesses across Queensland and beyond. If timesheets, payroll and job costing live in three different places today, [**book a free consultation**](/appointment). We will map the shortest path to capturing time once. --- # Odoo Landed Costs and Deferred GST: The Setup Guide for Australian Importers and Exporters - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-landed-costs-deferred-gst-australia - Category: Odoo ERP Australia - Published: 2026-08-11 - Description: How Odoo landed costs, the deferred GST scheme and multi-currency work for Australian importers and exporters, plus the settings that keep BAS accurate. Bringing goods in from overseas, or selling them out, adds a layer to every part of your accounting. Purchase orders land in foreign currencies, freight and customs charges arrive weeks after the stock does, GST behaves differently at the border than it does at the till, and the BAS has to reconcile all of it. Plenty of Australian importers run this on spreadsheets sitting beside their accounting file, which is exactly the kind of disconnection [45% of Australian decision-makers say limits their growth](https://www.myob.com/au/insight/post/erp-trends). Odoo handles the full loop in one system: the purchase in the supplier's currency, the landed costs that build your true product cost, the GST treatment on both sides of the border, and the BAS that reports it. Here is how the pieces fit for Australian importers and exporters, and the settings that decide whether the numbers can be trusted. ## What importing looks like inside Odoo An import starts as a normal purchase order, raised in the supplier's currency. [Odoo's purchasing module](/blog/odoo-erp-australia-6/odoo-purchasing-module-australia-purchase-orders-rfqs-and-what-you-can-automate-119) handles the RFQ, the confirmation and the receipt when the container finally arrives. Because the order sits in USD, EUR or RMB, [multi-currency accounting](/blog/odoo-erp-australia-6/odoo-multi-currency-accounting-australia) does the conversion work: exchange rates update automatically, and the difference between the rate on invoice day and the rate on payment day posts as a currency gain or loss without manual journals. The part spreadsheets get wrong is what happens between those steps. Stock that has left the supplier but not cleared customs, deposits paid months ahead, and freight invoices from a different vendor than the goods all need a home in the ledger. Odoo gives each one a place, which is what keeps your stock valuation and your BAS from drifting apart. ## How Odoo landed costs work for Australian importers The invoice price of imported stock is rarely its real cost. Sea freight, customs duty, insurance, port and handling charges all arrive on top, and if they are expensed straight to the profit and loss, your margins by product are fiction. [Odoo's landed costs feature](https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/product_management/inventory_valuation/integrating_landed_costs.html) takes those extra invoices and allocates them across the products on a receipt, by value, quantity, weight or volume, so inventory valuation reflects what the stock cost to get onto the shelf. Two conditions matter for Australian businesses. First, landed costs only apply under FIFO or average costing with automated inventory valuation turned on, so the costing method decision comes before anything else. Second, GST does not belong in landed costs. If you are registered and can claim the import GST back as a credit, it is not a cost of the goods, and building it into valuation overstates your stock. Duty and freight go in; claimable GST stays out. ## Deferred GST: the cash flow change most importers miss By default, [GST on taxable imports is payable at the border](https://www.abf.gov.au/importing-exporting-and-manufacturing/importing/cost-of-importing-goods/gst-and-other-taxes) before goods are released, calculated on the customs value plus duty, transport and insurance. For a business bringing in a few containers a month, that is real money leaving the account weeks before the stock earns anything. The [ATO's deferred GST scheme](https://ato.gov.au/deferredGSTscheme) moves that payment off the wharf and onto your BAS. Approved importers pay nothing at the border. The deferred amount appears on the monthly BAS at label 7A and is claimed back as a credit at label 1B on the same form, so for most fully creditable imports the two cancel out and the GST becomes a reporting line instead of a cash payment. The conditions: you must lodge your BAS monthly rather than quarterly, and lodge and pay electronically, which is the main adjustment for businesses used to quarterly cycles. > "Deferred GST is the first thing we check when an importer moves onto Odoo. Most are eligible, half have never heard of it, and the switch to a monthly BAS pays for itself in cash flow before the implementation is finished." > **Josh Craig, Director, Auboros** Inside Odoo, the setup is a monthly tax period plus correct tax mapping for import GST. The ATO adds your deferred total to the BAS it issues, so your job in the system is to record the credit side against the right tax grid, and [Odoo's Australian localisation](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98) builds the BAS from those grids. Mapped once, reported every month. ## Exports: GST-free, but only inside the 60 day window Sales of goods shipped overseas are [GST-free under ATO rules](https://www.ato.gov.au/businesses-and-organisations/international-tax-for-business/australians-doing-business-overseas/exports-and-gst), provided the goods leave Australia within 60 days of the earlier of payment or invoice. Miss the window without an approved extension and the ATO can treat the sale as taxable. You also need documentary evidence that the goods left the country; without it, GST-free treatment is not safe even if the container sailed. In Odoo that means two things. Export invoices get coded with a GST-free tax rather than the standard 10 per cent, so they report correctly as GST-free sales on the BAS. And because export customers usually pay in their own currency, the invoice, the payment and any gain or loss run through the same multi-currency engine as your imports. Attach the bill of lading or export declaration to the invoice record and the evidence lives where an auditor will look for it. ## The setup that decides whether the numbers hold Most import and export problems we see are configuration, not software. The common ones: landed costs enabled while products still run standard costing, so allocations never reach valuation. Import GST paid through the customs broker and then keyed again from a supplier bill, doubling the credit. Export invoices left on the default 10 per cent tax. And exchange rates updating daily while [bank feeds](/blog/odoo-erp-australia-6/odoo-bank-feeds-australia) post at the bank's actual rate, leaving small differences nobody reconciles. Fewer than [1 in 3 Australian businesses adopt new software successfully](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/), and trade-heavy setups fail on exactly these details. None of this is hard to get right at implementation time. It is expensive to fix two BAS cycles later. If your business imports, exports or both, [our Odoo services](/solutions/odoo) cover the trade configuration end to end: costing method, deferred GST mapping, export tax codes and the multi-currency setup underneath them. **Importing or exporting on Odoo? Get the GST and costing setup right first.** Auboros is a Brisbane based Odoo Silver Partner working with importers and distributors across Queensland and Australia. If you want landed costs, deferred GST and the BAS to reconcile without side spreadsheets, [**book a free consultation**](/appointment). A short conversation before you configure is cheaper than a correction after you lodge. --- # The AI Month-End Close Agent: How It Works Inside Odoo and MYOB Acumatica - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-month-end-close-agent-erp-australia - Category: AI & ERP - Published: 2026-08-10 - Description: What an AI month-end close agent does inside Odoo and MYOB Acumatica: task chasing, draft accruals and variance notes, with a human approving every entry. Month-end close runs on a checklist, and the checklist runs on chasing. Someone confirms the bank accounts reconcile, the accruals are booked and the draft entries are posted or cancelled, and then someone explains to the owner why freight costs jumped. Most of that work is coordination and first-draft writing, not judgement. That is exactly the work an AI agent can carry. An AI month-end close agent is software that reads your ERP during the close, tracks which closing tasks are done and which are stuck, drafts the routine outputs (accrual journals, exception lists, plain-language variance notes) and hands every one of them to a person for approval before anything posts. It does not close the books on its own. Nothing should reach the ledger without a human saying yes, and in our view nothing ever should. This is the third post in our finance agent series, following the [reconciliation agent](/blog/ai-erp-australia-8/ai-reconciliation-agent-erp-australia) and the [credit management agent](/blog/ai-erp-australia-8/ai-credit-management-agent-erp-australia). The pattern is the same each time: the agent reads, drafts and flags, and a person approves. ## What an AI month-end close agent actually does Four jobs, in rough order of value: - **Task tracking and chasing.** The agent reads the close checklist against live ERP data. Bank reconciliation finished? Draft invoices still sitting unposted? Stocktake adjustment booked? Where a task is waiting on a person, it asks that person, with the context attached, rather than letting the item sit until someone notices on day five. - **Exception surfacing.** It scans for the things that derail a close late: unmatched bank lines, a vendor bill that looks like a duplicate, a margin swing on one product line, an intercompany balance that does not agree. - **Draft journals.** Recurring accruals, prepayment releases and estimate-based entries get drafted with their workings attached. Drafted, not posted. - **Variance narratives.** It compares the month's profit and loss to the prior period and budget, then drafts the "why" commentary in plain English for a human to check and edit. The common thread is the verb list we use in every post in this series: the agent reads, drafts, flags and waits. ## What Odoo and MYOB Acumatica already do without AI Before you add an agent, be honest about the baseline, because both platforms ship real closing structure that plenty of businesses have never switched on. Odoo 19 has a proper closing workflow in Accounting: [lock dates](https://www.odoo.com/documentation/19.0/applications/finance/accounting/reporting/year_end.html) stop journal entries being created or changed on or before a chosen date, with any exception logged against the company record, and the closing process runs through validation checks (bank reconciliation complete, no draft entries, deferred entries set correctly, overdue receivables reviewed) that show as passed, to review or anomaly. Acumatica, the platform underneath MYOB Acumatica, [closes financial periods](https://help.acumatica.com/Help?ScreenId=ShowWiki&pageid=29BDF0D1-B6DA-4C73-8C85-F6BF48B950D9) in the general ledger and subledgers so nothing posts into a closed period. If your team is not using lock dates or period close today, start there. It is free and it fixes more than software should. On the AI side, the platforms are further apart than the marketing suggests. Odoo 19's AI agents run inside the signed-in user's access rights, and the standard assistant cannot create or alter records, which is the right default for finance work. The current MYOB Acumatica release for Australia and New Zealand includes anomaly detection for production variances, AI Studio is in technology preview, and the broader agent tooling is roadmap, with global Acumatica releases typically reaching the ANZ product 6 to 9 months later. Neither platform ships a month-end close agent natively today. The agent that chases tasks and drafts commentary is an external layer working over the ERP's APIs under its own permissions, which is how we build them. ## A worked example: day three of the close A Queensland wholesale distributor runs a monthly management close and a quarterly Business Activity Statement (BAS). On the morning of day three, the agent has been through the ERP overnight and the financial controller opens a queue, not a blank screen: - The close checklist shows 14 tasks, 9 complete. One is blocked because a supplier bill for July freight has not arrived, so the agent has drafted an accrual of $8,400 from the carrier's rate card and July despatch volumes, labelled as an estimate with the workings attached. - The stocktake adjustment is still with the warehouse manager, so the agent has messaged him directly with the two unresolved count sheets rather than waiting for the controller to chase. - Three bank lines have sat unmatched for more than three days and are routed to the reconciliation exception queue. One vendor bill is flagged as a possible duplicate. - A draft variance note explains the 1.8 point drop in gross margin, built from ledger figures: a fuel levy increase from one carrier and a one-off clearance of slow stock. The controller approves the accrual, rejects the duplicate flag because the second bill is a legitimate split delivery, rewrites one sentence of the variance note, and posts only what she approved. The agent did the chasing and the typing. She made every decision, and the audit trail shows exactly that. > "The unglamorous part is the win. Nobody's close is late because variance analysis is hard. It's late because task eleven sat with someone on leave and nobody noticed until day five. An agent that watches the checklist and asks the right person the right question a day earlier pays for itself before it drafts a single journal." > > **Bill Alvarez, Practice Manager, Auboros** ## Variance narratives and the hallucination problem The most requested output in this pattern is also the riskiest one. Large language models are confident writers, and if you let one freestyle an explanation for a cost movement it will produce something plausible whether or not it is true. We treat variance commentary as a drafting job with hard rules: every figure in the narrative comes from a ledger query, not from the model's own text; every claimed driver links back to the journal lines or documents behind it; the output is labelled a draft; and a person who knows the business signs it off before it goes anywhere near a board pack. The model writes prose around verified numbers. It never supplies the numbers. If you run MYOB Acumatica, the [reporting and dashboards layer](/blog/myob-acumatica-australia-7/myob-acumatica-reporting-dashboards-australia) is where those verified numbers should come from, and it is worth getting that structure right before pointing an agent at it. ## The BAS connection: why close discipline matters more in Australia A BAS is only as good as the month-end closes underneath it. Most businesses with GST turnover under $20 million lodge quarterly, with [due dates on 28 October, 28 February, 28 April and 28 July](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas/due-dates-for-lodging-and-paying-your-bas), and larger businesses lodge monthly by the 21st. If each month inside the quarter closes clean, with GST coding exceptions surfaced and fixed in the month they occur, the BAS becomes an output rather than an archaeology project. That is a distinctly Australian reason to care about close discipline, and it is one an agent supports well: coding exceptions are exactly the kind of pattern-scanning work that suits software, while the decision on how to treat them stays with your accountant. Adoption is moving quickly enough that this is no longer an early-adopter conversation. The Australian Bureau of Statistics reports that [12% of Australian businesses used AI in 2024-25, and 35% of large businesses](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25), roughly a tenfold rise for small business in two years. ## Where to start Not with software. Write the close checklist down first, because an agent cannot track a process that lives in someone's head. Then sequence the agent work the way we do with clients: reconciliation exceptions first, task tracking and chasing second, draft journals third, variance narratives last, because narratives are where the judgement and the risk concentrate. Run everything in a sandbox before it touches production, scope the agent's permissions to the role it serves, and keep an audit trail of every draft and every approval. The controls that make this safe are the same ones we covered in our [AI agent governance guide](/blog/ai-erp-australia-8/ai-agent-governance-australia), and they are the product, not optional extras. That drafts-first, human-approved design is how we build every agent in our [AI agent services](/solutions/ai-agents) practice, whether the job is reconciliation, credit control or the close itself. --- **Thinking about a month-end close agent for your business?** We're a Brisbane-based ERP consultancy that runs AI agents over Odoo and MYOB Acumatica for our own operations and for Queensland businesses, always drafts-first with a human approving every entry. If your close keeps running past day ten, [**book a free consultation**](/appointment). We'll look at where your close actually loses time and give you a straight answer on whether an agent would help. --- # Odoo Multi-Currency Accounting in Australia: How It Works and What to Watch - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-multi-currency-accounting-australia - Category: Odoo ERP Australia - Published: 2026-08-10 - Description: How Odoo multi-currency accounting works for Australian businesses: automatic exchange rates, foreign bank accounts, gains and losses, and BAS in AUD. Plenty of Australian businesses trade in more than one currency without thinking of themselves as international. You invoice a New Zealand customer in NZD, pay a supplier in USD, or hold a EUR account for European sales. Meanwhile your books, your Business Activity Statement (BAS) and your tax reporting all stay in Australian dollars. Odoo multi-currency accounting handles that split well, but only when the setup matches how the ATO expects foreign amounts to be converted. This post covers how it works and where it goes wrong. ## How Odoo multi-currency accounting works Multi-currency is built into Odoo Accounting rather than bolted on. You activate it under the accounting settings, nominate a journal for exchange difference entries, and set a gain account and a loss account, as described in the [official multi-currency documentation](https://www.odoo.com/documentation/19.0/applications/finance/accounting/get_started/multi_currency.html). From that point you can activate as many currencies as you trade in. The important design decision sits underneath: every transaction is recorded in your company currency, which for Australian businesses is AUD, alongside the value in the transaction currency. Reports run off the AUD figures. An invoice raised in USD carries both the USD amount your customer sees and the AUD amount your ledger and BAS work from. You never maintain two sets of books. Customers and suppliers can carry a default currency, so quotes, invoices and bills come out in the right currency without anyone selecting it each time. ## Exchange rates: automatic updates, and which rate the ATO accepts Odoo can update exchange rates manually or automatically. Set the interval to daily, weekly or monthly and pick the provider the rates come from. The European Central Bank is the default, with several alternatives available in the same setting. The rate provider is not just a technical choice. GST must be worked out and reported in Australian dollars regardless of the currency on the invoice. The ATO's foreign exchange conversion rules, set out in [GSTR 2001/2](https://www.ato.gov.au/law/view/document?docid=GST%2FGSTR20012%2FNAT%2FATO%2F00001), let you use a rate from the Reserve Bank of Australia, from your chosen foreign exchange organisation, or an agreed rate. The catch is consistency. Once you pick a source, you're expected to keep using it unless you have sound commercial reasons to change. So the practical setup rule is simple. Agree the rate source with your accountant first, then configure Odoo to match it, including the update frequency. A daily RBA-aligned rate with invoices coded properly will survive an audit conversation. A default setting nobody ever looked at is harder to defend. ## Foreign currency bank accounts If you hold a USD or NZD account, Odoo stores two values for every bank transaction: the amount in the account's currency and the equivalent in AUD, per the [foreign currency bank account documentation](https://www.odoo.com/documentation/19.0/applications/finance/accounting/bank/foreign_currency.html). You reconcile in the account's currency and Odoo takes care of the AUD side. One caveat for Australian setups. Odoo's Basiq bank synchronisation covers Australian financial institutions, so a foreign currency account held with an Australian bank can still feed in automatically. An account held offshore usually means manual statement imports instead. We covered the import options in our post on [Odoo bank feeds in Australia](/blog/odoo-erp-australia-6/odoo-bank-feeds-australia), and the matching workflow in the [bank reconciliation guide](/blog/odoo-erp-australia-6/odoo-bank-reconciliation-in-australia-statement-feeds-aba-matching-and-keeping-bas-tidy-131). ## Realised and unrealised gains and losses Two different things happen when rates move, and Odoo handles them differently. Realised differences appear when money actually changes hands. You invoiced USD 10,000 when the rate gave you one AUD figure, and the payment landed when it gave you another. Odoo posts the difference to your exchange difference journal automatically at reconciliation. No manual journal required. Unrealised differences sit in open invoices and bills that haven't been paid yet. Odoo's unrealised currency gains and losses report lists every open foreign currency position, shows the adjustment against current rates, and posts a revaluation entry from a single button, with an automatic reversal on the date you set. It's worth running as part of month-end close, otherwise your balance sheet shows foreign balances at whatever rate applied when each invoice was raised. > The mistake we see most is treating exchange rates as set-and-forget. Pick the rate source your accountant is happy to defend, set Odoo's update interval to match, and glance at the gains and losses accounts monthly. Five minutes of review beats a year-end surprise. > > **Bill Alvarez, Practice Manager, Auboros** ## Where multi-currency setups go wrong Multi-currency is a feature where configuration quality shows quickly. [Capterra's Australian research](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/) found fewer than 1 in 3 Australian businesses successfully adopt new software, and currency handling is a common reason finance teams lose confidence in a new system. The patterns we get called in to fix: - **A rate source nobody chose.** The bank uses one rate, Odoo uses the ECB default, and every payment lands with a small difference. Align the provider with the source your accountant nominated. - **GST worked out from the foreign amount.** GST is an AUD figure. If taxes on foreign currency invoices aren't mapped correctly, the BAS picks up the error. Our [Australian localisation guide](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98) covers how the AU tax setup should look. - **No revaluation routine.** The unrealised gains and losses report exists, but nobody runs it, so the balance sheet quietly drifts from reality. - **Overseas supplier bills entered in AUD.** The bill should carry the supplier's currency so the payment reconciles cleanly. This matters for [accounts payable runs](/blog/odoo-erp-australia-6/odoo-accounts-payable-in-australia-vendor-bills-3-way-matching-and-aba-payments-128) where foreign bills sit alongside domestic ABA batches. None of these are hard to fix. They're just easy to miss when multi-currency gets switched on as an afterthought during a bigger [Odoo implementation](/solutions/odoo). With MYOB's Mid-Market Survey finding [36% of Australian mid-sized businesses looking to upgrade their ERP](https://www.myob.com/au/insight/post/mid-market-survey-results-2025), plenty of finance teams will be setting this up for the first time this year. It rewards being done properly on day one. --- **Trading in more than one currency and not sure your Odoo setup is right?** We configure Odoo multi-currency accounting for Australian businesses from our base in Brisbane, covering rate providers, foreign bank accounts and the month-end revaluation routine. If your AUD reports and your bank balances have stopped agreeing with each other, [**book a free consultation**](/appointment) and we'll take a look. No obligation, and you'll leave knowing exactly what needs to change. --- # MYOB Acumatica Job Costing: Labour, Materials and Committed Costs in One View - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-job-costing-australia - Category: MYOB Acumatica Australia - Published: 2026-08-10 - Description: How MYOB Acumatica job costing tracks labour, materials and committed costs in real time, for Australian construction and professional services firms. Ask a builder, a fit-out contractor or an engineering consultancy what they actually need from an ERP and the answer is usually the same question: where is this job sitting against budget, right now? That's what job costing answers. MYOB Acumatica job costing tracks labour, materials, equipment and subcontractor commitments against each project in real time, and because it sits inside the same platform as your general ledger, the numbers on the project screen and the numbers in the accounts are the same numbers. This post covers how it works, and why it isn't only for construction. ## How MYOB Acumatica job costing works Every project in MYOB Acumatica carries its own budget, broken down by cost code. Budgets connect directly to contracts, the project plan and the accounting ledger, so a variation approved on the project flows through to margin reporting without anyone rekeying it. MYOB's [construction management page](https://www.myob.com/au/erp-software/industries/cloud-construction-software) describes the core of it: real-time costing across labour, material and equipment, percentage of completion tracking, and cost-to-complete estimates. In practice that means three things for the person running the job: - **Costs land as they happen.** Timesheets, supplier bills and stock issues post against the project when they're entered, not when someone compiles a report at month end. - **Percentage of completion is visible.** You can see how far through the budget you are against how far through the work you are, which is where problem jobs reveal themselves early. - **History feeds the next quote.** Detailed cost records by code make the next estimate an evidence exercise rather than a guess. ## Committed costs: the money you've already promised Actual costs only tell half the story. The half that sinks projects is the money you've committed but haven't been billed for yet: the subcontract signed last month, the purchase order raised for materials arriving in six weeks. MYOB Acumatica records subcontracts and purchase orders as commitments against the project budget the moment they're raised. Budget versus actual reporting includes those committed amounts, change orders and variations run through a controlled process instead of an email thread, and vendor payment status is visible per project. For Queensland builders there's a compliance angle on top of the cost control one, which we covered in our post on [MYOB Acumatica for construction in Queensland](/blog/myob-acumatica-australia-7/myob-acumatica-for-construction-in-queensland-job-costing-qbcc-compliance-and-what-s-included-105). ## Job costing isn't just for construction Construction gets all the attention here, but the same machinery runs client work. In a professional services firm, the job is a client engagement and the dominant cost is people's time. The mechanics are identical: a project, a budget, costs posting against it as timesheets land, and billing driven by what the project has actually consumed. MYOB's [project accounting features](https://www.myob.com/au/erp-software/features/project-accounting-software) cover expense tracking, employee management and real-time project outcomes across services businesses, not just job sites. Work in progress, fixed-fee versus time-and-materials billing, and revenue recognition all hang off the same project structure. We've written separately about [MYOB Acumatica for professional services firms](/blog/myob-acumatica-australia-7/myob-acumatica-for-professional-services-firms-in-australia-88) and the underlying [project accounting capability](/blog/myob-acumatica-australia-7/myob-acumatica-project-accounting-australia-123) if your jobs bill in hours rather than bricks. > The test we give prospects is one question: if I asked for the margin on your three biggest current jobs, how long would the answer take? If it's minutes, your system works. If it's a spreadsheet and a couple of days, that's the gap job costing closes. > > **Josh Craig, Director, Auboros** ## From the site or the client meeting back to the ledger Job costing only stays accurate if the data comes in from where the work happens. Daily field reports capture site activity, subcontractor updates and variation requests from a phone or tablet. Accounts payable workflows route supplier invoices through approval before they hit the job. And because payroll runs in the same platform, labour hits projects with its real cost, while compliance reporting for payroll tax, superannuation and PAYG is generated from the same data. The results roll up into dashboards you can shape per role, which we walked through in our recent post on [MYOB Acumatica reporting and dashboards](/blog/myob-acumatica-australia-7/myob-acumatica-reporting-dashboards-australia). A project manager sees cost versus budget per job. A director sees margin across the portfolio. ## When spreadsheet job costing stops working Most businesses start with job costs in a spreadsheet, and at a certain size it works fine. The wheels come off when volume arrives: more concurrent jobs, more subcontractors, more people entering data. Construction is Australia's largest industry by business count, with over 460,000 registered businesses per the [ABS business counts](https://www.abs.gov.au/statistics/economy/business-indicators/counts-australian-businesses-including-entries-and-exits/latest-release), and the vast majority run well below the size where an ERP makes sense. The sizing signals we look for are around 20 or more staff, multiple concurrent projects, and a finance team spending days each month reconciling project spreadsheets to the accounts. That reconciliation burden is the real cost. MYOB's [ERP Trends research](https://www.myob.com/au/insight/post/erp-trends) found 45% of Australian decision-makers say disconnected systems limit growth, and disconnected job costing is the sharpest version of that problem, because the disconnect shows up as margin surprises on finished work. If that sounds familiar, our [MYOB Acumatica services page](/solutions/myob) covers how we scope an implementation. --- **Want to see your job margins without the spreadsheet?** We implement MYOB Acumatica job costing for construction and services businesses across Queensland and beyond, from our base in Brisbane. If your project costs currently live in a workbook only one person understands, [**book a free consultation**](/appointment) and we'll walk through what a connected setup looks like for your jobs. No pressure either way. --- # The AI RMA and Warranty Triage Agent: How It Works Inside Odoo and MYOB Acumatica - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-rma-warranty-triage-agent-erp-australia - Category: AI & ERP - Published: 2026-08-09 - Description: How an AI agent sorts returns, checks warranty status and drafts replies in Odoo and MYOB Acumatica, and why Australian Consumer Law keeps a human approving. Every product business handles returns. A customer emails to say the pump stopped working, a freight-damaged carton arrives back at the warehouse, a retailer wants credit for a batch of faulty chargers. Someone on your team reads each message, digs out the order, checks the serial number, works out whether it's covered, and writes a reply. The work is repetitive, it never stops, and most of it can be taken most of the way by an AI agent, as long as a person makes the final call. An RMA and warranty triage agent is an AI agent that reads inbound return and warranty claims, matches them to the customer, product and serial number in your ERP, checks the warranty position, classifies the fault, and drafts a response for a person to approve. RMA stands for return merchandise authorisation, the reference your team raises to track a return through the warehouse. The agent does the reading and the drafting. The decision stays with a human, and in Australia there's a legal reason for that, which we'll get to. Adoption is moving quickly here: the Australian Bureau of Statistics reports [12% of Australian businesses used AI in 2024-25, rising to 35% of large businesses](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25). Returns and service triage is one of the more sensible places to start, because the volume is high, the facts the agent needs already live in your ERP, and the guardrails are easy to define. It's the same drafts-first pattern we described for the [AI credit management agent](/blog/ai-erp-australia-8/ai-credit-management-agent-erp-australia), applied to the service queue. ## What an RMA and warranty triage agent actually does The pattern breaks into five jobs, and none of them involves the agent sending anything on its own. - **Reads the intake.** Claims arrive as emails, portal forms, marketplace messages and photos of broken products. The agent extracts what happened, which product, and what the customer wants. - **Matches the records.** It finds the customer, the sales order, the invoice and the lot or serial number in the ERP, so the claim is anchored to a real transaction rather than to whatever the email says. - **Checks the coverage position.** Purchase date, warranty terms for that product, service history for that unit, and whether the fault described matches a known issue. This is a factual lookup, not a verdict. - **Classifies and routes.** Likely freight damage goes one way, suspected manufacturing fault another, change-of-mind another. Anything ambiguous or high value gets flagged for a person immediately. - **Drafts the paperwork.** A proposed reply to the customer, a draft RMA reference, a draft repair order or return receipt in the ERP. Everything sits in draft until someone approves it. Your service coordinator then works through a queue of prepared cases instead of a pile of raw emails. They approve, edit or reject each draft. On a busy returns desk that's the difference between triaging thirty claims a day and triaging a hundred, without a single automated decision leaving the building. ## What Odoo and MYOB Acumatica already do without AI An honest starting point: a lot of the transactional plumbing already exists in both platforms, and you should switch it on before adding any AI. In Odoo 19, the Helpdesk app's [after-sales tools](https://www.odoo.com/documentation/19.0/applications/services/helpdesk/advanced/after_sales.html) are shipped Enterprise features. From a single ticket your team can process a return through a reverse transfer, create a repair order with an Under Warranty option that zeroes the sale price of parts, issue a credit note against a posted invoice, and schedule an on-site visit. Products tracked by lot or serial number carry that reference through the whole chain. If your technicians do repairs in the field, our [FieldPro field service app](/solutions/odoo-field-service-australia-nz) syncs those jobs to mobile devices with offline support. MYOB Acumatica handles the equivalent through its service tools. [Field Service Edition tracks customer equipment, service history and warranty status](/blog/myob-acumatica-australia-7/myob-acumatica-field-service-edition-australia) against the actual unit installed at the customer's site, and [Acumatica's field service module](https://www.acumatica.com/cloud-erp-software/field-service-management/) globally now ships AI-embedded customer insights alongside scheduling and contract billing. The usual caveat applies: global Acumatica features typically reach the ANZ MYOB Acumatica release 6 to 9 months later, so confirm what's in your version before you plan around it. What neither platform does today is read a rambling customer email, match it to a serial number, weigh the coverage position and draft a considered reply. That reading and drafting layer is where the agent earns its keep, running over the ERP through APIs with its own scoped login rather than replacing any of the plumbing above. ## Australian Consumer Law is why the agent never decides Here's the part most AI vendors skip. Under the Australian Consumer Law, consumer guarantees are automatic, they exist regardless of any warranty the manufacturer offers, and they have no set expiry date. The ACCC received [more than 28,000 reports and enquiries about consumer guarantees and warranties in a single year](https://www.accc.gov.au/media-release/broken-but-out-of-warranty-your-consumer-guarantee-rights-may-still-apply), and its published list of misleading statements includes the classic: "your product is out of warranty, so we can only repair it for a fee." That sentence is exactly what a naive triage bot would generate. The warranty date in the ERP says expired, so the template says declined. But if the product failed sooner than a reasonable customer would expect for its type and price, the consumer guarantees may still entitle them to a remedy: a free repair for a minor failure, and the customer's choice of refund or replacement for a major one. Misleading customers about those rights is unlawful, and the penalties are not theoretical. Fitbit paid $11 million in penalties after admitting it misrepresented refund and replacement rights to customers with faulty devices. So the design rule is simple. The warranty window is a data point the agent surfaces, never a decision it acts on. Whether the consumer guarantees still apply involves judgement about durability, price and product type, and that judgement belongs to a person who can be held accountable for it. Asking for proof of purchase is fine. Auto-sending coverage verdicts is not. ## A worked example: the out-of-warranty claim A Queensland equipment importer, a pattern we see often, receives a warranty email with two photos attached. The agent reads it, finds the serial number in the ERP, and assembles the file: sold 26 months ago, 24-month manufacturer warranty, no prior service history, fault description consistent with a known component issue on that product line. A bot that stopped at the warranty date would draft a rejection. This agent instead flags the case with the full position: warranty expired, but the unit is a premium product two months past a two-year warranty, and the fault matches a known defect, so consumer guarantee obligations are likely in play. It drafts two options for the service coordinator, a goodwill repair and a formal assessment pathway, each with the supporting facts attached. The coordinator picks the repair option, softens one sentence, and approves. Only then does the agent's draft become a sent email and a draft repair order for the workshop, raised under the coordinator's approval, not the agent's initiative. > "The warranty date in your ERP tells you what the manufacturer promised. It doesn't tell you what the customer is entitled to under Australian Consumer Law. That gap is judgement work, and it's exactly why our triage agents draft and never send." > > **Josh Craig, Director, Auboros** ## Guardrails before you switch anything on The controls for a triage agent follow the same shape as the rest of our [AI agent governance](/blog/ai-erp-australia-8/ai-agent-governance-australia) playbook. - **Role-scoped access.** The agent reads with the same permissions as the service team, nothing more. In Odoo 19, AI agents already run inside the signed-in user's access rights, which is the right default to copy in any custom build. - **Drafts-first on every write.** Customer replies, RMA references, repair orders and credit notes are all created in draft. A named person approves each one, and credits especially never post without sign-off. - **A full audit trail.** Every claim, every draft, every approval and every edit is logged against the ticket, so you can reconstruct who decided what and when. - **Privacy by design.** Claims carry names, addresses and purchase histories, which are personal information under the [Australian Privacy Principles](https://www.oaic.gov.au/privacy/australian-privacy-principles). Keep the data inside your systems and check where your AI provider processes it. - **Clear escalation rules.** Safety-related faults, high-value units and angry customers skip the queue and go straight to a person, with the agent's research attached. None of this is exotic. It's the same discipline you'd apply to a new staff member on the returns desk: limited system access, supervised replies, and a manager who signs off before anything goes out the door. --- **Thinking about an agent for your returns queue?** We design and run drafts-first [AI agents over Odoo and MYOB Acumatica](/solutions/ai-agents) from Brisbane, including service and RMA triage, for businesses across Queensland and beyond. If you'd like to see what a warranty triage agent would look like over your actual returns process, [**book a free consultation**](/appointment). We'll look at your claim volume and tell you plainly whether it's worth automating yet. --- # Odoo Bank Feeds in Australia: Sync, Manual Imports, and Which to Choose - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-bank-feeds-australia - Category: Odoo ERP Australia - Published: 2026-08-09 - Description: How Odoo bank feeds work in Australia: the free Basiq connector, OFX and CSV imports, sync frequency, and which setup keeps reconciliation and BAS tidy. Bank reconciliation is only ever as good as the transaction data flowing into it. Get the feed setup right and reconciliation becomes a ten minute daily habit. Get it wrong and you're exporting spreadsheets from internet banking every Friday, wondering why the bank balance in Odoo never matches the real one. Odoo gives Australian businesses two ways to bring bank transactions in: automatic synchronisation through a bank feed, or manual statement imports. This post covers how each works, what the Australian connector actually supports, and how to decide which setup fits your business. ## How Odoo bank feeds work in Australia Odoo Enterprise includes online bank synchronisation, which connects your bank accounts to Odoo through a third-party data provider. For Australia, that provider is Basiq. The [Odoo documentation on Basiq](https://www.odoo.com/documentation/19.0/applications/finance/accounting/bank/bank_synchronization/basiq.html) confirms the connector is free for Odoo users and available only for Australian banks, which is exactly what you want: a connector built for this market rather than a global service with patchy local coverage. Once connected, Odoo checks for new transactions automatically every 12 hours. You can also trigger a fetch manually from the accounting dashboard whenever you need up to the minute data, such as before a payment run or at month end. The connection process runs through Basiq's consent flow. You authorise access to the specific accounts you want in Odoo, and only transaction data comes across. Odoo never stores your banking credentials. If your bank doesn't appear in the connection flow, that's your answer on coverage, and manual imports become the fallback. One thing worth being clear about: bank synchronisation is a feature of [Odoo Enterprise](https://www.odoo.com/documentation/19.0/applications/finance/accounting/bank/bank_synchronization.html). If you're weighing up editions, feeds belong on the Enterprise side of the ledger along with the [Australian localisation features](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98) like BAS reporting. ## Manual statement imports: OFX, QIF, CSV and CAMT Not every business wants a live feed, and not every account can have one. Odoo Enterprise ships with import support for the four common statement formats: OFX, QIF, CSV and CAMT.053. Most Australian banks export at least OFX or CSV from internet banking. CSV is the most flexible and the most work. On first import you map your bank's columns (date, description, amount) to Odoo's fields, and Odoo remembers the mapping for next time. OFX and QIF carry more structure, so they import with less setup. Manual imports make sense in a few situations: - **Low transaction volume.** If an account sees a dozen transactions a month, a weekly import takes two minutes and a feed adds little. - **Unsupported accounts.** Some credit union accounts, term deposits and specialty facilities don't appear in feed coverage. - **Policy reasons.** Some boards and finance committees are not yet comfortable authorising third-party data access, common in clubs and not-for-profits. Imports keep everything in-house. A quick clarification that trips people up: ABA files are for sending payments out of Odoo to your bank, not for bringing statement data in. If you're setting up supplier payment runs, that's covered in our guide to [Odoo accounts payable and ABA payments](/blog/odoo-erp-australia-6/odoo-accounts-payable-in-australia-vendor-bills-3-way-matching-and-aba-payments-128). ## Feed or import: how to choose For most trading businesses, the feed wins. The [MYOB ERP Trends report](https://www.myob.com/au/insight/post/erp-trends) found 45% of Australian decision-makers say disconnected systems limit their growth, and a bank account that only talks to your ERP when someone remembers to export a file is a disconnected system. The practical difference shows up in reconciliation behaviour. With a feed, transactions appear twice a day and someone can clear them in minutes while the transactions are still fresh in memory. With imports, reconciliation tends to drift into a batch job, and batch reconciliation is where errors hide. > "The businesses with clean books are never the ones with the fanciest setup. They're the ones where transactions arrive automatically and someone spends ten minutes a day clearing them. The feed is what makes that habit possible." > > **Josh Craig, Director, Auboros** There are legitimate mixed setups too. We regularly configure the main trading account on a Basiq feed and leave a rarely used foreign currency account or term deposit on quarterly CSV imports. Odoo handles per-journal configuration without fuss. ## Setup details that matter for Australian books Whichever path you choose, a few configuration decisions determine whether your feed helps or hurts at BAS time. - **Reconciliation models do the heavy lifting.** Bank fees, merchant charges and interest can be matched and coded automatically, including the right GST treatment. We covered this in detail in our [Odoo bank reconciliation guide](/blog/odoo-erp-australia-6/odoo-bank-reconciliation-in-australia-statement-feeds-aba-matching-and-keeping-bas-tidy-131). - **GST coding at the point of reconciliation.** Every transaction cleared with the wrong tax code is a future BAS adjustment. Set your models up so the common cases code themselves and the odd ones get flagged, not guessed. The ATO's guidance on [business activity statements](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas) is the reference point for what you're reconciling toward. - **Keep the source records.** The ATO's [record keeping rules](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/record-keeping-for-business/overview-of-record-keeping-rules-for-business) require most business records to be kept for five years. A feed doesn't replace statements; download and store the PDFs, or attach them to the statement records in Odoo. ## When feeds misbehave Feeds are reliable but not perfect, and it pays to know the failure modes. Connections occasionally need re-authorising after a bank-side security change. Pending transactions can shift dates when they settle, which is why Odoo's matching works on posted transactions. And if you disconnect and reconnect an account, watch the first fetch for duplicates before you reconcile it. None of these are reasons to avoid feeds. They're reasons to have someone who knows what a healthy feed looks like glance at the journal weekly, which is a far smaller job than manually importing everything forever. **Getting bank feeds flowing into Odoo** We set up Basiq feeds, statement imports and reconciliation models as part of every [Odoo implementation](/solutions/odoo) we deliver from Brisbane, for businesses across Queensland and beyond. If your reconciliation still starts with a CSV export, [**book a free consultation**](/appointment) and we'll show you what the daily habit version looks like. No pressure, just a look at how your current setup compares. --- # MYOB Acumatica Reporting and Dashboards: What You Can Build Without a Developer - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-reporting-dashboards-australia - Category: MYOB Acumatica Australia - Published: 2026-08-09 - Description: What MYOB Acumatica reporting includes: generic inquiries, role-based dashboards, Power BI connections and consolidated group reports, minus the spreadsheets. Ask a finance team why they bought an ERP and the honest answer is usually some version of "so we stop rebuilding the same spreadsheet every month." The [MYOB ERP Trends report](https://www.myob.com/au/insight/post/erp-trends) found 45% of Australian decision-makers say disconnected systems are limiting their growth, and the report's case studies describe teams winning back the equivalent of a day a week once reporting comes out of spreadsheets and into the platform. MYOB Acumatica reporting is one of the platform's stronger suits, but the toolkit has several layers and it isn't obvious from the outside which layer does what. Here's how the pieces fit, what you can build yourself, and where you'll want help. ## The four reporting layers in MYOB Acumatica Most reporting questions land in one of four tools, and knowing which one saves a lot of wandering. - **Financial statements.** The Analytical Report Manager builds your P&L, balance sheet and cash flow layouts directly from general ledger data, with the structure and comparatives your accountant expects. - **Generic inquiries.** The workhorse of the platform. A generic inquiry is a reusable query over any data in the system, built through configuration rather than code, and [Acumatica's documentation](https://www.acumatica.com/cloud-erp-software/reporting-dashboards-and-data-analysis/) confirms inquiries feed reports, dashboards, Excel exports and OData connections. - **Dashboards.** Role-based screens assembled from inquiry data: charts, tables, KPIs and trend tiles that update in real time and drill down to the underlying transactions. - **External BI.** When analysis outgrows the platform, inquiries publish through OData to tools like Microsoft Power BI, so your analysts work on live ERP data rather than last week's export. The pattern worth noticing: generic inquiries sit underneath almost everything. Get comfortable building them and most reporting requests stop needing anyone's help at all. ## Dashboards that match how people actually work The dashboard layer is role-based, which matters more than it sounds. A warehouse manager logs in to open orders and stock alerts. The financial controller sees cash position, overdue receivables and unreconciled accounts. Neither wades through the other's numbers, and access follows the same security roles that govern the rest of the platform, so nobody sees figures they shouldn't. Dashboards are built by configuration. Pick an inquiry, choose a widget type, set the filters. In our experience the first few are worth building alongside someone who knows the data model, after which most teams maintain their own. ## Consolidated reporting across companies For groups running multiple entities, this is where the platform earns its keep. MYOB Acumatica posts intercompany transactions and produces consolidated financials without the spreadsheet merge ritual, and dashboards can show group-wide or per-entity views from the same inquiries. We covered the underlying structure in our guide to [MYOB Acumatica multi-entity and intercompany accounting](/blog/myob-acumatica-australia-7/myob-acumatica-multi-entity-australia), including how GST groups change BAS lodgement. One boundary to keep clear: consolidated management reporting is not the same thing as your statutory obligations. Your BAS still gets built from the tax data underneath, and the ATO's [business activity statement guidance](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas) remains the reference for what has to be lodged and when. Good dashboards make BAS preparation calmer; they don't replace it. > "The reporting conversation I have most often isn't about a missing feature. It's a business that has owned the platform for two years and still runs month end out of Excel because nobody showed them generic inquiries in week one. The capability was sitting there the whole time." > > **Bill Alvarez, Practice Manager, Auboros** ## What you can build yourself, and where the edges are A realistic split, based on the implementations we support: - **Configuration territory.** New inquiries, dashboard changes, pivot tables, Excel and OData connections, side panels on existing screens. A capable finance user handles all of this after a day or two of guided practice. - **Partner territory.** Reports that need new calculated fields across modules, performance tuning on inquiries over very large tables, and anything touching the customisation layer. Our post on [MYOB Acumatica customisation](/blog/myob-acumatica-australia-7/myob-acumatica-customisation-australia-118) explains where configuration ends and development begins. Worth knowing on the roadmap front: Acumatica's 2026 R1 release adds AI-assisted anomaly detection on inquiries and live Excel export of analytical reports. MYOB packages global releases for Australia and New Zealand on its own schedule, and the current ANZ release is 25 R2, so treat those features as coming rather than available until they appear in MYOB's local release notes. The reporting layers above are core platform and have been shipping for years. ## Getting more out of the reports you already own If your MYOB Acumatica reporting still leans on exports, the fix is usually sequencing, not software. Start with the five numbers each role checks weekly, build one inquiry and one dashboard per role, and retire the matching spreadsheet the same week. Momentum does the rest. **Make MYOB Acumatica reporting earn its subscription** We build reporting and dashboard setups as part of [MYOB Acumatica implementations](/solutions/myob) and as standalone engagements for businesses already on the platform, from our base in Brisbane across Queensland and beyond. If month end still lives in spreadsheets, [**book a free consultation**](/appointment) and we'll map your current reports to the tools you're already paying for. Bring your worst spreadsheet; we've seen worse. --- # Why ERP Implementations Fail in Australia: The Six Patterns Behind Most Troubled Projects - Canonical URL: https://www.auboros.com/blog/insights-5/why-erp-implementations-fail-australia - Category: Insights - Published: 2026-08-07 - Description: The six patterns behind failed ERP implementations in Australia, what they really cost, and the warning signs to act on before your project needs a rescue. Fewer than one in three Australian businesses that buy new software successfully adopt it, according to [Capterra's research on Australian software buying](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/), based on a survey of 281 Australian decision-makers. ERP sits at the hard end of that statistic. An ERP project touches every team, every process and the finance function's ability to close the books, so when it goes wrong it drags more of the business down with it than any other software purchase. We implement Odoo and MYOB Acumatica, and we also get called in when projects run by others have stalled. That second kind of work teaches you things the first kind doesn't. This post covers the six patterns we see behind most failed ERP implementations in Australia, what failure costs, the warning signs worth acting on early, and what to do if your project is already in trouble. ## What a failed ERP implementation actually looks like The failures that make the news are the spectacular ones. The federal government's GovERP program spent [$340.6 million between 2019 and 2023](https://www.digital.gov.au/initiatives/enterprise-resource-planning/erp-delivery-and-expenditure) building a shared corporate services platform for the public service. The independent technical assessment found that of the 30 capabilities developed, none progressed past functional testing into production, and the program was [retired in favour of a new approach](https://www.finance.gov.au/government/new-aps-erp-approach) that lets agencies choose their own systems. Private-sector failures rarely look like that. The version we see in Australian mid-market businesses is quieter. The system is technically live, but the warehouse still runs on the old spreadsheets because nobody trusts the stock numbers. The go-live date has slipped three times and the original budget is a distant memory. Phase one wrapped up eighteen months ago and the modules that justified the investment are still switched off. A failed implementation is rarely a system that doesn't work. It's a system the business doesn't use. ## Why ERP implementations fail: the six patterns Every troubled project we've assessed traces back to at least one of these patterns, and usually two or three working together. ### 1. The software was chosen before the processes were understood [45% of Australian decision-makers say disconnected systems are limiting their growth](https://www.myob.com/au/insight/post/erp-trends), so ERP purchases often happen under pressure. A demo looks convincing, a quote fits the budget, and the contract is signed before anyone has mapped how orders, stock, jobs and invoices actually move through the business. The gap between how the demo assumed you work and how you actually work becomes the project's real scope, discovered one change request at a time. ### 2. Data migration was treated as a copy and paste job Customer records with three duplicates each, stock items nobody has sold since 2019, opening balances that don't tie back to the old system. Migration is where implementations quietly lose their schedules, because cleaning data is unglamorous work that every party assumed someone else would do. We published a [data migration checklist](/blog/odoo-erp-australia-6/odoo-data-migration-checklist-australia) partly because this one workstream decides more go-live dates than any other. ### 3. Too much customisation, too early Custom code written before the team has used the standard system locks early misunderstandings into software. Every customisation adds testing effort now and upgrade cost later, and the worst projects we rescue involve custom modules with no documentation and no author still reachable. The discipline that works is boring: run standard first, customise what proves necessary, and document everything as if the next consultant will need it, because they will. ### 4. Training got whatever budget was left Training is the easiest line to cut when a project runs over, and cutting it is how systems end up technically live and practically unused. The people processing orders, picking stock and paying suppliers decide whether an ERP succeeds, and they decide it in the first few weeks after go-live. If their introduction to the system was one rushed session and a PDF, they'll retreat to the spreadsheets they trust, and the business case retreats with them. ### 5. Nobody inside the business owned the project An implementation partner can configure the system, but they can't decide which of your two conflicting pricing processes is the real one. Projects need an internal owner with the authority to make those calls and the time to make them quickly. Where the project is everyone's second job and no one's first, decisions queue up, the partner idles between answers, and the schedule slips without anyone doing anything visibly wrong. ### 6. The partner relationship broke down Sometimes the fit was wrong from the start: a team configuring GST, BAS and payroll settings for the first time, or a generalist reseller out of their depth in manufacturing. Sometimes the partner disappears mid-project. Sometimes the relationship sours over a scope dispute and both sides stop talking. Whatever the cause, a project cannot survive long without a functioning relationship at its centre, which is why partner selection deserves more diligence than most businesses give it. ## What ERP failure costs Australian businesses [36% of Australian mid-sized businesses are looking to upgrade their ERP](https://www.myob.com/au/insight/post/mid-market-survey-results-2025), and 48% name operational efficiency as the main driver. Some portion of those upgrades are really second attempts: a business paying for a system it never fully adopted, going back to market to try again. The direct costs are easy to list. Licence fees on modules nobody uses. Consultant invoices for work that got parked. The double handling of running old and new systems side by side for months longer than planned. The larger costs are quieter: decisions made on numbers nobody trusts, staff hours spent re-keying data between systems that were supposed to be connected, and the organisational scar tissue that makes the next technology project twice as hard to get approved. ## The warning signs a project is drifting Most failures announce themselves months in advance. These are the signals we'd act on: - **The go-live date has moved more than once.** One slip is normal. Two slips with no change in approach means the plan is the problem, not the calendar. - **Parallel spreadsheets are multiplying.** Every new "temporary" spreadsheet is a vote of no confidence in the system. - **Change requests outnumber completed milestones.** The project is redesigning itself faster than it is being delivered. - **Your team has stopped turning up.** When internal staff quietly drop out of project meetings, adoption is failing before go-live has even arrived. - **The answers are getting vaguer.** If "when will this be done" no longer gets a date, the partner may not know either. Any two of these together justify a pause and an independent look. The earlier the intervention, the more of the original investment survives. ## What to do if the implementation is already in trouble Start with a diagnosis rather than a bigger contract. In the [ERP rescue work](/solutions/erp-rescue) we run, the engagement begins with a fixed-fee assessment of the configuration, the custom code, the data quality and the gap between what was built and how the business operates. It ends in three costed paths: stabilise what exists so the business can run while decisions get made, rebuild in place on the same platform, or replatform as the last resort. Most rescues end in the middle path, because the licence investment and parts of the build are usually worth keeping. > In most rescues we run, the platform was never the problem. The configuration didn't match how the business actually works, and the people who use the system every day were never asked. Fix those two things and the same software the client wanted to throw out usually earns its keep. > > **Bill Alvarez, Practice Manager, Auboros** If the assessment does point to replatforming, treat it as a structured [ERP migration](/solutions/erp-migration) rather than a fresh leap of faith. The second implementation has to be run better than the first, not just aimed at different software. ## Setting up an implementation that won't need rescuing The prevention list mirrors the failure list, which is the point: - **Map your processes before you sign anything.** A partner who wants to understand your workflows before quoting is showing you how they'll run the project. - **Start the data work in week one.** Cleaning customer, supplier and stock records can begin before the system is even configured, and it shortens everything downstream. - **Run standard before you customise.** Live with the out-of-the-box process for a cycle where you can. Half the "essential" customisations stop being essential once the team has used the real thing. - **Name an internal owner with real authority.** Someone who can make process decisions without convening a committee, and whose other duties have visibly been reduced. - **Make training a protected line item.** Budget it per role, schedule it before go-live, and repeat it after the first month of live running when the real questions have surfaced. - **Check references from businesses like yours.** Same industry, similar size, same compliance needs. Australian GST, BAS and payroll requirements are unforgiving of partners learning on your project. For a sense of what a well-run project looks like phase by phase, our [Odoo implementation guide](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) and our [MYOB Acumatica implementation timeline](/blog/myob-acumatica-australia-7/myob-acumatica-implementation-timeline-australia) both walk through the stages in detail, including where the schedule risk usually hides. **Worried your ERP project is heading the wrong way?** We implement and rescue Odoo and MYOB Acumatica systems for businesses across Brisbane, Queensland and the rest of Australia, and a second opinion early is far cheaper than a rescue later. If your project is drifting, [**book a free consultation**](/appointment). Bring the war stories, we've heard most of them. --- # The AI Credit Management Agent: How It Works Inside Odoo and MYOB Acumatica - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-credit-management-agent-erp-australia - Category: AI & ERP - Published: 2026-08-07 - Description: What an AI credit management agent does inside Odoo and MYOB Acumatica: risk flags, drafted reminders and credit holds, with a human approving every send. Chasing late payments is nobody's favourite job, and it's one of the first places Australian businesses ask us about AI agents. The work is repetitive, the data already sits in the ERP, and doing it badly shows up as a cash flow problem within a quarter. An AI credit management agent is software that reads your accounts receivable data, watches how each customer's payment behaviour changes over time, and drafts the responses: reminder emails, credit limit recommendations, hold requests and call lists for the credit team. The word drafts matters. In every design we build through our [AI agent services](/solutions/ai-agents), the agent proposes and a person approves. Nothing reaches a customer, and no account goes on hold, until a human has looked at it. This post covers what a credit management agent actually does, what your ERP already handles without any AI, and the guardrails that keep automated collections on the right side of Australian rules. ## What an AI credit management agent actually does Think of the agent as a credit officer's assistant that never gets bored of the aged receivables report. Five jobs, roughly in order of value: - **It watches behaviour, not just balances.** An aged trial balance tells you who is overdue today. The agent tracks the trend underneath: a customer who has drifted from paying in 30 days to paying in 55 over six months is a bigger risk signal than a single invoice a week late. - **It flags risk early.** Part payments where full payments used to arrive, a broken payment promise, orders growing faster than the payment record justifies. These patterns are visible in ERP data long before an account lands in the 90 day column. - **It drafts the follow-ups.** Instead of a template blast, the agent writes each reminder with context: the invoices involved, the customer's history, what was agreed last time. A person reads, edits and sends. - **It recommends credit decisions.** When a customer trips a risk threshold, the agent drafts the recommendation: reduce the limit, ask for prepayment on the next order, or place the account on hold. The decision stays with a human, because a wrong hold blocks a real order from a possibly loyal customer. - **It prepares the credit call sheet.** Each morning the credit controller gets a prioritised list: who to call, what they owe, what they said last time, and a suggested talking point. That's an hour of report wrangling replaced with judgement work. ## What your ERP already does without AI Here's the part most AI content skips: a good share of credit control is already built into the ERP you own, and it isn't AI at all. Odoo 19 ships [follow-up levels](https://www.odoo.com/documentation/19.0/applications/finance/accounting/payments/follow_up.html) that schedule payment reminders by days overdue, escalate through email, SMS or post, attach the overdue invoices, and can run automatically once configured. Each level can also schedule an activity for a responsible user, and the chatter keeps a record of every reminder sent. That's shipped functionality today, no AI involved. MYOB Acumatica inherits the Acumatica platform's [credit controls](https://www.acumatica.com/cloud-erp-software/financial-management/accounts-receivable/): credit limits enforced at order entry and invoicing with a warning or a hard block, dunning letters, overdue charge calculation, parent and child account credit relationships, and role-based control over who can see or change customer balances. As usual with MYOB Acumatica, newer platform features tend to reach ANZ releases 6 to 9 months after the global Acumatica release, so check what your version includes. If none of that is switched on in your system, start there. A surprising share of "we need AI for collections" conversations turn out to be "nobody ever configured follow-up levels". The agent belongs on top of a working process, not instead of one. ## Where the agent earns its keep Rule-based dunning treats every overdue invoice the same. Day 7 gets email one, day 14 gets email two, day 30 gets the stern letter. That works until it doesn't: your biggest customer gets the same stern letter as a habitual non-payer, over a $180 invoice they've already disputed. The agent's job is the judgement layer. Here's a worked example from the pattern we design for wholesale and distribution businesses. Overnight, the agent reads the aged receivables, payment history and open orders from the ERP under its own read-only login. It notices a customer whose average days to pay has moved from 32 to 61 across the last five invoices, while their order volume has nearly doubled. Exposure is growing while payment performance is falling, which is the pattern that precedes most bad debts. By 7am, the credit controller has three drafts waiting: a reminder email referencing the specific invoices and the customer's usual payment pattern, a recommendation to ask for a part payment before releasing the two open orders, and a note for the account manager, since the growth story might justify a different conversation. The controller softens the email, approves the part payment condition, rejects the hold, and it's all done before the first coffee. The agent wrote everything. It sent nothing and decided nothing. > "The aged receivables report never tells you the story. The agent's job is to read five reports at once and say: this account has changed. A person still decides what to do about it, and that's how it should be." > > **Bill Alvarez, Practice Manager, Auboros** ## The rules that keep AI collections safe in Australia Collections is regulated conduct, which is a concrete reason to keep humans in the loop rather than a nice-to-have. - **Debt collection conduct rules.** The ACCC and ASIC publish a joint [debt collection guideline](https://www.accc.gov.au/about-us/publications/guideline-on-debt-collection-for-collectors-and-creditors) covering how, and how often, debtors may be contacted. An unsupervised agent firing reminders on a loop could cross lines a person wouldn't. Draft and approve keeps contact frequency and tone under human control. - **Privacy.** Payment histories are personal information when your customers are sole traders or individuals, so the [Australian Privacy Principles](https://www.oaic.gov.au/privacy/australian-privacy-principles) apply to how that data moves through any AI workflow. From 10 December 2026, privacy policies must also disclose the kinds of substantially automated decisions that significantly affect people, and a credit decision is a textbook example. One more reason the agent recommends and a person decides. - **Approval gates on anything that acts.** Credit holds, limit changes and every outbound message pass through a person. A clumsy reminder is embarrassing; a wrong credit hold stops a genuine order and sours a relationship you spent years building. - **An audit trail.** Every recommendation the agent makes, and every approval or rejection, gets logged. When someone asks in June why a customer went on hold in March, there's an answer. ## How to start without betting your ledger The rollout pattern we use for [reconciliation agents](/blog/ai-erp-australia-8/ai-reconciliation-agent-erp-australia) applies here almost unchanged. Run the agent read-only for the first month, observing and reporting, so you can judge its risk flags against what your credit controller already knows. Test in a sandbox before it touches production data. Scope its ERP login to customer, invoice and payment data and nothing else, the same [role-scoped permissions approach](/blog/ai-erp-australia-8/ai-agent-governance-australia) we recommend for every agent. Then switch on drafting, keep every approval human, and review a sample of its recommendations weekly. None of this waits on vendor roadmaps. Our own practice runs the read, analyse, draft pattern with external agents working through each platform's APIs under scoped logins. If you want the platform-by-platform picture of what ships natively, we've covered [AI agents in Odoo](/blog/ai-erp-australia-8/odoo-ai-agents-australia) and [MYOB Acumatica's AI features](/blog/ai-erp-australia-8/myob-acumatica-ai-australia) separately. --- **Thinking about a credit management agent for your business?** We design drafts-first credit control agents over Odoo and MYOB Acumatica from Brisbane, with role-scoped access and human approval on every send and every hold. If the aged receivables report keeps growing and the chasing isn't keeping up, [**book a free consultation**](/appointment). We'll tell you what's worth automating and what your ERP already does out of the box. --- # Conversational ERP in Australia: What It Is, What's Shipped, and How to Keep It Safe - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/conversational-erp-australia - Category: AI & ERP - Published: 2026-08-06 - Description: Conversational ERP lets staff query live business data in plain English. What Odoo and MYOB Acumatica offer today, and the permission rules that keep it safe. Ask a question in plain English, get an answer from live business data. That is the pitch for conversational ERP, and in 2026 it has moved from conference demo to shipping feature. Odoo 19 includes a built-in assistant. MYOB has signed a five-year deal with Microsoft to bring natural-language queries to MYOB Acumatica. [12% of Australian businesses now use AI](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25), and among large businesses it is around 35%, so a chat box on top of the ledger is coming to your industry whether you plan for it or not. Here is the part the vendor demos skip: the model is not the hard bit. The hard bit is deciding whose eyes the answer is allowed to see through. ## What conversational ERP actually means Conversational ERP is natural-language querying of a live business system. Instead of building a filtered report, you type the question the report was meant to answer: "which invoices over $10,000 are more than 30 days overdue?", "what did we sell to Queensland customers last month?", "which purchase orders are late?" The answer comes back from live data, not from a spreadsheet someone exported last Tuesday. The people who benefit most are the ones who never learned the report builder. A warehouse lead who wants to know what is arriving this week. An owner who wants one number on a Saturday morning without phoning the bookkeeper. A sales rep prepping for a call who needs the customer's order history and open credits in thirty seconds. That value is real, and it lands on day one because answering questions does not require the agent to change anything. What conversational ERP is not: a reason to hand an AI system open access to everything. Which brings us to permissions. ## The permissions question that decides everything Every conversational ERP setup answers one question, either deliberately or by accident: whose login does the agent use? If the agent runs as a shared super-user account, anyone who can type a question can read anything the ERP contains. Payroll. Margins. The warehouse casual asking "what does everyone here get paid?" is one autocomplete away from an answer no permission matrix would ever have shown them. The rule we set out in [our AI agent governance guide](/blog/ai-erp-australia-8/ai-agent-governance-australia) applies with full force here: an agent acts with the requesting user's exact data scope, never a shared privileged account. > "Whose login does the agent run under? That single question does more for safety than any model choice. Get it wrong and you have built a search engine for everything the ERP was carefully hiding." > > **Josh Craig, Director, Auboros** There is also a compliance clock on this. From [10 December 2026](https://www.oaic.gov.au/engage-with-us/consultations/consultation-on-guidance-for-transparency-in-automated-decision-making), Australian privacy policies must describe automated decisions that use personal information and could affect people's rights or interests. A read-only question box sits at the low-risk end, but once the same agent starts recommending credit holds or reading staff records, the disclosure obligation is squarely in frame. Design the permission model now rather than retrofitting it in December. ## What Odoo and MYOB Acumatica offer today It pays to be precise about shipped versus promised, because the gap is wide. **Odoo: shipped.** Odoo 19 includes Ask AI, an assistant you can open anywhere in the database. Per [Odoo's official documentation](https://www.odoo.com/documentation/19.0/applications/productivity/ai/agents.html), the standard assistant can open views and display reports but cannot create or alter records, and agents operate inside the signed-in user's access rights. You can restrict an agent to approved sources, and it only gets write-capable tools you deliberately hand it. The AI apps are Enterprise-only. We covered the mechanics, and what the v20 roadmap adds, in [our Odoo AI agents deep-dive](/blog/ai-erp-australia-8/odoo-ai-agents-australia). **MYOB Acumatica: mostly roadmap.** [MYOB's April 2026 partnership with Microsoft](https://www.myob.com/au/press-releases/myob-and-microsoft-sign-five-year-strategic-partnership-to-jointly-fund) promises contextual financial insights, natural-language queries and AI-assisted document processing for MYOB Acumatica, with the first jointly built features due late in 2026. That is an announcement, not a release. What ANZ customers can use today is narrower: AI Studio in technology preview plus the shipped 25 R2 features we walked through in [our MYOB Acumatica AI review](/blog/ai-erp-australia-8/myob-acumatica-ai-australia). If a salesperson tells you natural-language querying is live in MYOB Acumatica today, ask them to show you. **The bring-your-own route: available now, with work.** You can also connect a hosted assistant to either platform through the [Model Context Protocol](https://modelcontextprotocol.io), an open standard for wiring AI tools to business systems. An MCP server sits in front of the ERP with its own scoped credentials, so you decide what it can see and do, and you can swap the underlying model later without rebuilding. This is how we run our own agents. For Odoo, MCP servers exist today from the community and the app store; at the time of writing there is nothing first-party from Odoo SA. ## A worked example: credit questions that stay read-only Here is how the pattern looks for a wholesale distributor. An accounts receivable officer asks the agent: "which customers are over their credit limit and still placing orders?" The agent queries the ERP under her login, and only her login. It returns four customers, each with the exposure amount, the last order date and a link to the underlying records so she can check the numbers herself. Then she asks it to do something about it: "draft hold notices for the two largest." The agent writes two emails and proposes a credit-hold flag on each account. And there it stops. Nothing sends and no flag changes until she has read each draft and approved it. Reads are instant, writes wait for a human. That one rule is the difference between a useful assistant and an incident report. ## Five questions before you switch it on Put these to any vendor, integrator or enthusiastic staff member proposing a chat interface over your ERP: - **Whose login does it use?** The agent should act with the requesting user's permissions, never a shared account with broad access. - **Can it write, and where are the gates?** Read-only is a fine starting point. Any write-back to ledgers, pricing, stock or customer records needs a named human approving each change. - **What gets logged?** You want a record of who asked what, what the agent read and what it proposed. Auditors will eventually ask for it. - **Where does the data go?** Know which model processes your prompts, in which country and under what retention terms before finance data flows through it. - **What is it allowed to answer from?** Source and tool allowlists beat an open connection to everything. Start narrow and widen deliberately. If those five have good answers, conversational ERP is one of the lower-risk places to start with AI: mostly reads, and easy to trial in a sandbox before anyone touches production. If they don't, the chat box can wait. --- **Thinking about a plain-English layer over your ERP?** Auboros designs and runs [drafts-first AI agents](/solutions/ai-agents) over Odoo and MYOB Acumatica from Brisbane, with role-scoped permissions and human approval on anything that writes. If you want to scope conversational ERP for your business, [**book a free consultation**](/appointment). We'll tell you what's shipped, what's roadmap, and what's worth waiting for. --- # Odoo Version Upgrades in Australia: How the Process Works and When to Schedule One - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-version-upgrade-australia - Category: Odoo ERP Australia - Published: 2026-08-06 - Description: How the Odoo version upgrade process works, what the free upgrade service covers, and when Australian businesses should schedule the move to v19 or v20. Odoo releases a new major version every year. That annual cadence is one of the platform's strengths, because features arrive quickly and the product never sits still. It also means every Odoo site faces the same recurring decision: which version to move to, when to schedule the work, and how much testing the move needs before it touches production. This guide covers how the Odoo version upgrade process works, what Odoo's upgrade service does and doesn't handle, and how Australian businesses should time an upgrade around BAS quarters and the upcoming v20 release. If you're weighing up a move from another system entirely, that's a migration rather than an upgrade, and our [Odoo data migration checklist](/blog/odoo-erp-australia-6/odoo-data-migration-checklist-australia) is the better starting point. ## How the Odoo version upgrade process works Every upgrade follows the same two-stage pattern, whatever your hosting: test first, then production. You request an upgraded copy of your database through [Odoo's upgrade platform](https://upgrade.odoo.com/), test everything on that copy, and only then upgrade the real thing. Odoo asks you to run the production upgrade within three days of a successful test upgrade, so the testing window needs to be planned rather than left open-ended. The mechanics differ slightly by hosting type: - **Odoo Online.** You request the upgrade from the database manager or from your subscription page. The first request can only be a test, which is a sensible guardrail. - **Odoo.sh.** The platform has a dedicated Upgrade tab. You test on a staging branch built from your latest production backup, then run the same process on the master branch when you're satisfied. - **On-premise.** You can use the upload form or a command line tool. The command line route is faster for large databases and can resume if the transfer is interrupted. In every case the upgraded database comes back to you for testing. That testing step is where upgrades succeed or fail, and it deserves more attention than the upgrade request itself. ## What the upgrade service covers, and what it doesn't Odoo's [upgrade documentation](https://www.odoo.com/documentation/19.0/administration/upgrade.html) is clear about scope. The service converts your database so that standard modules, your data, and Odoo Studio customisations work on the target version. What it does not do is rewrite custom module code. If your site runs custom developed modules or third-party apps, that code has to be adapted to the new version separately, either by your internal team or by your partner. On Odoo.sh this shows up directly in the process: after the database upgrade finishes, the platform prompts you to push a commit containing your updated customisations. Two facts worth stating plainly, because we still see confusion about both: - **The upgrade service is included with every Odoo Enterprise subscription.** It isn't a partner-only benefit and there's no extra fee to Odoo for using it. - **Community edition sites upgrade differently.** The hosted upgrade service is tied to an Enterprise subscription, so Community upgrades are a manual, technical exercise. If that trade-off matters to you, our guide to [Odoo Community vs Enterprise](/blog/odoo-erp-australia-6/odoo-community-vs-enterprise-australia) covers it in detail. The upgrade platform currently offers 17.0, 18.0 and 19.0 as target versions, which reflects Odoo's practice of supporting the three most recent major releases. If you're running v16 or older, you're outside that window, and getting back inside it should be treated as overdue maintenance rather than a nice-to-have. ## When to schedule an Odoo upgrade in Australia The upgrade itself is version-agnostic about dates. Your BAS calendar isn't. Our advice for Australian businesses is to schedule the production cutover early in a Business Activity Statement (BAS) quarter, not in the weeks before a lodgement deadline. If something needs fixing after go-live, you want clear air between the fix and your next [BAS obligations](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas), not a compliance deadline bearing down on the finance team. The same logic applies to end of financial year: don't upgrade in the middle of your June close. Testing should include your Australian localisation specifically. Run your BAS report on the upgraded test database and compare it against production. Check tax codes, bank feeds and any ABA payment files. Standard modules convert reliably, but configuration issues surface in exactly these workflows, and finding them on staging costs nothing. Then there's the v20 question. Odoo unveils its next major version at [Odoo Experience 2026](https://www.odoo.com/event/odoo-experience-2026-9099/page/oxp26-be-introduction) in Brussels, running 24 to 26 September. If you're on v18 or v19 and stable, there's no urgency. If you're on v17, upgrading to v19 now and looking at v20 later usually beats waiting, because a just-released version takes months to settle and your support window keeps shrinking while you wait. We covered what's expected in the release in our [Odoo v20 roadmap post](/blog/odoo-erp-australia-6/odoo-v20-australia-features-roadmap-115). ## What an Odoo version upgrade actually costs The database conversion costs nothing on Enterprise. The real costs sit around it: - **Custom module adaptation.** Developer time to make custom code compatible with the new version. This scales with how much custom code you have, not with database size. - **Testing effort.** Finance and operations staff walking through real workflows on the test database. - **Integration re-testing.** Anything connected to Odoo, from ecommerce platforms to shipping tools, needs a check against the upgraded version. For a site with light Studio customisation, testing might take a few days of part-time effort. Sites with heavy custom code can need 2 to 6 weeks of development and testing before production cutover. [Capterra's Australian research](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/) found fewer than 1 in 3 Australian businesses successfully adopt new software, and skipped testing is a big part of why change goes wrong. An upgrade is a smaller change than a new system, but the discipline is the same. > Most upgrade pain we see isn't the upgrade itself, it's untested custom code hitting production. Test the upgraded database properly, fix what breaks on staging, and the production cutover is usually an evening's work. > > **Bill Alvarez, Practice Manager, Auboros** It's also worth keeping upgrades in perspective. [MYOB's Mid-Market Survey](https://www.myob.com/au/insight/post/mid-market-survey-results-2025) found 36% of Australian mid-sized businesses are looking to upgrade their ERP. Staying current on a platform you already own is far cheaper than being forced into a replatform later because versions were left to drift. Regular upgrades are how [Odoo implementations](/solutions/odoo) stay healthy over a five or ten year life. **Planning an Odoo version upgrade before v20 lands?** Auboros runs test upgrades, adapts custom modules and times cutovers around BAS quarters for businesses across Brisbane, Queensland and the rest of Australia. Our [Odoo upgrade services](/solutions/odoo-upgrades) cover the whole process from staging to go-live. If you'd like a clear picture of what your upgrade involves before committing to anything, [**book a free consultation**](/appointment). We'll tell you if the timing is wrong, too. --- # MYOB Acumatica Multi-Entity and Intercompany Accounting for Australian Groups - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-multi-entity-australia - Category: MYOB Acumatica Australia - Published: 2026-08-06 - Description: How MYOB Acumatica multi-entity and intercompany accounting works for Australian groups: consolidated reporting, GST groups, and when it's worth the move. Plenty of Australian businesses don't actually run as one company. There's a trading entity, a second entity from an acquisition that never quite merged, a property trust holding the warehouse, maybe a franchise arm or a related not-for-profit. Each one keeps its own books, and every month someone in finance stitches the group picture together in spreadsheets. That stitching is exactly what multi-entity ERP exists to remove. This post covers how MYOB Acumatica multi-entity and intercompany accounting works, where the GST group question fits, and when a group actually needs it. ## What MYOB Acumatica multi-entity accounting looks like day to day MYOB Acumatica runs multiple companies and branches inside one system, with one login. Each entity keeps its own ledgers and its own transactions, so statutory reporting stays clean, while group-level dashboards and reports read across all of them in real time. Three capabilities from [MYOB's financial management feature set](https://www.myob.com/au/erp-software/features/financial-management-software) do most of the heavy lifting: - **Per-entity books with group visibility.** Every company posts to its own ledger, and consolidated reports sit on top rather than replacing entity-level records. - **Role-based access by company.** Access can be restricted to specific transactions or companies based on a user's role, so the team running one entity doesn't wander through another's payables. - **Multi-currency.** Base currency settings and exchange rate feeds handle groups with a New Zealand subsidiary or overseas supplier entities without side spreadsheets. ## Intercompany transactions without the month-end scramble Intercompany activity is where separate accounting files hurt most. One entity pays an invoice on behalf of another, head office recharges management fees, stock transfers between companies, and every one of those events has to be entered twice and reconciled later. MYOB Acumatica handles [intercompany accounting](https://www.myob.com/au/erp-software/products/myob-acumatica) natively: transactions post across companies automatically, covering reporting, inventory transfers, vendor payments and cash management between entities, and the balancing entries keep loan accounts straight without manual journals. Month end stops being an archaeology exercise. The payoff is bigger than saved data entry. [MYOB's ERP Trends research](https://www.myob.com/au/insight/post/erp-trends) found 45% of Australian decision-makers say disconnected systems limit their growth, and MYOB's own figures suggest businesses waste around a day a week on disconnected systems. A multi-entity group running three or four separate files is the sharpest version of that problem. ## GST groups, BAS and the compliance angle Multi-entity structures raise a tax question that software alone doesn't answer: should the group register as a GST group? Under the [ATO's GST group rules](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst/in-detail/managing-gst-in-your-business/gst-groups-and-branches/gst-groups), two or more associated entities can operate as a single business for GST purposes. A nominated representative member lodges the Business Activity Statement (BAS) for the whole group, and transactions between group members are ignored for GST, so intercompany recharges stop generating GST line items entirely. The system side supports whichever way you land. Each entity's records stay separate and auditable, group reporting is available either way, and intercompany transactions are tracked cleanly whether or not they carry GST. Whether grouping suits your structure is a question for your tax adviser, because the group members become jointly responsible for GST liabilities. What the ERP removes is the bookkeeping argument against either choice. ## Where Australian groups actually use this The pattern shows up across almost every vertical we work in: - **Franchise networks** running company-owned stores as separate entities with consolidated head office reporting. Our post on [MYOB Acumatica for franchise businesses](/blog/myob-acumatica-australia-7/myob-acumatica-for-franchise-businesses-in-australia-94) goes deeper on this one. - **Not-for-profits and community organisations** with a main entity, a foundation and program-specific entities, covered in our [not-for-profit guide](/blog/myob-acumatica-australia-7/myob-acumatica-not-for-profit-australia). - **Aged care and community services providers** running multiple entities across programs and funding streams, which we covered in our [aged care and community services post](/blog/myob-acumatica-australia-7/myob-acumatica-aged-care-community-services-australia). - **Religious organisations** with parish, diocese and trust structures, per our [religious organisations guide](/blog/myob-acumatica-australia-7/myob-acumatica-religious-organisations-australia). - **Professional and property groups** pairing a trading entity with service entities and asset-holding trusts. > When a group is consolidating three sets of books in spreadsheets every month, the cost isn't just the accountant's time. It's that nobody trusts the group numbers until three weeks after month end. Moving every entity onto one system is about speed and trust, not accounting elegance. > > **Josh Craig, Director, Auboros** ## When multi-entity ERP is more than you need An honest sizing note. If you run one trading company plus a dormant trust that lodges a nil return, you don't need multi-entity ERP, and smaller MYOB products or separate files will carry you fine at that scale. The manual consolidation trade-off only bites when there's something to consolidate. The switch starts making sense when several entities trade actively, intercompany charges happen every month, and the board or bank wants consolidated reporting they can rely on soon after month end. At that point the spreadsheet layer is usually costing more than it appears to, in time and in decisions delayed while the numbers get argued about. That's the conversation to have before entity number four arrives, and it's exactly what our [MYOB Acumatica services](/solutions/myob) team scopes every week. **Consolidating multiple entities in spreadsheets every month?** Auboros implements MYOB Acumatica for multi-entity groups across Brisbane, Queensland and the rest of Australia, from franchise networks to community organisations. If you want to know whether your structure fits, [**book a free consultation**](/appointment). Bring your entity diagram, however messy it is. --- # AI Reconciliation Agents Inside ERP: How the Pattern Works for Australian Finance Teams - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-reconciliation-agent-erp-australia - Category: AI & ERP - Published: 2026-08-03 - Description: How AI reconciliation agents match ERP transactions, route exceptions, and protect your BAS. What Odoo 19 and MYOB Acumatica can switch on today. The rule in our AI practice is simple: the agent drafts, the human approves, the system posts. That sequence is non-negotiable for anything that touches the general ledger or the Activity Statement. A reconciliation agent makes that sequence faster, not optional. Bank statement reconciliation is the use case most Australian finance teams tackle first when adding AI to their ERP. According to MYOB's 2025 ERP Trends report, 45% of decision-makers say disconnected data is their biggest barrier to better business decisions. Reconciliation sits right at that disconnect. The agent does not remove the decision, but it removes most of the searching. ## What the pipeline looks like A reconciliation agent runs a five-stage pipeline on a schedule your finance team sets. **Ingest.** The agent pulls the bank statement, either via a direct feed or a file import, and reads the outstanding items in your ERP: open invoices, vendor bills, pending journal entries, and payments in transit. **Normalise.** Dates parse to a standard format. Amounts strip currency symbols. Reference numbers extract from transaction descriptions using pattern matching on common Australian bank statement formats. **Match.** Deterministic rules run first. Exact amount, matching supplier, reference number present, date within the payment terms window. A large proportion of routine transactions match on these rules alone. Most mature deployments see 85 to 95 percent of high-volume items matched deterministically before the LLM processes a single line. **Reason over exceptions.** The transactions that did not match cleanly go to a reasoning layer. The agent checks the supplier history, compares the amount against the purchase order within a configured tolerance, and looks at prior resolutions to similar exceptions. It classifies each one: timing difference, amount variance under threshold, missing invoice, or possible control risk. **Draft and route.** For every exception, the agent produces a classification, a draft recommendation, and routes it to the right person. It does not post. The agent has no write access to a finalised period. ## What Odoo 19 has today [shipped] Odoo 19's bank reconciliation module includes configurable reconciliation models that apply rules automatically as bank statements import. The models learn from your team's choices over time: if you consistently match a particular transaction type to a specific account code, the model starts suggesting that pairing. Unmatched items hold in a review queue and do not block the rest of the import. For the deterministic matching layer, the native module handles routine volume well. Extending it with an agent, to handle the exceptions that fixed rules miss, requires connecting via Odoo's server actions and the Model Context Protocol. That is a configuration and development task, not a toggle. The server actions define what the agent is permitted to do; MCP controls how an external LLM reads and writes within the Odoo environment. Set the permission scope first. For the full list of what Odoo 19 server actions expose to an agent, and what the v20 roadmap adds on top, the [Odoo AI agents guide](/blog/ai-erp-australia-8/odoo-ai-agents-australia) covers this in detail. Direct reconciliation write-backs via Odoo's Ask AI feature, where you instruct the agent in natural language to reconcile specific items, are on the v20 roadmap [roadmap]. They are not available in Odoo 19. Ask AI in the current release can read and report; it does not execute ledger write-backs. ## What MYOB Acumatica has today [shipped/preview] MYOB Acumatica has automated bank reconciliation as a live, shipped feature. The platform matches bank feeds to ERP transactions, handles multi-currency feeds from multiple banks, and uses historical transaction patterns to suggest account codes for new entries. Finance teams on a live tenant see the exception queue shrink each month as the system learns their specific chart of accounts and supplier behaviour. The 2026 R1 release added AI Advisor, which flags anomalies and discrepancies in real time and routes them to the relevant reviewer rather than leaving them buried in a period-end report. This is available for ANZ customers on the 2026 R1 release [shipped]. AI Studio, which connects MYOB Acumatica to an external LLM via MCP, was in early-entry preview from May 2026 [preview]. Once at general availability, AI Studio will allow custom reconciliation agents to operate inside the MYOB Acumatica security boundary, with role-scoped permissions and no data leaving the system. For ANZ customers, allow some lead time between global release dates and local rollout. ## How an AI reconciliation agent handles exceptions If your agent matches 90 percent of transactions and routes the remaining 10 percent as undifferentiated exceptions, you have not solved the problem. You have moved the pile from the bank statement to a different inbox. The value of the agent is in how it classifies that 10 percent before it reaches the reviewer. There are three categories worth distinguishing for an Australian mid-market business. **Timing differences** are the most common. Payment sent before the bank clears. Invoice dated end-of-month, payment received the next business day. The agent identifies these by comparing the expected payment date to the actual receipt date within a configurable window, typically three to five business days, and confirming the amount and supplier match. **Amount variances under a threshold** cover rounding, bank fees, and currency conversion differences on international payments. The agent drafts a minor variance journal entry and routes it for a single confirmation. Most finance teams set this threshold at 1 percent of transaction value or $50, whichever is lower. Above the threshold, the item goes to the standard exception queue for manual review. **Missing invoices** are the control risk category. Payment received, no matching invoice in the system. The agent flags this for AP review. It does not attempt to resolve it independently, and it should not. A well-configured agent presents each exception with a classification, the evidence it found, and a draft action. The reviewer sees context, not a raw transaction line. > "The question I ask before scoping any reconciliation agent is: what is your current exception rate, and what happens to those exceptions today? If they pile up until the BAS deadline, the agent's real value is in the exception workflow, not the match rate." > > Josh Craig, Director, Auboros ## The Australian compliance layer Every GST-registered business has an additional constraint the agent must respect: the GST code on every transaction determines its BAS treatment. The agent can suggest a GST code based on the supplier and transaction type. It should not apply that code without a human confirming it first. A GST input tax credit posted on a transaction that is actually GST-free does not just create a reconciliation difference. It misrepresents your BAS and your tax liability. The ATO requires businesses to retain records of their GST transactions for five years. An agent that posts autonomously, without a log of the human approval that preceded the posting, creates an audit trail problem that outweighs the time saved. The practical control is a GST code allowlist. Common codes such as GST (standard rated), FRE (GST-free), and CAP (capital acquisitions) sit on the allowlist; the agent can suggest these without escalation. Less common codes, including IMP (imported services) and specific input-taxed categories, require mandatory human confirmation before the entry is drafted. When the agent is uncertain, it escalates rather than guessing. ## A worked example with an approval gate A wholesale distribution business runs Odoo 19 with a reconciliation agent configured over the API. On a Friday afternoon, a $4,680 payment arrives from a regular customer. The ERP has one open invoice for $4,680 dated 12 days ago. The deterministic matching layer identifies the exact amount, the same debtor, and the invoice date within terms. It assigns the payment to the invoice automatically. No one reviews this; it matched cleanly. Two hours later, a $4,950 payment arrives from the same customer. The ERP has a second open invoice for $4,680, still unpaid, and no invoice for $4,950. The agent checks the customer's history. This debtor has paid $270 over invoice face twice before in the same month, both times followed by a freight credit note processed separately. The agent classifies this as a probable split: $4,680 against the open invoice, $270 as an unapplied receipt pending the credit note. The agent routes it to the AR manager with that classification and draft entries. It does not post. On Monday morning, the AR manager opens the review queue, reads the agent's reasoning, confirms the credit note is on its way, and clicks approve. Both entries post. The agent's suggestion was right; the human confirmed it. That is what the approval gate looks like in a working deployment. ## Three configuration decisions before you go live **The exception threshold** sets what the agent routes versus what it tries to resolve. Start conservative, around 1 percent of transaction value or $50, and tune it after the first quarter of data. Setting it too high on day one means the agent approves items your finance team should have seen. **The GST code allowlist** constrains what the agent can suggest without escalation. Implement this explicitly before go-live. Failing to define the allowlist is the most common configuration oversight in reconciliation agent deployments. **The locked-period rule** prevents the agent from drafting entries into a closed accounting period. Code this into the agent's permission set explicitly. The ERP's own period-close controls are not a substitute; the agent needs to know your close schedule. ## What to do next For businesses on Odoo 19, the [Odoo bank reconciliation setup guide](/blog/odoo-erp-australia-6/odoo-bank-reconciliation-in-australia-statement-feeds-aba-matching-and-keeping-bas-tidy-131) covers the native configuration in detail. Extending it with an agent layer starts with scoping your transaction volumes, exception rate, and chart of accounts. For businesses on MYOB Acumatica, the existing automated reconciliation feature is already handling part of this work. AI Advisor adds the real-time anomaly layer, and AI Studio (preview) opens the path to custom agent configurations once it reaches general availability for ANZ. For a broader picture of what agents can do across the full scope of an ERP deployment, the [overview of AI agents for Australian businesses](/blog/ai-erp-australia-8/ai-agents-for-australian-businesses-what-actually-works-in-2026-132) covers the range of use cases and the governance model behind them. Our [AI agents service](/solutions/ai-agents) covers both Odoo and MYOB Acumatica and includes pattern design, exception taxonomy, and approval-gate configuration as part of the engagement scope. [Book a session](/appointment) if you want to estimate what your current reconciliation workflow would look like with an agent layer. --- # Odoo Success Packs vs Partner Implementation: What Australian Businesses Are Actually Buying - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-success-packs-vs-partner-implementation-australia - Category: Odoo ERP Australia - Published: 2026-08-03 - Description: Odoo Success Packs give you prepaid consultant hours. A certified partner gives you a scoped project. Here's which approach fits Australian businesses and when. ## What Odoo Success Packs Are (and What They're Not) An Odoo Success Pack is a block of prepaid consulting hours sold directly by Odoo SA. You buy a pack upfront, and a dedicated Odoo consultant uses those hours to configure your system, import your data, train your team, and guide you through go-live. Five tiers are available, each priced in AUD at [odoo.com/pricing-packs](https://www.odoo.com/pricing-packs): - **Starter** (4 hours): AUD $915 returning / AUD $777.75 new customers - **Basic** (25 hours): AUD $5,500 returning / AUD $4,675 new - **Standard** (50 hours): AUD $10,000 returning / AUD $8,500 new - **Custom** (100 hours): AUD $19,000 returning / AUD $16,150 new - **Pro** (200 hours): AUD $37,000 returning / AUD $31,450 new New customers receive 15% off their first pack only. All figures are in AUD as shown at odoo.com/pricing-packs with AU localisation. Odoo reports a 98% implementation success rate for businesses using a Success Pack, compared to 65% for those who go it alone. The methodology draws on Odoo's own experience across tens of thousands of deployments globally. One important caveat: Success Packs are not a fixed-scope project with guaranteed deliverables. Once the hours are consumed, the engagement ends. If configuration takes longer than expected, additional hours or a new pack are required. Where custom code is written, Odoo SA charges ongoing monthly maintenance fees for that code. ## What a Partner Implementation Looks Like A certified [Odoo Silver Partner](/solutions/odoo) starts with a discovery phase: we scope your actual requirements, document them, and agree a project plan before any configuration begins. The engagement is deliverable-based, not hours-based. [Auboros's implementation packages](/odoo-implementation-packages-for-australian-businesses) describe the full approach. A mid-market project covers discovery and requirements mapping, environment setup, module configuration, data migration (contacts, products, transaction history, opening balances), user training, acceptance testing, and go-live support. What you are getting is agreed before anything is built. The [Odoo implementation services guide](/blog/odoo-erp-australia-6/odoo-implementation-services-australia-126) breaks each phase down in detail. The practical difference from a Success Pack is that a partner commits to outcomes rather than hours, and brings the local compliance knowledge your business needs throughout. ## The Australian Compliance Gap Here is where Success Packs run into a practical challenge for most Australian businesses. Setting up [Odoo's Australian localisation](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98) involves more than selecting a country during initial setup. BAS reporting, STP Phase 2 payroll, Payday Super configuration, and PAYGW tax tables each require deliberate configuration choices. Get them wrong and your first BAS lodgement needs manual corrections. As the [ATO's GST guidance](https://www.ato.gov.au/business/gst/) makes clear, correct tax accounting requires the right rounding method, accurate BAS label mapping, and proper input tax credit claims. In Odoo, this means fiscal position configuration, cash-versus-accruals reporting decisions, income account mapping, and super contribution routing via the Superchoice API. Odoo SA's consultants know the software thoroughly. They may not hold the local regulatory depth that an Australian certified partner carries as standard. This gap is least visible on the sales and CRM side. It matters most on the accounting, payroll, and tax reporting side. ## When a Success Pack Is the Right Call Some Australian businesses do suit the Success Pack model: - **Fewer than 50 users.** Odoo's own estimator flags companies above 50 users for a separate consultation rather than a standard pack. - **Standard workflows.** Sales, invoicing, and basic inventory without unusual pricing logic, complex product variants, or non-standard approval chains. - **One or two modules in scope.** Invoicing, CRM, and Inventory are well within a Standard or Custom pack. Add manufacturing, field service, payroll, and an API integration in the same engagement and the hours run short quickly. - **No complex data migration.** Importing a clean contacts list and product catalogue is manageable within a pack. Migrating several years of transaction history from MYOB AccountRight with open purchase orders and partial payments is not. - **A capable internal resource at go-live.** Success Pack consultants train your team; they do not operate the system after the engagement ends. Someone internally needs to own Odoo from go-live onward. For a small services business or a trades firm moving from spreadsheets to their first ERP, a Standard or Custom pack can represent solid value. ## When You Need a Certified Partner If your situation falls outside that profile, a partner-led implementation is the safer path: - You are migrating from Xero, MYOB AccountRight, or a legacy ERP and need transaction history carried across cleanly. - You need the Australian localisation correctly configured from day one: BAS, STP Phase 2, and Payday Super. - Your workflows are industry-specific: job costing for construction, project billing for professional services, multi-warehouse inventory, or field service scheduling. - You are integrating Odoo with another platform: Shopify, Starshipit, a third-party API, or a custom internal tool. - You have more than 25 concurrent users, or more than two business units going live simultaneously. - You need local, ongoing support from people who know your specific configuration. In these situations the hours model creates risk. Complex implementations frequently run 30 to 50 percent over initial estimates. When that overrun hits a prepaid block, the cost falls entirely on the business. > "The question I ask is: what does day 61 look like? If your team can self-manage from that point with what they have learned, a Success Pack can work. If you will need someone who knows your data, your compliance setup, and your specific configuration to keep things running, scoping the project properly from the start costs less in the long run." *Bill Alvarez, Practice Manager, Auboros* ## How the Costs Compare [MYOB's 2025 ERP Trends report](https://www.myob.com/au/insight/post/erp-trends) found that 45% of Australian businesses say disconnected systems are limiting their growth. The cost of an implementation that goes live with compliance errors, or that requires a second pass to fix the accounting configuration, typically exceeds the cost of getting it right the first time. A Standard pack (50 hours) costs AUD $8,500 for new customers. A Custom pack (100 hours) is AUD $16,150 for new customers. The full current AUD pricing is at [odoo.com/pricing-packs](https://www.odoo.com/pricing-packs). The [Odoo pricing guide](/blog/odoo-erp-australia-6/odoo-pricing-australia) covers subscription costs separately. For implementation, our [packages page](/odoo-implementation-packages-for-australian-businesses) shows fixed-scope project costs agreed before work begins rather than derived from a tier. One middle-ground approach that works for some businesses: begin with a Success Pack for a tightly contained scope (CRM and Invoicing only), then engage a local partner when adding payroll, a second integration, or a second business unit. This works only when the initial scope is genuinely contained and the team is prepared for the handover. To work out which path fits your situation, [book a time with the Auboros team](/appointment). We will give you a straight assessment. --- # MYOB Acumatica AI: What Australian Finance Teams Can Switch On Today - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/myob-acumatica-ai-australia - Category: AI & ERP - Published: 2026-08-03 - Description: What MYOB Acumatica AI can do today: AI Studio in preview, cross-sell and anomaly detection shipped, the Microsoft deal, and what is still roadmap for ANZ. Every few weeks another AI announcement lands from Acumatica, MYOB or Microsoft, and somewhere in Australia a finance manager opens their MYOB Acumatica tenant looking for the feature it described. Usually it isn't there yet. Sometimes the announcement covered the global Acumatica product, which runs months ahead of the ANZ release, and the feature won't arrive for two or three quarters. That gap causes real planning mistakes. So here's the sorted version: what MYOB Acumatica AI can do in the release Australian customers are actually running, what's in preview, and what's still a promise with a date attached. Everything below traces to a vendor source checked this month. ## What MYOB Acumatica AI includes today MYOB Acumatica AI currently means two shipped features plus one preview. The shipped features arrived in [the 25 R2 release](https://www.myob.com/au/insight/post/2026-r2-acumatica-release), MYOB's first major MYOB Acumatica release of 2026. The Cross-Sell Assistant analyses your historical sales data and suggests complementary products at the point of sale, so the cross-sell relationships don't need to be maintained by hand. For businesses on the Manufacturing Edition, Production Variance Anomaly Detection watches production costs, labour time and efficiency, and flags unusual movements so teams can investigate early instead of finding the problem in month-end reporting. Notice what both features have in common: they suggest and they flag. Neither posts a transaction, changes a price or touches the ledger. A salesperson decides whether to offer the suggested product. A production manager decides whether the flagged variance matters. That's the shape of AI we tell clients to trust first, and it's the same drafts-first pattern we apply to [AI agents over ERP data](/solutions/ai-agents) generally. Demand for this is not speculative. [MYOB's ERP Trends research](https://www.myob.com/au/insight/post/erp-trends) found 78% of wholesale distribution businesses plan to use AI in their ERP, and the [ABS reports](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25) that 12% of Australian businesses used AI in 2024-25, rising to 35% of large businesses. The question for most mid-market finance teams is no longer whether to use AI, it's which features are real in their release. ## AI Studio: describe an agent, get a draft The most interesting piece of 25 R2 is AI Studio, and it's important to label it correctly: tech preview now, with general availability planned for 26 R1. Existing customers can register interest with MYOB to join the preview. AI Studio lets you build small AI agents inside MYOB Acumatica using plain-language instructions. Describe the task, connect the agent to the relevant business data, and it generates the output inside the platform. MYOB's launch examples include drafting product descriptions for large catalogues, summarising supplier transaction history and preparing customer service responses. Here's how that looks as a worked pattern for a wholesale distributor. An agent reads your open purchase orders and each supplier's delivery history, identifies the orders most likely to slip based on that history, and drafts a chasing email for each one with the PO details filled in. The purchasing officer reads the drafts each morning, edits the two that misread the situation, and sends the rest. Nothing leaves the building without a person deciding it should. The agent removes the hour of looking things up, not the judgement. The architecture matters for Australian buyers. MYOB states that AI Studio is powered by AWS and Anthropic, that AI processing runs in local data centres so data never leaves Australian or New Zealand borders, and that your data is never used to train external models. If your business already has a preferred AI provider, you can connect that instead. Those are exactly the questions a CFO should ask of any AI feature, and it's notable that MYOB answered them in the launch material rather than in fine print. A preview is still a preview. Capabilities can change before general availability, and you shouldn't build a month-end process around a feature that's still being shaped. Use the preview window to learn where your data lets you down. ## Why Acumatica's AI headlines aren't in your system yet This is the part most coverage skips. Acumatica, the global platform MYOB Acumatica is built on, released its 2026 R1 update in March 2026, including an [AI Assistant that's rolling out under a managed availability program](https://community.acumatica.com/acumatica-news-updates-2/acumatica-ai-assistant-2026-r1-managed-availability-and-faq-34846) rather than as a general release. Global Acumatica announcements generate most of the AI headlines you'll read. MYOB Acumatica typically receives global Acumatica features 6 to 9 months after the global release, because MYOB localises each release for ANZ payroll, GST and compliance requirements before shipping it. The current MYOB Acumatica release is 25 R2. The global 2026 R1 features are not in it, and MYOB hasn't published a committed ANZ date for them. So when you read about an Acumatica AI capability, ask one question before it goes anywhere near a plan: which release is that in, and is it a MYOB release? Your partner should be able to answer from the release notes. If they can't, that tells you something too. ## What the Microsoft partnership promises, and when In April 2026, [MYOB and Microsoft signed a five-year partnership](https://www.myob.com/au/press-releases/myob-and-microsoft-sign-five-year-strategic-partnership-to-jointly-fund) to jointly fund and build AI features across MYOB's products, using Microsoft's Foundry, Copilot Studio and Agent 365 tooling. For MYOB Acumatica specifically, the announcement promises native AI features for contextual financial insights, natural-language queries and AI-assisted document processing. All of that is roadmap. The first jointly developed customer features are due later in 2026, and none of the promised MYOB Acumatica capabilities have shipped as of August 2026. The partnership is a credible signal of where the platform is heading, and the natural-language query direction lines up with what our clients keep asking for. But a signed partnership is not a feature in your tenant. Don't build a business case on it until release notes say otherwise. ## Switching things on safely The features above are the vendor's side of the story. The other side is yours: an AI feature is only as safe as the controls around it and only as useful as the data underneath it. The controls are the same ones we've written about for [AI agent governance](/blog/ai-erp-australia-8/ai-agent-governance-australia): role-scoped access so an agent sees only what the requesting user could see, human approval on anything that writes to the ledger or leaves the business, and an audit trail of what was suggested and who accepted it. If customer or employee data flows through an AI feature, check your obligations under the Australian Privacy Principles via the [OAIC's guidance on commercial AI products](https://www.oaic.gov.au/privacy/privacy-guidance-for-organisations-and-government-agencies/handling-personal-information/guidance-on-privacy-and-the-use-of-commercially-available-ai-products) before you switch it on. The data question decides more outcomes than the model does. > "The businesses getting value out of these previews aren't the ones with the most ambitious use cases. They're the ones with clean item files, tidy supplier records and consistent naming. Point an agent at messy data and you get confident drafts of the wrong thing." > > **Bill Alvarez, Practice Manager, Auboros** If you want to be ready rather than waiting, the useful work this quarter is unglamorous: clean the master data the first agents will read, decide which workflows you'd trust to drafts-first automation, register for the AI Studio preview, and put a one-page AI usage policy in front of your team. We covered what that looks like in practice in our guide to [what AI agents actually do inside Australian businesses](/blog/ai-erp-australia-8/ai-agents-for-australian-businesses-what-actually-works-in-2026-132), and the [reconciliation agent pattern](/blog/ai-erp-australia-8/ai-reconciliation-agent-erp-australia) shows the approval-gate design end to end. **Working out what MYOB Acumatica AI is worth to your business?** Auboros implements and supports [MYOB Acumatica](/solutions/myob) across Queensland and beyond, and we run AI agents against live ERP systems in our own operations, so we can tell you which of these features will earn their keep in yours. [**Book a free consultation**](/appointment) and we'll go through it with your data, not a demo script. No pressure either way. --- # MYOB Acumatica for Aged Care and Community Services Providers in Australia - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-aged-care-community-services-australia - Category: MYOB Acumatica Australia - Published: 2026-08-03 - Description: How MYOB Acumatica supports aged care and community services providers: NDIS billing, fund tracking, multi-entity finance and the new Aged Care Act rules. Aged care and community services providers are running finance functions that would stretch businesses twice their size. A single mid-sized provider might juggle NDIS plan-managed and agency-managed billing, Support at Home funding, state grants, donations and fee-for-service work, each with its own reporting rules, across several legal entities. Most are doing it on accounting software built for a cafe. This post covers what MYOB Acumatica handles well for care providers, and just as importantly, what it doesn't try to do. ## Why care providers outgrow small business accounting The pressure isn't transaction volume. It's structure. Every funding stream a provider takes on needs to be tracked separately, acquitted separately and reported separately. The [NDIS now supports more than 739,000 Australians](https://www.ndis.gov.au/news/10850-stronger-ndis-improving-lives-participants), and the providers serving them must show exactly how funded dollars became delivered services. Grant funders want the same. So does the board. Small business accounting tools give you one profit and loss statement and a tracking-category workaround. That holds until the third funding program or the second entity, when month-end becomes a spreadsheet exercise stapled onto the accounting file. If that's where you are, the limitation is structural, and no amount of extra effort at month-end fixes structure. ## What MYOB Acumatica handles well for aged care and community services [MYOB Acumatica](https://www.myob.com/au/erp-software/products/myob-acumatica) is a mid-market ERP, and the parts of it that matter most here are the unglamorous ones. Multi-entity financials with automated intercompany accounting suit providers running separate entities for housing, services and fundraising. The [project accounting module](/blog/myob-acumatica-australia-7/myob-acumatica-project-accounting-australia-123) does the fund and program tracking: each program, grant or funding stream becomes a project with its own budget, costs and revenue, so acquittal reports come from the ledger rather than a reconstruction. General ledger sub-accounts let you report by program, location and funding source without maintaining parallel charts of accounts. Payroll handles Single Touch Payroll and the award complexity that comes with a large part-time and casual workforce, and with Payday Super now live, super timing is worth specific attention; our [Payday Super checklist for MYOB Acumatica](/blog/myob-acumatica-australia-7/myob-acumatica-payday-super-australia) covers what to verify. For ACNC-registered providers, the fund accounting patterns we described for [not-for-profit organisations](/blog/myob-acumatica-australia-7/myob-acumatica-not-for-profit-australia-109) and [religious organisations](/blog/myob-acumatica-australia-7/myob-acumatica-religious-organisations-australia) apply directly. ## The honest limitation: it is not care management software MYOB Acumatica will not roster support workers, manage care plans, record progress notes or submit NDIS payment requests through PRODA. Purpose-built care management platforms do that, and providers of any size generally need one. Anyone who tells you an ERP replaces care management software is selling you a rebuild you'll regret. The realistic architecture is a pairing: the care management platform runs service delivery and generates billing data, and the ERP is the financial backbone that turns that data into invoices, funding claims, payroll and board reporting. MYOB Acumatica's REST API is what makes the pairing workable, moving billing exports and timesheet data across without manual re-keying. Scoping that integration properly is most of the work, which is why we treat it as a first-class part of any [MYOB Acumatica implementation](/solutions/myob) for a care provider rather than an afterthought. > "Care providers don't fail audits because their care records are bad. They get into trouble when the money side can't show which program paid for what. That's the gap the ERP closes, and it's the part the sector's software conversation keeps skipping." > > **Bill Alvarez, Practice Manager, Auboros** ## The compliance backdrop keeps raising the bar The regulatory ground has shifted under the sector. The [new Aged Care Act commenced on 1 November 2025](https://www.health.gov.au/our-work/aged-care-act), bringing a rights-based framework and strengthened provider obligations. The same day, the [Support at Home program](https://www.health.gov.au/our-work/support-at-home) replaced Home Care Packages, changing how home care funding flows and is accounted for, with the Commonwealth Home Support Programme to follow no earlier than 1 July 2027. None of this is accounting software's job to solve on its own. But every reform lands the same way in the finance team: new funding categories, new reporting lines, new evidence requirements. A finance platform that can add a funding stream as configuration, rather than as a restructure, is what makes the next reform absorbable. Providers still assembling reports from spreadsheets will feel each change twice. ## When it fits, and when it doesn't MYOB Acumatica makes sense for providers around the 30-plus staff mark with multiple funding streams, multiple entities or both, and a finance team that has clearly outgrown its current tools. Below that size, well-configured small business accounting plus a good care management platform is usually the right answer, and we'll say so. Genuine multinationals and very large residential groups have platform options with deeper sector-specific modules, and an honest scoping conversation covers those too. **Running finance for an aged care or community services provider?** Auboros implements MYOB Acumatica from Brisbane for organisations across Queensland and the rest of Australia, including the care management integrations that make it work day to day. If your funding streams have outgrown your accounting file, [**book a free consultation**](/appointment) and we'll map what a right-sized setup looks like. No obligation either way. --- # Odoo Community vs Enterprise: The Australian Decision - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-community-vs-enterprise-australia - Category: Odoo ERP Australia - Published: 2026-08-03 - Description: Odoo Community is free and open source. Enterprise adds accounting, payroll and Australian compliance. Here's how to choose the right edition in 2026. Ask five Odoo consultancies whether you need Odoo Enterprise and you'll get five versions of "yes". The honest answer is more useful: some Australian businesses are well served by the free Community edition, and pretending otherwise costs them money and trust. But the two editions differ in ways that matter a great deal here, particularly around accounting, payroll and compliance. Here's how we walk clients through the decision. ## What Odoo Community actually gives you Odoo Community is the open source core of the platform, released under the [LGPLv3 licence](https://www.odoo.com/documentation/19.0/legal/licenses.html). It is free in the full sense. There's no per-user fee, no trial clock, and no artificial record limits. You download the source, host it yourself, and run it for as long as you like. That core is substantial. Community includes CRM, sales, purchasing, inventory, manufacturing, project management, basic invoicing, website building and eCommerce. A wholesaler running quotes, stock and purchase orders through Community is using real ERP functionality, not a demo. What you take on in exchange is responsibility. Community is self-hosted, so your business (or a partner) manages the server, backups, security patches and version upgrades. There's no official support desk from Odoo SA and no access to the official upgrade service. When something breaks at 4pm on BAS day, the person fixing it is whoever you've arranged in advance. ## Odoo Community vs Enterprise: what sits behind the paid licence Odoo Enterprise is built on top of Community, and [Odoo's official editions comparison](https://www.odoo.com/page/editions) sets out the split. The Enterprise subscription adds the applications most finance teams consider core: full accounting with bank feeds and reconciliation, payroll, field service, helpdesk, marketing automation, quality, and Odoo Studio for no-code customisation. It also unlocks the hosted platforms (Odoo Online and Odoo.sh), official support from Odoo SA, and the free upgrade service that moves your database between versions. Two things people often get wrong about Enterprise. First, the source code is not locked away: every Enterprise subscriber can access the Enterprise source, so you're not trading open source flexibility for a black box. Second, you don't need a partner to talk to Odoo SA. Any Enterprise customer can contact Odoo support directly; a partner adds implementation depth and local context, not gatekeeping. ## The Australian compliance question For most Australian businesses, this section decides it. The Australian accounting localisation that produces BAS reports, handles GST mapping and connects payroll to Single Touch Payroll sits in the Enterprise edition. Odoo's [Australian fiscal localisation documentation](https://www.odoo.com/documentation/19.0/applications/finance/fiscal_localizations/australia.html) covers what's included: BAS reporting, an ATO-aligned chart of accounts, employee super handling and STP submission. [Single Touch Payroll](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll) is not optional for Australian employers, so a business planning to run payroll inside Odoo needs Enterprise, full stop. On Community, the realistic patterns are running a separate Australian payroll product alongside Odoo, or handling accounting in another system entirely and using Community for operations. Both patterns work. We've written before about how that plays out in our [guide to Odoo's Australian localisation](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98). > "The businesses that do well on Community are the ones that chose it deliberately, with a plan for hosting, upgrades and accounting. The ones that struggle picked it because it was free and discovered the gaps at tax time." > > **Josh Craig, Director, Auboros** ## What each edition costs in practice Community's licence cost is zero, but running it isn't. Budget for hosting, backups, someone to apply security updates, and periodic upgrade work, which on Community is a technical project rather than a button. For a small team this might be a few hundred dollars a month in hosting and occasional developer time; it's real money, just spent differently. Enterprise is priced per user per month. As of August 2026, the Standard plan is AUD $34.40 per user per month and the Custom plan (which adds Studio, multi-company and the external API) is AUD $52.00, with a free single-app tier also available. Odoo adjusts pricing periodically, so check [the live pricing page](https://www.odoo.com/pricing) before budgeting. The subscription includes the hosted platform, support and upgrades, which is exactly the overhead Community asks you to carry yourself. Our [Odoo pricing guide for Australia](/blog/odoo-erp-australia-6/odoo-pricing-australia) breaks down the full cost picture, implementation included. ## When Community is the right call We recommend Community more often than you might expect from a partner that sells Enterprise implementations. It fits when the business has genuine technical capability in-house or on retainer, when accounting and payroll are staying in an existing system, and when the need is operational: inventory, manufacturing, projects, CRM. It also fits organisations philosophically committed to open source, and developers building products on the Odoo framework. Community is not a crippled trial. It's a complete platform for the right use case, and moving from Community to Enterprise later is a standard, supported path rather than a re-implementation. We support both editions through [our Odoo Community services](/solutions/odoo-community), including hosting setup, bespoke module development and retainers for sites we didn't build. ## When Enterprise earns its fee Enterprise is the right choice when Odoo will be your accounting system, when you run Australian payroll, when you want the hosted platform rather than managing servers, or when Studio-level customisation without developer time matters. In our experience that describes most Australian SMEs who want one system rather than three. The subscription buys compliance features you'd otherwise have to build or bolt on, plus an upgrade path that doesn't depend on a developer's weekend. If you're weighing the editions as part of a broader platform decision, our [Odoo implementation services](/solutions/odoo) page covers how we scope both, and the free consultation below is a sensible first step either way. **Deciding between Odoo Community and Enterprise?** Auboros implements both editions from Brisbane for businesses across Australia and New Zealand, and we'll tell you plainly if the free one is all you need. If you want a straight answer on which edition fits your operation, [**book a free consultation**](/appointment). Thirty minutes, no pitch deck. --- # AI Agent Governance for Australian Businesses: The Controls That Make Agents Safe to Run - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-agent-governance-australia - Category: AI & ERP - Published: 2026-08-01 - Description: What AI agent governance means for Australian businesses: role-scoped permissions, approval gates, audit trails, and the 10 December 2026 privacy deadline. Most Australian businesses experimenting with AI agents hit the same wall. The pilot works, the demo impresses, and then someone in the room asks the question that stalls everything: what happens when the agent gets something wrong in the accounts? That question deserves a real answer, not reassurance. AI agent governance is the set of rules, permissions and human checkpoints that determine what an AI agent can see, what it can do, who approves its work before it takes effect, and what record exists afterwards. Done well, it's the difference between an agent that drafts a supplier payment run for a person to review and an agent that can quietly post journal entries nobody checked. This post sets out the governance controls we use when wiring [AI agents into Odoo and MYOB Acumatica](/solutions/ai-agents) for Australian businesses. It maps those controls to the Australian Government's current guidance, and covers a privacy deadline arriving on 10 December 2026 that most AI content hasn't noticed yet. ## What AI agent governance actually covers Strip away the jargon and governance answers four questions about every agent you run. - **Access: what can the agent see?** Which records, which modules, whose data. An agent that triages customer service emails doesn't need to read payroll. - **Action: what can the agent do?** Reading and drafting are low-stakes. Creating, updating or deleting records is not. Each action an agent can take should be deliberately granted, not inherited by default. - **Approval: who checks the work?** For anything that touches the ledger, tax, pricing or stock, the answer should be a named person, every time. - **Audit: what record exists afterwards?** When someone asks why the agent recommended a credit hold in March, you need more than a shrug. Getting these four answers written down matters more than any tool choice. The [Australian Bureau of Statistics reports that around 12% of Australian businesses used AI in 2024-25](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25), and around 35% of large businesses. Very few of them adopted it with anything like this written down first. ## Why agents connected to your ERP raise the stakes A chatbot that writes a clumsy paragraph costs you a minute of editing. An agent connected to your ERP operates at a different scale entirely. It can touch hundreds of records in the time it takes you to read this sentence, and ERP records are not drafts. They're your ledger, your tax position, your stock levels and your customer pricing. The failure mode isn't dramatic. It's quiet. An agent that miscodes GST on supplier bills doesn't create one visible error, it creates a Business Activity Statement (BAS) discrepancy you'll discover at quarter end, spread across everything it processed. Large language models make mistakes, and any vendor telling you otherwise is selling something. The honest engineering response is to design so that mistakes get caught before they post, rather than promising an accuracy figure nobody can stand behind. That design is what the rest of this post is about. The demand is real, so the governance question isn't going away. In wholesale distribution, [MYOB's ERP research found 78% of businesses plan to adopt AI in their ERP](https://www.myob.com/au/insight/post/erp-trends). The gap between that intent and a safe rollout is exactly the set of controls below. ## Australia's AI6 practices, applied to AI agent governance Australia doesn't have a standalone AI Act. The current reference point is the National AI Centre's [Guidance for AI Adoption](https://www.ai.gov.au/staying-safe-and-responsible/essential-ai-practices/guidance-ai-adoption-implementation-guidance), published in October 2025, which replaced the earlier Voluntary AI Safety Standard. It's voluntary, but it's also a sensible checklist, and it sets out six essential practices. Here's what each one looks like when the AI in question is an agent working against your ERP. - **Decide who is accountable.** Every agent gets a named owner, a person, not a department. If the reconciliation agent misbehaves, someone specific owns switching it off and cleaning up. - **Understand impacts and plan accordingly.** Before an agent goes near a process, write down which records it touches, whose personal information is involved, and who's affected if it's wrong. - **Measure and manage risks.** Keep a short risk register per agent: what can go wrong, how you'd notice, what the blast radius is. Ten minutes of writing, disproportionate value. - **Share essential information.** Staff should know which processes involve an agent and customers shouldn't have to guess whether they're corresponding with software. - **Test and monitor.** Sandbox first, then ongoing spot checks of approved outputs. Testing continues for as long as the agent runs. - **Maintain human control.** For ERP agents this is concrete: a human approval gate on every write to ledger, tax, pricing or stock. Not most writes. Every write. If you've read our broader piece on [AI agents for Australian businesses](/blog/ai-erp-australia-8/ai-agents-for-australian-businesses-what-actually-works-in-2026-132), you'll recognise these themes. This is the deeper layer: the practices turned into system design. ## Permissions: an agent should act as a person, not as an administrator The single most common governance mistake we see is the shared super-user. The agent gets an administrator login because it's easy, and suddenly a piece of software that occasionally hallucinates has more access than your financial controller. The better pattern is role-scoped access. The agent acts with the permissions of the person who asked, or with a purpose-built role that grants the minimum it needs. A sales rep asking an agent about customer credit status should get an answer scoped to what that rep is allowed to see. The agent should not have a private backdoor to the whole database. The Australian Cyber Security Centre's joint guidance on the [careful adoption of agentic AI services](https://www.cyber.gov.au/business-government/secure-design/artificial-intelligence/careful-adoption-of-agentic-ai-services) recommends the same discipline: restrict agent tools to an approved allowlist, log agent activity, and restrict permissions automatically when behaviour looks unexpected. Platform design is starting to reflect this. In Odoo 19, for example, the tools an AI agent can call are server actions a developer has explicitly flagged for AI use, an allowlist by design. We cover the platform's built-in features in [AI in Odoo](/blog/odoo-erp-australia-6/ai-in-odoo-australia-2026-102) and the agent mechanics in [AI agents in Odoo](/blog/ai-erp-australia-8/odoo-ai-agents-australia). ## Approval gates: drafts first, always Here's the pattern that makes agents safe enough for finance work, using a job we build often. Each morning an agent reads the overnight bank feed and the open items in the ERP. It matches what it can, and for everything else it drafts a proposed resolution: this deposit looks like invoices 4312 and 4318 paid together short of $12.40, suggest matching both and writing off the difference as a bank fee. The bookkeeper opens a queue of these proposals with their coffee, approves most, rejects a few, and the approved ones post. The agent never posts anything itself. On a messy day the human is still in charge of the mess. That's drafts-first design, and it applies to every pattern we deploy: inbound purchase orders drafted as sales orders, credit control emails drafted for review, service replies drafted but never sent by the agent. The agent removes the repetitive work. The person keeps the judgement and the send button. > "The approval gate isn't a training-wheels phase you graduate out of. It's the design. The day someone removes it to save five minutes is the day the agent's mistakes start posting straight to the ledger." > > **Bill Alvarez, Practice Manager, Auboros** ## Audit trails and the 10 December 2026 privacy deadline Every agent action, proposal and approval should be logged: what the agent read, what it proposed, who approved it and when. Partly this is operational, because you'll want to trace errors. Increasingly it's also regulatory. From 10 December 2026, amendments to the Privacy Act require organisations to disclose in their privacy policies the kinds of decisions made using substantially automated processes that significantly affect people's rights or interests, and the kinds of personal information used to make them. The [OAIC is consulting on its guidance now](https://www.oaic.gov.au/engage-with-us/consultations/consultation-on-guidance-for-transparency-in-automated-decision-making) and expects to publish it before the obligation starts. Think about what that covers in an ERP context. An agent that recommends credit holds on customer accounts is using personal information to do something directly related to a decision that affects someone's interests. So might automated collections prioritisation or customer-facing pricing decisions. If agents touch decisions like these, your privacy policy will likely need updating before December, and that's a conversation to have with your privacy adviser now rather than in November. We're not lawyers, but we do design the audit trails that make the disclosure honest. ## Sandbox first: rolling out without betting the ledger We stage every agent rollout the same way, and recommend the sequence to anyone building their own. 1. **Sandbox with a copy of real data.** The agent runs against a duplicate of your ERP. Wrong answers cost nothing and teach a lot. 2. **Production, drafts only.** The agent works on live data but everything it produces sits in a review queue. You're measuring how often its proposals get approved unchanged. 3. **Narrow scope, then widen.** Start with one bank account, one customer segment, one document type. Expand when the approval rate has earned it. 4. **Scheduled permission reviews.** Put a recurring date in the calendar to re-check what each agent can access. Scope creep happens to agents just like it happens to staff accounts. One prerequisite deserves its own sentence: data hygiene. An agent reasoning over a customer file full of duplicates and stale credit limits will produce confident nonsense. Cleaning the data isn't a side quest, it's step zero. ## The policy pack: five documents worth having None of this needs a compliance department. For most mid-sized businesses the whole pack fits in a handful of pages. - **An AI usage policy** that staff actually sign: which tools are approved, what data can and can't go into them, and who to ask. The National AI Centre publishes a policy template alongside the AI6 guidance if you want a starting point. - **An agent register:** every agent you run, its owner, what it can access, and what approval gate sits in front of it. - **A risk register** per agent: failure modes, how you'd detect them, blast radius. - **An approved-tool allowlist:** which models, platforms and connectors are sanctioned, so shadow AI doesn't creep in through a browser tab. - **A permission review schedule:** quarterly is plenty for most businesses. If you have those five and the drafts-first pattern, you're ahead of the overwhelming majority of Australian businesses running AI today, and you're positioned to expand agent use without the board meeting turning nervous. --- **Thinking about AI agents but stuck on the governance question?** Auboros designs and runs drafts-first AI agents over Odoo and MYOB Acumatica from Brisbane, with role-scoped permissions, approval gates and audit trails built in from day one. If you want an agent working your reconciliations, orders or credit control without betting the ledger on it, [**book a free consultation**](/appointment). We'll tell you what's worth automating and what isn't yet. --- # How Long Does a MYOB Acumatica Implementation Take in Australia? - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-implementation-timeline-australia - Category: MYOB Acumatica Australia - Published: 2026-08-01 - Description: Realistic MYOB Acumatica implementation timelines for Australian businesses: what each phase involves, what stretches projects, and when 12 weeks is possible. The short answer: most MYOB Acumatica implementations we see in Australia take three to six months from kickoff to go-live. A tightly scoped, single-entity project can be done in around 12 weeks. A multi-entity rollout with custom integrations can stretch past nine months. The range is wide because the timeline is set less by the software and more by decisions, data and how much change your team can absorb at once. Here's how the time actually gets spent, and where projects lose or save weeks. ## The phases of a MYOB Acumatica implementation Every partner structures this slightly differently, but the shape is consistent: - **Discovery and scoping, 2 to 4 weeks.** Workshops to map how you quote, sell, buy, ship and report. This is where the fixed-price number and the timeline get set, so shortcuts here surface later as variations. - **Build and configuration, 4 to 8 weeks.** Company setup, chart of accounts, workflows, user roles, forms and reports. Runs partly in parallel with data work. - **Data migration, 2 to 6 weeks.** Cleaning and loading customers, suppliers, items, opening balances and open transactions. Almost always the phase people underestimate, because the effort sits with your team, not the partner. - **User acceptance testing, 2 to 4 weeks.** Your people run real scenarios end to end and log what doesn't work. The projects that skimp on UAT pay for it in the first month live. - **Training and go-live, 1 to 2 weeks.** Role-based training close to the cutover date, then the switch, then a hypercare period where the partner is on call daily. Add those up and you get roughly 11 to 24 weeks, which matches what we see in practice. ## What stretches a timeline, and what doesn't Company size matters less than people expect. A 40-person wholesaler with standard processes will go live faster than a 15-person business that wants every screen changed. The real stretch factors are customisation beyond configuration, each integration to another system, and data quality. Dirty data is the most common one. If your item file has 12,000 SKUs and 4,000 are dead, someone has to make 4,000 decisions before load day. The quietest one is decision speed. An implementation asks your business to make hundreds of small calls: how jobs are coded, who approves purchases, what the invoice should look like. If each one takes a week in committee, the calendar goes with it. [Capterra's Australian research](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/) found fewer than one in three businesses successfully adopt new software, and stalled internal decisions are a bigger cause than failed technology. > When a client asks how long it will take, the honest answer is: as long as your slowest decision. The platform work is predictable. The calendar risk sits in approvals, data sign-off, and how much change the team can take on while doing their day jobs. > > **Josh Craig, Director, Auboros** ## When 12 weeks is realistic Fixed-scope programs exist precisely to compress this. We deliver [MYOB's FastStart program for wholesale distribution](/solutions/myob-acumatica-faststart-wholesale-distribution) in Queensland, which packages a defined scope into a 12-week go-live. The trade-off is the point: you adopt standard processes rather than redesigning your own, customisation is limited, and the data templates are fixed. For a distribution business that mostly runs on standard workflows, that trade is usually worth making. For a business with unusual processes it's the wrong tool, and a good partner will say so in the first meeting. With [48% of mid-sized Australian businesses citing operational efficiency](https://www.myob.com/au/insight/post/mid-market-survey-results-2025) as their main driver for upgrading systems, there's a reason the fixed-scope route keeps growing: the sooner you're live, the sooner the efficiency shows up. ## Payroll runs on its own clock If payroll is in scope, plan it as a parallel workstream. Payroll go-lives in Australia carry their own compliance load: [Single Touch Payroll](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll) onboarding, award and pay item setup, and at least one parallel pay run against the old system before anyone trusts the new one. Payday Super, live since 1 July 2026, adds timing rules worth checking during setup; we covered the details in our [Payday Super checklist for MYOB Acumatica](/blog/myob-acumatica-australia-7/myob-acumatica-payday-super-australia). Many businesses sensibly cut payroll over at a different date from finance and operations, often at the start of a financial year or quarter. ## How to keep your project on schedule Four things separate the projects that land on time from the ones that drift: - **One decision-maker with real authority.** A named person who can settle process questions inside 48 hours. - **Start data cleaning at contract signing.** It's the longest lead-time item and it belongs to you, not the partner. - **Resist redesigning everything.** Adopt standard where standard works. Park the nice-to-haves on a phase 2 list and actually revisit it at 90 days. - **Protect your team's time.** UAT and training done in stolen half-hours produce a go-live that feels like an ambush. What a partner does during each of these phases, and how to choose one, is a topic on its own. We've written about [what a MYOB Acumatica partner actually does](/blog/myob-acumatica-australia-7/myob-acumatica-partner-australia-what-they-do-how-to-engage-and-how-to-pick-one-127) and [how implementation costs are structured](/blog/myob-acumatica-australia-7/myob-acumatica-cost-australia) if you're weighing this up. **Wondering what your timeline would actually look like?** As an official MYOB Acumatica Partner working with [mid-market businesses across Queensland and beyond](/solutions/myob), we scope timelines against your data, your integrations and your team's capacity rather than a template. [**Book a free consultation**](/appointment) and we'll give you a realistic range for your situation, including whether a 12-week program fits. --- # Odoo Data Migration Checklist for Australian Businesses - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-data-migration-checklist-australia - Category: Odoo ERP Australia - Published: 2026-08-01 - Description: The Odoo data migration checklist we use on Australian projects: what to clean, what to leave behind, GST mapping, opening balances and cutover timing. Most of the hard work in an ERP move has nothing to do with configuring software. It's the data. [36% of mid-sized Australian businesses](https://www.myob.com/au/insight/post/mid-market-survey-results-2025) are looking to upgrade their core business systems, and the projects that hurt usually hurt at the same point: getting years of accumulated records out of the old system and into the new one in a state anyone can trust. We've published detailed guides on [moving from Xero to Odoo](/blog/odoo-erp-australia-6/xero-to-odoo-migration-australia) and [moving from MYOB AccountRight to Odoo](/blog/odoo-erp-australia-6/myob-accountright-to-odoo-migration-australia). This post is the checklist that sits underneath both, and underneath [our ERP migration service](/solutions/erp-migration) more broadly. It's the sequence we work through on every Odoo data migration, whatever the source system. ## Decide what you won't migrate Start here, because this decision shapes everything that follows. You have three realistic options for historical transactions. Bring the full history across, bring opening balances plus open items only, or post monthly summary journals for the prior year or two. Full history sounds appealing and is almost never worth it. Every historical invoice you import has to carry the right GST code, the right contact, and the right account mapping, and one systematic error multiplied across five years of transactions is a very expensive cleanup. The [ATO requires you to keep business records for at least five years](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/record-keeping-for-business), but nothing in those rules says the records have to live inside Odoo. A complete export of the old system, kept somewhere accessible, satisfies the requirement. Most of our clients keep read-only access to the old platform for a few months and an archived export after that. ## Master data: the part worth being fussy about Master data is what you'll live with for the next decade, so this is where the cleaning effort belongs. - **Customers and suppliers.** Merge duplicates before export, not after import. Check ABNs, billing contacts and payment terms. If a record hasn't transacted in two years, ask whether it needs to come across at all. - **Products.** Confirm units of measure are consistent and decide your costing method now. FIFO or average cost is a setup decision in Odoo, and changing it after you're live is painful. - **Chart of accounts.** Migration is your one clean chance to restructure. Collapse the 40 unused accounts your old file collected. Odoo's Australian chart is a sensible starting point; map to it rather than recreating the old mess. - **GST tax codes.** Odoo's [Australian localisation](https://www.odoo.com/documentation/19.0/applications/finance/fiscal_localizations/australia.html) ships with standard GST codes wired to BAS reporting. Map every tax code in your old system to its Odoo equivalent before you import a single transaction. This one spreadsheet tab prevents most BAS problems later. ## Opening balances and open items Your trial balance at the cutover date needs to land in Odoo to the cent. That part is mechanical. The detail that catches people is open items: unpaid customer invoices and supplier bills should come across as individual records, not one lump balance, because incoming payments need real invoices to match against. The same goes for unpresented bank transactions sitting in your old reconciliation. > The migrations that go badly are almost never a software problem. They're a deciding problem. Nobody agreed early on what the new system didn't need to hold, so everything came across, mess included. > > **Josh Craig, Director, Auboros** ## Test your Odoo data migration before the real one Odoo imports master data and balances from spreadsheets, and the [import tooling](https://www.odoo.com/documentation/19.0/applications/essentials/export_import_data.html) is usable by non-developers for master data. That makes it tempting to go straight to the real load. Don't. Load your files into a staging database first. Reconcile the trial balance against the old system, open ten customers and check their details end to end, raise a test invoice and confirm the GST lands in the right BAS field. Then wipe it and run the real migration with the corrections applied. [Capterra's Australian research](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/) found fewer than one in three businesses successfully adopt new software, and mistrusted data is one of the quiet reasons. If the sales team's first search in the new system returns a duplicated customer with an old address, you've lost credibility you'll spend months earning back. Your first [bank reconciliation in Odoo](/blog/odoo-erp-australia-6/odoo-bank-reconciliation-in-australia-statement-feeds-aba-matching-and-keeping-bas-tidy-131) is the moment of truth. If the migration was clean, it's boring. Boring is the goal. ## Time the cutover to a BAS quarter The cleanest cutover date in Australia is the first day of a BAS quarter: 1 July, 1 October, 1 January or 1 April. Each BAS then comes entirely from one system, and your accountant will thank you. Cutting over mid-quarter means splitting a BAS across two systems, which is doable and never fun. One caveat we apply on every project: payroll is its own workstream with its own timeline. We scope payroll cutover separately from the finance and operations migration, and it often makes sense to run it on a different date. ## The checklist in one place - **Scope the history.** Decide what comes across: opening balances and open items for most businesses. - **Archive the source.** Full export of the old system, stored where you can reach it for five years. - **Clean master data.** Duplicates merged, ABNs checked, dead records culled. - **Map GST codes.** Every old tax code matched to an Odoo equivalent, reviewed by your accountant. - **Test load.** Staging database, trial balance reconciled to the cent, sample records checked. - **Real load and cutover.** First day of a BAS quarter, open items imported individually. - **Verify.** First bank reconciliation clean, first BAS reviewed against the old system's final one. **Planning an Odoo migration and not sure what your data will throw at you?** Our Brisbane team runs migrations for Australian businesses moving off Xero, MYOB and older ERPs as part of [our Odoo implementation work](/solutions/odoo), using the checklist above. [**Book a free consultation**](/appointment) and we'll tell you honestly how messy your migration is likely to be, and what we'd leave behind. --- # MYOB Acumatica for Religious Organisations in Australia: Funds, Parishes, and ACNC Reporting - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-religious-organisations-australia - Category: MYOB Acumatica Australia - Published: 2026-08-01 - Description: How MYOB Acumatica handles fund accounting, multi-entity parish structures, ACNC reporting, grants and clergy payroll for Australian religious organisations. Religious organisations run some of the most complicated books in the not-for-profit world. A single denomination might hold dozens of congregations, a property trust, an aged care arm, a school partnership, and an op shop, each with its own bank accounts, its own restricted funds, and its own volunteer treasurer. The money is rarely the problem. Knowing which fund every dollar belongs to, and proving it to a board, an auditor, or a denominational assembly, is where small accounting software runs out of road. This post covers how MYOB Acumatica, the platform formerly sold as MYOB Advanced, handles religious organisation finance, and when it's the right size for the job. ## Why religious organisation finance is harder than it looks Most congregational giving arrives with strings attached. A building fund gift can't quietly cover the electricity bill, a mission appeal can't fund office wages, and a bequest may carry conditions that outlive everyone who received it. That's fund accounting, and general-purpose accounting software doesn't really do it. Treasurers end up approximating funds with account codes and spreadsheets, which works until the first serious audit question. The structure question is just as real. Parishes, circuits, presbyteries, dioceses, and their agencies are often separate entities that still need to roll up into one denominational view. And the compliance layer sits on top: the ACNC's [latest Australian Charities Report](https://www.acnc.gov.au/tools/reports/australian-charities-report-12th-edition) counts more than 8,000 charities reporting as Basic Religious Charities, a category with its own rules. A [Basic Religious Charity](https://www.acnc.gov.au/manage-my-charity-type/basic-religious-charities) is exempt from lodging annual financial reports, but the exemption has edges: a charity that receives more than $100,000 in government grants in the current or previous two reporting periods loses BRC status, and so does one registered under any charitable subtype beyond advancing religion. Here's the honest bit: the BRC exemption doesn't mean the books can be loose. Boards, members, insurers, lenders, and denominational bodies still expect proper reporting, and any entity that grows past the BRC boundary lands in full ACNC financial reporting with whatever records it kept along the way. ## How MYOB Acumatica handles religious organisations ### Funds, appeals, and money with conditions MYOB Acumatica is a [cloud ERP platform](https://www.myob.com/au/erp-software/products/myob-acumatica) built for mid-market Australian organisations, and its structure suits fund-based finance. Subaccounts let you segment the general ledger by fund, campus, or ministry, so a building fund balance is a real ledger balance rather than a spreadsheet estimate. For grants, appeals, and bequests with acquittal conditions, [project accounting](/blog/myob-acumatica-australia-7/myob-acumatica-project-accounting-australia-123) tracks income and spending against each one, with budgets and committed costs visible while the money is being spent, not after. ### Parishes, agencies, and one consolidated view Multi-entity support is where the platform separates itself from congregation-sized software. Each entity keeps its own ledger, its own bank accounts, and its own reporting, while inter-entity transactions and consolidation happen inside the system instead of in a year-end consolidation workbook. For a diocese or state body, that means a treasurer in a regional parish and the finance office in Brisbane are working in the same system with very different views of it. ### Volunteer treasurers and audit trails Role-based access matters more in religious organisations than almost anywhere else, because so much of the finance work is done by volunteers. Access can be scoped so a local treasurer sees their entity and nothing else, approvals route to the right people automatically, and every change carries an audit trail. When the auditor or a denominational review asks who changed what and when, the answer is in the system. ## Clergy payroll, FBT, and tax concessions Paying clergy is its own discipline. The ATO treats [benefits provided to religious practitioners](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/fringe-benefits-tax/fbt-concessions-for-not-for-profit-organisations/fbt-and-religious-institutions) by registered religious institutions as exempt from fringe benefits tax when they're provided principally for pastoral duties, which is why stipend packages are often structured with housing and other non-cash components. Registered religious institutions can also access [broader tax concessions](https://www.ato.gov.au/businesses-and-organisations/not-for-profit-organisations/getting-started/in-detail/types-of-charities/tax-concessions-for-acnc-registered-religious-institutions) tied to their ACNC registration. The rules are specific and worth professional advice, but the practical point for software is this: payroll needs to handle mixed lay and clergy arrangements, allowances, and Single Touch Payroll reporting in one place. That's standard territory for the platform's payroll, which we covered in detail in our [MYOB Acumatica payroll guide](/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97). ## When it fits, and when it doesn't A single congregation with one bank account, a part-time bookkeeper, and simple giving doesn't need an ERP, and we'd tell you that in the first ten minutes. MYOB Acumatica earns its keep when several of these are true at once: - **Multiple entities or sites** that need their own books plus a consolidated denominational view. - **Restricted funds, appeals, or bequests** that must be tracked and acquitted properly, not approximated. - **Paid staff across entities**, with mixed clergy and lay payroll arrangements. - **Grant funding near or past the BRC threshold**, where full ACNC financial reporting is on the horizon. - **Volunteer treasurers at the edges** who need safe, limited access to a shared system. If that list sounds familiar, the platform sits in the same family of use cases as our posts on [member-based organisations](/blog/myob-acumatica-australia-7/myob-acumatica-for-membership-organisations-australia-92) and [not-for-profits](/blog/myob-acumatica-australia-7/myob-acumatica-not-for-profit-australia-109), with the religious layer of funds, entities, and clergy arrangements on top. > Religious organisation books fail in a particular way. The money is all there, but nobody can say with confidence which fund it belongs to. Once the funds are real ledger structures instead of a treasurer's spreadsheet, most of the audit stress disappears with them. > > **Bill Alvarez, Practice Manager, Auboros** **Running finance for a parish, diocese, or faith-based organisation?** Auboros is a Brisbane-based [MYOB Acumatica partner](/solutions/myob) working with Queensland and interstate organisations that have outgrown congregation-sized software. If your funds, entities, or ACNC obligations are getting harder to manage, [**book a free consultation**](/appointment). We'll tell you honestly whether an ERP is the right size for where you are. --- # AI Agents in Odoo: What You Can Wire Up Today, and What v20 Changes - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/odoo-ai-agents-australia - Category: AI & ERP - Published: 2026-07-31 - Description: What Odoo AI agents can do today, verified against the v19 source code, what the v20 roadmap actually promises, and how to run agents safely in Australia. Odoo now ships real AI agent features, Odoo 20 is about to promise bigger ones, and most of what's written about either comes from people who haven't opened the source code. We implement Odoo for Australian businesses and run AI agents against it in production, so this is the practitioner's version: what you can switch on in Odoo today, what you can wire up alongside it, and what to leave alone until it ships. First, a working definition. An AI agent in Odoo is software that uses a large language model to do useful work in your database: answering questions about your records, drafting content, sorting documents and, within strict limits, acting through tools an administrator has approved. In practice that covers two different things: the agent features built into the product, and external agents you connect through Odoo's APIs. The capability is different and so is the risk, so it pays to be precise about both. The demand side isn't speculative. MYOB's research found [78% of wholesale distribution businesses plan to use AI inside their ERP](https://www.myob.com/au/insight/post/erp-trends), and wholesale is exactly the kind of business Odoo wins in Australia. The question we hear in discovery calls has shifted from "should we?" to "what's actually real?" ## What ships in Odoo 19 for AI agents today Odoo 19, the current production release, includes a dedicated AI app, covered in the [official Odoo AI documentation](https://www.odoo.com/documentation/19.0/applications/productivity/ai.html). We've checked what follows against the v19 Enterprise source code, because vendor marketing and shipped software aren't always the same thing. Ask AI is the headline: an assistant available across the database that answers questions in plain language, finds records and opens the right views. Its most important property is what it can't do. The standard Ask AI agent cannot change your data. It will show you the report; it won't post the journal entry. Custom AI agents sit one level up. You create an agent, give it a system prompt and a response style, choose which large language model runs it, and attach knowledge sources it can search, like your product documentation or internal procedures. Then you give it topics: instruction sets with tools attached. The tool design is the detail worth understanding, because it's where Odoo quietly got the governance right. An agent's tools are Odoo server actions, and only the ones an administrator has explicitly flagged as available to AI. The agent can't grant itself new abilities. If nobody hands it a "schedule a follow-up activity" action, it can't schedule one. That's an allowlist, which is how agent permissions should work, and it's the same principle we apply to [every agent we build](/solutions/ai-agents) regardless of platform. The same app also brings the assistive features: AI fields that fill themselves from context, AI server actions for automations, document sorting and data extraction, livechat agents for the website, AI drafting in email templates, and voice transcription. Our guide to [AI in Odoo for Australian businesses](/blog/odoo-erp-australia-6/ai-in-odoo-australia-2026-102) walks through those feature by feature. Two caveats. The AI apps are part of Odoo Enterprise, so Community sites don't include them, though the API route below works for both editions. And what ships today is assistive: it answers, drafts, sorts and suggests. A native agent that runs a multi-step process across modules end to end isn't in v19. That's the v20 conversation. ## The Odoo AI agents you can wire up from outside Most of the practical agent value in 2026 comes from the second layer: an agent that runs outside Odoo, powered by whichever model you choose, working through Odoo's API under a normal user account. The [Model Context Protocol](https://modelcontextprotocol.io) has become the standard way to make that connection, [donated by Anthropic to the Linux Foundation's Agentic AI Foundation in December 2025](https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation) and backed by the major AI vendors. MCP connectors for Odoo already exist from the community and the Odoo app store, and we build ours against the API directly. Here's the worked example we're asked about most. A wholesale business receives purchase orders as PDF attachments, in a different layout for every customer. The agent watches the inbox, reads each PDF, matches the customer record, checks products and pricing against the price list, checks stock, and creates a draft quotation in Sales tagged for review. A salesperson opens the draft, corrects anything odd and confirms it. The agent never confirms an order itself. When it misreads a smudged quantity, and eventually it will, the mistake dies at the review step instead of shipping. Two properties make this safe enough for a sceptical CFO to sign off: - **The agent has its own user account.** Odoo enforces access rights on API sessions, so the agent sees exactly what that user role sees. No administrator login, ever. - **Writes arrive as drafts.** Anything touching the ledger, tax codes, pricing or stock is proposed by the agent and posted by a person. The approval gate is the design, not a training-wheels phase. This is the architecture from our broader guide to [AI agents for Australian businesses](/blog/ai-erp-australia-8/ai-agents-for-australian-businesses-what-actually-works-in-2026-132), and Odoo is a good host for it: the API is mature, permissions are granular, and everything the agent does is inspectable. ## What Odoo 20 changes, and what's still roadmap Odoo 20 gets unveiled at [Odoo Experience in Brussels, 24 to 26 September 2026](https://www.odoo.com/event/odoo-experience-2026-9099/page/oxp26-be-introduction), with general availability expected after the event. Agentic AI is the expected headline: agents that execute multi-step work across modules natively rather than assisting inside one screen. We track what's confirmed versus expected in our [Odoo v20 roadmap breakdown](/blog/odoo-erp-australia-6/odoo-v20-australia-features-roadmap-115). Until it ships, it's a roadmap. Nothing announced at a keynote should drive a 2026 implementation decision, and anyone selling you native "Odoo agents" as a present-tense product is describing slideware. > "The mistake we keep seeing is businesses pausing everything to wait for Odoo 20's agents. The API is the agent surface today. Wire the workflow up now, run it drafts-first, and when v20's native agents mature you'll already have the data discipline and the approval habits they'll need." > > **Josh Craig, Director, Auboros** Our advice hasn't changed: implement on the current version now, treat v20 as an upgrade decision once it's real and stable, and let external agents cover the gap in the meantime. The work transfers. Clean data and approval workflows are exactly what v20's agents will need too. ## Running Odoo AI agents safely in Australia Adoption is accelerating. The Australian Bureau of Statistics reports [12% of Australian businesses used AI in 2024-25](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25), up from 1% two years earlier, and most of them have no written rules about what the AI can touch. That gap is what turns a useful agent into an incident. The Australian framework is workable. The National AI Centre's [Guidance for AI Adoption](https://www.ai.gov.au/staying-safe-and-responsible/essential-ai-practices/guidance-ai-adoption-implementation-guidance) sets out six voluntary practices, including human oversight and accountability. The Privacy Act is not voluntary: customer records in your CRM are personal information, and the OAIC publishes [guidance on using commercial AI products](https://www.oaic.gov.au/privacy/privacy-guidance-for-organisations-and-government-agencies/guidance-on-privacy-and-the-use-of-commercially-available-ai-products). From 10 December 2026, privacy policies must also disclose the kinds of substantially automated decisions that significantly affect people. If an agent helps decide credit terms, that needs documenting before the deadline, not after. For an Odoo database specifically, safe operation comes down to five controls: - **Role-scoped access.** The agent runs as its own user with the narrowest access rights that still let it work. Odoo's permission model does the enforcement if you let it. - **Approval gates on writes.** Ledger, tax, pricing and stock changes are drafted by agents and posted by people. - **An audit trail.** Log what the agent read, what it proposed, who approved it and when. Odoo's chatter and server logs make most of this cheap. - **Sandbox first.** Prove the agent on a staging copy of your database before it sees production. - **A named owner per agent.** Someone reviews its permissions and output quality on a schedule, so access never quietly grows. ## Where to start if you run Odoo Start with the workflow that burns the most hours and has an obvious human checkpoint: inbound order entry, reconciliation exceptions and supplier chasing are the proven first picks. Fix the data the agent depends on, run it against a staging copy until its drafts are consistently right, then go live with the approval gate permanent. Add a second agent only once the first has an owner, a budget and a clean month behind it. None of this needs to wait for a keynote in Brussels. --- **Thinking about AI agents for your Odoo database?** Auboros is a Brisbane-based [Odoo Silver Partner](/solutions/odoo) that designs and runs AI agents over Odoo, drafts-first with human approval, for businesses across Queensland, NSW and Victoria. If you want to know what an agent could safely take off your team's plate, [**book a free consultation**](/appointment). If the honest answer is "fix the data first", you'll hear that instead. --- # MYOB AccountRight to Odoo Migration: What Moves, What Doesn't, and When Acumatica Is the Better Answer - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/myob-accountright-to-odoo-migration-australia - Category: Odoo ERP Australia - Published: 2026-07-31 - Description: Planning a MYOB to Odoo migration? What data moves from AccountRight, how payroll is handled, when to cut over for BAS, and when MYOB Acumatica fits better. AccountRight has probably run your books for a decade or more. It's familiar, your accountant knows it, and it still lodges your BAS every quarter. But somewhere along the way the business outgrew it: stock in two locations, a second entity, sales data in one system and financials in another, and a growing pile of spreadsheets doing the work the software can't. If that's where you are, this post walks through what a MYOB to Odoo migration actually involves, what comes across, what doesn't, and the question most partners won't put in writing: whether Odoo is even the right destination for you. A quick note on why we're placed to answer that last part. Auboros implements both Odoo and MYOB Acumatica. We don't need to talk you out of the MYOB ecosystem to win the work, so you'll get the honest version. ## Why businesses are leaving AccountRight now The push usually comes from growth more than dissatisfaction. AccountRight is accounting software with some inventory and payroll bolted on. It was never designed to run purchasing, warehousing, manufacturing, field service, and a customer pipeline. Businesses hit the ceiling when they need those functions to share one set of data, and [MYOB's own 2025 mid-market research](https://www.myob.com/au/insight/post/mid-market-survey-results-2025) found 36% of mid-sized Australian businesses were looking to upgrade their business management or ERP software. There was also a hard deadline this year. MYOB [decommissioned AccountRight Classic (v19 and earlier) on 28 February 2026](https://www.myob.com/au/support/myob-business/product-account/accountright-classic-v19-and-earlier-decommission). Classic files are now view-only, which forced every remaining desktop holdout to move somewhere. Plenty simply shifted to the current AccountRight, but for a lot of businesses the forced change became the moment to ask whether the next system should be an ERP instead of another accounting package. The decision framework is the same one we laid out for Xero users in [when to upgrade from accounting software to ERP](/blog/odoo-erp-australia-6/odoo-vs-xero-when-to-upgrade-from-accounting-to-erp-in-australia-91): if the pain lives in operations, not in the ledger, an accounting upgrade won't fix it. ## Two paths off AccountRight: Odoo or MYOB Acumatica Before any migration talk, be clear about the destination. From AccountRight there are two credible ERP paths, and we implement both. - **MYOB Acumatica** keeps you in the MYOB family. It's a mid-market cloud ERP with deep ANZ payroll and compliance built in, and the upgrade path from AccountRight is well worn. If your headcount is climbing, payroll complexity is a big part of your world, and you want a platform where the vendor handles local compliance end to end, read our [MYOB Acumatica vs AccountRight comparison](/blog/myob-acumatica-australia-7/myob-acumatica-vs-accountright-australia-117) before you decide anything. - **Odoo** takes you out of the MYOB ecosystem to an open platform where accounting, inventory, CRM, eCommerce, manufacturing, and field service are modules of one system. It tends to win when the business wants operational breadth, per-module flexibility, and more control over how the system is shaped. Neither is universally better. Acumatica usually suits payroll-heavy, finance-led mid-market businesses. Odoo usually suits operations-led businesses that want one platform across the whole workflow. The rest of this post covers the Odoo path, because that's what people searching for this topic are planning. ## What moves in a MYOB to Odoo migration ### Data that comes across cleanly AccountRight exports its lists and reports to Excel or CSV, and Odoo imports CSV and XLSX natively, with [Odoo's import tooling](https://www.odoo.com/documentation/19.0/applications/essentials/export_import_data.html) handling the mapping. In a typical migration we bring across: - **Chart of accounts.** Odoo's Australian localisation ships a default chart with GST tax codes and [BAS-ready configuration](https://www.odoo.com/documentation/19.0/applications/finance/fiscal_localizations/australia.html), so the real work is mapping your AccountRight accounts onto it, not rebuilding from nothing. - **Customers and suppliers.** Contact records, ABNs, and payment terms come across as a straight import. - **Open transactions.** Unpaid invoices and bills are recreated so your receivables and payables start accurate on day one. - **Items and stock.** AccountRight items become Odoo products, and opening stock is loaded as a counted adjustment at cutover. - **Opening balances.** A trial balance as at your cutover date, entered once your accountant has reconciled it. ### Data that needs a decision Historical transactions are the big one. You can migrate opening balances only, bring the current financial year across, or attempt full history. We usually recommend the middle option at most. Rebuilding ten years of AccountRight journals inside Odoo costs real money and delivers very little, because the history you need lives happily in an archive. If you use jobs in AccountRight for project or cost-centre tracking, they map to analytic accounts in Odoo, and that mapping is worth redesigning rather than copying, since analytic accounts can do considerably more than jobs ever did. ### What doesn't move Bank feeds don't transfer; they're re-established against your accounts in Odoo, and reconciliation works differently enough that it's worth reading our guide to [bank reconciliation in Odoo](/blog/odoo-erp-australia-6/odoo-bank-reconciliation-in-australia-statement-feeds-aba-matching-and-keeping-bas-tidy-131) before cutover. Recurring transaction templates, memorised reports, and user permissions are all rebuilt rather than migrated. None of this is difficult, but it belongs in the project plan, not in the surprises column. ## The payroll question, answered honestly AccountRight includes Australian payroll with Single Touch Payroll (STP) reporting, and if you run payroll in it today, this is the part of the migration to slow down on. Odoo has an Australian payroll module, but payroll is the area where we're most conservative with clients. Award interpretation, STP, and superannuation are unforgiving, and the local payroll ecosystem around Odoo is still maturing. For many AccountRight-sized teams, the right architecture is Odoo for operations and accounting with payroll scoped separately, which sometimes means a dedicated payroll product running alongside. Historical payroll records don't migrate either way; they stay in your archive with the rest of the history. We'd rather tell you that before you sign anything than have you discover it in week six. Payroll scoping is a standard part of how we run [an Odoo implementation](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87), and it's the first question we ask AccountRight businesses. ## When to cut over, and what to keep Cut over at the start of a BAS quarter. Your old system owns the last complete BAS, your new system owns the next one, and nobody splits a quarter across two platforms. The next clean window is 1 October 2026, which gives a business starting now a realistic runway for scoping, data preparation, and testing. Cutting over mid-quarter is possible, but it buys you nothing except a messier first BAS. Keep your AccountRight data after you leave. The ATO's [record-keeping rules](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/record-keeping-for-business/overview-of-record-keeping-rules-for-business) require most business records to be kept for at least five years. Before the subscription ends, export general ledger detail, trial balances, BAS worksheets, payroll reports, and your customer and supplier ledgers to PDF and Excel, and archive them somewhere the accountant can reach. Exported archives are searchable, free, and don't depend on anyone's software subscription staying alive. > "The AccountRight conversations we have are rarely about the software being bad. It's that the business has become three businesses and a warehouse since the file was set up. Our job is to work out whether that business belongs on Odoo or on Acumatica, and we don't mind which answer comes out." > > **Bill Alvarez, Practice Manager, Auboros** * * * **Thinking about moving off AccountRight?** Auboros is a Brisbane-based ERP consultancy and one of the few Australian partners implementing both [Odoo](/solutions/odoo) and MYOB Acumatica, so the advice starts with which platform fits, not which one we sell. Our [ERP migration page](/solutions/erp-migration) covers the wider move in detail. If you're weighing up a move from AccountRight, [**book a free consultation**](/appointment). Bring your questions and your messiest spreadsheet, and we'll tell you what we'd actually do. --- # Xero to Odoo Migration: What Moves, What Stays Behind, and When to Cut Over - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/xero-to-odoo-migration-australia - Category: Odoo ERP Australia - Published: 2026-07-31 - Description: Moving from Xero to Odoo? Here's what data comes across, what stays in Xero, how opening balances work, and the best cutover timing for Australian businesses. Deciding to leave Xero usually takes months. The migration itself takes weeks, and most of the anxiety in between comes from one question: what actually happens to my data? It's a fair thing to worry about. Your Xero file holds years of invoices, bills, payroll records and BAS history, and the idea of moving all of that into a new system sounds risky. Here's the part that surprises most people: a good Xero to Odoo migration moves far less data than you'd expect. The skill isn't in dragging everything across. It's in knowing what to bring, what to leave behind, and where to draw the line in time. This post walks through exactly that, based on the migrations we run for Australian businesses. ## What moves in a Xero to Odoo migration Three categories of data come across in almost every migration. Each one is exported from Xero, cleaned up, and loaded into Odoo using its [standard import tools](https://www.odoo.com/documentation/19.0/applications/essentials/export_import_data.html), which accept CSV and Excel files for pretty much any record type. ### Master data: contacts, accounts, and products Customers, suppliers, your chart of accounts, and your product or service list form the foundation. This is also the best data-cleaning opportunity you'll ever get. Every Xero file we've migrated carries duplicate contacts, dead accounts, and products nobody has sold in years. Migrate the mess and you've just paid to move rubbish into a new house. The chart of accounts deserves particular care in Australia. Odoo's [Australian localisation](https://www.odoo.com/documentation/19.0/applications/finance/fiscal_localizations/australia.html) ships with a local chart of accounts and GST tax codes already configured, so the job is mapping your Xero account codes onto it rather than rebuilding from scratch. Getting the tax mapping right here is what keeps your first Business Activity Statement (BAS) out of Odoo clean. ### Open items: what's still in flight Unpaid customer invoices, unpaid supplier bills, and outstanding credit notes come across as individual records. They have to, because you'll be receipting payments against them in Odoo. Anything already paid and settled stays behind as history. ### Opening balances: the line in time Everything else arrives as one journal entry. You run a trial balance in Xero dated the day before cutover, and that becomes an opening balance journal in Odoo: every asset, liability and equity account, matched to the cent. From that date forward, Odoo is the system of record. This single entry is where migrations succeed or quietly fail, which is why it gets reconciled against Xero before anyone processes a live transaction. ## What stays behind, and what to do about it Historical transactions generally don't move. Five years of paid invoices and old bank reconciliations add little day-to-day value inside Odoo, and importing them properly costs real money. But you can't just delete them either. The Australian Taxation Office [requires most business records to be kept for five years](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/record-keeping-for-business/overview-of-record-keeping-rules-for-business), and some company and employee records for longer. You have three practical options, and most businesses use a combination: - **Keep the Xero subscription on a reduced plan** for a year or two as a read-only reference, then export and cancel. - **Export everything to files**: reports, transaction listings and attachments saved to storage you control. Cheapest long-term, slightly clunkier when an auditor asks a question. - **Import summary history into Odoo**, such as monthly journal totals for the prior year or two, so year-on-year reporting works without importing every document. A few things need re-establishing rather than migrating. Bank feeds don't transfer, so you'll connect your bank to Odoo fresh and set a clean statement starting point. Payroll is its own workstream: employee records, leave balances and year-to-date figures need careful setup in whichever payroll arrangement you land on, and Single Touch Payroll (STP) reporting continues without gaps. If you're weighing up the connector route instead of a full migration, we've covered [what an Odoo Xero integration actually syncs](/blog/odoo-erp-australia-6/odoo-xero-integration-australia-how-to-connect-them-and-what-actually-syncs-124) separately, and third-party connectors on the [Odoo app store](https://apps.odoo.com/apps/modules/19.0/xero_odoo_integration) can bridge the two systems during a transition. ## When should you cut over from Xero to Odoo? The textbook answer is 1 July. Starting a new financial year in a new system means one clean set of books per year, one system per tax return, and an opening balance that matches your closing audited position. If you're reading this in July or August having just missed that window, you have not missed your chance. The start of any BAS quarter works nearly as well. For most Australian businesses that means 1 October, 1 January or 1 April. Cutting over on a quarter boundary means each BAS is prepared from a single system, which your bookkeeper will thank you for. Mid-quarter cutovers are possible, but someone ends up stitching two systems together for one lodgement, and that's an avoidable headache. There's also a staged path. Plenty of businesses stand up Odoo for operations first, keep Xero running the books, and move accounting across a quarter or two later. We've written about [running Odoo and Xero together](/blog/odoo-erp-australia-6/odoo-xero-run-together-australia-101), and it's a legitimate transition strategy rather than a failure to commit. The trap is treating it as permanent when it was meant to be a bridge. _"The migrations that go wrong are almost never a technology problem. Someone decides they want five years of transaction history recreated in Odoo, the project drags for months chasing perfect history, and meanwhile nobody has agreed what the opening balance is. Flip the priorities. Nail the opening balance, bring the open invoices, keep Xero as your archive, and you're live in weeks with books you can trust."_ **Josh Craig, Director, Auboros** ## How long does the migration take? The data migration itself is typically two to four weeks of elapsed time inside a broader implementation: extract and clean, trial import into a test database, verify, then the final cutover run. The wider project around it, configuring modules, training people and testing workflows, is what sets the overall timeline, and we've broken that down in our [Odoo implementation guide for Australian businesses](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87). The single biggest factor you control is data quality. A business that spends a fortnight cleaning contacts and products in Xero before extraction will migrate faster and cheaper than one that hands over the file as-is. The trial import matters just as much: you want every surprise to happen in the test database, not on go-live weekend. ## When staying on Xero is the right call Honesty time. If Xero still fits, keep it. A business with straightforward invoicing, no inventory, a single entity and no operational sprawl doesn't need an ERP, and Xero itself now markets [higher tiers aimed at growing businesses](https://www.xero.com/au/accounting-software/erp-software/) to stretch that ceiling further. The move to Odoo makes sense when the pressure is operational: stock in multiple locations, manufacturing, field teams, multiple entities, or a stack of disconnected apps taped around the accounting file. We've set out the signals in detail in our guide on [when to upgrade from Xero to an ERP](/blog/odoo-erp-australia-6/odoo-vs-xero-when-to-upgrade-from-accounting-to-erp-in-australia-91). If those signals aren't flashing yet, a migration buys you complexity you don't need. * * * **Planning a move from Xero to Odoo?** Auboros is a certified Odoo Silver Partner based in Brisbane, and migrations off Xero are one of the most common projects we run for businesses across Queensland, NSW and Victoria. We handle the data mapping, the opening balances and the GST setup, and we'll tell you plainly if we think you should stay on Xero for now. You can see how we approach [Odoo implementation and migration services](/solutions/odoo) on our solutions page. If you're weighing up a cutover date or want a second opinion on what to migrate, [**book a free consultation**](/appointment). Thirty minutes, no obligation, and you'll leave with a clearer migration plan either way. --- # MYOB Acumatica Field Service Edition: Scheduling, Equipment, and Job Costing for Australian Service Businesses - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-field-service-edition-australia - Category: MYOB Acumatica Australia - Published: 2026-07-31 - Description: What MYOB Acumatica Field Service Edition does for Australian service businesses: scheduling, equipment and warranty tracking, mobile, connected job costing. If you run a service business with technicians in the field, the software problem is always the same. The office runs on one system, the techs run on another, and the two only meet when someone retypes a job sheet into the accounts. Parts get used and never billed. Warranty work gets charged by mistake. A maintenance contract lapses because nobody saw the renewal date. The MYOB Acumatica Field Service Edition is built to close that gap by putting scheduling, equipment records, job costing, and invoicing in the same place as your financials. This is a practical look at what the field service capability in MYOB Acumatica actually does, where it fits, and how it connects to the rest of the platform for Australian businesses. ## What the MYOB Acumatica Field Service Edition does Field service management in MYOB Acumatica is an end-to-end module that connects work orders, scheduling, parts inventory, equipment records, time tracking, and invoicing. It is not a bolt-on app talking to your ERP through an integration. It is part of the same system, which is the whole point. You can see the full feature set on MYOB's [field services management page](https://www.myob.com/au/erp-software/industries/field-services-management). Here is how the pieces fit together. ### Service management and scheduling The module lets you capture a service need, shorten the gap between the call coming in and a job being assigned, and match the work to the best available technician. Scheduling is done through a Visual Calendar and Schedule Calendar Board, so you assign jobs based on who is available, where they are, and what skills the job needs. Custom dashboards show what is open, overdue, scheduled, and completed at a glance, so the office is never guessing about the state of the run. ### Equipment and warranty tracking For businesses that service customer-owned equipment, this is the part that earns its keep. You track each piece of equipment, its service history, usage, and location, and you set recurring preventative maintenance schedules so services get booked automatically rather than being remembered. Warranty handling is detailed: you can set multiple warranty classes on a single service order, for example two years on parts and one year on labour, and the system stops you invoicing for work that is actually covered. That alone prevents a common and awkward billing error. ### Mobile for technicians in the field Technicians work through the native MYOB Acumatica app for Apple iOS and Android, or any browser-enabled device. They get service history and equipment details on site, can update orders and appointments on the go, and plan their routes and upcoming appointments including last-minute changes. The practical effect is that the job sheet is filled out once, on the device, and flows straight back to the office and the invoice. No retyping, no lost dockets. ### Service contract management For recurring revenue, the module manages service contracts with visibility of renewal dates, multiple service schedules per customer, and alerts that warn the service and sales teams when a contract is about to expire. If your business runs on maintenance agreements, this is where you stop revenue leaking through missed renewals. ## Where the Field Service Edition fits, and where it doesn't Field service management suits businesses that send people out to install, maintain, or repair things: HVAC and refrigeration, equipment servicing, fire and security, medical and lab equipment, industrial maintenance, and similar trades-with-assets operations. The common thread is that you manage equipment over time, carry parts inventory, and bill against jobs and contracts rather than just selling product off a shelf. It is less of a fit if your "field work" is really project delivery with no recurring equipment or service contracts, or if you are a small operator who needs a simple job-and-invoice app rather than a full ERP. MYOB Acumatica is a mid-market platform, and the field service module makes most sense once your office and field operations are too tangled for spreadsheets and a separate scheduling tool to hold together. We are honest about that threshold during scoping, because nobody benefits from over-buying. _"The businesses that get the most out of field service in MYOB Acumatica are the ones drowning in the handoff between the field and the books. When a tech finishes a job, the parts, the labour, the warranty status, and the invoice should all settle without anyone re-entering anything. That single flow is what people are really buying. The scheduling calendar is nice, but the money is in the data not getting dropped on the way back to accounts."_ **Bill Alvarez, Practice Manager, Auboros** ## How it connects to the rest of MYOB Acumatica The reason to run field service inside MYOB Acumatica rather than as a standalone app is the connection to everything else. The module ties into the platform's financials, CRM, inventory, and purchasing, so a service order draws parts from the same stock the warehouse manages and posts to the same general ledger your accountant works from. For businesses where service work is part of a larger job, it also integrates with [MYOB Acumatica's project accounting](https://www.myob.com/au/erp-software/features/project-accounting-software), which we cover in detail in our guide to [project accounting for Australian businesses](/blog/myob-acumatica-australia-7/myob-acumatica-project-accounting-australia-123). The compliance side matters too. Because invoicing sits inside the ERP, the goods and services tax (GST) is handled correctly on service invoices, and your Business Activity Statement (BAS) draws from the same figures. Field technicians who are employees flow through the platform's payroll, which keeps you aligned with Single Touch Payroll (STP) reporting obligations to the [ATO](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll). You can see the broader platform capabilities on MYOB's [MYOB Acumatica product page](https://www.myob.com/au/erp-software/products/myob-acumatica). If you are weighing this against the construction or trades angle specifically, our piece on [MYOB Acumatica for construction in Queensland](/blog/myob-acumatica-australia-7/myob-acumatica-for-construction-in-queensland-job-costing-qbcc-compliance-and-what-s-included-105) covers the job costing and compliance overlap, and we walk through how the platform's editions differ in our [Manufacturing Edition breakdown](/blog/myob-acumatica-australia-7/myob-acumatica-manufacturing-edition-production-modes-mrp-and-the-current-release-129). * * * **Thinking about MYOB Acumatica for your field service business?** We are an official MYOB Acumatica partner based in Brisbane, working with service businesses across Queensland, New South Wales, and Victoria. The useful first step is to map how your field work and your books currently connect, then work out whether the field service module closes that gap for you. If you want to talk through whether the MYOB Acumatica Field Service Edition fits how you operate, [**book a free consultation**](/appointment). We will give you a straight answer, including if the timing is not right yet. You can also see our full [MYOB Acumatica services](/solutions/myob). --- # Payday Super Is Live: What to Check in MYOB Acumatica Payroll Now - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-payday-super-australia - Category: MYOB Acumatica Australia - Published: 2026-07-31 - Description: Payday Super started 1 July 2026. The checks MYOB Acumatica payroll teams should run now: qualifying earnings flags, super batch timing and the 7-day rule. Payday Super stopped being a future deadline on 1 July 2026. If you run payroll in MYOB Acumatica, you've now processed a few pay cycles under the new rules, and here's the uncomfortable part: pay runs that look completely normal on screen can still be quietly non-compliant. The software processed the pay, the super accrued, everyone got paid. Whether the right super amounts are reaching funds inside the new deadlines is a separate question, and it's the one the Australian Taxation Office (ATO) is now watching closely. Most of the content written about Payday Super was published before the start date and framed as preparation. This post is the other half: the checks worth running now that the regime is live, specifically for businesses on MYOB Acumatica. ## What changed on 1 July 2026 The old quarterly super guarantee cycle is gone for earnings paid from 1 July 2026 onwards. Under the new rules, your super contribution must be [received by the employee's fund within 7 business days of payday](https://www.ato.gov.au/businesses-and-organisations/super-for-employers/payday-super/paying-super-on-payday/payment-deadlines-for-payday-super), not just sent by then. The ATO calls payday the QE day, the day you pay qualifying earnings. A few points from the fine print that matter in practice: - **Received means received.** The clock stops when the fund has the money and the data needed to allocate it, so clearing house processing time is your problem, not the fund's. - **Business days exclude state-wide public holidays** anywhere in Australia, even if your business isn't in that state. A Queensland business can gain a day because of a Northern Territory holiday. - **Super is now calculated on qualifying earnings (QE)**, a new single earnings base that replaces ordinary time earnings for this purpose. Some pay items that weren't previously superable are now, and a few work the other way. - **The quarterly maximum contribution base is replaced by an annual one**, which changes how caps apply for high earners across the year. The [Fair Work Ombudsman's summary](https://www.fairwork.gov.au/newsroom/news/payday-super-new-rules-starting-1-july-2026) is a readable overview of the employer obligations. The Small Business Superannuation Clearing House also closed permanently on 1 July, which mostly affects smaller entities, though we've seen it catch subsidiaries inside larger groups that were still using it quietly. ## The first check: your pay item QE flags MYOB's guidance was to review every pay item after your final June pay run and before your first July one, marking each as liable or not liable for qualifying earnings. In MYOB Acumatica Payroll that happens on the Pay Item Liabilities screen (MPPP1025), which now carries separate columns for QE and super guarantee liability. The full walkthrough is in MYOB's [Payday Super transition guide](https://enterprisesupport.myob.com/knowledge/transitioning-to-payday-super-with-myob-acumatica). If that review happened in a hurry during EOFY week, or you're not sure it happened at all, run it again now. Compare your flags against the ATO's list of [what payments count as qualifying earnings](https://www.ato.gov.au/businesses-and-organisations/super-for-employers/payday-super/paying-super-on-payday/what-payments-are-qualifying-earnings), paying attention to allowances, bonuses and termination-adjacent items, because those are where the base moved. A wrong flag doesn't announce itself. It just accrues a small shortfall or overpayment on every single pay run until someone notices, usually at the worst possible time. ## Super batches now live on a 7-business-day clock Quarterly batching habits die hard. Under Payday Super, the practical rhythm is a super batch with every pay run, submitted promptly enough that the money lands in funds inside the window. MYOB Acumatica's super batch workflow handles the mechanics, but the timing discipline is yours: a batch created on payday and submitted two days later has already spent a chunk of its 7 business days. ### New starters get 20 business days, once The first contribution for a new employee, or the first to a new fund for an existing employee, has an extended deadline of 20 business days after the relevant payday. That's breathing room for onboarding paperwork and fund choice, not a licence to relax. From that employee's second regular contribution, the standard 7 business day window applies. ### Bonuses and out-of-cycle payments follow the next regular run Pay someone a bonus outside their normal cycle and the super on it is due with the contribution for their next regular payday, rather than starting its own clock. That's a sensible concession, but it means your super batch for that next run needs to pick up the out-of-cycle amounts correctly. Worth verifying the first time it happens rather than assuming. ## What happens if a payment lands late The super guarantee charge has been redesigned around the new deadlines. Miss the window and the shortfall attracts notional earnings, an administrative uplift and potentially a choice loading, and some of those components can still apply even if you pay the base shortfall quickly. The redesigned charge is generally tax deductible where the old one wasn't, but it's not a cost anyone should be budgeting for. The bigger shift is visibility. The ATO matches Single Touch Payroll (STP) data against what funds report receiving, so a late contribution is visible to them within weeks, not at the end of a quarter. If you do land late, acting quickly reduces the damage. Waiting to be contacted is the expensive option. _"The businesses having a rough July aren't the ones that missed the deadline entirely, they're the ones that did the version upgrade, ticked the boxes, and never re-checked the pay items that changed under qualifying earnings. One mis-flagged allowance across a hundred employees compounds every week. Fifteen minutes on the Pay Item Liabilities screen against the ATO's QE list is the cheapest insurance in payroll right now."_ **Josh Craig, Director, Auboros** ## Version and process checks worth five minutes MYOB Acumatica Payroll version 2025.2.100 and later includes the Payday Super tooling, and the detail of what changed on which screens is in the official [Payday Super release notes](https://help.myob.com.au/advanced/Docs/Published/ReleaseNotes/MYOBACU_RN_2025_2_1_Payroll_PayDaySuper.html). If your environment hasn't taken payroll compliance updates recently, confirm your version before anything else, because no amount of process discipline fixes calculations running on old rules. Compliance updates like this one are part of what a [MYOB Acumatica support arrangement](/blog/myob-acumatica-australia-7/myob-acumatica-support-what-s-included-and-what-you-ll-pay-extra-for-96) should be handling for you. The super guarantee rate itself is unchanged by Payday Super, sitting at the current 12%, so any variance you see should trace back to the QE base or timing, not the rate. Beyond the version, the questions we ask in a post-go-live review are simple. Who owns the super batch each pay run, and is it a named person rather than a shared assumption? Does your cash flow forecast reflect super leaving with every pay run instead of quarterly? And did anything in your [EOFY close](/blog/myob-acumatica-australia-7/myob-acumatica-eofy-checklist-2026-what-to-prepare-before-30-june-120) get deferred in June that's still sitting open now? We covered the preparation side in our [MYOB Acumatica payroll guide](/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97) before the deadline; this is the follow-through. * * * **Not sure your Payday Super setup is actually right?** Auboros is an official MYOB Acumatica partner based in Brisbane, working with mid-market businesses across Queensland, NSW and Victoria. A post-go-live payroll review is a short piece of work: we check your pay item QE flags, super batch timing and version status against what the rules now require, as part of our broader [MYOB Acumatica services](/solutions/myob). If you'd like a second set of eyes over your first months under Payday Super, [**book a free consultation**](/appointment). If everything checks out, you'll at least have that in writing. --- # AI Agents for Australian Businesses: What Actually Works in 2026 - Canonical URL: https://www.auboros.com/blog/ai-erp-australia-8/ai-agents-for-australian-businesses-what-actually-works-in-2026-132 - Category: AI & ERP - Published: 2026-07-30 - Description: What AI agents can do inside Australian businesses in 2026: worked ERP examples, where Odoo and MYOB Acumatica are up to, and the guardrails that matter. Most of what's written about AI agents comes from people who have never connected one to a live business system. The demos look effortless. The LinkedIn posts promise a workforce that never sleeps. Then you ask a practical question, like "what happens when the agent books a journal entry against the wrong tax code?", and the room goes quiet. We run AI agents in production, on our own operations and against ERP systems, so this guide is written from the unglamorous side of the demo. Here's what AI agents can actually do for Australian businesses in 2026, where Odoo and MYOB Acumatica sit today, and the governance work that separates a useful agent from an expensive incident. ## **What an AI agent actually is (and what it isn't)** An AI agent in a business context is software that uses a large language model to work towards a goal across multiple steps: it can read information from your systems, decide what to do next, use tools like your ERP's API to act, and hand the result to a person for approval. That last part matters. A chatbot answers questions. An agent does work. The distinction from traditional automation matters too. A workflow rule follows a fixed path: if X, then Y, every time. An agent handles the messy middle, like reading a purchase order PDF that's formatted differently by every customer, and still produces a structured result. That flexibility is the value, and it's also the risk, because language models make mistakes. Anyone selling you an agent that "never gets it wrong" hasn't run one for long. Adoption is no longer fringe. The Australian Bureau of Statistics reports that [12% of Australian businesses used AI in 2024-25](https://www.abs.gov.au/media-centre/media-releases/business-adoption-artificial-intelligence-accelerates-2024-25), up from 1% two years earlier, with 35% of large businesses on board. In the sectors we work with, intent is stronger again: MYOB's research found [78% of wholesale distribution businesses plan to use AI in their ERP](https://www.myob.com/au/insight/post/erp-trends). The question has shifted from whether to use AI to how to wire it into the systems that run the business without breaking anything. ## **What AI agents are doing in Australian businesses right now** Forget the abstract use-case lists. Here's the level of specificity that matters when you're scoping this work. ### **Reading inbound purchase orders and drafting sales orders** A wholesale business receives purchase orders as PDF attachments, each customer using their own format. An agent watches the inbox, reads each PDF, matches the customer against the ERP, checks the products and pricing against the price list, checks stock, and drafts a sales order. A person reviews the draft, fixes anything odd, and confirms it. The agent never posts the order itself. That single workflow routinely saves hours of rekeying a day, and because a human approves every order, a misread line item is an annoyance rather than a shipped mistake. ### **Flagging reconciliation exceptions before month end** Finance teams running an ERP alongside e-commerce, point of sale and a warehouse system spend days each month finding out why the numbers don't agree. An agent can compare transactions across those systems daily, flag the exceptions, and propose a resolution for each one: a missed payout fee here, a duplicated order there. The accountant reviews the proposals and applies the ones that are right. Nothing touches the ledger without sign-off, which also keeps your Business Activity Statement (BAS) position clean, because every correction is a human decision with an audit trail. ### **Chasing suppliers and watching stock** On the operations side, agents draft the boring correspondence: chasing suppliers for delivery confirmations on open purchase orders, flagging purchase orders that will land late against promised customer dates, and preparing replenishment suggestions from sales velocity and lead times. The pattern is identical in every case. The agent reads, drafts, flags and proposes. A person decides. If you're evaluating any agent product or consultancy, that pattern is the test. Ask exactly where the human approval sits. If the answer is vague, keep your API keys in your pocket. ## **Where Odoo and MYOB Acumatica actually are with AI** Vendor announcements and shipped software are different things, so here's the current state of both platforms we implement, with each capability labelled as shipped or roadmap. ### **Odoo: useful AI shipped in v19, agents on the v20 roadmap** Odoo 19, the current production release, ships AI embedded across the suite: AI-assisted fields and server actions, document extraction in accounting, AI in CRM, and AI-powered livechat and knowledge features. We've verified these against the v19 Enterprise source code, not the marketing site, and we cover the detail in our guide to [AI in Odoo for Australian businesses](/blog/odoo-erp-australia-6/ai-in-odoo-australia-2026-102). The bigger step is Odoo 20, which is expected to move from assistive AI towards agentic AI: agents that execute multi-step work across modules. That capability is roadmap, not product. It's due to be shown at [Odoo Experience in late September 2026](https://www.odoo.com/odoo-experience), with general availability expected after that. If a vendor or partner tells you Odoo agents are shipping today, they're describing the roadmap as the product. Our [Odoo v20 roadmap breakdown](/blog/odoo-erp-australia-6/odoo-v20-australia-features-roadmap-115) covers what's confirmed versus expected, and none of it changes our standing advice: implement on the current version now, and treat v20's agents as an upgrade decision once they're real and stable. ### **MYOB Acumatica: AI arriving on the usual release lag** Globally, Acumatica's 2026 R1 release [reached general availability in March 2026](https://www.acumatica.com/blog/acumatica-2026-r1-acumatica-ai-enabled-product-release-delivers-intelligence/) with an AI Assistant and AI Studio, AI-powered anomaly detection in reporting, and early AI-assisted workflows, some of it in experimental or early-access form. The important caveat for Australian and New Zealand businesses: global Acumatica releases typically reach [MYOB Acumatica](/solutions/myob) customers six to nine months later, and the release most local customers run today is 2025 R2. "Acumatica has it" and "your MYOB Acumatica instance has it" are usually two different statements, so confirm with your partner what's actually enabled on your version before you plan around it. In the meantime, agents don't have to wait for native features on either platform. Both expose APIs, which means the agent layer can sit outside the ERP under your own governance. That's where most of the practical work happens in 2026. ## **How agents connect to your ERP without handing over the keys** The connection layer is where most of the security and governance questions live, and it's matured a lot in the past year. The [Model Context Protocol (MCP)](https://modelcontextprotocol.io) has become the common standard for connecting AI models to business tools. It started at Anthropic and was [donated to the Linux Foundation's Agentic AI Foundation in December 2025](https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agentic-ai-foundation), with the major AI vendors backing it. In plain terms, MCP means you can build one governed connection to your ERP and let your choice of AI model use it, rather than wiring each tool to each system separately. That gives you a real architectural choice: - **Hosted assistants,** like Microsoft Copilot or Anthropic's Claude, connected to your ERP through MCP or an integration layer. Fastest to start, and the vendor handles the model. You still control what the connection can see and do. - **Self-hosted agent frameworks,** like the open-source [OpenClaw](https://openclaw.ai), which run on infrastructure you control. More work to operate, and you carry more of the security responsibility, but data flows and model choice stay entirely in your hands. - **Bring-your-own-LLM builds,** where the agent logic is yours and the underlying model is swappable. This is how we build: if a better or cheaper model ships next quarter, you change a setting, not the architecture. Whichever route fits, the non-negotiable is scope. The agent gets its own credentials, with the same data visibility as the person it works for, never a shared administrator login. An agent that helps a sales rep should see exactly what that rep sees. Nothing more. ## **The governance layer: what keeps agents out of trouble** This is the part most AI content skips, and it's the part your accountant, your auditor and your board will ask about. The good news is that Australia now has practical guidance to anchor it. The National AI Centre's [Guidance for AI Adoption](https://www.ai.gov.au/staying-safe-and-responsible/essential-ai-practices/guidance-ai-adoption-implementation-guidance), released in October 2025, replaced the earlier Voluntary AI Safety Standard and sets out six essential practices, including accountability, risk management and human oversight. It's voluntary, but it's the reference point we'd expect customers, insurers and larger trading partners to start measuring against. Privacy is not voluntary. The Privacy Act and the Australian Privacy Principles apply whenever personal information goes through an AI workflow, and the regulator has published specific [guidance on using commercially available AI products](https://www.oaic.gov.au/privacy/privacy-guidance-for-organisations-and-government-agencies/guidance-on-privacy-and-the-use-of-commercially-available-ai-products). There's also a date to put in your diary: from 10 December 2026, privacy policies must disclose the kinds of decisions made by substantially automated processes that significantly affect people. If an agent helps decide who gets credit terms, that's your problem to document before it's the OAIC's problem to investigate. In practice, the governance that matters on an agent-over-ERP build comes down to five controls: - **Role-scoped permissions.** The agent acts with the requesting user's data access, never a super-user account. - **Approval gates on writes.** Anything touching the ledger, tax codes, pricing or stock is drafted by the agent and posted by a person. - **Audit trails.** Every agent action is logged: what it read, what it proposed, who approved it, and when. - **Sandbox-first deployment.** Agents earn production access by proving themselves against a copy of your data first. - **A usage policy staff have signed.** Which tools are approved, what data can leave the building, and who owns each agent. _"The first decision on any agent build is what it's not allowed to touch. An agent that drafts a sales order and waits for a person is an asset. An agent that can post to the ledger unsupervised is a liability with an API key. The approval gate isn't a compromise, it's the design."_ **Bill Alvarez, Practice Manager, Auboros** ## **Where agents still fail (plan for it, don't pretend otherwise)** Language models produce confident, fluent errors. Not often, but never zero. An agent will occasionally misread a quantity, match the wrong customer, or summarise a document in a way that drops the one detail that mattered. Failure modes we design around, because we've seen them: - **Confident misreads.** A scanned purchase order with a smudged quantity becomes a wrong draft. The approval step catches it, which is why the approval step exists. - **Stale context.** An agent working from last week's price list quotes last week's prices. Agents need live system data, not exported copies. - **Permission creep.** An agent set up quickly with broad access "just to get it working" and never tightened. Schedule permission reviews the way you'd review user access. - **Cost drift.** Agents that retry, loop or over-read can quietly run up model usage bills. Set budgets and alerts per agent from day one. None of this argues against agents. It argues against unsupervised agents. The businesses getting real value in 2026 aren't the ones with the most autonomous setup, they're the ones whose agents remove the repetitive reading, matching and drafting while people keep the judgement calls. ## **Where to start if you run Odoo or MYOB Acumatica** The sequence we recommend, and follow ourselves: 1. **Fix the data first.** An agent reasoning over duplicate customers and stale price lists just automates confusion. Data hygiene is the unskippable prerequisite. 2. **Pick one workflow with a clear human checkpoint.** Inbound order entry, reconciliation exceptions and supplier chasing are proven starters. Pick the one that burns the most hours. 3. **Run it in a sandbox against real historical data.** Measure how often the agent's drafts are right before it goes anywhere near production. 4. **Go live drafts-first.** Keep the approval gate permanent on financial writes, and review the logs weekly for the first quarter. 5. **Only then add the next agent.** A registry of what runs, who owns it and what it can access stops "a few helpful agents" becoming an unmanaged crowd. This is the same discipline as any ERP project: scope tightly, prove it, then expand. If your platform decision is still open, or your current system's data isn't ready for any of this, that's a conversation about [ERP foundations](/solutions/other-erp-services) before it's a conversation about AI. ## **Frequently asked questions** ### **What is an AI agent in an ERP context?** An AI agent in an ERP context is software that uses a large language model to complete multi-step work against your business system: it reads data, decides the next step, acts through the ERP's interfaces or API, and hands the result to a person for approval. It differs from a chatbot, which only answers questions, and from workflow automation, which follows fixed rules. ### **Are AI agents safe for Australian businesses to connect to accounting software?** They can be, if the connection is governed. Safe setups give the agent role-scoped credentials rather than administrator access, require human approval before anything posts to the ledger, log every action, and are tested in a sandbox first. An agent with unsupervised write access to your accounts is not a safe setup, whatever the vendor demo suggests. ### **Do Odoo or MYOB Acumatica have AI agents built in?** Not as shipped products in Australia as of mid-2026. Odoo 19 includes useful assistive AI, with agentic capability on the Odoo 20 roadmap expected at the end of September 2026. Acumatica's 2026 R1 release added AI Assistant and early agent workflows globally, which typically reach MYOB Acumatica customers six to nine months after the global release. Agents connected through APIs work with both platforms today. ### **What does the Australian government require before a business uses AI?** There's no dedicated AI Act. The National AI Centre's Guidance for AI Adoption sets out six voluntary practices, while existing law still applies, most importantly the Privacy Act when personal information is involved. From 10 December 2026, privacy policies must also disclose certain substantially automated decisions that significantly affect people. ### **How is an AI agent different from workflow automation?** Workflow automation follows fixed rules: the same trigger always produces the same action. An AI agent interprets unstructured, variable input, like a differently formatted PDF order from every customer, and still produces structured output. That flexibility means agents handle work rules can't, but also that their output needs human review in a way deterministic automation doesn't. * * * **Thinking about AI agents for your ERP?** Auboros designs, governs and implements AI agents for businesses running Odoo and MYOB Acumatica, from our base in Brisbane serving Queensland, NSW and Victoria. We run agents in production ourselves, with the approval gates and permissions described above, so the advice comes from operating experience rather than a slide deck. If you want a clear-eyed view of what an agent could take off your team's plate, [**book a free consultation**](/appointment). We'll tell you what's worth automating and what isn't yet. --- # How Much Does MYOB Acumatica Cost in Australia? (2026 Guide) - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-cost-australia - Category: MYOB Acumatica Australia - Published: 2026-06-12 - Description: How much does MYOB Acumatica cost in Australia? We break down subscription pricing, implementation costs, and what actually drives the total investment. MYOB Acumatica doesn't publish a simple price list, and that's not accidental. The cost depends on how many users you need, which modules you're activating, and how complex your implementation will be. That said, the ballpark figures are well-established in the Australian market, and knowing them before you start talking to partners saves you from being surprised mid-process. This guide covers what you'll actually pay: subscription costs, implementation investment, and the factors that push the total up or down. ## MYOB Acumatica subscription pricing in Australia MYOB Acumatica is priced on a per-user, per-month subscription model. Based on current market pricing, most Australian businesses pay somewhere between **$148 and $215 per user per month** depending on the edition and modules activated. Entry-level access starts from approximately $131 per user per month for the Standard edition. For a business with five users, that puts your monthly software cost in the range of **$750 to $1,075 per month**. Larger teams with 10 to 20 users typically land between $2,500 and $6,000 per month once you factor in the modules required for their specific roles. These figures are indicative. Your actual subscription cost is quoted by MYOB directly through an authorised partner and will reflect your specific user count, licence type, and module selection. ### Named users vs concurrent users MYOB Acumatica uses named user licensing, meaning each licence is assigned to a specific person rather than a seat that can be shared. If you have 15 staff who need system access (even if only 8 of them are ever logged in at the same time), you'll need 15 licences. This is worth factoring into your budget early, particularly for businesses with large part-time or casual workforces. ## MYOB Acumatica implementation costs The subscription is an ongoing cost. The implementation is a one-time investment to get the system set up, configured, and your team trained. This is where the total cost of moving to MYOB Acumatica is most variable, and where most businesses underestimate their budget. Based on current implementation rates in the Australian market, here are realistic ranges by scope: | Implementation scope | Consultant days | Indicative cost | Typical timeline | | --- | --- | --- | --- | | Finance only | 15 to 20 days | $20,000 to $30,000 | 2 to 3 months | | Finance, distribution and inventory | 25 to 40 days | $30,000 to $50,000 | 3 to 4 months | | Finance, distribution and manufacturing | 40 to 60 days | $55,000 to $75,000 | 4 to 5 months | These are indicative ranges based on standard implementations. Custom integrations, complex data migrations, or heavily customised workflows will add to both the timeline and cost. Most mid-size Australian businesses investing in MYOB Acumatica should budget a minimum of $50,000 for implementation, with many projects landing in the $50,000 to $75,000 range. ## What drives the total cost up or down The implementation cost estimate you receive will depend on several factors that are specific to your business. These are the most common ones that shift the number: - **Number of users and locations.** More users means more licences. Multiple sites or warehouses add configuration and testing time. - **Data migration complexity.** Moving clean, structured data from a well-maintained system is straightforward. Migrating years of messy data from multiple sources takes significantly more time. - **Custom integrations.** Connecting MYOB Acumatica to a third-party platform (eCommerce, industry-specific software, a customer portal) requires development work that's scoped separately from the core implementation. - **Internal resource availability.** Implementations move faster when your team is available for workshops, testing, and sign-off. Projects where internal stakeholders are difficult to get hold of consistently run over time and budget. - **Module scope.** Activating payroll and workforce management adds meaningful configuration time compared to a finance-only implementation. Manufacturing adds more again. ## Ongoing costs beyond the subscription The subscription covers your access to the software. There are a few additional costs worth planning for: - **Support agreements.** Most partners offer tiered support plans covering helpdesk access, system administration, and minor configuration changes. These typically run $1,000 to $3,000 per month depending on the level of cover. - **Annual upgrades.** MYOB Acumatica releases updates regularly. Applying these in a managed environment involves partner time, particularly if you have customisations that need to be tested against the new version. - **Development work.** Customisations and integrations added after go-live are quoted separately. Having a clear scope before implementation reduces the need for unplanned development later. ## Is MYOB Acumatica worth the investment? The businesses that get strong returns from MYOB Acumatica are typically those that have genuinely outgrown simpler tools. If you're running MYOB Business (AccountRight) and hitting its ceiling, struggling with multi-entity reporting, complex inventory, project accounting, or payroll at scale, the efficiency gains from a proper mid-market ERP tend to pay back the implementation cost within 12 to 24 months. If you're a smaller business that doesn't yet have that complexity, the investment won't make sense. MYOB Acumatica is designed for organisations with at least 20 employees or an equivalent level of financial and operational complexity. Our [MYOB Acumatica implementation services](/solutions/myob) page covers the types of businesses we typically work with and what the process looks like. --- **Want a realistic cost estimate for your business?** We're a Queensland-based [MYOB Acumatica partner](/solutions/myob) and we give straight answers on cost. If you're still weighing platforms, our [Odoo vs MYOB Acumatica comparison](/compare/odoo-vs-myob-acumatica) puts the two side by side. If you're in the early stages of evaluating whether MYOB Acumatica fits your budget and requirements, [**book a free consultation**](/appointment) and we'll give you an honest estimate based on your specific situation. --- # Odoo Pricing in Australia: What It Costs, What's Included, and the Numbers People Miss - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-pricing-australia - Category: Odoo ERP Australia - Published: 2026-05-31 - Description: A clear look at Odoo pricing in Australia: the three plans, what each per-user fee includes, and the implementation and hosting costs most quotes leave out. The first question almost every business asks us about Odoo is some version of "what does it cost?" It is a fair question with an annoying answer, because the licence fee is the easy part and rarely the part that decides your budget. The per-user price is published, it is low, and it is the same whether you turn on three apps or twenty. The cost that actually moves is everything around the licence: implementation, hosting, the credits a few features consume, and the customisation you may or may not need. This is a plain breakdown of Odoo pricing in Australia as it stands in 2026. We will cover the three plans, what each one genuinely includes, and the costs that quotes from cheaper providers tend to leave off until later. ## Odoo pricing: the three plans Odoo sells subscriptions on a per-user, per-month basis, and the structure is unusually simple compared with most mid-market software. There are three plans, and you can see current rates on the [official Odoo pricing page](https://www.odoo.com/pricing), which displays figures in Australian dollars when you visit from here. Odoo typically adjusts pricing once or twice a year, usually around a major version release, so treat the numbers below as indicative and check the live page before you budget. ### One App Free The free plan gives you a single app for unlimited users at no cost, hosted on Odoo Online. It is genuinely free, not a trial. The catch is in the word "single." If you only need CRM, or only need the website builder, this can run a small operation for a long time. The moment you install a second app, you move onto a paid plan. It is a good way to test the interface before committing, and a reasonable home for a one-function workflow. ### Standard The Standard plan is AUD $34.40 per user per month on monthly billing, and it unlocks all of Odoo's apps for that single fee. That is the part people miss. You are not paying separately for Accounting, Inventory, CRM, Sales, Project, and the rest. Turn on what you need, leave the rest off, and the price per user does not change. Standard runs on Odoo Online, Odoo's managed cloud, which suits most small and mid-sized Australian businesses that do not need custom code. ### Custom The Custom plan is AUD $52.00 per user per month on monthly billing. It includes everything in Standard, plus the things growing businesses tend to need: Odoo Studio for building your own screens and automations, multi-company support, the external API, and the option to host on [Odoo.sh](https://www.odoo.sh) or on your own servers rather than Odoo Online. If you plan to customise Odoo, integrate it with other systems, or run more than one legal entity, this is the plan you will end up on. Note that the Custom licence does not include Odoo.sh hosting itself, which is a separate cost we cover below. A useful detail for headcount planning: Odoo only charges for internal users who log into the back end to create, view, or edit records. Customers and suppliers using the portal, and visitors placing orders through your website, are free. So a business with fifteen staff and thousands of customers pays for fifteen users, not thousands. Odoo explains this distinction on its [pricing page FAQ](https://www.odoo.com/pricing). ## Why the licence is the smallest part of your Odoo cost Run the licence maths for a ten-person business on the Custom plan and you land somewhere near AUD $6,240 a year. That is real money, but it is not the number that decides whether the project is a success. The implementation is. Software that is configured badly, or rushed, costs far more in lost time than the subscription ever will. The data backs this up. Capterra's 2025 research on Australian software buying found that [fewer than one in three Australian businesses successfully adopt new software](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/), which tells you the failure point is almost never the price tag. It is the rollout. A cheap licence attached to a poor implementation is the most expensive option on the table. > "The per-user price is the figure everyone anchors on, and it's the one that matters least. We've seen businesses save a few hundred dollars a month on licensing and then lose that ten times over because the chart of accounts was set up wrong and BAS time became a fortnight of cleanup. The money is in getting the foundation right, not in shaving the subscription." > > **Bill Alvarez, Practice Manager, Auboros** ## What an Odoo implementation costs in Australia Implementation is where the budget genuinely varies, because it depends on how much of your business you are moving into Odoo and how far your processes sit from the standard setup. Odoo offers two routes. Small companies under roughly 50 employees often work directly with Odoo using prepaid [Success Packs](https://www.odoo.com/pricing-packs), blocks of hours you draw down for configuration and training. Mid-sized and larger businesses usually work with a local [Odoo partner](https://www.odoo.com/partners) who handles project management, data migration, and the parts that need someone on the ground in your timezone. We publish indicative figures for each tier on our [Odoo implementation packages page](/odoo-implementation-packages-for-australian-businesses) rather than making you ask, because vague pricing helps nobody. As a rough frame, a clean single-entity setup with standard accounting and a couple of operational apps sits at the lower end, while a multi-company business with custom workflows, integrations to existing systems, and data migration from legacy software sits considerably higher. We walk through exactly what each phase buys you in our guide to [Odoo implementation services in Australia](/blog/odoo-erp-australia-6/odoo-implementation-services-australia-126). The honest version is that implementation is a range, not a sticker price, and any partner who quotes a fixed number before understanding your processes is guessing. A proper scope is the first thing worth paying for. ## The costs people forget: hosting, credits, and maintenance Three line items get left off cheap quotes and surprise people later. - **Hosting on Odoo.sh.** Odoo Online is included free with every plan, including up to 100GB of storage. But if you are on the Custom plan and running custom modules, you will likely want Odoo.sh, Odoo's development and staging platform, which carries its own monthly cost on top of the licence. On-premise hosting is also an option if you would rather run your own infrastructure. - **In-app purchase credits.** A handful of features consume prepaid credits rather than being included in the subscription: sending SMS, contact auto-complete, lead generation, and the AI that scans vendor bills and expenses. For most businesses this is a small, usage-based amount, but it is a real cost that flat per-user comparisons miss. - **Maintenance of custom code.** Anything bespoke that a partner builds for you needs to keep working across version upgrades. Standard apps are maintained by Odoo at no extra fee, but custom developments are your responsibility to maintain, which is usually folded into an ongoing support arrangement. None of these are hidden if you know to ask. They are spelled out in Odoo's own pricing terms. The problem is when a quote ignores them to look cheaper, and the bill arrives in month three. ## How Odoo pricing compares to what you might be leaving Most businesses we talk to are not pricing Odoo against nothing. They are weighing it against the stack they already run, which is often Xero plus three or four bolt-on apps for inventory, projects, CRM, and the rest. Add those subscriptions up per user and the picture changes, because Odoo's all-apps-for-one-fee model tends to consolidate several line items into one. We cover where that tradeoff makes sense, and where it does not, in our breakdown of [when to upgrade from Xero to Odoo](/blog/odoo-erp-australia-6/odoo-vs-xero-when-to-upgrade-from-accounting-to-erp-in-australia-91). The comparison that matters is not "Odoo per user versus Xero per user." It is "the total cost and admin of my current tool sprawl versus one integrated system." Sometimes the answer is still to stay put for now, and we will tell you that. You can see the full scope of what we do on our [Odoo services page](/solutions/odoo). If you want a clear picture of what Odoo would cost your business in Australia, [book a free consultation](/appointment). No obligation, and you will leave the call knowing more than when you started. --- # Odoo Bank Reconciliation in Australia: Statement Feeds, ABA Matching, and Keeping BAS Tidy - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-bank-reconciliation-in-australia-statement-feeds-aba-matching-and-keeping-bas-tidy-131 - Category: Odoo ERP Australia - Published: 2026-05-30 - Description: How to set up Odoo bank reconciliation in Australia: feed types, ABA batch matching, multi-currency, GST checks, and avoiding BAS lodgement errors Bank reconciliation is the part of an Odoo accounting implementation that quietly decides whether the finance team trusts the system. Get it right and the month-end close runs in days. Get it wrong and you're chasing unmatched transactions for weeks, your BAS won't tie back to the bank statement, and someone ends up reconciling by hand in a spreadsheet anyway. Australian businesses have a few specific moving parts here, ABA batch payments, GST cash versus accruals reporting, and the quirks of how Australian banks publish statement data, so the setup needs more attention than the standard Odoo accounting guide suggests. This post covers how Odoo bank reconciliation actually works in v19, the realistic options for connecting to Australian banks, how to reconcile ABA batches without manual line-by-line matching, and where most implementations go wrong. It's written for finance managers, controllers, and business owners deciding whether to commit Odoo as the source of truth for the bank. ## **How Odoo bank reconciliation actually works** Odoo reconciles bank statements against three things: vendor and customer payments that already exist in the system, open invoices and bills that haven't been matched to a payment yet, and direct journal entries you create on the fly (interest, fees, transfers). The reconciliation view groups these together and lets you match each statement line to one or more counterparts. When a match locks in, Odoo posts the bank journal entry and closes the statement line. The mechanics are the same whether you're running Community or Enterprise. What Enterprise adds is automatic bank synchronisation, the BAS report, and the reconciliation models that learn from your matches over time. Per Odoo's [v19 bank synchronisation documentation](https://www.odoo.com/documentation/19.0/applications/finance/accounting/bank/bank_synchronization.html), the automatic sync service is only available with a valid Enterprise subscription. Community users can still reconcile, they just have to import files manually. ## **Bank statement feeds for Australian banks** You have three options for getting statement data into Odoo, and the right choice depends on which bank you use, how often you reconcile, and what's actually supported. ### **Automatic bank synchronisation** Odoo connects to Australian banks through third-party aggregators, primarily Yodlee and Salt Edge depending on the bank, with coverage of over 26,000 financial institutions worldwide. In practice for Australian businesses, the big four (CBA, Westpac, ANZ, NAB) and most of the mid-tier banks (Bendigo, BOQ, Macquarie, Suncorp) are supported through one or the other. Before you commit to automatic sync as the production approach, log into Odoo's Accounting Features panel, click "See list of supported institutions," and verify your specific bank and account type appear. We've seen edge cases with business savings accounts and certain merchant-facilitated accounts where the feed is read-only or unavailable. Once connected, statements pull in daily. The catch is the connection occasionally drops and requires re-authentication, which finance teams forget to monitor. Build a weekly "is the sync healthy?" check into the close process, otherwise you'll discover a missing fortnight at month-end. ### **Manual file import (CSV, OFX, CAMT.053)** Per the [v19 bank transactions documentation](https://www.odoo.com/documentation/19.0/applications/finance/accounting/bank/transactions.html), Odoo accepts CAMT.053 (the SEPA cash management format), OFX, QIF, and CSV file imports. For Australian banks, OFX is the most reliable manual format because every major bank exports it directly from their business banking portal. CAMT.053 is rare outside European multinational subsidiaries operating here. CSV works but you have to map the columns yourself the first time, and Australian bank CSVs put the date, description, and amount in different places depending on the bank. The opening balance trap catches new implementations frequently. Odoo expects the first statement line to start from a known opening balance. If you start importing statements halfway through a financial year without entering the opening balance correctly, the running balance in Odoo will never agree with the bank, even if every individual line reconciles. ### **Manual entry (when you'd use it)** For low-volume accounts (a petty cash float, a foreign currency holding account that sees three transactions a quarter), manual entry into a bank journal is fine. We don't recommend it as the default for an operating account. The risk of typos and missed lines outweighs the cost of either the sync subscription or the five minutes it takes to import an OFX file. ## **Matching rules and how Odoo learns** Odoo's reconciliation engine uses what it calls "reconciliation models," which are essentially rules that auto-match common statement lines without human intervention. The default models handle exact-amount matches against open invoices and bills. Custom models let you handle the lines that repeat every month: bank fees, interest, EFTPOS settlement fees, FX margin charges, BAS refunds, and ATO PAYG payments. A model that books a $15 monthly bank fee directly to "Bank Fees" expense as soon as it appears will save a finance team an hour a month. Set up six or seven of these in the first week of the implementation. After that, Odoo's machine-matching also learns from manual choices and will start suggesting the right account for recurring lines automatically. ## **Reconciling ABA batch payments** ABA (Australian Bankers' Association) files are how Australian businesses pay multiple suppliers in a single bank transaction. The bank's statement shows one consolidated debit, but the underlying payments inside Odoo are individual vendor bill payments. This is the moment most accounting platforms fall apart in Australia, and Odoo handles it correctly if configured properly. Per the [Odoo v19 Australia fiscal localisation documentation](https://www.odoo.com/documentation/19.0/applications/finance/fiscal_localizations/australia.html), you enable batch payments in Accounting > Configuration > Settings, then configure each bank journal with the BSB code, Financial Institution Code (the 3-letter abbreviation your bank uses), and your Supplying User Number (the 6-digit identifier the bank issues). Once that's in place, the workflow is: register vendor bill payments using "ABA Credit Transfer" as the payment method, tick the bills to include, click Create Batch, then Verify and Validate. Odoo generates the ABA file and attaches it to the batch. You upload the file to your bank's business banking portal. The next time the bank statement syncs or imports, the statement line shows a single debit for the batch total. In the reconciliation view, you select the Batch Payment tab and match the statement line to the batch in one click. No line-by-line matching, no manual journal entries, just one match. Our [guide to Odoo accounts payable and ABA payments](/blog/odoo-erp-australia-6/odoo-accounts-payable-in-australia-vendor-bills-3-way-matching-and-aba-payments-128) covers the upstream side of this workflow in more detail, including the three-way matching that should happen before any payment ever gets to a batch. ## **Multi-currency and FX revaluation** If you hold a USD or EUR bank account (importers and exporters often do), Odoo records each transaction at the daily rate and revalues the balance to AUD at period end. The revaluation creates an unrealised FX gain or loss journal entry. This is correct accounting, but it adds one more reconciliation step: the bank balance in AUD shifts at month-end based on the closing exchange rate, and the unrealised entry has to reverse on day one of the next period. Two settings to check before you go live. First, the bank account currency must be set at the journal level (not just on the company). Second, the exchange rate source needs to be either the RBA daily rate or a manual override that matches whatever the auditors expect. If those don't match, the FX position on the balance sheet will be a few hundred dollars off every month, which finance teams find harder to ignore the longer it persists. _"The biggest reconciliation problem we fix on inherited implementations isn't matching, it's the opening balance. People start importing statements without setting a clean opening figure, and from that point forward the bank balance in Odoo drifts a few hundred dollars off the actual bank. Two months in, no one trusts the system. Fix the opening balance, set up four or five reconciliation models for recurring lines, and the close goes from days to hours."_ **Josh Craig, Director, Auboros** ## **Where bank reconciliation goes wrong** Three patterns account for most of the implementation problems we see, and all three are avoidable. **Reconciling too infrequently.** Some teams batch the whole month into the last week. By the time you're matching a transaction from 28 days ago, the context is gone and matching becomes guesswork. Reconcile weekly at minimum, daily if you're doing meaningful volume. The MYOB [2025 ERP Trends report](https://www.myob.com/au/insight/post/erp-trends) found 45% of Australian decision-makers say disconnected systems limit their ability to grow, and stale bank reconciliation is one of the practical ways that surfaces. **Treating the bank as the source of truth for GST.** The bank tells you cash moved. It doesn't tell you what GST applied. For accruals-basis BAS reporters, the tax invoice is the source, not the bank line. Per the [ATO's guidance on choosing an accounting method for GST](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst/accounting-for-gst-in-your-business/choosing-an-accounting-method), accruals reporters include GST in the period the invoice was issued or received, not when payment cleared. If you're auto-coding bank lines to GST-inclusive accounts without the invoice already in the system, BAS will be wrong. **Skipping the bank reconciliation step before lodging BAS.** The [ATO's BAS and GST tips](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas/bas-and-gst-tips) explicitly recommend reconciling all bank accounts before lodging. Odoo's BAS report draws from the GL, and if the GL doesn't agree with the bank, the BAS will have gaps. We've seen businesses lodge a BAS that the ATO later corrects when bank transactions were missed. ## **How bank reconciliation feeds the BAS report** The Australian Enterprise localisation includes a native BAS report that draws GST data straight from the GL. Once the bank is reconciled and the underlying invoices and bills are matched to payments, the BAS figures populate automatically. You preview the report from Accounting > Reports > BAS Report (AU), confirm the figures, and either lodge directly or export for the tax agent. Our [guide to Odoo Australian localisation for BAS and STP](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98) covers the BAS workflow end-to-end. The integrity of that report depends on the reconciliation finishing cleanly. Skipped reconciliation is the single most common reason a BAS draft looks wrong in Odoo. If the bank balance ties out and every invoice that's been paid is matched to a payment line, the BAS will agree with reality. If not, it won't. ## **If you're running Xero alongside Odoo** Plenty of Australian businesses run Xero and Odoo in parallel during a transition. The temptation is to reconcile in both systems. Don't. Pick one as the source of truth for the bank, and let the other receive a journal summary. Our post on [running Odoo and Xero at the same time](/blog/odoo-erp-australia-6/odoo-xero-run-together-australia-101) covers the trade-offs, and our [Odoo Xero integration guide](/blog/odoo-erp-australia-6/odoo-xero-integration-australia-how-to-connect-them-and-what-actually-syncs-124) walks through what syncs and what doesn't if you're committing to both systems for the medium term. ## **Frequently asked questions** ### **Does Odoo connect directly to Australian banks?** Yes, through third-party aggregators (Yodlee and Salt Edge) bundled with the Odoo Enterprise subscription. All four major Australian banks and most mid-tier banks are supported. Verify your specific account type in Odoo's bank list before go-live, as some business savings and merchant-facilitated accounts have limited support. ### **What file formats does Odoo accept for bank statements?** Odoo v19 accepts CAMT.053, OFX, QIF, and CSV imports. For Australian businesses, OFX is the most reliable because every major bank exports it from their business banking portal. CSV works but requires column mapping the first time you use it. ### **Can Odoo auto-reconcile ABA batch payments?** Yes. Configure your bank journal with BSB, Financial Institution Code, and Supplying User Number, then create batch payments using the ABA Credit Transfer payment method. When the bank statement shows the consolidated debit, you match it to the batch in a single click from the reconciliation view. ### **Does Odoo handle multi-currency bank accounts?** Yes. Set the currency at the journal level, configure the exchange rate source (RBA daily is the standard in Australia), and Odoo will revalue the balance at period-end and post unrealised FX gains or losses. Confirm the rate source matches what your auditor expects before going live. ### **Should I reconcile daily or weekly?** Weekly at minimum. Daily if you process more than 50 bank transactions a week or if you rely on real-time cash position reporting. Monthly reconciliation makes matching harder because context is lost, and it pushes risk into BAS lodgement. * * * **Considering Odoo for your finance team?** We're a [certified Odoo Silver Partner in Brisbane](/solutions/odoo) and we implement Odoo for Australian mid-market businesses across QLD, NSW, and Victoria. Bank reconciliation, ABA payments, BAS, and STP all sit inside our standard scope. If you want to talk through whether Odoo fits your business and what implementation would look like, [**book a free consultation**](/appointment). No obligation, just a conversation about your current setup. --- # MYOB Acumatica Distribution Edition vs Manufacturing Edition: How to Choose for Your Australian Business - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-distribution-edition-vs-manufacturing-edition-how-to-choose-for-your-australian-business-130 - Category: MYOB Acumatica Australia - Published: 2026-05-30 - Description: Distribution Edition vs Manufacturing Edition of MYOB Acumatica: what's in each, where they overlap, and how Australian businesses choose between them. If you're evaluating MYOB Acumatica and the conversation has moved to which edition you actually need, the question between Distribution and Manufacturing is one of the most common ones we field. The two editions overlap more than the marketing makes obvious, and choosing wrong has real downstream cost: licence selection, implementation scope, training, and how you'll add capability later. This post walks through what's actually in each edition, where they overlap, and the decision points Australian businesses should think through before signing a quote. It's written for operations managers, CFOs, and business owners who've shortlisted MYOB Acumatica and need to make the edition call before procurement starts. ## **What the editions actually are** MYOB Acumatica is sold in industry-aligned editions, and the relevant ones for product-handling businesses are Distribution, Manufacturing, Construction, and Field Service, alongside the more horizontal Standard edition. Per the [MYOB Acumatica product overview](https://www.myob.com/au/erp-software/products/myob-acumatica), each edition bundles the core financials with a set of modules and configurations suited to that industry. Pricing follows MYOB's named-user licensing model with tiered access levels (full access, sales, read-only, executive, and API), plus module-based components depending on the edition chosen. Importantly, editions are not rigid silos. Modules can be added or extended after the fact, and an implementation that starts on one edition can grow into another. But starting on the right one keeps the initial scope manageable and avoids paying for capability you won't use. ## **Distribution Edition: what's in the box** The Distribution Edition is built for wholesale, import, and distribution businesses that buy stock, hold it across warehouses, and sell it to other businesses or direct to consumers. Per [MYOB's inventory and distribution software page](https://www.myob.com/au/erp-software/features/inventory-distribution-software), the core modules in the Distribution Edition are: - **Sales Order Management:** Quotes, sales orders, partial shipments, drop-ship handling, credit limits, customer-specific pricing and discounts. - **Advanced Inventory:** Multi-warehouse and bin-level stock, lot and serial tracking, expiry dates, stock counts (cycle and full), and landed cost. - **Purchase Order Management:** Vendor management, blanket POs, automated replenishment, and three-way matching against goods receipts and vendor invoices. - **Requisition Management:** Internal request and approval workflows that flow into purchase orders. - **Warehouse Management System (WMS):** Wave and batch picking, barcode scanning, directed put-away, and confirmation steps. - **Advanced Financials:** Multi-entity, multi-currency, deferred revenue, and the full general ledger and reporting suite. MYOB's QLD-led [FastStart Wholesale Distribution program](/blog/myob-acumatica-australia-7/myob-acumatica-wholesale-distribution-faststart-australia-103) is a productised version of this edition aimed at Australian importers and distributors who need a faster implementation path. Auboros partners with MYOB on the Queensland delivery of this program. ## **Manufacturing Edition: what's in the box** The Manufacturing Edition includes everything in the Distribution Edition (sales, purchasing, inventory, WMS, financials) and adds the production capability that distribution businesses don't need. Our deep-dive on the [MYOB Acumatica Manufacturing Edition](/blog/myob-acumatica-australia-7/myob-acumatica-manufacturing-edition-production-modes-mrp-and-the-current-release-129) covers the production-side detail. In summary the additional capability includes: - **Bills of Material (BOMs):** Multi-level BOMs, by-products and co-products, phantom assemblies, and engineering change orders. - **Production Orders:** Across all six production modes (make-to-stock, make-to-order, configure-to-order, assemble-to-order, batch process, project-based), with full traceability of labour, materials, and overhead. - **Material Requirements Planning (MRP):** Time-phased net requirements, planned orders, and exception messages that drive purchasing and production scheduling. - **Shop Floor Control:** Operation tracking, clock-in and clock-out, materials issue, and real-time WIP visibility. - **Routings and Work Centres:** Sequence of operations, capacity planning, and standard vs. actual cost variance reporting. - **Engineering Change Control:** Versioned BOMs, change request workflows, and effectivity dates. The 2025 R2 release (which rolled out to MYOB Acumatica customers in the first half of 2026) added the material availability view on the production order screen and improved due date tracking, both of which materially improve scheduling decisions on the floor. ## **Where the editions overlap** This is the part most edition-comparison articles skip. Manufacturing Edition contains everything Distribution Edition contains. Distribution Edition contains everything except production. If your operation is "buy stock, hold it, sell it," Distribution does the job. If your operation is "make stock from inputs, hold the finished goods, sell them," you need Manufacturing. The grey area is light assembly. Businesses that pack kits, assemble bundles from components, or do simple two-step transformations (cut-to-length, bottling from bulk, repackaging) can often handle that within Distribution Edition using kit items, build assemblies, or bills of material at the inventory level. Once the work involves routings, work centres, labour costing, or scheduling against constrained capacity, you've crossed into Manufacturing territory. _"The conversation almost always starts with 'we do some light assembly, so we probably need Manufacturing.' We push back on that. If you're not tracking labour against a work order or scheduling against capacity, Distribution with kit assemblies will do what you need at a lower scope. Manufacturing is the right answer when production planning is a job on its own, not a side effect of inventory."_ **Josh Craig, Director, Auboros** ## **How to choose** ### **When Distribution Edition is enough** Distribution is the right starting point if the business buys and sells finished goods, handles multi-warehouse stock, and the only production-like work involves kitting or simple assembly. Importers, wholesalers, FMCG distributors, hardware merchants, electronics distributors, and most industrial supply businesses fit this pattern. The Australian Bureau of Statistics' [Counts of Australian Businesses to June 2025](https://www.abs.gov.au/statistics/economy/business-indicators/counts-australian-businesses-including-entries-and-exits/latest-release) shows the Wholesale Trade sector grew 0.1% in 2024 to 2025, with stable demand for the kind of inventory and distribution capability this edition is built for. ### **When Manufacturing Edition is necessary** If the business runs production orders, manages BOMs with multiple levels, tracks labour against work centres, or needs MRP to plan purchasing against demand, Manufacturing is the right edition. Food and beverage producers, metal fabricators, electronics assemblers, plastics manufacturers, custom equipment builders, and engineer-to-order businesses all fall here. The cost of starting on Distribution and trying to bolt on Manufacturing later is higher than starting on Manufacturing in the first place, particularly if BOMs and routings need to be set up under live transactional volume. ### **When you need both (or a hybrid)** Some businesses sell finished goods they manufacture and also distribute finished goods they import. The Manufacturing Edition handles both cases because it's a superset of Distribution. Where the question gets interesting is multi-entity structures, where one company manufactures and a sister company distributes. Each company is licensed and configured independently, so the manufacturing entity runs Manufacturing Edition and the distribution entity runs Distribution Edition. MYOB Acumatica's multi-entity capability is included in the Advanced Financials suite that ships with both editions. ## **Practical implementation considerations** Three practical points come up in almost every edition decision. **Don't over-buy upfront.** Manufacturing Edition is heavier to implement than Distribution, and if 80% of the team will never touch the production modules, the licence and training cost is wasted. Start at the edition the business actually operates, and upgrade later if the operation genuinely changes. MYOB's [2025 ERP Trends report](https://www.myob.com/au/insight/post/erp-trends) noted that 45% of Australian decision-makers say disconnected systems limit growth, but the inverse risk (an over-scoped ERP that nobody adopts) is equally real. **Think about the integrations before the edition choice.** If you're connecting to a Cin7 or DEAR inventory system, EDI for grocery chains, a shipping platform like StarshipIT, or a B2B portal, those integrations look different in Distribution vs Manufacturing context. Our [MYOB Acumatica customisation guide](/blog/myob-acumatica-australia-7/myob-acumatica-customisation-australia-118) covers the integration patterns in detail. **Implementation timeline differs.** A Distribution Edition implementation through a productised path like FastStart can be live in 8 to 12 weeks. A Manufacturing Edition implementation typically takes 16 to 24 weeks because BOM data migration, routing setup, and labour rate configuration add real scope. Plan accordingly. ## **What about Construction and Field Service editions?** If the business is in construction or trades, Construction Edition adds job costing, retentions, progress claims, and subcontractor management. Field Service Edition adds dispatching, mobile, and service contract management. Both are separate edition decisions that sit alongside Distribution and Manufacturing rather than competing with them. Our [MYOB Acumatica for construction in Queensland](/blog/myob-acumatica-australia-7/myob-acumatica-for-construction-in-queensland-job-costing-qbcc-compliance-and-what-s-included-105) guide covers the Construction edition in detail. For most businesses, the decision is just Distribution vs Manufacturing, and the other editions only enter the conversation if there's a clear field service or construction operating model. ## **Frequently asked questions** ### **Can you upgrade from Distribution Edition to Manufacturing Edition later?** Yes. Since Manufacturing Edition is a superset of Distribution, an upgrade involves adding the production modules and configuring BOMs, routings, and work centres. There's no data migration between editions because the underlying database is the same. The work is in setting up new modules and training the production team. ### **Does Distribution Edition handle light manufacturing or assembly work?** It handles kitting and simple build assemblies (component A plus component B equals finished item C) without needing the full production module. Once you need routings, work centres, labour tracking, or capacity planning, that's the Manufacturing Edition. ### **Is MYOB Acumatica Manufacturing Edition the same as Acumatica Manufacturing globally?** The underlying platform is the same Acumatica Manufacturing Edition globally, with MYOB packaging it for the Australian and New Zealand market and rolling out releases on a slightly delayed schedule compared to the global product. The 2025 R2 release reached MYOB customers in the first half of 2026, while Acumatica 2026 R1 went GA globally in March 2026. ### **How is each edition priced?** Both editions follow MYOB's named-user licensing model with tiered access levels (full access, sales, read-only, executive, API), plus the module bundle that comes with the edition. There is no separate per-seat or consumption-based pricing component. Specific pricing depends on user count and module selection, and an [official MYOB Acumatica partner](/solutions/myob) can scope a quote based on your business size and complexity. ### **What if we have both manufacturing and distribution in one company?** You licence Manufacturing Edition because it includes the full Distribution capability. There's no benefit to running two editions in the same legal entity. The Manufacturing modules can sit dormant for product lines that are bought-in rather than made. * * * **Need help choosing the right MYOB Acumatica edition?** We're an official MYOB Acumatica Partner based in Brisbane, supporting mid-market businesses across QLD, NSW, and Victoria. We deliver the Queensland FastStart Wholesale Distribution program with MYOB and implement Manufacturing, Construction, and Field Service editions for businesses that need them. Our [manufacturing ERP page](/industries/manufacturing) covers the production side of that decision in more depth. If you want a conversation about which edition fits your operating model and what implementation would look like, [**book a free consultation**](/appointment). No pressure, just an honest read on the scope. --- # Odoo Accounts Payable in Australia: Vendor Bills, 3-Way Matching, and ABA Payments - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-accounts-payable-in-australia-vendor-bills-3-way-matching-and-aba-payments-128 - Category: Odoo ERP Australia - Published: 2026-05-25 - Description: How Odoo 19 handles vendor bills, 3-way matching, ABA batch payments and BAS-ready GST coding for Australian businesses. A practical guide from Auboros. Accounts payable is one of those modules nobody gets excited about until something goes wrong. A duplicate payment, a missing tax invoice at BAS time, a vendor chasing money the system says was paid. Odoo handles AP in a way that catches most of these problems before they cost you, but only if it's set up properly. This post walks through what Odoo's vendor bill workflow actually does, how 3-way matching works in v19, where the Australian localisation fits in, and the AP mistakes we see most often during implementations. ## **What Odoo's vendor bill workflow does** A vendor bill in Odoo is the supplier's invoice, recorded against a purchase order and a goods receipt. The bill posts to your accounts payable ledger, picks up GST coding from the product or expense account, and queues for payment. That part is standard ERP behaviour. Where Odoo earns its keep is the upstream automation. The Accounting module captures vendor bills three ways: manual entry, email-to-bill (forward a PDF to a dedicated inbox and Odoo creates a draft), and AI document extraction. The [v19 vendor bill documentation](https://www.odoo.com/documentation/19.0/applications/finance/accounting/vendor_bills.html) covers each option. The OCR has improved noticeably in v19 and now picks up line items, totals, and tax components from most Australian supplier formats. We cover the v19 AI features in more detail in our [AI in Odoo guide](/blog/odoo-erp-australia-6/ai-in-odoo-australia-2026-102). Bills that arrive against an active PO get linked automatically when the supplier and reference match. Bills without a PO post straight to the relevant expense account. Both routes end at the same place: a draft bill that needs review before posting. ## **3-way matching: how it works in v19** 3-way matching compares the PO, the goods receipt, and the vendor bill before a payment is approved. It's the single feature that prevents most accidental overpayments. You enable it under Purchase, then Configuration, then Settings. The catch is that 3-way matching only works when the bill control policy is set to Received quantities, not Ordered quantities. With Received quantities, Odoo only allows you to bill what's been physically receipted, so a 100-unit PO that only had 80 units delivered will block a 100-unit bill. The [control policies documentation](https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/purchase/manage_deals/control_bills.html) covers both settings in detail. Once enabled, every vendor bill displays a Should Be Paid field. It defaults to Yes, switches to Exception if any field is edited away from the PO and receipt values, and switches to No if the bill exceeds what was received. The exception flag doesn't block the payment, which is deliberate. It's a prompt to check, not a hard stop. For businesses with a high volume of partial receipts (we see this constantly in wholesale and trades), 3-way matching is non-negotiable. For services-only businesses that mostly receive non-stock items, it adds friction without much benefit. We covered the upstream PO side of this in our [Odoo purchasing module post](/blog/odoo-erp-australia-6/odoo-purchasing-module-australia-purchase-orders-rfqs-and-what-you-can-automate-119). ## **GST coding and ATO tax invoice requirements** An Australian business claiming GST credits needs valid tax invoices on file. The [ATO's tax invoice page](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst/tax-invoices) lays out the rules. For purchases over $82.50 including GST, the invoice has to show the supplier's identity, ABN, invoice date, a brief description, the GST amount (or a statement that GST is included), and the extent to which each sale is taxable. For invoices of $1,000 or more, the buyer's identity or ABN also has to appear. Odoo's Australian localisation ships with the standard tax codes for the GST regime: 10% GST on purchases, GST-free purchases, capital purchases, and the input-taxed and export codes. Where businesses get into trouble is the default tax on the supplier record. If a vendor's default tax isn't set correctly, every bill from that supplier will post with the wrong code until someone notices at BAS reconciliation. The fix is a five-minute review of the supplier master, but it's the kind of thing nobody does until the BAS reconciliation falls over. For BAS preparation specifically, the source-of-truth principle from our [Australian localisation post](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98) applies here too. If Odoo is your accounting system, vendor bills posted in Odoo are what BAS draws from. If you're running Odoo alongside Xero (covered in the [run-together guide](/blog/odoo-erp-australia-6/odoo-xero-run-together-australia-101)), you need a clear rule on which system is BAS-authoritative. ## **ABA batch payments for Australian banks** Most Australian banks accept ABA files for batch EFT payments. Upload one file, pay all your suppliers in a single batch run. Odoo supports ABA generation natively through the l10n\_au\_aba module that ships with the Australian localisation. Setup lives under Accounting, then Configuration, then Settings, where you enable Batch Payments. Each bank journal needs its BSB and account number, and the company record needs a valid ABN and bank account configured for ABA. The [batch payments documentation](https://www.odoo.com/documentation/19.0/applications/finance/accounting/payments/batch.html) walks through the configuration. Once set up, the workflow is: select the bills you want to pay, register a batch payment, generate the ABA file, upload to your bank's portal, then reconcile the batch payment against the bank statement when the money clears. The reconciliation step is where AP work pays off. Odoo's bank reconciliation matches the batch against the original batch payment record, which means individual vendor bills get marked paid in one click rather than line by line. The first time you do this on a 40-supplier payment run, the time saved over manual matching is obvious. _"AP is the module clients ignore in the demo and then ask for help with three months after go-live. Getting 3-way matching, default supplier tax codes, and the ABA setup right during the build saves a quarter's worth of cleanup later. None of it is hard, it just needs to happen before bills start flowing through the system."_ **Bill Alvarez, Practice Manager, Auboros** ## **The AP mistakes we see most often** Five patterns come up in nearly every Odoo AP review we run: - **Default supplier tax codes never set.** Bills inherit the wrong GST treatment, and the BAS reconciliation surfaces it weeks later. - **Bill control left on Ordered quantities.** 3-way matching can't fire, and partial deliveries get over-billed before anyone notices. - **OCR-extracted bills posted without review.** The OCR is good, not perfect. A 10-second check catches a tax-code or supplier mismatch on roughly one bill in ten. - **ABA file generated but not reconciled to the batch payment.** The bank statement clears but the AP ledger still shows the bills as unpaid because the matching step was skipped. - **Vendor records duplicated.** Same supplier added twice with different name variants, so payment history splits across two records. Easy to fix with a merge, easier still to prevent with a strict vendor creation process. ## **When AP automation actually pays off** For businesses processing fewer than 30 vendor bills a month, the OCR and 3-way matching features are nice but not transformational. Manual entry and a simple review process work fine at that volume. Above 100 bills a month, the calculus changes. OCR plus 3-way matching plus ABA batch payments cuts AP team hours significantly, and the audit trail Odoo creates makes BAS reconciliation faster. The [MYOB 2025 ERP Trends report](https://www.myob.com/au/insight/post/erp-trends) found 45% of Australian decision-makers say disconnected systems limit growth. AP is one of those points where an integrated ERP earns its keep over a separate accounting tool and a spreadsheet-based approvals process. ## **Frequently asked questions** ### **Does Odoo support ABA payments for all Australian banks?** Yes. The ABA format is a standard accepted by all major Australian banks. Odoo generates the file from the batch payment record; you upload it through your bank's business portal. Each bank's portal interface differs, but the file format is the same. ### **What's the difference between Ordered and Received bill control?** Ordered quantities creates a draft bill as soon as the PO is confirmed, based on what was ordered. Received quantities only creates a bill after goods are receipted, based on what actually arrived. 3-way matching only works with Received. For inventory businesses, Received is almost always the right choice. ### **Can Odoo capture vendor bills from email automatically?** Yes. Each accounting journal can have a dedicated email alias. Suppliers (or your AP inbox) forward PDF invoices to that address, and Odoo creates a draft bill with the OCR-extracted data. The bill still needs a human review before posting, but the data entry step is automated. ### **How does Odoo handle GST credits on imports?** GST on imports is paid to the Australian Border Force, not the overseas supplier, so the vendor bill from the supplier is GST-free and a separate ABF bill carries the GST component. The [ATO's GST credits guidance](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst/claiming-gst-credits/when-you-can-claim-a-gst-credit) covers the rules. In Odoo this is set up as a separate ABF supplier record with the right tax code, plus a landed cost entry to allocate the GST and duty to the underlying stock. ### **Do I need the Enterprise version for these features?** Vendor bill management, 3-way matching, and ABA batch payments are all in Community. The OCR and AI document extraction features are Enterprise. For most Australian businesses running Odoo at any scale, Enterprise is the practical choice because of the support and upgrade path. * * * **Want your Odoo AP workflow reviewed?** If your Odoo accounts payable is taking longer than it should, or the BAS reconciliation keeps surfacing surprises, the fix is usually in the configuration rather than the software. We've cleaned up AP setups for Australian businesses across wholesale, trades, manufacturing, and services. If you'd like a second opinion on your AP workflow, [**book a free consultation**](/appointment). We configure vendor bills, 3-way matching and ABA payments as part of our [Odoo implementation work for Australian businesses](/solutions/odoo). Brisbane-based, no obligation. --- # MYOB Acumatica Manufacturing Edition: Production Modes, MRP, and the Current Release - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-manufacturing-edition-production-modes-mrp-and-the-current-release-129 - Category: MYOB Acumatica Australia - Published: 2026-05-25 - Description: A practical guide to MYOB Acumatica Manufacturing Edition: production modes, MRP, BOMs, shop floor, and what's current for Australian manufacturers in 2026. If you've been looking at MYOB Acumatica for a manufacturing business, you've probably noticed the editions. Standard, Distribution, Manufacturing, Construction. They're not just marketing tiers. Each edition adds modules the others don't have, and Manufacturing Edition is where MRP, production orders, BOMs, routings, and shop floor management actually live. This post covers what's inside Manufacturing Edition, the six production modes it supports, what's current in the 2025 R2 release (and what's coming in 2026 R1), and where Manufacturing Edition fits in the Australian mid-market. ## **What Manufacturing Edition gives you that Standard and Distribution don't** MYOB Acumatica Standard is the financials-and-inventory baseline. Distribution Edition (the version inside the [FastStart Wholesale Distribution](/blog/myob-acumatica-australia-7/myob-acumatica-wholesale-distribution-faststart-australia-103) program) adds advanced warehouse management, requisitions, and sales order workflows for wholesalers. Manufacturing Edition adds the modules a maker needs that a distributor doesn't: bills of material, routings, production orders, MRP, product configurator, and shop floor control. Construction Edition is a separate path again, covered in our [Construction in Queensland post](/blog/myob-acumatica-australia-7/myob-acumatica-for-construction-in-queensland-job-costing-qbcc-compliance-and-what-s-included-105). The edition you pick at implementation determines what's available to turn on later, so getting it right at scoping matters. The other piece worth knowing is that Manufacturing Edition includes all of Standard and most of Distribution. It's additive, not a separate platform. A business that needs both wholesale distribution and light manufacturing typically lands on Manufacturing Edition because it covers both, even though the headline is "manufacturing." ## **The six production modes, in plain English** MYOB Acumatica's manufacturing module supports six distinct ways of running production. Most businesses use more than one across their product range, and the platform handles that within a single database. The modes are: - **Make to Stock (MTS).** You build to a forecast, ship from stock. Classic FMCG, consumer goods, standard product lines. - **Make to Order (MTO).** Production triggered by a sales order. Common in custom industrial or B2B manufacturing where every unit has a destination before it's built. - **Assemble to Order (ATO).** Components held in stock, final assembly happens after the order lands. Furniture, equipment with options, anything where the variation is in the last build step. - **Configure to Order (CTO).** The product configurator builds a unique BOM for each order based on customer choices. Used heavily in equipment, machinery, and complex assemblies. - **Batch process.** Recipes and batch sizing for food, beverage, chemicals, cosmetics. Includes the lot tracking and variable-yield handling those industries need. - **Project-based.** Production tied to a project record, with revenue and cost rolling up to the project rather than the order. Engineering-to-order and one-off builds. The platform's strength is that a single business running, say, batch production for one product line and ATO for another doesn't need two systems. The downside is that flexibility creates implementation choices, and the choices need someone who understands what each mode actually does in practice. ## **Material requirements planning (MRP)** MRP is the planning engine. It looks at sales orders, forecasts, stock on hand, open POs, and lead times, and generates planned production orders and planned purchase orders to fill the gaps. Run MRP weekly (or daily, depending on your business), review the planned orders, release the ones that make sense, and convert them into firm production and purchase orders. Manufacturing Edition's MRP handles multi-level BOMs (parent assembly with sub-assemblies with components), lead time offsets, lot sizes, and safety stock by warehouse. The depth of configuration is one of the reasons we recommend running MRP in a sandbox for the first month after go-live, with planners reviewing each run before it goes against the live database. ## **BOMs, routings, and shop floor** A bill of material lists the components needed to make a parent product. A routing lists the operations (cut, weld, paint, pack) and the work centres each operation runs on. Together they define how a production order is costed, scheduled, and tracked. Shop floor control is where production orders get reported on. Operators log time and material against the work centre, scrap is recorded, and the system updates work-in-progress (WIP) and finished goods in near real time. The shop floor module supports barcode scanning and tablet-based operator interfaces, which matters more in practice than it sounds in theory. The data you get out of the system is only as good as the data operators are willing to put in. ## **The current release: 2025 R2, with 2026 R1 on the horizon** The release MYOB Acumatica customers in Australia and New Zealand are on right now is 2025 R2. It rolled out to MYOB customers in the first half of 2026 after the local team finished the ANZ-specific localisation work on top of the global Acumatica 2025 R2 codebase. The [MYOB Spring Release Hub](https://info.myob.com/myob-acumatica-spring-release-hub-2025) documents the major changes. The manufacturing-specific updates worth knowing are: - **Material availability view on production orders.** You can now see whether the materials needed for a run are on hand before you commit labour and machine time. Previously this took a separate inventory check. - **Due date tracking on production orders.** Shop floor supervisors get clearer visibility into which orders are on schedule and which are slipping, surfaced on the production order screen rather than a separate report. - **Production scheduling with retained constraint dates.** Schedules now hold to the dates you've set rather than recalculating every time the dependency tree shifts. - **AI features across finance and operations.** OCR-powered AP bill creation, automated expense receipts, anomaly detection for costs and margins. Useful for manufacturing finance teams running cost analysis across production orders. Globally, Acumatica 2026 R1 reached general availability at the end of March 2026, with bigger AI features (AI Assistant, AI Studio, document tagging, modern UI as default). For MYOB Acumatica customers, that release is expected in Early Access toward the end of 2026, with broader rollout in early 2027 once the ANZ localisation work is complete. If you're scoping a new implementation now, you'll go live on 2025 R2 and upgrade to 2026 R1 inside your first 12 months. The [MYOB Enterprise Support knowledge base](https://enterprisesupport.myob.com) tracks what landed in each release; verify release-specific behaviour there before committing to it. _"Manufacturers underestimate how much of the implementation is in BOM accuracy and routings before you ever switch MRP on. We've worked with manufacturers who had BOMs in a spreadsheet for ten years, and the first month of an Acumatica project is just rebuilding them properly. It's not the system's fault, but it's the work that needs doing."_ **Bill Alvarez, Practice Manager, Auboros** ## **Where Manufacturing Edition fits, and where it doesn't** Australian manufacturing isn't a small market. The [ABS June 2025 Counts of Australian Businesses release](https://www.abs.gov.au/statistics/economy/business-indicators/counts-australian-businesses-including-entries-and-exits/latest-release) recorded the manufacturing sector growing 7.0%, its highest growth on record. Industry value added sits around $134.8 billion. Manufacturers in the $5M to $200M revenue band are the typical fit for MYOB Acumatica Manufacturing Edition. It fits well when you need: - A single platform across financials, inventory, and production rather than three separate systems - Multi-level BOMs and routings with proper costing - Production order tracking with shop floor data capture - MRP that respects your real lead times and constraints - Local payroll, BAS, and STP compliance (covered in our [payroll post](/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97)) It fits poorly when you're a single-line repetitive manufacturer with very simple BOMs and no routing variation, where a much smaller production system would do. It also fits poorly when manufacturing is incidental to a distribution business; Distribution Edition will be cheaper to run and easier to manage. Pricing follows the standard MYOB Acumatica model: named-user licensing with tiered access levels (full access, sales, read-only, executive, API), plus module selection that includes the Manufacturing Edition components. Total cost depends on the user mix, the modules turned on, and any customisation. We don't quote ranges in posts because the spread is too wide; [a scoped quote](/appointment) is the practical way to get a real number. ## **Frequently asked questions** ### **What's the difference between MYOB Acumatica Distribution Edition and Manufacturing Edition?** Distribution Edition covers advanced warehouse management, requisitions, and wholesale sales workflows. Manufacturing Edition adds BOMs, routings, production orders, MRP, product configurator, and shop floor control. Manufacturing Edition includes most of Distribution Edition's capability, so businesses doing both usually choose Manufacturing. ### **Does MYOB Acumatica support batch process manufacturing for food and beverage?** Yes. Batch process is one of the six production modes and includes recipes, batch sizing, lot tracking, and variable yields. It's used by Australian food and beverage manufacturers as well as cosmetics and chemicals producers. ### **How does the product configurator work?** The configurator builds a unique BOM and routing for each sales order based on customer-selected options. It's used heavily in configure-to-order manufacturing for equipment, machinery, and complex assemblies. The configuration rules are set up once and reused across orders. ### **Can I switch editions later if my business needs change?** You can add modules and move to a higher edition, but the upgrade involves licensing and configuration work. It's not a single click. The practical advice is to scope the edition for where the business will be in 18 to 24 months, not just today. ### **How long does a Manufacturing Edition implementation take?** For a mid-market manufacturer with relatively clean BOMs and a single site, four to six months is realistic. Multi-site manufacturers, businesses with thousands of BOMs needing rebuilding, or complex shop floor integration push that timeline out. Our [implementation services post](/blog/myob-acumatica-australia-7/choose-right-myob-acumatica-implementation-services-5) covers what the phases look like. * * * **Looking at MYOB Acumatica for your manufacturing business?** Edition selection is the single most consequential choice early in a manufacturing ERP project. Getting it wrong means paying for capability you don't use, or hitting a wall in year two. We're a [Brisbane-based MYOB Acumatica implementation partner](/solutions/myob) with manufacturing experience across Queensland and the eastern seaboard, and our [manufacturing ERP page](/industries/manufacturing) covers the wider platform decision. If you'd like to scope an implementation or compare Manufacturing Edition against alternatives, [**book a free consultation**](/appointment). No obligation. --- # Odoo Implementation Services Australia: What You're Actually Buying, Phase by Phase - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-implementation-services-australia-126 - Category: Odoo ERP Australia - Published: 2026-04-28 - Description: What Odoo implementation services deliver in Australia. Phases, deliverables, team roles, pricing structures, and what to expect at go-live and after. You've decided Odoo is the right platform. Now you need to know what an implementation actually involves, who does the work, what it costs, and what you'll have when you're done. This is the practical version of that conversation. Most "Odoo implementation services" pages on the internet are sales brochures. This one is the work breakdown: phases, deliverables, team composition, pricing structures, and the parts that go wrong if you skip them. If you want the broader explanation of what Odoo implementation is in the first place, our [complete guide to Odoo implementation in Australia](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) covers that. This post covers the services you'd actually be buying from a partner. ## **What "Odoo implementation services" actually covers** Implementation services are the work a partner does to take Odoo from a blank instance to a working system your team uses every day. That's a wider scope than people often realise. It's not just installing the software (Odoo's hosted on Odoo.sh, Odoo Online, or your own cloud, so installation is rarely the hard part). The work is in the configuration, the data, the integrations, the training, and the change management. Most Australian implementations include some combination of: - **Discovery and scoping:** Understanding your processes, mapping them to Odoo modules, identifying gaps that need customisation. - **Configuration:** Setting up the modules you've licensed (Sales, Inventory, Accounting, Manufacturing, etc.) to match how your business actually runs. - **Customisation:** Building features Odoo doesn't ship with out of the box. Custom fields, workflows, reports, and occasionally entire modules. - **Australian localisation:** Configuring GST tax codes, BAS reporting, Single Touch Payroll if applicable, ABN handling, and Australian banking. - **Data migration:** Moving customers, suppliers, products, opening balances, and historical transactions from your old system. - **Integration:** Connecting Odoo to anything else you run (Xero, Shopify, freight, banking, EDI). - **Testing:** User acceptance testing with your team, end-to-end scenario testing. - **Training:** Role-based training for the people who'll use the system every day. - **Go-live and stabilisation:** Cutover, hypercare support, and the first month of real-world use. What's not typically included: ongoing user support after stabilisation (that's a separate support agreement), license fees (those go to Odoo SA directly), and infrastructure (Odoo.sh hosting is a separate Odoo SA charge if you choose it). ## **The four phases of an Odoo implementation** Implementations work in phases rather than as one continuous block. Each phase has its own deliverable and its own decision point. If something's wrong, the right time to find out is at the end of a phase, not during go-live. ### **Phase 1: Discovery and scoping (weeks 1 to 2)** The first two weeks are interviews and process mapping. We sit with your operations, finance, sales, and inventory leads (whoever applies) and walk through how the business runs today. Not how the org chart says it runs. Actually runs. The output is a scoping document that lists every process, the Odoo module or feature that handles it, any gaps that need customisation, the data sources we'll migrate, and the integrations we'll build. It also includes the timeline, team composition, and a fixed-fee quote (for fixed-fee engagements) or an estimate range (for time and materials). This is the phase where projects get killed if they're going to be killed. If discovery surfaces that Odoo isn't actually the right fit, we'll say so. That's rare but it does happen, particularly when the business has a very specialised industry vertical Odoo doesn't cover well out of the box. ### **Phase 2: Configuration and customisation (weeks 3 to 8)** This is the build. Six weeks is typical for a mid-market scope. Less if your processes are standard. More if you've got significant custom development. The work splits between functional consulting and development. Functional consultants set up modules, configure workflows, build reports, and handle Australian localisation. Developers write any custom modules, build integrations, and handle data migration scripts. Both work in parallel from week three. Australian localisation specifically means configuring the AU fiscal localisation package: tax codes that match the [Business Activity Statement (BAS) structure](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas), ABN fields, ATO-compatible report formats, and Single Touch Payroll (STP) if Odoo Payroll is being used. The [Odoo v19 Australia documentation](https://www.odoo.com/documentation/19.0/applications/finance/fiscal_localizations/australia.html) covers what's in the box; we cover the gaps in our [Australian localisation guide](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98). By the end of this phase, you have a configured system in a staging environment that matches the scoping document. Not in production yet. Not with real data yet. But functionally complete. ### **Phase 3: Data migration and UAT (weeks 8 to 12)** Data migration runs in parallel with user acceptance testing. UAT is your team using the system on staging with realistic data, working through scenarios from the scoping document. We sit with them, fix bugs, adjust configuration where it doesn't match how they actually work, and document the gaps. Data migration is its own discipline. Customer master data, supplier master data, products, opening balances, and historical transactions all need to come across cleanly. We typically run migration three times: a test migration to validate the script, a dress rehearsal a week before go-live, and the final migration on cutover weekend. The biggest risk in this phase is bad source data. If your old system has duplicate customer records, missing tax codes, or inconsistent product naming, those problems migrate too. Cleaning up source data before migration is almost always faster than fixing it in Odoo after. ### **Phase 4: Go-live and stabilisation (weeks 12 to 14)** Cutover is usually a long weekend. Production data migrates Friday night, the team logs in Monday morning, and we're on-site or on Slack for the first two weeks of real use. This is hypercare. The team will hit edge cases that didn't show up in UAT. Some will be configuration tweaks. Some will be training gaps. A few will be real bugs that need code changes. By the end of week 14, the daily operational issues should be down to a normal volume and you've moved from project mode to support mode. That's when implementation services formally end and ongoing support arrangements take over. ## **Who does what on an implementation** The team you'll work with from a partner is usually four to five people, plus your team. Each role does specific things and you should expect to meet all of them. - **Project manager:** Single point of contact, runs status meetings, manages timeline and budget, escalates issues. The PM is the person you call when something's not on track. - **Functional consultant (or two):** The Odoo experts who configure modules, run training, and own the UAT process. Most of your day-to-day project communication runs through this role. - **Developer:** Builds custom modules, integrations, data migration scripts. Often invisible to the business but essential. - **Solution architect:** On larger projects, sits across the design and signs off on technical decisions. On smaller projects this role merges with the senior functional consultant. - **Data migration specialist:** On complex migrations, a dedicated role. On simple ones, the developer handles it. From your side, you'll need a dedicated project owner (someone who can make decisions in the room), process owners for each major area (sales, inventory, finance, etc.), and a tester team for UAT. Implementations stall when the customer side doesn't have the bandwidth committed up front. ## **What's typically in scope, and what isn't** Scope is the single biggest source of implementation conflict, so it's worth being explicit. Most fixed-fee Odoo implementations include the modules listed in the scoping document, the configuration and customisation defined there, the integrations specified, the data migration listed, and the training rounds specified. What's typically out of scope unless explicitly added: - **New requirements discovered after scoping:** Handled via change requests, not absorbed into the original fee. - **Process re-engineering:** If you want to redesign how a department works during the project, that's consulting, not implementation. - **Hardware procurement:** Barcode scanners, mobile devices, payment terminals. We can advise but don't supply. - **Third-party software licenses:** If your integration needs a paid Xero plan or a Shopify upgrade, that's your cost. - **Ongoing support after stabilisation:** Separate agreement. - **User adoption coaching:** Training is included; one-on-one coaching with reluctant users usually isn't. ## **How Odoo implementation services are priced** There are two pricing models in active use across the Australian Odoo market: fixed-fee packages and time and materials. Both are legitimate. They suit different projects. ### **Fixed-fee packages** The partner quotes a single price for a defined scope. You know what you'll pay before you start. Change requests during the project are quoted as adjustments. This works well for businesses that have done their homework on requirements, want budget certainty, and are willing to invest in a thorough scoping phase up front. Auboros publishes our fixed-fee implementation pricing on the [Odoo implementation packages page](/odoo-implementation-packages-for-australian-businesses) precisely because most partners don't, and budget transparency is a fair thing to expect when you're spending six figures on a project. ### **Time and materials engagements** The partner bills hours at an agreed rate. You pay for what you use. This works well for projects where the scope genuinely can't be defined up front (highly customised builds, R&D-style projects, ongoing module rollouts) and you trust the partner to be honest about effort. The risk with T&M is open-ended budget. The protection is regular budget reviews, capped phases, and a partner who'll tell you when scope is creeping rather than just billing through it. ### **When each model fits** Fixed-fee suits 80% of mid-market Australian implementations. Most businesses have well-understood processes; the unknown is how Odoo configures around them, and a partner who knows the platform can scope that confidently after a two-week discovery. T&M suits the other 20%, typically heavily customised builds or businesses making significant process changes during the rollout. _"The single biggest predictor of a clean Odoo implementation isn't budget or scope size. It's whether the customer has someone with authority to make decisions in the room every week. Without that, every tiny choice escalates and projects drift."_ **Bill Alvarez, Practice Manager, Auboros** ## **What "go-live" actually looks like in week one** The first Monday after cutover is the longest day of the project. Your team is using the new system for real, with real customers, real orders, real money. Things will go wrong. The question is how quickly they get fixed. A typical week-one looks like: 10 to 30 issues raised on day one (most are training questions, not bugs), down to half that by Wednesday, down to a normal support volume by the end of the week. We're on-site or on a continuous Slack channel through that week. By Friday, the team is taking longer to ask each question because they've started to remember the answers from yesterday. Common week-one issues: tax codes that don't match a specific edge case, report formats that need adjustment, printer setup for new invoice templates, user permissions that need broadening or tightening. None of these are existential. All of them get fixed inside a day. ## **What happens after go-live (support transition)** Implementation services formally end at the close of stabilisation, usually two weeks after cutover. After that, ongoing support takes over. We offer support agreements ranging from incident-only (you raise tickets when something breaks) through to managed service (we own day-to-day administration of your Odoo environment). The right choice depends on whether you have an internal Odoo admin and how complex your customisations are. The handover from project to support is a deliberate event, not a slow drift. Documentation, runbooks, custom code repositories, and access lists transfer formally. The PM and consultants who built the system stay available for a defined period of post-implementation review, usually 30 days after stabilisation ends. ## **Frequently asked questions** ### **How much do Odoo implementation services cost in Australia?** For a mid-market business, expect $30,000 to $150,000 depending on scope. Smaller, simpler implementations with off-the-shelf configuration land at the lower end. Multi-module rollouts with customisation, integrations, and data migration sit in the middle to upper range. Auboros publishes fixed-fee package pricing for typical implementations on our packages page; partners who don't publish pricing usually quote on a project-by-project basis after scoping. ### **How long does an Odoo implementation take?** Twelve to fourteen weeks is typical for a mid-market scope. Smaller, single-module rollouts can land in six to eight weeks. Heavily customised builds or multi-entity rollouts can stretch to six months. Our [implementation timeline guide](/blog/odoo-erp-australia-6/how-long-does-an-odoo-implementation-take-in-australia-93) covers the variables. ### **What's the difference between an Odoo implementation company and an Odoo partner?** Any company can call itself an "Odoo implementation company." Odoo SA verifies and tiers official partners (Learning, Ready, Silver, Gold) based on certifications and customer outcomes. Working with a verified partner gives you access to the partner network resources and confirms the team has been through Odoo's certification track. Auboros is a Silver Partner, listed on the official [Odoo partner directory](https://www.odoo.com/partners). ### **Can I implement Odoo myself without a partner?** For very small businesses with simple needs, possibly. For mid-market businesses with multi-module scope, customisation needs, and Australian compliance requirements (GST, BAS, Single Touch Payroll), self-implementation typically costs more in time and rework than it saves in fees. The implementation isn't installing the software, it's making the configuration decisions correctly. ### **What happens if I want to change scope mid-project?** Scope changes get quoted as change requests on fixed-fee engagements, or absorbed into the running budget on time and materials. Most projects have one to three change requests. The partner should walk you through the cost and timeline impact before either party agrees to the change. ### **How do I pick the right Odoo implementation partner?** Look for verified Odoo certification (check odoo.com/partners), industry experience matching your business, references from similar Australian customers, and pricing transparency. The [Odoo consultant vs partner guide](/blog/odoo-erp-australia-6/odoo-consultant-vs-certified-odoo-partner-australia-enterprise-implementation-guide-2026-86) covers what to ask in evaluation calls. * * * **Looking for an Odoo implementation partner in Australia?** We're a Brisbane-based Odoo Silver Partner running fixed-fee implementations across Queensland, NSW, and Victoria. Our [Odoo services page](/solutions/odoo) covers what we deliver; our [packages page](/odoo-implementation-packages-for-australian-businesses) covers what it costs. If you're scoping an implementation and want a straight conversation about timeline, scope, and budget, [**book a free consultation**](/appointment). We'll work through your requirements and give you a realistic read on what implementation would look like. --- # Odoo vs Cin7 Core Australia: What Happens When You Outgrow Inventory Software - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-vs-cin7-core-australia-121 - Category: Odoo ERP Australia - Published: 2026-04-28 - Description: Cin7 Core handles inventory well. Odoo adds accounting, CRM, manufacturing and payroll in one system. Here's how to compare them for your Australian business. Most businesses that end up comparing Odoo and Cin7 Core aren't doing a first-time software selection. They're already on Cin7 Core, it's doing what it does, and then something changes. Revenue grows. The product range gets more complex. Someone asks why the accounting lives in Xero but the inventory lives in Cin7 and the sales team is still working from spreadsheets. That's the moment the comparison becomes urgent. This covers what Cin7 Core actually is, where it fits well, where it starts to struggle, and how Odoo compares when you're thinking about replacing or consolidating your software stack. We'll be direct about where each product wins, because the honest answer saves everyone time. ## **What Cin7 Core is (and where it came from)** Cin7 Core was known as DEAR Systems until January 2023, when its parent company Cin7 rebranded the product. Cin7 itself was a separate inventory platform before that, and the two products still have different feature sets and pricing structures. When people say "Cin7," they're sometimes referring to Cin7 Core (the former DEAR Systems product, focused on smaller businesses) and sometimes to Cin7 Omni (the original Cin7 product, aimed at larger operations and enterprise accounts). If a sales conversation gets confusing, ask which product they're actually proposing. Cin7 Core is owned by Rubicon Technology Partners. The product serves thousands of customers globally, with an Australian office and a network of local implementation partners. It's built primarily for product-based businesses that need inventory management, order processing, and basic financial tracking. Its integration ecosystem connects it to Xero, QuickBooks, Shopify, Amazon, and a range of other platforms. For current feature specifics, the [Cin7 Core product page](https://www.cin7.com/pricing/) is the source of truth. ## **What Cin7 Core does well** For businesses selling physical products, Cin7 Core covers the essentials competently. Inventory tracking, purchase orders, sales orders, basic warehouse management, and batch or serial number tracking for products that require it. The reporting is functional for stock-level visibility, and the interface for managing product catalogues and pricing is reasonably accessible without extensive training. The integration with Xero is Cin7 Core's most common deployment pattern in Australia. Cin7 Core handles inventory and order fulfilment; Xero handles accounts payable, accounts receivable, and the general ledger. For a business doing a straightforward volume of sales with consistent products, this combination works and doesn't require a significant implementation project to get running. Cin7 Core is also genuinely faster to get started with than Odoo for a simple use case. A small product business with a clear catalogue and a standard Xero setup can be operational in weeks. If you're a 5-person business moving products without much complexity, Cin7 Core doesn't need a lot of configuration to earn its keep. ## **Where businesses start hitting the ceiling** Cin7 Core's limitations become visible when a business grows beyond its design envelope. The most common friction points reported by businesses looking to switch fall into a few categories. **No native accounting module.** Cin7 Core doesn't include double-entry accounting. It tracks financial data at an inventory and order level, but your general ledger, bank reconciliation, BAS preparation, and financial reporting all live in Xero or QuickBooks. That means two subscription costs, two systems to keep reconciled, and any data discrepancy between them becomes your problem to diagnose manually. This split is exactly the pain point the [2025 MYOB ERP Trends report](https://www.myob.com/au/insight/post/erp-trends) captures when it finds 45% of Australian decision-makers say disconnected systems actively limit their ability to grow. For businesses processing high transaction volumes or dealing with complex cost of goods calculations, the split creates ongoing overhead. **No CRM pipeline.** There's no native sales pipeline, lead tracking, or opportunity management in Cin7 Core. If your business has a sales team following up prospects, you're adding a third system. CRM, inventory, and accounting each live in separate products, and integration points between them are typically one-directional or require middleware. **Manufacturing is limited to basic assembly.** Cin7 Core supports bill of materials (BOM) and basic production orders. If your manufacturing involves work orders, machine routing, shop floor control, quality inspection steps, or multi-level BOMs with labour and overhead costing, Cin7 Core runs out of capability fairly quickly. Businesses that move from simple product assembly into actual manufacturing processes typically find themselves evaluating a manufacturing module or a new platform entirely. **Customisation is constrained.** Cin7 Core's architecture doesn't allow for the kind of workflow customisation or module extension that open-source or highly configurable platforms support. If your business has non-standard processes, approval workflows, or reporting requirements outside the standard template, your options are limited to what the product supports natively. **User cost structure.** Cin7 Core's pricing is per-user at higher tiers, and several businesses have noted publicly on Capterra and similar review platforms that costs have increased substantially over the past few years, with some describing pricing as having nearly doubled since they first signed up. For businesses with growing teams, the cost projection matters when doing a full comparison. ## **How Odoo compares: one system vs a stack** The core difference between Odoo and Cin7 Core isn't that one does inventory better than the other. It's that Odoo is a full ERP and Cin7 Core is an inventory management platform with financial connectors. That distinction shapes every comparison. Odoo includes native accounting, inventory, purchasing, CRM, sales, manufacturing, project management, payroll, field service, and website management, all in one platform with a shared data layer. When an order is confirmed in CRM, it flows to inventory. When goods are received against a purchase order, stock updates and a vendor bill is created for accounts payable. There's no reconciliation between systems because there's only one system. Our post on the [Odoo inventory management module](/blog/odoo-erp-australia-6/odoo-inventory-management-australia-106) covers how that side of the platform works in detail, but the short version is that inventory in Odoo isn't siloed. For businesses that need manufacturing depth beyond basic assembly, Odoo's manufacturing module supports multi-level BOMs, work orders, routing, shop floor tracking, and quality control steps. For businesses distributing products that require lot or serial traceability, such as food products or medical devices, Odoo's traceability covers the full product journey from purchase receipt to customer delivery. The [Odoo manufacturing module guide](/blog/odoo-erp-australia-6/odoo-manufacturing-module-the-australian-guide-to-mrp-work-orders-and-shop-floor-95) goes deeper on what the MRP and work order functionality actually covers. Odoo is also open-source at its core, which means the platform can be customised at a code level if your business has genuinely non-standard requirements. That's different from most SaaS platforms, including Cin7 Core, where you're constrained to what the vendor has built. _"The businesses that come to us from Cin7 Core are usually managing three or four systems and spending real time each week reconciling them. The question isn't whether Odoo is cheaper than Cin7 Core on its own. It's whether Odoo replaces Cin7 Core plus Xero plus whatever they're using for CRM. Once you add up all those subscriptions and the time spent keeping them aligned, the comparison looks different."_ **Bill Alvarez, Practice Manager, Auboros** ## **Pricing: what each actually costs to run** Cin7 Core's published pricing has three main tiers: Standard at $349 per month (up to 5 users), Pro at $599 per month (up to 10 users, which is the most commonly recommended tier for growing businesses), and Advanced at $999 per month (up to 15 users). These figures are from their published pricing, but costs have historically increased, so verify current pricing before committing. Cin7 Omni, the enterprise product, uses custom pricing. Odoo pricing depends on which modules you need and how many users. Enterprise licensing is per user per month, with different rates depending on the module set. The total cost for an Odoo implementation also includes the implementation project itself, which for a mid-sized business with inventory, accounting, and CRM requirements typically runs from a few weeks to a few months depending on complexity. Auboros publishes our Odoo implementation packages at [auboros.com/odoo-implementation-packages](/odoo-implementation-packages-for-australian-businesses), which gives a clearer picture of what a scoped project actually costs. The honest comparison: Cin7 Core is cheaper to start with and faster to get running. Odoo has a higher implementation cost but typically replaces multiple subscription costs and can reduce manual reconciliation overhead. The break-even calculation depends on your transaction volume, team size, and how many systems you're currently paying for alongside Cin7. ## **Australian compliance: GST, BAS, and STP** Both platforms operate in Australia and handle Australian tax requirements, but the scope is different given their different purposes. Cin7 Core tracks GST on transactions at an inventory and order level. Your actual [Business Activity Statement (BAS)](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas) preparation and lodgement happens in Xero or your accounting platform. If the data flowing between Cin7 Core and Xero is clean, this works. If there are mismatches, you're troubleshooting across two systems before your BAS due date. Odoo's Australian localisation handles GST natively within the accounting module. Tax codes, BAS report generation, and GST reconciliation are all within the one platform. Odoo also includes [STP Phase 2](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll/expanding-single-touch-payroll-phase-2) payroll for businesses that want to run payroll inside their ERP rather than in a separate tool. Our post on [Odoo's Australian localisation](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98) covers how BAS, GST, and STP work together in the one platform. For businesses that are ATO-compliant now through a Cin7 Core and Xero combination, the compliance argument alone isn't sufficient reason to switch. But if you're already considering adding payroll or consolidating systems, having BAS, STP, and GST all in one platform is a meaningful simplification. ## **Who should stay with Cin7 Core** Cin7 Core is a reasonable choice for a business that sells physical products, uses Xero for accounting, doesn't need CRM or manufacturing depth, and isn't planning to add those requirements in the near future. If your operation is genuinely straightforward and the Cin7 Core and Xero combination is working without significant reconciliation overhead, the disruption of switching platforms is probably not worth it. Cin7 Core also has a larger ecosystem of off-the-shelf integrations with ecommerce platforms and marketplaces than Odoo has natively. If your business runs primarily through Shopify or Amazon with a high volume of channel integrations already configured, that's a real consideration. Odoo has ecommerce and integration capabilities, but they require configuration rather than plug-and-play setup. The switch to Odoo makes most sense when one or more of these conditions applies: you're currently managing three or more separate systems that should share data, you need manufacturing depth beyond basic assembly, you're growing a sales team that needs CRM inside the same platform as inventory, or your Cin7 Core and Xero reconciliation is creating regular manual work. Our [Odoo implementation guide for Australian businesses](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) covers the full evaluation process if you're working through whether a switch makes sense. ## **Frequently asked questions** ### **Can Odoo replace Cin7 Core and Xero together?** Yes, for most businesses this is exactly what an Odoo implementation achieves. Odoo includes native inventory management, purchasing, sales order management, and a full double-entry accounting module with Australian GST and BAS support. The transition involves migrating your product catalogue, customer and supplier records, and opening balances, and configuring Odoo to match your workflows. The implementation timeline varies by complexity, but replacing a Cin7 Core and Xero combination with Odoo is a common migration path. ### **Is Cin7 Core cheaper than Odoo?** Cin7 Core has lower upfront cost and lower implementation overhead for a simple use case. Odoo has higher implementation costs but typically replaces multiple subscriptions. The real comparison is Cin7 Core plus Xero plus any CRM or other tools you're currently running, versus the total cost of Odoo. For businesses with 10 or more users across several systems, the Odoo total cost is often comparable or lower over a three-year horizon. ### **Does Odoo handle lot tracking and serial numbers for compliance?** Yes. Odoo supports lot and serial number tracking across the full supply chain: from purchase receipt through warehouse storage to customer delivery. This covers the traceability requirements for product recall scenarios in food, medical devices, electronics, and similar regulated categories. The tracking is native to the inventory module and doesn't require a separate add-on. ### **What are the main complaints about Cin7 Core?** The most common issues reported by Cin7 Core users on review platforms relate to customer support response quality, pricing increases since initial signup, and limitations when businesses grow into more complex workflows. The lack of native accounting is a consistent operational friction point for businesses that need tighter integration between inventory and financials. These are not unique to Cin7 Core but they're worth understanding before committing. ### **How long does migrating from Cin7 Core to Odoo take?** For a straightforward product business migrating inventory, purchasing, and accounting from Cin7 Core and Xero to Odoo, a typical implementation runs 6 to 12 weeks depending on data complexity, the number of integrations, and how much customisation is required. Businesses with manufacturing requirements or large product catalogues with complex pricing rules take longer. A scoping conversation with an Odoo partner is the right way to get an accurate estimate for your specific situation. * * * **Evaluating Odoo as an alternative to Cin7 Core?** Auboros [implements Odoo for Australian businesses](/solutions/odoo) across Queensland, NSW, and Victoria. We can scope a migration from Cin7 Core and Xero, or run a more open-ended evaluation of whether Odoo fits what you're trying to build. Our [Cin7 alternatives guide](/compare/cin7-alternative-australia) covers the wider decision, including when staying on Cin7 is the right call. If you'd like a direct conversation about your situation, [**book a free consultation**](/appointment). We'll tell you what we think, including if Cin7 Core is the right call. --- # Odoo Xero Integration Australia: How to Connect Them and What Actually Syncs - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-xero-integration-australia-how-to-connect-them-and-what-actually-syncs-124 - Category: Odoo ERP Australia - Published: 2026-04-28 - Description: How to connect Odoo and Xero in Australia. What syncs, what doesn't, and when running both together is worth the reconciliation overhead. Brisbane partner. You're running Xero. You're moving to Odoo, or you've decided to add it for operations while keeping Xero for the books. Either way, the question is the same: how do you actually connect the two, and what should you expect once they're talking? This is the practical version. Connectors, sync directions, what cleanly transfers, and where the integration breaks down once you push real Australian data through it (GST, BAS, payment reconciliation). If you're still deciding whether to integrate at all or replace Xero with Odoo's accounting module, our [running Odoo and Xero together guide](/blog/odoo-erp-australia-6/odoo-xero-run-together-australia-101) covers that strategic decision first. ## **What an Odoo Xero integration actually does** An integration moves data between Odoo and Xero so you don't have to enter it twice. The most common flow is one-way: Odoo creates the invoice (because that's where your sales orders, projects, or service jobs live) and pushes it to Xero, where payments are reconciled against the bank feed. Customer master data, products, and tax codes can also sync, depending on the connector. Some connectors offer two-way sync. In practice, that's where things get fragile. Two systems editing the same record at the same time creates conflicts. Most Australian businesses we work with end up running a one-way push from Odoo to Xero and treating Xero as a read-only ledger for the accountant. ## **Built-in connectors vs third-party apps** Odoo doesn't ship with a native Xero module. Every Xero connector is third-party, available via the [Odoo Apps Store](https://apps.odoo.com/apps). The popular ones for v17, v18, and v19 are: - **Pragmatic Xero Connector:** OAuth 2.0, bi-directional sync of invoices, bills, payments, contacts, and products. Most actively maintained. - **SH Xero Connector:** Multi-entity support. Useful if you've got more than one Xero file. - **BI Xero Connector:** Lighter-weight, focused on financial data and contacts. - **MoonSun connector\_xero:** Part of a broader integration toolbox, finance-data oriented. You can also build a custom integration against the Xero API if your data flow is unusual or you need real-time syncing instead of scheduled batches. We've done a few of these for clients with multi-entity, multi-currency setups where off-the-shelf connectors couldn't keep up. Custom development costs more up front but you own the code and the logic. ### **What about Zapier or Make?** Both work for low-volume, simple flows: push a new Odoo customer to Xero, or send a Xero contact to Odoo. They fall over once you need invoice line items, tax codes, or payment matching. For anything beyond a handful of records a day, use a proper Odoo Apps Store connector or a custom build. ## **What syncs cleanly, and what doesn't** The general rule: simple records sync well. Anything with conditional logic or compliance dependencies doesn't. **Syncs cleanly:** - **Customer and supplier contacts:** Names, addresses, ABNs, default tax codes. - **Products and services:** Code, description, price. - **Sales invoices:** Header and line items, with the right tax codes mapped between systems. - **Vendor bills:** Same shape as invoices, going the other way. - **Payment status:** Once a payment is recorded in Xero against a bank feed, the connector can mark the Odoo invoice as paid. **Doesn't sync cleanly:** - **Inventory levels:** Xero doesn't really do inventory the way Odoo does. Stock counts, costing layers, and warehouse transfers stay in Odoo. - **Manufacturing and production orders:** Stay in Odoo entirely. - **Bank reconciliation:** Stays in Xero. Don't try to mirror it in Odoo. - **Payroll and STP:** Stays in Xero or wherever you currently run payroll. The Single Touch Payroll (STP) reporting obligation doesn't move with the integration. - **BAS preparation:** Whichever system holds the GST source data is where you should run BAS. Don't try to consolidate from both. ## **The GST and BAS angle that breaks most setups** Australian tax codes have to map exactly between Odoo and Xero or your invoices come through with the wrong GST treatment. Xero uses tax rates like "GST on Income," "GST on Expenses," "GST Free Income," and "BAS Excluded." Odoo's Australian fiscal localisation has its own equivalents (covered in our [Australian localisation guide](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98)). If you skip the tax code mapping during setup, you'll see invoices in Xero with no GST applied, or with the wrong rate. The fix is usually a one-time configuration in the connector settings, but it has to be done deliberately. The [Odoo v19 Australia localisation docs](https://www.odoo.com/documentation/19.0/applications/finance/fiscal_localizations/australia.html) list the standard tax codes shipped with the AU package, which gives you the mapping target. For [Business Activity Statement (BAS) preparation](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas), decide upfront which system is the source of truth. If you're keeping Xero for accounting and Odoo for operations, BAS comes from Xero and Odoo just feeds it. If you're moving to Odoo's accounting module, BAS comes from Odoo and Xero gets retired. Trying to reconcile BAS from both systems creates more problems than it solves. ## **When integration makes sense, and when it doesn't** Integration is worth it if you're in transition (12 to 18 months on Xero while Odoo gets fully implemented), or if you've made a deliberate decision to keep Xero for the accounting layer because your accountant works in it and you don't want to retrain them. Integration is not worth it if your goal is "use both forever." Two systems holding the same financial data will drift, even with sync. Reconciliation differences between Odoo and Xero are a regular topic with the clients we support, and the support cost compounds each year. _"Most of the businesses we help with Odoo and Xero integrations end up consolidating onto Odoo within a year. The integration buys time during cutover. After that, the reconciliation overhead starts costing more than the comfort of keeping the old system."_ **Josh Craig, Director, Auboros** ## **How to set up the integration (the high-level version)** 1. **Pick a connector.** If your data is straightforward, start with Pragmatic. If you're multi-entity, look at SH Xero Connector. If your needs are unusual, scope a custom build. 2. **Map your chart of accounts.** Odoo's chart of accounts has to match the Xero accounts you're posting to. Document the mapping before you turn the sync on. 3. **Map tax codes.** Every GST treatment in Xero needs an Odoo equivalent. Test with a single invoice before going live. 4. **Set sync direction.** One-way Odoo to Xero is the cleanest default. Only enable two-way if you have a specific reason and a plan for conflict handling. 5. **Run a parallel period.** Process a week of real invoices through both systems and reconcile. You'll find the edge cases here, not in testing. 6. **Decide on payment matching.** Will Xero's bank feed update Odoo's invoice status, or will you manage payments separately? Pick one. Plan on 2 to 4 weeks for setup if you're using an off-the-shelf connector and a tidy data set. Longer if you've got historical messes to clean up first. Our [Odoo implementation guide for Australia](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) covers the broader rollout context. ## **Frequently asked questions** ### **Does Odoo have a native Xero integration?** No. There's no Xero module shipped by Odoo. Every connector available is third-party via the Odoo Apps Store, or a custom build against Xero's API. We use OAuth 2.0 connectors for most Australian implementations. ### **Can Odoo and Xero do bidirectional sync?** Some connectors support it for contacts, products, and invoices. We usually recommend one-way (Odoo to Xero) because two-way creates conflicts whenever both systems edit the same record. The exception is multi-entity setups where the rules are clearer. ### **Will the integration handle my BAS reporting?** The integration moves invoice and bill data between systems. BAS reporting still comes out of whichever system you've designated as the source of truth. If Xero holds your accounting, BAS comes from Xero. If you've moved to Odoo's accounting module, BAS comes from Odoo, and Xero gets decommissioned. ### **How long does an Odoo Xero integration take to set up?** Two to four weeks for a clean dataset using a stable Odoo Apps Store connector. Add time if your chart of accounts needs cleanup, you have multiple Xero entities, or you're integrating during a wider Odoo rollout. ### **Is the integration worth keeping long-term?** For most Australian businesses, no. Running two financial systems indefinitely creates reconciliation work that compounds every month. The integration is best used as a transition tool while Odoo's accounting module gets configured, then retire Xero once you're confident in the new setup. * * * **Need help connecting Odoo and Xero, or moving off Xero entirely?** We're a [Brisbane-based Odoo Silver Partner](/solutions/odoo), and we've set up dozens of Odoo Xero integrations across Queensland, NSW, and Victoria. Our [Odoo integration services](/solutions/odoo-integrations) cover Xero, ecommerce, banking and WMS connections. We can scope a connector setup, build a custom integration, or help you transition fully to Odoo's accounting module without losing your historical data. If you want to talk through what makes sense for your business, [**book a free consultation**](/appointment). We'll look at your current Xero setup and tell you honestly whether integration or full migration is the better path. --- # MYOB Advanced vs MYOB Acumatica: What the 2024 Rebrand Means for Australian Businesses - Canonical URL: https://www.auboros.com/blog/insights-5/myob-advanced-vs-myob-acumatica-what-the-2024-rebrand-means-for-australian-businesses-125 - Category: Insights - Published: 2026-04-28 - Description: MYOB Advanced vs MYOB Acumatica: 2024 Rebrand Explained If you've searched for MYOB Advanced lately and ended up on a page about MYOB Acumatica, you're not lost. The product was renamed in 2024. The platform is the same, the data is the same, the partners are the same. The brand on the box changed. This is the short version of what actually happened, what you need to know if you're already a customer, and what it means if you're evaluating Australian mid-market ERP options in 2026 and seeing both names in the same comparison. ## **What changed when MYOB Advanced became MYOB Acumatica** On 16 July 2024, MYOB officially renamed MYOB Advanced Business to MYOB Acumatica. The rebrand was announced jointly by MYOB and Acumatica, the global cloud ERP company that has powered MYOB Advanced under the hood for over a decade. The [Acumatica press release](https://www.acumatica.com/corporate-newsroom/press-releases/acumatica-expands-partnership-with-myob/) framed it as an expanded partnership rather than a new product. The platform itself didn't change at the launch. The cloud infrastructure, the modules (financials, distribution, manufacturing, projects, payroll), the user interface, and the Australian and New Zealand localisations carried straight across. [MYOB's own announcement](https://www.myob.com/au/blog/myob-advanced-business-is-now-myob-acumatica/) confirmed it was a name change, not a software replacement. ### **Why MYOB rebranded the product** Two reasons, both of them strategic rather than technical. First, Acumatica is a globally known ERP platform, and aligning the brand makes the product easier to sell internationally and easier to find when buyers research mid-market ERPs. Second, the closer alignment lets MYOB ship Acumatica's twice-yearly global feature releases into the ANZ product more directly, instead of repackaging them under a separate brand. For Australian and New Zealand customers specifically, MYOB remains the exclusive partner of Acumatica in the region. That hasn't changed since the rebrand and isn't expected to. ## **What it means if you're already on MYOB Advanced** Practically nothing changes for you. Your subscription, your data, your customisations, your payroll module, and your support contract carry across to MYOB Acumatica without any migration. There's no upgrade you need to run. No data move. No reconfiguration. What you'll see over time is updated branding in the login screen, in invoices, in MYOB's documentation, and in renewal paperwork. You may also see your support team and partner refer to the product by its new name. If you've got internal training materials or process documents that still say "MYOB Advanced," they're not wrong, just out of date. Update them when convenient. The version release cadence continues twice a year. The 2026 release added a material availability view on production orders, AI-assisted features for anomaly detection, automated bank transaction matching, and Distribution Requirements Planning. Customers on the platform get those updates as part of the standard subscription, per [the MYOB Acumatica product page](https://www.myob.com/au/erp-software/products/myob-acumatica). ## **What it means if you're evaluating ERPs in Australia** If you're comparing options in 2026 and you see "MYOB Advanced" mentioned in a vendor list, an old review, or a comparison article, treat it as MYOB Acumatica. They are the same product, just with content written before or after the July 2024 rebrand. The same applies to capability claims. If a 2023 article praises MYOB Advanced's project accounting or warehouse management, that capability is still there in MYOB Acumatica. If a 2025 article talks about MYOB Acumatica's Distribution Edition, that's the current name for the same edition that used to be called MYOB Advanced Distribution. One thing worth checking when you read older content: pricing. MYOB Acumatica uses named user licensing with tiered access levels (full access, sales, read-only, executive, API). If you see a 2023 pricing article describing the platform as "consumption-based" or "per-seat" without that nuance, treat it as out of date and get a current quote from a partner. Pricing for the ANZ product is set by MYOB and quoted by partners on a scoped basis, not published as a flat rate. _"We still get prospects searching for 'MYOB Advanced' two years after the rebrand. The product is the same, but the search results are split. If you're evaluating, look at the platform itself rather than the brand history."_ **Josh Craig, Director, Auboros** ## **MYOB Acumatica editions in 2026** The product is sold in editions, each with industry-specific features layered on the core financial and distribution platform. The current line-up is: - **Standard:** Core financials, project accounting, CRM, and reporting. The base for most professional services and not-for-profit deployments. - **Distribution:** Adds inventory, sales orders, purchase orders, and warehouse management. Used by wholesalers, importers, and distributors. - **Manufacturing:** Adds production orders, bills of material, work orders, material requirements planning, and shop floor control. For discrete and process manufacturers. - **Construction:** Adds project costing, retentions, progress claims, and the workflow features needed for site-based work. Used by builders and trades, including those subject to QBCC trust account obligations. You can also get the platform through the FastStart Wholesale Distribution program, which Auboros runs in Queensland for businesses that want a fixed-scope, 12-week implementation. Our [FastStart guide](/blog/myob-acumatica-australia-7/myob-acumatica-wholesale-distribution-faststart-australia-103) covers what's included and who it's a fit for. ## **Frequently asked questions** ### **Are MYOB Advanced and MYOB Acumatica the same product?** Yes. MYOB renamed MYOB Advanced Business to MYOB Acumatica on 16 July 2024. The platform, modules, data, and Australian and New Zealand localisations are identical. Existing customers transitioned automatically with no software change. ### **Do I need to upgrade or migrate to MYOB Acumatica?** No. If you were on MYOB Advanced, your subscription continues as MYOB Acumatica without any data migration or system upgrade. The version release cadence (twice yearly) is unchanged. You'll see the new branding in the interface and in renewal documentation over time. ### **Why did MYOB rename the product?** To align the Australian and New Zealand product with the global Acumatica brand. Acumatica is the underlying ERP platform that has powered MYOB Advanced for over a decade. The rebrand makes the product easier to recognise internationally and lets MYOB ship Acumatica's global feature releases into ANZ more directly. ### **Is MYOB still the only Acumatica provider in Australia?** Yes. MYOB remains the exclusive partner of Acumatica for Australia and New Zealand. The rebrand reinforced rather than diluted that arrangement. You can't buy Acumatica directly from Acumatica in this market. You buy MYOB Acumatica through MYOB or an authorised partner. ### **How do I tell if a comparison article is about MYOB Advanced or MYOB Acumatica?** Check the date. Anything published before mid-July 2024 will refer to MYOB Advanced. Anything published after generally uses MYOB Acumatica. The product capabilities are the same in both cases, but pricing structures, edition names, and feature releases have evolved since the rebrand. Always verify current pricing and feature scope with a partner before deciding. * * * **Comparing MYOB Acumatica to your current accounting or ERP system?** We're an Official MYOB Acumatica Partner based in Brisbane, supporting mid-market businesses across Queensland, NSW, and Victoria. We can walk you through what the platform does today, where it fits, and where it doesn't, without the marketing spin. If you're evaluating MYOB Acumatica or trying to work out if you've outgrown [AccountRight](/blog/myob-acumatica-australia-7/myob-acumatica-vs-accountright-australia-117) or another mid-market system, [**book a free consultation**](/appointment). We'll give you a clear read on whether it's the right fit and what an implementation would look like. --- # MYOB Acumatica Partner Australia: What They Do, How to Engage, and How to Pick One - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-partner-australia-what-they-do-how-to-engage-and-how-to-pick-one-127 - Category: MYOB Acumatica Australia - Published: 2026-04-28 - Description: What an MYOB Acumatica partner does in Australia, how the engagement process works, what to expect, and how to pick one that fits your business and industry. If you're evaluating MYOB Acumatica, you've probably noticed you can't just buy it directly from MYOB. The platform is sold and delivered through partners. That's not unusual for mid-market ERPs, but it does change how the buying process works compared to picking up Xero or QuickBooks online. This is what a partner actually does in the Australian MYOB Acumatica ecosystem, how the engagement process runs, and how to tell which partner is the right fit. If you want the deeper evaluation framework, the questions to ask in the room and the references to check, our [guide on what to look for in MYOB Acumatica consulting](/blog/myob-acumatica-australia-7/myob-acumatica-consulting-what-to-look-for-99) covers that side. This post is about how the relationship works in the first place. ## **What an MYOB Acumatica partner actually does** A partner is the company that scopes, sells, configures, and ongoing-supports [MYOB Acumatica](https://www.myob.com/au/erp-software/products/myob-acumatica) for you. Some are pure resellers (they sell the licenses, you do everything else). Most do implementation work as well, including discovery, configuration, customisation, data migration, training, and post go-live support. A handful specialise in industry-specific deliveries like the FastStart Wholesale Distribution program. The work splits across the lifecycle: - **Pre-sale:** Demos, discovery, scoping, quoting. You're effectively shopping a partner more than you're shopping software at this stage. Two partners selling the same MYOB Acumatica platform will scope and price the same project differently. - **Implementation:** Configuration of modules (financials, distribution, manufacturing, projects), Australian localisation (GST, BAS, payroll if applicable), data migration, integrations to anything else you run, training, and cutover. - **Customisation and development:** If your business has workflows the standard configuration doesn't cover, partners build extensions on Acumatica's xRP platform. Reports, business events, custom inquiries, and occasionally full custom modules. - **Post go-live support:** Bug fixes, minor enhancements, user support, version upgrades. Most businesses need a support agreement with their implementation partner long-term, not just for the project. Licenses themselves come through MYOB. Partners arrange the subscription on your behalf, but you're paying MYOB for the platform and paying the partner for the work around it. ## **Why MYOB sells through partners (not directly)** Mid-market ERP isn't an off-the-shelf purchase. The platform has to be configured to match how your specific business runs, integrated with whatever else you've got, populated with your data, and adopted by your team. None of that scales as a product transaction; it needs people who understand both the software and your business. MYOB also lets partners specialise. Some focus on construction (with QBCC trust account experience), some on wholesale distribution (the FastStart program), some on professional services or not-for-profits. The partner network is wider than MYOB's internal delivery team would be, and partners bring depth in their chosen verticals that a generalist team couldn't match. For Australia and New Zealand specifically, MYOB is the [exclusive partner of Acumatica in the region](https://www.acumatica.com/corporate-newsroom/press-releases/acumatica-expands-partnership-with-myob/). You can't buy Acumatica directly from Acumatica here. Everything goes through MYOB or an authorised partner. Our [post on the 2024 rebrand from MYOB Advanced to MYOB Acumatica](/blog/myob-acumatica-australia-7/myob-advanced-vs-myob-acumatica-rebrand) covers how that relationship is structured. ## **How to engage with a partner: the standard process** Most partner engagements follow the same shape. Knowing it ahead of time means you can move through it faster. ### **Initial scoping conversation** The first call is usually 30 to 60 minutes. The partner asks about your business, your current systems, what you're trying to fix, and what your timeline looks like. You're judging whether they understand mid-market operations and whether they're listening or pitching. A good partner is asking more questions than they're answering on this call. Out of this comes either a more formal discovery proposal or a no-fit decision (the partner saying "this isn't our space" is a positive signal, not a negative one). ### **Solution design and quote** If both sides want to keep going, the next phase is paid or unpaid discovery. Some partners do half-day or one-day workshops at no cost; some do paid two-week scoping engagements. Either way, the deliverable is a solution document that lists what modules you need, what configuration is required, what customisation is in scope, what data migration looks like, what integrations are needed, and what the timeline and budget will be. Read the solution document carefully. The level of detail tells you how the partner will manage your project. Vague scoping documents lead to vague projects. ### **Contracting and project kickoff** If the solution document and quote work, you sign a statement of work and the partner signs an MYOB license arrangement on your behalf. Project kickoff typically follows two to four weeks later, depending on partner availability and your team's readiness. From kickoff, the project runs in phases (discovery, configuration, UAT, cutover, hypercare) that look similar across most partners. The differences are in pace, in transparency, and in how the partner handles change requests. Those become apparent inside the first month. ## **Common engagement models** The standard models you'll encounter in the Australian MYOB Acumatica market are: - **Fixed-scope industry programs:** The clearest example is FastStart Wholesale Distribution, a 12-week fixed-scope, fixed-fee program for wholesale distributors. Auboros runs this in Queensland. The [FastStart program guide](/blog/myob-acumatica-australia-7/myob-acumatica-wholesale-distribution-faststart-australia-103) covers what's included. - **Custom implementation projects:** The default for most mid-market deployments. Scope is defined per business, fee is project-quoted, timeline is typically three to nine months depending on complexity. - **Phased rollouts:** Some businesses implement in stages, starting with financials and distribution, then adding manufacturing or projects later. Partners can run this as a single contract with phase deliverables, or as a series of smaller engagements. - **Support and managed service agreements:** Post go-live, most businesses move to an ongoing arrangement with their implementation partner. Models range from incident-only ticket support to full managed service of the Acumatica environment. Choose the engagement model that matches your situation. If your business is a textbook wholesale distributor with standard processes, a FastStart program is faster and cheaper than custom. If your business has unusual operations, custom is worth the extra time. _"The partner you pick for implementation is usually the partner you'll be working with for the next decade. The relationship matters more than the lowest quote. We'd rather lose a deal at scoping than win one we can't deliver well."_ **Bill Alvarez, Practice Manager, Auboros** ## **How to pick the right partner for your business** The factors that actually matter, in rough priority order: - **Industry fit:** Have they done implementations in your industry before? Construction, wholesale distribution, manufacturing, professional services, and not-for-profits all have specific configuration patterns. A partner who's done five wholesale distribution rollouts will scope yours faster and more accurately than a generalist. - **References from similar customers:** Ask for two or three customer references from businesses similar to yours in size and industry. Call them. Ask what went well, what didn't, what they wish they'd known. - **Australian localisation depth:** The partner needs to understand GST, Business Activity Statement (BAS) reporting, Single Touch Payroll if you're using payroll, and Australian banking. This is non-negotiable for any AU implementation. The [ATO BAS guidance](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas) sets the compliance baseline they need to configure to. - **Geographic match:** Some clients prefer a partner who can be on-site for kickoff and go-live. Others are fully comfortable remote. Sort this preference up front. - **Team continuity:** Will the people you meet in the sales process actually deliver the project, or does it hand off to a different team after the contract signs? This is a fair question to ask directly. - **Pricing transparency:** Whether the partner publishes pricing or quotes per project, the conversation about cost should be specific and grounded. Vague pricing usually correlates with vague delivery. For the deeper evaluation criteria, including the technical certifications, the question framework, and the red flags, our [consulting evaluation guide](/blog/myob-acumatica-australia-7/myob-acumatica-consulting-what-to-look-for-99) goes into the detail. This post covers the engagement shape; that one covers the qualification framework. ## **What changes when you go through a partner vs MYOB directly** Practically, almost everything customer-facing comes through the partner. They're your primary contact for implementation, support, customisation, and most license administration. MYOB itself stays in the background as the platform vendor. Where MYOB shows up directly: license renewals (issued by MYOB, often invoiced through the partner), platform-level updates and security patches (handled by MYOB's hosting infrastructure), and product roadmap announcements (twice-yearly Acumatica releases shipped through MYOB's ANZ channel). If a partner relationship breaks down (rare but it happens), you can move to a different partner without changing platforms. Your data and configuration stay with the MYOB Acumatica subscription; what transfers is the support, customisation, and ongoing project work. ## **Frequently asked questions** ### **What does an MYOB Acumatica partner actually do?** A partner scopes, sells, implements, and supports MYOB Acumatica on your behalf. That covers discovery and quoting, configuration of the modules you've licensed, Australian localisation, data migration, integrations, training, and post go-live support. The partner is your primary point of contact across the lifecycle. ### **Can I buy MYOB Acumatica directly from MYOB?** In Australia, almost always through a partner. MYOB has a partner-led delivery model for the platform because mid-market ERP requires configuration and customisation that don't fit a self-service purchase. Some smaller, more standardised packages may be sold by MYOB directly, but the implementation work goes through partners. ### **How do I become an MYOB Acumatica partner?** You apply to MYOB for partner authorisation. Partners typically have qualified consultants, demonstrated implementation experience, and a defined service model. The authorisation level (e.g., reseller, implementation partner, FastStart-certified) depends on the firm's track record and certification investment. This post is about working with partners, not about becoming one. If you're researching the partner application route, contact MYOB directly. ### **How many MYOB Acumatica partners are there in Australia?** The current partner network includes several dozen firms across Australia and New Zealand, with concentrations in Sydney, Melbourne, Brisbane, and Auckland. Some specialise by industry (construction, distribution, manufacturing, services), some by region. MYOB publishes the current partner list on their website. ### **What if I want to change MYOB Acumatica partners?** You can move to a different partner without changing platforms or losing data. The MYOB Acumatica subscription stays with you. What transfers is the implementation, support, and customisation relationship. The transition usually takes one to two months as the new partner gets up to speed on your environment. * * * **Looking for an MYOB Acumatica partner in Australia?** We're an Official MYOB Acumatica Partner based in Brisbane, supporting mid-market businesses across Queensland, NSW, and Victoria. We run the QLD FastStart Wholesale Distribution program and deliver custom implementations across financials, distribution, manufacturing, and project accounting. Our [MYOB Acumatica services page](/solutions/myob) covers what we do. If you're scoping an MYOB Acumatica implementation or evaluating partner options, [**book a free consultation**](/appointment). We'll work through your requirements and tell you straight whether we're the right fit, or if a different partner would serve you better. --- # MYOB Acumatica Project Accounting for Australian Businesses - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-project-accounting-australia-123 - Category: MYOB Acumatica Australia - Published: 2026-04-28 - Description: How MYOB Acumatica project accounting handles budgets, WIP, billing, and revenue recognition for Australian services, construction, and NFP businesses. If your business makes its money by delivering projects, your accounting software has to answer one question cleanly: are we making money on this job? Businesses running Xero or AccountRight alone usually can't. They can tell you what was invoiced and what was paid, but not what it cost to deliver, what's sitting in work-in-progress, or whether the budget is on track. MYOB Acumatica's project accounting module is designed for this. It treats projects as a first-class accounting object, with their own budgets, billings, costs, and revenue recognition rules, all tying back into the general ledger. For Australian services firms, builders, engineering consultancies, and not-for-profits running grants, it's the functional reason to move off a small business accounting platform. ## **What MYOB Acumatica project accounting actually tracks** The [MYOB Acumatica product](https://www.myob.com/au/erp-software/products/myob-acumatica) includes a project accounting module that sits alongside financials, distribution, and payroll. Each project carries a structured record of: - **Budget:** Planned hours, materials, subcontractor costs, and revenue across phases, tasks, and cost codes. - **Actuals:** Real hours logged through timesheets, expenses, purchased items, subcontractor bills, and inventory issues. Everything that touches the job posts against its budget line. - **Billings:** Invoices raised against the project, including fixed-fee, time and materials, milestone, and progress billing methods. - **WIP:** Work delivered but not yet invoiced, carried as an asset until billing catches up. - **Revenue recognition:** How and when revenue hits the P&L, independent of when it's invoiced or paid. The point is that one record, the project, links timesheets, supplier bills, customer invoices, and stock movements. You don't need to reconcile five systems to find out what happened on a job. ## **Budget structure: phases, tasks, and cost codes** Project budgets in MYOB Acumatica are built as a three-level structure. A project has phases (for example, design, construction, commissioning). Each phase breaks into tasks. Each task carries budgeted cost and revenue by cost code. Cost codes are the chart of accounts for the project. Common codes include labour, materials, subcontractors, equipment, and overhead. Every time an expense hits the job, it codes to both the project and the cost code. Reporting by cost code tells you where the budget is bleeding, and the phase structure lets you compare current phase performance against earlier ones. For smaller engagements, you can run projects with a flat budget at the task level, no phases. The point is the module flexes between simple professional services engagements and complex multi-phase construction jobs. We covered where Acumatica fits for [professional services firms](/blog/myob-acumatica-australia-7/myob-acumatica-for-professional-services-firms-in-australia-88) in an earlier post. ## **Billing methods: matching how Australian businesses actually invoice** The billing model is where project accounting earns its keep. MYOB Acumatica supports the full range of methods Australian services and construction businesses use: - **Fixed fee:** Single invoice on completion, or split across milestones. Revenue recognition can be tied to percentage of completion independent of the billing schedule. - **Time and materials:** Bills based on logged timesheets and incurred expenses, using billing rates that can vary by role, project, or client. - **Milestone billing:** Invoices raised when pre-defined project milestones are met. Common in construction and major consulting engagements. - **Progress billing:** Invoices based on percentage of work complete, measured against budget. Typical for construction contracts. - **Cost-plus:** Bills at cost plus a margin, useful for government contracts and some construction arrangements. - **Retention:** A percentage held back until defect liability period ends, with automatic release on schedule. Critical for construction work. GST is calculated correctly on each billing type using the Australian tax codes in MYOB Acumatica. For [BAS preparation](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas), project billings flow into G1 (total sales) and 1A (GST on sales) automatically. ## **Revenue recognition: keeping GAAP and the ATO both happy** _"Revenue recognition is where most businesses discover that their old accounting system was lying to them. You invoice a fixed-fee project in full at kickoff, the P&L looks great, then six months of delivery cost turns up and the job is actually underwater. Acumatica splits billing from revenue recognition, which is what you need if you want to manage a services business on real numbers."_ **Bill Alvarez, Practice Manager, Auboros** MYOB Acumatica separates what's billed from what's recognised as revenue. For a fixed-fee project billed upfront, you can configure the module to recognise revenue using percentage of completion. The P&L then matches earned revenue to actual costs incurred, rather than booking 100% of revenue in month one. Available methods include: - **Completed contract:** Revenue recognised when the project is fully delivered. - **Percentage of completion:** Revenue recognised as costs are incurred against the budget. - **Milestone:** Revenue recognised as contractual milestones are hit. - **Straight-line:** Revenue spread evenly across the project duration. - **As invoiced:** Revenue recognised when billing goes out (the simpler model). For businesses preparing financial statements to Australian accounting standards, this separation between billings and revenue is how you produce reports that actually reflect performance. ## **Where project accounting fits across industries** ### **Professional services firms** Consulting, architecture, engineering, legal, and IT services businesses use project accounting to manage utilisation, WIP, and billing accuracy. Timesheet entry feeds directly into both cost tracking and invoicing, with different billing rates for different client contracts. Margin by client and project becomes visible rather than assumed. ### **Construction and trades** MYOB Acumatica also has a dedicated Construction edition that layers specific features on top of project accounting, including subcontractor compliance tracking and retention management. For Queensland builders, this ties in with [QBCC trust account requirements](/blog/myob-acumatica-australia-7/myob-acumatica-for-construction-in-queensland-job-costing-qbcc-compliance-and-what-s-included-105) on projects over $1 million. Our construction Queensland post covers that in detail. ### **Not-for-profits running grants** Grant acquittal is a project accounting problem by another name. Each grant is a project with a funder, a budget, restricted fund rules, and reporting requirements. MYOB Acumatica tracks restricted versus unrestricted costs, produces acquittal reports in the formats grantors expect, and supports multi-funder cost allocation. We covered this use case in our [MYOB Acumatica for not-for-profits](/blog/myob-acumatica-australia-7/myob-acumatica-not-for-profit-australia-109) guide. ### **R&D and innovation claims** Businesses claiming the R&D Tax Incentive need auditable records of eligible activities and spend. Project accounting with time tracking provides the evidence trail. Core activities, supporting activities, and ineligible work can be coded separately within a project structure. ## **What it takes to set up well** Project accounting is powerful, but the setup is where most implementations succeed or fail. The decisions that matter: - **Project templates:** Build templates for your common project types so new projects launch with the right budget structure, not a blank slate. - **Billing rate strategy:** Role-based, contract-based, or hybrid. Document which rate applies when, and test it with real data before go-live. - **Cost code standardisation:** Set cost codes once and apply them consistently. Changing them mid-year creates reconciliation headaches. - **Revenue recognition policy:** Work with your accountant or auditor to confirm the method that matches your contracts. Document it, and don't switch mid-project. - **Time capture workflow:** Timesheets are the input, and if the capture process is friction-heavy, the data quality collapses. Mobile entry, weekly approval workflows, and integration with project billing all need testing. Configuration like this is exactly what our [MYOB Acumatica implementation service](/blog/myob-acumatica-australia-7/choose-right-myob-acumatica-implementation-services-5) is built to cover. Getting project accounting set up right at kickoff saves a year of cleanup later. ## **Frequently asked questions** ### **Is project accounting included in MYOB Acumatica or an add-on?** Project accounting is a core module available within MYOB Acumatica editions. Licensing is based on named user access with tiered access levels, and the specific modules included depend on the edition. For specifics on what's included in a given edition, get a scoped quote through the [MYOB Acumatica implementation](/solutions/myob) process. ### **Can I run multiple projects for the same customer in MYOB Acumatica?** Yes. Customers can have unlimited projects, and each project carries its own budget, billing schedule, and revenue rules. Reports roll up by customer, by project, or both. ### **How does project accounting handle subcontractors?** Subcontractor bills can be coded directly to a project and cost code, and in the Construction edition, there's additional functionality for compliance certificates, payment schedules, and retention. For services businesses using subcontractors occasionally, the standard project accounting module handles it through AP bill entry. ### **Can I migrate project history from Xero or AccountRight?** Historical project data from Xero or AccountRight generally comes across as summary balances, not line-level detail, because those platforms don't structure projects the way MYOB Acumatica does. Open projects at the time of cutover can be rebuilt in MYOB Acumatica with opening budgets and actuals. Completed projects are usually kept in the old system for archive and referenced by number only. ### **Does project accounting support change orders?** Yes. Change orders are handled as revisions to the project budget and billing, with audit trail of what changed and when. For construction and major engineering projects, change orders are tracked against the original contract for variance reporting. * * * **Running your projects on spreadsheets alongside Xero or AccountRight?** For Australian businesses where project margin, WIP visibility, and billing accuracy affect cash flow, moving project accounting into a single ERP usually pays for itself inside two years. We scope MYOB Acumatica implementations for professional services firms, builders, engineering consultancies, and NFPs from our base in Brisbane. If you're weighing up whether project accounting in MYOB Acumatica fits your business, [**book a free consultation**](/appointment). A short call is usually enough to see whether it's the right move. --- # Odoo Purchasing Module Australia: Purchase Orders, RFQs, and What You Can Automate - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-purchasing-module-australia-purchase-orders-rfqs-and-what-you-can-automate-119 - Category: Odoo ERP Australia - Published: 2026-04-15 - Description: How Odoo's purchasing module handles purchase orders, RFQs, 3-way matching, and GST compliance for Australian businesses. What it does well and what to watch. Most Australian businesses running Odoo eventually consolidate their purchasing into the same system they use for everything else. That's the point. But the purchasing module is more involved than just raising purchase orders, and knowing what it actually does before you configure it saves a lot of backtracking later. This covers what the Odoo purchasing module does in practice, how it connects to inventory and accounts payable, the Australian compliance side (particularly GST and landed costs), and the situations where it works well versus where it needs careful setup. ## **What the Odoo purchasing module does for Australian businesses** The purchasing module sits at the intersection of procurement, inventory, and accounts payable. At its most basic, it lets you raise purchase orders, send them to vendors, and receive goods against them. At a fuller configuration, it handles requests for quotation (RFQs), multi-vendor comparison, blanket orders for recurring spend, 3-way matching between orders and invoices, and vendor performance reporting. In Odoo v18, the purchasing module is available in both Community and Enterprise editions, though Enterprise adds vendor pricelists, landed cost allocation, and procurement automation features that aren't included in Community. For Australian businesses with more than basic procurement needs, the Enterprise features are usually worth it. The module connects directly to Odoo's inventory and accounting modules. When goods are received against a purchase order, stock levels update without manual entry. When a vendor bill is matched to a PO and goods receipt, it flows through to accounts payable. For businesses that currently re-enter the same information across three different systems, this connection alone tends to be the biggest time saving. You can explore how this fits into a broader [Odoo implementation](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) if you're evaluating the platform more broadly. ## **Requests for quotation and blanket orders** An RFQ in Odoo is the starting point for most purchasing workflows. You create a draft purchase order, send it to one or more vendors by email, and convert the best response into a confirmed purchase order. Odoo can send a single RFQ to multiple vendors simultaneously and pull their responses into a comparison view, which is useful for straightforward multi-vendor comparisons without needing a separate procurement tool. For recurring spend where you've already negotiated supplier pricing, Odoo supports blanket orders. You lock in prices for a defined period and then release individual purchase orders against that agreement without re-negotiating each time. This works particularly well for businesses with consistent material requirements, such as manufacturers with regular raw material purchases or distributors with ongoing supplier contracts. The module also supports automated purchase order creation when stock falls below a minimum threshold. Reorder rules in Odoo's [inventory management module](/blog/odoo-erp-australia-6/odoo-inventory-management-australia-106) can trigger draft purchase orders automatically, which means your procurement team reviews and confirms rather than creating from scratch. For businesses that currently monitor stock levels manually and email suppliers when they get low, this removes a consistent overhead from the operations team. ## **3-way matching and why it matters for BAS** When a vendor invoice arrives, you need to confirm it matches what you ordered and what you actually received. Odoo's 3-way matching compares the vendor bill against the purchase order and the goods receipt. Discrepancies are flagged before you approve payment, which catches overcharges, short deliveries, and billing errors before they become accounting problems. For Australian businesses, this has a compliance dimension beyond just catching errors. The 10% GST you pay on supplier invoices becomes an input tax credit you claim on your Business Activity Statement (BAS). If you're claiming credits on invoices that don't correspond to delivered goods, or on invoices that aren't valid tax invoices, you have an ATO exposure. Odoo's matching workflow creates a clear audit trail connecting each credit to the original order and receipt. One practical point: you need a valid tax invoice (not just a receipt) to claim GST credits on purchases over $82.50 including GST. Odoo's vendor bill workflow captures the invoice reference and supplier details, which makes it easier to confirm you have the right documentation at BAS time. The ATO has [guidance on valid tax invoices](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas/bas-and-gst-tips) worth reviewing if your team processes high volumes of supplier invoices. ## **Landed costs and imported goods** For businesses that import products, the purchase price is only part of the true cost. Freight, insurance, customs duties, and port handling all affect your actual cost of goods. Odoo's landed cost feature lets you allocate these additional costs to specific product lines, adjusting inventory valuation to reflect what you actually paid to get goods into your warehouse. This matters for businesses using FIFO or average cost valuation, as incorrect landed costs distort margin calculations. For imported goods, the Australian Border Force charges 10% GST calculated on the customs value plus any applicable customs duty, and Odoo's purchasing and accounting integration captures this correctly when configured properly. ### **Vendor analytics and performance tracking** Beyond individual transactions, the purchasing module tracks vendor performance over time. You can see delivery times against committed lead times, order fill rates, and price variance against historical orders. This gives procurement teams verifiable data to review supplier performance, rather than relying on memory or searching through email threads for the last time something arrived late. Odoo v18 also includes some AI-assisted features relevant to procurement. If you're interested in how these fit into the broader platform, the [AI in Odoo Australia post](/blog/odoo-erp-australia-6/ai-in-odoo-australia-2026-102) covers what's actually useful versus what's still experimental. ## **When Odoo purchasing works well and when it doesn't** The purchasing module delivers the most value for businesses that have regular supplier relationships, process more than 20 to 30 purchase orders a month, or need to connect purchasing to inventory replenishment rules. If your procurement team is currently managing orders through email and entering supplier invoices manually, Odoo's workflow removes a consistent overhead. For very small businesses with occasional one-off purchasing, the module can feel like more process than value. You're creating vendor records, RFQs, and receipts for transactions that might have been quicker to handle directly in accounts payable. The payoff from Odoo purchasing scales with volume and supplier complexity. If you're already using Odoo for inventory and accounting, adding purchasing is a natural extension and the setup is straightforward. If you're evaluating Odoo specifically for procurement standalone, map your current procurement process against what Odoo supports before committing to an implementation. Our [Odoo services page](/solutions/odoo) has more on how we scope purchasing implementations for Australian businesses. _"The businesses that get the most from Odoo's purchasing module are usually the ones that were previously managing purchase orders through email threads and entering supplier invoices manually. Once that workflow is in Odoo, the time savings compound quickly because inventory, accounts payable, and GST reporting all update from the same process."_ **Bill Alvarez, Practice Manager, Auboros** ## **Frequently asked questions** ### **Does Odoo handle Australian GST on purchases?** Yes. Odoo v18 includes Australian tax configuration as part of the standard localisation. GST is applied at 10% on applicable purchase lines, and input tax credits are captured for BAS reconciliation. The Australian localisation covers both GST-inclusive and GST-exclusive pricing, which matches how most Australian suppliers invoice. ### **What is the difference between Odoo Community and Enterprise for purchasing?** Community includes core purchasing functionality: purchase orders, vendor management, goods receipts, and vendor bills. Enterprise adds vendor pricelists, landed cost allocation, automated purchase rules triggered by reorder points, and more detailed procurement analytics. For businesses importing goods or managing multiple supplier price structures, Enterprise is usually the right choice. ### **Can Odoo match purchase orders to vendor invoices automatically?** Odoo prompts you to create a vendor bill from a received purchase order and flags discrepancies between the billed amount and the PO. It highlights where quantities or prices differ, so the approver reviews the exception rather than checking every line manually. Full automated bill creation from structured supplier EDI feeds is possible with additional configuration. ### **How does Odoo purchasing connect to inventory management?** When goods are received against a purchase order, Odoo updates stock immediately. Reorder rules can also trigger purchase orders automatically when stock falls below a defined minimum, keeping procurement and inventory aligned without manual monitoring. This connection is one of the main reasons businesses move away from standalone purchasing tools once they're on Odoo for inventory. ### **How long does it take to configure Odoo purchasing for an Australian business?** A standard purchasing configuration for a business with existing vendor data and clear workflows typically takes 2 to 4 days of implementation time. More complex setups involving multi-currency orders, custom approval workflows, or extensive vendor pricelist management take longer. The timeline also depends on how much data migration is involved if you're moving from a previous system. * * * **Ready to move purchasing out of email and into your ERP?** Auboros implements Odoo for Australian businesses across Queensland, NSW, and Victoria. We handle purchasing module configuration as part of a broader Odoo implementation or as a standalone project. If you're evaluating whether Odoo purchasing fits your workflow, [**book a free consultation**](/appointment). No obligation, and we'll be direct about whether it's the right fit. --- # MYOB Acumatica EOFY Checklist 2026: What to Prepare Before 30 June - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-eofy-checklist-2026-what-to-prepare-before-30-june-120 - Category: MYOB Acumatica Australia - Published: 2026-04-15 - Description: MYOB Acumatica EOFY 2026 checklist for Australian businesses. STP finalisation, Payday Super prep, BAS Q4, period close, and what to do before 30 June. Two deadlines define EOFY for most Australian businesses: 30 June (end of the financial year) and 14 July (when STP finalisation is due to the ATO). For MYOB Acumatica users this year, there's a third: 1 July 2026, when Payday Super takes effect and changes how superannuation payments need to be processed going forward. This checklist covers the main tasks to work through before and after 30 June, with the MYOB Acumatica workflows and key compliance deadlines you need to know. Start the process in April or May rather than June if you can, particularly if your payroll configuration or inventory records need attention before the close. ## **Payroll and STP finalisation** Single Touch Payroll (STP) finalisation is the process of formally confirming your employees' year-to-date payroll data to the ATO. In MYOB Acumatica, this happens through the payroll module once your last pay run for the financial year is complete. The standard STP finalisation deadline is **14 July 2026**. This is the date by which the ATO expects all employers to have submitted their finalisation declarations, so employees can lodge their individual tax returns with accurate PAYG figures. Employers with only closely held payees have a longer window, but for most businesses, 14 July is the target. The ATO's [STP finalisation guidance](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll/start-reporting/end-of-year-finalisation-through-stp) covers the full requirements. Before running finalisation in MYOB Acumatica, confirm all pay runs are posted, any payroll adjustments have been applied, and your year-to-date figures reconcile to your payroll reports. The most common problem at EOFY is a discrepancy between the amounts in MYOB Acumatica and what employees believe they've received. Work through those reconciliations before you submit, not after. If your employees receive reportable fringe benefits (RFB) or reportable employer super contributions (RESC), confirm these are correctly coded in your payroll configuration before finalisation. Our post on [MYOB Acumatica payroll compliance](/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97) covers the broader payroll obligations and what to review in your system configuration ahead of the new financial year. ## **Superannuation: the current rate and Payday Super** The superannuation guarantee rate has been 12% since 1 July 2025 and stays at 12% for the 2026-27 financial year. If your payroll configuration was updated correctly when the rate changed last July, no adjustment is needed for the new year. If you're reviewing an older configuration or implementing MYOB Acumatica for the first time ahead of 1 July, confirm the rate is set to 12% before your first pay run of 2026-27. The ATO publishes [current super guarantee rates and thresholds](https://www.ato.gov.au/tax-rates-and-codes/key-superannuation-rates-and-thresholds/super-guarantee) if you need to verify. The more significant change this year is Payday Super. From **1 July 2026**, employers are required to pay super contributions within 7 days of paying wages, rather than the current quarterly schedule. The government confirmed the implementation date, and the ATO is the enforcement body. For most businesses currently paying super quarterly, this is a material change to cash flow planning and payroll workflows. For MYOB Acumatica users, Payday Super means your superannuation processing frequency changes substantially. Talk to your implementation partner or MYOB before 1 July to confirm what configuration changes are required in MYOB Acumatica to support per-pay-cycle super payments and the new STP reporting fields. Don't leave this until late June. ## **Inventory: stocktake and reconciliation** If your business holds physical inventory, a stocktake is required before 30 June. Your balance sheet needs to reflect the actual value of stock on hand at financial year-end under Australian accounting standards. In MYOB Acumatica, complete your physical count, enter the results in the inventory adjustment screen, and reconcile inventory valuation against your general ledger. Discrepancies between the inventory module and the GL are common, particularly if adjustments have been posted directly to the GL rather than through inventory. These need to be resolved before you close the financial year. If your business purchased assets during the year that may qualify for the instant asset write-off, confirm the current threshold and eligibility with your accountant before lodging your tax return. Rules on the write-off threshold have changed in recent years and your accountant will have the current position. ## **Fixed assets and depreciation** MYOB Acumatica's fixed assets module lets you run depreciation calculations for the financial year before closing. Run your depreciation schedule for the period ending 30 June, review for accuracy, and post the entries. For businesses with multiple depreciation books (such as tax depreciation and book depreciation), confirm both are current before closing the financial year. Take a system snapshot in MYOB Acumatica before you process year-end journal entries or close the financial year. Snapshots give you a restore point if something goes wrong during the close process. This is standard practice recommended by most MYOB Acumatica implementation partners and takes only a few minutes to set up. If you need a refresher on what's possible with MYOB Acumatica's system configuration tools, the [MYOB Acumatica customisation post](/blog/myob-acumatica-australia-7/myob-acumatica-customisation-australia-118) covers configuration options and when to involve your partner. ## **Period close and Q4 BAS** Before closing the June period in MYOB Acumatica, confirm all transactions for the period are posted: accounts payable, accounts receivable, payroll, inventory adjustments, and any manual journals. Running aged payables and aged receivables reports at this stage confirms there are no outstanding items that should have been included in the period. The right close sequence matters. Work through payroll first, then superannuation, then accounts payable and accounts receivable, then inventory and fixed assets, then the general ledger. Closing periods out of order can create reconciliation issues that are time-consuming to untangle. Q4 BAS (April to June 2026) is due by **28 July 2026** for businesses that self-lodge. If you use a registered tax agent, the deadline is 25 August 2026. MYOB Acumatica's GST reporting pulls directly from posted transactions, so the accuracy of your BAS depends on a clean period close. The ATO provides [BAS preparation guidance](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas/bas-and-gst-tips) if you're working through specific questions about what's reportable. If you're a government supplier working toward the eInvoicing mandate, use this EOFY period to confirm your setup is complete. Our post on [MYOB Acumatica eInvoicing](/blog/myob-acumatica-australia-7/myob-acumatica-einvoicing-australia-2026-107) covers the Peppol requirements and the compliance timeline for 2026. _"EOFY in MYOB Acumatica doesn't have to be chaotic if you start in April rather than June. The areas that create the most problems are payroll configuration, super payments, and inventory reconciliation. Getting those right before 30 June means the close process itself is straightforward. With Payday Super starting 1 July this year, the payroll preparation piece is more important than usual."_ **Josh Craig, Director, Auboros** ## **EOFY quick reference checklist** **Before 30 June:** - **Confirm super guarantee rate is 12%** in payroll settings and check Payday Super configuration changes needed from 1 July 2026 - **Complete physical stocktake** and reconcile inventory module to general ledger - **Run fixed asset depreciation** for June period and review for accuracy - **Post all AP, AR, payroll, and inventory transactions** for June before closing - **Take a system snapshot** before processing year-end journals or closing the financial year **After 30 June:** - **Submit STP finalisation declaration** by 14 July 2026 - **Lodge Q4 BAS** by 28 July 2026 (self-lodgers) or 25 August 2026 (registered agent) - **Close June period** in MYOB Acumatica after BAS lodgement is confirmed - **Confirm first pay run of 2026-27** applies the Payday Super payment schedule correctly ## **Frequently asked questions** ### **When is the STP finalisation deadline for 2026?** The standard STP finalisation deadline is 14 July 2026. Employers with only closely held payees have until 30 September 2026. Your accountant or payroll adviser can confirm whether any specific exemptions apply to your situation. The ATO updates its STP guidance regularly, so check directly for any changes to the timeline. ### **What is Payday Super and when does it start?** Payday Super is a new requirement that employers pay superannuation within 7 days of paying wages, rather than the current quarterly schedule. It starts on 1 July 2026. MYOB Acumatica users will need to adjust their payroll workflows, super payment schedules, and MYOB Acumatica configuration before that date. Talk to your implementation partner well before June. ### **What is the superannuation guarantee rate for 2026-27?** The super guarantee rate is 12% and has been since 1 July 2025. It stays at 12% for the 2026-27 financial year. The ATO publishes [current rates and thresholds](https://www.ato.gov.au/tax-rates-and-codes/key-superannuation-rates-and-thresholds/super-guarantee) if you need to verify what applies to your payroll. ### **When is Q4 BAS due for the 2025-26 financial year?** Q4 BAS (April to June 2026) is due 28 July 2026 for businesses that self-lodge. If you use a registered tax agent, the deadline is 25 August 2026. Your MYOB Acumatica GST report provides the figures you need, but a clean period close is essential for the numbers to be accurate. ### **Should I take a snapshot in MYOB Acumatica before closing the financial year?** Yes. A snapshot before year-end processing gives you a restore point if something goes wrong during journal entry posting or period close. It takes a few minutes and is recommended by MYOB and most experienced implementation partners as standard practice. Don't skip it. * * * **Need help preparing MYOB Acumatica for EOFY 2026?** Auboros supports [MYOB Acumatica users](/solutions/myob) across Queensland, NSW, and Victoria with EOFY preparation, Payday Super configuration, and system health checks. If you want a second opinion on your EOFY readiness or need help with a specific configuration issue, [**book a free consultation**](/appointment). We're Brisbane-based and work across Australia. --- # Odoo ERP in Brisbane: What Working With a Local Silver Partner Actually Looks Like - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-erp-brisbane-silver-partner-113 - Category: Odoo ERP Australia - Published: 2026-04-05 - Description: Looking for an Odoo consultant in Brisbane? Here's what working with a local Odoo Silver Partner means in practice, from scoping to go-live and beyond. There are a few dozen Odoo partners operating in Australia. Some are based in Sydney or Melbourne and service Brisbane remotely. Some are offshore teams with an Australian domain name. Auboros is actually in Brisbane, with staff who know the Queensland business environment, understand QBCC compliance for construction clients, and can be in the room when an implementation gets complicated. Whether that matters depends on your business and your project. Here's what a Brisbane-based Odoo Silver Partner actually delivers, and when being local matters more than you'd expect. ## **Why location matters for ERP implementation (and when it doesn't)** Remote ERP implementations work. Requirements workshops, configuration, training, and support can all be done effectively over video calls. If your business is straightforward and your team is comfortable with remote collaboration, geography matters less than the partner's competence and track record. Where local starts to count is in the complexity layer. When you need to walk through a physical warehouse to understand how goods actually move. When a go-live weekend involves your team, your systems, and real business pressure. When your accounts manager needs a quick answer from someone who already knows their BAS configuration and is in the same time zone. Brisbane businesses tell us consistently that having a partner they can reach, who understands their industry and Queensland-specific requirements, takes a lot of pressure off an implementation. ## **What Auboros does in Brisbane and southeast Queensland** ### **Our Odoo Silver Partner status: what it means in practice** Auboros holds [Odoo Silver Partner status](https://www.odoo.com/partners), which requires at least 75 net new paid Odoo users per year, three Odoo-certified staff members, and a 70% client retention rate. We have 12 verified client references and a 100% retention rate across every project we've delivered. Silver tier also means our team has direct access to Odoo's partner resources, escalation paths for complex technical issues, and early access to new version training before general release. In practice: when you work with us, you're not working with someone who recently discovered Odoo. You're working with a team that has been implementing it across multiple industries, has certified consultants on staff, and has a documented track record of clients staying on after go-live. You can verify our partner status directly on the [Odoo partners page](https://www.odoo.com/partners/auboros-4957994). ### **Industries we work with in SEQ** Our Brisbane client base covers manufacturing, professional services, field service, wholesale distribution, and construction. Each has its own compliance angle that matters for how Odoo is configured. Field service businesses in Queensland, for example, have specific requirements around GST invoicing in the field, subcontractor handling, and QBCC compliance for licensed trades. Our dedicated [Odoo Field Service page](/solutions/odoo-field-service-australia-nz) covers what that looks like in practice. ## **Queensland-specific considerations that affect your Odoo setup** ### **Queensland payroll tax thresholds** Queensland's payroll tax threshold is $1.3 million per year as of 2026, with a rate of 4.75% on taxable wages above that threshold. Businesses approaching or exceeding this threshold need their Odoo payroll configuration to produce the right data for payroll tax reporting, separate from the Single Touch Payroll (STP) reporting they're already doing to the [ATO](https://www.ato.gov.au). This is a configuration question, not a software limitation, but it's one that an implementation partner with Queensland-specific experience handles differently from one who's never dealt with state payroll tax reporting. ### **QBCC compliance for construction and trades** Queensland's [Queensland Building and Construction Commission (QBCC)](https://www.qbcc.qld.gov.au) has financial requirements for licensed contractors, including minimum net tangible asset ratios and financial reporting obligations for projects above certain thresholds. If your Brisbane business is a licensed contractor or subcontractor, your Odoo accounting configuration needs to produce the financial data your QBCC reporting requires. We've implemented Odoo for construction businesses in SEQ and understand what that configuration looks like. ## **What a Brisbane Odoo engagement looks like** _"The moment that sticks with me most from a recent Brisbane implementation was a go-live weekend where the client's warehouse team picked up a scanner for the first time on a Monday morning. Having someone physically there, who knew their products and their team, made the difference between a smooth start and a panic call. That's the thing remote support genuinely can't replicate."_ **Josh Craig, Director, Auboros** A typical Odoo engagement starts with a discovery session, usually two to three hours, where we map your current processes, identify the gaps Odoo needs to fill, and give you a realistic implementation scope and timeline. From there, we configure in weekly sprints with your team involved throughout, rather than disappearing for months and presenting a finished system that doesn't fit how you actually work. Our implementation timeline for a mid-size Brisbane business is typically 10 to 18 weeks from project start to go-live, depending on scope and the complexity of integrations or customisations involved. Full details on our approach and pricing are on our [Odoo implementation packages page](/odoo-implementation-packages-for-australian-businesses). Post-go-live support is included in every project and transitions into ongoing support if you need it. Our clients don't get handed off to a helpdesk after implementation. The team that implemented their system knows their configuration and stays involved. You can read more about what our [Odoo services](/solutions/odoo) include on our solutions page. ## **Frequently asked questions** ### **Is Auboros the only Odoo Silver Partner in Brisbane?** Auboros is Brisbane's locally based Odoo Silver Partner. There are other Odoo partners operating in Australia, some of whom service Queensland remotely from Sydney or Melbourne. Auboros is physically located in Brisbane, with staff based in SEQ. You can verify the full Australian partner list and tier status on the Odoo partners page at odoo.com/partners. ### **Can you implement Odoo remotely for us?** Yes. We work remotely with clients across Queensland, NSW, and Victoria, and handle most of the implementation process via video and shared project tools. For Brisbane and SEQ clients who prefer it, we can also work on-site for workshops, go-live support, and training. The mix depends on what your business and team need. ### **Do you work outside Brisbane?** We work with businesses across Queensland, NSW, and Victoria. Our Brisbane base is our home, but we've implemented Odoo for clients on the Gold Coast, Sunshine Coast, and in regional QLD, as well as interstate. Remote delivery works well for most project phases. We travel for go-live support and training when it makes sense. ### **How long does an Odoo implementation take in Queensland?** For a typical mid-size Queensland business, 10 to 18 weeks from project start to go-live is a realistic expectation, depending on the number of modules involved, any third-party integrations, and how quickly your team can participate in the configuration and testing phases. Our [Odoo implementation guide for Australian businesses](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) goes into timeline detail across different project sizes. * * * **Looking for an Odoo partner in Brisbane or southeast Queensland?** Auboros is Brisbane's locally based Odoo Silver Partner. We implement, customise, and support Odoo for businesses across Queensland and nationally, with a team that understands Queensland compliance, industry-specific requirements, and what it takes to make an implementation land properly. If you want a no-obligation conversation about your project, [**book a free consultation**](/appointment). We'll give you an honest assessment of scope, timeline, and whether Odoo is the right fit for your business. --- # Odoo Field Service Australia: Scheduling, Mobile, and GST Invoicing for Trades and Service Businesses - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-field-service-australia-110 - Category: Odoo ERP Australia - Published: 2026-04-05 - Description: How Odoo Field Service works for Australian trades and service businesses. Scheduling, mobile worksheets, GST invoicing, and inventory in one platform. If you run a field service business in Australia, you've likely stitched together a handful of tools to keep the wheels turning. A job management app here, an invoicing platform there, maybe a spreadsheet for parts. It works, until it doesn't. Odoo Field Service is one module inside a larger ERP, which means it connects to your inventory, your accounts, and your customer records rather than sitting in its own silo. This post covers what it actually does, where it fits well, and where it has limits. ## **What does Odoo Field Service actually do?** [Odoo Field Service](https://www.odoo.com/app/field-service) is a job dispatch and management tool. You create tasks, assign them to technicians, track completion, log parts used, and generate invoices, all within the same system your accounts team is already using. The scheduler sees a kanban or calendar view of the whole team. Technicians get a mobile app. Customers get a portal where they can view their job history and invoices. What makes it different from a standalone tool like Fergus or ServiceM8 is the integration depth. A completed field job can automatically pull the parts used from your warehouse stock, create a draft invoice with GST calculated correctly, and post to your general ledger without anyone re-entering data. That's the trade-off: you get more integration, but you're also committed to a full ERP rather than a lightweight app. ## **Scheduling and dispatch in practice** The scheduling side of Odoo Field Service gives dispatchers four views: kanban, calendar, Gantt, and map. The map view is particularly useful for route planning when you've got multiple technicians covering a region. You can drag and drop jobs between team members, set dependencies (don't go to site B before site A is done), and see everything in hourly, daily, or weekly resolution. Recurring jobs are also supported natively, so if you have maintenance contracts or regular service visits, these generate automatically on the schedule you set. For businesses running preventive maintenance programs across a portfolio of equipment, this removes a significant amount of manual scheduling work. Tasks can also be created automatically rather than manually dispatched. A sales order, a helpdesk ticket, a web form, or an email alias can all trigger a new field job. For businesses where the gap between "client signs up" and "job gets booked" is a constant source of friction, this matters. ## **The mobile experience: what technicians can do on-site** The Odoo mobile app covers the essentials for field technicians. They can view their assigned jobs, update task status, fill in worksheet forms, record parts used, capture customer signatures, and generate a draft invoice on the spot. There's a built-in timer for tracking labour time, which feeds directly into the invoice. Worksheets are customisable. You can build templates specific to your service types, so an electrical inspection checklist looks different from a plumbing fault report. Completed worksheets can be sent to the customer as a PDF report at job close-out. If you need pre-built Australian compliance templates covering standards like electrical (AS/NZS 3000), HVAC, heights safety, and fire safety, our [FieldPro field service solution](/solutions/odoo-field-service-australia-nz) includes these out of the box alongside Odoo. One practical limit worth knowing: Odoo's mobile app works best with a stable internet connection. Offline mode is available in [Odoo v19](https://www.odoo.com/documentation/19.0/applications/services/field_service.html) for some functions, but it's not as fully developed as some purpose-built field service apps. If your technicians work in areas with poor mobile coverage regularly, test this carefully before committing. For businesses where offline capability is non-negotiable, our [FieldPro app](/solutions/odoo-field-service-australia-nz) works fully offline and syncs back to Odoo when connectivity is restored. ## **Parts, inventory, and GST invoicing** When a technician records parts used on a job, those stock movements update inventory in real time. If you've set up reorder rules, a low stock alert can trigger a purchase order automatically. For businesses that carry a van stock of commonly used parts, this kind of visibility is genuinely useful. On the invoicing side, completed field jobs generate a draft invoice that includes labour time (from the timer), parts used (from the worksheet or parts list), and any additional charges. GST is applied according to your tax rules in Odoo's accounting module, which handles the Australian 10% GST rate and generates invoices in the correct format for [ATO compliance](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst). Business Activity Statement (BAS) reporting pulls from the same invoicing data, so there's no manual export or reconciliation step. For [businesses managing warehouse stock](/blog/odoo-erp-australia-6/odoo-inventory-management-australia-106) alongside field operations, having both sides inside Odoo means your field team and warehouse team are working from the same inventory data rather than separate systems that get reconciled at month end. ## **How Odoo Field Service connects to the rest of the business** The integration with Odoo's other modules is the main reason you'd choose this over a cheaper, simpler field service app. From a single job record, you can see the customer's full history (quotes, previous jobs, open invoices), the stock levels of parts you'll need, and the profitability of the project once it's closed. That kind of connected view is hard to get from a stack of separate apps. _"Most field service businesses we work with are running three or four separate systems. Scheduling in one place, invoicing in another, inventory somewhere else. Odoo isn't the lightest tool on the market, but once it's set up properly, the fact that a technician can close a job on their phone and the invoice is ready to approve in accounting ten minutes later is where the real efficiency shows up."_ **Josh Craig, Director, Auboros** Odoo Field Service also connects naturally to the CRM module if you're managing service contracts as part of a sales pipeline, and to the project module if your field jobs are part of a larger project with multiple stages. For [businesses already using Odoo CRM](/blog/odoo-erp-australia-6/odoo-crm-australia-features-guide-104), adding field service means your service delivery and customer relationship data live in the same place. ## **Does Odoo Field Service suit Australian trades businesses?** Construction is Australia's largest industry by business count, with [462,939 businesses recorded by the ABS at 30 June 2025](https://www.abs.gov.au/statistics/economy/business-indicators/counts-australian-businesses-including-entries-and-exits/latest-release), and the sector grew 2.2% in the 2024-25 period. Most of them are small. According to the ABS, 91% of construction businesses have fewer than five employees. But plenty of those businesses have real operational complexity: quoting, dispatching, parts tracking, invoicing, BAS reporting. The tools that handle a sole trader at 20 jobs a month stop working well at 200. Where Odoo fits best in this market: businesses that have outgrown simple job management apps and need their field operations connected to real accounts, real inventory, and proper BAS reporting. If you're quoting, dispatching, and invoicing all from a single system, you remove a significant amount of double-handling. Where it may not be the right fit: very small operations (under five people) where the setup cost and learning curve of a full ERP outweighs the benefit, or businesses that need deep integration with Australian-specific trade platforms like Simpro or Fergus. Those tools have more trade-specific features, but they don't include a full ERP behind them. For businesses considering Odoo as a full [ERP platform](/solutions/odoo), the field service module is included in the Enterprise subscription rather than charged separately. If you're already running Odoo for accounting, inventory, or sales, adding field service doesn't add to the per-user cost. Our dedicated [Odoo Field Service page for Australia and NZ](/solutions/odoo-field-service-australia-nz) covers how we configure and support implementations for local businesses, including integration with Australian payroll and compliance requirements. ## **Frequently asked questions** ### **Does Odoo Field Service work offline?** Odoo v19 includes limited offline capability for the mobile app, covering basic task viewing and updates. Full offline functionality, including parts recording and invoice creation, typically requires a connection. If your technicians work in areas with poor mobile coverage, it's worth testing this in a demo environment before you commit. It's improving with each release, but standalone trade apps like Simpro handle offline better. If full offline functionality is a firm requirement, our [FieldPro solution](/solutions/odoo-field-service-australia-nz) is built specifically for this and syncs with Odoo when back online. ### **Can Odoo generate GST-compliant tax invoices from field jobs?** Yes. Odoo's accounting module includes Australian GST tax rules, so invoices generated from completed field jobs include the correct 10% GST breakdown and meet the ATO's requirements for a valid tax invoice. These invoices also feed into your BAS reporting automatically. For more on how the localisation works, see our post on [Odoo's Australian localisation for BAS and STP](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98). ### **What's the difference between Odoo Field Service and Odoo Project?** They're related but serve different purposes. Odoo Project is built for multi-task, multi-stage work where the focus is tracking progress and collaboration. Odoo Field Service is optimised for dispatching mobile workers to specific locations, capturing on-site work records, and generating invoices from those records. For a plumbing firm responding to service calls, Field Service makes more sense. For a construction company managing a multi-month build, Project is the better fit. Many businesses use both. ### **Is Odoo Field Service available on iOS and Android?** Yes, the Odoo mobile app is available on both iOS and Android and supports the Field Service module. Technicians can access their scheduled tasks, fill in worksheets, record parts, capture signatures, and create invoices from their phone or tablet. ### **How does Odoo Field Service handle subcontractors?** Odoo can assign tasks to external contractors as well as internal staff. The vendor management and purchase order functionality handles subcontractor costs, which can be included in job profitability reporting. The level of visibility into subcontractor time and work completion depends on whether they have access to your Odoo instance, which some businesses allow and others prefer to manage externally. * * * **Is Odoo the right fit for your field service operation?** We implement and support Odoo Field Service for trades and service businesses across Queensland, New South Wales, and Victoria. If you want to understand whether it suits your operation before you commit, we're happy to walk through a real scenario with you. If you're evaluating your options, [**book a free consultation**](/appointment). No pressure, just a straight conversation about whether Odoo fits. --- # Odoo Shopify and WooCommerce Integration for Australian Businesses: What Syncs, What Doesn't, and When It Makes Sense - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-shopify-woocommerce-integration-australia-114 - Category: Odoo ERP Australia - Published: 2026-04-05 - Description: Running Shopify or WooCommerce in Australia? Here's how Odoo integrates with both, what syncs automatically, and when keeping two systems is the right call. A lot of Australian businesses end up in the same situation: Shopify or WooCommerce is running their online store, and Odoo is (or will be) running everything else. The question they ask us is whether those two systems can actually talk to each other, and whether the connection is worth building. The short answer is yes. The longer answer is that the value depends heavily on how you configure it. Here's how both integrations work, what they sync well, where they fall short, and when it makes more sense to consolidate onto Odoo eCommerce instead. ## **Two ways to connect Odoo with your online store** Odoo doesn't include a Shopify or WooCommerce connector in its core product. Connections are built through third-party modules from the [Odoo Apps Store](https://apps.odoo.com) or through connector modules available via Shopify's own app marketplace. These are production-tested modules used by thousands of businesses globally, not experimental integrations. The two most common approaches are: - **Install a connector module in Odoo** that polls or webhooks with your Shopify or WooCommerce store. You manage the sync configuration from within Odoo. - **Install a connector app in Shopify** that pushes data to Odoo. You manage the connection from the Shopify side. Most Australian businesses use the Odoo-side module approach, because it gives you more control over sync rules, data mapping, and error handling. Either way, you're connecting two live systems, and the configuration decisions you make at setup determine how well it runs day to day. ## **Odoo and Shopify integration: what syncs and what doesn't** ### **Products, variants, and inventory** Product data is the core of any eCommerce integration. A well-configured Odoo-Shopify connector syncs product details (name, description, images, SKUs), pricing, variant combinations (size, colour, material), and stock levels between the two platforms. Inventory adjustments in Odoo, whether from a purchase receipt, a stock count, or a manual adjustment, push updated quantities to Shopify automatically or on a scheduled job. The sync usually runs in both directions for inventory but one direction for product data. Shopify is often the storefront source of truth for product presentation; Odoo is the source of truth for stock and costing. Getting that right at implementation is the decision that determines whether the sync runs cleanly day to day. Get it wrong and you'll spend time reconciling phantom stock or duplicated products. ### **Orders, fulfilment, and refunds** Shopify orders import into Odoo automatically, triggering delivery orders in Odoo's warehouse module. When you mark a delivery as done in Odoo, the fulfilment status updates in Shopify and the customer gets their shipping notification. Refunds and returns can be handled in Odoo and reflected back to Shopify, though the exact behaviour depends on which connector you use and how payment processing is configured. Partial fulfilment (sending some items now and the rest later) works in most connectors but requires careful setup. If your fulfilment operations are complex, test this thoroughly before going live. ### **GST handling and Australian tax settings** Australian businesses selling through Shopify collect GST at 10% on most goods and services. Odoo's Australian localisation handles GST automatically in its accounting and inventory modules, but the integration between Shopify's tax records and Odoo's tax lines requires specific mapping. If this isn't configured correctly, your BAS reconciliation becomes painful. It's worth spending time at setup to verify that Shopify's GST amounts match what Odoo is recording for each order type, particularly if you sell a mix of GST-applicable and GST-free goods. The [ATO's GST guidance](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst) is the reference point for what applies. ## **Odoo and WooCommerce integration: the WordPress option** WooCommerce integration with Odoo follows the same broad pattern as Shopify but with some practical differences. WooCommerce runs on WordPress, which means the integration is typically built through a WordPress plugin or an Odoo module that connects via WooCommerce's REST API. Several well-supported modules specialise in this connection, and it's well-established for businesses that have invested significantly in their WordPress storefront. WooCommerce gives you more control over the storefront than Shopify does (no platform fees per transaction, full code access), but the integration is typically more involved to set up and maintain. If your WooCommerce site is heavily customised, plan for a more complex integration project than a standard Shopify connection would require. _"The integration mistake we see most often isn't choosing the wrong connector. It's treating the sync as a set-and-forget after go-live. The sync rules need reviewing as your product catalogue changes, as you add new order types, and when either platform updates. Building in a quarterly review of sync health is worth the hour it takes."_ **Bill Alvarez, Practice Manager, Auboros** ## **Australian logistics: StarshipIT and Australia Post** For most Australian businesses, the integration picture extends beyond the store and ERP to include a shipping connector. StarshipIT connects directly with Odoo's inventory and delivery modules and supports Australia Post, Sendle, DHL, and other carriers. When a Shopify or WooCommerce order lands in Odoo and a delivery is confirmed, StarshipIT generates the label and books the carrier automatically. This is worth building into your integration plan from the start. Separating the eCommerce sync and the shipping integration into two separate phases often causes duplication of effort. Our post on [Odoo inventory management for Australian businesses](/blog/odoo-erp-australia-6/odoo-inventory-management-australia-106) covers the StarshipIT connection in more detail. ## **Getting the integration right: the Auboros approach** You don't have to choose between a rigid off-the-shelf connector and a fully custom-built solution. The connector modules available in the [Odoo App Store](https://apps.odoo.com) are a solid foundation for most Shopify and WooCommerce integrations, and can be extended to meet your specific requirements without the cost and risk of building from scratch. Our recommended approach is straightforward: take one of these existing connectors, deploy it in a staging environment first, and run a structured gap analysis before anything goes live. The staging phase lets you see exactly how data flows between Odoo and your store in a controlled setting. You'll quickly identify which fields map correctly, where the edge cases appear, and what the connector doesn't handle out of the box. The gap analysis then becomes your scoping document for the go-live build: here's what works as-is, here's what needs configuration, and here's what needs a targeted extension. This approach produces better results than commissioning a full custom integration from day one. You're extending something production-tested across thousands of deployments globally, rather than building logic from scratch and discovering edge cases in your live environment. The gaps in your specific setup are usually configuration decisions rather than fundamental limitations of the underlying connector, and starting from that baseline is both faster and lower-risk than starting from nothing. ## **When to keep Shopify or WooCommerce (and when to switch to Odoo eCommerce)** If you've invested significantly in your Shopify theme, your conversion rate is solid, and your product catalogue is well-structured there, keeping Shopify as your storefront and connecting Odoo as the back end is often the right call. You get Shopify's storefront strengths and Odoo's operational depth, and you don't have to rebuild something that's working. The case for migrating to [Odoo eCommerce](/solutions/odoo) gets stronger when you're already deep in Odoo for everything else and your Shopify store doesn't have complex front-end customisation that would be costly to rebuild. Odoo eCommerce shares the same product catalogue, pricing, and inventory as the rest of Odoo natively, so there's no sync to manage and no risk of data drift between systems. For businesses starting from scratch, this often makes more sense than running two platforms. What doesn't make sense is running two systems without connecting them at all. Manual order entry from Shopify into Odoo is the worst of both worlds: double-handling, error-prone stock counts, and BAS figures that require manual reconciliation. If you're doing this now, the integration project will pay for itself quickly. Details on our [Odoo implementation packages](/odoo-implementation-packages-for-australian-businesses) are on our pricing page, including integration scoping. ## **Frequently asked questions** ### **Does Odoo have a native Shopify connector?** Odoo doesn't include a Shopify connector in its core product. Connections are built through third-party modules from the Odoo Apps Store or through Shopify's own app marketplace. Several well-supported connectors are available for Odoo v18 and v19, covering product sync, order import, inventory updates, and fulfilment status. ### **Can I run WooCommerce and Odoo at the same time?** Yes. Running WooCommerce as your storefront with Odoo handling inventory, accounting, and operations is a common and workable setup for Australian businesses. The connection requires a WooCommerce-Odoo integration module, careful configuration of product mapping and tax settings, and ongoing maintenance as either platform updates. ### **Does the Shopify-Odoo integration handle Australian GST automatically?** GST handling requires specific configuration during setup. Odoo's Australian localisation manages GST correctly within Odoo, but you need to map Shopify's tax records to Odoo's tax lines accurately to ensure your BAS figures reconcile without manual adjustment. This is one of the most important things to test before going live, particularly if you sell a mix of taxable and GST-free products. ### **How long does a Shopify or WooCommerce integration with Odoo take to set up?** A standard Shopify integration with a straightforward product catalogue and order flow typically takes 2 to 4 weeks from scoping to go-live, including configuration, testing, and staff training. WooCommerce integrations with heavily customised WordPress sites or complex order types can take longer. The shipping connector (StarshipIT or similar) adds time if it's scoped as part of the same project. * * * **Connecting Odoo to your Shopify or WooCommerce store in Australia?** Auboros implements and integrates Odoo for businesses across Brisbane, Queensland, and nationally. Our [Odoo integration services](/solutions/odoo-integrations) page covers how we design syncs that hold up in production. We scope integrations properly, which means mapping your tax rules, product variants, and fulfilment workflows before anything goes live rather than fixing problems after the fact. If you're planning an eCommerce integration or evaluating whether to consolidate onto Odoo, [**book a free consultation**](/appointment). We'll give you an honest read on what's involved. --- # Odoo v20: What's Confirmed, What's Expected, and What Australian Businesses Should Plan For - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-v20-australia-features-roadmap-115 - Category: Odoo ERP Australia - Published: 2026-04-05 - Description: Odoo v20 is the most AI-forward release yet. What's confirmed, what's expected at Odoo Experience 2026, and what Australian businesses should plan for now. Odoo v20 is expected to launch at [Odoo Experience 2026](https://www.odoo.com/odoo-experience) in Brussels from 24 to 26 September, with general availability following in October or November. Based on the official v20 roadmap presented by Luc Nailis, Odoo's Product Owner, this release is the most AI-forward in Odoo's history, with significant upgrades across finance, manufacturing, inventory, CRM, field service, and infrastructure. Here's what's on the roadmap by module, what it means for Australian businesses, and how to think about timing. ## **The big theme: agentic AI across the platform** The defining shift in v20 is the move from assistive AI to agentic AI. Odoo v18 and v19 introduced AI features that respond to your prompts: drafting emails, scoring leads, extracting document data. V20's direction is for the AI to monitor your business data and initiate actions without being asked. In practice, this means Odoo could raise a purchase order automatically when stock drops below threshold, flag an overdue invoice cluster before your accounts team spots it, or route a support ticket based on message sentiment without manual triage. AI-powered suggestions are deepening across CRM, email, helpdesk, and document processing. The platform is designed to support AI agents that can take multi-step actions across modules autonomously. If this delivers as described, it changes the nature of what ERP software does. Odoo moves from a system you operate to one that handles some of the monitoring and routine decision-making for you. We covered what the current AI modules already do in our post on [AI in Odoo for Australian businesses](/blog/odoo-erp-australia-6/ai-in-odoo-australia-2026-102). V20 builds significantly on that foundation. For Australian SMEs, the AI improvements have a practical payoff: less manual bookkeeping, automated bank reconciliation matching, and workflow automation for tasks that currently require staff attention. The businesses that benefit most will be those with clean, well-structured data, which is another reason why how you implement v18 or v19 now matters for what you get from v20 later. ## **Finance and accounting** The accounting module in v20 gets meaningful upgrades beyond the agentic AI layer. Financial forecasting moves into the core platform, with AI-assisted cash flow predictions sitting alongside your standard reporting rather than requiring custom reports or add-ons. Bank reconciliation improves with smarter AI matching that learns from your reconciliation patterns over time, reducing the manual work that currently sits between importing your bank feed and completing the reconciliation. Real-time financial dashboards and better reporting are on the roadmap, giving finance teams visibility without needing to export to spreadsheets. Multi-currency and multi-company handling also sees improvements, relevant for Australian businesses with international operations or holding company structures managing multiple entities in Odoo. How these features interact with the Australian localisation (specifically GST treatment, BAS quarter reporting, and Single Touch Payroll) will be confirmed closer to the release. Australian localisation updates typically follow the core international release by several weeks as the local team validates compliance against current ATO requirements. ## **Manufacturing and MRP** V20 brings a more capable manufacturing module, with improved MRP scheduling and capacity planning at its core. Work order management improves with real-time production tracking, giving floor managers better visibility into what's in progress, what's blocked, and where bottlenecks are forming. The integration between manufacturing and inventory tightens in v20, which has practical implications for businesses running both modules. Inventory consumption from production, quality hold management, and finished goods receipts should all require less manual intervention than in current versions. Quality control improvements are also on the roadmap. For Australian manufacturers and distributors already using Odoo's MRP module, the scheduling and capacity planning improvements are likely to be the most immediately useful change. Capacity planning has historically required workarounds in Odoo; v20 addresses this more directly in the core product. ## **Inventory and supply chain** The inventory module in v20 focuses on operational efficiency for businesses running complex warehouse operations. Putaway rules and warehouse routing logic improve, making multi-location warehouse configuration simpler without custom development. Cross-docking and multi-step route management also sees improvements for businesses with more complex fulfilment workflows. Demand forecasting gets better AI integration, with the system using historical sales data to suggest reorder points and purchase quantities. Lot and serial number tracking improves for businesses with traceability requirements, relevant for food, pharmaceutical, and regulated industries operating in Australia. These are incremental but meaningful improvements to areas that come up regularly in inventory-heavy implementations. ## **CRM and sales** The CRM module gets AI-assisted lead scoring and next-action recommendations in v20, building on the lead probability features already in v18 and v19. Pipeline management and sales forecasting improve, with better visibility into deal velocity and more accurate revenue projections. Customer communication tracking (emails, calls, meetings) integrates more tightly with the pipeline view, reducing the context-switching that sales teams currently deal with when trying to understand the history of a deal. Quotation and proposal tools also improve, which is useful for businesses using Odoo for complex B2B quoting. The combination of better lead scoring, improved forecasting, and stronger communication tracking makes v20's CRM module meaningfully more capable for sales-led organisations. ## **Field service, eCommerce, and other modules** The [field service module](/solutions/odoo-field-service-australia-nz) gets scheduling and dispatching improvements in v20, along with mobile app improvements for field technicians. Better time tracking and reporting round out the field service updates, useful for businesses billing on time and materials or managing large field teams. Odoo's eCommerce module continues to evolve, with an improved website builder, better SEO tools built into the platform, and an improved product page and checkout experience. For businesses considering Odoo eCommerce as an alternative to Shopify or WooCommerce, the v20 improvements make the native option more competitive, though integrating an existing third-party storefront remains the right call for businesses with established eCommerce operations worth preserving. ## **Infrastructure: read replicas and performance at scale** On the infrastructure side, v20 introduces read-replica database architecture. This means Odoo can direct reporting and analytics queries to a secondary database copy rather than competing with live transactional processing. The practical result is better operational performance when someone is pulling a large financial report or running a complex analysis while the rest of the team is actively working in the system. Multi-company and multi-database support also improves in v20, along with API capability improvements for businesses building integrations with other systems. For businesses running Odoo at scale, these infrastructure improvements become more valuable as data volumes grow over time. ## **How v20 connects to what's already in v18 and v19** Odoo v18 and v19 already include a solid set of AI-assisted features: document digitisation, lead scoring in CRM, email suggestions, and sales forecasting. These are well-established and working in Australian production environments. V20's agentic layer is designed to sit on top of this foundation, not rebuild it. This matters practically for anyone implementing now. If you deploy v18 or v19 and configure it well, you're not creating technical debt you'll have to undo for v20. You're building the data foundation that v20's autonomous features will need to work from. A messy v18 implementation won't suddenly run well under v20. Clean, well-scoped projects upgrade better, and the [implementation decisions you make now](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) matter for how smoothly you'll move forward. ## **Should you wait for v20 or implement on v18 now?** _"The most common question we get at the moment is whether to implement v18 or hold out for v20. Our answer is almost always the same: a well-configured v18 running now beats waiting 12 months for v20. Every month without an integrated system is a month of manual work, data gaps, and business decisions made without the visibility you should have."_ **Josh Craig, Director, Auboros** Waiting for v20 means waiting until at least October 2026 for general availability, and realistically into Q1 2027 before a fully localised, stable Australian version is ready for production use. Australian localisation updates, covering [Single Touch Payroll (STP)](https://www.ato.gov.au/businesses-and-organisations/employer-obligations/single-touch-payroll-employer-guide), GST, and BAS reporting, typically follow the core international release by several weeks as the Australian team validates compliance against current ATO requirements. The case for acting on v18 or v19 now is practical rather than urgent. Most businesses see a 12-to-18-month return on investment window after an Odoo implementation. If you start now, you'll be in a stable, productive system well before v20 is ready for Australian production deployment. And the eventual upgrade to v20 is a supported, planned process, not a rip-and-replace exercise. ## **What the upgrade process looks like for Enterprise subscribers** One of the less-discussed advantages of Odoo Enterprise is the upgrade model. The [Odoo upgrade service at upgrade.odoo.com](https://upgrade.odoo.com) is free for all Enterprise subscribers, regardless of which version you're moving from. You submit your database, Odoo runs the automated upgrade against a staged environment, and you test before cutting over to production. It's not zero-effort, but it's a planned, supported process rather than a rip-and-replace exercise. What requires attention between versions is typically your custom modules and any third-party apps you've installed. Core Odoo modules upgrade cleanly. If you've built significant customisations, those need compatibility review before any major version jump. That's true now and will be true when v20 arrives. It's another reason to keep customisations well-documented and scoped to genuine business needs rather than cosmetic preferences. Our [Odoo implementation and support services](/solutions/odoo) include upgrade planning as part of ongoing support, including pre-upgrade audits of custom modules and third-party compatibility checks. ## **Frequently asked questions** ### **When is Odoo v20 released in Australia?** Odoo v20 is expected to launch at Odoo Experience 2026 (24 to 26 September, Brussels), with general availability from October 2026. Australian localisation, including GST, BAS, and STP updates, typically follows the core release by several weeks. Businesses considering Australian production deployments should plan for late 2026 or early 2027 for a fully localised stable version. ### **Is the v20 upgrade free for Odoo Enterprise customers?** Yes. The Odoo upgrade service at upgrade.odoo.com is available at no additional cost to all Enterprise subscribers, whether you're moving from v17, v18, or v19. The cost involved is the partner time to manage the process, test customisations, and support the transition, not the upgrade itself. ### **What are the biggest new features in Odoo v20?** The biggest shift in v20 is the move to agentic AI: the system initiates actions based on data patterns rather than waiting for user prompts. Beyond AI, v20 brings significant upgrades to finance (AI-assisted forecasting and bank reconciliation), manufacturing (MRP scheduling and real-time production tracking), inventory (demand forecasting and improved warehouse routing), CRM (AI lead scoring and pipeline management), and infrastructure (read-replica database support for better performance at scale). ### **Should we implement v18 now or wait for v20?** For most businesses, implementing on v18 or v19 now is the better decision. V20 won't be production-ready in Australia until late 2026 at the earliest. Waiting means continuing to operate without the operational visibility an integrated system provides. The upgrade from v18 to v20 is a supported process through Odoo's free upgrade service, not a reimplementation. * * * **Planning your Odoo roadmap ahead of v20?** Auboros is an Odoo Silver Partner based in Brisbane, supporting businesses across Queensland, NSW, and Victoria. We implement on v18 and v19 now and build upgrade pathways into every engagement, including a roadmap review session when v20 is ready for Australian deployment. If you're on an older version today, our [Odoo upgrade service](/solutions/odoo-upgrades) covers how we get you current without the drama. If you want an honest assessment of where your business sits in the v20 roadmap, [**book a free consultation**](/appointment). We'll give you a clear picture of what's coming and what to do now. --- # MYOB Acumatica Customisation in Australia: What's Possible, What It Costs, and How to Scope It - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-customisation-australia-118 - Category: MYOB Acumatica Australia - Published: 2026-04-05 - Description: MYOB Acumatica is highly customisable, but what does that mean in practice? We cover what's possible, how it's scoped, and what it costs in Australia. One of the most common questions we get during MYOB Acumatica evaluations is some version of: "Can it be customised to fit how we work?" The short answer is yes. The longer answer is that "customisation" covers a wide range of things, from configuring a dashboard to writing custom screens that change how the system behaves for your industry. Understanding the difference matters before you start scoping, because the cost and ongoing maintenance implications are very different depending on what you're actually asking for. This post covers the distinction between configuration and customisation, what the xRP platform makes possible at each level, what custom work typically costs in Australian projects, and how to avoid the mistakes that make custom development expensive to maintain. ## **Configuration versus customisation: why the distinction matters** MYOB Acumatica draws a clear line between configuration and customisation, and it's worth understanding before you brief a partner. Configuration is everything you do inside the standard Acumatica interface without touching code. Setting up your chart of accounts, defining approval workflows, building Generic Inquiries (custom reports), configuring Business Events (automated notifications and triggers), setting user roles and access permissions, building dashboards for different roles in your business. Most of what Australian businesses need to make Acumatica work for their operations falls into this category. A well-scoped implementation handles all of this during the standard project. Customisation is what happens when configuration isn't enough. It means extending or modifying the platform's behaviour using Acumatica's xRP development framework. Adding a custom field to a standard screen. Building a new screen for a workflow that doesn't exist in the core product. Integrating with a third-party system via the REST API. Building industry-specific functionality that Acumatica doesn't include out of the box. The reason this distinction matters: configuration changes are safe across version upgrades. Customisations need to be tested and sometimes updated with each major version. That ongoing maintenance cost is real, and it's what shapes how we scope any custom development request. ## **What MYOB Acumatica's xRP platform makes possible** MYOB Acumatica is built on [Acumatica's xRP platform](https://www.acumatica.com/acumatica-erp-platform/), which is designed specifically for extensibility. Unlike some ERP platforms where custom code sits in a separate layer that breaks on every upgrade, xRP customisations are built using a published API and documented patterns that the upgrade process recognises. Custom objects upgrade with the system rather than against it, which is a meaningful difference when you're looking at a platform you'll run for a decade. ### **Generic Inquiries: custom reporting without code** Generic Inquiries are one of the most underused tools in a standard MYOB Acumatica implementation. They let you build custom reports, pivot tables, and data exports from any table in the Acumatica database, entirely within the standard interface, no code required. If your CFO needs a report that the standard library doesn't produce, Generic Inquiries are almost always the right starting point before commissioning custom development. They also feed into configurable dashboards, so the KPIs your warehouse manager sees when they log in can look completely different from what your finance director sees. ### **Business Events: automated triggers across the system** Business Events let you define conditions and automated actions across the platform. When a purchase order is approved above a certain value, notify the finance director. When stock falls below a reorder point, create a purchase requisition. When a project milestone is marked complete, send a billing notification. These are all configuration, not customisation, and they cover a significant portion of the workflow automation that businesses assume requires custom code. ### **REST API for external integrations** MYOB Acumatica's [REST API](https://help-2024r2.acumatica.com/Help?ScreenId=ShowWiki&pageid=b93fa992-42c7-4f4d-a38e-f9cffd0d3e71) exposes the full range of Acumatica's business logic for integration with external systems. eCommerce platforms, third-party logistics providers, custom portals, and industry-specific tools all connect via the API. According to [MYOB's ERP Trends Report 2025](https://www.myob.com/au/insight/post/erp-trends), 45% of Australian decision-makers say disconnected systems are limiting their business growth. For most of those businesses, the API is where the answer starts, not a custom module build. ### **Custom screens and industry-specific extensions** Where the xRP framework goes beyond configuration is in genuinely custom screens and business logic. Examples from Australian projects include: a custom job card screen for a manufacturer that doesn't fit neatly into the standard production order workflow; a client-portal-facing view that surfaces specific project data without exposing the full Acumatica interface; a compliance tracking screen built for a business with regulatory reporting requirements specific to their industry. These are real development projects, scoped, built, and tested like any software engagement. _"The question I ask before we scope any customisation is: if we build this, who maintains it in two years? If the answer is unclear, that's a signal to look harder at what the standard platform already does. We've saved clients significant custom development spend by going back to the Business Events and Generic Inquiry toolset they already had access to."_ **Bill Alvarez, Practice Manager, Auboros** ## **What customisation typically costs in Australian projects** Custom development in MYOB Acumatica is priced as a professional services engagement. There's no flat rate because the scope varies too widely. A simple custom field or screen modification might take four to eight hours of developer time. A complex industry-specific extension with its own data model, custom screens, and business logic could run to 80 to 200 hours or more. For Australian businesses planning a customisation budget, the main variables are the number of custom objects involved, whether the customisation needs to interact with multiple Acumatica modules, the complexity of testing and validation required, and how many users are affected. Our guide on [choosing the right MYOB Acumatica implementation services](/blog/myob-acumatica-australia-7/choose-right-myob-acumatica-implementation-services-5) covers how to evaluate whether your prospective partner has the technical capability to build and support what you need. The ongoing maintenance consideration is worth budgeting separately. Each major Acumatica version release requires a compatibility review of any custom code. For well-scoped, well-documented customisations, this is typically a few hours of work per upgrade cycle. For sprawling, poorly documented custom builds, it can become a significant cost that wasn't anticipated at the time of implementation. This is the argument for keeping customisations targeted and for working with a partner who documents what they build. ## **What to avoid when customising MYOB Acumatica** The mistakes we see most often in custom Acumatica work: customising something the standard platform already handles with the right configuration, building custom code for a one-off requirement that will change in six months, and using customisation to paper over a process problem rather than fixing the process. None of these make the platform better. They add maintenance cost without adding lasting value. A second common mistake is scoping customisations before configuration is complete. The standard Acumatica toolset is more capable than most businesses expect: Generic Inquiries, Business Events, configurable workflows, role-based dashboards. Many businesses that come to us assuming they need custom development find that what they need already exists, and that the gap was in how their previous implementation was configured rather than what the product can do. Our [MYOB Acumatica consulting guide](/blog/myob-acumatica-australia-7/myob-acumatica-consulting-what-to-look-for-99) covers what good partner engagement looks like at the scoping stage, including how a partner should challenge customisation requests before committing to build them. For businesses currently running customisations built by a previous partner and looking for ongoing support, our [MYOB Acumatica support services guide](/blog/myob-acumatica-australia-7/myob-acumatica-support-australia-96) explains what a handover review involves and what you should expect from a support partner managing inherited custom code. ## **Frequently asked questions** ### **What's the difference between configuring and customising MYOB Acumatica?** Configuration uses the standard Acumatica toolset, including Generic Inquiries, Business Events, dashboards, workflow approvals, and user roles, to fit the platform to your business without writing code. Customisation uses the xRP development framework to extend or modify platform behaviour beyond what configuration can achieve. Configuration changes are safe across version upgrades; customisations require a compatibility review with each major release. ### **Can MYOB Acumatica integrate with our existing systems?** Yes. MYOB Acumatica's REST API provides a published, documented integration layer that connects with eCommerce platforms, third-party logistics systems, industry-specific tools, and custom portals. Most integration projects are scoped as API development engagements rather than platform customisations. The complexity and cost depends on what the external system can expose and how much business logic needs to sit on the Acumatica side. ### **Do customisations survive version upgrades?** Customisations built using the xRP platform's published API and documented patterns are designed to upgrade with the system rather than against it. In practice, each major version release requires a compatibility review and sometimes minor updates to custom code. Well-scoped, well-documented customisations typically require a few hours of work per upgrade cycle. Poorly documented or workaround-style builds can be significantly more expensive to maintain across versions. ### **How do I know if I need customisation or just better configuration?** The right starting point is a thorough review of your current configuration against your requirements. Generic Inquiries, Business Events, and configurable workflows cover more than most businesses realise. If you've had an implementation that didn't configure these tools well, what looks like a product limitation is often a configuration gap. A partner should always assess configuration options before recommending custom development. If you're being pushed toward custom code without that conversation happening, that's a signal to ask more questions. * * * **Evaluating MYOB Acumatica customisation for your business?** Auboros is an official MYOB Acumatica Partner based in Brisbane, supporting businesses across Queensland, NSW, and Victoria with implementation, configuration, and custom development. You can see the full range of our [MYOB Acumatica services](/solutions/myob) on our solutions page. We scope customisations honestly, which means telling you when the standard platform already does what you need. If you want to understand what's genuinely custom versus what's configuration, [**book a free consultation**](/appointment). We'll give you a straight answer on both. --- # MYOB Acumatica for Manufacturing in Australia: What the Platform Does and When It Fits - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-manufacturing-australia-116 - Category: MYOB Acumatica Australia - Published: 2026-04-05 - Description: What MYOB Acumatica's Manufacturing edition covers, the six production modes it supports, and how to tell whether it fits your Australian operation. Manufacturing businesses in Australia run on tight margins, complex production schedules, and supply chains that can unravel fast. The software holding all of that together needs to be more than an accounting system with a production tab bolted on. MYOB Acumatica's Manufacturing edition is built specifically for this, and it holds its own in a market with no shortage of ERP options. This post covers what the Manufacturing edition actually includes, how it connects to the rest of the platform, and how to tell whether it fits your operations. ## **What MYOB Acumatica's Manufacturing edition includes** ### **The six production modes and when each applies** MYOB Acumatica's manufacturing module supports six distinct production modes, which is where it separates from lighter ERP platforms. Each represents a different way of managing production, and selecting the right one determines how orders flow, how costs are calculated, and how your warehouse and finance modules interact with the production floor. - **Make-to-stock (MTS)** suits businesses producing standard goods to inventory levels based on demand forecasts. You manufacture first, sell from finished goods stock. - **Make-to-order (MTO)** is for businesses that don't produce until a customer order is confirmed. Production orders are driven by sales orders directly. - **Configure-to-order (CTO)** handles products with significant variation, where the customer selects specifications at order time and the bill of materials is generated from those choices. - **Assemble-to-order (ATO)** combines a base product from stock with customer-specific components. Common in light assembly environments. - **Batch process** is suited to industries like food, chemicals, and pharmaceuticals where production runs in lots rather than individual units. - **Project-based manufacturing** ties production orders to a project accounting record, relevant for custom fabricators, defence contractors, and businesses with long-run complex builds. The production mode decision shapes the entire implementation. Getting it wrong during scoping costs more in rework than the software itself. Many manufacturers use more than one mode across their product range, and Acumatica handles that within a single database. ### **Bill of materials, routings, and production orders** MYOB Acumatica's bill of materials (BOM) functionality supports multiple BOM versions per product, phantom assemblies (subassemblies that are consumed rather than stocked), and by-product tracking for manufacturing processes that generate secondary outputs alongside the primary product. Routings define the sequence of operations and work centres involved in making a product. MYOB Acumatica uses routings to calculate labour costs, machine time, and production lead times. When a production order is created, the system generates the operation schedule based on the routing and the available capacity of each work centre. ### **Material requirements planning** MRP in MYOB Acumatica calculates what materials you need, when you need them, and flags shortages before they cause production stoppages. It considers current stock levels, open purchase orders, confirmed production orders, and sales demand to generate purchase recommendations and production schedules. The 2026 release of MYOB Acumatica added a material availability view directly on the production order screen. You can now see whether materials are available before committing labour and machine time to a run. ## **What's new in the 2026 MYOB Acumatica Manufacturing release** The [2025-2026 release cycle](https://www.myob.com/au/insight/post/whats-new-2025-myob-acumatica-spring-release) brought several targeted improvements to the Manufacturing edition. The material availability view mentioned above is the most operationally useful. Due date tracking on production orders was updated to give shop floor supervisors clearer visibility into which orders are on schedule and which are at risk. Production scheduling improvements reduced the manual workarounds many businesses had built to handle capacity constraints across multiple work centres. MYOB Acumatica's 2026 releases are also introducing AI-assisted features across the platform, including anomaly detection and pattern monitoring relevant to production planning. These are early-stage at the time of writing but point toward the platform's direction. ## **How manufacturing connects to the rest of MYOB Acumatica** _"The production mode decision is the one that determines whether a manufacturing implementation succeeds or stalls. We see businesses come to us after a failed implementation elsewhere, and in most cases the original partner either chose the wrong mode or didn't recognise that the business needed more than one. Getting this right at scoping is non-negotiable."_ **Bill Alvarez, Practice Manager, Auboros** ### **Inventory, purchasing, and warehouse management** MYOB Acumatica's manufacturing module shares the same inventory database as its warehouse and purchasing modules. When a production order consumes materials, stock levels update in real time. When finished goods are completed and moved to the warehouse, they're immediately available for sale and shipment. Purchase recommendations generated by MRP flow directly into the purchasing module as purchase orders, which is one less place for manual entry and one less source of purchasing errors. Our post on [MYOB Acumatica for wholesale distribution](/blog/myob-acumatica-australia-7/myob-acumatica-wholesale-distribution-faststart-australia-103) covers the supply chain side of the platform in more detail. ### **Project accounting for make-to-order and custom work** For manufacturers doing custom work or long-run builds, MYOB Acumatica's project accounting module connects production costs, labour, materials, and overhead directly to a project record. This gives you job-level profitability reporting, progress billing against milestones, and the ability to track costs against budget throughout a production run rather than discovering overruns at job completion. ### **Finance, BAS, and GST for manufacturers** MYOB Acumatica's Australian localisation handles the compliance requirements that manufacturing businesses deal with, including [GST](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst) on raw material purchases, landed cost calculations for imported components, and Business Activity Statement (BAS) reporting that reflects both your purchasing and sales activity. The production cost journal entries flow to the general ledger automatically, so your financial statements reflect actual manufacturing costs without manual posting. For manufacturers using [MYOB Acumatica](/solutions/myob) and working with an implementation partner, the finance configuration is typically done in tandem with the production setup to ensure your costing method (standard cost or actual cost) matches your reporting requirements and how you manage variance analysis. ## **Is MYOB Acumatica the right fit for your manufacturing business?** MYOB Acumatica's manufacturing capability is designed for mid-market manufacturers, typically businesses with 20 to 500 employees that have outgrown spreadsheet-based production planning or lightweight accounting software with a production module added on. According to [MYOB's ERP Trends Report 2025](https://www.myob.com/au/insight/post/erp-trends), 45% of Australian decision-makers say disconnected systems limit their growth. For manufacturers, that disconnect usually shows up as stock figures that don't match production records, purchase decisions made without visibility of what's actually on the floor, and financial reporting that can't tell you which product lines are actually profitable. Where it's less likely to fit: very small manufacturers (under $5 million revenue) where the implementation cost is disproportionate to the complexity of operations, and large-scale process manufacturers with highly specialised requirements that need purpose-built process manufacturing software. For businesses in between, it's one of the strongest platforms in Australia for mid-market manufacturing. If you're in the construction sector rather than discrete manufacturing, our post on [MYOB Acumatica for construction in Queensland](/blog/myob-acumatica-australia-7/myob-acumatica-for-construction-in-queensland-job-costing-qbcc-compliance-and-what-s-included-105) covers that vertical specifically, including QBCC trust account requirements and job costing. ## **Frequently asked questions** ### **Does MYOB Acumatica support both discrete and process manufacturing?** Yes. MYOB Acumatica supports discrete manufacturing (individual units produced to a bill of materials and routing) and batch process manufacturing (runs producing lots rather than individual units, common in food, chemicals, and pharmaceuticals). The production mode you select determines how the system handles scheduling, costing, and lot tracking. Most manufacturers use one primary mode, but the platform supports multiple modes within a single database. ### **Can MYOB Acumatica handle multiple warehouses and locations?** Yes. MYOB Acumatica supports multi-warehouse and multi-location inventory, including warehouse transfers, location-level stock visibility, and zone picking. For manufacturers with raw material stores, work-in-progress areas, and finished goods warehouses as separate locations, the platform handles inter-location movements and provides location-level inventory reporting. ### **What does a MYOB Acumatica manufacturing implementation typically involve?** A MYOB Acumatica manufacturing implementation typically covers system configuration, BOM and routing setup, work centre configuration, MRP setup and testing, integration with purchasing and sales, data migration from your existing system, and staff training. Implementation timelines for a mid-size manufacturer are generally 16 to 24 weeks depending on the complexity of production modes and the number of integrations involved. Refer to the [implementation services guide](/blog/myob-acumatica-australia-7/choose-right-myob-acumatica-implementation-services-5) for more on what to look for in a partner. ### **How is MYOB Acumatica different from MYOB Exo for manufacturing?** MYOB Exo is an on-premise platform with limited manufacturing capability, primarily suited to distribution rather than production. MYOB Acumatica is a cloud-based platform with a dedicated Manufacturing edition supporting full MRP, production order management, and multi-mode production. MYOB Exo Payroll reached end of life in November 2025, which is prompting many Exo businesses to evaluate Acumatica as their next platform. * * * **Evaluating MYOB Acumatica for your manufacturing business?** Auboros is an official MYOB Acumatica Partner based in Brisbane, supporting manufacturing businesses across Queensland and nationally. We work through the production mode decision properly during scoping, which is where most manufacturing implementations either succeed or fail before they start. If you want to understand whether MYOB Acumatica is the right fit for your operations, [**book a free consultation**](/appointment). We'll walk through your production environment honestly and tell you what the implementation would actually involve. --- # MYOB Acumatica vs AccountRight: When You've Outgrown MYOB's Accounting Software - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-vs-accountright-australia-117 - Category: MYOB Acumatica Australia - Published: 2026-04-05 - Description: AccountRight Classic is gone and the platform gap is widening. What changes when you move to MYOB Acumatica, what it costs, and when upgrading makes sense. MYOB AccountRight and MYOB Acumatica are both MYOB products, but they're built for fundamentally different businesses. AccountRight is accounting software with some inventory and payroll capability bolted on. MYOB Acumatica is a full ERP platform built for organisations that need finance, operations, inventory, project accounting, and multi-entity management to work as one system. The question isn't which is better in absolute terms. It's which one fits where your business is right now, and whether you've grown past what AccountRight was designed to handle. According to [MYOB's Mid-Market Survey 2025](https://www.myob.com/au/insight/post/mid-market-survey-results-2025), 36% of Australian mid-sized businesses are actively looking to upgrade their ERP. This guide is for the ones asking whether Acumatica is the right next step. ## **What AccountRight does well, and where it stops** AccountRight is a solid product for small to mid-size businesses with straightforward accounting needs. Payroll, invoicing, bank reconciliation, BAS preparation, and basic inventory tracking all work well within its scope. It integrates with a wide range of third-party tools, most Australian accountants and bookkeepers know it, and the learning curve is manageable. It starts to struggle when your business outgrows its design assumptions. AccountRight is built around a single company file. Multi-entity reporting, inter-company transactions, and consolidated financials across related businesses require workarounds that become increasingly painful at scale. Its inventory module is functional for simple stock management but doesn't support manufacturing, complex warehouse operations, or real-time stock visibility across multiple locations. Reporting is largely limited to what's in the standard report library, and customising that requires exporting to spreadsheets. AccountRight Classic (version 19 and earlier) was [decommissioned by MYOB on 28 February 2026](https://www.myob.com/au/support/myob-business/product-account/accountright-classic-v19-and-earlier-decommission). If you were on Classic and have moved to AccountRight Live, you're now on the current platform, but the underlying design constraints of the product remain the same. ## **The signs you've outgrown AccountRight** ### **Volume and complexity are creating problems** AccountRight was not designed for high transaction volumes. As your sales, purchase orders, and inventory movements grow, you may notice slower performance, more frequent reconciliation errors, and month-end close processes that take longer than they should. When your accounting software starts to feel like it's working against your business rather than for it, that's a sign you've hit its ceiling. ### **You're running multiple entities or locations** If you operate more than one company, run projects across multiple cost centres, or manage inventory across multiple warehouses, AccountRight's single-file architecture requires you to maintain separate company files and manually consolidate reporting. This is time-consuming, error-prone, and gets worse as your entity structure grows. MYOB Acumatica handles multi-entity, multi-currency, and multi-warehouse natively in a single database. ### **Reporting requires too much manual work** When your standard financial reports don't answer the questions you need answered and you're spending hours each month exporting data to spreadsheets to build the picture, you've outgrown your accounting software's reporting capability. MYOB Acumatica includes configurable dashboards, generic inquiries (custom report builder), and real-time reporting that doesn't require exports. One case study cited by [MYOB's official comparison](https://www.myob.com/au/erp-software/alternatives/acumatica-vs-accountright) showed reporting cycles accelerating by 40 to 50% after the upgrade. ### **You need integrations AccountRight can't support** As businesses grow, they typically need their accounting system to connect to their eCommerce platform, their warehouse management system, their CRM, or their manufacturing operations. AccountRight's integration capability is limited compared to MYOB Acumatica's REST API and the ecosystem of certified connectors available for the Acumatica platform. ## **What MYOB Acumatica adds** ### **A full ERP across finance, operations, and inventory** MYOB Acumatica covers the full breadth of business operations in a single platform: accounts payable and receivable, general ledger, fixed assets, cash management, purchasing, sales orders, inventory, warehouse management, project accounting, payroll, and manufacturing. All of these modules share the same database, so financial data flows from operational transactions automatically rather than requiring manual entry or imports. ### **Multi-entity, multi-currency, and multi-warehouse natively** MYOB Acumatica is designed from the ground up for businesses with complex structures. Inter-company transactions post automatically with eliminations. Consolidated financial statements are generated without manual consolidation. Foreign currency transactions revalue at period end without manual journal entries. Warehouse transfers, stock visibility across locations, and location-level reporting are standard, not add-ons. ### **Real-time reporting you can configure** MYOB Acumatica's generic inquiry tool lets you build custom reports, dashboards, and pivot tables from any data in the system without exporting to Excel. Role-specific dashboards show each team member the KPIs relevant to their function. Report scheduling means the reports that matter most are sitting in your inbox each Monday rather than requiring someone to run them manually. ## **The honest case for staying on AccountRight** _"The clearest signal that a business is ready to move from AccountRight is when their month-end close starts taking more than two days. At that point, it's usually not an efficiency problem you can solve by working faster. It's a data architecture problem. AccountRight wasn't built to hold the complexity of what the business has become."_ **Josh Craig, Director, Auboros** Not every AccountRight user should upgrade to Acumatica. If your business has straightforward accounting needs, a single entity, limited inventory, and a small team, AccountRight Live is a capable, cost-effective platform and the upgrade to Acumatica is unlikely to justify the investment. MYOB Acumatica is mid-market software. The implementation cost, the licensing model, and the configuration complexity suit organisations with the operational scale to benefit from the full platform. Businesses under $5 million in revenue with simple operations will find Acumatica expensive relative to the problem it's solving. It's worth being clear about which category you're in before starting an evaluation. ## **What the upgrade process looks like** Moving from AccountRight to MYOB Acumatica is a full ERP implementation, not a file upgrade or data migration. Your chart of accounts, customer and supplier records, and historical transaction data need to be mapped, cleaned, and migrated into the new system. Your processes need to be configured in Acumatica. Your team needs training on a fundamentally different platform. The good news is that data migration from AccountRight is well-understood, and there are established migration tools and methodologies. The implementation timeline for a typical AccountRight-to-Acumatica upgrade is 12 to 20 weeks, depending on the complexity of your operations and the quality of your existing data. Our guide on [choosing the right MYOB Acumatica implementation services](/blog/myob-acumatica-australia-7/choose-right-myob-acumatica-implementation-services-5) covers what to look for in a partner and what questions to ask before you commit. For businesses evaluating this alongside other platforms, our [MYOB Acumatica consulting guide](/blog/myob-acumatica-australia-7/myob-acumatica-consulting-what-to-look-for-99) explains how the partner model works and what good partner support looks like. You can also see the full [MYOB Acumatica services](/solutions/myob) Auboros offers across implementation, customisation, and support. ## **Frequently asked questions** ### **Is MYOB AccountRight Classic still available?** No. MYOB decommissioned AccountRight Classic (version 19 and earlier) on 28 February 2026. If you were on Classic, you need to have migrated to AccountRight Live or another platform by that date. AccountRight Live is the current version of the product and remains available. MYOB has published official guidance on the decommission on their support pages. ### **Can I migrate my AccountRight data to MYOB Acumatica?** Yes. Customer records, supplier records, chart of accounts, and historical transactions can be migrated from AccountRight to MYOB Acumatica. The migration requires mapping and cleaning your data before import. Not all AccountRight data structures map directly to Acumatica equivalents, and some historical data is best brought across as opening balances rather than full transaction history. Your implementation partner manages this process. ### **What does upgrading from AccountRight to MYOB Acumatica cost?** Implementation costs depend on the scope of your migration, the number of modules involved, and the complexity of your operations. Scoping engagements for a typical AccountRight-to-Acumatica project start from $25,000, with full implementation costs for a mid-size business typically ranging from $50,000 to $150,000 or more for complex operations. MYOB Acumatica uses named user licensing with tiered access levels. For a scoped estimate specific to your business, the right starting point is a consultation with a certified MYOB Acumatica partner. ### **How long does an AccountRight to MYOB Acumatica implementation take?** A typical AccountRight-to-Acumatica implementation takes 12 to 20 weeks from project start to go-live. This includes requirements gathering, system configuration, data migration, user acceptance testing, training, and go-live support. Businesses with complex operations, multiple entities, or significant customisation requirements will sit at the higher end of that range. * * * **Thinking about upgrading from AccountRight to MYOB Acumatica?** Auboros is an official MYOB Acumatica Partner based in Brisbane, supporting businesses across Queensland, NSW, and Victoria through the transition from accounting software to full ERP. We work through the business case honestly before any implementation starts, and our [ERP migration guide](/solutions/erp-migration) covers what actually moves, what it costs, and the alternatives worth weighing. If you want to understand whether MYOB Acumatica is the right next step for your business, [**book a free consultation**](/appointment). We'll give you a straight answer, including if Acumatica isn't the right fit. --- # MYOB Acumatica vs NetSuite Australia: Which Mid-Market ERP Fits Your Business? - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-vs-netsuite-australia-111 - Category: MYOB Acumatica Australia - Published: 2026-04-05 - Description: MYOB Acumatica vs NetSuite for the Australian mid-market: pricing structures, local payroll and compliance, implementation timelines, and when each wins. If you're shortlisting cloud ERP platforms for a mid-market Australian business, MYOB Acumatica and NetSuite will almost certainly both come up. They target a similar size of organisation, both are cloud-native, and both are serious platforms with a strong local presence. The decision comes down to your specific situation rather than a generic winner. This post lays out the real differences, including where each platform is stronger, so you can make an informed call. ## **MYOB Acumatica vs NetSuite: who they're built for** MYOB Acumatica (formerly MYOB Advanced, rebranded in 2024) is designed specifically for mid-sized Australian and New Zealand businesses. The sweet spot is organisations with 20 to a few hundred employees that need more than accounting software but don't have the complexity or budget of a large enterprise implementation. It's built by an ANZ-first company, which means local compliance is baked in rather than configured on top. NetSuite, owned by Oracle, is a global platform with strong international capabilities. It fits businesses that are scaling rapidly, have multiple subsidiaries, or operate across multiple countries. In Australia, it's often used by businesses in the $50M to $500M revenue range that have outgrown mid-market platforms or need the multi-entity consolidation that NetSuite handles well. According to [MYOB's own comparison](https://www.myob.com/au/erp-software/alternatives/acumatica-vs-netsuite), MYOB Acumatica is the more appropriate choice for most ANZ mid-market businesses, particularly those where local compliance is the primary concern. That's a fair representation, with the caveat that it comes from MYOB's own marketing. The full picture is more nuanced. ## **Pricing: how each platform licences users** MYOB Acumatica is priced per user, with licence costs tied to job function and level of access. There are three main licence tiers: Full Users (complete system access across all modules), Limited Users (module-specific access, typically priced at around 50 to 67% of a Full User licence), and Portal Users (external access for customers or vendors, typically 25 to 67% of a Full User licence). Pricing also varies by edition: Plus, Enterprise, and Manufacturing editions each carry different per-user rates, with indicative per-user costs starting from around $215/month for the Plus Edition and $271/month for Enterprise. Actual pricing is negotiated through MYOB and its channel partners. Because most businesses have a mix of user types (not everyone needs full system access), the per-user, job-function model can be cost-effective compared to platforms that charge a flat rate regardless of what a user actually does. NetSuite also uses per-user pricing, with a base platform fee on top. Based on [Capterra's current listings](https://www.capterra.com.au/software/135757/netsuite), NetSuite's base platform fee starts around $999 USD per month, with per-user costs varying by access tier. NetSuite negotiates pricing and published rates are a starting point rather than a final figure. First-year total costs for a mid-market implementation typically land in the $50,000 to $200,000 AUD range including services. Neither platform publishes a full price list publicly. The right comparison is a scoped quote from a partner who knows your user mix, transaction volumes, and required modules. For MYOB Acumatica specifically, the access tier breakdown means the quote can vary significantly depending on how many Full versus Limited or Portal Users your business needs. ## **Australian compliance: built-in vs localised** MYOB Acumatica includes GST (Goods and Services Tax), Single Touch Payroll (STP) Phase 2, Business Activity Statement (BAS) reporting, and ATO compliance as core platform features rather than add-ons. These are maintained by MYOB as the platform vendor, which means compliance updates roll out with regular product releases. For more detail on current [MYOB Acumatica payroll compliance requirements](/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97) including the 1 July 2026 Payday Super changes, we've covered this in a separate post. NetSuite does support Australian GST and BAS, but the localisation is configured rather than native. Depending on your partner and the complexity of your requirements, this configuration adds to implementation time and cost. Support for changes to ATO compliance rules, such as the STP Phase 2 expansion, typically comes through partner-maintained configurations rather than out-of-the-box platform updates. This isn't necessarily a dealbreaker, but it's worth factoring into your implementation timeline and ongoing support model. For businesses dealing with ATO-specific requirements, the [ATO's guidance on GST](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst) is the authoritative source, and both platforms ultimately need to meet those requirements. The question is how much configuration work your implementation team needs to do upfront. ## **Implementation: timeline and complexity** MYOB Acumatica implementations for a standard mid-market business typically run three to six months for a full go-live, depending on scope. The platform's low-code customisation tools mean that common configuration changes, custom workflows, specific report formats, can be handled without developer-level intervention. This reduces the cost and time of getting the system to fit your processes. NetSuite implementations tend to run longer and require more consultant hours, particularly when localisation, custom fields, or integrations are involved. In our experience, NetSuite implementations often demand extensive consulting and custom configuration, leading to higher upfront costs. NetSuite implementations that are complex or poorly scoped can stretch to twelve months or more. The partner ecosystem for both platforms in Australia is mature. For MYOB Acumatica, [Auboros is an official MYOB Acumatica partner](/solutions/myob) and can provide implementation, customisation, and ongoing support across Queensland, New South Wales, and Victoria. For the wholesale distribution sector specifically, we also deliver fast start implementations for wholesale verticals. ## **Where NetSuite wins (and we'll be direct about it)** NetSuite has real advantages in several areas. Pretending otherwise doesn't help anyone make a good decision. Multi-entity consolidation is the clearest one. If you have multiple legal entities, intercompany transactions, or subsidiaries across different countries, NetSuite handles this natively. MYOB Acumatica is a domestic-first platform. Businesses with genuine international complexity will hit its limits. The global partner ecosystem is also larger. NetSuite has more third-party integrations in international markets and a bigger developer community. If your integration requirements extend well beyond ANZ, the NetSuite ecosystem gives you more to work with. Reporting is another area where larger organisations tend to favour NetSuite. The SuiteAnalytics platform is flexible and well-regarded by finance teams managing complex consolidations. If your CFO is running a global P&L with multiple currencies, that matters. _"Both platforms are legitimate choices, and any honest consultant should tell you that. Where we see MYOB Acumatica win consistently is with Australian businesses in the 20 to 200 employee range that need strong local compliance, predictable costs, and a faster path to go-live. NetSuite tends to make more sense when there's genuine international complexity or multi-entity structure that MYOB Acumatica struggles with. The wrong choice is picking one because of brand familiarity or a salesperson's pitch without doing the comparison."_ **Josh Craig, Director, Auboros** ## **Which businesses should choose each platform?** MYOB Acumatica suits Australian or New Zealand businesses in the 20 to 300 employee range with domestic operations, where built-in GST and BAS compliance matters and where predictable licence costs are a priority. Wholesale distribution, professional services, not-for-profit, and construction are industries where we've seen it work well in the Australian market. NetSuite is more appropriate if you have international operations, multiple legal entities that need consolidation, or you're on a growth path toward a public listing or acquisition. It's also worth considering if you're already in the Oracle ecosystem, where commercial bundling can offset some of the higher licence cost. According to the [MYOB ERP Trends Report 2025](https://www.myob.com/au/insight/post/erp-trends), 36% of Australian mid-sized businesses are looking to upgrade their ERP, with operational efficiency cited as the primary driver by 48% of respondents. For most of those businesses, the comparison starts with fit for purpose and cost, not brand. A proper scoping exercise with both vendors, or a partner who can represent both platforms, is the right process before signing anything. If you're comparing these platforms and want to understand how the [Odoo vs NetSuite comparison](/blog/odoo-erp-australia-6/odoo-vs-netsuite-australia-2026-erp-comparison-90) fits into the picture, we've covered that separately for businesses considering all three options. ## **Frequently asked questions** ### **Is MYOB Acumatica the same as MYOB Advanced?** Yes. MYOB Advanced was rebranded as MYOB Acumatica in 2024. It's the same platform, built on the Acumatica cloud ERP engine and distributed by MYOB for the Australian and New Zealand market. If you see references to MYOB Advanced in older content, it refers to the same product now called MYOB Acumatica. ### **How does MYOB Acumatica licensing work?** MYOB Acumatica uses per-user licensing with costs tied to job function and access level. The three main licence tiers are Full Users (complete system access), Limited Users (module-specific access, typically 50 to 67% of the Full User rate), and Portal Users (for customer or vendor access, typically 25 to 67% of the Full User rate). Pricing also varies by edition (Plus, Enterprise, or Manufacturing), which affects the per-user rate. Most businesses require a mix of licence types rather than full licences for everyone, so your partner will scope the right user mix as part of the quoting process. ### **How long does a MYOB Acumatica implementation take?** Most standard mid-market implementations run three to six months from project kick-off to go-live. Scope, data migration complexity, and customisation requirements are the main variables. Businesses that go through a structured requirements process before implementation tend to stay within budget and timeline more reliably. Our post on [choosing the right MYOB Acumatica implementation services](/blog/myob-acumatica-australia-7/choose-right-myob-acumatica-implementation-services-5) covers what to look for in a partner. ### **Does NetSuite support Australian GST and BAS?** NetSuite supports Australian GST and can be configured for BAS reporting, but this requires localisation work during implementation rather than being a standard out-of-the-box feature. The configuration is handled by your implementation partner. For Australian businesses where compliance simplicity is a priority, MYOB Acumatica's native compliance features typically reduce the implementation work required in this area. ### **Can an Australian business run both MYOB Acumatica and NetSuite?** You can, but there's rarely a good reason to. Businesses occasionally end up with both platforms due to acquisitions or legacy decisions, and integration between them is possible but adds cost and complexity. If you're evaluating fresh, pick one. If you've inherited a dual-platform situation and want to rationalise, that's a worthwhile scoping exercise before your next renewal cycle. * * * **Evaluating MYOB Acumatica for your business?** Auboros is an official MYOB Acumatica partner serving businesses across Queensland, New South Wales, and Victoria. We can walk you through a detailed comparison based on your specific requirements, not a generic product pitch. Our [NetSuite alternatives guide](/compare/netsuite-alternative-australia) sets out the wider shortlist for Australian mid-market businesses. If you're in the evaluation stage, [**book a free consultation**](/appointment). Bring your shortlist and your questions. --- # Odoo vs SAP Business One Australia: Which ERP Fits Mid-Market Businesses? - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-vs-sap-business-one-australia-108 - Category: Odoo ERP Australia - Published: 2026-03-31 - Description: Odoo and SAP Business One both target Australian mid-market businesses. An honest comparison of pricing, implementation, and which ERP fits your situation. If you’re evaluating ERP for a business somewhere between $5 million and $50 million in annual revenue, you’ve probably landed on two names: Odoo and SAP Business One. They’re both sold as mid-market platforms. They both have real-world implementations behind them. But they’re built on very different philosophies, and choosing the wrong one can cost you years of frustration and a budget you won’t easily recover. This comparison comes from a consultancy that implements Odoo as a certified Silver partner and has scoped projects alongside SAP Business One for businesses across Queensland and NSW. We’re not trying to sell you Odoo. We’re trying to help you work out which platform actually fits your situation. ## **Two different takes on what mid-market ERP means** SAP Business One has been around since 2002 and carries SAP’s DNA: structured, process-centric, and built around the assumption that your business runs standard processes and wants a system that enforces them. It works particularly well for wholesale distribution, light manufacturing, and businesses with well-defined workflows that want a globally supported platform to run them. Odoo grew from an open-source project into a modular ERP platform covering CRM, inventory, manufacturing, accounting, field service, project management, and more. The philosophy is flexibility: you start with what you need and add modules as the business grows. That modularity is its strength and the reason it requires more upfront configuration work than a more prescriptive system like SAP B1. Neither platform is categorically “better.” The right choice depends on how your business operates today and where you’re headed. ## **How the pricing compares in Australia** SAP Business One is licensed on a per-user model. Cloud subscription pricing in Australia varies by partner and user type, but publicly available partner pricing typically places Professional users in the range of AU$150-200+ per user per month. For a 15-user team, that’s roughly $2,250-3,000 per month in licensing before implementation, support, or customisation costs. You can view user reviews and pricing context on [Capterra Australia’s SAP Business One page](https://www.capterra.com.au/software/1010597/sap-business-one). Odoo Enterprise pricing depends on user count and which modules you activate. For a mid-sized Australian business using the full suite, annual licensing is generally lower than SAP B1 at an equivalent user count. See our [Odoo implementation packages page](/odoo-implementation-packages-for-australian-businesses) for indicative Australian pricing. Implementation cost tells a different story. SAP B1 implementations in Australia typically start from $50,000 and run to $150,000 or more for businesses with complex requirements. Odoo implementations vary similarly depending on scope, but the modular approach means you can genuinely start smaller and expand. A focused Odoo project covering core financials, inventory, and sales for a 10-15 user business can often be completed for less than an equivalent SAP B1 engagement. ## **Implementation timeline and what to expect** SAP Business One implementations typically run three to eight months for a mid-market Australian business. The structured approach means less discovery time upfront, but it also means more change management, because the system assumes you’ll adapt your processes to match its workflows rather than the other way around. Odoo timelines vary more widely, which is one of the arguments against choosing it without careful scoping. A well-scoped Odoo project for 10-20 users can go live in eight to twelve weeks. A poorly-scoped project with heavy customisation can run much longer. The most important question to ask any Odoo partner before signing: what’s in scope, what’s out of scope, and what does the fixed-price implementation actually include? For more on this, see our post on [how long Odoo implementations take in Australia](/blog/odoo-erp-australia-6/how-long-does-an-odoo-implementation-take-in-australia-93). ## **Australian compliance: BAS, STP, and GST** Both platforms handle the core Australian compliance requirements. Odoo’s [Australian localisation](/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98) covers Business Activity Statement (BAS) reporting, Single Touch Payroll (STP) Phase 2, and the 10% GST rate, maintained and updated across each major version. SAP Business One has similarly mature Australian localisation, developed through its network of certified local partners. For businesses with more complex compliance requirements, such as multi-entity GST grouping, project-based BAS reconciliation, or eInvoicing to government clients under the Peppol framework, both platforms can be configured to handle these with appropriate partner support. The [ATO’s guidance for Australian businesses](https://www.ato.gov.au/businesses-and-organisations/not-for-profit-organisations/getting-started) applies equally regardless of which platform you run. ## **Where Odoo tends to work better** Odoo fits best when a business values flexibility over standardisation. If you’re in a growth phase and expect your processes to change, its modular architecture makes it easier to add capability without a full system overhaul. The CRM-Sales-Inventory-Accounting integration is genuinely unified in a way that’s difficult to replicate through bolt-on connectors with more structured systems. eCommerce businesses, field service companies, and manufacturers who want to run sales, production, and dispatch from a single system tend to find Odoo’s breadth useful. Our [Odoo services page](/solutions/odoo) covers the modules we implement most frequently for Australian businesses. ## **Where SAP Business One tends to work better** SAP B1 is the stronger choice for businesses with stable, well-defined processes that want a system to enforce structure rather than accommodate exceptions. Companies with complex multi-currency requirements, strong financial reporting needs, or operations that align closely with SAP’s standard manufacturing and distribution workflows tend to get good value from it. SAP also carries reputational weight that matters for some organisations, particularly those with international parent companies, enterprise supply chain partners, or audit requirements that specify recognised ERP platforms. For those businesses, SAP B1’s brand recognition is a genuine consideration, not just brand preference. _“Most clients who were comparing Odoo and SAP Business One came to us because an accountant or advisor mentioned SAP. When we mapped their actual processes against both platforms, Odoo covered what they needed at a lower total cost in the majority of cases. But for a small number of clients with structured manufacturing or complex multi-currency distribution, SAP B1 genuinely was the better recommendation, even though we don’t implement it. Telling a client that is how you build trust.”_ **Josh Craig, Director, Auboros** ## **Frequently asked questions** ### **Can I migrate from SAP Business One to Odoo in Australia?** Yes. The process involves exporting master data (customers, suppliers, products, chart of accounts), mapping that data to Odoo’s structure, migrating open transactions, and validating before go-live. Historical transaction data is typically left in SAP B1 for reference access rather than fully migrated. For a mid-sized business, plan for a six to ten week migration process. ### **Does SAP Business One have a good partner network in Australia?** Yes. SAP has an established partner network in Australia with certified implementers across Brisbane, Sydney, and Melbourne. For Australian implementations, look specifically for partners with experience in local compliance requirements including BAS reporting and STP Phase 2. ### **Is Odoo’s open-source background a concern for enterprise buyers?** Odoo Enterprise is a fully commercial product with paid support, a structured upgrade pathway, and access to Odoo SA’s development roadmap. The open-source Community version exists separately. Most Australian businesses implement Odoo Enterprise to access the Australian localisation, Odoo’s direct support, and hosted deployment options. The open-source aspect is more relevant to developers than business buyers evaluating the platform. ### **Which ERP is better for a Brisbane or Queensland-based manufacturer?** For most Queensland manufacturers in the $5-30 million revenue range, Odoo Enterprise covers the requirements: multi-site inventory, manufacturing work orders, BOM management, purchasing, and accounting in one system. SAP Business One is more appropriate for manufacturers with complex discrete manufacturing processes, strong MRP requirements, or international production operations. The honest answer is that the right fit depends on the specific manufacturing model, not geography. ### **What’s the realistic five-year total cost of ownership for each?** For a 15-user Australian mid-market business, Odoo Enterprise typically has a lower five-year total cost of ownership than SAP Business One when you include licensing, implementation, support, and upgrades. The gap narrows significantly for Odoo projects with heavy customisation, where consulting costs can exceed the licensing savings. Both have ongoing annual costs: Odoo annual subscription and SAP B1 annual maintenance fees. * * * **Evaluating Odoo for your Australian business?** We’re a certified Odoo Silver Partner based in Brisbane, and we implement Odoo for businesses across Queensland, NSW, and Victoria. If you’re comparing ERP platforms and want a practical, no-pressure view of what each option means for your situation, we’re happy to work through it. If you’d like an honest assessment of which ERP fits your business, [**book a free consultation**](/appointment). We’ll tell you if Odoo isn’t the right fit. --- # MYOB Acumatica for Not-for-Profit Organisations in Australia: What It Does and When It Fits - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-not-for-profit-australia-109 - Category: MYOB Acumatica Australia - Published: 2026-03-31 - Description: MYOB Acumatica handles fund accounting, grant management, and ACNC compliance for Australian NFPs. An honest look at what it covers and when it’s a good fit. Running finance in a not-for-profit organisation is not a simplified version of running finance in a commercial business. It’s more complex in specific ways: fund accounting, restricted grant spending, acquittal reporting to funding bodies, mixed GST treatment, ACNC annual reporting obligations, and workforce costs spread across programs rather than profit centres. Standard accounting software handles some of this. Mid-market ERP like MYOB Acumatica is built to handle all of it. Australia has more than 600,000 not-for-profit organisations, with [52,627 charities registered with the Australian Charities and Not-for-profits Commission (ACNC)](https://www.acnc.gov.au/tools/reports/australian-charities-report-11th-edition) as of the most recent national charities report. The sector employs around 10.7% of the Australian workforce and generates revenue approaching $240 billion annually. These are not small organisations running on spreadsheets. The bigger ones need enterprise-grade financial management to stay compliant and accountable. What follows is what MYOB Acumatica actually offers NFPs and charities in Australia, where it genuinely solves the problem, and where spending $80,000 on an ERP implementation when you need a $15,000 accounting upgrade would be the wrong call. ## **What makes NFP financial management different** The core difference between NFP and commercial accounting is fund accounting. A commercial business tracks profit and loss for the whole entity. An NFP tracks income and expenditure across multiple funds, programs, or cost centres, often with different rules for each. Government grants come with acquittal obligations. Philanthropic donations may be restricted to specific uses. NDIS funding streams require granular cost allocation. ATO concessions including income tax exemption, GST concessions, and FBT concessions apply differently depending on how the [ATO classifies your organisation](https://www.ato.gov.au/businesses-and-organisations/not-for-profit-organisations/getting-started/starting-an-nfp). Getting this wrong is not a minor accounting issue. It’s an ACNC compliance issue. Charities registered with the ACNC must submit an Annual Information Statement each year with financial data broken down to a level that standard accounting software does not easily produce. MYOB Acumatica is designed to make that reporting a byproduct of normal operations rather than a manual exercise every June. ## **Core financial management features for Australian NFPs** MYOB Acumatica’s general ledger supports multi-dimensional chart of accounts, which is the foundation of fund accounting. You can structure your accounts to segment by program, funding source, geographic area, or any combination that matches how your funding bodies require you to report. Budgets are set at the program or fund level, not just the entity level, so you can track whether a government-funded program is on track for acquittal without manual spreadsheet reconciliation. GST treatment for NFPs is more complex than for commercial businesses. Charitable activities may be GST-exempt, input-taxed, or GST-free depending on the nature of the activity and the organisation’s registration status. MYOB Acumatica handles mixed GST treatment across transactions, which reduces the manual adjustment work at BAS time. For organisations dealing with multiple grant streams under different GST rules, this is a material time saving. Accounts payable and receivable work in the standard mid-market ERP way, but with the added ability to tag every transaction to a program or fund. That tagging is what makes acquittal reporting practical: you can pull a report showing all spending against a specific grant reference without manually sorting through a chart of accounts that wasn’t designed for this purpose. ## **Grant management and program accounting** Grant management in MYOB Acumatica sits within the project accounting module. Each grant is set up as a project with its own budget, funding period, allowable expenditure categories, and reporting milestones. Labour costs can be allocated to specific programs based on timesheets, which is often a condition of acquittal to government funding bodies. For organisations running multiple programs at once, the practical benefit is time. Instead of maintaining parallel spreadsheets to reconcile what’s been spent from each funding stream, program managers see their budget status in real time. The finance team pulls acquittal reports directly from the system rather than building them from scratch when the funding period closes. That’s the most common reason Australian NFPs contact us about MYOB Acumatica: grant management has grown beyond what MYOB AccountRight can handle. If you have more than three or four active grant streams with acquittal obligations, the manual work in standard accounting software starts consuming finance team hours that could go elsewhere. ## **Workforce management for NFP organisations** NFPs often have a mix of paid staff, part-time employees, casuals, and volunteers. MYOB Acumatica’s workforce module handles rostering, timesheets, leave management, payroll, and single touch payroll (STP) reporting to the ATO. The [Payday Super changes effective 1 July 2026](/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97) apply to NFP payroll just as they do to commercial businesses, and MYOB Acumatica handles this within the same system as your program accounting. Volunteer management sits in the CRM module: a configurable database for volunteer records, availability, skills, and contact history. For organisations that depend on large volunteer workforces, having that data in the same system as your operational records avoids the fragmentation that comes with maintaining separate volunteer databases. ## **ACNC compliance and financial reporting** Registered charities must submit Annual Information Statements to the [ACNC](https://www.acnc.gov.au/) each year. The financial components of that statement require revenue, expenditure, and asset data in a format that maps to the ACNC’s reporting categories. MYOB Acumatica’s reporting engine can be configured to produce financial summaries that align with these categories, which reduces the end-of-year mapping work your finance team would otherwise do manually. Organisations with Deductible Gift Recipient (DGR) status have additional obligations around how donation income is tracked and reported. The system supports the level of transaction tagging and audit trail required to demonstrate compliance with DGR conditions under ATO review. _“NFPs and charities are usually surprised by how much time their finance teams spend on manual reconciliation when they’re running on standard accounting software. When you have five or six different grant streams, each with its own acquittal format, that work compounds every quarter. MYOB Acumatica solves this by making program-level reporting a byproduct of day-to-day data entry rather than a separate exercise.”_ **Bill Alvarez, Practice Manager, Auboros** ## **When MYOB Acumatica is the right fit for an NFP** MYOB Acumatica is designed for organisations with at least 20 employees. For Australian NFPs, the platform becomes a strong fit when the organisation has multiple active grant streams requiring acquittal reporting, a payroll of 15 or more staff, complex program accounting requirements, or NDIS service delivery that requires cost allocation at the support item level. It’s also worth considering if your organisation has outgrown MYOB AccountRight. The transition from AccountRight to Acumatica is a supported migration path, and the two products share enough DNA that finance teams make the move without a complete retraining exercise. Our post on [MYOB Acumatica for membership organisations](/blog/myob-acumatica-australia-7/myob-acumatica-for-membership-organisations-australia-92) covers similar ground for peak bodies and associations that share some of the same compliance requirements. ## **When simpler software might be enough** Not every NFP needs MYOB Acumatica. If your organisation has a single funding stream, a small team, and no complex program reporting requirements, MYOB AccountRight or even Xero with appropriate add-ons may cover everything you need at a lower cost and with less implementation effort. MYOB Acumatica is mid-market ERP, and it carries mid-market ERP complexity and cost. The investment makes sense when the organisation has genuinely outgrown simpler tools. The eInvoicing mandate from the ATO is also relevant for NFPs that supply to government. If your organisation invoices government agencies, [MYOB Acumatica’s eInvoicing capability](/blog/myob-acumatica-australia-7/myob-acumatica-einvoicing-australia-2026-107) and Peppol connectivity may be relevant ahead of the July 2026 compliance deadlines. ## **Frequently asked questions** ### **Does MYOB Acumatica handle NDIS billing and support item tracking?** MYOB Acumatica can be configured to track service delivery against NDIS support items, with cost allocation to individual participants and funding streams. Implementation partners with NDIS experience typically set up a project accounting structure that maps to the NDIS price guide categories. This is a customisation-assisted setup rather than an out-of-the-box NDIS module, so confirm the scope of this work with your implementation partner during the sales process. ### **Can MYOB Acumatica produce ACNC Annual Information Statement reports?** MYOB Acumatica’s reporting module can be configured to produce financial summaries that align with the ACNC’s reporting categories. This requires the chart of accounts and program structure to be set up correctly at implementation. Done well, the system produces the data your finance team needs to complete the Annual Information Statement without manual reworking. ### **How does MYOB Acumatica handle mixed GST for charitable activities?** MYOB Acumatica supports mixed GST tax codes within transactions, which allows it to handle the GST-exempt, GST-free, and input-taxed activity distinctions that apply to registered charities. Your BAS preparation should reflect the correct GST treatment across all activity types without manual adjustments, provided the tax codes are mapped correctly during implementation. Check with the [ATO’s NFP guidance](https://www.ato.gov.au/businesses-and-organisations/not-for-profit-organisations/getting-started) for your specific organisation type and activity classification. ### **What’s a realistic MYOB Acumatica implementation timeline for an NFP?** For a not-for-profit with five to eight active programs and 20-40 staff, a typical MYOB Acumatica implementation runs twelve to sixteen weeks. Complex grant management configurations, NDIS integration, or data migration from legacy systems can extend this. A phased approach, going live with core financials first and adding payroll and project accounting in subsequent phases, is common and generally reduces implementation risk. ### **Is there NFP pricing available for MYOB Acumatica in Australia?** MYOB does not publish a standard NFP discount for Acumatica, but some not-for-profit pricing arrangements are available through implementation partners depending on the organisation’s size and situation. Contact MYOB or an official MYOB Acumatica partner for current pricing relevant to your organisation. * * * **Managing grants, programs, and ACNC compliance in Queensland or NSW?** We’re a Brisbane-based [MYOB Acumatica implementation partner](/solutions/myob) with experience implementing the platform for NFPs and service organisations across Queensland. If your current accounting software is creating manual work around grant acquittal or program reporting, it’s worth a conversation about whether MYOB Acumatica is the right step up. If you’d like to discuss your organisation’s situation, [**book a free consultation**](/appointment). We’ll give you an honest view of whether MYOB Acumatica fits. --- # Odoo CRM Australia: What It Does, What It Doesn't, and When It Makes Sense - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-crm-australia-features-guide-104 - Category: Odoo ERP Australia - Published: 2026-03-24 - Description: Odoo CRM connects pipeline management, quoting and customer history in one platform. Here's what it covers and when it makes sense for Australian businesses. A lot of businesses reach Odoo through the CRM. They're outgrowing a spreadsheet, or paying more than they'd like for Salesforce, and someone mentions Odoo does it for a fraction of the price. That's true. But the more important question isn't "is Odoo CRM cheap?" It's "does it actually fit the way our sales team works, and does it connect to the rest of our business?" This guide answers that honestly. We'll cover what Odoo CRM does well, where it falls short, and when it makes sense to use it instead of a standalone CRM. ## **What Odoo CRM actually covers** Odoo CRM is a full-featured pipeline tool. You get a Kanban board where opportunities move through stages, drag-and-drop between columns, customisable stages per sales team, and activity scheduling attached to each opportunity. Every call, email, note and meeting logs against the record so your team has full context without digging through inboxes. Lead management is solid. You can capture leads from a website form, a live chat conversation, an email alias, or a manual import. Duplicate detection runs automatically. You can score leads using rules, assign them to reps based on territory or round-robin logic, and nurture them with automated email sequences before they're ready to hand off to sales. Reporting covers the basics well: pipeline value by stage, expected revenue by rep, lead source analysis, activity completion rates, and won/lost analysis. For most SMEs this is more than enough. If you want something more granular, Odoo's built-in dashboards let you build custom views with filters and groupings. What separates Odoo CRM from a standalone tool is the integration with everything else. A qualified opportunity converts into a quote in one click, using live pricing from your product catalogue. The quote becomes a sales order, which triggers inventory, which feeds into invoicing. The [Odoo CRM documentation](https://www.odoo.com/documentation/19.0/applications/sales/crm.html) outlines how this workflow connects across modules, and in practice it means your sales team isn't re-entering data that operations already has. ## **Where the value compounds for Australian businesses** The practical benefit for Australian businesses is what happens after the deal is won. When CRM, Sales, Inventory and Accounting are in the same platform, a confirmed opportunity automatically updates expected revenue in your forecast, and when a quote is confirmed, your invoicing queue reflects it. There's no hand-off delay between sales and finance. For businesses that issue GST-registered tax invoices, that path from CRM to invoice matters. The quote that goes out from Odoo is already pulling the right GST treatment from your chart of accounts. You're not reconciling between a CRM and your [ATO-compliant](https://www.ato.gov.au/businesses-and-organisations/gst) accounting system after the fact. According to a [MYOB ERP Trends report](https://myob.com/au/insight/post/erp-trends), 45% of Australian decision-makers say disconnected systems limit their ability to grow. Odoo CRM addresses that directly, not by being the best standalone CRM on the market, but by being genuinely connected to the rest of your operation. _"The CRM question we hear most often isn't about features, it's about whether sales data actually reaches the people who need it. When your CRM and your ERP are the same system, that problem disappears. No exports, no integrations to maintain, no version of the truth sitting in a spreadsheet somewhere."_ **Bill Alvarez, Practice Manager, Auboros** ## **How Odoo CRM compares to Salesforce for Australian SMEs** Salesforce is a genuinely strong CRM. Its reporting depth, third-party integrations and ecosystem of add-ons are hard to match. If your business runs mostly on sales activity and the deal itself is the end of the process, Salesforce does that well. For businesses with a large sales team and complex sales processes, it's worth the investment. Odoo CRM makes more sense when the deal is the start of your workflow, not the end. If winning a job triggers a work order, a purchase order, a project, or a delivery, Odoo keeps all of that inside one system. [Odoo's own comparison page](https://www.odoo.com/page/odoo-vs-salesforce-crm) makes the pricing point clearly: Salesforce Professional Edition runs approximately USD $75/user/month, while Odoo Enterprise includes CRM plus every other module for a single per-user fee. For a 10-person business, the cost difference over three years is significant. Salesforce holds an edge in deeply customised sales processes, large enterprise deployments, and organisations already running Salesforce Service Cloud or Marketing Cloud. Odoo makes more sense when CRM needs to sit alongside inventory, accounting, project management, or field service without a custom integration sitting in the middle. ## **What you should know before implementing Odoo CRM** Odoo CRM is not complex to use. The pipeline interface is intuitive and most sales reps pick it up quickly. The configuration is where you'll spend time: deciding how many stages you need, what the lead scoring rules should be, which teams get which views, and how automated email sequences should work. If you're implementing Odoo CRM as part of a wider Odoo rollout, that configuration happens once and feeds the rest of the system. If you're adding CRM to an existing Odoo database, the upgrade path is clean because it's the same codebase. You're not integrating two platforms; you're activating an additional module. One thing worth managing early: the distinction between a Lead and an Opportunity in Odoo. By default, incoming enquiries land as Leads and your team qualifies them into Opportunities before they enter the pipeline. That distinction is worth thinking through before go-live, because it affects your reporting baseline. Capterra research found that [fewer than one in three Australian businesses successfully adopt new software](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/) without significant disruption. Most of the failures come down to unclear requirements and poor data migration, not the software itself. Getting your existing contact data clean before you go live matters more than which CRM you choose. If you're currently using Xero and wondering whether adding Odoo CRM means you'd need to move your accounting too, it's worth reading our guide on [when to upgrade from Xero to an ERP](/blog/odoo-erp-australia-6/odoo-vs-xero-when-to-upgrade-from-accounting-to-erp-in-australia-91). The short answer is: you don't always have to do both at once. ## **Odoo CRM for field service and project-based businesses** For businesses in trades, construction, or professional services, Odoo CRM connects directly to the Field Service and Project modules. A won opportunity can trigger a service request, create a project task, or schedule a job automatically. This is particularly useful for businesses where the sales team and the delivery team are different people who currently communicate by email or phone. Auboros works with a number of field service businesses in Queensland and NSW through our [Odoo Field Service practice](/solutions/odoo-field-service-australia-nz). The CRM-to-service workflow is one of the most common use cases we set up, and it's where the joined-up architecture pays for itself quickly. ## **Frequently asked questions about Odoo CRM in Australia** ### **Does Odoo CRM work for Australian tax invoices and GST?** Yes. Quotes and sales orders generated from Odoo CRM pull GST treatment directly from your product and accounting configuration. When a quote is accepted, the resulting invoice is already correctly formatted for Australian tax requirements. You don't need a separate invoicing tool. ### **Can Odoo CRM integrate with my existing email?** Odoo CRM works with any IMAP-compatible email system, including Google Workspace and Microsoft 365. Emails to a configured alias automatically create leads, and all replies from Odoo appear in the customer's record. Your team can keep working from their inbox while activity logs in the CRM in the background. ### **Do I need the full Odoo ERP to use the CRM module?** No, but the value of Odoo CRM is strongest when it's connected to Sales and Accounting. You can use CRM with a minimal Odoo setup, but if you're running inventory or finance in a separate system, you'll need an integration to get the quote-to-invoice workflow working. For most businesses, starting with CRM plus Sales and Invoicing gives you the most practical starting point. ### **How long does it take to set up Odoo CRM for a small Australian business?** A basic CRM configuration, including pipeline stages, email integration, lead assignment rules, and user setup, can be done in two to four days for a straightforward deployment. Our [Odoo implementation packages](/odoo-implementation-packages-for-australian-businesses) cover this in detail if you want to understand what's included at each level. ### **Is Odoo CRM Community or Enterprise better for Australian businesses?** Community Edition includes basic CRM functionality. Enterprise adds predictive lead scoring, email marketing automation, a more advanced activity management interface, and full reporting. For most businesses using CRM seriously, Enterprise is worth the cost. Community works for simple pipelines where your main need is a shared contact list and basic stage tracking. * * * **Thinking about Odoo CRM for your business?** We're an [Odoo Silver Partner based in Brisbane](/solutions/odoo), with certified consultants across the full Odoo suite including CRM, Sales, and Field Service. We work with businesses across Queensland, NSW, and Victoria. If you want to know whether Odoo CRM fits your current setup, [**book a free consultation**](/appointment). No sales pitch, just a straight answer. --- # Odoo Inventory Management for Australian Businesses: What It Does and When It's Worth It - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-inventory-management-australia-106 - Category: Odoo ERP Australia - Published: 2026-03-24 - Description: Odoo Inventory covers multi-warehouse stock, barcode scanning, FIFO/AVCO costing, and StarshipIT. What it does and when it works for Australian businesses. Inventory management is where ERP software either earns its cost or doesn't. A business can tolerate a clunky HR tool or a slow CRM, but when your warehouse stock levels are wrong, the pain is immediate: overselling, stockouts, missed deliveries, and customers who don't come back. Odoo Inventory is built to fix that. What it actually delivers, though, depends on how it's configured and what you're comparing it to. So here's an honest look at what you get. ## **What Odoo inventory management actually includes** Odoo Inventory is a native module within the Odoo platform. It shares the same database as your sales orders, purchase orders, accounting, and manufacturing. No middleware, no sync jobs. When a sales order is confirmed, stock is reserved automatically. When a supplier delivery is received, on-hand quantities update in real time. The corresponding accounting entries are generated at invoicing under the Perpetual method, or at your scheduled closing interval under Periodic. The core features most Australian businesses use are multi-warehouse and multi-location management, barcode scanning for receipts and pickings, automated replenishment rules, lot and serial number traceability, and support for multiple picking strategies including batch picking and wave picking for higher-volume operations. Drop-shipping and cross-docking are both supported natively, which is useful for distributors who don't always hold physical stock. Odoo 19 changed how inventory and accounting talk to each other in a way that's worth understanding before you configure anything. In v18 and earlier, the system posted journal entries at each stock movement using interim accounts. [Odoo 19 redesigned this](https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/inventory_valuation/cheat_sheet.html): valuation is now stored directly on stock moves, and the accounting method you choose determines when entries hit your general ledger. Under the Perpetual method, journal entries are generated when vendor bills or sales invoices are confirmed. Under Periodic, entries post at a scheduled closing interval. The practical benefit is a cleaner audit trail and the ability to back-date transfers, which is useful for year-end stock counts adjusted after 30 June. ## **Australian logistics: StarshipIT, Australia Post, and local freight** Odoo v18 and v19 include a native [StarshipIT connector](https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/shipping_receiving/setup_configuration/starshipit_shipping.html), which is the shipping platform most Australian online retailers use. The integration pulls carrier rates from Australia Post, DHL, TNT, and other couriers automatically, generates labels, and sends dispatch notifications without leaving Odoo. If you're shipping domestic orders, it's the integration to set up first. For businesses importing from overseas, the landed cost feature is worth knowing about. You can allocate international freight, customs duties, and insurance across the items in a shipment proportionally, so your inventory valuation reflects what you actually paid rather than just the supplier invoice. Importers sourcing from Asia, where duty rates and freight costs shift from shipment to shipment, tend to find this useful once they understand it's there. ## **Inventory valuation and GST compliance** Odoo supports three inventory costing methods: standard price, Average Cost (AVCO), and First In First Out (FIFO). Each method affects how the cost of goods sold is calculated and how your inventory appears on the balance sheet. Standard price suits businesses with stable costs, typically manufacturers with fixed bills of materials. AVCO works well for distributors handling commodity goods where prices fluctuate. FIFO is required for perishables and is also preferred under Australian Accounting Standards for any business where the cost of older stock differs materially from newer stock. Choosing the wrong costing method won't affect your Goods and Services Tax (GST) calculation directly, but it will affect your gross margin reporting and BAS reconciliation, so it's worth getting right at setup. When you're using the Perpetual accounting method, [Odoo Accounting](/solutions/odoo) receives journal entries when vendor bills and sales invoices are confirmed, keeping your stock valuation reconcilable with your general ledger. Your accountant or BAS agent can work from Odoo directly without needing to import data from a separate system. The [ATO's guidance on GST accounting](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst/accounting-for-gst-in-your-business) requires that tax invoices and goods valuations are accurate and retained. The Perpetual method supports that requirement. If you're using Periodic, your accountant will need to generate closing entries before the ledger reflects current stock values, which is worth factoring into your BAS preparation process. ## **Traceability for regulated and perishable products** For businesses handling food, pharmaceuticals, or medical devices, lot and batch tracking is usually non-negotiable. Odoo lets you assign lot numbers at receipt, track them through every transfer, and pull a full traceability report showing where every unit ended up. FEFO (First Expiry First Out) is available as a removal strategy, so pickers automatically grab the stock nearest to its expiry date rather than whatever's closest to hand. For TGA-regulated products, batch-level documentation is a compliance obligation, not a preference. [ATO record-keeping rules](https://www.ato.gov.au) also require that businesses maintain accurate stock and cost records. Odoo's traceability tools satisfy both without needing a separate compliance system running alongside your inventory. _"The businesses that get the most from Odoo Inventory are the ones that set their product categories and costing methods carefully at the start. Trying to change costing methods mid-implementation is painful. Getting it right upfront means your stock valuation reconciles cleanly and your accounting doesn't need manual adjustments each quarter."_ **Bill Alvarez, Practice Manager, Auboros** ## **What Odoo Inventory doesn't do well** Being honest about limitations is more useful than a feature list. Odoo Inventory works best when your operational processes are reasonably clean. If your warehouse has years of inconsistent product data, duplicate SKUs, or mixed costing methods in your existing system, the migration work is significant and often underestimated. Advanced warehouse management systems from specialist vendors will outperform Odoo for very large operations: think 100,000-plus SKUs, complex third-party logistics billing, or highly automated pick-and-pack with conveyor integration. For most Australian SMEs and mid-market distributors, Odoo covers what's needed. But it's worth being clear that Odoo is an ERP with strong inventory capabilities, not a dedicated WMS. Some third-party integrations also require custom development or community modules rather than native connectors. If you rely on a niche Australian freight provider, check availability in the [Odoo Apps Store](https://apps.odoo.com) before assuming native support exists. According to [Capterra's research on Australian software adoption](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/), fewer than one in three Australian businesses successfully adopt new software without disruption. Confirming integration compatibility before you commit is one of the simplest ways to improve those odds. If you're evaluating Odoo against other options, our [Odoo implementation packages page](/odoo-implementation-packages-for-australian-businesses) outlines what a typical setup covers and what's included in each tier. ## **Frequently asked questions** ### **Does Odoo Inventory support multiple warehouses in Australia?** Yes. Odoo Inventory supports an unlimited number of warehouses and locations within each warehouse. You can manage inter-warehouse transfers, set routing rules per warehouse, and view consolidated stock across all locations from a single dashboard. ### **Does Odoo integrate with Australia Post?** Odoo integrates with StarshipIT, which connects to Australia Post along with other carriers including DHL, TNT, and CouriersPlease. The StarshipIT connector is available natively in Odoo v18 and v19 and allows label printing, rate retrieval, and dispatch tracking directly from within Odoo. ### **How does Odoo handle GST on inventory transactions?** Odoo Accounting applies GST tax codes to purchase and sales transactions automatically based on the tax configuration set on each product. Under the Perpetual accounting method in Odoo 19, journal entries are generated when vendor bills and sales invoices are confirmed, keeping your ledger reconcilable for BAS preparation. If you're using the Periodic method, you'll need to generate closing entries before the ledger reflects current stock values. Either way, GST amounts are tracked in Odoo and your BAS can be prepared without exporting data to a separate system. ### **Can Odoo Inventory handle landed costs for imported goods?** Yes. Odoo's landed cost feature lets you allocate freight, customs duties, insurance, and other import costs across the products in a received shipment. This updates the inventory valuation so your cost of goods sold reflects the actual acquisition cost, not just the supplier invoice price. ### **Is Odoo Inventory suitable for food businesses with expiry dates?** Yes. Odoo supports lot tracking with expiry dates and FEFO picking, which automatically prioritises stock with the nearest expiry. This suits food, beverage, pharmaceutical, and any other business where stock rotation is a compliance or operational requirement. * * * **Evaluating Odoo Inventory for your Australian warehouse or distribution operation?** We implement Odoo for distributors, manufacturers, and retailers across Queensland, NSW, and Victoria. We can walk you through a working demo built around your product types, warehouse layout, and compliance requirements. If you'd like to see Odoo Inventory in action with your own scenarios, [**book a free consultation**](/appointment) and we'll tailor the session accordingly. --- # MYOB Acumatica eInvoicing: What Australian Businesses Need to Know Before the 2026 Deadlines - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-einvoicing-australia-2026-107 - Category: MYOB Acumatica Australia - Published: 2026-03-24 - Description: Odoo Inventory covers multi-warehouse stock, barcode scanning, FIFO/AVCO costing, and StarshipIT. What it does and when it works for Australian businesses. If your business supplies goods or services to Australian government agencies, there are two dates in 2026 worth understanding. The first is 1 July 2026. The second is December 2026. Both are tied to Australia's eInvoicing mandate, and if you're running MYOB Acumatica, the good news is that you already have what you need to comply. You just need to connect the pieces. This post covers what eInvoicing actually means in 2026, what's changed from the earlier Peppol rollout, and how MYOB Acumatica users get set up before the deadlines hit. ## **What Australia's eInvoicing mandate requires in 2026** Australia adopted the Peppol eInvoicing standard back in 2019. What's changed is the teeth behind it. The [Australian Taxation Office](https://www.ato.gov.au/businesses-and-organisations/einvoicing/einvoicing-for-government) now requires all Non-Corporate Commonwealth Entities (NCEs), meaning federal government departments and agencies, to receive 30% of their invoices via eInvoicing by 1 July 2026. By December 2026, they must also be able to send eInvoices automatically. For businesses supplying to government, the practical effect is straightforward: if you're invoicing a federal agency and you're not sending via Peppol, there's a good chance your trading partner will start pushing you in that direction this year. Some agencies are already requiring it for new supplier onboarding. The technical standard has also tightened. Since 15 May 2025, the only supported format for sending eInvoices in Australia is [Peppol PINT A-NZ](https://www.ato.gov.au/businesses-and-organisations/einvoicing/peppol). The earlier ANZ BIS 3.0 format is no longer valid for sending. If your system was set up on the older format, it needs updating. ## **How MYOB Acumatica connects to the Peppol network** MYOB Acumatica doesn't connect to Peppol directly out of the box. You connect through an accredited Peppol Access Point, which is a service provider that sits between your system and the Peppol network and handles the translation and routing. The most established Access Point for MYOB Acumatica users in Australia is [MessageXchange](https://home.messagexchange.com/integrations/myob-acumatica/), which holds Peppol certification and maintains a dedicated MYOB Acumatica integration. MessageXchange handles the PINT A-NZ format mapping and can adjust the configuration as standards evolve, without you needing to touch the underlying ERP setup. Setup is faster than most people expect. According to MessageXchange, connecting to the Peppol network through an Access Point can take less than a day once you have your ABN registered as your Peppol Participant ID. The ABN is how your business is identified on the Australian Peppol network, and it's the same identifier your trading partners use to route invoices to you. ## **What changes in your day-to-day invoicing workflow** Once you're connected, the invoicing workflow in MYOB Acumatica doesn't change significantly for your team. You create the invoice the same way you always have. The Access Point intercepts the data, converts it to PINT A-NZ format, and delivers it directly into your customer's accounts payable system through the Peppol network. The practical differences your team will notice: no more PDFs attached to emails for Peppol-connected customers, faster acknowledgement of receipt, and in many cases faster payment because the invoice arrives pre-structured in the buyer's system rather than requiring manual keying. Importantly, a Peppol eInvoice that meets the A-NZ Invoice Specification qualifies as a valid tax invoice under Australian law. You don't need to add "tax invoice" or "GST invoice" headers. The structured data fields carry the required information. If you want to confirm how this aligns with your current invoicing obligations, the [ATO's tax invoice guidance](https://www.ato.gov.au/businesses-and-organisations/gst/tax-invoices) covers the data requirements in detail. _"Most MYOB Acumatica clients we work with are closer to Peppol-ready than they realise. The platform handles the invoicing data correctly. What they're usually missing is the Access Point connection and the PINT A-NZ mapping. That's a configuration project, not a system overhaul."_ **Bill Alvarez, Practice Manager, Auboros** ## **What about businesses that don't supply to government?** The 2026 mandates apply specifically to Non-Corporate Commonwealth Entities as buyers. There's currently no legal requirement for private-sector businesses to send eInvoices to other private-sector businesses in Australia. That said, eInvoicing adoption among larger private-sector buyers is growing. The same PINT A-NZ standard works across all trading relationships, and if a major customer asks you to invoice via Peppol in the next 12-24 months, being already connected means you can say yes immediately. It's also worth considering the operational side. Accounts payable teams at larger organisations are under pressure to reduce manual processing. Structured eInvoices that arrive directly into their ERP reduce re-keying errors and processing time. Some buyers are starting to prioritise Peppol-capable suppliers as part of their procurement criteria, even where it isn't mandated. ## **Payday Super and eInvoicing: two compliance projects landing in 2026** It's worth noting that eInvoicing isn't the only compliance change hitting MYOB Acumatica users in 2026. The Payday Super requirement, which links superannuation payments directly to each payroll run rather than quarterly, takes effect from 1 July 2026. If you're planning a system review ahead of the financial year, both projects make sense to address at the same time. Our [MYOB Acumatica payroll guide for 2026](/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97) covers the Payday Super requirements in detail if you want to understand the scope of that change alongside eInvoicing. ## **Frequently asked questions about MYOB Acumatica eInvoicing** ### **Is eInvoicing mandatory for all Australian businesses in 2026?** Not for private-sector transactions. The current mandate applies to Non-Corporate Commonwealth Entities as buyers, requiring them to process 30% of invoices via eInvoicing by 1 July 2026 and to send eInvoices by December 2026. There is no mandatory requirement for business-to-business eInvoicing in the private sector, though adoption is growing. ### **What is Peppol PINT A-NZ and why does it matter?** PINT A-NZ (Peppol International A-NZ) is the current mandatory format for eInvoicing in Australia and New Zealand. Since 15 May 2025, it is the only supported format for sending invoices on the Peppol network. If your eInvoicing setup was configured on the earlier ANZ BIS 3.0 format, it needs to be updated before you can send compliant eInvoices. ### **Do I need a separate system to send Peppol eInvoices from MYOB Acumatica?** You need an accredited Peppol Access Point to connect MYOB Acumatica to the Peppol network. Providers like MessageXchange offer a dedicated MYOB Acumatica integration that handles the format conversion and delivery. You continue using MYOB Acumatica as normal; the Access Point manages the transmission to your trading partner. ### **How do I register for Peppol eInvoicing in Australia?** You register your ABN as your Peppol Participant ID through your chosen Access Point provider. Once registered, your business appears in the Peppol Directory and trading partners can send eInvoices directly to you. The ATO maintains a [register of accredited Peppol Access Point providers](https://softwaredevelopers.ato.gov.au/accreditation-Peppol-service-provider-register) if you want to review your options. * * * **Need help getting MYOB Acumatica ready for eInvoicing?** Auboros is an [official MYOB Acumatica partner](/solutions/myob) based in Brisbane, supporting businesses across Queensland, NSW, and Victoria. If you're not sure what to look for when choosing a partner to help with compliance work like this, our guide on [what to look for in a MYOB Acumatica consultant](/blog/myob-acumatica-australia-7/myob-acumatica-consulting-what-to-look-for-99) is a useful starting point. Whether you're assessing your eInvoicing readiness or need to get connected before the July deadline, we can help scope the work quickly. If you'd like a straight answer on what's involved for your specific setup, [**book a free consultation**](/appointment). We'll tell you exactly where you stand. --- # MYOB Acumatica for Construction in Queensland: Job Costing, QBCC Compliance, and What's Included - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-for-construction-in-queensland-job-costing-qbcc-compliance-and-what-s-included-105 - Category: MYOB Acumatica Australia - Published: 2026-03-24 - Description: MYOB Acumatica Construction covers job costing, QBCC trust accounts, and workforce management for Queensland contractors. Here's what the platform includes. Construction businesses in Queensland face a compliance environment that most ERP systems weren't designed for. Project trust accounts, QBCC obligations, complex job costing, and a workforce spread across multiple sites are the kind of problems that Xero or generic accounting software was never built to handle. MYOB Acumatica's Construction edition exists specifically for this environment, and the Queensland compliance angle, particularly the trust account framework, is where it pulls away from the alternatives. ## **MYOB Acumatica Construction: what's in the platform** MYOB Acumatica Construction is a cloud-based ERP built for mid-sized construction companies. It's not a bolt-on module sitting on top of a generic accounting system. The construction capabilities are built into the core platform alongside financials, payroll, procurement, and project management, so everything talks to everything else. The core capabilities include real-time job costing across labour, materials, equipment, and subcontractor commitments; project budget tracking with committed cost visibility; change order management; subcontract and purchase order management; daily field reporting accessible on mobile; and document management for drawings, certificates, and compliance records. According to [MYOB's construction product page](https://www.myob.com/au/erp-software/industries/cloud-construction-software), the platform is designed to give project managers and back-office teams a single view of project activity, from site variations to invoicing. The commitment tracking is worth singling out. You can see what's been spent, what's locked in approved purchase orders, and what the forecast cost to complete looks like, all without waiting for end-of-month reporting. For a project running close to margin, that real-time visibility changes how you manage the last 30% of a job. ## **QBCC trust accounts: the Queensland compliance requirement that changes everything** For Queensland contractors, MYOB Acumatica Construction addresses something that most construction software ignores entirely: [QBCC trust account compliance](https://www.qbcc.qld.gov.au/running-business/trust-accounts). Under the Building Industry Fairness (Security of Payment) Act 2017, Queensland contractors working on eligible projects are required to hold project payments in dedicated trust accounts rather than general operating accounts. There are two types: - **Project Trust Accounts (PTA):** One separate account is required per eligible contract. All project payments received from the principal must go into this account, and subcontractors must only be paid from it. - **Retention Trust Accounts (RTA):** Holds retention amounts withheld from subcontractors. Only one RTA is required per business, covering multiple projects. Since October 2025, the framework applies to all eligible construction projects of $1 million or more. Getting this wrong carries serious regulatory risk. MYOB Acumatica Construction is designed to help you manage these obligations within the platform rather than tracking them in spreadsheets alongside your main system. The platform automates deposits and withdrawals across separate project and retention trust ledgers, generates pre-defined compliance reports for the QBCC, beneficiaries, principals, and auditors, and maintains transaction records for the required retention period. MYOB describes it as the first business management platform in Australia purpose-built for trust account compliance. _"Queensland contractors using spreadsheets for trust account reconciliation are carrying real risk. When auditors come in, the question isn't just whether the money is there, it's whether the records are complete and match the project ledger. MYOB Acumatica automates that reconciliation, which takes a significant compliance burden off the business."_ **Bill Alvarez, Practice Manager, Auboros** ## **Job costing and project financials** Accurate job costing is the foundation of profitable construction. Most construction businesses that come to us have a version of the same problem: project managers know roughly what's been spent but the finance team is always a few weeks behind, and by the time the overrun shows up on a report, it's too late to act on it. MYOB Acumatica addresses this by connecting site activities to the financial ledger in real time. Timesheets entered by site workers update labour costs against the job immediately. Purchase orders raised for materials create committed cost entries before the supplier invoice arrives. Subcontractor progress claims are tracked against approved contract values, with variation workflows keeping the audit trail clean. [MYOB's 2025 ERP Trends Report](https://www.myob.com/au/insight/post/erp-trends) found that 45% of Australian business decision-makers say disconnected systems limit their ability to grow. In construction, that disconnect almost always sits in the same three places: the site management tool, the payroll system, and the accounting platform. Three separate sources of truth, and none of them agree. MYOB Acumatica connects all three. ## **Payroll and workforce management for construction teams** Construction payroll in Australia is genuinely complex. Award rates under the Building and Construction General On-site Award vary by classification and site. Allowances for tool use, travel, and site conditions shift by project. Super guarantee contributions and Single Touch Payroll (STP) Phase 2 reporting are already live, and [Payday Super obligations from 1 July 2026](/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97) add the next layer of compliance to get right. MYOB Acumatica's workforce management module handles rostering, timesheets, leave, and payroll for large and geographically dispersed teams. STP Phase 2 reporting is built in, as are super contribution management and payslip distribution. For QLD construction businesses, the platform also supports [MYOB's payroll compliance updates](https://enterprisesupport.myob.com), which are updated as the ATO and Fair Work issue changes. ## **Is MYOB Acumatica Construction right for your business?** MYOB Acumatica Construction is best suited to mid-sized construction companies: typically businesses with annual revenue above $5 million, more than 20 staff, and projects that involve subcontractor management and compliance reporting. It's most clearly justified when you're managing QBCC trust account obligations, running multiple concurrent projects, or operating in the mid-market where generic accounting software like Xero or MYOB AccountRight has started to create friction. You can see more about [our full MYOB Acumatica service offering](/solutions/myob) if you want to understand the implementation scope before going further. For smaller trades businesses, it's likely more than you need. For large, complex contractors with 200-plus staff and highly specialised operational requirements, a more tailored enterprise construction platform may be worth evaluating alongside it. [Construction is Australia's largest industry by number of businesses](https://www.abs.gov.au/statistics/economy/business-indicators/counts-australian-businesses-including-entries-and-exits/latest-release), with 462,939 nationally and 2.2% growth in 2024-25. Queensland led all states at 3.1%. That growth means more businesses entering the mid-market threshold where generic accounting software stops coping, and where the QBCC trust account obligations start applying. The stakes of getting your system wrong are higher than in most sectors. ## **Frequently asked questions** ### **Does MYOB Acumatica Construction handle QBCC trust accounts?** Yes. MYOB Acumatica Construction includes dedicated trust account management covering both Project Trust Accounts and Retention Trust Accounts. It automates ledger entries, generates QBCC compliance reports, and maintains records for the required retention period under the Building Industry Fairness (Security of Payment) Act 2017. ### **What construction businesses is MYOB Acumatica best suited to?** MYOB Acumatica Construction is designed for mid-sized construction companies, typically those with annual revenue above $5 million managing multiple concurrent projects with subcontractor relationships. It's well-suited to head contractors with QBCC obligations, commercial builders, civil contractors, and construction-adjacent businesses like mechanical and electrical contractors. ### **How does MYOB Acumatica handle construction payroll in Queensland?** MYOB Acumatica's workforce management module covers rostering, timesheets, leave management, and payroll with Single Touch Payroll Phase 2 reporting built in. For Queensland construction businesses, this includes super guarantee management and support for the Payday Super changes taking effect 1 July 2026. ### **Does MYOB Acumatica integrate with site management tools?** MYOB Acumatica supports integration with a range of third-party tools including job management and field service platforms. Integration availability depends on the specific tool. An implementation partner can advise on what connects natively versus what requires custom development. * * * **Running a construction business in Queensland and evaluating your ERP options?** We work with construction companies across Queensland and can help you assess whether MYOB Acumatica fits your project size, compliance obligations, and growth plans. We know the QBCC trust account requirements and the specific complexities of construction payroll in this state. If you'd like to understand what an implementation would look like for your business, [**book a free consultation**](/appointment) and we can work through your specific situation. --- # AI in Odoo: What's Actually Useful for Australian Businesses in 2026 - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/ai-in-odoo-australia-2026-102 - Category: Odoo ERP Australia - Published: 2026-03-19 - Description: Odoo 19's AI covers sales, accounting, documents and livechat. Here's what's actually working for Australian businesses right now, plus what's coming in v20. There's a lot of noise around AI in ERP right now. Some of it is marketing. Some of it is genuinely useful. If you're running Odoo or evaluating it, you want to know which bits are actually ready to use in a real business today, which ones need careful setup, and what's coming that will change how you think about automation altogether. This post covers the full picture: what Odoo AI does across every major module in v19, what the Australian context changes about the answer (GST, BAS, and compliance matter here), what Odoo's CEO Fabien Pinckaers announced about AI-assisted development in February 2026, and where Odoo v20 is taking things later this year. We've also been configuring AI inside Odoo since version 16, so we can tell you what the ROI actually looks like from client work, not from a vendor brochure. ## **How Odoo AI has evolved: from v17 to v20** Odoo's AI capabilities have changed substantially across recent versions. Before getting into the specifics, here's the version landscape, because where you are now shapes what's available to you: | Version | Key AI additions | What it meant in practice | | --- | --- | --- | | **v17** | Basic content generation, early OCR | AI as a drafting aid. Useful for product descriptions and email templates. Not deeply embedded in business processes. | | **v18** | Improved document OCR, lead scoring in Sales, email drafting, expense product prediction | AI starts doing operational work. Invoice processing becomes materially faster. Lead scoring gives sales managers a prioritised pipeline view. | | **v19** | Dedicated AI app, AI Agents, AI automation rules, AI across Sales, Accounting, Documents, Knowledge, Livechat, Website | AI becomes a platform layer, not a feature list. Every module gets AI capability. Natural language database queries. Custom agents trained on your own data. | | **v20** _(expected Sept 2026)_ | Agentic AI: autonomous, proactive workflow execution | Moves from responding to instructions to acting independently. The system checks, decides, and acts without being prompted. | ## **What AI features does Odoo 19 include?** Odoo 19 introduced a dedicated [AI app](https://www.odoo.com/documentation/19.0/applications/productivity/ai.html) that runs inside the modules you already use. It's not a bolt-on integration. The [Odoo 19 release notes](https://www.odoo.com/odoo-19-release-notes) and the v19 Enterprise source code (which Auboros accesses as a certified Silver Partner) confirm AI integration across the following areas: - **Ask AI and natural language database queries:** ask questions about your Odoo data in plain English, without navigating menus or building filters manually. - **AI Agents:** configurable assistants you train on your own documents, knowledge base, and website content. They answer queries and, with the right setup, take actions inside Odoo. - **AI in Odoo Studio (automation rules):** set up automations that use AI to evaluate conditions and update record fields without any custom code. - **AI Document Management:** automatically sorts uploaded documents into the right folders based on content classification. - **AI in Accounting:** AI-assisted drafting for payment follow-ups and collection letters, layered on top of the invoice OCR that has been in Odoo since v18. - **AI in Sales and CRM:** automatic lead creation from emails, website interactions, and livechat, plus the pipeline probability scoring from v18. - **AI in Knowledge:** AI text drafting and content improvement inside the Knowledge module. - **AI Website Builder:** page creation and content drafting for businesses running their public website on Odoo. - **AI in Livechat and Helpdesk:** suggested responses for agents in real time, plus ticket history summarisation. ## **AI across your Odoo modules: what it actually does** The feature list above is accurate but abstract. Here's what each area means for someone running a business in Australia. ### **Sales and CRM: smarter pipeline management** Lead scoring has been in Odoo since v18 and assigns probability percentages to deals based on historical close data. The model learns from your own pipeline, not a generic benchmark. A deal at 70% in one industry might behave completely differently from a deal at 70% in yours, and Odoo's scoring reflects your actual history. In v19, automatic lead creation adds another layer. The system can identify and generate leads from website form submissions, livechat conversations, and incoming email threads without a sales rep manually creating a record. For teams managing high inquiry volume, this removes the admin gap between "someone contacted us" and "that contact is tracked in the pipeline." ### **Accounting: the clearest ROI for most businesses** Most businesses notice the accounting AI first, and for good reason. The document OCR engine reads uploaded supplier invoices, receipts, and bills, and pre-fills vendor name, ABN (where present), invoice total, GST amount, and due date. In an Australian context, getting the GST extraction right matters directly for your BAS (Business Activity Statement) accuracy. One wrongly coded line on a supplier invoice can create a reconciliation issue you won't find until BAS time. If your accounts payable team is processing a high volume of supplier invoices, most of that data entry disappears once the system has learned your regular vendors. The time saving compounds quickly. Finance staff spending two hours a day on manual invoice entry get most of that time back. V19 also adds AI-assisted drafting for overdue payment reminders and collection letters. For businesses that let aged receivables sit because nobody has time to write the follow-up, this removes the friction. ### **Document Management: intelligent sorting, without manual filing** Odoo's AI document sorting automatically classifies uploaded files and routes them to the right location based on content. Bills go to the Bills folder. Contracts go to Contracts. HR documents go to HR. For businesses that have a shared inbox or document upload process and rely on someone manually sorting what comes in, this is where you recover hidden administrative hours. The AI document integration with accounting (a separate module in v19 Enterprise) goes a step further, linking sorted documents directly to accounting workflows so bills are ready for review rather than sitting in a queue waiting to be filed first. ### **AI Automation Rules: powerful without a developer** If your business doesn't have a dedicated development team, this is the feature worth paying close attention to. In Odoo's automation configuration, you can write rules in plain language that the system interprets and applies to your data. An automation rule might say: when a new enquiry comes in, use AI to assess the description and assign the opportunity to the right sales team based on what they're asking about. No code. No developer. Just a rule you configure in the settings. The line between "using Odoo AI" and "building something custom" is starting to disappear. Workflows that used to require a developer to build can now be configured by a business analyst or operations manager with the right knowledge of the platform. ### **Ask AI and natural language queries: the quietest productivity gain** The ability to type "show me all overdue invoices from Queensland customers over $10,000" and get a filtered result immediately is practical and doesn't need configuration. Finance managers and operations staff who know what they want but often have to ask someone else to build the report will use this constantly. It lowers the cost of getting to your own data. ### **Knowledge and internal tools: keeping your process library current** For businesses using Odoo Knowledge as their operations manual or training resource, AI assists with drafting and improving articles. Most knowledge bases go stale because updating them takes effort nobody has time for. If the effort of updating a procedure becomes "open the article, click improve, review the suggestion," more people will actually do it. ### **Livechat and customer support: faster responses, less effort** For businesses running Odoo Livechat, AI suggests responses to common queries in real time. For Helpdesk, it summarises the history of an ongoing ticket when an agent picks it up. Both reduce time to a useful response for the customer, and reduce the cognitive load on the agent handling the interaction. ## **What real ROI looks like** We've been configuring AI features inside Odoo since version 16, across implementations in Queensland, New South Wales, and Victoria. The return varies by business, but the patterns are consistent. Accounts payable automation delivers the fastest visible result, typically within the first month of go-live. Businesses that were spending significant staff time on manual invoice entry see that time drop substantially, and the accuracy of their GST coding improves because the AI doesn't make transcription errors. Beyond invoice processing, the more interesting ROI comes from automations that businesses couldn't afford to build before. Agentic workflows that trigger supplier communications based on inventory thresholds. AI agents trained on product catalogues that handle first-level customer queries without a human in the loop. Lead qualification rules that route high-intent enquiries to senior sales staff automatically. None of these are theoretical. They're things we've built in production for Queensland clients. _"We've been configuring AI inside Odoo since v16, well before it became a marketing headline. The ROI is real and the business cases are genuinely only limited by how well you understand your own processes. We've built some incredibly useful things for clients: invoice automation running overnight without anyone touching it, agentic workflows triggering supplier communications based on stock movements, AI agents handling live customer queries from a product catalogue. We're genuinely excited about what v20 will bring. As AI matures in the Odoo ecosystem, the move towards truly autonomous workflows is going to open up use cases we haven't built yet."_ **Bill Alvarez, Practice Manager, Auboros** According to [MYOB's 2025 ERP Trends Report](https://myob.com/au/insight/post/erp-trends), 45% of Australian decision-makers say disconnected systems limit their business growth. The businesses getting the most from Odoo AI are the ones where everything, finance, inventory, sales, support, sits inside a single system. The AI has richer data to work with, the automations don't have to cross system boundaries, and the natural language queries can see the whole picture. ## **What this means for Australian businesses specifically** Odoo's Australian localisation covers GST, BAS reporting, and Single Touch Payroll (STP) Phase 2. The AI features don't replace any of that, but they make it easier to feed those reports accurately. Where this actually shows up: - **Invoice processing with GST:** when Odoo AI reads a supplier invoice, it extracts the GST amount and codes it to the right tax account. If your vendor and tax mapping are correct, the pre-filled entries include the right GST treatment. This matters for BAS accuracy. - **Natural language queries for BAS prep:** instead of building a custom report, you can ask "show me all GST collected this quarter" directly. It doesn't generate the BAS itself, but reviewing the underlying data before lodgement becomes much faster. - **AI Agents for compliance queries:** train an agent on your ATO correspondence, payroll policies, and internal procedures, and it can handle routine team questions about process without someone senior stepping in each time. - **STP and payroll compliance:** Odoo's Australian payroll module handles Single Touch Payroll Phase 2 reporting. AI doesn't touch the STP submission itself, but it assists with the surrounding HR and payroll workflow, drafting communications and summarising employee records. For current ATO compliance requirements, [ato.gov.au](https://www.ato.gov.au) is the authoritative source. Odoo's own Australian localisation documentation covers how these are implemented in the platform. ## **Claude Code and Odoo.sh: what Fabien Pinckaers announced in February 2026** This is the announcement that generated the most discussion in the Odoo developer community in early 2026. In February, Odoo CEO Fabien Pinckaers announced that [vibe coding is being officially integrated into Odoo.sh](https://muchconsulting.com/blog/odoo-2/odoo-news-february-2026-139) with Claude Code as the AI development tool of choice. What this means practically: developers using Odoo.sh can use Claude Code directly within the platform to generate custom Odoo modules by describing what they want in natural language. Claude Code reads the entire project context, including existing models, manifest files, and inheritance chains, and generates multi-file changes simultaneously. It's not a generic code generator. It understands Odoo's framework patterns because the model has been trained extensively on Odoo's open-source codebase, which is a genuine advantage over trying to use a general-purpose AI assistant for Odoo development. Pinckaers describes the approach as three elements: standard Odoo applications as the foundation, rapid AI-assisted customisation as the mechanism, and Odoo.sh as the platform that keeps deployment safe. The claim is that custom features that previously took weeks of development can be produced in minutes. Community reaction has been engaged and honestly divided. Some developers see this as a step-change in how quickly small teams can customise Odoo for clients. Others raise legitimate concerns about unreviewed AI-generated code in live business environments, drawing comparisons to early Odoo Studio experiences with code quality and upgrade path stability. The position we'd take: the AI generates faster, but someone who understands Odoo still needs to review what comes out before it goes near production data. For [Odoo clients](/solutions/odoo) in Australia, the practical implication is that customisation is becoming more accessible. Features that previously required a larger development engagement can potentially be delivered faster and at lower cost. That's good news for businesses who've wanted specific workflows but couldn't justify the investment. ## **What about Odoo v18? And what we've built for clients on it** If you're on Odoo 18, which many Australian businesses are given it reached stable release in late 2024, you're not waiting on the sidelines. Version 18 includes document OCR for invoice processing, text generation across the platform, email drafting, lead scoring in CRM, and an expense product prediction feature. The dedicated AI app with Agents is a v19 addition, but the most commonly used day-to-day AI features are available right now on v18. We've also built native AI capabilities directly into v18 implementations for several Queensland clients, going beyond the standard feature set. Document classification rules, automated purchase order matching, and workflow automations triggered by AI-detected conditions are all things we've configured within v18 without waiting for a version upgrade. If you're on v18 and want to understand what's accessible now versus what requires moving to v19, it's worth a direct conversation rather than going by the published feature list alone. Auboros is [certified in Odoo v18](/solutions/odoo) and works with clients upgrading to v19. If you're planning an implementation or upgrade, timing your version choice to align with which AI capabilities you want access to is worth factoring in early. ## **What's coming in Odoo v20: agentic AI** Odoo v20 is expected at Odoo Experience in September 2026 in Brussels, and the anticipated headline feature is agentic AI. The distinction from v19 is significant: v19 AI responds when asked. V20 AI is expected to act without being asked, proactively executing workflows based on conditions it monitors itself. The practical difference is the gap between a smart calculator and an employee who checks inventory every morning, files the reorder automatically, and emails the supplier before you knew there was a short. For manufacturing businesses, agentic AI embedded in production scheduling could adjust work orders in real time based on machine downtime data, supplier delays, and demand signals simultaneously. For distribution businesses, it could monitor stock movements and trigger purchase orders or customer notifications autonomously. These are roadmap directions, not confirmed feature announcements. Odoo makes official product announcements at Odoo Experience each year. What's clear is that the v19 AI platform layer is being built specifically as the foundation for this kind of autonomous operation. Getting your Odoo implementation AI-ready now, with clean data, well-structured automations, and the right module configuration, is what makes upgrading to v20 a natural progression rather than a disruptive project. ## **Do you need Enterprise to use Odoo AI features?** Yes. The AI app and most AI features require an Enterprise subscription. Some features also require configuring an AI provider API key, typically OpenAI, or using Odoo's IAP (In-App Purchase) credits available through your Odoo.com subscription. Your implementation partner handles this as part of the setup. One thing worth being clear on: Odoo Enterprise source code is accessible to all Enterprise subscribers, not just partners. So the question of whether to bring in a partner for AI configuration or handle it internally is a capability question, not an access question. If your internal team has the technical depth, a lot of the AI setup is something you can manage yourselves. If it's not a core competency, a partner will get you there faster and with fewer configuration mistakes to unpick later. There are community-built approaches for adding AI to Odoo Community Edition using workflow tools and open-source integrations, but these carry more maintenance overhead. For most Australian mid-market businesses, the Enterprise route is the practical path. The [Auboros implementation packages page](/odoo-implementation-packages-for-australian-businesses) covers what's included at each tier. ## **Frequently asked questions** ### **Is Odoo AI available for Australian businesses?** Yes. All Odoo AI features are available globally with no geographic restrictions. Australian Enterprise subscribers access them the same way as anyone else. Setup requires configuring an AI provider API key or IAP credits, which your implementation partner handles as part of onboarding. ### **Does Odoo AI help with BAS and GST processing?** Indirectly, yes. Odoo AI improves invoice data entry accuracy, which feeds directly into your BAS (Business Activity Statement) figures. Natural language queries let you review GST-coded transactions before lodgement without building a custom report. Odoo's Australian localisation handles the BAS report structure itself. The AI assists the inputs, not the report. For current BAS and GST requirements, [ato.gov.au](https://www.ato.gov.au/businesses-and-organisations/tax-obligations/gst) is the authoritative source. ### **Can Odoo AI read and process supplier invoices automatically?** Yes. Odoo's invoice OCR reads uploaded bills and pre-fills vendor details, amounts, GST lines, and due dates. Accuracy improves over time as the system learns your regular vendors. You still review and approve before posting. Available in both v18 and v19. V19 adds automatic document sorting on top of processing. ### **What does Claude Code in Odoo.sh mean for my business?** It means customisations that previously required significant development time are becoming faster and less expensive to deliver. Fabien Pinckaers announced in February 2026 that Claude Code is being integrated into Odoo.sh for AI-assisted module development. Features you've wanted but couldn't justify the build cost for are increasingly within reach. The code still needs review by someone who knows Odoo before it goes to production, but the build time is shrinking. ### **When is the right time to add AI features to an Odoo implementation?** Start with a stable core first. AI features work best when your data is clean, your chart of accounts is correct, and your team understands the basics. Most Auboros clients look at AI configuration in phase two, once the core go-live is settled and the team knows what they actually want automated. Layering AI on top of a setup that hasn't been properly configured creates more problems than it solves. ### **Is Odoo AI ready to replace an accountant or finance manager?** No, and it's not designed to. What it handles is the volume work: data entry, routine lookups, repetitive drafting. Judgment calls, exception handling, and the professional accountability that comes with BAS lodgement and STP payroll still need a person. The value is in returning hours of manual work to your finance team so they can focus on the work that actually needs thinking. * * * **Thinking about AI as part of your Odoo implementation?** We've been building Odoo AI configurations for Queensland and New South Wales businesses since v16. We know what delivers real results and what needs more setup than most businesses are prepared for. Getting the architecture right from the start is what makes AI genuinely useful rather than a feature nobody ends up using. If you're planning an Odoo implementation or upgrade and want a straight conversation about where AI fits in your specific situation, [**book a free consultation**](/appointment). No obligation, just an honest assessment of what makes sense for your business and your timeline. Start writing here... --- # MYOB Acumatica for Wholesale Distribution: What the FastStart Program Gives You - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-wholesale-distribution-faststart-australia-103 - Category: MYOB Acumatica Australia - Published: 2026-03-19 - Description: FastStart is MYOB Acumatica's fixed-scope program for small wholesale distributors under $10m. Auboros delivers it in Queensland in 12 weeks. Wholesale distribution businesses have a particular ERP problem. You need inventory control, purchase orders, sales orders, accounts receivable, and financials all talking to each other from day one. But most ERP implementations are either too slow, too expensive, or too generic to get you there without a long configuration project that drains time and budget before you've seen anything running. [MYOB Acumatica FastStart for Wholesale Distribution](/solutions/myob-acumatica-faststart-wholesale-distribution) is a fixed-scope, pre-configured implementation program built specifically for smaller wholesale distributors that have outgrown their accounting software. If you're the right fit, it gets you live in 12 weeks. If you're not, a broader implementation is the honest answer. This post covers both. ## **What is MYOB Acumatica FastStart?** FastStart is MYOB Acumatica's structured deployment methodology for small-to-mid wholesale distributors. The scope is fixed before the project begins: pre-built workflows already configured for distribution processes, defined milestones, and a 12-week timeline from kick-off to go-live. The difference from a standard ERP implementation is that you're adjusting a working base, not designing one from scratch. Standard implementations begin with weeks of discovery workshops before configuration starts. FastStart skips that blank-canvas phase because the core wholesale distribution workflows are already built in. According to [MYOB's 2025 ERP Trends Report](https://myob.com/au/insight/post/erp-trends), 45% of Australian decision-makers say disconnected systems limit their business growth. For distributors running separate inventory, order management, and finance tools, that's a familiar position. FastStart is designed to replace that patchwork, but it's designed for businesses that fit a specific profile. ## **Who is FastStart actually built for?** FastStart has a defined eligibility criteria. It is built for wholesale distribution businesses that meet all of the following: - **Single legal entity, single branch**: businesses operating under one ABN and one physical location. Multi-entity structures or businesses with multiple branches are outside FastStart scope. - **Under 10 users**: the pre-configured implementation is sized for smaller teams. Larger user counts require a broader scoping conversation. - **Under 50 staff**: FastStart is not a large-enterprise program. It's built for growing businesses at a specific stage. - **Under $10 million annual turnover**: above this threshold, the complexity of operations typically warrants a full-scope implementation rather than the FastStart framework. - **Standard wholesale distribution processes**: the program works well when your core operations follow recognisable distribution patterns: buy, hold, and sell stock. Businesses with highly unusual or bespoke processes are a poor fit. - **No requirement for bespoke integrations in Phase 1**: custom integrations with third-party platforms can be added later, but they're not part of the FastStart scope. If your business sits outside these parameters, multiple entities, over 10 users, complex non-standard workflows, or manufacturing requirements, FastStart is not the right starting point. The [Auboros MYOB Acumatica services page](/solutions/myob) covers what a full implementation looks like. ## **What does Wholesale Distribution FastStart actually cover?** The program covers six operational areas across the [MYOB Acumatica Wholesale Distribution](https://www.myob.com/au/erp-software/industries/wholesale-distribution-software) platform: - **Finance, banking and taxes:** general ledger, bank feeds, GST and BAS configuration, financial reporting. Built for Australian compliance from the start. - **Accounts receivable and payable:** customer invoicing, payment collection, credit management, supplier liabilities, prepayments, and adjustments. Integrated with inventory and the general ledger so your financial picture stays current. - **Inventory and pricing:** item master setup, multi-location stock management within your single branch, pricing structures, and physical stock counts. - **Sales orders and purchasing:** end-to-end order management from quote to fulfilment. Purchase orders, shipment processing, and supplier invoices in one workflow. No switching between systems to get an order out the door. - **User acceptance testing:** structured scenario-based testing with formal sign-off checkpoints at each phase. You validate the system against real business scenarios before go-live, not after. - **Data migration and go-live:** migration from your legacy system, cutover support, and handover to make sure your team is operational from day one. These come pre-configured for wholesale distribution, so the starting point is already closer to what your business needs than a generic ERP setup. You're adjusting configuration, not building processes from scratch. ## **What the 12 weeks involves** FastStart runs across 7 structured phases, each with defined scope and formal sign-off before the next phase begins. The 12-week timeline is realistic when the scope stays fixed and both sides stay on track. On the client side, expect to commit around 95 hours across the project, roughly 8 to 9 hours per week. That includes around 14.5 hours of self-paced training through MYOB Academy. It's not a passive process. The businesses that hit 12 weeks are the ones where the internal project owner is engaged and prepared to make decisions at each checkpoint. _"Wholesale distribution businesses often tell us their biggest ERP concern is going live too slowly and spending too much before they see any value. FastStart changes that dynamic, but only for the right type of business. When the fit is right, single entity, standard processes, a team under 10 users, we can have them live and operational within 12 weeks. When the fit isn't right, we say so upfront rather than putting a business through a program that wasn't designed for their situation."_ **Bill Alvarez, Practice Manager, Auboros** Auboros is MYOB's FastStart Wholesale Distribution partner in Queensland. That means we've worked through the methodology with multiple clients in the region and we know where the common decisions come up and how to handle them without extending timelines. ## **What's not included** Being clear about what FastStart doesn't cover is as important as what it does. Outside the fixed scope: - Custom integrations with third-party platforms (eCommerce, 3PL, EDI, CRM), these can be added in a subsequent phase - Manufacturing or work-in-progress management - Complex project accounting - Multi-entity or multi-branch structures - Bespoke workflow development If you need any of the above from the start, a full-scope MYOB Acumatica implementation is the right conversation, not FastStart. Your Statement of Work will define the exact scope clearly before any work begins. ## **A note on Australian compliance** MYOB Acumatica is built for the Australian market. The FastStart implementation includes GST at 10%, BAS reporting, and Single Touch Payroll Phase 2 for businesses that need payroll inside the platform. These are not add-ons. For businesses supplying government agencies, MYOB Acumatica also supports eInvoicing via the [Australian Peppol network](https://www.ato.gov.au/businesses-and-organisations/einvoicing). For current payroll compliance requirements, the [MYOB Enterprise Support payroll compliance page](https://enterprisesupport.myob.com/knowledge/payroll-compliance-changes-au) keeps that current. ## **Frequently asked questions** ### **Is FastStart right for my wholesale distribution business?** FastStart works best for single-entity wholesale distributors under $10 million turnover, under 10 users, and with standard distribution processes. If your business is larger, runs multiple entities, or has complex or bespoke workflow requirements, a full MYOB Acumatica implementation scoped to your specific situation will serve you better. We'll tell you which applies before any engagement begins. ### **How long does a MYOB Acumatica FastStart implementation take?** Auboros targets go-live within 12 weeks for Wholesale Distribution FastStart projects. That timeline holds when the scope stays fixed, data quality is reasonable for migration, and the client-side project owner can commit around 8 to 9 hours per week. Scope changes or complex data migrations can extend it. ### **What's not included in FastStart?** Custom integrations with third-party platforms, advanced manufacturing, complex project accounting, multi-entity structures, and highly bespoke workflows are outside the FastStart scope. These can be added in a subsequent phase, or scoped as part of a broader implementation from the start if you need them on day one. ### **How does Auboros deliver FastStart for Queensland businesses?** Auboros is [MYOB's FastStart Wholesale Distribution partner in Queensland](/solutions/myob-acumatica-faststart-wholesale-distribution). We work with businesses across South East Queensland and regional QLD. Delivery is a mix of on-site and remote work depending on what stage of the project you're in. Training and go-live support typically involve on-site time to make sure your team has what they need at cutover. ### **Does MYOB Acumatica FastStart handle Australian payroll and GST?** Yes. MYOB Acumatica includes Australian payroll with Single Touch Payroll Phase 2 compliance, GST at 10%, BAS reporting, and superannuation at the current guarantee rate. These are built into the platform. For the latest payroll compliance changes, the [MYOB Enterprise Support payroll compliance page](https://enterprisesupport.myob.com/knowledge/payroll-compliance-changes-au) keeps that current. * * * **Not sure if FastStart is the right fit?** Auboros is MYOB's FastStart Wholesale Distribution implementation partner in Queensland. Our [wholesale distribution ERP page](/industries/wholesale-distribution) covers the wider platform decision for distributors. If you're a wholesale distributor in Brisbane or South East Queensland and want a straight answer on whether FastStart fits your situation, [**book a free consultation**](/appointment). We'll tell you upfront whether FastStart is right or whether a broader implementation is the honest answer. --- # Can You Run Odoo and Xero at the Same Time? - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-xero-run-together-australia-101 - Category: Odoo ERP Australia - Published: 2026-03-18 - Description: Yes, you can run Odoo and Xero at the same time. Here's when it works, when it causes problems, and what the integration actually does and doesn't sync. The short answer is yes. You can run Odoo and Xero at the same time, and plenty of Australian businesses do. [Xero's FY25 half-year results](https://www.xero.com/au/investors/) show 1.9 million subscribers in Australia, which tells you how embedded it is in local accounting teams and bookkeeping practices. When a business starts outgrowing Xero's operational capabilities but its finance team or external accountant lives entirely in Xero, the idea of running both side by side is a reasonable one to explore. But whether you _should_ run both is a different question. We've covered the broader upgrade decision in our [Odoo vs Xero guide](/blog/odoo-erp-australia-6/odoo-vs-xero-when-to-upgrade-from-accounting-to-erp-in-australia-91). This post is specifically for businesses that have already decided they need Odoo for operations and want to know if they can keep Xero for accounting at the same time. ## **Why businesses want to run Odoo and Xero together** The motivation is usually one of three things. The finance team knows Xero well and doesn't want disruption. The external accountant or bookkeeper is already set up in Xero and charges less to work there. Or the business is in a transitional phase, bringing on Odoo for inventory, CRM, or job management while planning to deal with the accounting side later. All of these are legitimate reasons. The problem is that "we'll sort the accounting side later" has a habit of becoming permanent. According to [MYOB's 2025 ERP Trends report](https://www.myob.com/au/insight/post/erp-trends), 45% of Australian decision-makers say disconnected systems are actively limiting their business growth. Running two systems long-term is a choice worth making deliberately, not drifting into. ## **When running both actually makes sense** There are scenarios where an Odoo and Xero integration is the right call, at least for a period: - **Your accountant is genuinely better off in Xero.** If your external bookkeeper is fast and accurate in Xero and switching them would cost more than the integration, keeping Xero for the accounting layer is defensible. - **You're in a planned transition.** If you're bringing Odoo in stages and accounting is the final phase, a temporary integration while staff get trained is a reasonable bridge. - **Xero's bank feeds matter to you.** Xero's bank reconciliation and live bank feed connections are genuinely good. If your team relies on them and you're not ready to replicate that workflow in Odoo Accounting, keeping Xero temporarily makes sense. - **The sync is one-directional and limited.** Odoo generates invoices, those flow into Xero for payment tracking and reconciliation. That's it. When the scope is narrow and clearly defined, the integration is manageable. ## **When the integration causes more problems than it solves** The integration runs into trouble when expectations are too broad. Bidirectional syncing of products, inventory levels, payments, and contacts across two systems creates reconciliation complexity that usually costs more to maintain than it saves. [Capterra's 2026 Software Buying Trends Report](https://newshub.medianet.com.au/2025/10/australian-businesses-risk-overspending-and-disruption-without-smart-software-buying-capterra-report-reveals/126318/), based on 281 Australian business decision-makers, found that fewer than one in three Australian businesses successfully adopt new software without setbacks that affect productivity and budget. Adding integration complexity on top of a new platform implementation is where projects get into trouble. The other issue is visibility. One of the main reasons businesses move to Odoo is to get a real-time view of profitability across operations, inventory, and finance in one place. If your financial data lives in Xero and your operational data lives in Odoo, you don't have that. You have two partial pictures. _"We often talk to businesses that want to keep their accountant happy in Xero while using Odoo to run everything else. That's a reasonable starting point. But it only works if you're clear about which system owns what. The integration breaks down when people expect it to do too much."_ **Josh Craig, Director, Auboros** ## **What the integration actually syncs, and what it doesn't** Third-party Odoo-Xero connectors are available through the [Odoo Apps Store](https://apps.odoo.com/apps/modules/browse?search=xero) for Odoo 17, 18, and 19. What they typically sync: - **Customer invoices and vendor bills:** generated in Odoo, pushed to Xero - **Contact data:** customers and suppliers synced between both systems - **Payments:** recorded in Xero, pulled back into Odoo to reconcile against invoices - **Chart of accounts and tax rules:** mapped at setup What the integration does not handle well: live inventory levels, payroll (Xero Payroll and Odoo Payroll are entirely separate), bank feeds (these stay in Xero), and detailed project or job costing. If you need those to reconcile across systems, you're building a custom integration, not a standard connector. Keep the scope narrow. One-directional. Invoices and payments only. The more you try to sync, the more you'll spend maintaining it. ## **Frequently asked questions** ### **Is there a native Odoo Xero connector?** There is no native, Odoo-built Xero connector. Third-party connectors are available on the [Odoo Apps Store](https://apps.odoo.com/apps/modules/browse?search=xero) and are compatible with Odoo 17, 18, and 19. Quality varies between providers. Before committing to a connector, confirm what it actually syncs, how it handles errors, and what support is available when something breaks. ### **Should I migrate from Xero to Odoo Accounting, or just integrate?** If Odoo is going to be your long-term platform, migrating to Odoo Accounting gives you a single source of truth and removes the ongoing cost of maintaining two systems. Integration makes sense as a transitional measure or when there's a specific reason to keep Xero, such as an existing accountant relationship. If you're unsure, our [Odoo implementation packages](/odoo-implementation-packages-for-australian-businesses) include guidance on the accounting migration decision. ### **Can my accountant still use Xero if my business moves to Odoo?** Yes, with an integration in place. Invoices and payments can flow from Odoo into Xero, meaning your accountant works in Xero as usual while your operations run in Odoo. The practical question is whether the integration cost and complexity is worth keeping that workflow intact, or whether it's simpler to move your accountant to Odoo Accounting with proper training. ### **How long does an Odoo Xero integration take to set up?** A basic connector install and configuration typically takes a few days, assuming your chart of accounts and tax setup are clean in both systems. The longer work is data mapping and testing to make sure invoices are flowing correctly and reconciling properly. Budget for more time than you expect, particularly if your Xero data has inconsistencies that need cleaning before syncing. * * * **Running Odoo alongside Xero in Queensland?** We work with Queensland businesses at every stage of the Odoo journey, from initial implementation through to full accounting migration. If you're weighing up whether to integrate with Xero or move across fully to [Odoo's accounting module](/solutions/odoo), we can give you a straight read on which makes sense for your situation. The integration itself is covered on our [Odoo integration services](/solutions/odoo-integrations) page. If you'd like to talk it through, [**book a free consultation**](/appointment). No obligation, just an honest conversation. --- # ERP Services Gold Coast: Which Platform Fits Your Business in 2026 - Canonical URL: https://www.auboros.com/blog/insights-5/erp-services-gold-coast-100 - Category: Insights - Published: 2026-03-18 - Description: Gold Coast has 83,000+ registered businesses and Australia's fastest-growing economy. Here's which ERP fits your sector, and why local implementation matters. The Gold Coast is [Australia's fastest-growing economy](https://www.goldcoast.qld.gov.au/About-our-city/Gold-Coast-economy) according to the City of Gold Coast's 2024 Economic Outlook. Its gross regional product is forecast to grow 10.07% between 2024 and 2028, [outpacing Brisbane (9.04%) and the national average (7.9%)](https://www.investgoldcoast.com/why-gold-coast/future-growth/economic-outlook). With that growth comes operational pressure: more staff, more projects, more systems held together with spreadsheets and manual exports. According to [Australian Bureau of Statistics business register data](https://economy.id.com.au/gold-coast/number-of-businesses-by-industry), the Gold Coast has 83,266 registered businesses. Construction accounts for 15,355 of them (18.4% of all local businesses), followed by professional and technical services (11,181), transport and warehousing (5,633), manufacturing (3,156), and wholesale trade (2,658). These are the industries where ERP software earns its keep. ## **Why Gold Coast businesses are outgrowing basic software in 2026** Growth is usually what breaks a business's software. Not a dramatic failure, just a slow accumulation of workarounds: an extra spreadsheet for job costing here, a manual export for payroll there, month-end reconciliation that takes longer every quarter. MYOB's [2025 ERP Trends report](https://www.myob.com/au/insight/post/erp-trends) found that 45% of Australian decision-makers say disconnected systems are actively limiting their business growth. The same report documents a business that reduced administrative hours by 62% and increased revenue by 18% after moving to an integrated ERP system. According to MYOB's [2025 Mid-Market Business Survey](https://www.myob.com/au/insight/post/mid-market-survey-results-2025), 36% of Australian mid-sized businesses are currently looking to upgrade or improve their ERP. The top driver is operational efficiency, cited by 48% of respondents. That matches what we see from Gold Coast businesses reaching out to us. They aren't in crisis. They've grown past the point where their current tools keep up. _"The Gold Coast businesses we talk to are often managing construction projects, inventory, and compliance across a patchwork of systems. The cost of that friction shows up in reporting delays, invoicing errors, and staff time that could be spent on actual work."_ **Josh Craig, Director, Auboros** ## **Which ERP fits your Gold Coast business?** The right platform depends on your industry, size, and what you're actually trying to fix. There's no single answer. Here's how we think about it honestly. ### **Odoo for SMEs and growing businesses** Odoo is a modular platform that works well for businesses with roughly 5 to 100 staff. It suits Gold Coast professional and technical services firms, construction trades, retailers, and e-commerce operators, Manufactures, Wholesale. You start with the modules you need and add more as the business grows. The [Odoo Enterprise edition](/solutions/odoo) includes Australian localisation for Business Activity Statement (BAS) reporting, Single Touch Payroll (STP) Phase 2, and superannuation. Compliance is built into the platform, not added on as an afterthought. ### **MYOB Acumatica for mid-market organisations** MYOB Acumatica suits businesses with more operational complexity: wholesale distributors, manufacturers, construction firms managing multiple project cost centres, and professional services organisations needing advanced financial reporting. The Gold Coast has 2,658 registered wholesale businesses and 3,156 manufacturers (ABS data), many of which have grown beyond what AccountRight or MYOB Exo was built to handle. The [MYOB Acumatica platform](/solutions/myob) manages multi-entity financials, project accounting, inventory, and payroll in a single system. For wholesale distribution businesses specifically, Auboros delivers a [FastStart implementation](/solutions/myob-acumatica-faststart-wholesale-distribution) that gets eligible businesses live in 12 weeks. ## **Does it matter where your ERP partner is based?** Yes, more than most vendors will admit. ERP implementation involves discovery sessions, data migration, configuration, user training, and go-live support. When your partner is in Sydney or Melbourne, those activities involve flights, scheduling delays, and consultants who may not be reachable for the smaller but important questions that come up between milestones. There is no MYOB Acumatica implementation partner headquartered on the Gold Coast. Auboros is based in Brisbane, approximately one hour from the Gold Coast. We cover both Odoo and MYOB Acumatica, which is uncommon among Australian ERP partners. Our [published Odoo implementation packages](/odoo-implementation-packages-for-australian-businesses) show exactly what's included at each tier. We don't believe in scope surprises. ## **Frequently asked questions** ### **Is there an ERP consultant based on the Gold Coast?** Specialist ERP implementation partners are not based on the Gold Coast. Most implementations for Gold Coast businesses are delivered by Brisbane, Sydney, or nationally based firms. For MYOB Acumatica specifically, there is no accredited implementation partner headquartered locally. A Brisbane-based partner is the closest practical option for on-site responsiveness when it's needed. ### **What ERP do Gold Coast construction businesses typically use?** Construction is the Gold Coast's largest business sector, accounting for 15,355 registered businesses according to ABS data. Construction firms typically need job costing, project management, subcontractor tracking, and BAS compliance in one place. Both Odoo and MYOB Acumatica support construction, though the right choice depends on your scale. Trade businesses and smaller contractors tend to suit Odoo. Larger contractors managing complex multi-project financials tend to suit MYOB Acumatica. ### **Is there government support available for ERP investment in Australia?** The Australian Government's Digital Economy Strategy committed AUD $1.2 billion to support SME digital technology adoption, including cloud software and ERP systems. State-level grants and incentives also exist at various times. For current programmes, check [business.gov.au](https://business.gov.au/grants-and-programs) before finalising your project budget. ### **How long does ERP implementation take for a Gold Coast business?** A standard Odoo implementation for a small-to-mid-sized business typically takes 8 to 16 weeks from project kick-off to go-live. A MYOB Acumatica implementation for wholesale distribution can be delivered in 12 weeks through the FastStart programme. More complex projects with custom development or large data migrations take longer. The biggest variable is almost always internal readiness, not the software. * * * **ERP for Gold Coast and Southeast Queensland businesses** We work with businesses across Southeast Queensland on both Odoo and MYOB Acumatica. Whether you're on the Gold Coast, Sunshine Coast, or anywhere in the region, we can talk through which platform makes sense before you commit to anything. If you're evaluating ERP options or want an honest read on where your current systems are holding you back, [**book a free consultation**](/appointment). No pitch, just a straight conversation. --- # MYOB Acumatica Consulting: What to Look for in a Partner - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-consulting-what-to-look-for-99 - Category: MYOB Acumatica Australia - Published: 2026-03-18 - Description: Not all MYOB Acumatica partners are equal. Here's what separates a good implementation from a difficult one, and what to check before you sign anything. Most ERP implementations don't fail because of the software. They fail because of the partner. Rushed discovery, under-scoped projects, consultants who've never worked in your industry, and post-go-live support that's essentially non-existent. These are common patterns, and they're expensive to recover from. Choosing the right MYOB Acumatica consulting partner is probably more important than choosing MYOB Acumatica itself. This guide covers what actually separates competent partners from the rest, what questions to ask before you commit, and what red flags look like in practice. ## **MYOB Acumatica partner vs MYOB consultant: what's the difference?** A MYOB consultant typically handles day-to-day support, payroll queries, or basic configuration changes on an existing system. They're useful when you already have MYOB Acumatica running and need help with specific tasks. A certified MYOB Acumatica implementation partner is accredited by MYOB to deliver full implementations. That means scoping the project, migrating your data, configuring the system to your processes, training your team, and managing go-live. It's a different engagement entirely. If you're starting from scratch, upgrading from AccountRight or MYOB Exo, or replacing another ERP, you need a partner, not a consultant. MYOB Acumatica is not a software-as-a-service product you can set up yourself in an afternoon. It's a mid-market ERP platform with significant configuration depth. The quality of that configuration determines how much value you get out of it. ## **The criteria that actually matter when choosing MYOB Acumatica consulting services** ### **Official MYOB Acumatica accreditation** Start here. Not all MYOB partners are MYOB Acumatica partners. Some are accredited for AccountRight, Exo, or payroll products only. You want a partner who is officially accredited by MYOB for Acumatica implementations specifically. Ask them directly, and verify it. [MYOB's own product pages](https://www.myob.com/au/erp-software/products/myob-acumatica) list accredited partners, and you can confirm a partner's status through MYOB's channel team. ### **Experience in your industry** MYOB Acumatica can be configured for wholesale distribution, manufacturing, construction, project accounting, professional services, and more. But each of those industries requires different module choices, reporting structures, and workflow designs. A partner who has implemented MYOB Acumatica for a professional services firm ten times will ask different questions during discovery than one doing it for the first time in your sector. Ask for references from businesses similar to yours, not just a general client list. ### **A methodology, not just a timeline** Good partners have a documented implementation methodology. They can explain how they approach discovery, how they handle scope changes, what the testing phase looks like, and how they run go-live. If a partner's proposal consists of a start date, an end date, and a price, ask more questions. ERP projects that skip proper scoping and testing are the ones that go badly. ### **Honest scoping and risk conversations** Any implementation carries three types of risk: software risk (will the platform do what you need?), implementer risk (does the partner have the skills?), and self-inflicted risk (can your team commit the time required?). A good partner surfaces all three and talks about them plainly. Be cautious of partners who tell you everything will be simple. MYOB Acumatica implementations involve real complexity, and partners who acknowledge that are the ones who plan for it. ### **Post-go-live support that's actually included** Going live is not the end of the project. Staff need time to build confidence in the new system. Processes that looked clear during training feel different under real operating pressure. A good partner has a clear post-go-live plan that includes a hyper-care period, defined support channels, and response time commitments. Ask specifically what support looks like in the 60 days after go-live and what's included in the ongoing support arrangement. For more on what MYOB Acumatica support typically includes, see our guide to [what's included and what's extra](/blog/myob-acumatica-australia-7/myob-acumatica-support-what-s-included-and-what-you-ll-pay-extra-for-96). ## **Questions to ask before you sign** These questions will tell you a lot about a partner before any contract is signed: - **How many MYOB Acumatica implementations have you completed in my industry?** You want a specific number, not a vague answer about "extensive experience." - **Who will actually be working on my project?** Some partners pitch senior consultants and deliver with junior staff. Ask who your project lead will be and whether they'll be with you through the whole engagement. - **What happens if the project scope changes?** Change is normal in ERP projects. The question is how the partner handles it, and whether the contract allows for honest conversations about it. - **What does the data migration process look like?** Data migration is consistently one of the hardest parts of any implementation. If a partner brushes it off, that's a warning sign. - **Can you give me references from businesses similar in size and industry to ours?** Talking to a past client directly is the most reliable way to assess a partner's track record. ## **What to watch out for** A few patterns consistently show up in implementation projects that go poorly. Low initial quotes that grow significantly once the project is underway. Proposals that treat your data migration as a minor task. Consultants who suggest going live before your team is ready to reduce their hours on the project. And partners who are hard to reach between milestone payments. The long-term cost of recovering from a poor implementation far exceeds the short-term cost of choosing a more thorough partner upfront. This is not a purchase you want to make twice. ## **Frequently asked questions** ### **How many MYOB Acumatica partners are there in Australia?** There are dozens of accredited MYOB Acumatica partners across Australia, ranging from large national firms to smaller boutique consultancies. The quality and specialisation varies significantly. Being accredited is a baseline requirement, not a quality guarantee. Experience in your specific industry and the depth of your partner's MYOB Acumatica team are more useful indicators than partner size alone. ### **Does it matter if my MYOB Acumatica partner is based in Queensland?** Most major MYOB Acumatica partners are based in Sydney, Melbourne, or have national operations. For Queensland businesses, particularly those outside Brisbane, this means fly-in consultants for on-site work and potential delays when you need urgent help. A Queensland-based partner can respond faster and will understand the local business environment, including industries like resources, construction, and agribusiness that have a strong presence in Queensland specifically. ### **What's the difference between MYOB Acumatica consulting and MYOB Acumatica support?** Consulting typically refers to implementation and project work: configuring the system, migrating data, building integrations, and delivering training. Support refers to the ongoing relationship after go-live: answering questions, resolving issues, handling system updates, and making incremental changes as your business evolves. A good partner provides both, and you should understand from the start how the handover from implementation to support works. ### **What should I expect from a first conversation with a MYOB Acumatica partner?** A good first conversation should involve the partner asking about your business, your current systems, and what problems you're trying to solve, not leading with a product demonstration. They should ask about your industry, your team size, your go-live timeline, and your budget range. If the first conversation is mostly about MYOB Acumatica features rather than your specific situation, that's worth noting. * * * **Looking for a MYOB Acumatica consulting partner in Queensland?** Auboros is an Official MYOB Acumatica Partner based in Brisbane. We work with mid-market businesses across Queensland on implementations, customisation, and ongoing support. We're also an [Exclusive Queensland partner for FastStart Wholesale Distribution](/solutions/myob), which means businesses in distribution can go live in as little as 12 weeks. If you're evaluating MYOB Acumatica or wondering whether it's the right fit for your business, [**book a free consultation**](/appointment). We'll give you an honest assessment of whether it suits your situation. --- # Odoo Australian Localisation: BAS Reporting, STP Phase 2, and What Actually Changed in v19 - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-australian-localisation-bas-stp-v19-98 - Category: Odoo ERP Australia - Published: 2026-03-17 - Description: How Odoo handles BAS reporting and STP Phase 2, what the v19 Superchoice API integration changes, and what Australian businesses need to set up correctly. If you're evaluating Odoo for an Australian business, or you're already live and wondering whether the compliance side is properly configured, the short answer is: yes, Odoo handles Australian BAS reporting and payroll compliance, and the v19 release made both significantly better. The longer answer involves understanding what's in the base localisation, what requires Enterprise, and what specifically changed when Odoo moved from v18 to v19. That last part matters more than most people realise. One of the v19 changes makes Odoo one of the few mid-market ERP platforms where STP Phase 2 lodgement and SuperStream contributions are both handled natively, without a separate clearing house or third-party payroll product. ## **What the Odoo Australian localisation includes** The Australian localisation is not a single module. It's a layered set of modules that build on each other, and understanding which layer does what determines whether your setup will actually work for compliance purposes. ### **Community vs Enterprise: what each edition provides** The base Community module (`l10n_au`) installs the Australian chart of accounts, GST tax codes, tax positions, and fiscal rules. This gives you the correct account structure and 10% GST treatment on sales and purchases, along with GST-free, export, and capital purchase variants. This layer is the same in both Community and Enterprise. The BAS report itself, payroll compliance, and STP lodgement all require Enterprise modules. Specifically, BAS reporting needs `account_reports` and `account_reports_cash_basis`, which auto-install `l10n_au_reports` and provide the full BAS report, TPAR, and closing journal functionality. Payroll compliance is handled by `l10n_au_hr_payroll`, and the new v19 direct lodgement capability lives in `l10n_au_hr_payroll_api`. If you're a GST-registered employer running Odoo Community, you have the chart of accounts but none of the compliance reporting or STP lodgement. That gap is worth being clear-eyed about before committing to a Community-based implementation. You can review what [our Odoo implementation services](/solutions/odoo) include across both editions. ## **BAS reporting in Odoo: which form, how it works, and what to configure** The Business Activity Statement (BAS) is the ATO's mechanism for collecting GST, PAYG withholding, and other tax obligations in one periodic lodgement. Odoo handles BAS reporting natively once the Enterprise localisation is installed, with the report accessible from **Accounting > Reports > BAS Report (AU)**. ### **Which BAS form your business uses** Odoo comes loaded with all seven BAS form variants the ATO uses. Most businesses work with one of these, but it's worth knowing the full set: - **BAS-A:** Full form covering GST and PAYG withholding. The most common form for businesses registered for both. - **BAS-C:** Instalment amount form, used when the ATO has pre-calculated your GST instalment. - **BAS-G:** GST only, no PAYG withholding. For entities with no employee withholding obligations. - **BAS-U:** Annual PAYG instalment payers making quarterly contributions. - **BAS-V:** Quarterly GST instalment with tax withheld. - **BAS-Y:** Annual GST return for businesses registered for annual reporting. - **Master BAS:** Odoo's internal template that the other forms inherit from. You won't use this directly. Confirm which form applies with your accountant before go-live rather than assuming BAS-A is correct. In most cases it will be, but the [ATO's BAS guide](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/activity-statements/completing-your-business-activity-statement) covers each scenario. Before you post your first BAS closing entry, set your GST payable and GST receivable accounts in the tax group configuration. Odoo prompts you if these are missing, but it's easy to skip past during a busy go-live. Also go to **Accounting > Configuration > Settings** and configure your tax return periodicity (monthly or quarterly) and fiscal year end date. For most Australian businesses that's 30 June. ### **PAYG withholding: the W1 to W5 sections in your BAS** If you're running Odoo Payroll, PAYG (Pay As You Go) withholding flows automatically into the W1 to W5 sections of your BAS. W1 captures total gross wages and other payments subject to withholding. W2 captures the total amount withheld. These figures come directly from your processed payslips: no export, no manual reconciliation, no end-of-quarter data entry between two systems. It's one of the more practical advantages of running payroll and accounting on the same platform. For a full picture of how the implementation fits together, our [Odoo ERP implementation guide for Australia](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) covers the end-to-end process. ## **TPAR: the annual report many service businesses don't know about** The [Taxable Payments Annual Report (TPAR)](https://www.ato.gov.au/businesses-and-organisations/income-deductions-and-concessions/income-you-must-declare/taxable-payments-reporting-system) is a separate ATO obligation from the BAS. If your business is in building and construction, cleaning, couriers, IT, security, or road freight, you're required to report all payments made to contractors and subcontractors to the ATO annually. TPAR is due by 28 August each year and has nothing to do with your quarterly BAS cycle. Odoo includes a TPAR report in `l10n_au_reports`. It identifies reportable payments via the `Service` and `Tax Withheld` tax tags on journal items. The critical thing: getting TPAR right depends on your fiscal positions and product types being configured correctly from day one. If you're in a TPAR-relevant industry and you start processing supplier invoices before those tags are set up, you'll face a messy retroactive fix before August. It's one of the areas our [Odoo implementation packages](/odoo-implementation-packages-for-australian-businesses) specifically review during the accounting configuration phase. ## **Odoo Payroll for Australian compliance** ### **STP Phase 2: what's required and what Odoo covers** Single Touch Payroll (STP) Phase 2 requires employers to submit a detailed breakdown of payroll data to the [ATO](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll) each pay run. Where Phase 1 required gross wages and tax withheld, Phase 2 goes further: it requires disaggregated gross income reported by income stream type, salary sacrifice amounts reported separately rather than netted off, and additional detail that the ATO uses to pre-fill individual tax returns and validate super contributions. Odoo v19 supports all ten STP Phase 2 income stream types: salary and wages (SAW), closely held payees (CHP), inbound assignees to Australia (IAA), working holiday makers (WHM), PALM scheme workers (SWP/PALM), foreign employment income (FEI), joint petroleum development area (JPD), voluntary agreement (VOL), labour hire (LAB), and other specified payments (OSP). This is the full set the ATO requires. All ten are implemented in the v19 payslip model. ### **Superannuation: rates and how Odoo applies them** The compulsory super guarantee rate is currently 12%, effective from 1 July 2025. Odoo's payroll module has the full legislated rate schedule hardcoded correctly: 11% from January 2023, 11.5% from July 2024, and 12% from July 2025. When you process a pay run, Odoo applies the rate based on the physical pay date. You don't need to update anything manually at the start of each financial year. The [ATO publishes the current rate and schedule](https://www.ato.gov.au/individuals-and-families/super-for-individuals-and-families/super/growing-and-keeping-track-of-your-super/how-much-super-to-pay) if you need to verify what applied in prior periods. ## **What actually changed from Odoo v18 to v19 for Australian businesses** This is the section that matters most if you're deciding whether to implement on v19, or whether to upgrade from an earlier version. The changes aren't cosmetic. For Australian businesses specifically, v19 includes the most significant compliance advancement the platform has made. ### **Direct STP lodgement via the Superchoice API: new in v19** In v18, Odoo generated the STP Phase 2 XML file correctly, but you still needed a separate clearing house to actually submit it to the ATO. You'd export from Odoo, upload to a third-party service, and manage the status there. That workflow is gone in v19. The new `l10n_au_hr_payroll_api` module, which does not exist at all in v18, integrates directly with the Superchoice API. STP Phase 2 lodgement happens from within Odoo, and the status updates in real time inside the same screen. The full ATO status lifecycle is tracked in the system: Draft, Submitted, ATO Pending, Accepted, and Failed. If a lodgement fails with an ATO validation error, the error message surfaces in Odoo directly. You can't delete an STP record that's already been submitted to the ATO. The system prevents it, which is the correct compliance behaviour. In practical terms: you finalise your pay run, submit the STP report, and track its acceptance with the ATO, all within Odoo. No separate clearing house account, no manual export, no status-checking in a third-party portal. ### **SuperStream contributions handled natively** The same `l10n_au_hr_payroll_api` module also handles SuperStream contributions natively through Superchoice acting as the clearing house. The full payment lifecycle is tracked inside Odoo: Employer Pending (direct debit initiated), Fund Pending (debit cleared, fund payment initiated), Success, and Cancelled. If a fund payment is dishonoured or needs to be cancelled, that's managed from within Odoo rather than through a separate clearing house portal. Previously, super contributions required either a manual SuperStream submission through a separate service or the Small Business Superannuation Clearing House. In v19, both STP lodgement and super contributions run through the same integrated channel. That's a meaningful reduction in the number of systems an Australian employer needs to operate for payroll compliance. ### **ATO-mandated security controls now enforced by the module** The ATO requires specific security controls for systems that access its payroll reporting infrastructure. In v19, these controls are enforced by the `l10n_au_hr_payroll_api` module rather than relying on administrators to configure them manually. Privileged Australian payroll and accounting users have TOTP-based multi-factor authentication required at login. The system enforces this; it's not optional. Social OAuth login via Facebook is blocked for internal users with the Australian payroll integration installed. Sensitive payroll field changes trigger audit log entries that are synced to Superchoice. The 30-minute inactivity timeout and 24-hour session timeout are applied to privileged users automatically. These aren't configuration options an administrator might forget to turn on. They're module-level requirements that activate when the Australian payroll API integration is installed. ### **BAS quarterly calendar fix and W1-W5 closing** Two BAS-specific improvements also landed in v19. First, the quarterly calendar fix: in v18 and earlier, Odoo used calendar quarters internally, which meant July to September appeared as Q3 rather than Q1 in Australian terms. If you've been on v18 and your BAS quarters looked misaligned with the ATO's reporting periods, that's the cause. V19 corrects this: July is now correctly treated as Q1. Second, v19 adds BAS report closing for the PAYG withholding sections (W1 to W5), which was not available in earlier versions. BAS figures now also round down by default to meet ATO requirements, and pre-loaded 2025-26 tax rates mean you don't need to update anything manually at the start of the new financial year. ## **Frequently asked questions** ### **Does Odoo submit STP Phase 2 directly to the ATO?** Yes, in Odoo v19 Enterprise. The `l10n_au_hr_payroll_api` module submits STP Phase 2 reports directly to the ATO via the Superchoice API from within Odoo. Status tracking (Draft, Submitted, ATO Pending, Accepted, Failed) is visible inside the system. This functionality does not exist in v18, where Odoo generated the STP XML but required a separate clearing house to complete the lodgement. ### **Does Odoo Community include BAS reporting?** Community includes the Australian chart of accounts and GST tax codes, but not the BAS report. The BAS report, TPAR, and BAS closing functionality require the `account_reports` and `account_reports_cash_basis` Enterprise modules. For any GST-registered business, Community alone is not sufficient for BAS compliance reporting. ### **What is the difference between Odoo v18 and v19 for Australian compliance?** The major difference is the `l10n_au_hr_payroll_api` module, which is new in v19 and does not exist in v18. It adds direct STP Phase 2 lodgement via the Superchoice API, native SuperStream contribution management, ATO-mandated security controls enforced at the module level, and payroll audit logging. On the BAS side, v19 fixes the quarterly calendar alignment and adds W1-W5 BAS closing support. Together these make v19 a significantly more capable compliance platform for Australian employers than v18. ### **Do I need to upgrade to v19 to get the Superchoice integration?** Yes. The direct STP lodgement and SuperStream functionality via Superchoice is specific to v19 Enterprise and the `l10n_au_hr_payroll_api` module. It is not available as a backport to v18. If you're currently on v18 and using a separate clearing house for STP submissions, upgrading to v19 is the path to consolidating that into Odoo directly. * * * **Getting the Australian localisation configured correctly from day one** We implement Odoo v19 for Australian businesses across Queensland, NSW, and Victoria, with the accounting localisation, BAS reporting, TPAR configuration, and payroll compliance set up correctly before a single live transaction is processed. If you're planning a new implementation or assessing an upgrade from v18, [**book a free consultation**](/appointment). We'll walk through what's relevant to your specific business and flag anything that needs attention before go-live. --- # MYOB Acumatica Payroll: What Australian Businesses Need to Know Before 1 July 2026 - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-payroll-what-australian-businesses-need-to-know-before-1-july-2026-97 - Category: MYOB Acumatica Australia - Published: 2026-03-17 - Description: MYOB Acumatica Payroll handles STP Phase 2 and the 12% super guarantee. What's changing for Australian businesses before Payday Super starts 1 July 2026 Three major payroll compliance changes are landing for Australian employers in 2026. The super guarantee rate is already at 12%. Payday Super starts 1 July 2026, shifting superannuation from a quarterly obligation to something that happens every single pay run. And MYOB Exo Payroll reaches end of life in November 2026. If you're running MYOB Acumatica Payroll or evaluating whether to move to it, here's what the platform covers and what you need to have sorted before July arrives. ## **What MYOB Acumatica Payroll covers** [MYOB Acumatica Payroll](https://www.myob.com/au/erp-software/products/myob-acumatica-payroll) is a cloud-based payroll module built specifically for Australian and New Zealand compliance. It handles Single Touch Payroll (STP) Phase 2 lodgement, superannuation contributions, PAYG withholding, leave accruals, award rate interpretation, and Employment Termination Payment (ETP) calculations. It's integrated natively with the MYOB Acumatica accounting and HR modules, which means payroll journal entries post directly to the general ledger without a separate export or import step. That integration is a meaningful practical difference from standalone payroll products. When payroll and financials sit in the same system, you're not reconciling two sets of numbers at month end, and the super liability, PAYG withholding, and wages expense land in the right accounts automatically. If you'd like to understand what [MYOB Acumatica implementation](/solutions/myob) looks like for a mid-market business, our team can walk through your specific situation. ## **Single Touch Payroll (STP) Phase 2: what it requires and how MYOB Acumatica handles it** Single Touch Payroll Phase 1 required employers to report gross wages and tax withheld each pay run. Phase 2 goes further: it requires a disaggregated breakdown of gross income, separated by income stream type (salary and wages, closely held payees, working holiday makers, and several others), plus salary sacrifice amounts reported separately rather than netted off. The ATO uses this detail to pre-fill individual tax returns and calculate super contributions correctly. MYOB Acumatica Payroll is STP Phase 2 compliant. Each time you finalise a pay run, the required data submits directly to the ATO from within the platform. There's no separate reporting tool or clearing house required for STP submissions, and status tracking is visible in the system so you can see whether a lodgement is accepted, pending, or has returned an error. The [payroll compliance changes documentation](https://enterprisesupport.myob.com/knowledge/payroll-compliance-changes-au) from MYOB covers the specific field-level requirements for Phase 2 in detail. ## **The superannuation guarantee rate in FY2026** The compulsory super guarantee rate increased to 12% from 1 July 2025. This is the final step in a legislated schedule of annual increases that's been running since 2021. MYOB Acumatica Payroll applies the current rate automatically when you open a pay run with a physical pay date on or after 1 July 2025. No manual adjustment is required. The [ATO publishes the current rate](https://www.ato.gov.au/individuals-and-families/super-for-individuals-and-families/super/growing-and-keeping-track-of-your-super/how-much-super-to-pay) and historical schedule if you need to verify what applied in earlier periods. One change that often gets missed in the 12% conversation: paid parental leave now also attracts a super contribution for babies born or adopted on or after 1 July 2025. The government pays 12% super on top of the funded parental leave payment, directly to the employee's nominated fund. This is a change from previous arrangements and is worth noting in your payroll configuration if you have employees accessing the scheme. ## **Payday Super: the major change arriving 1 July 2026** From 1 July 2026, all Australian employers must pay superannuation at the same time as wages. Contributions need to reach the employee's fund within 7 business days of the pay date. This is a significant operational shift for businesses that currently pay super quarterly or even monthly. ### **What "at the same time as wages" means for your cash flow** The practical impact is straightforward but worth planning for: instead of four super payments per year, a fortnightly payroll means 26 super payments. The quarterly super lump sum that many businesses used to smooth their cash flow disappears. Treasury modelling suggests employees accumulate meaningfully more super over their working lives under Payday Super, because contributions start compounding immediately rather than sitting in employer accounts for weeks or months before being transferred. MYOB has confirmed its products will be updated to support [Payday Super requirements](https://www.myob.com/au/resources/guides/payroll/payday-super) ahead of the deadline. The ATO has also indicated that in the first 12 months it will take an education-focused approach to compliance for employers that are genuinely trying to meet the new requirements. That's some comfort if you hit teething issues, but it doesn't mean planning can wait until June. ### **The Small Business Superannuation Clearing House closes on the same date** The Australian Taxation Office's Small Business Superannuation Clearing House (SBSCH) closes to all users on 1 July 2026, the same day Payday Super begins. If any of your employees currently have their super contributions processed through the SBSCH, you'll need an alternative clearing house arrangement in place before that date. MYOB Acumatica Payroll processes super contributions through its own integrated clearing house, so for businesses already on the platform this transition should be managed within the product. Confirm this with your implementation partner or MYOB support if you're unsure how your current setup routes contributions. ## **Other 2025-26 compliance changes affecting MYOB Acumatica Payroll** Beyond the super guarantee rate and Payday Super, a few other changes are in effect for the current financial year. [MYOB's compliance changes documentation](https://enterprisesupport.myob.com/knowledge/payroll-compliance-changes-au) covers these in full, but the key items are: - **Lump sum E threshold removed.** The ATO removed the $1,200 reporting threshold for lump sum E amounts. This affects how certain back payments are reported through STP, and applies to payments made on or after 1 July 2024. - **Student loan repayment threshold increased.** The compulsory repayment threshold rose to $67,000. Employees with HELP, VSL, or SSL debts have adjusted withholding calculations as a result. - **ETP thresholds updated.** Employment Termination Payment whole-of-income cap and ETP cap amounts are indexed annually. MYOB Acumatica Payroll applies the current year figures automatically. - **Paid parental leave super.** Government-funded parental leave for eligible parents now attracts 12% super, paid directly by the government to the employee's fund. This is a new obligation separate from employer-funded parental leave. ## **MYOB Exo Payroll end of life: what November 2026 means for your business** MYOB has announced that MYOB Exo Employer Services reaches end of life in November 2026. After that date, MYOB will no longer provide support, updates, or compliance patches for the product. Running payroll on unsupported software after November means no ATO-mandated compliance updates when payroll legislation changes again, and it will change. STP requirements, super rates, tax thresholds, and award interpretations all evolve, and an unsupported product won't keep pace. MYOB Acumatica Payroll is the supported migration destination for Exo users, particularly those with the complexity that justified Exo in the first place, such as multi-entity payroll, complex award structures, or ERP integration requirements. If you're on Exo and haven't started planning the migration, November 2026 is closer than it feels. Our page on [MYOB Acumatica implementation services](/solutions/myob) covers what a migration typically involves, and what to look for in what's included in [ongoing MYOB Acumatica support](/blog/myob-acumatica-australia-7/myob-acumatica-support-what-s-included-and-what-you-ll-pay-extra-for-96) once you're live. ## **Frequently asked questions about MYOB Acumatica Payroll in Australia** ### **Is MYOB Acumatica Payroll STP Phase 2 compliant?** Yes. MYOB Acumatica Payroll is STP Phase 2 compliant. Each pay run submits the required disaggregated data directly to the ATO from within the platform. No separate reporting tool or clearing house is required for STP submissions, and lodgement status is visible in the system. ### **What is Payday Super and when does it start?** Payday Super requires all Australian employers to pay superannuation contributions at the same time as wages rather than quarterly. It starts 1 July 2026. Contributions must reach the employee's super fund within 7 business days of the pay date. MYOB Acumatica Payroll is being updated to support this requirement ahead of the deadline. ### **What is the current superannuation guarantee rate in Australia?** The current compulsory super guarantee rate is 12%, effective from 1 July 2025. MYOB Acumatica Payroll applies this rate automatically based on each employee's pay date. The ATO publishes the current rate and historical schedule at [ato.gov.au](https://www.ato.gov.au/individuals-and-families/super-for-individuals-and-families/super/growing-and-keeping-track-of-your-super/how-much-super-to-pay). ### **What happens to MYOB Exo Payroll after November 2026?** MYOB will no longer provide support, updates, or compliance patches for Exo Employer Services after November 2026. Running payroll on an unsupported product after that date means no updates when tax rates, super rules, or STP requirements change. Migration to MYOB Acumatica Payroll is the supported path forward, and planning the transition now rather than in September is strongly advisable. * * * **Getting your payroll ready for Payday Super and beyond** We work with mid-market businesses across Queensland, NSW, and Victoria on MYOB Acumatica implementations, including businesses migrating off Exo Payroll and those with complex award structures or multi-entity payroll requirements. If you're assessing whether MYOB Acumatica Payroll fits your situation, or want to understand what a migration from Exo involves, [**book a free consultation**](/appointment). We'll give you a straight answer on fit and what implementation typically looks like. --- # Odoo Manufacturing Module: The Australian Guide to MRP, Work Orders and Shop Floor - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-manufacturing-module-the-australian-guide-to-mrp-work-orders-and-shop-floor-95 - Category: Odoo ERP Australia - Published: 2026-03-15 - Description: Everything Australian manufacturers need to know about Odoo's MRP module: bills of materials, work orders, shop floor, quality and what it costs to run. If you're running a manufacturing business in Australia and you're looking at Odoo, you'll quickly notice that "manufacturing" isn't a single module. It's a cluster of them. MRP, Quality, Maintenance, PLM, Shop Floor. They connect, but they also each do something distinct. This guide explains what each one does, which ones you actually need, and what manufacturing in Odoo looks like when it's running well. ## **What the Odoo manufacturing module actually includes** The core module is Manufacturing (also called MRP, or Material Requirements Planning). It handles bills of materials, manufacturing orders, work orders, and production scheduling. That's the foundation. On top of it, Odoo offers several companion modules that most manufacturers will use in some combination: - **Manufacturing (MRP):** Bills of materials, manufacturing orders, components, work centres, routing, and production scheduling. - **Shop Floor:** A tablet-based interface for operators on the production line. They can log time, confirm steps, report scrap, and raise quality alerts without leaving the floor. - **Quality:** Define quality control points, create quality alerts, manage non-conformances, and link checks to specific production steps. - **Maintenance:** Preventive and reactive maintenance for equipment, with work orders, scheduled intervals, and OEE (Overall Equipment Effectiveness) tracking. - **PLM (Product Lifecycle Management):** Manage engineering change orders (ECOs), version-control BOMs, and push approved changes directly into production. - **Master Production Scheduling (MPS):** A demand forecasting and planning dashboard, useful for aligning sales forecasts with production capacity. Most of these are available in both Community and Enterprise, though some advanced features, including the full MPS dashboard, PLM, and the Shop Floor app, require [Odoo Enterprise](https://www.odoo.com/app/manufacturing). If you're running a production operation of any real complexity, Enterprise is where you'll need to be. ## **Bills of materials and production planning in Odoo** The bill of materials (BOM) is the starting point for everything in Odoo manufacturing. A BOM defines what goes into a product: the components, their quantities, and (optionally) the operations needed to assemble or produce it. Odoo supports multi-level BOMs, which means components can themselves be manufactured sub-assemblies. This is useful for products with complex supply chains or kitted finished goods. You can create variant-specific BOMs when the same product comes in different configurations (colour, size, spec), and phantom BOMs for sub-assemblies that are built directly into the parent order without generating their own separate manufacturing order. This covers most of what discrete manufacturers need. For process manufacturers in food and beverage, chemicals, and cosmetics, Odoo handles recipes, by-products, and lot-based traceability. You can track batch numbers from raw material intake through to finished goods dispatch, which matters for food safety audits and compliance with Australian food standards. Production planning in Odoo runs through two mechanisms. The MRP scheduler generates replenishment orders based on current stock, forecasted demand, and safety stock rules. It can trigger purchase orders and manufacturing orders automatically. For longer-horizon planning, the Master Production Schedule gives you a visual demand-versus-capacity view, letting you plan by week or month and adjust before you hit the floor. ## **Work orders, routings and shop floor management** A manufacturing order in Odoo represents what you're making and how many. Work orders sit inside that manufacturing order and represent the individual steps: cut, weld, assemble, test, pack. Each work order is assigned to a work centre (a machine, a production line, or a team) and Odoo tracks time, progress, and output at that level. Routings define the sequence of work orders. Once you attach a routing to a BOM, any manufacturing order using that BOM will automatically generate the correct work order sequence. You can configure parallel or sequential steps, and Odoo will schedule them against work centre availability. The [Shop Floor app](https://www.odoo.com/documentation/19.0/applications/inventory_and_mrp/manufacturing.html) is where this becomes practically useful. Operators at a work centre see only what's relevant to them. They tap to start, log steps, scan components, report scrap, or flag a quality issue, all from a tablet on the floor. The system records actual versus planned time, which feeds into work centre efficiency reporting. For Australian manufacturers, this integration between work orders and inventory is particularly valuable. When a component is consumed in a work order, Odoo updates stock in real time. There's no end-of-day stock count or manual reconciliation. The numbers are current as production runs. ## **Quality, maintenance and PLM: the modules you'll actually use** The Quality module lets you define checkpoints at specific points in the production flow: at goods receipt, during a particular work order step, or before shipping. When a manufacturing order hits that checkpoint, the system prompts the operator to complete the check. If they find an issue, they can raise a quality alert and trigger a non-conformance workflow. This is useful for businesses working toward ISO 9001, for food manufacturers who need HACCP documentation, or for any business that currently manages quality through spreadsheets and wants a proper audit trail. All quality records are tied back to the specific manufacturing order, batch, and operator. The Maintenance module handles equipment upkeep. You define your machines and their maintenance schedules, based on time intervals, metre readings, or production counts, and Odoo generates maintenance work orders on schedule. When a machine breaks down unexpectedly, operators can trigger a corrective maintenance request directly from the Shop Floor app. Downtime and mean time between failures (MTBF) are tracked automatically. PLM is useful once your products are complex enough that engineering changes are a regular occurrence. When a design needs updating, an Engineering Change Order (ECO) captures the proposed change, routes it for approval, and once approved pushes the updated BOM and routing directly into production. There's no risk of a work centre running an outdated version. ## **What Odoo manufacturing looks like for Australian businesses** We work with Australian manufacturers across discrete and process production environments. The businesses that get the most out of Odoo manufacturing tend to share a few characteristics: they've outgrown spreadsheets and disconnected tools, they need visibility across purchasing, production, and inventory in one place, and they want something that handles Australian compliance without a pile of workarounds. On the compliance side, Odoo's accounting integrates directly with manufacturing costing. When you complete a manufacturing order, the cost of components and labour posts automatically to your accounts. Business Activity Statement (BAS) reporting, GST treatment, and [ATO compliance](https://www.ato.gov.au/businesses-and-organisations/gst-excise-and-indirect-taxes/gst) work through Odoo's Australian localisation, the same one used for non-manufacturing businesses, extended to cover manufacturing-related transactions. For make-to-order businesses, Odoo links sales orders directly to manufacturing orders. A confirmed sale triggers production automatically, and the customer's order status reflects real production progress. For make-to-stock businesses, replenishment rules and MPS handle the planning layer. Businesses that run both models, which is common in food manufacturing and industrial components, can configure different rules by product category. Multi-warehouse and multi-location inventory works across production too. If you have raw material stores, a work-in-progress location, and finished goods all under one roof (or across multiple sites), Odoo tracks stock movements at each location throughout the production process. As a certified [Odoo Silver Partner](/solutions/odoo), we've implemented manufacturing modules for businesses across Queensland, NSW, and Victoria. The implementation approach matters. A well-configured manufacturing setup takes time and process mapping upfront, but it's worth doing properly. You can see what a typical [Odoo implementation in Australia](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) involves in our full guide. ## **What Odoo manufacturing doesn't do well (and what to watch for)** Odoo is a strong fit for discrete and light process manufacturing. It's less suited, without significant customisation, to industries with very complex process manufacturing requirements: pharmaceuticals with full GMP validation, continuous-flow chemical production, or environments where regulatory documentation requirements are unusually heavy. The MPS module works well for planning, but it's not as sophisticated as a dedicated advanced planning and scheduling (APS) tool. If you're in an environment with very tight capacity constraints, a complex machine mix, and overlapping production runs that need optimisation, you may hit the limits of native Odoo scheduling. That said, for most SME manufacturers in Australia, the native tools are more than enough. Odoo Community (the free version) includes a basic MRP module, but Quality, Maintenance, PLM, and the Shop Floor app all require Enterprise. If you're evaluating Odoo and you're a manufacturer, factor this into your [cost planning](/odoo-implementation-packages-for-australian-businesses). The Enterprise licence is per user, per month, and the manufacturing companion modules are included in that price at no extra charge per module. ## **Frequently asked questions** ### **Does Odoo support make-to-order and make-to-stock manufacturing?** Yes. Odoo supports make-to-order, make-to-stock, and engineer-to-order workflows. You can configure different reordering rules by product, and set some products to trigger manufacturing automatically on sale confirmation while others are planned through MPS or manual orders. ### **Can Odoo handle multi-level bills of materials?** Yes. Multi-level BOMs are a standard feature in Odoo manufacturing. You can define sub-assemblies with their own BOMs and nest them inside a parent BOM. Odoo can explode the full BOM tree to calculate total material requirements, and you can choose whether sub-assemblies are manufactured separately or as phantom (built inline). ### **Is the Odoo Shop Floor app available on tablets?** Yes. The Shop Floor app is designed for tablet use and can run in a browser on any device. Operators can start and stop work orders, log actual time, confirm production steps, scan barcodes, report scrap, and raise quality alerts, all without needing desktop access to the full Odoo system. ### **Does Odoo manufacturing integrate with Odoo Inventory and Accounting?** Yes, and this is one of its main advantages. Component consumption updates inventory in real time, and manufacturing order costs post directly to your accounts when production is complete. There's no separate data import or reconciliation step between your production records and your financials. ### **Is Odoo manufacturing suitable for Australian food and beverage producers?** It works well for most food and beverage manufacturers, particularly those needing lot traceability, recipe management, by-product handling, and quality checkpoints. Odoo supports HACCP-style documentation within the Quality module. For manufacturers with very specific food safety certification requirements (e.g., SQF, BRCGS), you'd want to confirm the specific documentation requirements can be met before committing. * * * **Thinking about Odoo for your manufacturing business?** We're a certified Odoo Silver Partner based in Brisbane, with hands-on experience implementing manufacturing modules for Australian businesses. Our [manufacturing ERP page](/industries/manufacturing) covers how we phase these implementations and how Odoo compares with MYOB Acumatica for production work. If you want to understand whether Odoo fits your production environment before you commit to anything, [**book a free consultation**](/appointment). No obligation, just an honest conversation about what will and won't work for your operation. --- # MYOB Acumatica for Franchise Businesses in Australia - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-for-franchise-businesses-in-australia-94 - Category: MYOB Acumatica Australia - Published: 2026-03-15 - Description: MYOB Acumatica handles multi-entity financials and intercompany accounting for Australian franchise networks. Here is what it does well, and what to plan for. Running a franchise business creates an accounting problem that standard software doesn't solve cleanly. You have a franchisor entity, multiple franchisee entities, shared branding and systems, and reporting requirements that span all of them. MYOB AccountRight handles one company's books. MYOB Acumatica handles a franchise network. Here's what that actually means in practice. ## **What franchise businesses actually need from an ERP** The ERP requirements for a franchise are more specific than most people realise when they start evaluating software. You need the ability to maintain separate financial records for each entity, the franchisor and each franchisee, while also being able to consolidate them into a single view. You need intercompany transactions to be handled automatically rather than manually reconciled across systems. And you need all of this to work within Australian compliance requirements: GST, Business Activity Statement (BAS) reporting, and Single Touch Payroll (STP). Beyond the accounting, a franchise typically needs centralised purchasing (so the franchisor can manage supplier relationships on behalf of the network), location-level inventory and sales reporting, and in some cases integration with point-of-sale systems across the franchise locations. MYOB Acumatica was designed for exactly this kind of structure. ## **How MYOB Acumatica handles multi-entity franchise structures** MYOB Acumatica's [multi-company architecture](https://www.myob.com/au/erp-software/products/myob-acumatica) lets you set up each entity separately with its own chart of accounts, financial periods, and reporting requirements, while accessing all of them from a single login. A franchisee's P&L stays private to that entity. Consolidated reporting across the whole network is available to the franchisor at the top-level company. ### **Intercompany accounting and automatic eliminations** The feature that saves franchise finance teams the most time is automated intercompany accounting. When the franchisor charges a franchisee a management fee, or transfers inventory from a central warehouse to a franchise location, MYOB Acumatica records the transaction across both entities simultaneously. On consolidated reports, it then eliminates those intercompany transactions so they don't double-count. This is work that would otherwise be done manually in spreadsheets. It's also where most multi-entity accounting errors originate. Consolidated reporting also supports multi-currency for franchise networks that operate across Australia and New Zealand, with automatic exchange rate handling and currency translation at the group level. ## **Centralised purchasing and inventory across franchise locations** One of the practical advantages of running a franchise network on MYOB Acumatica is the ability to manage supplier relationships and purchasing centrally, while still distributing inventory to individual locations. The franchisor can raise purchase orders at the network level, receive stock into a central warehouse, and then transfer inventory to franchise locations, with each transfer reflected in the relevant entity's books automatically. Location-level inventory reporting lets you see what each franchise has on hand, what's moving, and where you have stock imbalances across the network. For franchise businesses that run marketing or promotional campaigns across all locations, this visibility matters: you can't run a network-wide promotion if you don't know whether the locations have enough stock to support it. ## **Australian compliance across a franchise network** Compliance is more complex in a franchise than in a single business, because each entity has its own tax obligations, and the franchisor often has obligations that span the whole network. ### **GST and BAS reporting with multiple entities** Each legal entity in a franchise network files its own Business Activity Statement (BAS) with the [Australian Taxation Office](https://www.ato.gov.au/businesses-and-organisations/tax-obligations-when-running-a-business/gst/how-gst-works), reporting its own GST collections and credits at the standard 10% rate. MYOB Acumatica handles GST configuration per entity so that BAS reporting is generated correctly for each one. If you have a franchisor that provides services to franchisees (management fees, training, marketing levies), those transactions need to be correctly taxed and reflected in both entities' BAS. MYOB Acumatica tracks this through the intercompany module. ### **Single Touch Payroll (STP) for franchise employers** Single Touch Payroll (STP), the ATO's real-time payroll reporting requirement, applies to each employing entity separately. If the franchisor employs staff and each franchisee also employs staff, each entity needs to report payroll through STP individually. MYOB Acumatica's payroll module handles STP Phase 2 reporting per entity, including salary sacrifice, allowances, and superannuation at the current guarantee rate. If you're running payroll across a large franchise network and want to understand the full compliance picture, our [MYOB Acumatica services page](/solutions/myob) covers what's included in a standard implementation. ## **Point-of-sale and integrations for retail franchise networks** For franchise businesses in retail or hospitality, point-of-sale (POS) integration is often the most important integration decision in the project. MYOB Acumatica integrates with [1Retail](https://1retail.cloud/), a POS solution built specifically for multi-location retailers and franchise operators on the Acumatica platform. 1Retail handles multi-location inventory, loyalty programs, and gift cards, with transactions feeding directly into MYOB Acumatica's financial records at the entity level. Auboros also has its own in-house POS solution that integrates directly with MYOB Acumatica. If you'd like to explore that option alongside 1Retail, our [MYOB Acumatica solutions page](/solutions/myob) has more detail on what's available. Other integration options depend on your existing tech stack. MYOB Acumatica has an open API, and eCommerce, shipping, and workforce management integrations are available through certified partners. If your franchise uses a specific POS or retail platform, it's worth confirming integration availability early in your evaluation, before you've committed to the platform. ## **Where MYOB Acumatica fits best in a franchise context** MYOB Acumatica works well for franchise businesses with at least four or five entities and a genuine need for consolidated financial reporting. It's particularly strong for wholesale distribution franchises and retail networks, largely because of the depth of the distribution module and multi-location inventory capabilities. If you have fewer than three or four entities and your reporting requirements are straightforward, it's worth having an honest conversation about whether MYOB Acumatica is the right fit or whether a simpler platform would serve you better. That's the kind of conversation we have with prospects before anyone signs anything. If you're comparing it to MYOB AccountRight, our post on [when to upgrade from AccountRight to Acumatica](/blog/myob-acumatica-australia-7/myob-acumatica-vs-accountright-when-to-upgrade) covers the decision criteria in detail. ## **Frequently asked questions** ### **Can MYOB Acumatica keep the franchisor and franchisee accounts completely separate?** Yes. Each entity has its own chart of accounts, financial periods, and user access permissions. A franchisee's financial data is only visible to users with access to that entity. The franchisor's finance team can access consolidated views, but that access is configured by the system administrator, not automatic. ### **Does MYOB Acumatica integrate with point-of-sale systems?** Yes. The most purpose-built option for franchise retail is 1Retail, which is built natively on the Acumatica platform. Other POS integrations are available depending on your existing systems. Confirm integration availability for your specific POS before committing to the platform, as this is a common area where expectations don't match reality if it's not checked early. ### **Is MYOB Acumatica suitable for a smaller franchise network with five locations?** It can be, but it depends on your complexity. Five locations with separate legal entities, multi-entity reporting requirements, and meaningful transaction volume is a reasonable fit. Five locations operating as branches of a single entity with simple reporting probably isn't the right fit. Simpler software would do the job at lower cost. A scoping conversation will usually answer this question quickly. ### **What's the difference between MYOB Acumatica and AccountRight for a franchise?** MYOB AccountRight is designed for a single company. It doesn't natively support multi-entity structures, intercompany accounting, or consolidated group reporting. For a franchise with multiple legal entities, AccountRight means maintaining separate files per entity and consolidating manually, which works up to a point and then becomes untenable. MYOB Acumatica handles all entities in a single system with automatic intercompany processing. Our [post on MYOB Acumatica for member-based organisations](/blog/myob-acumatica-australia-7/myob-acumatica-member-based-organisations-australia) covers the broader multi-entity capabilities if you want more context. * * * **Running a franchise network and wondering if MYOB Acumatica is the right fit?** Auboros is an official MYOB Acumatica partner based in Brisbane, working with franchise businesses across Queensland, NSW, and Victoria. We'll tell you honestly whether the platform fits your structure, or whether something else makes more sense. If you want to talk through your franchise setup, [**book a free consultation**](/appointment). No commitment required. --- # MYOB Acumatica Support: What's Included and What You'll Pay Extra For - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-support-what-s-included-and-what-you-ll-pay-extra-for-96 - Category: MYOB Acumatica Australia - Published: 2026-03-15 - Description: Understand what MYOB Acumatica support covers: partner vs. direct MYOB, what is included as standard, what costs extra, and how to choose the right setup. One of the most common questions we get after an implementation is: "So who do we call when something goes wrong?" With MYOB Acumatica, the answer isn't as simple as ringing a 1800 number. There are two distinct support channels: your implementation partner and MYOB directly. What each one covers is quite different. Getting this right before you go live saves a lot of frustration. ## **The two support channels: partner vs. MYOB direct** MYOB Acumatica is delivered through a partner network. That means the business you engaged for implementation, whether that's Auboros or another certified partner, is your primary support relationship, not MYOB. This is how most mid-market ERP platforms work, and it makes sense: your partner knows how your system is configured, what customisations have been applied, and how your business processes map to the software. MYOB does offer a [direct customer support program](https://www.myob.com/au/support/myob-acumatica) through Acumatica, which sits alongside your partner arrangement. It gives named users access to MYOB's technical support team for platform-level issues via your partner. It covers technical troubleshooting, not consulting, configuration help, training, or business process guidance. In practice, most businesses find they rarely need to go directly to MYOB. A good partner handles the vast majority of support cases through their own help desk, escalating to MYOB only when there's a confirmed platform bug or an issue that requires MYOB's backend access to investigate. ## **What's typically included in partner support** Partner support arrangements vary, but most certified MYOB Acumatica partners include the following as part of an ongoing support retainer or annual support agreement: - **Help desk access:** A dedicated channel (usually a ticketing portal or email) to log issues, with response time commitments based on priority level. - **Break-fix support:** When something stops working (a report error, a failed import, a workflow that's behaving unexpectedly), your partner diagnoses and resolves it. - **Minor configuration changes:** Small adjustments to reports, user permissions, notification rules, or workflows that don't require full development work. - **Platform upgrades:** MYOB Acumatica releases major updates twice a year. Your partner guides you through the upgrade process, tests your customisations against the new version, and manages the deployment. - **User and access management:** Adding or removing users, adjusting role permissions, and managing your licence as your team changes. What support agreements typically don't include, at least not without additional scoping, is new development work, integrations with new third-party systems, significant process changes, or new module implementations. Those fall under consulting or project work, which is scoped and priced separately. ## **What you'll pay extra for** This is where businesses sometimes get caught out. They assume their support agreement covers everything, and then they request something that falls outside it. The distinction matters: support is reactive (fix what's broken, maintain what exists), while consulting is proactive (build something new, change how something works). Things that typically sit outside standard support and are billed as project work: - **New customisations:** Any development that changes how the system behaves: custom workflows, new fields, screen modifications, custom reports beyond minor adjustments. - **New integrations:** Connecting MYOB Acumatica to a new external system, whether that's a WMS, a POS platform, a CRM, or an ecommerce store. - **Training:** Onboarding new staff, training on modules your team doesn't currently use, or refresher training after a major upgrade. - **Additional module implementations:** If you go live with financials and later want to add Payroll or Advanced Inventory, that's a new implementation project, not a support task. - **Data migration or cleanup:** Importing data from a legacy system or cleaning up data quality issues in your existing instance. None of this is unusual. It reflects how ERP support works across the market. The key is knowing the boundary so you can plan and budget for it. A transparent partner will be upfront about what falls inside and outside their support scope before you sign. ## **How to evaluate a MYOB Acumatica support partner** Your support relationship will outlast your implementation by years, so it deserves as much scrutiny as the initial project. A few things worth asking any prospective partner: - **What are your response time commitments by priority level?** A critical issue (system down, payroll blocked) should have a different SLA than a non-urgent configuration query. - **Who actually handles support tickets?** Some partners pass support work to junior staff or offshore teams. Know who you're working with. - **How do you handle MYOB Acumatica upgrade cycles?** MYOB releases updates on a set schedule. Your partner should have a clear process for testing and deploying these, and should communicate the timeline to you before it happens. - **What's the escalation path?** When a partner can't resolve an issue internally, they escalate to MYOB. Ask how that process works and roughly how long escalations typically take to resolve. Partner certification matters too. MYOB accredits partners at different levels based on their team's qualifications and experience. A certified partner with a demonstrated track record in your industry is a lower risk than a generalist consultancy that handles MYOB Acumatica alongside a dozen other platforms. At Auboros, we're an official MYOB Acumatica Partner and we offer ongoing [support arrangements for Australian businesses](/solutions/myob). We also have a dedicated help desk for clients in Queensland and beyond. If you're reviewing your current support setup or considering a move to MYOB Acumatica, you can see what that looks like in more detail on our [MYOB services page](/solutions/myob). ## **Frequently asked questions** ### **Can I get support directly from MYOB without going through a partner?** Yes, but with limitations. MYOB offers a direct customer support program through Acumatica for platform-level technical issues. It covers troubleshooting and bug escalation, but it doesn't include consulting, training, configuration help, or implementation services. For most businesses, partner support is the more practical day-to-day option. ### **What happens to support during a MYOB Acumatica upgrade?** MYOB releases major platform updates twice a year. Your partner should communicate the upgrade schedule in advance, test your environment, including any customisations, against the new version, and manage the deployment. In most partner support agreements, upgrade management is included, though the level of testing and preparation varies. Confirm this specifically before you sign. ### **How quickly should a support issue be resolved?** That depends on severity and your support agreement. A critical issue like payroll failing to process or the system being inaccessible should typically get same-day attention. Lower-priority issues, such as minor report errors or non-urgent configuration queries, are commonly addressed within two to five business days. Response time commitments should be written into your support agreement, not left to verbal assurances. ### **Is MYOB Acumatica support included in the subscription cost?** The subscription cost covers access to the platform, hosting, and MYOB-provided updates. Partner support is a separate arrangement and is typically charged as an annual retainer or consumed from a block of hours. The split between what MYOB provides and what your partner provides is an important distinction to understand before you budget for your total cost of ownership. * * * **Not sure what your current MYOB Acumatica support arrangement actually covers?** We work with businesses across Queensland, NSW, and Victoria who want straightforward, responsive support from a partner that knows their system. If you're assessing your options, [**book a free consultation**](/appointment) and we'll give you an honest picture of what good support looks like and what to expect. --- # How Long Does an Odoo Implementation Take in Australia - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/how-long-does-an-odoo-implementation-take-in-australia-93 - Category: Odoo ERP Australia - Published: 2026-03-14 - Description: How long does an Odoo implementation take? Use our free calculator to get a realistic estimate by business size, modules, and complexity. Built for Australia. The most common answer you'll get from an Odoo partner is "it depends." That's true, but it's also not very useful when you're trying to budget, plan staff time, or set a go-live target. Here's what actually drives the timeline, and a practical tool to estimate what yours might look like. ## **What determines YOUR Odoo implementation timeline?** Five variables shape every Odoo project timeline: what type of business you are, how many users you have, how complex your data migration is, how much customisation the project needs, and how well-documented your processes are. Everything else, including location and whether you're on Enterprise or Community, matters far less than these five inputs. Industry is the biggest single variable most calculators ignore. A manufacturing company running multi-level bills of materials is a fundamentally longer project than a professional services firm with clean data, even if both have the same number of users. Use the calculator below to get a rough estimate for your situation. It's based on timelines from real Australian implementations, not marketing material. Odoo implementation timeline estimator Answer five questions to get a rough timeline for your project. Business type Professional services / consulting / office-based Retail (standard Odoo shop or POS) Retail / eCommerce with Shopify or WooCommerce integration Wholesale and distribution Manufacturing (make to order, simple products) Manufacturing (MRP, multi-level BOMs, work centres) Number of Odoo users Under 25 users 25 to 100 users Over 100 users Data migration complexity Minimal (spreadsheets only) Moderate (one system, reasonably clean) Complex (multiple systems, large product catalogue, or dirty data) Customisation needed Minimal (standard Odoo as-is) Some (minor tweaks or automations) Significant (custom modules or integrations) Process documentation Well documented (clear SOPs, team knows the workflows) Partially documented (most things are clear) Mostly in people's heads (processes need to be mapped first) Estimated total timeline \- weeks Update the fields above to calculate. Discovery & scoping \- Configuration & setup \- Data migration \- Training & testing \- Want a more accurate estimate for your business? [Book a free consultation](/appointment) Estimates based on typical Australian Odoo implementations. Actual timelines depend on your partner, team availability, and project governance. Go-live and stabilisation (typically 1-2 weeks) not shown separately above. ## **The phases where time actually goes** Looking at the calculator phases in more detail: discovery and scoping is the phase most businesses underestimate. It seems like admin, but the decisions made here, specifically what's in scope, what your chart of accounts will look like, and which integrations are required, shape every phase that follows. Skipping it or rushing it is the single most common reason projects run long. Configuration typically takes the most time, and it grows quickly when scope expands mid-project. Every change request after sign-off adds to this phase. The best thing you can do here is be as specific as possible before build starts, and resist the temptation to add "just one more thing" once the project is underway. Data migration is where client-side effort is highest. Your partner can build the migration scripts, but only you can clean the data. Businesses that start cleaning their data early, removing duplicates, standardising formats, and resolving missing values, consistently finish on time. Businesses that leave it until the last minute don't. ## **What slows most Australian implementations down** After running implementations for Australian businesses of various sizes, the delays we see most often come from the same sources. Scope creep is the biggest: requirements that weren't fully captured in discovery, or new ideas that surface once the team starts testing. Internal resourcing is a close second. Implementations need a project champion on the client side with actual time allocated, not just good intentions. Whoever owns the project needs to be able to make decisions quickly. Data readiness is the third. You can have a well-run project and still miss your go-live date because the product list is a mess or the customer database hasn't been cleaned. If you're planning an Odoo implementation, start preparing your data well before the project formally kicks off. The fourth, and the one most businesses don't see coming, is process clarity. This one hits manufacturing and distribution businesses hardest. If your team manages workflows in their heads, if your BOM structure has never been formally documented, or if different people have different ideas about how your production process actually works, you can't configure Odoo until that's resolved. Process mapping becomes part of the project scope, and it adds weeks before a single module is configured. The calculator above accounts for this. If you selected "mostly in people's heads," look carefully at that timeline. ## **Frequently asked questions** ### **Can you go live with a single Odoo module in under a month?** Yes, for a small team with clean data and minimal configuration needs. A single-module rollout (CRM or accounting only, for example) for a business under 15 users can realistically go live in three to four weeks. It's not common because most businesses need more than one module, but it's achievable with a focused scope and a partner who doesn't over-engineer it. ### **Does the number of modules significantly affect the timeline?** Yes, but not linearly. Going from two modules to four roughly doubles configuration time. Going from four to eight doesn't double it again, because there's shared configuration work across modules: your chart of accounts, your customer records, your tax settings. The bigger driver beyond four or five modules is usually integrations with third-party systems, not the modules themselves. ### **What's the difference between going live and being fully operational?** Go-live means your team is using Odoo instead of the old system. Fully operational means the team is comfortable, your reporting is accurate, and you've moved past the stabilisation period where minor issues still surface. For most businesses, that gap is four to eight weeks. It's normal and expected, so build it into your planning. The [full implementation guide](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) covers what the stabilisation phase involves in more detail. ### **How does implementation timeline affect cost?** Directly. Most partners charge by the hour or by project phase, so a longer project costs more. The surest way to control cost is to control scope and arrive at the project with clean data. See [Auboros's implementation packages](/odoo-implementation-packages-for-australian-businesses) for how we structure fixed-price engagements, and our [Odoo implementation services](/solutions/odoo) for what a certified Silver Partner delivery looks like end to end. * * * **Planning an Odoo implementation in Queensland or beyond?** The calculator above gives you a rough estimate. For a proper scoping conversation, where we look at your actual modules, your data, and your team's availability, a free call is the right next step. If you want to know what your project would actually look like, [**book a free consultation**](/appointment). No commitment required. We'll give you a straight answer on scope and timeline. --- # Odoo vs Xero: When to Upgrade from Accounting to ERP in Australia - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-vs-xero-when-to-upgrade-from-accounting-to-erp-in-australia-91 - Category: Odoo ERP Australia - Published: 2026-03-14 - Description: The signs you've outgrown Xero, what Odoo adds, what it costs to move, and when staying on Xero is the right call. Honest advice from a team that uses both. If your Xero is working fine, you don't need Odoo. That sounds obvious, but it's worth saying outright, because plenty of businesses switch before they should, and just as many wait years past the point where the pain was already obvious. The question isn't which platform is "better." It's which one matches where your business actually is. ## **What's the actual difference between Xero and Odoo?** Xero is accounting software. It records what your business does financially: invoices, bank reconciliations, BAS reporting, payroll. It does this very well. Most Australian accountants and bookkeepers are comfortable in it, the ATO integration is tight, and setup takes hours rather than weeks. Odoo is an ERP (Enterprise Resource Planning) platform. It doesn't just record financial outcomes. It manages the operations that create those transactions in the first place. Sales quotes, purchase orders, warehouse movements, manufacturing jobs, project timesheets: all of it flows into the ledger automatically because it's happening inside the same system. Xero tells you what happened. Odoo helps you manage what's happening. That structural difference is at the heart of the Odoo vs Xero question for Australian businesses, and it's worth keeping in mind as you read through what follows. ## **Five signs your business has outgrown Xero** Not every growing business needs ERP. But these five patterns tend to show up consistently in the ones that do. - **You're copying data between systems.** Xero has basic inventory, project tracking, and job features, but they don't talk to each other in any meaningful way. If you're patching the gaps with a separate inventory tool, a CRM, or a dedicated project platform and spending hours reconciling between all of them, you're already paying the cost of fragmentation. - **Inventory is hitting Xero's limits.** [Xero's native inventory tracks up to 4,000 items](https://www.unleashedsoftware.com/app-marketplace/xero-inventory-management/xero-inventory-management-guide/), and performance noticeably degrades well before that. It has no native multi-warehouse support. If you're running two or more locations, you're working around the system, not with it. - **You have multiple related entities.** Xero handles a single company well. Multiple legal structures with intercompany transactions and consolidated reporting need a platform built for that from the ground up. - **You can't see profitability by job or project.** Xero gives you financial reporting at the entity level. It doesn't tell you which jobs cost more than expected, or which products are actually profitable once warehouse handling is factored in. - **Your finance team lives in spreadsheets.** Not because they're slow. It's because the information they need is scattered across five platforms and the only way to bring it together is manually. If three or more of these sound familiar, it's worth a proper conversation about whether ERP is the right next step. Our [Odoo implementation guide for Australian businesses](/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87) covers what that process actually involves. ## **What Odoo gives you that Xero can't** Odoo's accounting module covers the same ground as Xero: invoicing, bank reconciliation, expense claims, BAS. But because it shares a single database with the rest of the business, the financial data is richer from the start. Stock movements generate journal entries automatically. A confirmed sales order creates a delivery task. A completed manufacturing job posts its material costs to the P&L. Nothing needs to be re-entered or reconciled across platforms. For businesses with field operations, Odoo's field service module tracks job times, materials used, and customer sign-off, with those costs flowing directly to the profit and loss. That kind of closed loop is very difficult to achieve with separate tools, regardless of how many integrations you build between them. ### **Australian compliance in Odoo: what you need to know** Odoo isn't pre-configured for Australia the way Xero is. You'll need a partner with localisation experience to set up GST correctly, configure [BAS (Business Activity Statement)](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas) reporting, and connect payroll with [Single Touch Payroll (STP)](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll) requirements. Once that configuration is done properly, ongoing compliance works reliably, but it's not a "plug in your ABN and go" experience. That's a legitimate consideration. If accounting compliance is your only need, Xero still wins on setup time. If you've outgrown Xero operationally, the configuration investment pays off quickly and the ongoing running cost is comparable. ## **When you should stay on Xero** Xero is genuinely well-suited to the businesses it's designed for. If you're under roughly $5M in revenue with a single location, straightforward or no inventory, and no intercompany complexity, there's no practical reason to move to ERP. Switching for its own sake creates real problems: longer setup time, a more complex system, and a team that was happy in Xero now learning something new. The businesses that get the best return from Odoo are the ones who were already feeling the pain of their current setup. If you're not there yet, come back to this question in 12 months. ## **Odoo vs Xero Australia: a side-by-side comparison** | | Xero | Odoo | | --- | --- | --- | | **Best for** | Accounting and compliance | Full business operations | | **Ideal business size** | Under ~$5M revenue | $5M+ with operational complexity | | **Australian payroll** | Native, ATO-connected | Requires partner configuration | | **Inventory** | Basic, 4,000 item limit, single location | Full multi-warehouse support | | **Multi-entity** | Limited | Native support | | **Job and project costing** | Via add-ons | Native | | **Implementation time** | Hours to days | Weeks to months | | **Ongoing cost** | Subscription only | Subscription plus implementation investment | For a detailed look at [Odoo pricing for Australian businesses](/odoo-implementation-packages-for-australian-businesses), we've published our implementation packages openly. Knowing what things cost before you start a conversation saves everyone time. ## **Frequently asked questions** ### **Is Odoo a replacement for Xero in Australia?** Yes. Odoo includes a full accounting module that covers everything Xero does: invoicing, bank reconciliation, payroll, and BAS reporting. Most businesses that move to Odoo replace Xero entirely rather than run both in parallel. The setup requires a partner with Australian localisation experience to configure GST, BAS, and STP correctly. ### **Can you run Xero and Odoo at the same time?** You can, and some businesses do this during a transition period, with Odoo handling operations and Xero handling accounting, syncing data between them. In practice, this adds complexity and most businesses consolidate onto one system within 6 to 12 months. Running both indefinitely tends to recreate the reconciliation problem you were trying to solve. ### **How long does migrating from Xero to Odoo take?** A typical implementation takes 8 to 16 weeks depending on the complexity of your operations and how many modules you're activating. Historical financial data from Xero can be migrated or simply kept in Xero as an archived reference system. Many businesses find the latter cleaner. ### **Is Odoo harder to use than Xero?** Yes, there's a steeper learning curve, particularly for staff who've only ever used accounting tools. Odoo's interface has improved considerably in recent versions (v17 and v18), and most teams get comfortable within a few weeks of going live with proper training. The trade-off is that a more capable system takes more to learn. * * * **Thinking about moving from Xero to Odoo?** We're a Brisbane-based [Odoo Silver Partner](/solutions/odoo) with experience managing Australian ERP transitions, covering everything from accounting migration and GST configuration to going live without disrupting your operations. If you're weighing up whether the switch makes sense, [**book a free consultation**](/appointment) and we'll give you an honest read on whether Odoo is actually right for your business right now. --- # Odoo vs NetSuite Australia: 2026 ERP Comparison - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-vs-netsuite-australia-2026-erp-comparison-90 - Category: Odoo ERP Australia - Published: 2026-03-11 - Description: What NetSuite really costs in Australia, how Odoo pricing compares, and which platform fits your business. AUD figures, GST compliance, honest trade-offs. Odoo vs NetSuite Australia: 2026 ERP Comparison Two ERP platforms come up in almost every mid-market conversation in Australia: Odoo and NetSuite. They're not the same kind of software, they don't suit the same kinds of businesses, and the price difference between them is significant. If you're comparing the two, this guide will help you work out which one actually fits your situation. ## **What you're actually comparing: Odoo vs NetSuite** Before getting into feature lists, it's worth understanding what these two platforms are at a fundamental level. They were built for different purposes, and that shapes everything downstream. ### **Odoo: modular, open-source, flexible** Odoo is an open-source ERP built on a modular architecture. You start with the modules you need and add more as your business grows. There's a free Community edition and a paid Enterprise edition, with licensing available per user per month. Importantly, [Enterprise source code is accessible to all Enterprise subscribers](https://www.odoo.com/pricing), not just implementation partners. The platform covers accounting, inventory, sales, purchasing, CRM, manufacturing, field service, e-commerce, HR, and more. Odoo's flexibility is its biggest strength and, in the wrong hands, its biggest risk. It can be configured extensively, but a poorly planned implementation creates technical debt that compounds quickly. That's why [working with a certified Odoo Silver Partner](/solutions/odoo) makes a meaningful difference to how your implementation lands. ### **NetSuite: integrated cloud ERP for complex financials** NetSuite is a fully closed-source, cloud-hosted ERP owned by Oracle. It was built from the ground up for businesses with complex financial structures: multi-entity consolidation, revenue recognition, subscription billing, and intercompany transactions. It runs on a single integrated database, which means there's less configuration needed to connect modules, but also less flexibility to modify how those modules work. NetSuite suits businesses that are finance-heavy, often globally distributed, and have internal IT resources to manage an enterprise system. It has a large ecosystem of Solution Providers in Australia, and implementation costs reflect the platform's complexity. In practice, NetSuite tends to be the stronger choice when advanced financial reporting and multi-entity structures are the primary drivers of an ERP decision, rather than operational functionality. ## **How the costs compare for Australian businesses** This is where the conversation changes quickly. The licence cost difference between Odoo and NetSuite is not marginal, and it compounds significantly when you factor in implementation and ongoing support. ### **Odoo pricing in Australia** Odoo Enterprise is priced per user per month. In Australia in 2026, the Standard plan runs **AUD $43 per user per month** on annual billing, and the Custom plan, which unlocks full customisation and all modules, runs **AUD $65 per user per month**. For a business with 15 users on the Custom plan, that's roughly $11,700 per year in licence costs alone. Implementation costs for a mid-sized Australian business typically range from $20,000 to $50,000, depending on complexity and the number of modules deployed. We publish our [Odoo implementation pricing](/odoo-implementation-packages-for-australian-businesses) so you can assess the investment before starting a conversation. ### **NetSuite pricing in Australia** NetSuite does not publish pricing. Based on what Australian mid-market buyers and consultants report, licences typically run **AUD $5,000 to $15,000 per month** for a mid-sized team, depending on modules and user count. Implementation projects regularly reach $100,000 or more for a mid-market deployment. NetSuite also commonly charges separately for SuiteSuccess onboarding, support tier upgrades, and additional modules after the core platform. ### **Five-year total cost of ownership** For a $20 million revenue Australian business, the five-year total cost of ownership for NetSuite is commonly reported at AUD $500,000 to $1 million, including implementation, licences, and ongoing support. Odoo's five-year TCO for a comparable deployment typically runs 70 to 90% less. That's a meaningful gap when the functional difference between the two platforms is marginal for most Australian businesses at that scale. ## **Where Odoo is the stronger choice for Australian businesses** Odoo tends to be the better fit in these situations: - **You're a manufacturer, wholesaler, or field service business.** Odoo's manufacturing, inventory, and field service modules are mature and well-suited to Australian operational businesses. Bill of materials management, work orders, and scheduling are genuinely useful without being overbuilt for mid-market needs. - **You want to grow into the system progressively.** Starting with Odoo Accounting and CRM and adding modules as you scale is practical and cost-controlled. NetSuite implementations tend to be all-or-nothing, which increases upfront cost and risk. - **You're managing GST and BAS reporting.** Odoo can be configured for Australian GST at 10%, Business Activity Statement (BAS) reporting, and [Single Touch Payroll (STP) Phase 2](https://www.ato.gov.au/businesses-and-organisations/super-for-employers/single-touch-payroll) through Australian localisation. A certified Australian partner handles this configuration during implementation. - **Budget matters.** If you're a $5M to $30M revenue business with genuine operational complexity, Odoo's pricing structure means you get enterprise-grade functionality without an enterprise-grade bill. - **You're currently on Xero or MYOB and outgrowing it.** Our guide to [Odoo ERP implementation in Australia](/blog/odoo-erp-australia-6/odoo-erp-implementation-australia-guide-2026) covers what the transition actually looks like in practice. ## **Where NetSuite is the stronger choice** NetSuite is genuinely better for some businesses, and it's worth saying so plainly rather than pretending Odoo wins in every scenario. - **You need multi-entity consolidation at scale.** If you run several legal entities, need automated intercompany eliminations, or are reporting across currencies for an ASX-listed group, NetSuite's financial architecture handles this more natively than Odoo does out of the box. - **You have a subscription or SaaS business model.** NetSuite's subscription billing and revenue recognition capabilities are strong and tightly integrated with its financials. Odoo can be configured for this, but it requires more partner work. - **GAAP or IFRS multi-book accounting is a hard requirement.** NetSuite has more depth here than Odoo in its standard configuration. - **You have a dedicated internal system administrator.** NetSuite rewards businesses that can invest internal resources in managing the system. Without that, ongoing costs compound. Odoo is generally easier to support with a smaller internal team. ## **Australian compliance: BAS, GST, and Single Touch Payroll** For any Australian business, payroll compliance and ATO reporting are non-negotiable. Both platforms can handle the core requirements, but implementation approach matters significantly. Odoo's Australian compliance, including GST at 10%, BAS configuration, and STP Phase 2 payroll reporting, is handled through localisation modules that certified Australian partners configure during implementation. The quality of that setup varies depending on who does it. NetSuite includes Australian localisation in its core product, though businesses still need partner support to configure it correctly for their specific entity structure and reporting requirements. For current ATO requirements on STP and BAS, the [ATO's official STP guidance](https://www.ato.gov.au/businesses-and-organisations/super-for-employers/single-touch-payroll) is the authoritative source. Any ERP vendor or partner making compliance claims should be able to point you to the specific ATO requirements their configuration addresses. Odoo also publishes an [official comparison of Odoo and NetSuite across manufacturing and operations](https://www.odoo.com/page/odoo-vs-netsuite-mrp), which is useful if those modules are central to your evaluation. ## **Which type of Australian business should choose which?** Here's a practical decision framework based on what we see across the businesses we work with: - **Under $5M revenue, 10 to 20 staff:** Odoo Standard may be more than you need right now. Xero or MYOB AccountRight is likely the right fit at this stage. An ERP implementation adds cost and complexity that's hard to justify until you're hitting genuine operational ceilings. - **$5M to $50M revenue, operational complexity:** Odoo is likely the right fit, particularly if you're in manufacturing, distribution, field service, or e-commerce with a need to manage inventory and operations in a single system. The modular approach means you can grow into the system without paying for what you don't yet need. - **$50M or more, multi-entity, finance-heavy:** NetSuite deserves serious consideration, particularly if revenue recognition, intercompany accounting, or consolidated multi-entity reporting are core requirements. For a broader view of how Odoo compares to other ERP platforms in the Australian market, our [2026 ERP company guide](/blog/insights-5/erp-solutions-company-2026-4) covers the full landscape including SAP, Microsoft Dynamics, and MYOB Acumatica. ## **Frequently asked questions** ### **Is Odoo cheaper than NetSuite in Australia?** Yes, significantly. Odoo Enterprise typically costs 70 to 90% less than NetSuite over a five-year period when you account for licence fees, implementation, and ongoing support. For a 15-user business, the annual licence difference alone is often $150,000 or more. The gap is substantial at almost every scale relevant to Australian mid-market businesses. ### **Can Odoo replace NetSuite for an Australian business?** For most Australian SMEs and mid-market businesses, yes. Odoo covers the same core functional areas: accounting, inventory, CRM, sales, purchasing, manufacturing, and HR. Where NetSuite maintains a clear edge is in complex multi-entity financial structures and built-in GAAP/IFRS multi-book accounting. If those capabilities aren't requirements for your business, Odoo is a credible and substantially cheaper alternative. ### **Does Odoo support Australian payroll and Single Touch Payroll?** Odoo can be configured for Single Touch Payroll (STP) Phase 2 and Australian payroll through localisation modules. That configuration needs to be done by an experienced Australian implementation partner. It doesn't work correctly out of the box without that partner involvement. At Auboros, STP and payroll configuration is a standard component of every Odoo implementation we deliver. ### **Which ERP is easier to implement in Australia?** Neither is simple, but Odoo implementations for mid-sized businesses typically run 8 to 16 weeks depending on scope. NetSuite implementations tend to take longer and cost more because the platform has more inherent complexity. Odoo's modular approach also means you can go live on core modules and expand progressively, which reduces initial project risk. ### **Is NetSuite overkill for a $10M revenue Australian business?** In most cases, yes. At $10M revenue with fewer than 50 staff and a single legal entity, you're paying for NetSuite's financial depth that you're unlikely to fully use. Odoo gives you the operational functionality you need at a significantly lower total cost of ownership. NetSuite makes more sense when the business is past $50M, operates across multiple legal entities, or has genuinely complex financial reporting requirements that Odoo's standard configuration doesn't cover. * * * **Comparing Odoo and NetSuite for your Australian business?** We work with manufacturers, wholesalers, and service businesses across Queensland, NSW, and Victoria to implement Odoo properly, including BAS configuration, STP Phase 2, and the Australian localisation that makes the system actually usable for your team. If you are weighing the full field of options, our [NetSuite alternatives guide](/compare/netsuite-alternative-australia) covers where Odoo and MYOB Acumatica each replace it, and when staying put is right. If you're working through this decision, [**book a free consultation**](/appointment). We'll give you a straight assessment of which platform fits your situation, not a pitch for either one. --- # How to Choose the Right MYOB Acumatica Implementation Services - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/choose-right-myob-acumatica-implementation-services-5 - Category: MYOB Acumatica Australia - Published: 2026-03-11 - Description: Learn how to choose the right MYOB Acumatica implementation services to ensure a successful ERP rollout, scalability and long-term business value. Choosing the right enterprise resource planning solution is a major decision for any organisation. However, selecting the right implementation partner is just as critical as choosing the software itself. MYOB Acumatica is a powerful cloud-based ERP system, but its success depends heavily on how well it is implemented and aligned with business processes.  Businesses exploring MYOB Acumatica often begin their journey by researching experienced service providers who understand both the technical and operational sides of ERP systems. Organisations such as [**Auboros**](/) operate in this space, offering ERP and business system solutions across multiple platforms, including MYOB and other enterprise software.  This article provides a practical and structured guide on how to choose the right MYOB Acumatica implementation services, focusing on long-term value, risk reduction and operational alignment rather than sales-driven promises.  ## **Understanding MYOB Acumatica implementation services**  MYOB Acumatica implementation services refer to the professional support required to configure, deploy and optimise the MYOB Acumatica ERP platform for a specific business. These services typically go beyond software installation and include analysis, planning and ongoing optimisation.  **What implementation services typically include**  A standard MYOB Acumatica implementation may involve:  - Business process analysis and requirements gathering  - System configuration and module selection  - Data migration from legacy systems  - Customisation and integration with third-party tools  - User training and documentation  - Testing, deployment and post-go-live support  Each of these stages plays a critical role in ensuring the ERP system delivers accurate reporting, streamlined operations and scalability.  ### **Why implementation quality matters**  Poor implementation can lead to data inconsistencies, user resistance and underutilisation of system features. Even a technically sound [**ERP system**](/solutions/other-erp-services) can fail if it does not align with how the organisation operates daily. Choosing the right MYOB Acumatica implementation services helps mitigate these risks by ensuring the system reflects real business workflows.  ## **Assessing your business requirements first**  Before selecting an implementation partner, it is important to understand your own business needs clearly. This allows for informed discussions and realistic expectations.  ### **Identify operational challenges**  Start by documenting current issues such as:  - Manual data entry or duplicate records  - Lack of real-time reporting  - Disconnected systems across departments  - Scalability limitations in existing software  These insights will help determine which MYOB Acumatica modules and configurations are most relevant.  ### **Define short-term and long-term goals**  An ERP implementation should support both immediate improvements and future growth. Consider whether your organisation plans to expand operations, introduce new services or operate across multiple locations. This forward-thinking approach ensures the implementation is scalable rather than short-sighted.  ## **Evaluating experience with MYOB Acumatica**  Not all ERP consultants have the same level of expertise with MYOB Acumatica. Experience with the platform directly affects implementation quality.  ### **Industry and functional experience**  Look for service providers with experience in your industry or similar operational environments. An implementation partner familiar with your sector is more likely to anticipate regulatory requirements, reporting needs and operational nuances.  ### **Proven MYOB Acumatica expertise**  Ask about the partner’s track record with MYOB Acumatica specifically. Experience with other ERP platforms such as Odoo or alternative systems can be beneficial, but Acumatica-specific knowledge is essential. Providers offering multiple ERP solutions, such as those listed under [**MYOB services**](/solutions/myob) , often bring broader perspective while maintaining platform expertise.  ## **Understanding the implementation methodology**  A clear and structured implementation approach reduces uncertainty and ensures accountability throughout the project lifecycle.  ### **Project planning and governance**  A reliable implementation partner should provide a defined project plan outlining:  - Key milestones and deliverables  - Roles and responsibilities  - Risk management processes  - Communication and reporting structures  This transparency allows stakeholders to track progress and address issues early.  ### **Data migration and system testing**  Data accuracy is critical in ERP systems. Ensure the implementation services include rigorous data validation, testing cycles and reconciliation processes. Testing should involve real-world scenarios rather than theoretical use cases.  ## **Considering customisation versus configuration**  MYOB Acumatica offers strong configuration capabilities, but not every business requirement should be met through custom development.  ### **Avoid unnecessary customisation**  Excessive customisation can increase costs, complicate upgrades and create long-term maintenance challenges. A skilled implementation partner will focus on configuring standard features wherever possible and recommend customisation only when there is a clear business justification.  ### **Integration with other systems**  Many organisations rely on additional platforms such as CRM, payroll or e-commerce tools. MYOB Acumatica implementation services should include integration planning to ensure seamless data flow and reporting accuracy.  ## **Training and change management**  User adoption is one of the most common challenges in ERP projects. Even a well-implemented system can fail if users do not understand how to use it effectively.  ### **Role-based training**  Effective training should be tailored to different user roles rather than delivered as a generic session. Finance teams, operational staff and management each interact with the system differently and require targeted guidance.  ### **Ongoing support and knowledge transfer**  Implementation services should not end at go-live. Ongoing support, documentation and system reviews help organisations adapt as their processes evolve.  ## **Evaluating post-implementation support**  ERP systems are not static. As business requirements change, the system must evolve accordingly.  ### **Support models and responsiveness**  Understand what level of support is available after implementation. This may include issue resolution, system enhancements and performance optimisation. Clear service-level expectations help prevent future misunderstandings.  ### **Continuous improvement approach**  Some service providers also support periodic system reviews to identify underutilised features or optimisation opportunities. This approach ensures continued value from the ERP investment.  ## **Comparing ERP providers beyond MYOB Acumatica**  While MYOB Acumatica may be the right choice for many organisations, it is still valuable to understand alternative platforms. Providers offering solutions such as [**Odoo ERP**](/solutions/odoo) often help businesses compare systems objectively before finalising their decision.  This broader understanding allows organisations to confirm that MYOB Acumatica aligns with their operational complexity, budget and growth plans.  ## **Asking the right questions before selecting a partner**  Before engaging MYOB Acumatica implementation services, consider asking the following:  - What is your experience with similar businesses  - How do you manage data migration and testing  - What level of customisation do you recommend and why  - How do you support users after go-live  - What risks should we anticipate during implementation  Clear and direct answers indicate a thoughtful and transparent approach.  ## **Planning next steps carefully**  Selecting an implementation partner should be a structured decision rather than a rushed one. Taking time to assess requirements, review experience and understand methodologies reduces the likelihood of project delays or unexpected costs.  Businesses seeking further guidance often begin with an initial consultation to explore suitability and implementation scope. Enquiries can typically be initiated through a dedicated [**contact page**](/contactus).  ## **Frequently Asked Questions**  What are MYOB Acumatica implementation services?  MYOB Acumatica implementation services include planning, configuration, data migration, training and support required to deploy the ERP system successfully within an organisation.  How long does a typical MYOB Acumatica implementation take?  Implementation timelines vary depending on business size and complexity. Smaller implementations may take a few months, while larger projects can extend longer due to integrations and data migration requirements.  Is customisation always required for MYOB Acumatica?  No. Many business requirements can be met through standard configuration. Customisation should only be used when necessary to support critical business processes.  Why is post-implementation support important?  Post-implementation support ensures system stability, addresses user issues and allows the ERP system to evolve alongside business changes.  Can MYOB Acumatica integrate with other business systems?  Yes. MYOB Acumatica supports integrations with various third-party applications, including through its ISV (Independent Software Vendor) marketplace, which offers pre-built solutions for common business needs. These integrations should be planned carefully during implementation to ensure data consistency and long-term maintainability. --- # Odoo Consultant vs Certified Odoo Partner Australia: Enterprise Implementation Guide 2026 - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-consultant-vs-certified-odoo-partner-australia-enterprise-implementation-guide-2026-86 - Category: Odoo ERP Australia - Published: 2026-03-10 - Description: Learn how a certified Odoo partner's enterprise implementation tools, upgrade and partnership knowledge compare to an independent consultant in Australia. So you've picked Odoo. Good move. It's a solid platform and for a lot of Australian businesses it's the right call. Flexible, modern, and considerably more affordable than the SAPs and NetSuites of the world, especially now that [Odoo ERP implementation costs in Australia](/odoo-implementation-packages-for-australian-businesses) are a lot more transparent than they used to be. But here's where things get murky. You jump on Google, type "Odoo consultant Brisbane" or "Odoo partner Australia," and you get a mix of results. Freelancers. Agencies. Some call themselves partners, some call themselves consultants. A few call themselves both. And from the outside, they all look pretty much the same. They're not. The difference between an Odoo consultant and a certified Odoo partner isn't just a label. It affects what tools they can access, how they handle escalations when something breaks, what your upgrade looks like three years from now, and critically, whether you're actually dealing with who they say they are. In 2026, with more providers entering the Australian market, that last point matters more than it ever has. Let's break it down properly. **Quick check before you read further:** If you've already found someone claiming to be an Odoo partner in Australia, take 30 seconds and search their name at [odoo.com/partners](https://www.odoo.com/partners/country/australia-14). If they're not listed there, they are not a certified Odoo partner, regardless of what their website says. We'll explain why this matters below. ## **What actually is an Odoo consultant?** An Odoo consultant is usually a freelancer or small dev shop who's worked on Odoo ERP projects and knows their way around the platform. They might be quite good at what they do. Some have been building on Odoo for years. But they don't have a formal relationship with Odoo SA, the company that builds and maintains the software. They're independent operators. You'll typically find them on Upwork, through LinkedIn, or via referrals. Their engagement model is usually hourly or fixed-price per project. They tend to be strongest at defined, smaller work: installing a module, fixing a bug, setting up a single workflow. Clear scope, clear outcome, in and out. Here's an important nuance on source code. If your business holds an active [Odoo Enterprise subscription](https://www.odoo.com/documentation/19.0/legal/terms/enterprise.html), your consultant _can_ access the Enterprise source code. Any Enterprise subscriber can download the full source from odoo.com. The code is standard Python, not obfuscated. So a consultant working on your Enterprise instance can read, modify, and extend those modules, and build custom addons that interact with Enterprise features. Where it gets different is _how_ they access that code. Consultants work with downloaded archives. They don't get access to Odoo's private GitHub repository, which is reserved for certified partners. That means no version-controlled diffs between releases, no easy tracking of what changed between versions, and no streamlined Git-based development workflow. It's workable, but it's a rougher setup. Consultants can also publish modules on the [Odoo App Store](https://apps.odoo.com/apps/faq) without being a partner. The store is open to all developers. So independent consultants have more capability than people often assume. The question is what's behind the capability: tooling, accountability, and backup when things get complex. ## **What actually is a certified Odoo partner?** A certified Odoo partner is a company that's been vetted by Odoo SA and maintains an active, ongoing commercial relationship with them. And I want to stress "tracked." This isn't a logo you stick on your website after paying a fee. Odoo runs four [partner tiers](https://www.odoo.com/become-a-partner): Learning, Ready, Silver, and Gold. Each tier has real requirements. Revenue targets, certified employees who've passed Odoo's own exams on recent versions, verified client references, and retention rates. These are reviewed quarterly. If numbers drop, the tier drops. If clients are unhappy, Odoo hears about it. To give you an idea of what the bar looks like: Silver partners need to sell 75 net new Enterprise users per year, maintain at least 3 certified employees, and hold a 70% or higher client retention rate. Gold requires 300 new users, 6 certified staff, and 80% retention. These aren't vanity metrics. They're enforced. In exchange, partners get meaningful advantages: access to the private Enterprise GitHub repository for version-controlled development, a dedicated Account Manager at Odoo SA, the [Partnership Knowledge Base](https://www.odoo.com/slides/partnership-knowledge-base-39) covering implementation best practices and project methodology, free Odoo.sh access for testing and development, trial extension codes for prospects, early access to new version training, and lead generation from Odoo's own website. Full transparency: we're an Odoo Silver Partner, based in Brisbane and serving businesses across Queensland, NSW, and Victoria. We have certified v18 experts on staff, 12 verified references, and 100% client retention going into 2026. You can verify all of that yourself at [odoo.com/partners](https://www.odoo.com/partners), and you should verify every provider you speak to before signing anything. I'll show you exactly how further down. ## **The verification problem in 2026** Here's something that's become more relevant as Odoo has grown in Australia: not everyone calling themselves an "Odoo partner" actually is one. There are currently **35 official certified Odoo partners in Australia**, across Gold, Silver, and Ready tiers. Every single one is listed at odoo.com/partners with their tier, certified staff count, client references, and retention rate. This is a public registry. There's no excuse for not checking it. What should concern you is when a provider: - Calls themselves an "Odoo Implementation Partner" in their website title or copy but can't be found on the official partner directory - Has no named team members, no LinkedIn presence, and no verifiable company registration - Has no ABN displayed on their website  - Has client testimonials but no verifiable client references you can actually follow up on This isn't a hypothetical scenario. It's worth spending two minutes on the partner directory before you spend tens of thousands of dollars on an Odoo ERP implementation. ## **Where the difference actually shows up** Enough definitions. Let's talk about where this plays out in practice, because that's what matters when you're mid-project and something isn't working. ### **Enterprise source code access** As mentioned above, both partners and consultants (working on an Enterprise-licensed instance) can access and modify source code. The [Odoo Enterprise Edition License](https://www.odoo.com/documentation/19.0/legal/licenses.html) permits executing, modifying, and running modified versions with a valid subscription. Anyone can build custom addons that extend Enterprise functionality. The difference is the workflow. Partners get access to Odoo's private GitHub repository: proper version control, clean diffs between releases, a professional development pipeline. They also get free Odoo.sh environments for testing and development, and the license explicitly allows partners to use Enterprise in testing environments without an active client subscription. That matters during pre-sales demos and development sprints. If your Odoo ERP implementation requires BAS reporting, payroll localisation, advanced manufacturing, or multi-company consolidation, you're in Enterprise territory. Both consultants and partners can work inside it, but the partner has a more structured toolkit. ### **Support and escalation** This is the area with the most confusion, so let's set the record straight. If your business holds an [Odoo Enterprise subscription](https://www.odoo.com/documentation/19.0/legal/terms/enterprise.html), you can contact Odoo SA support directly. You don't need to go through a partner. The Enterprise Subscription Agreement makes this explicit: customers can work with a partner as their main contact, or directly with Odoo SA. You can switch between models with 30 days' written notice. Every Enterprise subscriber gets unlimited support tickets at no extra charge through odoo.com/help, covering bugs and standard feature guidance. Odoo commits to beginning to handle bug submissions within 2 business days. So what do partners actually get that's different? - **A dedicated Account Manager at Odoo SA** . A named person, not a generic support queue. - **Second-level assistance** on standard features. Partners can escalate complex questions beyond what the standard support channel handles. - **The ability to report bugs on behalf of clients** through the Partners Portal, streamlining the process when the partner already understands the issue technically. - **Contractual obligation to serve as first-level support** for their clients, meaning your partner is triaging and solving most issues before they ever reach Odoo SA. One important caveat for self-hosted deployments: if you work directly with Odoo SA (not through a partner) and you self-host, support for Covered Extra Modules isn't available. That support is only provided to Cloud Platform customers in the direct model. Working through a partner gives you broader support coverage regardless of how you host. An independent consultant doesn't have any of these partner-specific channels. They can help you lodge support tickets through your own Enterprise subscription, but they don't have the dedicated Account Manager relationship or the second-level escalation path. ### **Odoo ERP implementation cost: where the real difference shows up** This is one of the most common questions we get from Australian businesses in 2026, and it's worth addressing head-on rather than dodging it. Per hour, a certified partner's rates are typically higher than a freelance consultant. That's true. But total Odoo ERP implementation cost is often comparable, and in complex projects frequently lower, for a few reasons: - **Partners move faster.** Better tooling, direct GitHub access, and dedicated Odoo SA support channels mean less time spinning on problems that a partner would diagnose quickly. - **Fewer re-do's.** Australian localisation done wrong by an offshore consultant who's never filed a BAS in their life costs real money to fix. A partner who configures GST and STP every week gets it right the first time. - **Upgrades are cheaper long-term.** A partner with early version access and upgrade-specific training anticipates breaking changes. An independent consultant investigates them from scratch and bills you for the time. For a detailed breakdown of what Odoo ERP implementations typically cost for Australian SMEs, see our [Odoo implementation pricing page](/odoo-implementation-packages-for-australian-businesses). We publish our packages with real numbers because we think you should know what you're getting into before any conversation starts. ### **The upgrade question** This is where a lot of businesses get surprised by costs they didn't plan for. The [Odoo upgrade service](https://www.odoo.com/documentation/19.0/administration/upgrade.html) at upgrade.odoo.com is free for all Enterprise subscribers, not just partners. Any business with an active Enterprise subscription can submit their database, and Odoo runs it through automated upgrade scripts. The recommended process: run a test upgrade first, validate workflows, report issues to Odoo's Upgrade Team, then submit your production upgrade when satisfied. Odoo also publishes an open-source [upgrade-util package](https://github.com/odoo/upgrade-util) on GitHub. Anyone can use it. The partner advantage: early access to new versions before general release, yearly upgrade training after each new version ships, and GitHub repository access to track exactly what changed between versions at a code level. In practice, this means a partner can anticipate breaking changes in custom modules that an independent consultant would discover during the upgrade itself, and bill you for the time to fix. ### **Australian localisation** This one bites harder than people expect. GST handling. BAS reporting. Superannuation. Single Touch Payroll. State-specific obligations. These aren't optional. They're compliance requirements, and the ATO doesn't care that your ERP provider didn't understand Australian tax law. A Brisbane-based Odoo partner configures this every week across every client engagement. An offshore consultant you found on a freelancer platform may have never seen a BAS in their life. A misconfigured GST setup doesn't just cause headaches. It can cost thousands in compliance penalties and trigger exactly the kind of ATO attention you don't want. This isn't strictly a partner vs consultant issue. It's a "do they know Australian compliance requirements" issue. But in practice, Australian-based [Odoo partners operating in Queensland and NSW](/solutions/odoo) have deeper experience here simply because they deal with it across every client engagement. ### **Accountability** Odoo actively monitors partner performance. Retention rates, client satisfaction, implementation quality, all tracked on a quarterly basis. If a partner slips, they lose their tier, their Account Manager access, and their commission rates. That's a genuine incentive to deliver. With an independent consultant, the only accountability is their reputation. That can be strong. But it's not the same as having a third party keeping score, especially when you can't find the consultant's company registration or verify who they actually are. ### **Training and current knowledge** Partners get access to the [Partnership Knowledge Base](https://www.odoo.com/slides/partnership-knowledge-base-39): implementation methodology, project management, technical best practices, 36+ lessons and 49+ hours of content. They attend Odoo's annual training, get certified on each new release, and receive version-specific upgrade training. General resources like the [eLearning platform](https://www.odoo.com/slides), functional documentation, and the community forum are publicly available to everyone. Certification exams are open to anyone, not just partner employees. An independent consultant can absolutely get certified. The difference is that partners have a contractual requirement to maintain certified staff, so it's not optional. ## **When a consultant is actually the right call** We're a partner, but we're not going to pretend a partner is always the answer. That wouldn't be honest. An independent consultant can be a great fit when: - **The job is small and well-defined.** Install a module. Fix a report. Tweak a workflow. Tight scope, clear outcome, no long-term support needed. - **Budget is tight and scope matches.** Small operation running Community edition with one or two modules. A freelancer can sort you out without the overhead of a full engagement. - **You've got Odoo expertise in-house.** Your team knows the platform and you need an extra pair of hands for a few weeks. Contractor model makes sense. - **You're on Community with no Enterprise plans.** If you're not going Enterprise, some partner-specific advantages become less relevant. Low complexity, clear scope, limited risk. A good independent consultant can deliver in those situations. ## **When you genuinely need a certified Odoo partner** A certified partner earns their keep when the stakes go up: - **Full Odoo ERP implementation across your business.** Sales, inventory, manufacturing, accounting, the whole stack. When modules need to talk to each other seamlessly, you need someone who understands how the full platform integrates, not just one corner of it. - **Enterprise features.** Advanced manufacturing, multi-company, Odoo Studio, quality management. Enterprise-only, and while both consultants and partners can work with the code, partners have a more structured workflow and testing environment. - **System integrations.** Xero, Shopify, Power BI, shipping carriers, payment gateways. Integration work is where complexity compounds fast. A dedicated Account Manager and second-level Odoo SA support is the difference between a two-day fix and a two-week problem. - **Australian compliance done right from day one.** GST, BAS, STP, super. Getting these wrong is expensive. Getting them right requires someone who's done it before. Recently. In Australia. - **Long-term relationship.** ERP is not set-and-forget. You'll need upgrades, new modules, bug fixes, and training as your business grows. A certified partner is structured for that ongoing relationship. A freelancer may have moved on to their next gig. ## **How to verify a partner is legitimate (takes two minutes)** This is the easiest due diligence you'll ever do, and it's surprising how many businesses skip it before committing to a six-figure Odoo ERP implementation. Go to [**odoo.com/partners, filter by Australia**](https://www.odoo.com/partners/country/australia-14). Every certified partner is listed there with their tier, references, certified expert count, and retention rate. If a provider tells you they're a certified Odoo partner and they're not on that page, they are not a certified partner. Full stop. Here's what each metric tells you: - **Tier (Learning / Ready / Silver / Gold):** Higher tiers mean higher thresholds for revenue, certifications, and proven client success. Learning partners aren't listed publicly. If you can see them on the page, they're Ready tier or above. - **Certified Experts:** Real people who've passed Odoo's certification exam on one of the three most recent versions. The exam covers 16+ core apps with ~120 questions, requiring 70% to pass with penalties for wrong answers. Not a rubber stamp. - **Client References:** Verified by Odoo, not self-reported. Higher numbers mean more implementations under their belt. - **Retention Rate:** How many clients from the last 3 years are still active. The metric that's hardest to fake. If clients keep coming back, the partner is doing something right. Beyond the partner directory, also check: - **ABN Lookup at abr.business.gov.au**. Any legitimate Australian business should have a registered ABN. If they're invoicing you for significant work and you can't find their ABN, that's a red flag. - **Named team members.** A real consultancy has identifiable people. No team page, no LinkedIn profiles connecting to the business? That warrants a closer look. - **ASIC registration.** Companies operating in Australia can be verified at asic.gov.au. None of this takes more than five minutes. For a decision that affects your entire business operations, it's worth doing. ## **Questions worth asking before you sign anything** Whether you're talking to a partner or a consultant, these questions will sort the ones who can deliver from the ones who are good at sales calls: - Are you a certified Odoo partner? What tier? Can you show me your listing on odoo.com/partners? - How many of your team are certified on the current Odoo version? - Can you give me a verifiable client reference from an Australian business similar to mine? - Have you done Australian localisation before? Walk me through how you handle GST, BAS, and STP. - What does your upgrade process look like when the next major version drops? - When you hit a complex bug, what's your escalation path? Do you have a dedicated contact at Odoo SA? - What's your total Odoo ERP implementation cost for a business our size? What drives that number up or down? - Will I own the custom code? Where does it live and how do I access it if we ever part ways? Anyone worth hiring will answer these straight. If someone gets vague or changes the subject, that's all the information you need. ## **Frequently asked questions** ### **What's the actual difference between an Odoo consultant and an Odoo partner?** A consultant is an independent operator with Odoo skills but no formal relationship with Odoo SA. A partner has been vetted, holds active certifications, and gets access to the private Enterprise GitHub repository, a dedicated Account Manager at Odoo SA, the Partnership Knowledge Base, and partner-only training. Both can work with Enterprise source code if the client has a valid subscription, but partners have a more structured toolkit and direct escalation channels. ### **How much does an Odoo ERP implementation cost in Australia?** Most Australian SMEs invest between $25,000 and $120,000 for a full Odoo ERP implementation, depending on user count, module complexity, integrations, and customisation requirements. Smaller implementations covering core modules (CRM, Sales, Inventory, Accounting) typically start from $25,000. Enterprise rollouts with manufacturing, multi-warehouse, and complex integrations generally exceed $120,000. See our [Odoo implementation pricing page](/odoo-implementation-packages-for-australian-businesses) for a full breakdown of what's included at each level. ### **Can a consultant access Odoo Enterprise source code?** Yes, if the client has an active Enterprise subscription. Any Enterprise subscriber can download the full source code from odoo.com. The [Odoo Enterprise Edition License](https://www.odoo.com/documentation/19.0/legal/licenses.html) permits modifying and running modified versions with a valid subscription. Consultants can also build and sell custom addons on the Odoo App Store. The key difference is that partners get access to the private GitHub repository for version-controlled development, which consultants do not. ### **Can I contact Odoo SA support directly without a partner?** Yes. The [Enterprise Subscription Agreement](https://www.odoo.com/documentation/19.0/legal/terms/enterprise.html) explicitly allows customers to work with Odoo SA directly for bug fixes, support, and upgrades. Every Enterprise subscriber gets unlimited support tickets at no extra charge. Partners add value through first-level support, a dedicated Account Manager, and second-level escalation for complex issues. One caveat: if you self-host and work directly with Odoo SA without a partner, support for Covered Extra Modules is unavailable. ### **Is the Odoo upgrade service only available through partners?** No. The [upgrade service](https://www.odoo.com/documentation/19.0/administration/upgrade.html) at upgrade.odoo.com is free for all Enterprise subscribers. You submit your database with your subscription code and Odoo handles the migration. Partners get the advantage of early access to new versions and yearly upgrade training, which helps them anticipate and resolve issues faster, but the core service is available to everyone. ### **Are partners always more expensive?** Per hour, usually yes. But total Odoo ERP implementation cost is often comparable because partners move faster with better tooling and direct Odoo SA support channels. The real gap shows up at upgrade time and during complex integrations, where a partner's early version access, upgrade training, and GitHub repository access can significantly reduce total hours, and therefore total cost. ### **How do I verify if an Odoo provider is a real certified partner?** Go to [odoo.com/partners](https://www.odoo.com/partners/country/australia-14) and filter by Australia. There are 35 certified partners currently listed. Every legitimate certified partner is on that page with their tier, certified staff, client references, and retention rate. If someone claims to be a certified Odoo partner and isn't listed, they aren't one, regardless of what their website says. You can also verify their Australian business registration at [abr.business.gov.au](https://abr.business.gov.au/). ### **Why does Australian localisation matter so much?** Because the ATO doesn't grade on a curve. GST, BAS reporting, super, STP: these have to be configured correctly or you're looking at compliance issues that cost real money to fix. A provider who hasn't worked with Australian requirements before can deliver something that looks right on the surface but falls apart at reporting time. **Looking for a certified Odoo partner in Queensland?** We're [**Auboros**](/), a Brisbane-based Odoo Silver Partner serving businesses across Queensland, NSW, and Victoria. We've got 100% client retention, verified references on the Odoo partner directory, and we publish our [Odoo ERP implementation pricing upfront](/odoo-implementation-packages-for-australian-businesses) because we think you should know what you're getting into before any conversation starts. If you're evaluating Odoo in 2026 and want a straight conversation about whether it's the right fit, [**book a free consultation**](/appointment). No pressure, no 47-slide deck. Just an honest look at your requirements and what an implementation actually involves. --- # Odoo ERP Implementation in Australia: Cost, Timeline and Traps (2026 Guide) - Canonical URL: https://www.auboros.com/blog/odoo-erp-australia-6/odoo-erp-implementation-in-australia-complete-guide-for-2026-87 - Category: Odoo ERP Australia - Published: 2026-03-10 - Description: What an Odoo implementation costs in Australia, how long each phase takes, and what to ask a partner before signing. From a certified Odoo Silver Partner. # Odoo ERP Implementation Australia: 2026 Guide Most Australian businesses that come to us have already looked at Odoo. They've seen the demo, liked the price, and started thinking about what an implementation would actually involve. Then they've run into a wall of conflicting information: vague timelines, wildly different cost estimates, and marketing material that doesn't help them make a decision. This guide cuts through that. It's written for Australian business owners and operations managers who want to know what an Odoo ERP implementation actually looks like, what it costs in Australian dollars, how to choose a partner from the 33 registered in this country, and what trips people up along the way. ## **What does an Odoo ERP implementation actually involve?** The word "implementation" gets thrown around loosely. In practice, it means taking Odoo from a blank system to a configured, data-loaded, trained-up platform that your team uses every day instead of spreadsheets or legacy software. It's a project, not a product. Your partner isn't just installing software; they're rebuilding your workflows in a new system, migrating your historical data, making sure your Australian tax obligations are configured correctly, and training your people to use it all. ### **The six phases most Australian projects follow** Most Odoo implementations move through six distinct phases. The names vary by partner, but the substance doesn't. - **Discovery and scoping.** Before a single module is configured, a good partner will spend time mapping your current processes. Which parts of the business are in scope? What does your chart of accounts look like? What integrations are required? This phase shapes everything that follows, and skipping it is the single most common cause of project overruns. - **System design.** Once scope is agreed, your partner designs how Odoo will be configured: which modules, which workflows, what custom fields or automations are needed. A well-run design phase reduces surprises during build. - **Configuration and customisation.** The system takes shape. Standard Odoo modules are configured first. Custom development, if required, happens here. This is also where most projects expand in scope, so keep a close eye on change requests. - **Data migration.** Your existing data, whether it lives in MYOB, Xero, Excel, or a combination, gets cleaned, mapped, and loaded into Odoo. Poor data quality is one of the most common causes of delay. - **Training and user acceptance testing.** Your team tests the system against real scenarios before go-live. This phase often surfaces gaps the configuration phase missed. - **Go-live and support.** The system goes live. A good partner provides structured support during the first few weeks, when issues are most likely to appear. ## **How much does Odoo implementation cost in Australia?** The honest answer: it depends on your size, your complexity, and your partner's rates. For a small Australian business implementing two to four Odoo modules (accounting, CRM, and inventory, for example), expect to spend $15,000 to $40,000 on implementation services. For a mid-market business with multiple departments, integrations, and custom requirements, $60,000 to $150,000 is a realistic range. Enterprise-scale rollouts with heavy customisation can exceed $300,000. On top of implementation fees, you'll pay Odoo's subscription. [Odoo Enterprise](https://www.odoo.com/pricing) is priced per user per month. At current exchange rates, Australian businesses are paying roughly AUD $40 to $65 per user per month for the Standard plan. The Custom plan, required for [Odoo.sh](http://Odoo.sh) hosting and custom development, costs more. Australian Odoo partners typically charge between AUD $120 and $350 per hour depending on their experience and certification tier.   For a detailed look at what you'll actually pay for a structured Odoo project in Australia, see our [transparent implementation packages](/odoo-implementation-packages-for-australian-businesses). ### **What drives costs higher (and how to manage them)** Three things consistently push Odoo implementation costs above initial estimates. **Scope creep** is the biggest. As more team members get involved and see what Odoo can do, they want more of it. This is natural, but it adds cost. Budget a 20 to 30% contingency from the start, and establish a formal change request process with your partner before the project begins. **Over-customisation** is the second driver. Odoo covers an enormous amount out of the box. Every customisation adds development cost upfront and makes future upgrades harder and more expensive if not done correctly. If you're told a standard business process needs to be custom-built, ask why and consider getting a second opinion. **Poor data quality** is the third. If your existing customer records, product lists, or chart of accounts are messy, migration takes longer and costs more.  This applies beyond basic data too. If you're implementing inventory or manufacturing modules, you need clarity on your internal product structure: the units of measure you sell in, how your bills of materials are constructed, and where sub-assembly processes sit in your workflow.  If you don't have clear answers to those questions before migration starts, you'll be making them up under pressure during the project. Start cleaning and documenting your data before your implementation begins, not during it. ## **How long does an Odoo implementation take?** A focused implementation of two to four modules for a small business typically takes six to ten weeks. A full-suite rollout for a 30-person business with inventory, manufacturing, and accounting integrations is more likely to take four to six months. Large or complex projects can run longer. Timelines stretch when scope expands mid-project, when data migration is underestimated, or when key decision-makers aren't available to approve configurations. One practical tip: avoid scheduling your go-live near Australia's financial year-end in June, or your own business's peak season. Cutting over to a new ERP when your team is at maximum load is a risk you don't need to take. ## **Choosing the right Odoo partner in Australia** Australia has [33 registered Odoo partners](https://www.odoo.com/partners/country/australia-14), but not all are equal. You'll encounter three tiers: Ready, Silver and Gold partners . (Gold exists globally; there are currently no Gold partners in Australia.) ### **What a Certified Odoo Partner actually means** Odoo's partner programme has verifiable entry criteria. To reach Silver tier, a partner must achieve at least 75 new paid users per year, maintain three [Odoo-certified staff members](https://www.odoo.com/become-a-partner), and hold a 70% client retention rate. These figures are verified by Odoo SA and listed on the official partner directory, not self-reported marketing claims. Auboros is a Silver-tier Odoo partner. We hold Odoo 18 certifications, have 12 verified client references, and have maintained 100% client retention across every implementation we've run. That retention figure matters more than a sales pitch: a partner losing clients doesn't stay at Silver for long. For a deeper breakdown of what partner tiers mean for your project risk, see our guide on [the difference between an Odoo consultant and a certified partner](/blog/odoo-erp-australia-6/odoo-consultant-vs-certified-odoo-partner-australia-enterprise-implementation-guide-2026-86). ### **Five questions to ask before signing anything** 1. **How many Odoo implementations have you completed in the last 12 months?** A ballpark is fine. Be cautious about vague or evasive answers. 2. **Do you have references from Australian businesses in a similar industry?** Talking to existing clients is the best due diligence you can do. 3. **What does your discovery process look like, and how do you handle scope changes?** Partners without a defined discovery process will cost you more later. 4. **How do you manage Odoo upgrades?** The [upgrade service from Odoo](https://upgrade.odoo.com/) is free for all Enterprise subscribers, but your partner still needs to coordinate the process on your behalf and upgrade custom modules. 5. **What does post-go-live support look like, and what does it cost?** The go-live is not the end of the project. Ongoing support is where many partner relationships succeed or fail. ## **Australian compliance: BAS, GST, and STP from day one** This is where most global Odoo implementation guides fall short. Australian businesses have compliance obligations that need to be built into the system from the start, not retrofitted later. **Business Activity Statement (BAS)** reporting is mandatory for most Australian businesses registered for GST. Odoo's accounting module supports BAS reporting, but it needs to be configured correctly for your reporting period, tax codes, and lodgement frequency. The [ATO's BAS guidance](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas) outlines what's required; your partner needs to know how to implement it in Odoo. Get this wrong and you'll be correcting it while trying to run your business. GST is set at 10% and applies to most goods and services in Australia. Odoo handles GST natively, but your tax mapping, including any GST-free or input-taxed transactions, needs to be reviewed by someone who understands Australian tax requirements rather than just Odoo configuration. **Single Touch Payroll (STP)** is the ATO's real-time payroll reporting system. If you're running payroll through Odoo, your STP configuration needs to meet the [ATO's current requirements](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll). A partner who doesn't raise BAS, GST, and STP in the first discovery conversation hasn't implemented many Australian projects. These aren't optional extras; they're foundational. ## **The most common Odoo implementation mistakes** We've seen the same mistakes repeat across dozens of projects. They're almost never about the software itself. **Skipping discovery.** Every hour spent in discovery saves three in rework. Businesses that push to start configuring immediately, without mapping their processes first, almost always pay for it during the build phase. **Trying to replicate your old system exactly.** Odoo works differently from MYOB AccountRight, Xero, or whatever you're replacing. If you insist on recreating every quirk of your existing workflow, you'll end up with an expensive version of what you had before, plus Odoo's licence cost on top. Let your partner challenge your assumptions. **Under-investing in training.** Your team doesn't need to know every feature on day one, but they do need to be confident in their core daily workflows. Budget real training time, not just a one-hour handover call. Low user adoption is consistently cited as one of the top reasons ERP implementations fail to deliver value. **Going live before the system is ready.** The pressure to close out a project is real, especially when partners are billing by the hour. But a rushed go-live leads to workarounds, frustrated staff, and eventually paying someone else to fix what was missed. Agree on clear readiness criteria with your partner before the project starts, and hold to them. **Choosing a partner based on price alone.** The cheapest implementation rarely stays that way. A poorly configured system costs you in lost productivity, rework, and, in many cases, a second implementation to sort out what the first one got wrong. Our [Odoo implementation services](/solutions/odoo) page sets out what a properly scoped project looks like. ## **Frequently asked questions** ### **How much does Odoo ERP implementation cost in Australia?** For small businesses implementing two to four modules, expect $15,000 to $40,000 in partner fees. Mid-market businesses with multiple departments, integrations, and custom requirements typically spend $60,000 to $150,000. These figures cover implementation services only, not Odoo's subscription fees, which run roughly AUD $45 to $65 per user per month for Enterprise at current exchange rates. ### **How long does an Odoo implementation take in Australia?** Small, focused implementations typically take six to ten weeks. A full-suite rollout for a 30-plus-person business is more likely to take four to six months. The biggest drivers of delay are scope expansion mid-project, data quality issues, and limited availability of key decision-makers during the build phase. ### **Do I need a certified Odoo partner to implement Odoo in Australia?** You're not legally required to use a certified partner, but most businesses shouldn't implement Odoo without one. The configuration complexity, Australian compliance requirements, and data migration risks are significant. If you do engage a partner, Silver-tier certification is a reasonable baseline for quality assurance. It means Odoo SA has verified their client volumes, staff certifications, and retention rates. ### **Does Odoo handle BAS and GST reporting for Australian businesses?** Yes, Odoo's accounting module supports BAS reporting and GST, but it needs to be configured correctly for your Australian tax obligations, including tax codes, GST rates, and reporting periods. It's not plug-and-play. You need a partner who understands ATO requirements and can validate the configuration before go-live. ### **What is the difference between Odoo Community and Odoo Enterprise?** Community is the free, open-source version with a limited module set and no official support from Odoo SA. Enterprise is the paid version with the full module suite, direct support, and access to the free upgrade service. Most Australian businesses implementing across multiple departments will need Enterprise. Community is better suited to businesses with strong in-house technical resources who want to manage everything themselves. **Planning an Odoo implementation in Australia?** We work with Australian businesses at every stage, from initial scoping to post-go-live support. Auboros is a Brisbane-based, Silver-certified Odoo partner with 12 verified references and 100% client retention across every project we've run in Queensland and beyond. If you're working through the decision and want a straight conversation about what your project would actually involve, [**book a free consultation**](/appointment). No hard sell, just an honest discussion about whether Odoo is the right fit and what it would take to implement it properly. --- # MYOB Acumatica for Professional Services Firms in Australia - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-for-professional-services-firms-in-australia-88 - Category: MYOB Acumatica Australia - Published: 2026-03-10 - Description: Is MYOB Acumatica right for your professional services firm? This guide covers project billing, WIP tracking, and what Australian businesses should expect. # MYOB Acumatica for Professional Services Australia Most accounting software was built for businesses that sell things. Professional services firms don't sell things; they sell time, expertise, and outcomes. That's a different operating model, and it creates a specific set of problems when you try to run it on general-purpose accounting software. Timesheets that don't talk to billing. Project profitability you can't see until after the fact. WIP tracked in someone's spreadsheet, or not properly tracked at all. MYOB Acumatica was designed with this in mind. Its project accounting module isn't a bolt-on; it's native to the platform. That means time entries, expenses, billing, and financial reporting all work from the same data set, without the manual reconciliation that most services firms spend too much time on. This guide covers what the platform actually does for professional services businesses, who it's right for, and what to expect from an implementation in Australia. ## **Why professional services firms are different as ERP users** Product-based businesses track inventory, purchase orders, and sales margins. Professional services businesses track hours, contract types, resource availability, and project profitability. These are different problems, and most entry-level accounting tools are designed for the first one, not the second. The practical result is that services firms often end up running two or three systems in parallel: an accounting tool for financials, a separate timesheet platform, and spreadsheets to fill the gaps between them. That works at small scale, but it breaks down as project volume grows, billing arrangements become more varied, or the business adds entities. If you're spending meaningful time at the end of each month reconciling data between systems before you can issue invoices, that's a system design problem rather than a process problem. It won't get better by working harder at it. This is the gap that [MYOB Acumatica's project accounting capabilities](/solutions/myob) are built to address. ## **What MYOB Acumatica does for professional services businesses** ### **Project billing: time and materials, fixed price, and everything in between** One of the more useful things about MYOB Acumatica's billing module is that it supports multiple billing arrangements within the same system, and within the same project if needed. [MYOB Acumatica supports](https://www.myob.com/au/erp-software/features/project-accounting-software) time and materials, fixed price, cost-plus, and milestone billing. For firms running a mix of contract types across their client base, this is significant. You're not working around the system or maintaining separate tracking for different billing arrangements. Invoices are generated directly from project data, which means you're not re-entering time and expense information at billing time. That removes a reconciliation step that most professional services firms do every month without questioning whether they should have to. ### **Timesheet and expense management** Staff, contractors, and partners can log timesheets from any device. Leave and public holidays are reflected automatically in the timesheet view, which removes one of the common friction points when reviewing timesheets at period end. Expense claims attach to the relevant project, keeping your cost data accurate without manual allocation afterwards. For firms where cost-per-project matters (and it should matter to every services business), having time and expense data captured directly against projects rather than reconciled into them later is a practical improvement over most alternative setups. ### **Work in progress and project profitability reporting** WIP (work in progress) tracking is where a lot of professional services firms either have a real problem or are managing it poorly without realising it. MYOB Acumatica provides real-time WIP reporting: unbilled work, project progress against budget, and financial performance at the task level, not just the project level. The 2024.2 platform release included specific improvements to WIP reporting, with enhanced visibility into current project progress and the financial performance of individual project tasks. That's useful for project managers making resourcing and billing decisions mid-project, not just for the finance team at month-end. You can compare budgets and expected revenue against actuals in real time, rather than discovering margin problems after a project has closed. ## **Which professional services industries use MYOB Acumatica in Australia?** The platform is used across a range of services businesses in Australia. The most common we see at Auboros are management and business consulting firms, engineering and architecture practices, IT services and technology consultancies, project-based contractors, and accounting or financial services firms with complex client billing requirements. MYOB Acumatica also has specific functionality for not-for-profit organisations, construction and project-based businesses, and field services operations, all of which sometimes overlap with professional services depending on how the business is structured. If your business spans more than one of these categories, a unified platform tends to serve you better than specialist tools for each. Understanding why mid-market firms across these industries are moving to cloud-based ERP is worth reading if you're still weighing the decision; our article on [why mid-market firms are moving to cloud ERP](/blog/insights-5/cloud-erp-mid-market-australia-visibility-boost-7) covers the shift in more detail. ## **When does a professional services firm actually need MYOB Acumatica?** The question isn't really about headcount. We've seen 12-person firms that badly needed a proper project accounting platform, and 80-person firms still managing reasonably well on AccountRight. The trigger is complexity, not size. ### **Signs you've outgrown your current setup** - **Your timesheets and billing system don't connect.** Every billing cycle involves manual reconciliation between two or more systems before you can issue invoices. - **Project managers can't see profitability in real time.** Getting a read on how a project is tracking financially requires a request to the finance team and a wait for a report. - **You're managing different billing arrangements in spreadsheets.** Fixed-price clients in one place, T&M clients in another, and no single view across all of them. - **WIP isn't properly tracked.** You know roughly what's been worked but not yet billed, but you couldn't produce an accurate WIP figure on demand. - **You have more than one entity or bill in multiple currencies.** Your current software handles one entity adequately but requires workarounds for anything more complex. - **You're losing money on projects without a clear picture of why.** Your cost data and time data are in different places, so post-project profitability analysis is slow or incomplete. If two or more of those sound familiar, you're likely past the point where better accounting software helps. You need a platform with native project accounting built in from the ground up. ## **What does implementation look like for a professional services firm?** Professional services implementations tend to move faster than manufacturing or distribution projects, mostly because there's no inventory to configure and less complexity around supply chain and warehousing. A typical services firm implementing MYOB Acumatica's core financials plus project accounting can expect 10 to 16 weeks from project kick-off to go-live, assuming scope is well-defined upfront. The areas that take the most time are almost always billing configuration and data migration. Billing configuration takes time because you need to map your existing contract types, rate cards, and billing rules into the system. Data migration takes time because most services firms have client and project history spread across multiple systems, spreadsheets, and inboxes. Getting that data clean before migration starts is worth the effort; trying to do it under project pressure during the implementation is not. For guidance on what to look for in a partner before you sign anything, see our article on [choosing the right MYOB Acumatica implementation partner](/blog/myob-acumatica-australia-7/choose-right-myob-acumatica-implementation-services-5). The questions you ask at the start of that process have a significant effect on how the project runs. Budget for ongoing support after go-live too, not just the implementation itself. As your team gets comfortable with the platform, you'll want to adjust billing configurations, build out project templates, and refine reporting. That work happens in the months after go-live, not before it. ## **MYOB Acumatica vs the alternatives for Australian professional services** **MYOB AccountRight** is the most common system we see firms moving from. AccountRight handles accounting well for smaller businesses, but it doesn't have native project accounting or WIP tracking. If you're using it alongside a separate timesheet tool and reconciling them manually each month, that's a workaround, not a solution. [MYOB's own comparison](https://www.myob.com/au/erp-software/alternatives/acumatica-vs-accountright) is direct about this: AccountRight is for small-to-medium businesses with straightforward needs; Acumatica is for mid-market organisations with more complex requirements. **Xero** is common among younger professional services firms. It handles accounting well but relies on third-party integrations for project and time management. Those integrations can work at small scale, but they add ongoing cost, create data sync dependencies, and tend to become maintenance burdens as project volume grows. You end up owning the reliability risk of the integration, not just the software. **NetSuite** is the other mid-market platform that regularly comes up. It has strong project accounting capabilities and is a genuine alternative for larger firms. The practical differences for most Australian businesses are cost (NetSuite is typically more expensive), a smaller pool of Australian implementation partners with deep local compliance knowledge, and MYOB's long-standing track record with Australian tax obligations including BAS and [Single Touch Payroll](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll). For most Australian professional services firms in the 20 to 200 employee range needing proper project accounting, MYOB Acumatica is the strongest option that doesn't require the complexity and cost of a top-tier enterprise system. ## **Frequently asked questions** ### **Is MYOB Acumatica suitable for small professional services firms?** MYOB Acumatica is designed for mid-market businesses, typically those with 20 or more staff or significant project accounting complexity. Smaller firms are usually better served by AccountRight, Xero, or a specialist practice management tool. The simplest test: if your current billing and project tracking setup is genuinely causing you pain and costing you hours each month, it's worth a conversation about whether Acumatica is the right next step. ### **Does MYOB Acumatica handle time and materials billing in Australia?** Yes. MYOB Acumatica supports time and materials billing natively, alongside fixed price, cost-plus, and milestone billing. You can apply different billing types to different projects or to individual tasks within a project. Invoices are generated directly from timesheet and expense data, so there's no manual re-entry at billing time and no reconciliation step between your time tracking and your accounting system. ### **How does MYOB Acumatica handle GST on professional services invoices?** MYOB Acumatica is built for Australian tax requirements and handles GST at 10% on professional services invoices. Tax codes and GST treatment are configured during implementation and link directly to your [Business Activity Statement (BAS)](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas) reporting, so GST collected on services is captured correctly for ATO lodgement. If any of your services may qualify for GST-free treatment, confirm that with your accountant before configuration is finalised. ### **What is the difference between MYOB Acumatica and MYOB AccountRight for services firms?** AccountRight is a cloud-assisted accounting tool for small and medium businesses. It handles invoicing, payroll, and basic reporting, but it doesn't have native project accounting or WIP tracking. MYOB Acumatica is a full ERP platform with project billing, timesheet management, resource planning, multi-entity support, and real-time profitability reporting. They're not competing versions of the same product; they're designed for different business sizes and levels of complexity. ### **How long does a MYOB Acumatica implementation take for a professional services business?** Most professional services implementations take 10 to 16 weeks from project kick-off to go-live, with scope focused on financials and project accounting. Implementations that include payroll, multi-entity configuration, or third-party integrations will take longer. The most common causes of delay are billing configuration complexity and data migration from legacy systems and spreadsheets. **Considering MYOB Acumatica for your professional services firm?** Auboros is an official MYOB Acumatica Partner based in Brisbane, working with professional services firms across Queensland and beyond. We focus on getting billing configuration and project accounting right from the start, so you're not fixing it six months after go-live. If you want a straight conversation about whether MYOB Acumatica fits your firm and what implementation would actually look like, [**book a free consultation**](/appointment). No obligation, no pitch deck. --- # Cloud ERP Mid-Market Australia - Canonical URL: https://www.auboros.com/blog/insights-5/cloud-erp-mid-market-australia-visibility-boost-7 - Category: Insights - Published: 2026-03-09 - Description: Discover how cloud ERP delivers 96% visibility gains for mid-market Australian manufacturing, construction, and services firms. Learn key features, ROI # Cloud ERP Mid-Market Australia ![Discover how cloud ERP delivers 96% visibility gains for mid-market Australian manufacturing, construction, and services firms. Learn key features, ROI](/images/blog/cloud-erp-mid-market-australia-visibility-boost-7-43fcb498.webp) By 2026, [70% of ERP market revenue shifted to cloud-based deployments](https://www.forbes.com/councils/forbesbusinesscouncil/2025/04/25/enterprise-resource-planning-for-mid-market-enterprises/), marking a decisive transformation in how mid-market businesses manage operations. For Australian operational leaders in manufacturing, construction, and professional services, this shift represents more than a technology upgrade. It’s a strategic response to fragmented systems, manual processes, and limited real-time visibility that throttle growth. Cloud ERP delivers unified, scalable platforms that replace disconnected spreadsheets with a single source of truth, enabling smarter decisions and faster execution. ## Table of Contents - [Introduction To Cloud ERP For Mid-Market Businesses](#introduction-to-cloud-erp-for-mid-market-businesses) - [How Cloud ERP Addresses Industry-Specific Operational Complexities](#how-cloud-erp-addresses-industry-specific-operational-complexities) - [Key Cloud ERP Features Driving Operational Efficiency And Growth](#key-cloud-erp-features-driving-operational-efficiency-and-growth) - [Overcoming Challenges And Misconceptions In Cloud ERP Adoption](#overcoming-challenges-and-misconceptions-in-cloud-erp-adoption) - [Practical Benefits: Operational Improvements And ROI Of Cloud ERP](#practical-benefits-operational-improvements-and-roi-of-cloud-erp) - [Choosing And Scaling Cloud ERP For Mid-Market Australian Businesses](#choosing-and-scaling-cloud-erp-for-mid-market-australian-businesses) - [How Auboros Supports Your Cloud ERP Journey](#how-auboros-supports-your-cloud-erp-journey) - [Frequently Asked Questions About Cloud ERP For Mid-Market Australian Businesses](#frequently-asked-questions-about-cloud-erp-for-mid-market-australian-businesses) ## Key Takeaways | Point | Details | | --- | --- | | Visibility Improvement | Cloud ERP adoption drives a 96% boost in operational visibility and cuts reporting time by 30%. | | Industry Fit | Manufacturing, construction, and professional services gain sector-specific modules that address unique workflow complexities. | | Cost Savings | Automation through cloud ERP reduces operational costs by 20-30% while improving forecast accuracy. | | Scalable Architecture | Modular, composable ERP systems allow mid-market firms to scale without costly overhauls or rip-and-replace cycles. | ## Introduction to Cloud ERP for Mid-Market Businesses The 70% cloud adoption rate in ERP deployments by 2025 reflects a fundamental shift in how Australian mid-market businesses approach operational management. Legacy on-premise ERP systems struggle to keep pace with today’s demands for agility, remote access, and seamless integrations. They lock data in silos, require expensive hardware refreshes, and complicate collaboration across distributed teams. Mid-market firms in manufacturing, construction, and professional services face particularly acute challenges. You’re managing complex supply chains, coordinating project budgets across multiple sites, or tracking billable hours for clients spread nationwide. Manual processes and fragmented tools create bottlenecks, errors, and missed opportunities. Cloud ERP solves these problems by delivering: - Real-time data access from any device, anywhere, enabling faster response to operational changes - Automatic software updates that eliminate costly upgrade projects and keep your systems current - Scalable infrastructure that grows with your business without upfront capital investment - Seamless integrations with supply chain, CRM, and industry-specific tools that unify workflows The shift to cloud isn’t just about moving software offsite. It’s about gaining operational flexibility, improving visibility, and building systems that support growth rather than constrain it. Understanding [cloud ERP trends](https://auboros.com/blog/our-blog-5) helps you evaluate whether your current systems can sustain your ambitions or if a cloud-first approach makes strategic sense. ## How Cloud ERP Addresses Industry-Specific Operational Complexities Generic ERP systems force you to bend operations around software limitations. Cloud ERP platforms built for mid-market sectors do the opposite, adapting to your workflows with industry-specific modules that tackle real operational challenges. **Manufacturing:** [Growing mid-market manufacturers need deep manufacturing and supply chain functionality](https://blog.nbs-us.com/what-growing-mid-market-manufacturers-should-look-for-in-cloud-erp) including production planning, quality management, demand forecasting, and lot/serial traceability. You’re juggling bill of materials changes, tracking component availability, managing work orders across production lines, and ensuring quality standards at every stage. Cloud ERP consolidates these processes, giving you visibility from raw material procurement through finished goods delivery. **Construction:** Project-based operations require budget tracking, procurement coordination, subcontractor management, and compliance documentation across multiple sites. Cloud ERP for construction integrates project management with financial controls, letting you monitor costs in real time, manage change orders efficiently, and ensure materials arrive when crews need them. You avoid cost overruns by catching variances early and improving communication between site teams and head office. **Professional Services:** Workflow automation, financial tracking, and resource scheduling define success in consulting, engineering, and advisory firms. Cloud ERP helps you allocate staff to projects based on skills and availability, track time accurately for client billing, and monitor project profitability as work progresses. You replace manual timesheets and spreadsheet-based resource planning with systems that update automatically. | Industry | Core Challenge | Cloud ERP Solution | | --- | --- | --- | | Manufacturing | Production planning complexity, quality control, inventory accuracy | Real-time BOM management, automated work orders, integrated quality checks | | Construction | Multi-site coordination, budget overruns, procurement delays | Project-based accounting, subcontractor portals, automated procurement workflows | | Professional Services | Resource allocation, time tracking, project profitability | Automated timesheets, skill-based scheduling, real-time financial dashboards | Exploring [industry-specific ERP modules](https://auboros.com/solutions/odoo) reveals how cloud platforms adapt to your sector’s unique demands rather than forcing generic workarounds. ## Key Cloud ERP Features Driving Operational Efficiency and Growth Cloud ERP’s value extends beyond industry fit. Core technological features deliver efficiency gains and scalability that transform how mid-market businesses operate. ![](/images/blog/cloud-erp-mid-market-australia-visibility-boost-7-1712dd3a.webp) **AI-Driven Automation:** Artificial intelligence embedded in modern cloud ERP systems improves [forecast accuracy by approximately 20% and reduces costs](https://www.astracanyon.com/blog/erp-2026-insights-future-of-erp-systems-market-trends-in-manufacturing) through smarter demand planning and inventory optimization. AI analyzes historical patterns, market signals, and seasonal trends to predict customer demand more accurately than manual methods. This reduces excess stock, minimizes stockouts, and improves cash flow. Automated invoice matching, expense approvals, and exception-based alerts free your team from repetitive tasks, letting them focus on strategic work. **Modular Architecture:** Cloud ERP systems with modular, composable architectures allow scale and customization without costly overhauls. You start with core financial management and add manufacturing, project accounting, or service management modules as your needs evolve. This approach avoids the all-or-nothing risk of traditional ERP deployments. You implement what you need now and expand functionality incrementally, spreading costs and reducing change management complexity. **Integration Capabilities:** Modern cloud ERP platforms connect seamlessly with manufacturing execution systems (MES), IoT sensors, CRM tools, and supply chain networks. Real-time data flows between systems eliminate manual data entry, reduce errors, and give you a complete operational picture. A manufacturing firm can link production floor sensors to ERP inventory modules, automatically updating stock levels as products move through assembly. A construction company can integrate project management software with ERP financials, ensuring every material purchase and labor hour updates project budgets instantly. **Pro Tip:** When evaluating modular ERP features, map each module to a specific operational pain point in your business. Don’t pay for functionality you won’t use. Focus on modules that directly address complexity in your workflows, whether that’s advanced manufacturing scheduling, multi-currency project accounting, or automated service dispatch. Understanding [AI-driven ERP automation](https://auboros.com/solutions/myob) helps you see how intelligent features translate into measurable productivity gains. ## Overcoming Challenges and Misconceptions in Cloud ERP Adoption Despite clear benefits, misconceptions about cloud ERP persist among mid-market leaders. Let’s address the most common myths and practical challenges. **Security Concerns:** Many believe cloud ERP is less secure than on-premise systems. The reality is different. Leading cloud ERP vendors invest heavily in security infrastructure, encryption, multi-factor authentication, and compliance certifications that exceed what most mid-market firms can afford to build internally. Your data sits in enterprise-grade data centers with redundant backups, disaster recovery protocols, and 24/7 monitoring. On-premise systems, by contrast, often rely on aging servers, inconsistent backup practices, and limited IT security expertise. **Customization Limits:** Some assume cloud ERP lacks the customization flexibility of on-premise solutions. Modern cloud platforms offer extensive configuration options, custom fields, workflow automation, and API access that let you tailor the system to your processes. Modular design means you’re not locked into a rigid structure. You can extend functionality through integrations, add-ons, and custom development when necessary. **Enterprise-Only Myth:** Cloud ERP isn’t just for large corporations. Mid-market businesses benefit even more because cloud models eliminate upfront capital costs, reduce IT overhead, and deliver enterprise-grade capabilities at subscription pricing. You gain access to sophisticated forecasting, analytics, and automation that were previously out of reach. **Practical Challenges:** Real adoption hurdles include change management resistance, integration complexity with legacy systems, and ensuring industry fit. Staff accustomed to spreadsheets and manual processes may resist new workflows. Legacy systems may lack APIs for smooth data migration. Generic ERP platforms may not address sector-specific needs. **Pro Tip:** Start change management early. Involve end users in ERP selection and design phases. Provide hands-on training before go-live and designate internal champions who can support peers during the transition. Partner with vendors who understand your industry and can navigate integration challenges effectively. Exploring [cloud ERP implementation challenges](https://auboros.com/blog/our-blog-5/erp-solutions-company-2026-4) prepares you to avoid common pitfalls and plan realistic timelines. ## Practical Benefits: Operational Improvements and ROI of Cloud ERP Quantifying cloud ERP benefits helps you build a business case and set realistic expectations. Mid-market Australian firms across manufacturing, construction, and professional services report measurable improvements after implementation. ![](/images/blog/cloud-erp-mid-market-australia-visibility-boost-7-a2b37d2c.webp) **Visibility and Reporting:** Cloud ERP adoption leads to 96% improvement in operational visibility and 30% reduction in reporting time. Unified dashboards replace manual report compilation, giving you instant access to inventory levels, project budgets, cash flow, and sales pipelines. You make decisions based on current data rather than week-old spreadsheets. **Cost Reduction:** [Cloud ERP can reduce operational costs by 20-30% through automation](https://neolysi.com/blog/?p=539). Automated invoice processing, purchase order approvals, and inventory replenishment eliminate manual tasks that consume hours each week. You reduce errors that lead to stockouts, billing disputes, or compliance penalties. Lower IT infrastructure costs, fewer manual reconciliations, and improved resource utilization compound savings over time. **Collaboration and Decision-Making:** Unified systems break down departmental silos. Sales teams see real-time inventory availability before quoting delivery dates. Project managers monitor budgets and resource allocation without chasing finance for updates. Manufacturing planners coordinate production schedules with procurement to avoid material shortages. Everyone works from the same data, reducing miscommunication and speeding response times. | Benefit Area | Typical Improvement | Impact on Mid-Market Operations | | --- | --- | --- | | Operational Visibility | 96% increase | Real-time dashboards replace manual reporting, enabling faster decisions | | Reporting Speed | 30% reduction | Automated data consolidation cuts time spent compiling weekly and monthly reports | | Operational Costs | 20-30% decrease | Automation, error reduction, and improved resource utilization lower expenses | | Forecast Accuracy | ~20% improvement | AI-driven demand planning reduces excess inventory and stockouts | Reviewing [operational benefits of cloud ERP](https://auboros.com/solutions/other-erp-services) shows how these improvements translate into competitive advantages for your business. ## Choosing and Scaling Cloud ERP for Mid-Market Australian Businesses Selecting the right cloud ERP requires careful evaluation of industry fit, scalability, and vendor expertise. Follow these steps to guide your decision. 1. **Define operational pain points clearly.** Document current workflow bottlenecks, data silos, and manual processes that slow your team. Rank them by impact on revenue, costs, or customer satisfaction. 2. **Prioritize industry-specific functionality.** Ensure the ERP platform offers modules tailored to manufacturing, construction, or professional services workflows. Generic systems force costly customizations. 3. **Evaluate modular architecture.** Choose platforms that let you implement core modules first and add functionality as your business grows. Avoid all-or-nothing deployments that overwhelm your team. 4. **Assess integration capabilities.** Verify the ERP connects with existing tools like CRM, e-commerce, supply chain systems, or industry-specific software. Look for robust APIs and pre-built connectors. 5. **Review vendor local expertise.** Partner with vendors who understand Australian business requirements, provide local support, and have proven experience in your sector. 6. **Plan for change management.** Budget time and resources for staff training, process documentation, and ongoing support. Successful implementations depend as much on people as technology. **Common Pitfalls to Avoid:** - Skipping stakeholder input during ERP selection, leading to systems that don’t fit actual workflows - Underestimating data migration complexity and cleansing requirements - Choosing the cheapest option without evaluating long-term scalability - Ignoring integration needs with existing systems and third-party tools - Failing to allocate sufficient training time for end users Exploring guidance on [selecting scalable cloud ERP](https://auboros.com/blog/our-work-4/choose-right-myob-acumatica-implementation-services-5) helps you build a selection framework aligned with your growth strategy. ## How Auboros Supports Your Cloud ERP Journey Transforming operations with cloud ERP requires more than software selection. You need a partner who understands mid-market complexities and delivers practical, scalable solutions. Auboros specializes in end-to-end ERP delivery for Australian businesses in manufacturing, construction, and professional services. We map your workflows, design systems that fit your reality, and support you through implementation, integration, and beyond. Our expertise with Odoo and MYOB Acumatica means you get platforms built for operational complexity, not generic solutions. Whether you’re replacing fragmented systems or scaling operations, we focus on building [ERP solutions](https://auboros.com) that work long term. From discovery and design through training and ongoing optimization, our hands-on approach ensures your ERP investment delivers measurable results. Explore our ERP services or learn how MYOB Acumatica solutions support mid-market growth. ## Frequently Asked Questions about Cloud ERP for Mid-Market Australian Businesses ### Will cloud ERP work for my mid-market manufacturing business? Yes, if you choose a platform with manufacturing-specific modules like production planning, quality management, and inventory traceability. Cloud ERP scales with your production complexity and integrates with MES and supply chain tools. ### How secure is cloud ERP compared to on-premise systems? Cloud ERP typically exceeds on-premise security through enterprise-grade encryption, multi-factor authentication, redundant backups, and 24/7 monitoring. Leading vendors maintain compliance certifications and invest in security infrastructure beyond what most mid-market firms can afford internally. ### Can cloud ERP be customized for complex operational workflows? Modern cloud ERP platforms offer extensive configuration, custom fields, workflow automation, and API access. You can tailor the system to your processes without the rigidity of older ERP models. Modular architecture supports incremental customization as needs evolve. ### What cost savings can I expect from cloud ERP? Mid-market businesses commonly achieve 20-30% operational cost reductions through automation, error elimination, and improved resource utilization. You also eliminate upfront hardware costs and reduce IT overhead, with subscription pricing spreading expenses over time. ### How do I choose the right ERP vendor in Australia? Prioritize vendors with proven experience in your industry, local support teams, and strong references from similar mid-market businesses. Evaluate their approach to change management, training, and post-implementation support. Learn more about choosing ERP vendors effectively. ## Recommended - [solutions/odoo | Auboros](https://auboros.com/solutions/odoo) - [Our Blog | Auboros](https://auboros.com/blog/our-blog-5) - [ERP Services for Sage, SAP Concur, NetSuite & More | Auboros](https://auboros.com/solutions/other-erp-services) --- # MYOB Acumatica for Member-Based Organisations in Australia - Canonical URL: https://www.auboros.com/blog/myob-acumatica-australia-7/myob-acumatica-for-membership-organisations-australia-92 - Category: MYOB Acumatica Australia - Published: 2026-03-08 - Description: How member-based organisations run memberships, renewals, finance and payroll on MYOB Acumatica (formerly MYOB Advanced), and what implementation involves. Member-based organisations run finances differently from most businesses. Revenue arrives in waves: membership renewals, event registrations, grants, sponsorships, publication sales. The people list is always changing. Reporting requirements vary depending on whether you're a charity, an incorporated association, or a national industry peak body. Most accounting software handles the books but nothing else. That's where MYOB Acumatica comes in. ## **What makes member-based organisations different from other businesses?** Financial complexity in membership organisations comes from multiple directions at once. Revenue streams are diverse and irregular. Expenses often need to be allocated across projects, cost centres, or funding programs. And the people you're managing are not the same as customers. Members have statuses, renewal dates, committee roles, varying fee structures, and a relationship with your organisation that goes beyond individual transactions. Standard business accounting software handles this badly. Xero, for example, works well for trading businesses but has no native concept of a member: their status, renewal cycle, or the link between their financial history and their membership record. You end up managing members in a spreadsheet or a separate CRM and reconciling manually. MYOB Acumatica is built for this level of operational and financial complexity. It's a cloud ERP designed for Australian organisations with at least 20 employees or equivalently complex financials. National associations, state-level peak bodies, professional institutes, large sporting clubs, and industry groups of that scale tend to find it fits well. ## **How MYOB Acumatica handles membership management** MYOB Acumatica handles the financial side of membership natively. For the member-facing layer (online renewals, self-service portals, event registrations), most organisations integrate it with a dedicated membership platform. If you'd prefer to keep everything with one vendor, we build custom membership portals directly within MYOB Acumatica. [Book a demo](/appointment) to see how that works. ### **Member and contact management in a single database** MYOB Acumatica's CRM capabilities let you maintain detailed records for each member: contact information, membership category, payment history, committee roles, communication preferences, and subscription status. Because this lives in the same system as your financials, you don't need to reconcile a membership database against your accounting system. A member's payment updates their record. Their renewal status reflects their actual financial position. ### **Renewals, subscriptions, and automated billing** Recurring invoices for membership renewals can be automated in MYOB Acumatica. You define the billing schedule, fee structure (individual, corporate, honorary, life member), and renewal cycle. The system generates and sends invoices without manual intervention. Overdue renewals trigger reminder workflows. Payment receipts update the member record automatically, with no double entry and no chasing up spreadsheets. ## **Financial management for associations and peak bodies** ### **Fund accounting, grants, and project tracking** Many membership organisations receive grant funding that must be tracked separately from operational revenue, with specific reporting requirements for acquittals. MYOB Acumatica handles this through sub-accounts and allocation templates, allowing you to report on each funding stream independently without running a separate system. Project accounting tracks expenditure and income against specific initiatives: a national conference, an industry research program, an advocacy campaign. You get a clear view of whether each project came in on budget. ### **GST, BAS, and ATO compliance for associations** Not all membership income is GST-free. The rules depend on your organisational structure and the nature of each supply. [The ATO's guidance on GST for not-for-profits](https://www.ato.gov.au/businesses-and-organisations/not-for-profit-organisations/your-organisation/gst-for-not-for-profits) sets out which supplies are taxable, which are input-taxed, and which are GST-free. The answer varies depending on whether your income comes from membership fees, events, publications, or grants. MYOB Acumatica handles mixed GST treatment across multiple revenue streams, and its [BAS (Business Activity Statement)](https://www.ato.gov.au/businesses-and-organisations/preparing-lodging-and-paying/business-activity-statements-bas) reporting is configured for Australian compliance requirements. For associations that employ staff, payroll is managed natively within the platform, including [Single Touch Payroll (STP)](https://www.ato.gov.au/businesses-and-organisations/hiring-and-paying-your-workers/single-touch-payroll) reporting to the ATO and the current superannuation guarantee rate. ## **Payroll and workforce management for membership organisations** MYOB Acumatica is the only platform in its category that combines ERP, payroll, and workforce management in a single system. For associations with staff, particularly those with complex rostering such as event teams, part-time administrative staff, or mixed permanent and casual workforces, this removes the need for a separate HR or payroll platform. Staff timesheets flow into payroll calculations. Payroll is reported to the ATO through STP automatically. Leave balances, roster planning, and compliance with relevant modern awards are all managed in the same place where your financial reporting happens. It's a meaningful simplification for organisations that have historically patched together multiple systems to cover these functions. ## **Connecting MYOB Acumatica with membership software** For organisations that need a member-facing portal (online renewals, event registrations, committee elections, member directories), [MemberConnex](https://www.myob.com/au/apps/memberconnex) is the most widely used integration in the Australian market. It's specifically built to connect with MYOB products and currently manages more than one million people across 250,000 entities in Australia and New Zealand. The integration works in both directions. A member renewing online through MemberConnex creates a transaction that flows directly into MYOB Acumatica, with no manual import or reconciliation required. Administrators have a full picture of financial and membership status in one place. Members get a self-service experience on any device. ## **Is MYOB Acumatica right for your member-based organisation?** It depends on size and complexity. MYOB Acumatica is designed for organisations with at least 20 employees or an equivalent level of financial and operational complexity. Smaller associations often do well with simpler, lower-cost tools and a basic membership plugin. The organisations that tend to get the most out of MYOB Acumatica are: - **National or state-level associations** with multiple revenue streams, grant funding, and compliance reporting obligations across different jurisdictions - **Professional institutes** with tiered membership structures, CPD tracking needs, and publication or event revenue - **Industry peak bodies** managing grants, advocacy projects, research programs, and government funding acquittals - **Large sporting or recreation bodies** with significant event operations, casual workforce management, and club-level financial reporting If you're running a smaller organisation and struggling with your current setup, our team can help you understand what mid-market ERP would realistically cost and whether the efficiency gains are worth it. Our [MYOB Acumatica implementation services](/solutions/myob) page covers what we do and how we work. ## **Frequently asked questions** ### **Can MYOB Acumatica manage membership renewals automatically?** Yes. MYOB Acumatica supports recurring invoice automation and can trigger renewal workflows based on membership cycle dates. For a more complete member-facing portal with online renewals and self-service access, most organisations pair it with MemberConnex, which is purpose-built for the Australian membership sector. ### **What's the difference between MYOB Acumatica and MYOB Business for a membership body?** MYOB Business (formerly AccountRight) is designed for small businesses with straightforward accounting needs. MYOB Acumatica is a full cloud ERP with multi-entity support, project accounting, fund tracking, grant management, and integrated workforce management. For a membership organisation with more than 20 staff or complex financials, Acumatica is the appropriate product. Note that MYOB rebranded MYOB Advanced to MYOB Acumatica in 2024. It's the same platform with the same underlying capabilities. ### **How much does MYOB Acumatica cost for a member-based organisation?** MYOB Acumatica is priced on a subscription model that varies depending on the modules activated, number of users, and complexity of your operations. Rather than provide a number that may not reflect your situation, we'd recommend a consultation to get a realistic estimate. Implementation is a separate cost from the ongoing subscription, and scoping that properly upfront avoids surprises. ### **Does MYOB Acumatica work for not-for-profit organisations?** Yes. Many NFPs and charities across Australia run on MYOB Acumatica. The platform handles fund accounting, grant management, and the mixed GST treatment common in the NFP sector. MYOB publishes specific guidance for [non-profit management](https://www.myob.com/au/erp-software/industries/non-profit-management) that's worth reviewing if that's your context. * * * **Running a membership organisation on software that's showing its age?** We're a Queensland-based [MYOB Acumatica partner](/solutions/myob) with experience implementing ERP for organisations with complex, multi-stream financials. If you're evaluating whether MYOB Acumatica fits your association, peak body, or membership group, [**book a free consultation**](/appointment) and we'll give you a realistic picture of what's involved. --- # What to Look for in an ERP Solutions Company in 2026 - Canonical URL: https://www.auboros.com/blog/insights-5/erp-solutions-company-2026-4 - Category: Insights - Published: 2026-02-17 - Description: Learn how to choose the right ERP solutions company in 2026, including key features, industry expertise, scalability, and long-term support considerations. Enterprise Resource Planning systems continue to play a central role in how organisations manage operations, data, and decision-making. As businesses move into 2026, expectations around ERP platforms and the companies that deliver them are evolving rapidly.  When evaluating an ERP solutions company, it is no longer enough to consider software features alone. Businesses must assess long-term adaptability, integration capabilities, data governance, and vendor expertise in an increasingly digital and regulated environment.  Organisations exploring ERP options often begin by researching providers that offer structured information about their services, implementation approach, and supported platforms. [**Auboros**](/) present a clear overview of ERP-related services and supported systems, helping decision-makers understand how different ERP solutions align with operational needs. Providers such as Auboros offer structured overviews of their ERP services and supported platforms, helping decision-makers assess alignment with their operational needs.  This article outlines what to look for in an ERP solutions company in 2026, focusing on practical, non-promotional criteria that support informed decision-making.  ## **The Changing Role of ERP Systems in 2026**  ERP platforms are no longer limited to back-office functions such as accounting, inventory management, and procurement. Modern ERP systems increasingly support:  - Real-time reporting and analytics  - Integration with cloud services and third-party tools  - Compliance with regional and international regulations  - Scalability across locations and business units  As a result, the ERP solutions company responsible for implementing and supporting these systems becomes a long-term technology partner rather than a one-time vendor.  ## **Understanding What an ERP Solutions Company Does**  An ERP solutions company typically provides services that include:  - ERP software selection and consultation  - System configuration and customisation  - Data migration and system integration  - User training and documentation  - Ongoing support and optimisation  In 2026, businesses should expect these services to extend beyond initial deployment, with a strong emphasis on system longevity, adaptability, and performance monitoring.  ## **Key Factors to Consider When Choosing an ERP Solutions Company**  ### **Industry and Operational Understanding**  An effective ERP solutions company should demonstrate an understanding of the operational realities of different industries. ERP requirements vary significantly between sectors such as manufacturing, retail, professional services, and distribution.  Rather than offering a one-size-fits-all approach, a capable provider assesses business workflows and maps ERP functionality accordingly. This reduces unnecessary customisation and improves system adoption.  ### **Platform Expertise and ERP Ecosystem Knowledge**  ERP platforms continue to diversify, with businesses choosing systems based on size, complexity, and regional requirements. In 2026, companies often look for ERP solutions companies that support multiple platforms rather than focusing on a single product.  For example, some organisations may require flexibility across platforms such as Odoo or MYOB Acumatica, while others may need specialised ERP services. Providers that outline their platform expertise transparently, such as through dedicated pages for [**Odoo ERP solutions**](/solutions/odoo) or [**MYOB Acumatica**](/solutions/myob), allow businesses to assess suitability more easily.  ### **Scalability and Future Readiness**  ERP implementations should support growth, not restrict it. An ERP solutions company must consider how the system will perform as the organisation expands in terms of:  - Transaction volume  - Number of users  - Business units or locations  - Regulatory requirements  Scalability planning should be built into the initial design, ensuring the ERP system remains functional and cost-effective over time.  ### **Integration Capabilities**  Modern businesses rely on multiple digital tools, including CRM systems, e-commerce platforms, payroll software, and data analytics tools. An ERP solutions company should have experience integrating ERP platforms with third-party applications.  In 2026, integration is less about technical feasibility and more about maintaining data consistency, security, and performance across systems.  ### **Data Security and Compliance Awareness**  With stricter data protection regulations and increased cybersecurity risks, ERP systems must support secure data handling. An ERP solutions company should demonstrate knowledge of:  - Data access controls  - Audit trails and reporting  - Regional compliance requirements  - Backup and disaster recovery processes  Security considerations should be discussed early in the ERP selection and implementation process.  ## **Cloud-Based ERP and Deployment Models**  ### **Cloud, On-Premise, or Hybrid Approaches**  By 2026, cloud-based ERP systems are widely adopted, but on-premises and hybrid models still exist for specific use cases. An ERP solutions company should provide objective guidance on deployment models based on business needs rather than promoting a single approach.  Key considerations include:  - Data residency requirements  - Internet reliability  - Internal IT resources  - Long-term cost implications  ### **Performance and System Reliability**  Cloud ERP systems rely on stable infrastructure and performance monitoring. An ERP solutions company should outline how system performance is measured, maintained, and optimised over time.  ## **Implementation Methodology and Project Management**  ### **Structured Implementation Approach**  ERP projects involve multiple stakeholders, data sources, and operational processes. A structured implementation methodology reduces risks such as delays, cost overruns, and system misalignment.  A reliable ERP solutions company should clearly define phases such as:  - Discovery and requirement analysis  - System configuration  - Data migration  - User acceptance testing  - Go-live and post-launch review  ### **Communication and Stakeholder Involvement**  ERP implementations affect multiple departments. Clear communication, documentation, and stakeholder engagement are essential for adoption and long-term success.  ## **Training and User Enablement**  ### **Practical Training Programmes**  ERP systems are only effective if users understand how to work with them. An ERP solutions company should provide training that aligns with actual job roles rather than generic system overviews.  Training formats may include:  - Role-based workshops  - Documentation and user guides  - Ongoing knowledge transfer  ### **Change Management Support**  ERP adoption often involves changes to existing processes. Companies that acknowledge and plan for change management tend to achieve higher user engagement and system value.  ## **Ongoing Support and System Optimisation**  ### **Post-Implementation Support**  ERP systems require ongoing maintenance, updates, and refinements. An ERP solutions company should offer structured support options that include:  - Issue resolution  - System updates  - Performance reviews  Providers offering broader ERP support services, such as those outlined under [o**ther ERP services**](/solutions/other-erp-services), demonstrate an understanding that ERP systems evolve alongside businesses.  ### **Continuous Improvement**  In 2026, ERP systems are expected to adapt to new regulations, technologies, and operational changes. A long-term partnership with an ERP solutions company should include periodic system reviews and optimisation opportunities.  ## **Evaluating Transparency and Communication**  Transparency is an often-overlooked factor when selecting an ERP solutions company. Businesses should assess how clearly providers communicate about:  - Project scope and limitations  - Costs and timelines  - Risks and assumptions  Clear communication reduces misunderstandings and helps establish realistic expectations.  ### **Local and Regional Knowledge**  ERP implementations are influenced by local regulations, tax structures, and business practices. An ERP solutions company with regional experience can better align systems with local requirements while maintaining global standards.  ## **When to Engage an ERP Solutions Company**  Organisations may consider engaging an ERP solutions company when:  - Existing systems no longer support growth  - Manual processes limit efficiency  - Data visibility is fragmented  - Compliance requirements increase  Early consultation allows businesses to plan ERP adoption strategically rather than reactively.  ## **Making an Informed Decision**  Selecting an ERP solutions company in 2026 requires a balanced evaluation of technical expertise, industry knowledge, and long-term support capabilities. Decision-makers should prioritise clarity, adaptability, and alignment with business goals over short-term features.  For organisations seeking further information or professional consultation, contact details are typically available through provider websites [**contact page**](/contactus), allowing businesses to initiate informed discussions.  ## **Frequently Asked Questions**  What is an ERP solutions company?  An ERP solutions company helps businesses streamline their operations, improve visibility across departments, and get more value from their systems and data. This typically includes consulting, software selection, implementation, integration, and ongoing support to ensure the ERP system continues to align with business goals as the organisation grows.  Why is choosing the right ERP solutions company important?  The ERP solutions company plays a critical role in how effectively an ERP system supports business operations. The right provider helps reduce implementation risks and ensures long-term system value.  Should an ERP solutions company support multiple ERP platforms?  Supporting multiple platforms allows an ERP solutions company to recommend systems based on business needs rather than platform limitations. This flexibility is increasingly important in 2026.  How long does an ERP implementation usually take?  ERP implementation timelines vary depending on system complexity, business size, and data requirements. A structured approach and clear communication help manage expectations.  What should be included in ERP support services?  ERP support services typically include system maintenance, troubleshooting, updates, and performance optimisation. Ongoing support ensures the ERP system remains aligned with business needs. --- # Case Study: Circulis Runs Reverse Vending and Recycling on Odoo - Canonical URL: https://www.auboros.com/blog/our-work-4/circulis-2 - Category: Case Studies - Published: 2025-06-15 - Description: How Auboros built Circulis an end-to-end Odoo platform: reverse vending machine fleet, field service, international supply chain and financials in one system. ### From R&D Concept to Nationwide Commercial Rollout, Powered by Odoo Circulis is a forward-thinking green technology company on a mission to build a cleaner, more sustainable future. By designing and deploying innovative Reverse Vending Machines (RVMs), they are revolutionizing how recyclable containers are collected. After four years of intensive R&D, Circulis was ready to move from concept to commercialisation, but faced a significant operational roadblock: they had no integrated system to manage their complex, multi-faceted business model. ### The Challenge: A Complex Business with No Central System Transitioning from R&D to a full-scale commercial operation revealed major gaps in their infrastructure. The team was relying on a combination of Xero and spreadsheets to manage what was quickly becoming a highly complex international supply chain and a local service network. Their core challenges included: - **Fragmented Operations:** With no central system, every step, from purchasing machines in China to managing service contracts with Australian shopping centres and schools, was handled in a silo. - **Lack of Visibility:** They had no way to track the entire lifecycle of their machines, from procurement and landed costs to assembly, distribution, maintenance, and asset depreciation. - **Manual Processes:** A heavy reliance on spreadsheets created a high risk of data errors, wasted time on double-entry, and offered no scalability for their planned growth. - **Complex Service Management:** Their model required robust fleet management, field service scheduling for maintenance, and detailed tracking of user recycling activity across numerous sites. Circulis needed a single source of truth: a powerful, unified platform that could manage their entire business, from international purchasing to local field service, all in one place. ### The Solution: An End-to-End Business Platform Built by Auboros Understanding the unique complexity and scale of Circulis's vision, Auboros proposed and implemented a comprehensive Odoo solution. The goal was to build a robust, scalable foundation that would not just solve their immediate challenges but support their long-term growth. The implementation was rolled out progressively, starting with the most critical functions to ensure a smooth transition. Auboros deployed an extensive suite of Odoo 17 apps to create a fully integrated business management system: - **Supply Chain & Operations:** **Purchase, Inventory, Manufacturing, and Accounting** modules were configured to manage the entire process of importing machines. This gave Circulis full visibility into landed costs, including freight and duties, while the **MRP, Maintenance, and Quality** modules ensured every machine was assembled and maintained to the highest standard. - **Distribution & Service Delivery:** The **Fleet, Field Service, and Project** modules provided the tools to manage machine distribution, on-site installations, and contract rollouts. The **Helpdesk** module created a streamlined process for managing customer support and service inquiries. - **Commercial & Financial Management:** **CRM, Sales, Invoicing, and Accounting** modules were integrated to manage everything from new leads and contracts with sites to automatically generating invoices for third parties based on sales data collected directly from the machines. The **Rental and Subscriptions** modules were used to manage lease agreements and track assets effectively. - **Administration & Documentation:** The **Documents, E-Sign, and Timesheet** modules were implemented to digitise paperwork, streamline contract signing, and accurately track project time. ### The Results: A Seamless, Scalable Operation By partnering with Auboros, Circulis transformed its operations from a collection of manual spreadsheets into a single, automated, and intelligent platform. - **Complete Visibility:** Circulis now has a 360-degree view of their entire business in real-time, from inventory levels of spare parts to the maintenance schedule of a specific machine in the field. - **End-to-End Automation:** The integrated Odoo system eliminated manual data entry, reducing errors and freeing up the team to focus on strategic growth. Processes like invoicing based on machine data are now fully automated. - **A Scalable Foundation for Growth:** With a robust Odoo infrastructure, Circulis has the confidence to scale its operations, sign new contracts, and expand its network of RVMs across the country without being limited by technology. - **Data-Driven Decision Making:** With all their data in one place, from user recycling habits in the CRM to operational costs in the Accounting module, the Circulis team can now make smarter, faster business decisions. > "Moving from R&D to full commercialisation was a massive step. We had the vision, but we lacked the operational backbone. Auboros didn't just implement a piece of software; they built the integrated system our entire business now runs on. With Odoo, we have full control over our supply chain, service delivery, and financials in one place. We couldn't have made this transition so successfully without them." > > **Carl Cunanan, Circulis Pty Ltd** **At a Glance**

Client

Circulis Pty Ltd

Industry

Green Technology & Recycling

The Challenge

Transitioning from an R&D phase to full commercialisation with no integrated systems to manage a complex business model involving international procurement, local assembly, distribution, and field service.

The Solution

A comprehensive, progressive implementation of Odoo 17 to create a single, unified platform for all business operations.

Key Modules

Purchase, Inventory, MRP, Maintenance, Fleet, Field Service, CRM, Sales, Invoicing, Accounting, Project, and Custom Module for RVMs.