A nonprofit's hardest accounting question is not what was spent — it is which pot it came out of, and whether the funder would agree. Accounting Seed puts the general ledger, fund separation, grant and program budgets and financial reporting on the Salesforce platform, alongside the donor, grant and program records your team already works in. Twopir Consulting designs the fund architecture, configures it around your award terms, and builds the logic when configuration runs out. One ledger, from gift to grant report.
All four figures are from a single documented Accounting Seed engagement with a 150-employee US organization — not a blended average, and not a nonprofit sector benchmark. Read the full case study.
Twopir Consulting has delivered Salesforce and finance systems for 500+ organizations across 12+ years — including mission-driven organizations running funds, grants and the general ledger on one platform.
Systems We Build On
A nonprofit's financial problems are rarely accounting problems. They are separation problems — the gift is recorded where fundraising works, the restriction is recorded in a spreadsheet, and the spend is recorded in a third place. Every gap below is one of those separations breaking down, and each one costs staff time or funder trust.
Fund balances are maintained outside the ledger, so the restricted position is a reconstruction rather than a report. The organization carries real exposure on a file one person maintains.
The award budget sits in the proposal, the spend sits in the general ledger, and the comparison is rebuilt by hand before every funder report. Overspend is discovered after the period it happened in.
Fundraising reports one total, finance reports another, and the difference is pledges, timing and refunds nobody has time to unpick. The board is shown whichever number was ready first.
Splitting salaries and shared costs across program, management and fundraising is a quarterly workbook exercise. The allocation basis is defensible, but only because one person remembers it.
Every schedule the auditor asks for is assembled from exports, and the same schedules are rebuilt the following year. Audit season consumes a finance team that is already too small.
Direct cost, allocated cost and restricted revenue by program, site and funder require a rebuild each quarter. Programme decisions get made on a number that is already out of date.
Accounting Seed is an accounting platform built natively on the Salesforce platform. It provides general ledger, accounts receivable, accounts payable, billing and invoicing, project accounting, financial reporting and online payment processing, with support for multiple ledgers and a multi-dimensional chart of accounts — and because it is native rather than integrated, the organization's financial records sit on the same platform as its donor, grant and program records. It has been listed on the Salesforce AppExchange for over a decade and is used by finance teams in more than 30 countries.
For a nonprofit the practical consequence is specific: there is no nightly sync to reconcile between the fundraising database and the ledger, and no second definition of a constituent to keep in step. Fund accounting is not a switch on the product — it comes from how ledgers, sub-accounts and reporting dimensions are structured for your restrictions and awards, which is the design work this page is about. Accounting Seed does not publish public pricing; licensing is quoted per organization by the vendor. Accounting Seed's own product documentation covers the product surface; this page covers what we build with it.
The platform's own capability. None of this is something Twopir built — it ships with the product.
The service. We design the fund architecture, then implement, configure and extend the product to match it.
The operating change. This is what a finance director and a board actually notice in the first two quarters.
"We work with Accounting Seed" hides the only question that matters to a buyer: which of these do you actually need? Twopir Consulting offers all four, and the boundary between configuration and custom development is stated below rather than discovered halfway through a project.
| Engagement | What it covers | Where the boundary sits |
|---|---|---|
| Implement | Standing the product up: ledger and fund structure, chart of accounts, entity setup, users and permissions, opening balances, and migration of historical AR, AP and fund positions."Accounting Seed implementation partner" | Ends when the organization can run a full month and close a period on the new ledger. Everything here is standard product setup — no custom code is involved. |
| Configure | Shaping the product to your awards: fund and net-asset structure, grant budgets and periods, program and site dimensions, allocation bases, approval routing, funder report layouts, dashboards."Accounting Seed fund accounting configuration" | Declarative only — Flow, formula fields, page layouts, permission sets and native settings. If it can be built without Apex, it belongs in this tier and it stays upgrade-safe. |
| Build on | Custom development where the configuration surface runs out: automated functional expense allocation, indirect cost recovery calculations, multi-year award tracking, bespoke funder report formats, gift and payroll system APIs."custom Accounting Seed development" | Starts the moment a requirement needs Apex, Lightning Web Components or an API integration. We write it as tested, bulk-safe code against the product's supported objects, never by modifying the managed package. |
| Rescue | Fixing an existing deployment: unwinding workarounds, correcting fund and ledger structure, repairing broken integrations, and rebuilding reporting the board stopped trusting."Accounting Seed implementation not working" | Begins with an assessment, not a rebuild. Most of what's wrong is architecture, not the product — we keep the org wherever the data and structure can be corrected in place. |
Most organizations need two of the four. The purpose of discovery is to tell you which two before you commit restricted or unrestricted budget to the wrong one.
These are the modules we actually deliver on Accounting Seed for mission-driven organizations — described in fund and grant vocabulary rather than as a restatement of the vendor's feature list. Which of them you need is a discovery question, not a package.
Restricted, temporarily restricted and unrestricted balances held in separated ledgers with sub-accounts by fund, so the restricted position is a report rather than a reconstruction.
Award budgets loaded against the period and the funder they belong to, with actual spend posting to the same structure so budget-versus-actual is live rather than assembled.
Salaries and shared costs split across program, management and general, and fundraising by a documented basis that runs as automation, with the basis itself stored rather than remembered.
Cost and revenue by program, site, funder and cost centre reported from ledger dimensions agreed up front, so a new program does not require a new spreadsheet.
Recovery calculated against each award's own negotiated rate and base, posted as a real transaction rather than added as a note at the end of the reporting period.
Online giving, pledges and payment processor settlements applied against the ledger so fundraising and finance report one reconciled total instead of two defensible ones.
Vendor bills, payroll journals and subrecipient payments recorded against the fund and award that carry them, so allowability questions are answered from the record.
Statement of activities, statement of financial position, fund balance and functional expense schedules produced from the ledger — the same schedules an auditor asks for, ready before they ask.
A nonprofit's finance stack is only as good as its weakest handoff. This is the integration surface we build around Accounting Seed in nonprofit engagements — and the one relationship on the list that needs no integration at all.
| Systems | Business purpose | What moves, and which way |
|---|---|---|
| Salesforce · Accounting Seed | Keep the constituent, the grant and the money on one record so fundraising and finance argue about strategy rather than about whose total is right. | No integration Native — same platform, same database. Accounts, contacts and grant records are shared objects, not synchronised copies. Nothing to reconcile and no middleware to maintain. |
| Nonprofit Cloud · NPSP | Turn recorded gifts, pledges and awards into ledger entries without re-keying, for organizations already running Salesforce for fundraising. | Fundraising → ledger Gifts, pledge schedules and award records create receivables and fund entries; posted and reconciled status returns to the record. Consumed by finance and development. Built per organization — the mapping is the work. |
| Online giving platforms | Have donations land against the right fund and campaign without a monthly import-and-match exercise. | Gifts → ledger Transactions and settlement detail post to cash receipts against the designated fund. Consumed by finance, with the acknowledgement still owned by development. |
| Chargent · payment gateways | Take card and ACH gifts and program payments inside Salesforce and apply them to the right invoice or fund automatically. | Payments → ledger Authorisations and settlements post to the invoice and cash receipt. Consumed by finance. |
| Payroll & timesheets | Get salary cost onto the right program and award, which is where most functional expense allocation actually goes wrong. | Payroll → ledger Payroll journals and allocated time post against program, fund and award dimensions. Consumed by finance and program leads. Built per organization. |
| QuickBooks · incumbent ledger | Serve organizations running Accounting Seed alongside an incumbent system during a phased move, or keeping a separate entity's books. | Bi-directional Journal summaries and vendor bills move both ways on an agreed cut. Consumed by group finance. Built per organization — the mapping is the work, not the connector. |
Building one of these into an existing Salesforce org? See our Salesforce integration practice, or the wider Salesforce practice this sits inside.
Most failed accounting implementations are configuration exercises that skipped the architecture. We do the fund and dimension design before anyone opens a setup screen — because a chart of accounts is very expensive to change once a year of restricted transactions sits on top of it.
We map how the organization is actually funded and how it spends: restriction types in use, award terms and reporting dates, program and site structure, allocation bases, the close calendar, and which schedules the board and auditor genuinely need. Output is an architecture, not a task list. Typically 1–2 weeks.
Chart of accounts, ledger and fund structure, net asset classes, program and funder dimensions, and the allocation rules the organization will defend at audit — agreed with finance before a single object is configured. Typically 2–3 weeks.
Native configuration first — budgets, approval routing, funder report layouts, dashboards. Custom Apex and Lightning Web Components only where the requirement genuinely exceeds the configuration surface, written against supported objects so upgrades stay clean. Typically 4–8 weeks.
Opening balances, historical AR and AP and fund positions migrate and are reconciled line by line. The organization then runs a full month in both systems and the numbers must agree before anything is switched off. Typically 2–4 weeks.
We stay through the first period closes and the first funder reporting cycle, fix what real transaction volume exposes, and hand over to a finance team that can administer the system themselves rather than one that has to call us.
Durations are typical ranges for a single-entity organization and are confirmed in discovery. Multi-entity and multi-country structures run longer — see multi-entity and multi-currency consolidation — and a rescue engagement starts with an assessment before any timeline is quoted.
Both are published Twopir Consulting engagements delivered on Accounting Seed and Salesforce. Neither organization is a nonprofit — that is what the documented Accounting Seed evidence currently covers — and both turn on the same mechanics a funded organization needs: separated balances, automated allocation and reconciliation that stops being manual. Every figure is scoped to the organization it was measured at.
Twopir's specialized Salesforce customization enabled efficient integration of third-party systems and streamlined administration and billing, leading to seamless financial operations and enhanced productivity. Automated mass billing and matter management minimized errors across our entire legal workflow.
Client funds separated in the ledger and manual tracking eliminated with Accounting Seed and Salesforce — 17 automation modules delivered.
Twopir provided Salesforce customisation and integration services to help us build a robust, compliant, and scalable legal operations platform — connecting case management, document processing, and financial systems into one unified workflow. The result was transformative for how we run case-to-cash operations.
Streamlining intake-to-disbursement operations across Salesforce, AWS and QuickBooks.
Accounting Seed implementations fail in one of two directions: an accounting firm that cannot build on the Salesforce platform, or a Salesforce partner that has never closed a period. Fund accounting needs both, on the same team.
Ledgers, net asset classes and reporting dimensions are agreed with your finance team and, where it helps, your auditor first. It is the cheapest hour of the project and the most expensive one to skip.
Twopir Consulting delivers donor lifecycle, grants management and impact reporting on Salesforce. We know what the development team needs the gift record to do, which is what makes reconciling the two sides possible.
When a requirement exceeds native setup — an allocation rule, an indirect cost calculation, a funder report format — the same team writes the Apex. No second vendor and no handoff.
Go-live is not the finish line for a finance system. We are there for the first period closes and the first funder reporting cycle, when real volume finds what testing did not.
A large share of this work is rescue — organizations already on Accounting Seed whose fund structure was never right. We assess before we rebuild, and we keep what can be corrected in place.
Configuration is anything achievable declaratively — fund and ledger structure, grant budgets, program and funder dimensions, approval routing, Flow automation, reports and dashboards. Custom development starts when a requirement needs Apex, a Lightning Web Component or an API integration: automated functional expense allocation, indirect cost recovery calculations, multi-year award tracking, or a bespoke funder report format. We always exhaust the configuration surface first, because declarative work stays upgrade-safe and your team can maintain it without us.
Twopir Consulting is a Salesforce Partner and a HubSpot Partner, and we implement, configure and build on Accounting Seed for nonprofit organizations. Accounting Seed licences are bought from Accounting Seed directly — the vendor does not publish public pricing and quotes per organization. We deliver the implementation and the custom development around it; we are not reselling the product.
Yes, and the important detail is how. Accounting Seed supports multiple ledgers and a multi-dimensional chart of accounts, which is what allows restricted and unrestricted funds to be held separately with sub-accounts by fund, program and funder. Fund accounting is not a packaged module you enable — it comes from how those ledgers, sub-accounts, approval rules and reporting dimensions are structured for your restrictions and award terms. That structural design is the part we do, and it is where most fund accounting problems actually originate.
No. Nonprofit Cloud and NPSP hold the constituent, gift, pledge and program relationship; Accounting Seed holds the ledger. Because both run on the Salesforce platform they share the same account and contact records rather than syncing copies, so the reconciliation problem between a fundraising database and an accounting system largely goes away. What we build is the mapping: which gift and award events create ledger entries, how pledges are treated, and how posted status is reflected back to the development team.
It makes the schedules produceable rather than reconstructable, which is where most of the effort actually goes. When fund balances, functional expense allocation and program dimensions are held in the ledger, the statement of activities, fund balance schedules and functional expense analysis are reports rather than workbooks. It does not change what your auditor tests or what your Form 990 requires, and preparing the return remains your accountant's work — we make sure the numbers behind it come out of the system with an audit trail.
For a single-entity organization, the phases on this page typically run around three to four months end to end, including a parallel run before anything is switched off. Multi-entity and multi-country structures run longer, and the honest answer is that the timeline is set by two things we cannot see before discovery: the state of your historical data, and how many genuinely distinct restriction and award types are in use. We confirm the schedule after the architecture phase, not before it.
That is where a lot of these engagements start. A deployment can be technically live and still operationally wrong — usually because the fund structure, ledger separation or reporting dimensions were set up without a financial architecture behind them. We assess the ledger, the configuration, the integrations and the data before proposing anything, then correct in place wherever the structure can be repaired without a rebuild. Starting from a blank org is the last option, not the first.
Whether you are choosing Accounting Seed, midway through configuring it, or living with a deployment that never quite worked — the first conversation is about your restrictions and your award terms, not about software.
Fund accounting, grant tracking & board reporting on Salesforce
