Case Study: How a Melbourne Construction Company Stopped Pestering the Bookkeeper About Invoice Status

A Real Scenario You Probably Recognise

A Melbourne construction company that does commercial fit-outs and renovations. About 25 people: 4 project managers, 6 site supervisors, an admin, one bookkeeper, and the owner. Before we got involved, this happened every day:

Project Manager A (on site) messages the bookkeeper:

"Has the progress claim 1 invoice for ABC Property been paid yet? I'm about to talk to the client about the next stage."

The bookkeeper opens MYOB AccountRight, finds ABC Property, scrolls through the sales register to invoice INV-2025-…, checks the status, screenshots it, sends it back. That round trip takes 10–20 minutes.

Site Supervisor B emails the bookkeeper:

"Did we pay subcontractor C for last week's invoice? He's threatening to walk off site."

Same drill: log into MYOB, find the supplier, check the purchase register, confirm paid/unpaid, reply.

Across a week, the bookkeeper was losing roughly 8–12 hours just answering ad-hoc internal queries — about 1.5 working days per week, gone, before getting anywhere near reconciliation, BAS, or month-end.

And the project managers weren't happy either: the client was waiting on site for an answer, and the PM was waiting on a Slack reply from the office. Everyone was waiting on someone else.

Why This Happens (When the Data Is Already in MYOB)

In about 90% of construction SMBs we've worked with, MYOB or Xero is the accounting tool — and only the bookkeeper and the owner have logins. That's a perfectly reasonable setup:

• MYOB AccountRight per-seat licensing is $130+/month per user — adding 5–10 frontline seats costs real money
• Frontline staff don't need (or want) to see payroll, profit, bank reconciliations
• Accounting UIs are built for accountants, not site supervisors

But the cost is real: financial data ends up locked in a box only the bookkeeper can open, so anyone who needs that data has to go through her. Waiting, interrupting, context-switching — all three sides lose.

What We Built: A Read-Mostly MYOB Window Inside Their ERP

This client already had an internal project management system we'd built for them earlier — projects, customers, subcontractors, quotes, all tracked there. We added a MYOB data layer on top:

1. Sync — read mostly, write minimally

• Every 30 minutes: pull sales invoices, purchase invoices, payments, customer/supplier balances from MYOB
• Write only on specific triggers: when a new project is signed in the ERP, auto-create the matching customer record in MYOB (so the bookkeeper doesn't double-enter)
• Event-triggered real-time sync: when an invoice is issued or a payment recorded, push immediately

2. A "Finance" tab inside every project view

Open any project in the ERP. There's a new tab on the right: Finance. It shows:

• Every progress claim invoice for this project (issued, paid, outstanding)
• Every subcontractor invoice tied to this project (paid/unpaid, payment date)
• Cumulative retentions (the 10% withhold)
• Live project margin: contract value − paid subcontractor costs − direct costs, calculated in real time

3. Permissions match the ERP, not MYOB

• Project managers: see finance data only for their assigned projects
• Site supervisors: see subcontractor payment status for their sites
• Bookkeeper + owner: full access
• Nobody non-finance sees payroll, bank accounts, or tax data

4. Answers in five seconds, not five hours

A project manager opens the ERP on their phone from a job site. Within 5 seconds they know:

• "Did ABC Property pay last week's invoice?" → Status: Paid, on 2026-04-23
• "Did we pay subcontractor C?" → Status: Paid + payment date
• "What's still outstanding on this project?" → Live AR figure
• "What margin are we tracking on this job?" → Live percentage

What Changed After Go-Live

Bookkeeper: time spent answering interrupting queries dropped from 8–12 hours per week to roughly zero. Her own description: *"I can finally do month-end without being interrupted five times a morning."*

Project managers: they stopped saying "let me check with the office" in front of clients. Faster decisions, more confident conversations.

Owner: opens the ERP, sees live margins on the five active projects without waiting for a month-end report. Spots a project trending toward loss before it actually loses — and that early-warning capability is real money.

Bookkeeper retention also got better. A bookkeeper whose week is mostly being interrupted is a bookkeeper who eventually leaves. Freeing her up to do work she actually trained for makes the role sustainable.

The Technical Build (Skip If You're Not the Curious Type)

For readers who want the under-the-hood version:

• Auth: MYOB AccountRight via OAuth 2.0 (this client is on cloud, not the legacy desktop edition)
• Sync cadence: 30-minute incremental pulls + event-triggered real-time syncs on key actions
• Rate limits: MYOB's API has per-minute caps; we run a queue with exponential backoff so a busy hour doesn't break sync
• Data caching: MYOB data lands in the ERP's own Postgres database. We don't hit MYOB's API on every page view — we'd kill the rate limit and the page would feel slow. A `last_synced_at` timestamp is shown to the user so they know how fresh the data is.
• Permissions: the ERP user's existing project-level access drives what MYOB data they can see (row-level security at the database layer)

If your bookkeeper uses MYOB Business (not AccountRight), the API is a different one (newer, OData-based). We've built integrations for both editions.

Who Else Should Care

Based on what we've seen, the same pattern works wherever:

• Construction / fit-out / trades — project manager × site supervisor × bookkeeper triangle (this case study)
• Wholesale & distribution — sales reps want to see customer AR status; warehouse wants to confirm payment before releasing stock
• Professional services (consulting, design, legal) — matter leads want to see what's outstanding for a client before continuing work
• Multi-location retail — store managers see receipt/payment status for their store without bothering head office finance

The shared pattern: financial data is queried daily by frontline staff, but they shouldn't (and don't need to) have direct accounting software access.

Why Not Just Buy More MYOB Seats?

You could. It usually doesn't work in practice:

1. Licensing cost. MYOB AccountRight Premier is ~$130/month per user. Five to ten frontline seats add up fast.
2. Permission granularity is too coarse. MYOB's role model is built for finance roles — there's no clean way to say "show me invoices on my projects but hide payroll and bank balances".
3. Training cost. A site supervisor doesn't want to learn an accounting system. They want a finance tab inside the system they already use.
4. Audit / offboarding. Every extra MYOB user is a credential to manage when someone leaves.

A custom integration is usually cheaper than the licence + training + risk costs of widening MYOB access. One-off integration spend, recurring licence savings.

Summary + What to Do Next

This case isn't really about MYOB. It's about the wall between operational systems and financial systems — a wall most Melbourne SMBs have. Knocking it down has outsized payoff: bookkeeper unblocked, frontline decisions faster, owner sees real margins live.

If your business has any of these signs:

• Frontline team pings finance multiple times per week with the same kinds of question ("has this been paid?", "what do they owe us?")
• The bookkeeper can't focus on month-end without being interrupted
• The owner only finds out a project lost money at month-end

…you probably need this kind of integration. We've built MYOB AccountRight, MYOB Business, Xero, and QuickBooks integrations into client CRMs, ERPs, and project management systems.

[Book a free consultation](/#contact) — tell us your accounting tool + your internal system, and we'll scope the integration: what to sync, how long it takes, what it costs.

Related reading:

• Custom Project Tracking for Melbourne Builders — the operational system that hosts these integrations
• Workflow Automation Service — how we approach connecting business tools end-to-end
• Custom vs Off-the-Shelf Software for Melbourne SMBs — the decision framework for build vs buy