Restricted fund records

A restriction decision makes sense only beside the spending record it governs. The AP Specialist prepares the partner bill, selects its organization and attaches the source material. The Controller then reviews the linked fund record: the named fund, the restriction text, its effective date and the amount available for this decision. The restriction has its own status and revision, so a reviewer can tell which decision was in force when the bill moved forward.

Consider a facilities invoice that draws on a restricted program fund. The invoice may be correctly coded to an expense account yet still fall outside the fund’s permitted purpose. Keep the bill and restriction review together. A coding check answers where the cost posts; the restriction review answers whether the fund may bear it. The Controller makes that decision before approving the accounting document.

• Bill context. The accounting document identifies the counterparty, organization, amount, due date and accounting period.
• Restriction context. The linked fund record holds the fund name, available amount, effective date, restriction text, revision and decision date.
• Decision trail. Approval or rejection is visible on the restriction record; the bill’s own review decision and operation result remain separate evidence.

Decide who owns the wording of each restriction and how available amounts are checked before a bill is approved. Choose a consistent naming rule for funds and organizations. A fund name written two ways can split a review queue and make the same restriction harder to find. Decide whether a revised restriction replaces the prior decision for new expenses or requires the Controller to review bills already in progress.

A useful pilot uses one organization and a small set of bills with clear outcomes. Include one eligible expense and one that should be rejected. Give the reviewer the source invoice and supporting explanation, then compare the recorded amount with the amount the finance team expects to charge. The decision date should tell the next reader when the judgment was made.

Open a bill for a partner invoice and follow its linked restriction. The AP Specialist should see the payable amount and the fund context before asking for approval. The Controller should be able to read the restriction, available amount and effective date, record the decision, and return to the same bill. If the restriction is rejected, check that its status, revision and decision date identify the outcome for the next reviewer. If it is approved, review the bill’s coded lines and supporting attachments before the bill approval action.

Do not treat an approved restriction as proof that the payment reached a bank. The Treasury Analyst follows the separate payment record and its release result. This separation keeps a policy decision, an approved payable and an actual money movement understandable on their own terms.

• Accounting Documents Control Desk — Documents needing a decision, with organization and status filters and a link to the source bill.
• Accounting Documents Awaiting Review — Partner bills waiting for the Controller’s document decision.

Follow the restricted expense path or prepare the first case in implementation.