StewaraCount
Gifts land in an open batch with donor, fund, and method, including online giving through the church’s own Stripe account.
- Batch gift entry
- Multiple funds
- Online giving, church-owned
The batch on the table and the entry in the books are the same act, not two jobs.
Giving · Offering
Sunday, before anyone types it twice.
Giving · Offering
Sunday's gifts, already in the books.
Count once in open batches, lock when it's clean, and totals post into Stewara Treasury, not a CSV you re-key into another accounting app. Members only ever see their own giving; year-end statements go out in one click.
Often replaces a separate online giving platform, and the CSV you export from it every month.
No credit card to start · 30-day trial of every module in the suite except Stewara Assistant. · See pricing
- 1Open, then lock Count in an open batch; commit when it is clean.
- 2Fund detail Restricted gifts stay on the fund they were given to.
- 3Private by role Members never see another person’s giving.
What Offering is, and what it isn’t.
Offering records church contributions once, keeps donor and fund detail, and produces giving statements from that same record. Locked batches can post into Stewara Treasury by fund, in integer cents, so Sunday is not re-typed into another accounting app. Members only ever see their own giving. Card processing is Stripe’s, at the nonprofit rate Stripe grants your 501(c)(3); Stewara adds no markup either way.
See it in action
A short, real walkthrough of Offering in Stewara. No sign-up required to watch.
Sunday, counted once
Capture, lock, post, then acknowledge — without a second set of books.
- After the last service
Record the gift in the batch
Pick the donor, fund, and method inside an open batch, as fast as a Sunday-afternoon count needs to be. Cash, check, and online gifts share the same trail.
- When it locks
The count becomes the record
Commit the batch once it is counted. Totals can post into Treasury by fund through a one-way bridge. There is no silent delete, only a tracked void.
- January
Statements without overtime
Year-end statements email to every donor with an address on file, in one click. Analytics already moved when the batch locked, so January is not a rebuild.
Count Sunday once.
Start your 30-day trialWhat it does, grouped by the job.
Lock
The batch commits once it is counted. The trail is timestamped, and a void is tracked rather than quietly deleted.
- Open then committed lock
- Tracked voids, never silent deletes
- Integer-cent totals
Post to the books
A one-way bridge carries locked batches into Stewara Treasury by fund, so the treasurer is not re-keying a CSV.
- One-way Treasury bridge
- Post by fund
- No CSV re-key
Keep giving private
Only admin, pastor, treasurer, and bookkeeper see church-wide giving. Members only ever see their own history.
- Role-gated church totals
- Members see only their own
- One-click year-end statements
Also includedEvery Offering feature, in one list
- Online giving through your church's own Stripe account: funds settle directly to your bank; the nonprofit rate Stripe grants your 501(c)(3), zero Stewara markup
- Batch-based gift entry with open/committed lock workflow
- Multiple funds (General, Missions, Building & more) with tax-deductible flag
- Void with a full audit trail, never a silent delete
- Giving analytics: YTD totals, monthly trend, fund breakdown, top donors
- One-click year-end statements, emailed to donors
- Per-role access: view (admin/pastor/treasurer/bookkeeper), edit, manage
- Members see only their own giving, always
- One-way bridge to Stewara Treasury for full fund accounting
- Integer-cent accounting: no floating-point rounding errors
For switchers
If you're on Planning Center Giving
- UsuallyGifts live in the church app; the books live somewhere else. A CSV moves between them every week.With StewaraLocked batches post into Stewara Treasury by fund. Members only see their own giving. Statements go out in one click.
Next, make sure Sunday's gifts land in a real ledger.
The objections, answered here.
Do you take a cut of our giving?
No. Card processing is Stripe’s and that money goes to the card networks. Stewara adds no markup at any rate. Stripe discounts its rate for registered nonprofits: you apply to Stripe with your 501(c)(3) determination letter, and Stripe decides, not us. A church that has held its status for years clears it easily. A plant still waiting on the IRS starts on Stripe’s standard rate and moves over when the letter arrives. Software is a flat church bill on Pricing, never a percent of the offering.
What happens in the books?
Locked batches can post into Stewara Treasury by fund through a one-way bridge. Offering stays the gift record; Treasury is the ledger. Nothing is re-typed from a CSV.
Can a bookkeeper see pastoral notes?
Giving access is its own role set. A treasurer or bookkeeper can work church-wide giving without the door to pastoral care opening at the same time.
How do year-end statements go out?
One click emails statements to donors with an address on file. Members can also see their own giving history any day of the year, never anyone else’s.
Included in the Stewara plan, and every plan above it.
Count Sunday once.
Lock the batch and let the books take it from there. Start your 30-day trial today: every module in the suite except Stewara Assistant, no card required.