> For the complete documentation index, see [llms.txt](https://charity.childsafetyfund.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://charity.childsafetyfund.org/policies/organization/quickstart-3/quickstart-2.md).

# Banking

CSF is committed to maintaining transparent, secure, and compliant financial management practices across all funding sources. This policy establishes standards for the management of bank accounts, ensuring clarity in the use of federal and non-federal funds, adherence to internal controls, and protection of organizational assets.

***

### **Account Management**

CSF shall maintain separate and clearly identifiable bank accounts for:

1. Operational and Non-Federal Funds – Used for private donations, legacy gifts, unrestricted revenue, and general operations.
2. Federal Awards and Restricted Grants – Used exclusively for the receipt, management, and disbursement of funds awarded under federal or otherwise restricted programs.

Funds from federal awards shall not be commingled with non-federal funds. Each account will be used solely for its designated purpose to maintain transparency and traceability in accordance with generally accepted accounting principles (GAAP) and CSF’s internal control framework.

***

### **Account Oversight and Authorization**

* All bank accounts must be authorized by the Board of Directors prior to opening.
* The Treasurer shall maintain oversight of all accounts, with monthly reconciliation to the general ledger.
* The Treasurer and authorized staff are authorized signatories; dual authorization is required for any disbursement exceeding $5,000.
* Bank statements shall be reviewed regularly by the Treasurer and quarterly by the full Board as part of the financial review process.

***

### **Internal Controls and Segregation of Duties**

To align with the principles outlined in the GAO *Green Book* and COSO Internal Control Framework:

* Receipt, deposit, reconciliation, and reporting functions shall be segregated to the extent possible based on staffing capacity.
* All transactions shall be supported by source documentation (invoices, payroll records, or award documentation).
* Transfers between accounts shall require written approval and be supported by justification consistent with funding restrictions.

***

### **Interest and Program Income**

Interest or program income derived from federal funds shall be tracked separately and used or remitted according to applicable grant conditions and federal cost principles.

***

### **Bank Selection and Relationship Management**

CSF shall maintain banking relationships only with federally insured financial institutions. Institutions must provide online access, monthly statements, and fraud protection services to support CSF’s compliance and monitoring activities.

***

### **Record Retention**

All bank records, reconciliations, and supporting financial documentation shall be retained for no less than five (5) years after the final expenditure report or as otherwise required by federal or state law.

***

### **Annual Review**

This policy shall be reviewed annually by the Board of Directors to ensure ongoing compliance with CSF’s financial integrity standards and any applicable federal or state regulations.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://charity.childsafetyfund.org/policies/organization/quickstart-3/quickstart-2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
