How do I import credit card transactions into Church Windows Accounting?

How does card spend get into Church Windows Accounting?

Church Windows Accounting publishes no public API, and it typically runs on-premise on the church's own computer — so there is no card platform that can post transactions into it directly. Card spend enters the books the way any transaction does: entered in the program, or imported from a structured file. For a church where a handful of staff and ministry leaders carry cards, that has traditionally meant a monthly pile of receipts and a long data-entry session.

What makes the raw card statement a poor import?

The statement export from a card provider knows nothing about fund accounting. It carries the provider's dates and columns and merchant strings — and no fund, no account, no ministry designation. The bookkeeper still has to allocate every line, so importing a raw statement mostly relocates the typing rather than removing it. Worse, allocation happens weeks after the spend, when nobody remembers what the transaction at the hardware store was for.

What does the Vergo routine look like?

Vergo moves the allocation to the moment of spend and delivers a file in the shape Church Windows expects:

• Staff and ministry leaders spend on Vergo cards and snap the receipt at purchase; the transaction is coded to its fund and account while the context is fresh.
• The bookkeeper or treasurer reviews and approves transactions in Vergo through the month.
• At close, they download a custom-built CSV export matched to Church Windows' import format on the office computer.
• Import the file, reconcile the card account, close the month.

Is this dependable enough for a church's books?

Yes — because nothing exotic is happening. Church Windows' import works the way it always has; what changes is that the file arriving is complete and correctly shaped every time, with fund and account coding already on each line and the receipt for every transaction stored in Vergo for the finance committee or an audit. No API is involved because none exists; this is the working path, stated honestly.

What does getting started look like?

Setup is modest: issue Vergo cards to the staff and ministry leaders who spend, mirror the church's funds and accounts in Vergo so coding matches the chart, and run one test import into Church Windows to confirm the file lands as expected. After that the month has a rhythm — approve, download, import, reconcile — and the treasurer's report stops depending on whose receipts made it to the office. Questions from the finance committee are answered from Vergo's record rather than from memory.