Connecting Sage Intacct to MinistryStats

Preview — launching soon. The Sage Intacct integration isn't live in your account yet. This guide shows how it will work so you can plan ahead. The final screens may differ slightly, and we'll confirm the exact steps at launch.

If your church keeps its books in Sage Intacct, this integration brings your weekly giving totals straight onto your MinistryStats finance dashboard — reconciled from your actual accounting records, automatically, so your giving numbers match your books.

What you get

Pulls in: your weekly giving totals, reconciled from your Intacct general ledger, onto your finance dashboard.

Doesn't touch: MinistryStats only reads from Intacct. It cannot write, change, or delete anything in your accounting records — this is guaranteed by how the integration is built, not just by policy. (More on that in Your data is safe below.)

Before you start

• You need an Admin or Owner role in MinistryStats.
• The giving/finance module is off by default. An admin turns it on and grants access before this integration is available.
• You'll need a set of read-only Intacct credentials for a Web Services user — we strongly recommend a dedicated, least-privilege, read-only user rather than a full-access login. At launch we'll give you the exact list and a short "how to create the read-only user in Intacct" walkthrough.
• This connection is read-only, always.

Connect it (preview — steps will be finalized at launch)

1. Sign in to MinistryStats as an Admin or Owner.
2. Go to Settings → Integrations and find the Sage Intacct card.
3. Enter your Intacct Web Services credentials (Sender ID, Sender password, Company ID, User ID, and User password).
4. MinistryStats runs a read-only test query against Intacct to confirm the credentials work before saving anything — nothing is stored unless the test succeeds.
5. Once connected, the card confirms your Intacct company is linked.

Because this is a preview, the exact field labels and layout above may change. We'll update this guide and confirm the steps with you when Intacct goes live.

Using it (preview)

• At launch, you'll run giving syncs manually with a Sync now button — you stay in control of when your books are read.
• Automatic scheduled syncing is planned for a later release; it will not be on by default at launch.
• Reconciled giving totals land on your existing finance dashboard — there's no separate screen to learn.

What it does and doesn't do

• Does: read your giving lines from the Intacct general ledger and reconcile them into your weekly giving totals on the finance dashboard.
• Doesn't: write anything to Intacct — ever. It also doesn't pull anything beyond the giving accounts you've mapped.

Disconnecting

You'll be able to disconnect from the Sage Intacct card at any time. Future syncs stop; totals already on your dashboard stay.

If something looks wrong

• Credentials rejected — confirm you're using the read-only Web Services user and that all five values are correct. Nothing is saved unless the read-only test passes.
• Totals look off — the giving accounts and mapping are configured per church during setup; contact us and we'll check the mapping with you.
• Questions before launch? Email support at ken@ministrystats.com and we'll tell you where Intacct is in the rollout.

Your data is safe

Sage Intacct holds your church's real, live financial books, so this is the most carefully guarded integration we build. It is read-only by construction — the software has no ability to write to Intacct at all. This isn't a setting we promise not to flip; there is simply no write path in the code:

• The only Intacct operations the software can perform are on a fixed, hardcoded read-only list — anything else is rejected before it ever reaches Intacct.
• There are no create, update, or delete functions in the Intacct client — a write is impossible, not merely blocked.
• We recommend (and document) a least-privilege, read-only Intacct user, so even the credentials you give us can't change anything.
• Your credentials are stored securely on the server, in your own church's database — never in your browser after entry, never in our logs (passwords are redacted). The integration is admin-only and off by default.

Multiple independent layers, each of which would stop a write on its own. That's deliberate: your books are the one thing we will never risk.