Funding Sources
Set aside money for each Line of Business by fiscal year, split it into Capex and Opex, and route and approve the requests that draw on it.
A funding source, shown in the app as a funding, is a pool of money that belongs to a Line of Business for one fiscal year. Projects, portfolios and intake requests ask for money from fundings, and the money counts against a funding only once the request is approved.
On this page
Choose the fiscal yearAdd a fundingRead the Funding tabChoose how requests reach a fundingRequest funding for a project or portfolioRoute requests from the queueFunding on an intake requestFunding approvalEach LOB can have several fundings in a year, for example one per budget line, program or funding source. They are listed on the LOB's Funding tab.
- Each funding belongs to one LOB and one fiscal year.
- Amounts are split into Capex and Opex.
- Each funding has an owner, a user or a group, known as its Fund Manager.
- A funding can be tagged with the project types it is meant for.
- Money moves through these states: In queue while waiting to be sent to a funding, Requested while waiting for approval, Reserved when approved on an intake request, and Committed when approved for a project or portfolio.
If Lines of Business are new to you, start with Lines of Business Overview.
Choose the fiscal year
Open All LOBs, click the LOB, and go to the Funding tab. The tab shows one fiscal year at a time. Use the year selector at the top right to switch between past years, Current FY and Next FY.
Select Next FY to set up next year's fundings before the year starts.
Add a funding
Select the fiscal year the funding belongs to, then click Add funding and fill in the form:
- Name, required.
- Description, optional, what the funding is for.
- Project types, optional. Select one or more project types. Projects can only draw from a funding tagged with their project type.
Click Add to save the funding, then set its owner, a user or a group. The owner shows on the funding's card and is the funding's Fund Manager in approval policies. Because each funding belongs to one year, create new fundings for each new fiscal year.
Only users with permission to edit the LOB's funding see Add funding and can change fundings.
Read the Funding tab
| Name | Source | Status | Total | Capex | Opex |
|---|---|---|---|---|---|
| 333 | Project | Committed | $25,000 | $25,000 | $0 |
| Service Activation | Project | Committed | $170 | $120 | $50 |
| r6 | Intake | Reserved · 14 days | $900 | $500 | $400 |
| Name | Source | Status | Total | Capex | Opex |
|---|---|---|---|---|---|
| Bio Tasking | Project | Requested · 20 days | $170,000 | $140,000 | $30,000 |
| Data Migration | Project | Need more info · 18 days | $8,255 | $7,000 | $1,255 |
The summary cards show the totals for the selected year:
- Available to commit, the money not yet committed or reserved, with the percentage allocated. Below it are Total funding, Committed and Reserved.
- Requested, pending approval, the amount waiting for approval, split into Capex and Opex and into requests from intakes and from projects.
- Allocated by spending type, how much Capex and Opex is left, with the committed and reserved amounts for each.
Below the summary, each funding has its own row. On the left are its available amount, a bar showing what is committed and reserved, its Total, Capex and Opex, and its project type tags. On the right, a table lists every project, portfolio and intake drawing on the funding, with its source, amounts and status:
- Committed, approved for a project or portfolio.
- Reserved, approved on an intake request that is not yet a project, with the number of days since it was reserved.
- Requested, waiting for approval, with the number of days waiting.
- Need more info, sent back by an approver with a comment, with the number of days waiting.
Use the controls at the top of the tab:
- Waiting on you shows the requests waiting for your approval.
- Include requested adds requested amounts that are not yet approved to the bars, so you can see what each funding would look like if they were approved.
- Search finds a funding by name, the download icon downloads the data, and the history icon shows who changed the numbers and when.
Choose how requests reach a funding
Each LOB chooses, in its settings, how funding requests reach a funding:
- Requesters pick the funding. The project manager or intake requester chooses the funding when they submit the request. The request goes straight to approval.
- Centralized queue. The requester only chooses the fiscal year and enters the amounts. The request enters a queue, shown as In queue, and a designated person routes it by hand to the right funding, or splits it across several. From there, it goes through approval like any other request.
Use the centralized queue when requesters should not need to know which funding pays for their work, or when a finance team decides where money comes from.
Request funding for a project or portfolio
Projects and portfolios request funding the same way, from the fiscal-year budget:
- If requesters pick the funding, add a funding row for each funding to draw from, with the Capex and Opex amounts needed. The fundings offered are those of the LOB for that year that match the project type. Add more rows to draw from several fundings.
- If the LOB uses the centralized queue, choose the fiscal year and enter the Capex and Opex amounts needed, without choosing a funding.
Then submit the request. Once it reaches a funding, it shows as Requested until the approvers act on it:
- Approved, the amount becomes Committed on the funding.
- Need more info, an approver sends it back with a comment. Update the request and submit it again.
- Rejected, the request goes back to its submit state, so it can be changed and submitted again.
- Reopen pulls an approved commitment back, like an undo, so it can be changed.
The budget shows whether it is Not funded, Partially funded or Funded, based on the approved fundings. Funding can go above 100%, for example 125% funded. This is allowed on purpose, since extra funding is often kept as contingency.
Money is not committed until the request is approved. A requested or queued amount does not count as committed on any funding.
Route requests from the queue
In an LOB that uses the centralized queue, requests wait In queue until a designated person routes them. This person is given the routing permission through the LOB's roles.
- Send each request to the funding that should pay for it.
- Split a request across several fundings when more than one should pay part of it.
- Once sent, the request shows as Requested on each funding and goes through approval.
If a request reaches the wrong funding, the funding's Fund Manager can send it back to the queue instead of rejecting it, so it can be routed again. Only the funding's Fund Manager can send a request back.
In an LOB where requesters pick the funding, there is no queue. If a request reaches the wrong funding, the Fund Manager rejects it and the requester submits it again to the right funding.
Funding on an intake request
Intake requests use the same funding component as projects, and follow the LOB's choice of picking the funding or using the centralized queue. Approvers can see where the money will come from before the project is created.
Once the funding is approved, it shows as Reserved on the funding. When the intake is promoted to a project, the reserved funding moves to the new project as committed, with no second approval.
Reserving funding at intake is especially useful when intake is the only way new projects are created, because funding is agreed as part of the approval.
Funding approval
Funding requests are approved through the Funding Approval policy, in the LOB's approval policies. The policy decides who must approve a request before the money is committed or reserved.
- Default Approvers apply to every request. Approval can be required from members, groups or roles.
- The Fund Manager role always points to the owner of the funding the request is on, a user or a group. Add it to Default Approvers so each request goes to the right owner without naming people in the policy.
- Add rule adds more approvers when a request meets a condition. For example, a rule can say that any request over $200,000 also needs the CFO. When a rule matches, both the default approvers and the added approvers must approve.
- Active shows the policy is in use.
| Members | None |
| Groups | None |
| Roles | Fund Manager |