Expenses correspond to amounts spent to attain the objectives of the Folio.  They can belong to any of the three categories described in section Categories: OPEX, CAPEX or FINEX.  Expenses can be single occurrence, or they can be recurrent.  Recurrent expenses can also be amortized; in which case the amount associated with the payment will be evenly split on the payment period.  Expenses should represent all money that you plan to be spent during the Folio's time frame, such as rents, maintenance contracts, software license purchases, loan financing costs or mortgages.

See the Expenses page for more information on expenses and how they are calculated.

Positions are the salary expenses you plan the Folio will incur at one point or another. They are operational expenditures.   Positions are grouped by title (e.g. Developer, Architect, Q&A). You can collapse (or expand) a group of positions by clicking the triangle icon ( ) next to a position title.

Example of positions could be J2EE Developer 1, System Architect, Test Automation Specialist, etc.

See the Positions page for more information on positions and how their cost is calculated.

Anchor
AddExpense AddExpense

Planning an expense

To add an expense, either click the Plan Expense button or hit the "a" (for add) shortcut key.  This brings the expense edition dialog.  Check the "Plan another" box at the bottom of the dialog in order to create many expenses in sequence. 

Anchor
CopyExpenseToActual CopyExpenseToActual

Copying an expense to actual

Select an existing expense to copy to actual by clicking on it and then either click on the drop-down menu on the top-right part of the expense details view (on righthand side of the screen) and select the Copy to actual option or hit the "t" (for to Actual) shortcut key.  This will copy the selected expense to actual, including its attached files. 

You can copy multiple expenses to actual at once by selecting them in the budget (by pressing and holding the Control key while clicking the expenses to copy).  You can then copy the selected expenses the same way you copy a single expense.  The confirmation message will inform you of how many expenses have been copied.

Anchor
IMPORT IMPORT

Import / Export

FOLIO Allows you to import or export your data in CSV (comma separated values) format.

Importing Planned Expenses

To import data from an existing CSV file, click on the ... button and select Import data. Alternatively, you can type the keyboard shortcut i to open the import dialog. See Importing Data from CSV and Planned Costs Importing Tips to learn more about importing Planned expenses.

Exporting Planned Expenses

To export data to an external CSV file click on the ... button and select Export data. Alternatively, you can type the keyboard shortcut x to instantly export Planned Expenses. Exported CSV file includes both budgeted positions and expenses. See Planned Costs CSV Export Detail to learn more about Planned expenses export.

Anchor
SCOPE SCOPE

Scope Inspector

The scope inspector allows you to view the breakdown of the Folio's scope by issue type (user stories, bugs, etc.) and see if the planned positions have a capacity that matches the effort required for that scope. It will help you answer questions such as:

• Are the planned salaries sufficient to implement the planned features of our application?
• How much required effort has been estimated for the planned scope? How much to fix the known bugs?
• What's the maximum effort a person can possibly provide given the current Folio's time frame?

Clicking the Scope button brings up that information in the details panel on the right.

Details
Scope Inspector	Shows or hides Scope Inspector.
X	Hides the Scope Inspector.
	Inline Help. Clicking on the icon opens up an inline dialog containing definitions of elements displayed in section.
Saved filter	Clicking on Saved Filter link displays all JIRA issues included in your Folio's scope
Capacity per Person	A single person's capacity in terms of regular working hours given the Folio's timeframe and the Working Schedule configuration.
Planned positions	Total number of positions currently planned
Planned Effort	Total number of working hours currently planned
Breakdown By Issue Type
Issue Type	Type of issues (User Story, Task, Bug, etc.)
Count	Total number of issues by type
Earned Value Field	Sum of the Earned Value Field for all issues of given type. Will not be display if earned value field is Original Estimate.
Original Estimate	Sum of Original Estimate for all issues of given type.