Skip to content
ERP integration · Australia

ERP integration service: your ERP connected to one other system for a fixed scope

A written scope, a tested link, and a log that shows what moved.

When the same data is typed twice, or order and stock numbers do not match between systems, a connection between your ERP and one other system can help. True North Innovations is a Melbourne-based team working with businesses across Australia. We connect two systems, one pair per job, through their official interfaces. The ready-made app is often the right start; this page is for when it is not enough. Other connection jobs: API integration and system integration; whole processes with approvals are workflow automation.

Written scope · Official interfaces · Test cases · Log and alerts

Melbourne based.
Australia-wide delivery.

Melbourne · Sydney · Brisbane · Perth · Adelaide · Canberra

When it fits

When the ready-made app is not enough

01

The app does not carry your fields

A ready-made connector moves standard fields. Your own fields, rules or statuses are left out.

02

The direction or timing is wrong

You need data one way only, or on a set time, or only when a state changes.

03

Failures are invisible

When a record fails to move, nobody is told, and the two systems drift apart.

04

Your pair has no app

The other system is a custom tool, or a less common one.

If a ready-made app covers your case, we will say so.

Pairs

Pairs we connect

One ERP and one other system per job. Typical pairs, to be checked system by system:

01

ERP and website shop

Orders, stock levels and customers between the shop and the ERP.

02

ERP and CRM

Customers, quotes and orders kept the same in both.

03

ERP and a reporting or booking tool

Figures or jobs passed on a set time.

We check each system's interface, permissions and limits before we promise a connection.

Scope

How we scope

Fields
What is written downExactly which fields move, and what each is called on each side.
Direction
What is written downOne way or both ways, and which system wins in a clash.
Timing
What is written downWhen it runs: at once, on a schedule or on a trigger.
Failure cases
What is written downWhat happens when a record is missing, wrong or rejected.
Access
What is written downWhich keys or admin rights are needed and who holds them.

You approve the written scope before we build.

How the work runs

Scope, build, test, hand over

  1. 01

    Scope

    We read both systems and write the scope.

    Output: The written scope

  2. 02

    Build

    We build the link on the systems' official interfaces, on a test account where possible.

    Output: A working link

  3. 03

    Test

    We run at least 10 test cases, including failures, and a person signs off the results.

    Output: A test record

  4. 04

    Log and alerts

    We add a log of what moved and an alert for failures.

    Output: A log and alerts

  5. 05

    Hand over

    We write a short note for the next person. Support runs for 30 days.

    Output: A hand-over note

What we need from you

What you give us to start

  • Interface keys or admin access to both systems.
  • A test account where the system allows one.
  • A list of the fields and rules that matter, with a few real examples.
  • The person who can say which system is right when the two disagree.
  • The person who will sign off the test cases.
Scope

What is not included

01

Accounting advice

We connect the systems; we do not advise on your accounts.

02

System fees

Licences and interface fees are paid by you to each maker.

03

Unlimited changes

The written scope is the job. New fields or systems are a new scope.

Scope

What affects the scope

01

Number of fields and records

More fields and more kinds of record mean more rules and tests.

02

One way or both ways

Two-way links need clash rules and more tests.

03

Quality of the interface

Some systems have a full interface, some a thin one.

04

Your data

Messy data has to be cleaned before it can move.

A written scope is agreed before we start.

Common questions

ERP integration: good to know

What is an ERP integration?

It is a link that keeps data the same between your ERP and one other system, so it is not typed twice.

When is a ready-made app enough?

When it carries your fields, direction and timing, and tells you about failures. If it does, we say so.

How is this different from API integration?

The method is the same. This page is for ERP pairs; API integration is for other pairs.

How many systems do you connect per job?

Two: your ERP and one other. A third system is a new scope.

What are the test cases?

At least 10 written cases, including failures such as a missing record or a rejected one, with the result of each.

What do I see when something fails?

A log shows what moved, and an alert tells a named person about a failure.

Do you need access to my ERP?

Interface keys or admin access to both systems, and a test account where the system allows one.

How long does it take?

Usually 2 to 3 weeks once access is in place.

Who signs off the work?

A person at True North signs off the test cases, and you approve the written scope.

What support is included?

30 days of support after hand-over.

Do you advise on accounting?

No. We connect systems and leave accounting decisions to you and your accountant.

Explore more

Related services

API integration →

Two systems connected through their official interfaces.

System integration →

Two business systems that share data in a written way.

Workflow and business process automation →

Whole processes that cross several systems and people.

Custom CRM development →

A system to hold your customer and job records.

See all services

Tell us about your business

Tell us about the two systems

Tell us which two systems and what should move between them. We reply with questions and a scope.

Call 03 4158 4444info@truenorthinnovations.com.au

Every job is scoped before work starts.

We use your details to respond to your enquiry. Read our Privacy Policy.