Why double entry keeps happening
Most growing businesses add software one problem at a time. Sales picks a CRM, finance picks an accounting package, HR picks a payroll tool, and operations runs on spreadsheets. Each choice makes sense on its own. The trouble starts when the same customer, invoice or employee has to be typed into three places.
Double entry is slow, but the bigger cost is inconsistency. A customer’s address is updated in the CRM but not in accounting. A new hire’s salary is changed in HR but the old figure is used in a project costing sheet. Nobody is sure which number is right, so people keep their own copies, and the problem grows.
Start with a map, not a tool
Before any connector is switched on, list the main records your business handles and decide which system is the single source of truth for each. A simple table is enough:
- Customers and contacts: usually owned by the CRM.
- Invoices, payments and tax: owned by the accounting system.
- Employees, salaries and leave: owned by the HR or payroll system.
- Jobs, projects, stock or bookings: owned by your operations tool.
For each record, note who creates it, who changes it and which other systems need to read it. Data should flow out from the owning system. If two systems can both edit the same field, decide which one wins in a conflict, or you will end up with records overwriting each other.
Singapore requirements that shape the design
Some local rules affect what your integrated systems need to produce and keep. Check these early so the design supports them:
- GST and InvoiceNow. IRAS requires GST-registered businesses to submit invoice data to IRAS using InvoiceNow-Ready Solutions, rolled out in phases. Businesses that apply for voluntary GST registration on or after 1 April 2026 are already covered, and existing GST-registered businesses are phased in from 1 April 2028 to 1 April 2031 according to their annual supplies. InvoiceNow is Singapore’s e-invoicing network based on the Peppol standard. If your sales or operations system creates invoices, plan how that data will reach an InvoiceNow-Ready accounting solution.
- Itemised payslips. MOM requires employers to issue itemised payslips to employees covered by the Employment Act, with items such as basic salary, allowances, deductions and overtime. Payslips must be given with payment or within three working days, and records kept for the latest two years for current staff. If timesheets or overtime come from an operations tool, the HR integration must carry those figures accurately.
- Personal data. Integrations copy personal data between systems, which widens the area you must protect. Under the PDPA, if a data breach is assessed as notifiable, the organisation must notify the PDPC no later than three calendar days after that assessment.
Choosing how to connect
There are three common ways to link business systems. Most companies use a mix.
- Native connectors offered by the software vendor. Quick to set up and supported by the vendor, but limited to the fields and triggers the vendor chose.
- An integration platform that sits between your tools and moves data according to rules you define. Good when you have several systems and want one place to monitor flows.
- Custom integration built against each system’s API. Best when you need specific logic, high volumes or systems that off-the-shelf connectors do not cover.
Whichever route you choose, ask for error handling as part of the build. Every integration fails at some point: an API is down, a field is missing, a password expires. You need to know about it the same day, and you need a way to replay the failed records.
A practical checklist before you build
- Each record type has one owning system, written down and agreed.
- Field mappings are documented, including formats for dates, currencies and phone numbers.
- Duplicates have been cleaned up in the source systems before the first sync.
- Each integration uses its own service account with only the access it needs.
- Personal data is only copied to systems that genuinely need it.
- Failed syncs raise an alert to a named person.
- There is a test environment, or at least a test company file, for trying changes.
- Someone owns the integration after go-live and knows how to pause it.
Working with an integration partner
If an outside firm builds or runs your integrations, it may process personal data on your behalf. PDPC guidance explains that a contractor processing personal data for a customer is likely to be a data intermediary, and that the customer remains liable for the contractor’s acts or omissions that breach the PDPA. PDPC publishes sample contract clauses covering purpose limits, security, overseas transfers, retention and breach notification. It is worth using them as a checklist for your agreement.
Useful questions to ask a partner:
- Where will our data be stored and processed, and will any of it leave Singapore?
- How will you tell us about a failed sync or a suspected breach, and how quickly?
- What documentation will we receive, so another team could take over?
- How are API keys and passwords stored and rotated?
A sensible next step
Take one record that is typed in more than once today, such as a new customer or a new employee, and trace every place it ends up. Note who enters it, in which system, and how long it takes. That single trace usually shows where an integration would save the most time and where the data protection risks sit. We can help you turn it into a practical integration plan.
Related service: Systems Integration


Comments
No comments yet. Questions about the guide are welcome.