A church treasurer once described her job as “knowing where the money went after it landed.” That is a precise way to put it, and it points at a confusion that trips up a lot of small churches shopping for software: moving money and recording money are two different jobs, done by two different kinds of tool, and no amount of marketing copy makes one of them do the other.
Online giving processing is about the moment a gift changes hands — a card is charged, a bank account is debited, the money lands somewhere. Recording giving is about everything that happens next: who gave what, when, toward which fund, and what that adds up to by the time someone needs a report. Confusing the two leads churches either to overpay for payment features they will barely use, or to assume a records system can take a gift it was never built to touch.
What a payment processor is actually licensed to do
A payment processor sits between a giver’s card or bank account and your church’s bank account. It is regulated, it carries compliance burdens most church software does not, and it exists to move a specific dollar amount from one place to another safely. Stripe, PayPal Giving, a denomination’s hosted giving page, a bank’s ACH product — these are the tools doing that job.
This is a narrow, serious responsibility, and it is why processors charge a transaction fee: they are underwriting risk, handling card networks, and keeping your church out of the business of storing card numbers. A tool that does not do any of that — that has no bank integration, no card vault, no way to initiate a transfer — is not a processor, and it should not claim to be one.
What a records system is actually built to do
A records system, by contrast, does not care how the money arrived. A check placed in the plate, cash counted by two ushers, a wire from a processor’s weekly deposit — to a records system, all three are just a contribution that needs to be logged against the right person, on the right date, toward the right fund. Its job is to hold the ledger: who gave what, edited when a mistake is caught, deleted when a duplicate entry slips in, and rolled up into trends and statements when someone needs the full picture.
This is the piece that most small-church software conversations skip past, because it is less exciting than “accept online gifts,” but it is the piece a volunteer treasurer actually lives in every week. If you want a fuller sense of what that habit looks like day to day, tracking giving in a way that respects the giver walks through the recording side in more detail.
Why the two rarely belong in the same product
There is a real temptation to want one login that does everything: take the gift and keep the books. In practice, the churches that try to buy both from one small vendor often end up with a processor that is mediocre at moving money and a ledger that is mediocre at reporting on it, because building either one well is a full-time job for a software team, let alone both.
The more common — and more resilient — pattern is a specialized processor for the transaction, paired with a separate system of record for everything the transaction produces. The processor deposits money weekly or monthly; a person enters that deposit, and every other gift the church received, into the records system; the two get reconciled against each other on a schedule. It is two tools, but it is one clean division of labor: money moves in one place, the truth about it lives in another.
What SundayBridge is, and is not, in this picture
SundayBridge is the records side of that pairing, and only the records side. It lets you record, edit, and delete a contribution; set giving goals; watch trends across a fund or a household; and generate a year-end statement that is ready to print, whether the gift came in as cash, a check, or a processor’s deposit. It does not process a card, hold a bank connection, or move a single dollar — if your church wants to accept gifts online, that is a separate, dedicated tool, and SundayBridge is not trying to be one.
For a look at how the recording side connects to the rest of a church’s admin work — not just giving, but people, follow-up, and serving — choosing church management software covers the broader decision a small church faces before it commits to any single tool.
The order most churches actually get this right in
A church of 80 people rarely needs online giving before it needs a reliable ledger. The more common early failure is not “we can’t accept a card” — it is “we can’t tell you what Linda gave last year without digging through a shoebox.” That is a records problem, and it is usually the cheaper, faster one to fix. A church that has been running giving off a spreadsheet, or a mix of a paper ledger and somebody’s memory, tends to feel this most acutely at year-end statement time, and it is worth reading how that transition usually goes in moving a church off spreadsheets.
Online giving becomes the more pressing need once people are already asking for it — a member traveling for work who wants to keep giving consistently, a younger family whose entire financial life is digital and who simply forgets to bring a check. That is a real, common pressure, and it is worth solving with a processor built for exactly that job. But it is a different purchase, made at a different point in a church’s life, than the decision to finally get giving records out of a shoebox and into something searchable.
Reconciling the two without adding a second job
The friction people worry about — “won’t two systems mean double entry” — is real but manageable. A processor’s weekly deposit report is usually a single line per giver, or a batch total with a downloadable detail file. Entering that into a records system is a five- or ten-minute task once a week for most congregations this size, not a second full-time role. The trade is small compared to the alternative: a single vendor that half does both jobs, and does neither one well enough to trust at tax time.
Once giving is landing reliably in a records system, whichever way it arrived, the payoff shows up in the reporting a treasurer or finance committee actually needs — not just a total, but a trend. If your church has never looked closely at what a quarter-over-quarter giving pattern can tell you, reading giving trends is a good next read once the recording habit is solid.
A short way to decide which problem you actually have
Ask which sentence is closer to true right now. “We have givers who want to give online and currently can’t” points to a processor gap. “We have gifts coming in fine, but nobody can tell you what they add up to without a week of digging” points to a records gap. Most churches, if they are honest, have more urgency on the second sentence than the first — the plate has been filling for years; the ledger is what has quietly fallen behind.