Restricted Fund Tracking in QuickBooks and Xero

For restricted fund tracking in QuickBooks and Xero, the cleanest pattern is usually to use reporting dimensions, not a separate expense account for every fund. In QuickBooks Online, that often means Classes plus Customers/Donors or Projects when a grant needs its own trail. In Xero, it usually means one tracking category for fund, donor, or project and a second tracking category for program or activity when both dimensions are needed.

The reason is simple: restricted-fund reporting is made or broken at the supplier-bill line. If a bill for rent, software, catering, or consultant time is posted without the right Class, project, donor, fund, program, or tracking option, the month-end report will not fix itself. The accounting file may still balance, but the restricted-fund report will have unassigned costs, mixed grant activity, or unrestricted spending pulled into the wrong column.

US nonprofit reporting also uses specific language. FASB ASU 2016-14 net asset guidance distinguishes contributions with donor-imposed restrictions from those without donor-imposed restrictions, reported as net assets with donor restrictions or net assets without donor restrictions. Many bookkeepers still hear the older terms "temporarily restricted" and "permanently restricted", especially in inherited charts of accounts, board reports, and older procedures. The practical software question is the same: which bill lines belong to restricted activity, and which do not?

This is not a full nonprofit accounting standards guide or a buyer's guide to fund-accounting software. It is an operating model for coding supplier invoices in QuickBooks Online and Xero so restricted, unrestricted, grant, project, program, and functional reporting can be checked before the bill reaches the ledger.

Do not make one field carry every nonprofit dimension

Small nonprofits get into trouble when one field is asked to answer every reporting question. A restricted fund answers, "Was this money limited by the donor?" A program or functional category answers, "What activity did the cost support?" A grant or project answers, "Which award or deliverable should this cost be charged to?" A department or location answers an internal management question. Those are related, but they are not interchangeable.

That is why creating a separate expense account for every restriction is usually a weak design. If "Office Supplies" becomes "Office Supplies Restricted", "Office Supplies Grant A", "Office Supplies Grant B", and "Office Supplies Unrestricted", the chart of accounts starts carrying reporting detail that belongs in dimensions. The result is a longer account list, less comparable expense reporting, and more cleanup when one supplier bill needs to be split across more than one restriction.

Keep donor restrictions separate from board-designated or management-designated money. A donor-restricted grant or appeal has an external restriction. A board-designated reserve is internally earmarked, even if the board treats it seriously. UK charity teams will also distinguish restricted, designated, and unrestricted funds; the same terminology discipline matters when applying UK charity supplier invoice coding under SORP 2026, while the focus here stays on the QBO and Xero bill-coding mechanics.

Functional expense reporting is a separate layer. A bill line might belong to a restricted grant and also be part of program service, management and general, or fundraising. If the organization reports US functional expenses, Form 990 functional expense allocation from supplier invoices is the next workflow to solve. Do not hide functional expense categories inside the same field that is supposed to prove donor restriction.

Before touching Classes or tracking categories, write down the dimensions that must appear on each supplier-bill line. For many organizations, that list is account code, fund or restriction, program or function, donor/grant/project where relevant, and location only if location is a real reporting axis. The software setup should serve that list, not the other way around.

QuickBooks Online setup for restricted grants and supplier bills

In QuickBooks Online, Classes are often the first place nonprofit bookkeepers look for restricted fund tracking. That can work well when the organization wants a Profit and Loss by Class for funds such as General, Building, Missions, Grant A, or Grant B. The setup becomes harder when Classes also need to represent program service, management and general, fundraising, or departments.

Confirm the subscription and settings before building the process around Classes. Current QuickBooks guidance puts class tracking in QuickBooks Online Plus and Advanced, and the file can be set to assign one Class to the entire transaction or one Class to each row. Restricted supplier bills usually need the row-level setting if one invoice can touch more than one fund, program, or grant.

The decision is not "Class or no Class." It is what the Class means. If Classes represent restricted funds, then a grant-funded office-supplies line and an unrestricted office-supplies line can use the same expense account while reporting in different fund columns. If Classes represent functional expense categories, then the restricted grant detail may need to live somewhere else, such as Customer/Donor or Project, so the same cost can still be connected to the award.

Customers, Donors, and Projects are useful when a nonprofit needs a trail by grant, funder, or project while preserving Classes for another reporting axis. This is common for organizations that need both fund reporting and program or functional reporting. A bill line might carry an expense account, a Class for program/function, and a Customer/Project for the restricted grant. The exact pattern depends on the reports the treasurer, accountant, board, and grantor actually review.

Locations should be reserved for real location reporting. If the nonprofit runs sites, branches, campuses, or regional operations, Location can be meaningful. If it is only being used because another field is already occupied, it can confuse future reports and make training harder for volunteers or outsourced bookkeepers.

For restricted supplier bills, line-level Class assignment matters more than the bill header. If a single invoice from one vendor includes expenses for two restricted grants, the bill should be split into separate lines with the correct amount, account code, and Class or project detail on each row. A header Class may be convenient for a bill that belongs entirely to one fund, but it is dangerous when the line detail tells a different story.

Custom Fields can support review notes, donor references, internal approvals, or grant identifiers, but they are not a substitute for the fields that drive P&L by Class or project reporting. If a field will be used to filter, compare, or produce board and grant reports, it needs to be part of the reporting structure, not only metadata typed onto the bill.

Xero setup when only two tracking categories can be active

Xero's equivalent design decision is tracking categories and tracking options. A category is the reporting dimension, such as Fund, Project, Donor, Activity, Program, Department, or Location. The options are the values inside that dimension, such as General Fund, Building Fund, Youth Program, Grant A, Grant B, or London Office.

The constraint is real: Xero allows four tracking categories in total, but only two can be active at a time. Xero also recommends keeping tracking options to no more than 100 per category so reports load properly. For a nonprofit or charity, that means the first design choice is not cosmetic. The two active categories must carry the reporting questions that matter most at bill-entry time.

A common charity pattern is Fund plus Activity. Fund separates restricted, designated, and unrestricted money. Activity separates program areas or operational work. Another pattern is Donor/Project plus Program, which works when grant reporting is more important than a broad fund column. Some organizations use Department plus Fund where internal departments own budgets and restricted-fund reporting is still required.

Avoid creating a tracking option for every small appeal, event, or short-lived restriction unless those options will genuinely be used in reports and entered consistently on bills. A tracking list that looks comprehensive on day one can become unusable by month six if closed projects stay active, old grants remain selectable, and bookkeepers cannot tell which option belongs to the invoice in front of them. Archive or clean up options when grants close, projects end, or naming conventions change.

As with QuickBooks, the tracking belongs on the bill lines when a supplier invoice is split. If one invoice includes unrestricted administration, a restricted program cost, and a donor-funded project cost, the line rows need their own tracking options. Header-level thinking is not enough.

Unassigned tracking is a control failure, not just a blank field. A Xero Profit and Loss filtered or compared by tracking category only works if the underlying bill lines carry the right options. If unassigned rows are allowed through, the report can understate restricted spending while the ledger still appears complete.

How to code supplier invoices that touch more than one fund

The simplest supplier bill belongs entirely to one restricted fund. In that case, each relevant line carries the normal expense account, the fund Class or tracking option, and any separate program, project, donor, or tax/VAT detail the organization uses. The expense account still says what was bought. The fund dimension says which restricted or unrestricted resource paid for it.

A split between two restricted grants needs separate bill lines, even if the vendor issued one invoice. If a consultant invoice covers work on Grant A and Grant B, the bill should be split by amount, account code, and grant or fund dimension. The line description should make the split reviewable later, especially if the grantor asks how the cost was allocated.

A split between restricted and unrestricted spending needs the same discipline. Do not let the unrestricted portion inherit the restricted Class or Xero tracking option because the first line was coded that way. The unrestricted row should carry the unrestricted fund or blank restriction treatment that matches the organization's reporting design, while the restricted row carries the donor-imposed restriction.

Shared overhead is slightly different because the supplier's invoice may not tell the whole accounting story. A broadband, rent, payroll-service, or insurance bill might be allocated across programs or functions using a board-approved or accountant-approved basis. The bill lines still need the correct fund and program coding, but the allocation basis should be documented outside the supplier's description if the invoice itself does not support it.

Recurring vendor bills deserve periodic review. A monthly software subscription, storage invoice, or facilities bill may start as unrestricted, then become partly grant-funded, or move from one program to another. Recurring templates reduce typing, but they also copy old coding mistakes with impressive consistency.

Month-end cleanup should focus on exceptions: missing Classes, unassigned tracking options, bill lines with project clues in the description but no project code, and invoices where the header suggests one fund while the line detail points elsewhere. For restricted-fund coding, the most expensive errors are usually ordinary bills that looked routine enough to skip review.

What the invoice import file should carry before posting

The review file should contain enough detail for a bookkeeper to approve the coding before anything is posted. At minimum, capture vendor, bill number, bill date, due date where available, line description, account code, amount, fund/Class/tracking option, program or functional category, donor/grant/project clue, PO or reference text, tax or VAT treatment where relevant, confidence flags, source file and page reference, and reviewer notes.

That file should not pretend to make the accounting judgment on its own. The extraction step can surface proposed coding columns and the evidence behind them, but the reviewer still approves the Class, tracking option, account code, tax treatment, and allocation basis. This distinction matters for restricted funds because an invoice may mention a project, donor, campaign, or location without proving how the cost should be recognized.

A reviewed spreadsheet gives the team a control point before import. Uncoded rows can be filtered. Split bills can be checked back to the invoice total. Project or grant clues can be reviewed against the source PDF. Rows with low confidence, missing tracking, or conflicting descriptions can be held back instead of creating month-end cleanup inside QuickBooks or Xero.

Invoice Data Extraction fits this control point when the nonprofit needs invoice data extraction for supplier bills into a structured review file. The product converts invoices and financial documents into Excel, CSV, or JSON outputs from a prompt, supports invoice-level and line-item extraction, and includes source file and page references so reviewers can cross-check rows against the original document. A prompt can ask for the coding columns the finance team wants to review, such as fund, Class, tracking option, program, donor, grant, project, account code, and notes, but the approved accounting treatment remains with the human reviewer.

For implementation detail after the review file is designed, the related workflows are converting PDF supplier invoices to QuickBooks and converting PDF supplier invoices to Xero. The restricted-fund layer sits on top of those mechanics: the import is only useful if the bill-line fields carry the reporting dimensions the nonprofit needs.

Reports and releases prove whether the coding worked

The QuickBooks test is whether the reports show the story the organization expects. Run the P&L by Class, review project or donor reports if those fields carry grant detail, and filter for unclassified transactions. Spot-check split supplier bills where the bill header, line descriptions, and Classes could disagree. If a restricted grant shows no expense activity but the vendor invoices exist, the coding is probably missing or sitting in the wrong dimension.

In Xero, review the Profit and Loss by tracking category, compare categories where that report view is useful, and filter for unassigned tracking. Closed grants, archived projects, and old restricted funds should not remain easy choices for new bills. If they do, the month-end reviewer will keep finding current invoices coded to stale options.

Release-of-restriction entries are a separate accounting step. A supplier invoice can prove that spending occurred, and a coded bill can show which fund, grant, program, or project absorbed the cost. The journal entry that releases net assets from restriction depends on whether the donor restriction has been satisfied. Invoice extraction can help populate the bill data that supports review, but it should not decide when a restriction is released.

The payoff is cleaner reporting. Grant reports tie back to bill lines. Board packets separate restricted and unrestricted activity without spreadsheet surgery. Audit-prep workpapers have a clearer trail from source invoice to ledger row. An outsourced bookkeeper or accountant can review exceptions instead of rebuilding the coding logic from scratch.

The practical standard is simple: every supplier bill line that affects restricted-fund reporting should carry the dimensions needed before it reaches the ledger.