System integration services
Your systems already have the data. We make them share it.
An invoice typed into one system and retyped into another. A payroll run exported to a spreadsheet so finance can post it. We remove those steps by connecting the systems directly: ERP, HR, e-invoicing, workshop, and the enterprise platforms you already run.
ERPNext
OracleSAP SuccessFactorsSAPEach line is an integration we have delivered.
- 6
- delivered integrations shown on this page
- 5
- integration methods
- 2
- directions: every link can read and write
Why integrate
What it costs when systems do not talk.
The same data, typed twice
Every re-entry is a chance for a wrong digit, and an hour of someone’s day that produces nothing new.
Two versions of the truth
HR’s payroll total and finance’s posting disagree, and month-end turns into an investigation.
Compliance waits for a person
An invoice that ZATCA must clear cannot wait for someone to export a file and upload it.
Delivered integrations
Six integrations we have already built.
These are live examples, not a wish list. Pick a pair to see what moves between the two systems.
ERPNextERP to ZATCA e-invoicing
- ERPNextsends
- Sales invoices, credit notes and debit notes go to Taxilla for validation and ZATCA clearance.
- Taxillasends
- The cleared status, invoice UUID and QR code come back onto the invoice in ERPNext.
ResultE-invoicing compliance without leaving the ERP.
Oracle, SAP and SAP SuccessFactors were the customers’ existing systems in these projects.
The products in these integrations:ERPNextTaxilla e-invoicingHR WorksGaragePlug
What we connect
All types of integration services.
If two systems need the same data, we can connect them. These are the pairs we are asked for most.
ERP and e-invoicing
Invoices cleared with ZATCA from inside your ERP.
ERP and HR or payroll
Payroll, loans and end-of-service postings into the ledger.
HR and enterprise platforms
HR Works alongside Oracle, SAP and SAP SuccessFactors.
Devices and attendance
Biometric terminals and access control into time attendance.
Industry systems and ERP
Workshop, cafeteria and visitor systems into finance and stock.
CRM and contact center
Calls and messages matched to the customer record.
Reporting and BI
Data from several systems in one model for dashboards.
Legacy and custom applications
Older or in-house systems connected, or migrated out.
Methods
Five ways to connect, chosen by what each system supports.
- 01
API / SDK
The preferred route when both systems expose one. Fast, and suited to real-time exchange.
- 02
Web services
SOAP and REST services, common on enterprise platforms.
- 03
FTP / SFTP
Scheduled, secure file exchange for systems that work in batches.
- 04
Staging tables
A shared set of database tables that one system writes and the other reads.
- 05
Custom connectors
Purpose-built middleware when a system offers none of the above.
How we work
Five steps, and a document at each one.
- 1
Map
We list the data, the direction, the frequency and the system that owns each field.
You getA field-mapping document
- 2
Design
We choose the method, the triggers and what happens when something fails.
You getAn integration design
- 3
Build
We build the link against test environments of both systems.
You getA working link in test
- 4
Test
We run real cases with your team and reconcile counts and totals on both sides.
You getA signed test report
- 5
Run
We go live, watch the first cycles, and support the link when either system changes.
You getMonitoring and support
What keeps an integration reliable
One owner per field
Each piece of data has one system of record, so the two sides never argue.
Failures are visible
A record that does not go through is logged and retried. It is never dropped silently.
Both sides reconcile
Counts and totals are compared, so a gap is found the same day.
Access is limited
The link uses its own credentials with only the permissions it needs.
FAQ
Questions we hear first.
Can you integrate a system that is not on this page?
Yes. If the system offers an API, a web service, file exchange or database access, we use that. If it offers none, we build a custom connector.
Do you only integrate products you sell?
No. In the HR Works projects with Oracle, SAP and SAP SuccessFactors, the other system was the customer’s existing platform. We connect whatever you already run.
Is the exchange real time or scheduled?
Either. ZATCA clearance happens as the invoice is issued. A payroll posting happens once per approved run. We choose the timing that the process needs.
What do you need from us to start?
The two systems and their versions, the data that should move and in which direction, how often, and access to a test environment of each.
Who supports it after go-live?
We do. We monitor the link, fix failed records, and update the integration when either system is upgraded.
Tell us the two systems. We will tell you how they connect.
Send the names of the systems and the data you want to move. We will reply with the method we recommend and what we need to scope it.
Discuss an integrationERPNext, Taxilla, GaragePlug, Oracle, SAP and SAP SuccessFactors are trademarks of their owners. HR Works is a Prestige product.