NetSuite integration
Demurrage charges in NetSuite, matched and paid
Approved demurrage charges become NetSuite invoices for carriers and vendor bills for fuel buyers, with payments marked paid both ways.
Pro for carriers ($199 a month); free for fuel buyers
What it does
For carriers
- Each approved charge becomes an invoice for the customer in NetSuite, using the item you choose.
- Payments made in Demurly are recorded in NetSuite, and invoices paid in NetSuite mark the charge paid.
For fuel buyers
- Each approved charge becomes a vendor bill against the vendor you map (or one Demurly creates, if you turn it on).
- Vendor payments go both ways: paid in Demurly, recorded in NetSuite; paid in NetSuite, shown in Demurly.
How it works
- 1An admin connects NetSuite under Settings > Integrations with token-based authentication: account ID, consumer key and secret, token ID and secret.
- 2OneWorld accounts can name the subsidiary. Demurly tests the connection when you save.
- 3Each sync shows under Recent activity.
Questions
- Can I connect a NetSuite sandbox?
- Yes: use the sandbox's account ID (for example 1234567_SB1) to try it before connecting production.
- What NetSuite permissions does Demurly need?
- A role that can create and read the records it syncs. The setup guide lists them.
Other integrations
QuickBooks Online
Invoices for carriers, 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.
EDI
214s open and close waits; 210s go out for approved charges.
API and webhooks
REST API, signed webhooks, test mode and an MCP server.