Do we have to use EDI?

No. Most carriers record waits with the driver app. EDI suits carriers whose TMS already sends 214s.

210s are sent as X12 version 004010. The setup guide lists the segments Demurly reads from a 214 and writes in a 210.

EDI integration

EDI 214s in, 210 invoices out

Carriers' X12 214 status messages open and close demurrage waits in Demurly, and an X12 210 invoice goes out for each approved charge.

Pro for carriers; SFTP delivery on Enterprise

Your TMS's X12 214 status messages (arrived, departed) open a wait when the truck arrives and stop it when it leaves, at the reported times.
An X12 210 invoice goes to your partner for each approved charge, by HTTPS, to a REST API, or on Enterprise as a file on the partner's SFTP server.
Every inbound interchange is answered with a 997 acknowledgment.

1Set up inbound and outbound configurations under Settings > EDI.
2Send 214s to Demurly by HTTPS POST, signed with your configuration's secret; a resent message is processed once.
3Message History shows every message in and out, and Settings > Data exchange shows whether each route is working.

Do we have to use EDI?: No. Most carriers record waits with the driver app. EDI suits carriers whose TMS already sends 214s.
Which X12 version?: 210s are sent as X12 version 004010. The setup guide lists the segments Demurly reads from a 214 and writes in a 210.

QuickBooks Online

Invoices for carriers, bills for fuel buyers, payments both ways.

NetSuite

Invoices for carriers, vendor bills for fuel buyers, payments both ways.

SAP Business One

A/R invoices for carriers, A/P invoices or drafts for fuel buyers.

PDI Enterprise

Import files for approved charges, and payment registers back.

API and webhooks

REST API, signed webhooks, test mode and an MCP server.