LEAP + MYOB integration
LEAP and MYOB integration that finally reconciles trust.
We build the middleware that makes LEAP and MYOB agree on the trust ledger. Melbourne law firms hand-key trust transfers between matter management and the general ledger every month, and a partner notices three months later that two of them never landed in MYOB. The database-first move stops the gap by reconciling LEAP, the bank feed and MYOB on a nightly schedule, so a missing transfer surfaces the next morning rather than at the audit.
Where LEAP and MYOB break the join
LEAP holds the matter spine: matter records, trust accounting at matter level, time entries, conflict checks and the partner-facing WIP view. MYOB holds the firm-side ledger: the chart of accounts, payables, payroll, BAS, end-of-month reporting. The join points are specific, and each one has a recognisable failure mode at production volume.
Trust receipts
The day-one entry never lands
Trust transfers
Transfer-from-trust as the silent gap
Time entry to invoice
The reshape between systems
End-of-month GL reconciliation
Where the practice manager loses Sunday
How we approach LEAP-MYOB integration
Discovery before anything else
We map where each piece of trust and ledger data lives today, who edits it, and what "right" actually means. Which LEAP fields drive the MYOB journal, which staff member is the silent reconciler, where the workaround spreadsheet sits that the official systems never caught. That conversation is where the real data model comes from, not from reading the LEAP or MYOB API docs in isolation.
Model the matter-to-ledger join, not the API
The database-first move. Before we build anything, we write down the contract between a matter, a trust receipt, a trust transfer, a bank entry and a general ledger posting. Integration then becomes a question of reading from LEAP and MYOB, not negotiating between them after the fact. Reconcile at rest, in one place, not in the air between two APIs at three in the morning.
Reconciliation as a contract
Three-way reconciliation runs on a nightly schedule. The LEAP trust ledger is compared to the bank feed and to MYOB's general ledger. Any discrepancy surfaces to the practice manager the same morning, with the matter, the transfer, the date and the variance. Retries, idempotency and dead-letter handling are written down before the first line of integration code. If a record disappears, somebody finds out on day one, not at the next quarterly audit.
Middleware that handles vendor failures
LEAP and MYOB each misbehave in specific ways. Rate limits, auth-token refresh quirks, silent payload changes, bank-feed lag of a day or two. We build the integration on real infrastructure with queues, monitoring and alerts, so a throttled API or an expired token raises a hand rather than quietly dropping a transfer. A failed transfer surfaces on the morning queue the night it happens, with the matter and the amount attached, so the practice manager fixes it before the client ever notices it went missing.
AI-ready as a side-effect
The reconciliation layer we just described is also the substrate an AI agent would need to act on the firm safely later. One canonical record per matter, audit trail by default, permissions modelled in the database, the agent reading from the source of truth rather than reconciling LEAP and MYOB each time it acts. We do not bolt agents on in this engagement, but the work leaves the firm with the substrate ready when the AI question lands.
We have done this since 2007. See who we are.
What this typically looks like in practice
A Melbourne law firm we worked with was running LEAP for matter management and MYOB for the general ledger. Trust transfers between the two systems were hand-keyed each month. The reconciliation against the bank feed lagged by weeks because the practice manager had no time to chase the small variances during BAS season. The pattern that triggered the call: a partner noticed at the annual audit that two transfers from a quarter earlier had been recorded in LEAP but never posted to MYOB. The reconciliation belonged to one practice manager who had run out of hours for it. The small variances were the ones that fell through.
Every night, a middleware layer compares the LEAP trust ledger, the bank feed and the MYOB general ledger against each other. Where the three disagree on a transfer, the practice manager gets the matter, the transfer and the amount on screen the next morning instead of finding it at the audit. The fix sat alongside LEAP and MYOB rather than replacing either. Trust reconciliation moved from end-of-month firefighting to a nightly check.
Trust reconciliation moved from end-of-month firefighting to a nightly check. The practice manager stopped working Sundays.
From the LEAP-MYOB reconciliation case study
Pattern story, anonymised. No named client, dates or dollar amounts. We will publish a named case study once a Melbourne law firm engagement has consented.
Common questions about LEAP and MYOB integration
Why not use the native LEAP-MYOB connector if there is one?
Use it if it covers your work. For a firm with a clean chart of accounts, standard billing schedules and no bespoke GL coding rules, the native connector or the off-the-shelf option is the cheapest correct answer. We build middleware when the native option misses fields, loses transfers under load, cannot model custom trust handling, or does not honour the disbursement and write-off rules a partner committee actually agreed to. The diagnostic looks at what LEAP and MYOB already ship together before we quote anything new.
How does trust reconciliation actually work after integration?
Three-way. The LEAP trust ledger holds the matter-level record. The bank feed shows what cleared the trust account. The MYOB general ledger shows what was posted on the firm side. The middleware compares all three on a nightly schedule and surfaces any discrepancy to the practice manager the same morning. A trust receipt that landed in LEAP but never made it to MYOB is flagged on day one, not at the audit three months later. The Legal Profession Uniform Law audit sign-off stays the partner's responsibility; the database removes the evidence-hunt that used to eat the week before it.
What if our firm is moving from MYOB to Xero?
The integration shape is the same. Trust ledger reconciles to bank feed reconciles to the general ledger, regardless of which accounting system holds the GL. We have built this pattern with both MYOB and Xero on the accounting side. The vendor-specific code sits in one layer, so a migration becomes a question of rewriting that layer rather than rebuilding the whole integration. If you are mid-migration, we usually run both feeds in parallel for a month so the audit trail does not lose a record on the cutover.
How long does a LEAP-MYOB integration build take?
Most builds we ship land in the six to eight week middle. The full range runs four to twelve, and where you sit inside it depends almost entirely on how much hand-keyed trust history has to be reconciled before the nightly job can run cleanly. A firm with sensible accounts and conventional join points lands near four. A firm that has been hand-keying trust transfers for years lands near twelve, because the back-history is the real work. The diagnostic prices that cleanup honestly before you commit.
What about Legal Profession Uniform Law audit obligations?
The LPUL trust handling rules and Victorian Legal Services Board audit requirements stay the partner's responsibility. We build the database underneath to make the evidence trail straightforward: every trust receipt, transfer and write-off has a timestamped record, the user who made it, and the reconciliation result against both the bank feed and MYOB. When the external auditor arrives, the answer to "show me the supporting record for this transfer" is one query, not a week of paper. We do not sign off on compliance; we make the compliance week stop being a write-off.
Does this set us up for AI agents on top later?
Yes, and increasingly that is why firms ask before the AI conversation rather than after. The integration is the foundation: a database the firm controls, one canonical record per matter, audit trail by default, permissions modelled in the data layer. Without that substrate, an agent has nothing to act on except whatever LEAP and MYOB each expose that week, and no record of what it did. We do not build the agents in this engagement, but the work leaves you with the data shape that makes adding them later a scoping question, not a foundation question.
Not sure if your firm needs middleware or a sharper LEAP rollout?
Start with a conversation. We will look at how LEAP and MYOB talk today and tell you honestly which fix earns its keep: nightly three-way reconciliation if the trust transfers are draining the practice manager's week, a sharper LEAP rollout if the matter-level data is where the partner committee keeps re-litigating the same write-offs, or something smaller again.