Integrations
What Covex talks to
Covex talks to your accounting system, the map, the inbox and your own systems. Here is what's ready, what is produced as a file, and what needs an agreement with a third party — without dressing it up.
The customer, the address and the price are entered once in Covex. The integrations make sure the rest of your systems get the same data — without a daily export and without keying it in twice.
How are they connected?
Every integration follows the same pattern: a connection with provider and status, references that link a Covex object to the provider's so nothing is created twice, and a log with one entry per run.
Where do the keys live?
Never in the database. The connection points to the name of an environment variable, and the server reads the key from there.
What if something fails?
The integration's log shows the reasons, not just the count. Identical errors are grouped, so 40 failures become one line with a count and a few examples.
Connections and status
| Area | What | Status |
|---|---|---|
| Accounting system | e-conomic: invoices, credit notes, payment status | Ready |
| E-invoicing | UBL 2.1 and Peppol BIS Billing 3.0 to NemHandel | File produced |
| Documents in | Bookings and consignment notes from email, read and matched | Ready |
| Maps and route distance | Mapbox, PTV or OSRM | Ready |
| Credit checks | Creditsafe, with automatic blocking after the due date | Needs an agreement |
| Telematics | Positions, driving and rest times and kilometres driven, from the cab | Needs an agreement |
| Open API | Orders, events and supplier invoices, plus webhooks | Ready |
Some integrations need an agreement with a third party before they can be used: credit bureaus, telematics, ferry and toll companies, EDI and electronic consignment notes. The code is built and tested against their documented interfaces, but it can only be switched on once the agreement is in place. Under Integrations, Covex honestly says “no adapter” for the ones that aren't connected yet.
Honest status
Ready, file produced or needs an agreement — that's what it says, and that's what applies.
Integrations
Finance system
e-conomic
ReadyE-invoice
Peppol BIS 3.0
File generatedMaps and distance
Mapbox, PTV, OSRM
ReadyTelematics
Positions and driving time
Requires agreementCredit check
Block after due date
Requires agreementArea 1
Accounting and e-invoicing
Covex talks to e-conomic. Customers are created there if they're missing and linked to the ones that exist. Issued invoices become drafts with the Covex number as reference, credit notes become drafts with negative lines. Once an invoice is booked and paid in e-conomic, it shows as paid in Covex.
The e-invoice is produced as UBL 2.1 and Peppol BIS Billing 3.0 — the format NemHandel uses.
things kept in step with e-conomic: customers, invoices and payments.
Invoice 2024-0412
Nordlys Møbler · DKK 12,480
Finance system
e-conomic
ReadyE-invoice
UBL 2.1 · Peppol BIS 3.0
File generated
“Drafts are not booked from Covex. The numbers in the accounts have to be approved by a person.”
How the e-conomic integration works
Area 2
Documents, maps and telematics
Bookings and consignment notes from email are read, matched and put up for review as a draft. Route distances are calculated with Mapbox, PTV or OSRM.
Telematics provides positions, driving and rest times and kilometres driven, straight from the cab. It needs an agreement with the provider. Positions can also be sent in through the API; a position older than the latest one on the trip doesn't overwrite the current picture.
map providers to choose from for route distance: Mapbox, PTV or OSRM.
Import customers
customers.xlsx · 1,284 rows
“An integration never sets a status directly. It triggers a transition, and the transition can be rejected.”
A Covex principle
Area 3
Open API and webhooks
Your own system can fetch orders, create new ones and send events: positions, stop events, scans and status changes. Orders coming in from outside are created as drafts, so a person sees them before they become an agreement.
Carriers can send supplier invoices, which Covex allocates to the orders and matches line by line against the agreement. Webhooks pass on events from the order with a signature the receiver can verify.
calls a minute per API key before Covex asks you to wait. The limit can be raised per installation.
Webhook
https://erp.kolvand.example/covex
Last delivery 14:47 · 200 OK
order events can be sent as webhooks — from created to invoiced.
retries of a webhook, after 1, 2, 4, 8 and 16 minutes, if the receiver doesn't respond.
scopes a key can have: read orders, create orders, read tracking and send events.
Missing an integration?
Some integrations need an agreement with a third party before they can be used. The code is built and tested against their documented interfaces, but it can only be switched on once the agreement is in place.
Tell us which system you use, and we'll get back to you with where it stands — honestly.
Contact us
Contact us – email coming soon