Wialon integrated with the systems you already run

The job backs off and retries on a schedule rather than hammering the endpoint, and the run is marked incomplete rather than partially successful. Bulk history pulls are moved off the hours when operational calls need the budget, so a backfill never starves a live workflow.

Yes, and it is the common case. Most integrations run against an API or an agreed file exchange over SFTP. Direct database writes are a last resort — they couple the integration to a schema the vendor is free to change without telling you.

A reconciliation job compares record counts and key aggregates between Wialon and the target on a schedule, and alerts on drift beyond a threshold you set. Without that check, an integration that quietly stops looks identical to a quiet week.

Yes. Transactions arrive from the card provider as a CSV or an API feed, are matched to a unit by its card assignment, and are then checked against that unit's position and fuel level at the time of the transaction. You get back the transactions that disagree with the vehicle — wrong place, no rise in the tank, more litres than the tank holds — and the rest posted as fuel cost per unit, driver and cost centre.

Any provider that publishes a statement. DKV, E100, Shell, Circle K, UTA, Neste and the national chains all publish a CSV or Excel file on SFTP, an API, or both; the columns differ, and mapping them is a day of work rather than a dependency. A provider that only emails a PDF can be read out of the mailbox and parsed, which is slower to set up and worth avoiding if a file can be requested instead.

Yes, and three checks say whether you need one: the report wants a field Wialon does not hold, it has to cross accounts or resources, or it exceeds the execution budget — five minutes of server time, 400,000 rows for a detalized table. Any of the three means the report gets built beside Wialon and reads it through the API on a schedule.

Yes. Scheduled delivery is part of the same build: PDF or XLSX by email on a date you set, a file on SFTP, or a message into Telegram or Slack, with your logo and colours on the document. The recipients need no Wialon login, which is usually the reason the report is being built.

Yes. Units, accounts and billing plans come out of Wialon, get priced against your contracts, and land in the accounting system as invoice lines — 1C, Business Central, Odoo, or whatever holds your ledger. The same pass recharges fuel and mileage to the customer who incurred it, so nothing is retyped from a report.

Small integrations usually take 3 to 5 weeks. Multi-system programs are phased and typically run 8 to 12 weeks.