System integration
Getting our systems talking to the ones you already run, so a number entered once does not need entering again somewhere else. Most of the value in new software is lost at the seams.
What we integrate with
Anything with an API or a file drop: Sage, payroll systems, banking files, municipal financial systems, and the spreadsheet somebody maintains by hand.
Benefits
One version of the number
Data entered once and read everywhere, instead of three systems disagreeing about the same figure.
Less manual re-keying
The copying between systems that eats an afternoon a week, and introduces the errors nobody can trace later.
Your existing systems keep working
Integration rather than replacement, so a system that does its job well is left alone.
What it covers
API integration
Documented, authenticated connections between our products and yours, built to survive the other side changing without warning.
File-based exchange
Where an API does not exist, scheduled imports and exports in the format the other system actually accepts.
Financial system links
Posting to the general ledger properly, including the mSCOA segments municipal systems require.
Error handling that tells you
When a sync fails, somebody is told and the record is queued, rather than the failure being discovered at month end.
How the work runs
Map the data
What lives where, which system owns each field, and what has to move in which direction.
Agree the contract
The exact shape of what is exchanged, written down so both sides can build against it.
Build and test
Built against a copy of your data, and reconciled line by line before it touches production.
Monitor
Alerting on failures, because a silent integration is one nobody notices has stopped.