Grant-to-accounting integration.
A field guide

It's written for foundations and larger grantees running Fluxx, Foundant, SmartSimple or Submittable next to Sage Intacct, QuickBooks, NetSuite, Financial Edge NXT or Zoho Books.

Most broken integrations we're asked to fix share one cause: both systems were allowed to own the same fact. Sound familiar? The grants team edits a payment date, finance edits the bill, and nobody knows which is right. Draw the line once, in writing, before anyone builds a connector.

That last row matters. When funders ask for spend and outcomes in one report, join them at reporting time; don't copy outcome data into the ledger. If programme data is still in spreadsheets, our guide to what a nonprofit MIS should hold covers that side.

A $300,000 three-year grant can show as $300,000 awarded, $100,000 committed and $50,000 paid on the same day. All three are correct. They answer different questions, and each one belongs in a different place.

Funders. Under ASU 2018-08, a grant is conditional when the agreement has both "a barrier that must be overcome" and a right of return or release. The unconditional portion is generally expensed, with a grants payable, when approved and communicated. Conditional tranches are disclosed, not booked, until the barrier is met.

Grantees. The same test applies. An unconditional grant is revenue, held in net assets with donor restrictions if it's restricted by purpose or time. Cash received ahead of a condition is usually a refundable advance, a liability.

So the grants system needs a field the connector reads, not a note in a PDF: each tranche marked conditional or unconditional, and an event fired when someone with authority marks the condition met.

Multi-year grants

Multi-year awards break integrations two ways. Amendments change the schedule in the grants system but not the PO or bill already in the GL. And multi-year unconditional promises may need to be recorded at present value. Agree the policy with your auditor, then make the connector carry it.

Restricted funds. Releasing net assets with donor restrictions, when a purpose or time restriction is met, is a GL event. If the grants system shows spend against a restricted grant, it should read that from the GL, not compute its own.

Budget vs actual. The approved budget is a grants-system fact; actuals are GL facts. Push the approved budget into the GL's budget module by the same grant and line dimensions, and run budget-vs-actual there. Federal grantees will recognise this. 2 CFR 200.302(b)(5) requires "comparison of expenditures with budget amounts for each Federal award", and (b)(3) requires records that identify "the amount, source, and expenditure" of federal funds.

Reconciliation. Monthly, per grant, match what the grants system says was paid, what the GL says was paid, and what the bank shows. Differences go to an exceptions list with an owner. At one large fundraising nonprofit we worked with, staff re-uploaded donation batches into the donor system, then reconciled the bank against those uploads by hand. The data wasn't the problem. Nobody owned the match.

Events, not tables

Don't sync whole tables on a timer. Sync the six events that change money:

The Armanino Fluxx–Sage Intacct pack follows this shape: grantees become Intacct vendors, approved grants become purchase orders, and payment details flow back.

IDs, mapping, frequency and errors

• IDs. Every record that crosses carries the grants system's ID in a GL field, backed by a cross-reference table. Never match on name.
• Mapping. Map to GL dimensions (grant, fund/restriction, programme, function, location). QuickBooks Online uses classes and locations, Sage Intacct and NetSuite use dimensions or segments, and Zoho Books uses reporting tags (up to 10, 500 options each).
• Frequency. Payments and approvals daily or faster; budgets on change; reconciliation monthly. Fluxx's BILL integration syncs every five minutes, but most foundations don't need faster than daily.
• Errors. Failed events go to a log with payload, retry rule and named owner. Silent failure is how an approved grant never gets paid.

When we build on Zoho, the grants workflow (applications, approvals, tranches, conditions, reporting calendar) runs as a Zoho Creator grants app and the ledger stays in Zoho Books. FundZola, our fund accounting product, tags expenses to grant, programme head and cost centre, checks overhead against each funder's ceiling, and builds utilisation reports from the same records. A person approves before anything posts.

When isn't Zoho the answer? If you're a US foundation on Sage Intacct with dimensions working, keep Intacct and fix the connector. If you're a federal-heavy grantee with indirect cost rates and Single Audit exposure, use a ledger your auditor already knows. Zoho fits when the grants side must bend to how your programmes run, or an enterprise stack doesn't match your size. If you fund individuals, see our scholarship management guide for disbursement-level controls.

1. Two owners for one fact. Payment dates edited in both systems.
2. One GL account per grant. Hundreds of accounts, and no functional expense statement.
3. Conditional grants booked as payables. The board sees liabilities that don't exist yet.
4. Name-matching. "Asha Trust" and "ASHA Trust (Bengaluru)" become two vendors.
5. Amendments outside the connector. Extended in the grants system, never in the GL.
6. CRM treated as the grants system. A donor CRM shows pipeline, not obligations; see our nonprofit CRM comparison.
7. No audit trail on the connector. Every write needs a user, timestamp and before/after value.

1. Write the ownership table.
2. Give every grant an ID that exists in both systems.
3. Mark each tranche conditional or unconditional.
4. Agree recognition policy with your auditor.
5. Put grant, fund, programme and function in dimensions.
6. Load approved budgets into the GL by those dimensions.
7. Write down the journal each event creates.
8. Match organisations by ID, never by name.
9. Set sync frequency and an error owner per event.
10. Define the amendment workflow.
11. Reconcile three ways, per grant, monthly.
12. Test closeout and refunds before go-live.