Why is card spend hard to get into Enertia?
Enertia publishes no public API, so card platforms cannot push transactions into it directly. For upstream operators, that means the card statement lands on accounting's desk at month end as a wall of uncoded lines — supply house charges, fuel, parts, services — each needing an allocation and an account before it can be entered into Enertia.
What are the two ways to do it?
Manual: reconcile the statement, chase receipts, determine each charge's allocation, and key the batch into Enertia. Automated: use a card platform that captures coding at the point of purchase and produces a file matched to Enertia's import format, reducing the whole exercise to a review and a file load. Since there is no API, both routes end in Enertia's import capability — the difference is who does the coding, and when.
How does the Vergo-to-Enertia import work?
Vergo issues the cards and captures data at the swipe. The cardholder — a pumper, foreman, or office admin — snaps the receipt and codes the purchase against your Enertia account structure while the context is fresh. Accounting reviews the coded transactions in Vergo, then exports a custom-built CSV matched to the import format Enertia expects and loads it.
What is the step-by-step?
1. Field and office staff make purchases on Vergo cards.
2. At purchase, the cardholder attaches the receipt and codes the charge to the right account and allocation in your Enertia structure.
3. Accounting reviews and approves transactions in Vergo.
4. Export approved transactions as a CSV built for Enertia's import format.
5. Import the file into Enertia and reconcile against the card statement.
What changes at month end?
The keying session disappears. Transactions arrive in Enertia coded and documented, receipts are already attached in Vergo, and close time goes to review rather than data entry. Whether you run Enertia in the cloud or on-premise, the import is the same file load.
What does clean import data mean for upstream reporting?
Everything downstream of the GL depends on the allocation being right when the transaction lands. Charges coded correctly at purchase flow into accurate property-level costs, which keeps operating statements and partner billing defensible. The reverse — a statement coded from memory at month end — produces the reallocation churn every upstream accountant knows. Moving the coding to the swipe, with the receipt attached and a review step before export, is what makes the file import into Enertia not just faster but more accurate than the manual routine it replaces.
Can a card feed connect directly to Enertia?
No. Enertia publishes no public API, so there is no live card feed. Transactions enter Enertia by manual entry or file import.
What file does Vergo generate for Enertia?
A custom-built CSV export matched to the import format Enertia expects, generated from transactions already coded and approved in Vergo.
Who does the coding?
The cardholder, at the point of purchase, against your Enertia account structure — with accounting review in Vergo before anything is exported.
Does deployment matter?
No. Enertia runs cloud or on-premise; the file-based import works identically in both.
