Fiscal Sponsor Administrative Allocations

A fiscal sponsorship agreement sets a percentage of project revenue for the sponsor's oversight, accounting, and compliance work. Agreements, board memos, and search results still call that percentage an administrative fee. On the sponsor's books it is an administrative allocation of money the sponsor already holds.

This guide explains how to record that share under Model A, Model C, and Model F, and how it differs from a general interfund transfer.

Quick Answer: Administrative Allocations

The administrative share is an internal allocation. The gift is contribution revenue once. The percentage then moves from the project fund to the sponsor's operating activity. Consolidated totals should not count those dollars a second time.

Model A is an allocation inside one legal entity. Model C is a retained share of contributions the sponsor controls, followed by a regrant of the rest. Model F can be a real service bill, because the project already owns the funds.

For typical ranges, see fiscal sponsorship fee structures. For the legal letters, see fiscal sponsorship accounting models. For the ledger, see fund accounting.

Why the books use an allocation

Under comprehensive fiscal sponsorship, donors give to the sponsor. The sponsor has discretion and control over those charitable assets. The project fund is a way to track a program inside that same entity. It is not a customer, and it is not a second charity that can be invoiced.

The monthly percentage allocates the sponsor's own resources from the project fund to the operating activity that carries payroll, insurance, audit, and the rest of the back office.

Record the gift once. If the allocation is posted again as revenue, the consolidated statement of activities counts the same support twice: once when the donor gave, and again when the sponsor moved its own money. Fund-level reports can still show the allocation, so each project sees the share that supports sponsor operations. The organization-wide total should eliminate it.

Form 990 Builder states the same rule for filing: internal sponsor administrative allocations should stay unmapped so consolidation does not double-count them.

Model A, Model C, and Model F

The letter in the agreement decides whether the share is an internal allocation or a charge to someone else.

Model A

Model A puts revenue, expenses, contracts, and liability on the sponsor. Donor receipts use the sponsor's EIN. Staff may be the sponsor's employees. Assets in the project fund belong to the sponsor.

The monthly percentage reallocates unrestricted resources the sponsor already recognized. A common path:

1. Code the gift to the project fund as contribution revenue.
2. At month-end, allocate the agreed percentage from that fund to the sponsor's operating activity.
3. Leave the allocation out of consolidated revenue and out of the Form 990 amounts that would count it again.

The project team still needs a clear report: eligible revenue, the rate, the amount allocated, and the remaining fund balance. Clarity comes from the fund report, not from treating the project as a debtor.

Model C

Model C is a grant relationship. The project is a separate entity with its own EIN. The sponsor still receives the charitable gifts, so donor receipts still use the sponsor's EIN. The sponsor then grants funds to the project.

The percentage in the agreement is the share the sponsor keeps before that regrant. The project does not receive the full gift and then write a check back. Treating the share as a bill the project pays makes the sponsor look like a conduit: money in, money out, with the sponsor taking a toll. Deductibility depends on the sponsor's discretion and control, which a pass-through charge undermines.

On the sponsor's ledger, a Model C relationship can still sit in its own fund. AlignMint records Model C as a fund on the sponsor's books, not as a second organization with its own chart of accounts. The administrative allocation posts inside that ledger. The regrant is the separate entry for the amount that actually leaves.

Model F

Model F is the case where a fee is the right word. The project already has its own exemption, gifts are received in the project's name, and the sponsor provides technical assistance without controlling the funds. The project can pay for bookkeeping, payroll, or other back-office work. That payment is a charge between two organizations.

AlignMint does not store Model D or Model F as a fund setting. Model D, the group exemption, is different again: subordinates can receive deductible gifts directly, and a central organization's assessment can be a real charge between organizations.

Allocation and interfund transfer

Both an administrative allocation and an interfund transfer stay inside one entity. They are different workflows.

Use the monthly administrative allocation for the percentage in the sponsorship agreement. It is calculated from eligible revenue, confirmed by the parent organization, and posted to the mapped allocation accounts.

Use an interfund transfer when unrestricted dollars cover a restricted deficit, when programs reclass net assets, or when due-to and due-from balances need to move for a reason other than that monthly share. The interfund workflow is the wrong tool for the sponsorship percentage.

Cash can still move. If the project fund and the operating fund use different bank accounts, the sponsor may settle the allocation by moving its own cash. That settlement is a transfer between the sponsor's accounts. It is not a receivable from an outside project.

Card-processing charges are a third category. Those are fees a payment company bills. Keep them separate from the administrative allocation.

What to put in the agreement

Write the economics in allocation language, and mention the everyday name so nobody thinks a term was hidden.

• The rate, and the base it applies to (which revenue counts, and which grants or pass-through amounts do not).
• Whether the rate changes with volume, project age, or services such as payroll and insurance.
• The services the share covers, and the costs that sit outside it.
• The monthly report the project will receive: base, rate, amount allocated, and remaining balance.
• For Model C, the regrant timing, and that the sponsor retains discretion and control over charitable funds.
• Exit terms for the remaining fund balance.

People will still say "fee" in conversation. The agreement can say: the administrative allocation described here is the amount sometimes called an administrative fee. The label in the contract should match the ledger.

Posting the month

Sponsor Administrative Allocation calculates the monthly share from eligible revenue for each sponsored organization. The product default is 7.5% of eligible revenue. Set each organization's rate to match the agreement before you confirm. Parent admins confirm the batch. Sponsored organizations can view the result. Map the posting accounts before the first run.

If you want the cash movement in the same step, turn on cash settlement. That adds the due-to, due-from, and checking entries for money moving between the sponsor's own accounts.

A spreadsheet process can post the same economics. Export revenue by fund, apply each fund's rate, and enter one balanced allocation. Skip the line that books extra revenue for the sponsor and an expense of a separate organization. Those two lines invent a second party and a second helping of revenue.

Use the fiscal sponsor fee calculator to model the rate before you write it into the agreement. The calculator compares percentages. The ledger still records an allocation.

Related

• Fiscal Sponsorship Fee Structures Explained — typical ranges and what a given rate should cover
• Fiscal Sponsorship Accounting Models — Model A, Model C, and Model D on the ledger
• Fund Accounting — funds, restrictions, and reports
• Sponsor Administrative Allocation — the monthly posting workflow