Wave Accounting and TrueCommerce integration

What moves between them

Inbound EDI documents flow from TrueCommerce SFTP into Wave. Purchase Order (850) and Purchase Order Change (860) documents are parsed and stored in Wave's transaction log. Invoice (810) and Remittance Advice (820) documents are posted as vendor expenses and matched to Wave's chart of accounts. Outbound, Wave invoices are exported to TrueCommerce SFTP as EDI 810 documents for supplier visibility. Reference data such as vendor names and account codes are synced bidirectionally so Wave customers align with TrueCommerce partner names. All EDI documents carry functional acknowledgments (997) to confirm receipt.

How ml-connector handles it

ml-connector polls TrueCommerce SFTP daily on a schedule you set. Each poll retrieves EDI documents and converts them using document-type-specific transformers: 850 becomes a Wave transaction record, 810 becomes an expense entry allocated to the matching account code, 997 is processed for deduplication via X12 ISA control numbers. Wave authentication uses OAuth 2.0 with token refresh every 90 minutes before expiry. TrueCommerce credentials (SFTP username and password) are stored encrypted in ml-connector's vault. Because TrueCommerce does not expose rate limits publicly and file naming is customer-specific, ml-connector confirms naming conventions and polling intervals during onboarding with the TrueCommerce support team. Failed documents are retried with exponential backoff and tracked in the audit log for replay. Every transformation carries full lineage so EDI source data can be traced back to Wave entries.

A real-world example

A small manufacturing business uses Wave Accounting for expense tracking and invoicing, and TrueCommerce EDI to connect with three major suppliers who send purchase orders, invoices, and advance ship notices. Before the integration, the operations team downloaded EDI files from the TrueCommerce mailbox each morning, manually extracted vendor and line-item details, and entered them into Wave by hand. Supplier price changes, order cancellations, and invoice corrections all required re-keying. With Wave and TrueCommerce connected, EDI documents arrive in Wave's expense log automatically, allocated to the correct cost codes, and the reconciliation between what was ordered, what was shipped, and what was invoiced happens in minutes rather than hours.

What you can do

• •Automatically post incoming TrueCommerce EDI invoices (810) to Wave as vendor expenses and map them to the correct general ledger accounts.
• •Transform EDI purchase orders (850) into Wave transaction records so supplier orders are visible in the same system as Wave invoicing.
• •Sync Wave vendor records with TrueCommerce trading partner names and account codes so orders and invoices route to the correct supplier.
• •Authenticate Wave with OAuth 2.0 token refresh and retrieve EDI documents from TrueCommerce SFTP with encrypted credentials stored in ml-connector.
• •Poll TrueCommerce on a custom schedule, deduplicate documents via X12 ISA control numbers, and maintain a full audit trail of every EDI transformation.

Questions

Which direction does data move between Wave Accounting and TrueCommerce?

The main flow is TrueCommerce EDI into Wave. Purchase orders, invoices, and advance ship notices from trading partners flow into Wave as transaction and expense records. Wave invoices can also be exported to TrueCommerce as EDI 810 documents for supplier visibility. Vendor names and account codes are aligned bidirectionally.

How does ml-connector handle TrueCommerce's lack of a public API and custom file naming?

TrueCommerce provisions SFTP credentials and confirms file naming conventions and integration paths during account setup with the TrueCommerce team. ml-connector stores those credentials encrypted and polls the SFTP mailbox on a schedule you define. Polling intervals are typically hourly or daily depending on your trading partner activity.

What happens if an EDI document fails to transform or post to Wave?

ml-connector logs every document and transformation in the audit trail. Failed documents are retried with exponential backoff. If a retry exhausts, the document is flagged for manual review and the transformation steps are recorded so the record can be replayed once the root cause is fixed.