Connecting over a service
If the other program exposes a web service, this is the cleanest route. Records are written through the program's own rules, with no direct interference in its database.
Integrations
You do not have to abandon the accounting software you already use. Your Xpoda applications talk to your existing system.
Why integrate?
In most companies the same information is entered twice — once in the field or in sales, and again in accounting. That costs time and creates errors. With integration, data is entered once and flows automatically to the relevant system.
Connection Methods
How the systems connect
There is no single method — we pick based on what the other system allows. Most installations end up using two or three of these together.
Reading at database level
For systems without a service, the relevant tables are read with an authorised user. Write operations are only performed where the vendor supports them.
File-based transfer
Scheduled transfer via CSV, XML or Excel. Where live flow is not required — an overnight stock sync, for example — this is simple and resilient.
e-Invoice and e-waybill
Document processes run through the private integrator you already work with. A document raised in Xpoda keeps the same numbering as the financial side.
Process
How we set it up
An integration is not a switch you flip once; it is a small project. We usually work in this order:
1
Discovery. We establish which program, which version and which modules you run, and look at the reachable data together.
2
Field mapping. We put in writing which field corresponds to what — account code, stock unit, VAT rate and so on.
3
Test environment. The transfer runs first against copied data, so you can compare results without touching live records.
4
Go live. After your approval it is switched on; transfers are monitored in the first period and corrected if anything drifts.
Mikro Yazılım
Mikro Yazılım – Xpoda Integration
We set up two-way data flow between the accounts, stock and invoice records you keep in Mikro Yazılım and your field, warehouse and sales applications on Xpoda. An order entered by your sales team reaches accounting; the account balance in accounting is visible in the field.
Data typically transferred
- Customer / supplier account cards and balances
- Stock cards, units and price lists
- Order, waybill and invoice movements
- Collection and payment records
The scope of the integration depends on your Mikro version and the modules you licence. We review your existing installation and confirm together which fields can be transferred.
Logo Yazılımları
Logo Yazılımları – Xpoda Integration
We build a data bridge between the Logo product family (Tiger, GO and similar) and your Xpoda applications, so you can run warehouse, production and field processes on Xpoda while your financial records stay in Logo.
Data typically transferred
- Account and stock cards
- Order and dispatch documents
- Invoice and waybill movements
- Stock levels by warehouse
Scope varies with your Logo version and licensed modules. We define the details during a discovery call.
SAP
SAP – Xpoda Integration
We build a robust and reliable data bridge between your SAP ERP system (S/4HANA, ECC) and your operational applications on Xpoda. While you manage your production, purchasing, warehouse, and HR processes with Xpoda's flexibility, your master data and costs remain up-to-date in SAP.
Data typically transferred
- Material and customer (customer/vendor) master data
- Purchase orders, production orders, and confirmations
- Goods receipt/issue and stock movements
- Financial records and cost center distributions
SAP integration can be provided via BAPI, RFC, OData, or IDoc. We determine the most suitable method for your needs and SAP infrastructure during the system architecture phase.
Canias ERP
Canias ERP – Xpoda Integration
Thanks to the integration we will establish between Canias ERP and Xpoda, we enable the end-to-end digitalization of your business. The TROIA infrastructure and Xpoda's flexible low-code architecture complement each other to accelerate your processes.
Data typically transferred
- Account, stock, and BOM (Bill of Materials) cards
- Sales orders and dispatch operations
- Production work orders and routing steps
- Warehouse counting and transfer documents
Integration is usually designed bi-directionally via Canias Web Services (SOAP/REST) or direct database (secure views).
FAQ
Common questions about integration
Do I have to drop my current accounting software?
No — the point of integration is the opposite. Your financial records stay in the program you use today, while Xpoda takes over the operational side: field, warehouse, production. The two systems feed each other.
Does data flow one way or both ways?
Either is possible; which one we build depends on your process. Stock levels often flow one way from accounting into Xpoda, while orders travel from Xpoda into accounting. Direction and scope are written down during field mapping.
How often does synchronisation run?
It varies by setup. Critical movements such as orders can be triggered at the moment of the transaction, while large data sets like stock and price lists are usually transferred at intervals or in an overnight batch. The frequency is set by what the other system can carry.
Do I need an extra licence or module?
This comes up on the other program's side, not Xpoda's. Some accounting packages licence their web service or integration module separately. We check your existing licence during discovery and tell you before we start if anything extra is required.
What happens if a transfer fails?
Transfers are logged. If a record hits a rule in the other system — a missing account code, an undefined unit — that record is flagged and reported with its reason, then resent once the issue is fixed. One bad record does not stop the whole transfer.
How long does setup take?
Quoting a fixed number of days would be misleading; what decides it is the number of fields to transfer and how accessible the other system is. After the discovery call we share a realistic schedule based on the actual scope.
Note: These answers describe the general approach. What is possible in your particular setup depends on the version and licence of the program you run, and is confirmed during the discovery call.
Other systems
Using a program that is not listed here? Thanks to Xpoda's integration capabilities, a connection can usually be built with any system that is open to data exchange — whether through an API, a database or files. Tell us which software you use and we will assess it and come back to you.
Let us review your current system
Tell us which program you use and which data you want to flow; we will give you a clear answer on what is technically possible.
Get in Touch