Which direction does data move between Deltek and TrueCommerce?

It moves both ways. Inbound 850 purchase orders and 820 remittance advice flow from TrueCommerce into Deltek as projects and receivables, while AR invoices flow from Deltek out through TrueCommerce as 810 EDI invoices. TrueCommerce is the delivery network to your trading partners, so it never holds finance master data of its own.

Does TrueCommerce expose a REST API like Deltek does?

No. TrueCommerce is EDI middleware that exchanges X12 documents over a provisioned SFTP server, not a self-serve REST API with vendor or invoice objects. ml-connector polls and writes flat files on that SFTP host, and TrueCommerce translates them to and from X12 for the trading partner. Deltek, by contrast, is read and written through its OAuth2 REST API.

How does the integration handle authentication and duplicate documents?

ml-connector requests a Deltek bearer token through the OAuth2 password grant and refreshes it on a 401, and it connects to TrueCommerce with the SFTP credentials TrueCommerce provisions at onboarding. Because Deltek has no idempotency key, it checks for an existing record by number before posting, while the EDI ISA control number prevents duplicate interchanges on the TrueCommerce side.

DeltekTrueCommerce

Deltek and TrueCommerce integration

Deltek runs project accounting and finance. TrueCommerce moves EDI documents between you and your trading partners. Connecting the two lets inbound electronic orders and remittance advice land in Deltek without re-keying, and lets the AR invoices Deltek bills flow out to retailers as standard EDI. ml-connector reads the very different transports on each side, an OAuth2 REST API on Deltek and a provisioned SFTP server on TrueCommerce, and moves the records on a schedule you control.

How Deltek works

Deltek Vantagepoint exposes firms, contacts, employees, projects, AP invoices, AR invoices, journal entries, cash receipts, and GL accounts through a REST API on a tenant-specific URL such as https://acme.deltekfirst.com/acme/api/. It authenticates with an OAuth2 password grant that returns a bearer token, and the Allow Password Grant Type setting must be enabled for server-to-server use. Vantagepoint has workflow-driven outbound webhooks on hub record saves, but they carry no HMAC signature and are not a general event bus, so finance records are read by polling. Deltek Costpoint covers the same data through SOAP web services and preprocessor file imports instead.

How TrueCommerce works

TrueCommerce is EDI middleware, not an ERP, so it has no native vendor, invoice, or GL objects of its own. It exchanges X12 transaction sets, including 850 purchase orders and 820 remittance advice inbound and 810 invoices, 855 PO acknowledgments, and 856 ship notices outbound, by dropping and picking up flat files on its hosted SFTP server at integrationftp.truecommerce.com. Credentials are provisioned by TrueCommerce during onboarding rather than self-issued, and import and export folder paths plus ISA sender and receiver IDs are configured per customer. TrueCommerce is pull-based with no reliable self-serve webhook, so the supported pattern is a scheduled poll of its SFTP directories.

What moves between them

Inbound, ml-connector polls the TrueCommerce SFTP drop for 850 purchase orders and 820 remittance advice and writes them into Deltek as projects or AR receipts mapped to the matching firm. Outbound, it reads new AR invoices from Deltek and renders them as 810 invoice files that TrueCommerce translates to X12 and delivers to the trading partner, and it can return 855 acknowledgments for orders Deltek accepts. Reference data such as trading-partner identity and item codes is aligned to Deltek firms and projects so each document lands on a valid record. Cadence is poll-based on both sides, typically hourly, because neither Deltek finance reads nor TrueCommerce SFTP offers a dependable push.

How ml-connector handles it

ml-connector stores both credential sets encrypted, requests a Deltek bearer token with the OAuth2 password grant and refreshes it when a call returns 401, and connects to the TrueCommerce SFTP host with its provisioned username and password. Because TrueCommerce file paths and ISA IDs are not standardized, the inbound and outbound folders and the sender and receiver IDs are configured per customer at setup. Each 850 is mapped to a Deltek firm and a project, and each Deltek AR invoice is mapped to an 810 with the correct PO reference and remit-to. Deltek has no idempotency key, so ml-connector checks for an existing record by number before posting, and the EDI ISA control number guards duplicates on the TrueCommerce side. Deltek publishes no rate limit, so it backs off conservatively, retries failed posts, and keeps a full audit trail so any document can be replayed if a downstream call fails. Watch for the Deltek API role: fields hidden from that role return zero or are omitted rather than erroring, so the integration user needs full field visibility.

A real-world example

A mid-sized architecture and engineering firm of around two hundred staff runs Deltek Vantagepoint for project accounting and bills several large institutional clients that mandate EDI through TrueCommerce. Before the integration, a billing clerk exported each project invoice from Deltek and manually keyed it into the TrueCommerce portal as an 810, then watched the SFTP folder for inbound client purchase orders and typed them into Deltek as new projects. With Deltek and TrueCommerce connected, approved AR invoices flow out as 810 files automatically and inbound 850 orders open projects against the right client firm, so the clerk stops re-keying both directions and EDI rejections from mismatched references drop sharply.

What you can do

Turn inbound TrueCommerce 850 purchase orders into Deltek projects mapped to the right client firm.
Read new Deltek AR invoices and send them out through TrueCommerce as 810 EDI invoices with the correct PO reference.
Post inbound 820 remittance advice from TrueCommerce against the matching Deltek receivables.
Bridge the Deltek OAuth2 password-grant token with TrueCommerce provisioned SFTP credentials and per-customer folder paths.
Poll both sides on a schedule with duplicate checks, retries, and a full audit trail on every document.

Questions

Which direction does data move between Deltek and TrueCommerce?: It moves both ways. Inbound 850 purchase orders and 820 remittance advice flow from TrueCommerce into Deltek as projects and receivables, while AR invoices flow from Deltek out through TrueCommerce as 810 EDI invoices. TrueCommerce is the delivery network to your trading partners, so it never holds finance master data of its own.
Does TrueCommerce expose a REST API like Deltek does?: No. TrueCommerce is EDI middleware that exchanges X12 documents over a provisioned SFTP server, not a self-serve REST API with vendor or invoice objects. ml-connector polls and writes flat files on that SFTP host, and TrueCommerce translates them to and from X12 for the trading partner. Deltek, by contrast, is read and written through its OAuth2 REST API.
How does the integration handle authentication and duplicate documents?: ml-connector requests a Deltek bearer token through the OAuth2 password grant and refreshes it on a 401, and it connects to TrueCommerce with the SFTP credentials TrueCommerce provisions at onboarding. Because Deltek has no idempotency key, it checks for an existing record by number before posting, while the EDI ISA control number prevents duplicate interchanges on the TrueCommerce side.

Connect Deltek and TrueCommerce

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started