Why is importing card transactions into Spruce a manual job?
ECI Spruce does not publish a public API, so no card platform can push transactions into it directly. That leaves building materials dealers with the classic month-end routine: download the card statement, open a spreadsheet, retype or reshape each line, assign a GL account to each purchase, chase cardholders for receipts, and key or import the result into Spruce. Across a fleet of cards, that routine consumes real close time.
What are the options for getting card spend into Spruce?
There are two. The manual route: reconcile the statement by hand and enter transactions into Spruce yourself, coding each one as you go. Or the automated route: use a card platform that produces a file Spruce can import, so the coding happens upstream and the import is a single step. Because there is no API to build on, any honest automation for Spruce runs through file import.
How does the import work with Vergo?
Vergo issues the cards and captures everything at the point of purchase. When an employee buys materials or fuel, Vergo prompts them for the receipt and the coding — the GL account and any tracking fields your Spruce setup uses. Finance reviews the coded transactions in Vergo, then exports a custom-built CSV matched to the import format Spruce expects. Load that file into Spruce and the card spend is on the books, coded and documented.
What is the step-by-step?
1. Employees make purchases on Vergo cards; Vergo captures merchant, amount, and date automatically.
2. Cardholders snap the receipt and pick the coding from your imported chart of accounts.
3. Finance reviews and approves transactions in Vergo.
4. Export the approved transactions as a CSV built to Spruce's import format.
5. Import the file into Spruce and reconcile against the card statement.
How often should you run the import?
Whatever matches your close rhythm. Some dealers import weekly to keep the GL current; others run one import at month end. Because the file is generated from already-coded transactions, the import itself takes minutes either way.
What should the file contain before it reaches Spruce?
A clean import batch needs each transaction's date, merchant, amount, and GL coding, in the column layout Spruce's import expects. Building that by hand from a card statement is the part that eats time — and where transposition errors creep in. Because Vergo generates the file from transactions that were coded at purchase and reviewed by finance, the batch arrives complete: no blank coding cells to chase down, no columns to rearrange, and the receipt behind every line is one click away in Vergo if a question comes up during reconciliation.
Can I connect a credit card feed directly to ECI Spruce?
No. Spruce publishes no public API, so direct card feeds are not possible. Card spend enters Spruce through data entry or file import.
What file format does the Vergo export use for Spruce?
Vergo provides custom-built CSV exports matched to the import format Spruce expects, so the file loads without manual reshaping in a spreadsheet.
Who codes the transactions before import?
Cardholders code purchases in Vergo at the point of sale, and finance reviews before export — so the file arrives in Spruce already coded to your GL accounts.
How long does the import take?
Minutes. The time-consuming parts — coding, receipts, review — happen continuously in Vergo, so the Spruce import is a single file load on your close schedule.
