What are your options for card spend in PowerChurch?
PowerChurch is on-premise software with no API — its staff have said plainly that no PowerChurch-specific API exists, and the read-only ODBC access to its FoxPro tables cannot post transactions in. That leaves two routes for church card activity: re-key each charge by hand from statements, or import a prepared file. For a church office where the bookkeeper may be part-time or a volunteer, re-keying a month of staff and ministry spending is exactly the kind of work worth eliminating.
How does the Vergo-to-PowerChurch workflow run?
1. Spend happens on Vergo cards. Staff, ministry leaders, and trusted volunteers each carry their own card, and every transaction is captured at the point of sale with a receipt prompt.
2. Transactions are coded in Vergo. Each charge is assigned to the right expense account — and the right fund, where your fund accounting requires it — while the purchaser still remembers what it was for. Rules automate the recurring spend.
3. Vergo generates the export. When your bookkeeper is ready to post, Vergo produces a custom-built CSV matched to the import format PowerChurch expects, structured so the file lands cleanly.
4. Your bookkeeper imports into PowerChurch. The file comes into the on-premise system for review and posting — already categorized, receipt-backed, and fund-aware.
Why does coding at the point of spend matter for fund accounting?
Because fund accounting is unforgiving of guesswork. A charge that surfaces on a statement weeks later, with no receipt and no memory of its purpose, gets parked in the wrong fund or a catch-all account — and unwinding that before an audit or finance-committee review is real work. Coding when the transaction happens keeps designated funds clean from the start, and the export carries that coding into PowerChurch.
How often should the import run?
The export covers any date range, so it fits your office's rhythm — weekly to keep fund balances current, or monthly as part of close before the finance committee meets. Either way, the bookkeeper's manual work is the import and a review pass; the gathering, coding, and formatting are already done.
What do you need before the first import?
Mirror your PowerChurch accounts — and funds, where designated giving requires it — in Vergo so coding rules assign spend the way your books expect, then run a short test export and confirm it imports cleanly. From there the routine is the same every period: spend, code, export, import, post. Vergo maintains the PowerChurch-matched export template, so keeping the format working is not another job for a part-time bookkeeper.
Can card transactions post into PowerChurch automatically?
No. PowerChurch staff confirm there is no PowerChurch-specific API, and its ODBC access is read-only. Card activity comes in by file import.
What file does Vergo produce for PowerChurch?
A custom-built CSV matched to the import format PowerChurch expects, with each transaction coded to accounts — and funds, where required — before export.
Does this work with fund accounting?
Yes. Transactions are coded to the right fund at the point of spend in Vergo, so designated funds stay clean instead of being reconstructed from statements.
Who runs the import, and how long does it take?
Your bookkeeper, in minutes, on whatever schedule fits — weekly for current fund balances or monthly at close. The upstream work is already done in Vergo.
