NetSuite, Infor, and fully custom or in-house-built ERPs — if it can produce structured invoice data, we've likely already connected something like it.
NetSuite, Infor M3/LN, and bespoke systems built on anything from legacy 4GL platforms to modern custom stacks.
| Method | When we use it |
|---|---|
| SFTP-based exchange | Scheduled file drop/pickup — the standard path for systems with batch export capability but no live API. |
| Intermediate/staging database | A shared staging layer between the source system and dsFatoora Middleware. |
| Direct database extraction | Reading transactional data straight from the source system's database where no API or export exists. |
| REST API-based integration | Real-time, used wherever the source system exposes one. |
In-house systems are often tightly fitted to a specific business process, which makes source data well understood by the team that built them.
Almost none ship with ZATCA/FTA compliance built in, and documentation quality varies widely — discovery takes longer than with a commercial ERP.
We've delivered live integrations in KSA against known ERPs, legacy platforms, and fully in-house-built systems using whichever of the four methods above fits what the source system can actually expose — see our Legacy & Custom ERP Integration Methods page for the detailed comparison.
In most cases yes, via direct database extraction or a staging database, provided we can get read access to posted invoice data.
Typically 1–3 weeks depending on schema complexity and how much institutional knowledge is available from your team.