Drypowder Help Center

How Spruce integration keeps data in sync

What syncs from Spruce in real time, what posts back, and what happens when the sync breaks.

Drypowder connects to ECI Spruce to pull AR data and post settled payments back to the general ledger. This article explains what data flows in each direction, how the two integration modes differ, and what to expect.

Two integration modes

Drypowder supports two ways of getting AR data into the system.

ECI Spruce (direct integration): Real-time, bidirectional sync through ECI's private API. AR data flows from Spruce to Drypowder automatically, and settled payments post back to the Spruce GL through the auto-post workflow.

File-based (CSV upload): AR data is exported from the ERP and uploaded to Drypowder manually through the Integration page. GL posting is done by downloading a CSV from Drypowder and uploading it to the ERP.

Your integration mode is configured during onboarding. You can check which mode your dealership uses on the Integration page.

What syncs from Spruce to Drypowder

For Spruce-integrated dealers, the following data flows into Drypowder in real time:

DataDescriptionUsed in
Customer accountsAccount name, number, type, status, contactsCustomers Dashboard
Open invoicesInvoice number, date, due date, amount, balance, status, jobCustomers Dashboard, Payments portal
Credit adjustmentsCredits, discounts, write-offsCustomer detail, Payments portal
Debit adjustmentsAdditional charges, correctionsCustomer detail, Payments portal
StatementsStatement balance, discount date, due date, and the items rolled into the statementCurrent Statement view in the Payments portal

When any of these change in Spruce, the change appears in Drypowder in real time. There is no polling interval or overnight batch.

What posts from Drypowder to Spruce

Settled payments are posted to the Spruce GL through the settlement workflow:

DataDescriptionWhen
Invoice postingsPayment amounts applied to specific invoicesWhen an operator runs auto-post on a settlement
Credit adjustment postingsCredits applied with paymentsSame
Debit adjustment postingsDebits applied with paymentsSame
Statement discountThe discount amount when a customer pays a full statement by the discount dateSame, on statement payments

This post-back closes the loop. When a customer pays through the Payments portal, the payment is eventually recorded in the Spruce GL so the customer's balance in the ERP reflects the payment.

Note that GL posting is not fully automatic; it requires an AR operator to run the posting wizard on each settlement. The integration handles the data transfer, but the operator initiates it.

File-based integration

For dealers not on direct Spruce integration, the workflow is:

Getting data in. Export AR data from your ERP as a CSV file, then upload it through the Integration page. Drypowder processes the file and populates customer accounts, invoices, and adjustments.

Getting data out. When a settlement is ready to post, download a CSV posting file from the Settlements tab and upload it to your ERP yourself.

Ingestion history. The Integration page shows a log of all file uploads, including timestamps and processing results. If a file fails to process, the log shows error details.

File-based integration means your data in Drypowder is only as current as your most recent upload. Daily uploads keep the Customers Dashboard and Collection Priority scores accurate.

Data freshness

For Spruce-integrated dealers, data is real-time. When an invoice is created in Spruce, it appears in Drypowder within seconds. When a customer opens the Payments portal, they see the same balance their dealer sees in the ERP at that moment.

For file-based dealers, data freshness depends on upload frequency. If you upload daily each morning, the data is current as of the previous business day's close.

What happens if the sync breaks

Integration issues are rare, but if connectivity between Drypowder and Spruce is interrupted:

  • Drypowder continues to work with the most recent data. Balances and invoices reflect the last successful sync.
  • Payments can still be submitted because the payment flow does not depend on a live Spruce connection at the moment of payment.
  • GL postings are queued and will process when connectivity is restored.
  • The sync resumes automatically. No manual intervention is required.

On this page