Updating Positions for the Next Fiscal Year

Modified on Tue, Oct 1 at 2:40 PM

Updating Positions

Positions can be updated via Martus, or via Excel using the export and import process. The export and import process may be advisable if many changes need to be made.

Notes about Positions

  • Positions are specific to each scenario, thus it is possible to have multiple scenarios per year, each with a different set of positions.
  • Adjusting positions in one scenario does not affect any other scenario.
  • Positions can represent a single employee or a pool of employees.
  • Positions should only be removed from a scenario if the position will not exist in the year for which you are budgeting; it is not advisable to remove a position if it is currently vacant.
  • It is best practice to have one "Vacant Position" employee set up in Martus to budget for health insurance for any open positions since coverages for health insurance are linked to the employee record.


Updating Positions in Martus

  1. Go to Personnel Budgeting > Scenarios.
  2. Click on the Positions tab.


  3. To add a new position not already in the scenario, click Add New Position and enter the appropriate information and pay items. 
  4. To update existing positions, click Edit (the pencil icon) next to the appropriate Position Name.


  5. Edit the necessary fields


  6. Click Save


Updating Positions via Export and Import: 

  1. Go to the Scenarios tab.
  2. Export the Pay Data File.
  3. Remove all tabs except the Positions tab.
  4. Update as needed.
  5. Import the Pay Data File back into Martus.

For more information on the Pay Data File click here.



Use the link below to navigate through the learning path.


Create Next Year's Personnel Scenario << New Year in Personnel - Learning Path >> Updating Pay Items on Positions

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article