Map funds to income accounts
Every fund used in a new posting or replacement classification needs an active approved income mapping. The mapping supplies the revenue credit account; an operator does not enter arbitrary GL account IDs in the posting form.
Fields and prerequisites
You need finance view/configure rights, active settings and authorised account discovery. The fund and account must belong to the current tenant.
| Field | Rule |
|---|---|
| Fund ID | Existing fund ID verified from Fund management; fixed when editing that mapping |
| Approved revenue credit account | Active eligible REVENUE account with credit normal balance |
| Required recognition/configuration reason | Private explanation of the approved mapping, maximum 500 characters |
| Active approved income mapping | Explicit approval for this configured revenue recognition |
The current mapping form uses a numeric Fund ID field. Obtain it from the correct existing tenant fund; do not guess from another tenant's examples.
Create a mapping
- Review the fund purpose and its approved income recognition with finance.
- Open Financial configuration → Fund income mappings.
- Search/check existing pages for that fund.
- Enter Fund ID, select the approved revenue account and enter the reason.
- Select the approved active state and choose Save mapping.
- Reload and verify fund, income account, activity and version.
Update and historical effect
Choose the existing mapping's Edit action. Its fund ID stays fixed; review the account, active state and reason, then save against the displayed version. New mappings/classification changes affect future financial revisions. Existing posted journal lines and snapshots keep their original account IDs.
Example: Education's future income recognition is approved to use another eligible revenue account. Updating the mapping does not rewrite yesterday's donation. If a posted donation also needs reclassification, perform a separate reviewed financial correction using the current approved mappings.
Recognition boundary
Activating a mapping explicitly approves revenue recognition for the workflow. The module does not infer deferred income, conditional-gift liabilities or accounting treatment from the word RESTRICTED. If the gift's approved treatment does not fit this revenue-posting workflow, stop at the appropriate supported state and obtain the separately approved finance procedure.
If a split has no active mapping, resolve that exact fund's configuration. Do not collapse allocations into General Support or choose an unrelated account to make preview succeed. A configuration/version change after preview requires a fresh proposal and review.