Start With the Business Question, Not the Software
Before any system work begins, decide what the business needs to improve. In many Centurion and Johannesburg firms, the real issue is not the software itself but the gaps between finance, sales, stock control and payroll. If invoices are raised in one place and payments are captured in another, someone must reconcile the difference every week. That takes time and often leads to mistakes.
Ask a few direct questions first. What process is causing the most rework? Which team enters the same data more than once? Which reports are trusted and which ones are disputed? Once these answers are clear, it becomes easier to decide whether you need simple data sync, a full ERP connection, or a phased rollout across departments.
- What must be automated first to save the most time?
- Which reports need to be accurate for month-end?
- Who will own the process once the systems are linked?
- What can be left manual for now without creating risk?
Map Every System and Every Data Owner
A good integration plan starts with a full system map. List each tool in use, the data it holds, and the person who controls it. This includes accounting software, payroll, CRM, stock tools, spreadsheets, banking files, and any external platform used for orders or customer service. In Durban and Cape Town, where teams may work across sites or from home, it helps to note who updates what and when.
Do not assume that two systems use the same terms. A customer code in one package may be a debtor account in another. A product description may be shortened in one place and detailed in another. These small differences can break imports, reports or approvals if they are not planned for early.
- List every system, spreadsheet and external service in use.
- Record the owner of each data set.
- Note file formats, update times and export rules.
- Check whether the same record exists in more than one place.
Questions to Ask Before Connecting Finance, Payroll and Sales
Some connections are straightforward, while others need tight controls. Finance and payroll often carry sensitive information, and sales data may be used by several teams at once. For South African SMEs, compliance matters as well, especially where employee records, tax information and customer data are involved. A rushed integration can create more admin than it removes.
Use these questions to test whether the connection is ready. Will the integration update live records or run on a schedule? What happens if a file fails halfway through? Can users see only the information they need, or too much? Is there a clear sign-off step for payroll, invoices or credit notes? If the answer is unclear, that process should be defined before any build begins.
- Does the system need live sync or batch updates?
- Who approves each transaction before it posts?
- How are errors flagged and corrected?
- What audit trail is kept for each update?
Plan for Data Quality, Cutover and Load-Shedding
Integration work is only as good as the data going into it. If customer names, supplier codes or stock items are inconsistent, the linked systems will simply repeat the problem faster. Clean-up must be part of the plan, not an afterthought. This is especially important for businesses with old records, multiple branches or staff who have entered data different ways over several years.
Cutover is another point that needs care. Decide when the old process stops and the new one starts, who checks the first batch of results, and how long both systems will run in parallel. In South Africa, power cuts can interrupt a transfer or sync at the worst time, so timing matters. If a process may be affected by load-shedding, choose a window with support on hand and a clear recovery step.
- Clean duplicate records before the connection goes live.
- Set a date and time for the cutover.
- Keep a backup export of critical data.
- Test the process after power interruptions and reconnects.
Set Rules for Security, Access and Reporting
Not every user should see or change every field. A payroll clerk does not need the same access as a sales manager, and a branch user should not override finance controls. Clear access rules reduce mistakes and protect confidential information. For businesses operating in Pretoria, East Rand and West Rand, this is often where integration planning either holds up well or falls apart later.
Reporting needs equal attention. Decide which numbers must be pulled from the source system, which should be calculated in the ERP, and how often management reports must refresh. If your figures are used for cash flow, stock planning or client billing, the definitions must be the same across all teams. One small mismatch can throw off a month-end pack and waste hours in follow-up, so the rules should be written down before go-live.
Use a Practical Go-Live Checklist
Once the mapping is done, the next step is to test the flow in a controlled way. A strong checklist helps the project team avoid last-minute surprises. It also makes handover easier for support teams, especially when more than one branch is involved or the business works across different provinces. Keep the list short enough to use, but detailed enough to catch the important things.
- Confirm all source data has been cleaned and approved.
- Test each connection with real sample records.
- Check that failed transactions can be reprocessed.
- Verify reports after the first live update.
- Train the users who will work with the new process daily.
- Set a support path for the first week after launch.
After go-live, review what worked and what slowed the team down. A proper integration plan is not only about the first connection, it is about keeping the flow reliable as the business grows.
