How to load adjustments
Updated 10 November 2026
Overview
This guidance covers how to load the following adjustments within the OSCAR budgeting system.
Disaggregation adjustments (to allocate data loaded centrally by GEP, or received via MOGs or BCTs):
- Budget Measure Disaggregation
- Reserve Claim Disaggregation
- Spending Review Settlement Disaggregation
- Budget Exchange Disaggregation
- HMT Disaggregation
- BCT Disaggregation
- MOG Disaggregation (Budget Neutral)
Other adjustments loaded by departments for approval by spending teams
- Final Outturn
- Budget Regime Change
- Discount Rate Change
- Internal Departmental Change (Budget Neutral)
- Annually Managed Expenditure
- Non-Budget
- Switch
- General Provisions
- Capital Provisions
- Capitalised Provisions
There is separate guidance which covers loading donating BCT and MOG adjustments, and Vote on Account adjustments.
For more information about the adjustment types please see the ‘How OSCAR works’ page, or for more information on what codes to use, visit the plans or outturn recording guidance pages all available on the homepage.
For any issues logging onto OSCAR, please visit the OSCAR Users & User Authorisers page on OneFinance or contact oscar.support@hmtreasury.gov.uk
Accessing the Budgeting homepage on OSCAR
1) Once logged onto OSCAR, click ‘Enter Data’, followed by ‘Reports and Analysis’:

2) Click ‘Budgets & Estimates’, followed by ‘Budgeting Homepage’:

3) This should take you to the Budgeting Homepage:

There are sections in this guidance which separately cover Creating adjustments, Managing adjustments (either reviewing previously submitted adjustments, or returning to an adjustment to edit it or move it through the workflow). The guidance on reporting also sits on the separate How to analyse budgeting data and download reports page.
The budgeting homepage can be accessed from any of the above pages by selection the Home icon at the top left of the page:

Creating adjustments and adjustment types
4) Click ‘Create Adjustment’. Here, users can select their department from the dropdown listed under ‘Organisation Group’. If a user has access to multiple departments, they should all be available to select in the dropdown. In the below example HM Treasury has been selected. Similarly, users can also select the adjustment type they are looking to create. All available adjustment types will be available for users here (including BCTs, MOGs and Vote on Account adjustments for which there is separate guidance for).

You can review a brief summary of what each adjustment type is for at the top of this page.
Disaggregation adjustment types, and internal departmental change (budget neutral) adjustments do not require spending team approval. These will become confirmed as the step after locking. All other adjustments can only be submitted by department users. It is then for spending teams to confirm or reject the adjustments.
For disaggregation adjustments, they need to match the amount for that specific upload type. For example, if 100,000 RDEL was loaded as a budget measure, and 50,000 RDEL was confirmed as a BCT, users would need to load one Budget Measure disaggregation type for the 100,000, and another separate BCT disaggregation adjustment for the 50,000. If a user tried to disaggregate the entire 150,000 as a Budget Measure disaggregation, or another different disaggregation type, validation errors would prevent the adjustment from being loaded. More information about disaggregation adjustment types is available here.
Creating adjustments
6) Click on the ‘Adjustment Type’ dropdown and select the adjustment type required, and type a description for this into the text box underneath the selection. In the below example we have selected to load a Final Outturn adjustment and given a title of ‘Final Outturn adjustments for HMT’. After this, click ‘OK’. This should then result in the user being navigated to a data input grid where the adjustment can be entered, as shown below:

Note: only GEP users will be able to create the Control Total adjustment types for Reserve Claims, Budget Measures, Budget Exchanges, Spending Review Settlements and Type HMT.
7) You should now be able to enter data into the data input grid as shown above. The five available outturn years in live, that are available to adjust, will be the years in the first five columns from the left. The adjustment type users create alters the years that are available for adjustment. In this example, for Final Outturn, no plans years are shown. Whereas, for example, if a user had created a Budget Measure disaggregation adjustment, only plans years would be shown.
Data Entry
8) Users have the option to paste in data from an Excel workbook, or to type directly into each grid. If typing in codes, a dropdown will appear to show the available codes for selection. This can be toggled on and off by selecting ‘Y’ or ‘N’ in the ‘Deactivate Picklists’ box at the top of the list.

For most adjustments, OSCAR data entry users a combination of Organisation codes, Account codes and Sub-segment codes, followed by the amounts in thousands for each year (e.g. ‘1’ on OSCAR equals £1,000). Users can also toggle the view from ‘Code View’ to ‘Name View’, to see the names for the codes entered on the grid:

A default of 10 rows is selected in the view, but users can also input up to 10,000 rows of data within one adjustment by selecting a different option. Note that if a user adds data in any row over 10, for example row 15, and reverts back the 10 row view, the data in row 15 will still be stored in the adjustment and will be processed unless it is either removed or blocked from being entered by validations.

9) Once all data has been entered, including the amount, users are required to click the ‘Validate’ button to check for any validation errors before they can further process the adjustment. If this is successful, a message will appear to show that the validation has been completed. There is a section in this guidance which covers common validation errors that prevent an adjustment from being validated successfully.
To lock and submit the adjustment once it has passed the validation check, users should click the circled pencil icon next to the home button as shown in the image below:

To follow the next steps to select and lock adjustments, users can skip to the guidance sections further down the page.
Common validation errors
If there are validation errors, there would be an error message in the Validation box at the top of the screen, or for the individual row where the validation issue is occurring.
- A common validation for disaggregation adjustments is the use of the wrong adjustment type. E.g. using a budget measure disaggregation adjustment for data that was loaded as a reserve claim. In this case you would receive a validation error message (as shown below in the first screenshot), highlighting that it doesn’t match the control totals that are unallocated. Even if the total is correct, it won’t validate if loaded against the wrong adjustment type.
- A common validation error for outturn adjustments is the use of ‘Plans’ account codes, which cannot be used for outturn years. Changing the codes to outturn account codes (or codes that can be used for both outturn and plans) should resolve the issue.

An example of these validation errors are shown in the image above.
- A common disaggregation validation error can also be that the amount doesn’t match the control totals loaded. For example, some data might have fallen into different economic ringfences, or just have differences to the overall total of the adjustment loaded. One way to check the overall total in the adjustment loaded is to follow the ‘Checking control totals within an adjustment’ section to check the adjustment contents. Additional information about how disaggregation works is available in the guidance below.
Checking control totals within an adjustment
10) Once all validation checks have passed, users can check the overall impact on the control totals by selecting the ‘Control Total’ option underneath the ‘Validate’ button to the top right of the screen.
For each Economic Budget (e.g. Resource/Capital), Control Budget (e.g. DEL Prog/Admin) and Economic Ringfence (E.g. Non-Ringfenced, General Capital) combination, there are three rows:
- Adj: This row shows the total amount entered within the disaggregation adjustment you are currently editing. In the below example a value for ‘500’ has been entered for 2027-28.
- CT: This is the amount which is unallocated and needs to be disaggregated. The data in the Adj row/entered in the adjustment must match the CT row. In the example below, data shows 1,000 for 2027-28 and 1,000 values up to 2030-31.
- Diff: This shows the difference between the Adj and the CT row.

Please note that this Control Total view will only work as intended for ‘Disaggregation’ type adjustments. For other adjustment types (e.g. AME, Final Outturn) the Control Total view does not correctly show the offset against the CT row (as there is no control total data loaded to compare against).
Users can toggle between the ‘Control Total’ view and the ‘Code View’ to edit the amounts within the adjustment as many times as required.
Other things to consider when disaggregating control totals include:
- All years must be disaggregated at once. If the right control total value is entered for one year, the adjustment will still fail to validate.
- If the CT row is showing 0s, it means there is nothing to disaggregate. In this scenario, consider if there is still anything left to disaggregate or if you are disaggregating against the wrong adjustment type (using a Budget Measure disaggregation for a Reserve Claim), or disaggregating against the wrong code (using DEL Admin codes instead of DEL Programme codes).
- OSCAR will automatically offset the unallocated amount. Users only need to match the unallocated amount loaded, and do not need to remore anything from the system.
Disaggregation adjustments
When control totals for Budget Measure, Spending Review Settlements, Reserve Claims, Budget Exchanges, and Type HMT are loaded to OSCAR, they need to be disaggregated using the associated disaggregation type as shown in the guidance above. The same also applies to MOG and BCT adjustments that are confirmed by receiving departments. More information on MOGs and BCTs is available below
The main difference with disaggregation adjustments is that they must meet the following conditions:
- Disaggregation adjustments must match the amount that has been confirmed against that adjustment type
- All years that contain unallocated data for that adjustment type must be disaggregated within the same adjustment
If, for example, two Budget Measure adjustments were loaded on separate dates, the amounts for both adjustments would have to be disaggregated within the same Budget Measure disaggregation adjustment. The idea is that OSCAR requires users to disaggregate everything that is unallocated on system in one go, so that nothing is left as unallocated. Departments users can move data using Budget Neutral changes at any point after disaggregation.
More guidance is available on the How to analyse budgeting data and download reports page which explains how to find out the unallocated amounts for each adjustment type.
Example for disaggregation
This focusses on Budget Measure disaggregation types, but the same process applies to all disaggregation types on OSCAR.
11) Follow the guidance from the Accessing the Budgeting homepage on OSCAR above to navigate to the budgeting Homepage.
Click on ‘Reporting’ followed by ‘Control Total Summary’ .

12) The following view is an example for HM Treasury. It is advised that users select the option for ‘Confirmed’ when reviewing unallocated data, as data can only be disaggregated once it is confirmed. The ‘Total Unallocated’ dropdown should be automatically selected. You can see in the below example that HM Treasury has data to disaggregate for several years. If there was nothing at all to disaggregate, the view would return as empty.

13) The total of the unallocated data maybe be from a comination of different adjustment types. To determine what adjustment types require disaggregation, users can select the different adjustment types from the ‘Total Unallocated’ dropdown.
For example, in the below example ‘Unallocated BM’ has been selected in the first example. This shows the data which needs to be disaggregated using a Budget Measure Disaggregation adjustment type:

If comparing the above Unallocated BM selection to the Total Unallocated view, you can see that these amounts do not match, meaning there must be more unallocated data of other types to disaggregate. Working through the list, the ‘Unallocated HMT’ dropdown also shows unallocated totals. The amounts shown in the image above are those that will need to be disaggregated using the ‘HMT Disaggregation’ adjustment type.
Working through this Unallocated Total list should result in viewing all those control totals which require disaggregation across all adjustment types.
14) Once finding the exact figures for disaggregation, users can either create a new adjustment or manage/edit an existing adjustment to disaggregate the data. Using the type HMT data as an example, a budget measure disaggregation adjustment has been created in the example below.
15) Enter the organisation, account and subsegment codes on the left, and the data to disaggregate against each one. Note that the total of each row of adjustments should match the overall total for the unallocated HMT amounts:

If users try to disaggregate a different amount, an error message will appear. For example, if changing the amount in 2026-27 to ‘500’ instead of ‘1,000’, this results in the above message. You can read more about common validation error messages here.
Once content with the adjustments, click ‘Validate’. If the totals align to the unallocated data amounts, this should present no error messages:
Managing Adjustments
15) If you are looking to review or process an adjustment you have already created, you can do so by clicking on the ‘Manage Adjustments’ button on the budgeting homepage.

The Manage Adjustment screen will look similar to this (the following view has HM Treasury selected as the organisation):

If you have access to multiple organisations, you can select them from the organisation dropdown column. You can also filter and reorder any columns to your preferences. Users can revert to the budgeting homepage by clicking the Home symbol in the top left corner at any time (the view shown in step 15 to access adjustment creation and reports).
Selecting adjustments
If an adjustment is selected, it will show the row in green highlight. Adjustments might be automatically selected if they have just been created.

If the adjustment highlighted in green is not the adjustment you wish to review or lock/submit, you can unselect it by either clicking in the Select box and clicking ‘N’. or clicking the ‘Clear Selections’ button (screenshots of these are shown above). Once unselected, all rows will appear with a white background. You can reselect any row by clicking in the select column for that adjustment, and selecting the ‘Y’ option. Please note that you cannot process two selected adjustments – the budgeting system works on a single select basis only. If an error message appears to advise you have more than one adjustment selected, but can only see one highlighted green line, it might be that you have filtered out your other selected adjustment. This should be resolved by pressing the option to ‘Clear selections’ as shown in the step above.
Reviewing or editing existing adjustments
16) To review an adjustment, or to open it up to edit it, make sure it is first selected (by following the guidance above). Next, click the blue button labelled ‘Review/Edit’:

This should result in navigating to a data input screen with that adjustment selected. If the adjustment has already been locked, submitted or confirmed, it cannot be edited. If it is still in draft or in rejected status, the data can be edited.

After reviewing or editing an adjustment, users can return to the Manage Adjustments screen by clicking the manage adjustments icon at the top left of the screen (as boxed in red above).
Locking and submitting adjustments
17) To lock an adjustment, navigate to the Manage Adjustments homepage and make sure the adjustment is selected and has passed all validations (above sections in this guidance cover validations and selection). Next, click the ‘Lock/Submit’ button in green. This may result in a pop up box appearing in the top right of the screen to indicate the adjustment is processing. Once this is finished, the adjustment status should change to ‘Locked’. If the status does not update after several minutes, it may be due to a time out issue. If you refresh the page, it might have updated. Please try and avoid clicking the ‘Lock/Submit’ button multiple times, as it can lead to delays in processing the adjustment.

18) To submit or confirm an adjustment, follow the steps shown above once the adjustment is in ‘Locked’ status. Once an adjustment is submitted, it cannot be edited unless it is rejected.
For all disaggregation adjustments, the workflow will jump straight from Locked to Confirmed. As disaggregation is budget neutral, there is nothing required for spending team approval. Adjustments cannot be deleted once confirmed, so to adjust a confirmed adjustment users can load a Budget neutral adjustment to make any corrections.
Unlocking and Rejecting adjustments
19) An adjustment can be unlocked only if it is currently in locked status. To Unlock an adjustment, make sure it is selected on the Manage Adjustments homepage, and click the Yellow button to ‘Unlock/Reject’:

A pop-up box will appear. It will ask you to add a comment if you are rejecting an adjustment. If you are only unlocking, you can just click ‘OK’ to proceed:

This may result in a pop up box appearing in the top right of the screen to indiciate the adjustment is processing. Once this is finished, the adjustment status should change to ‘Draft’. If the status does not update after several minutes, it may be due to a time out issue. If you refresh the page, it might have updated. Please try and avoid clicking the ‘Unlock/Reject’ button multiple times, as it can lead to delays in processing the adjustment.
19) Department users are only able to reject BCT and MOG adjustments. There is specific guidance for BCTs and MOGs which details this process. However, it broadly follows the same process as above, with the exception of adding a comment, and that the adjustment must be in submitted status to reject it. Other submitted adjustments can be confirmed or rejected by spending teams, where there is also separate guidance available.
Deleting adjustments
There is currently restricted access on the users who are able to Delete adjsutments. This will be reviewed to consider if it could be opened up to more user groups in the future.
Other workflow considerations
- If your department group is locked by a Process Owner or a user with special permissions, you will be unable to process any adjustments until you are unlocked.
- Some adjustments will show in ‘Closed’ status where what is described as a ‘Parent’ adjustment has been created. For example, as a user you might create a BCT adjustment where you are donating to three different departments within the same adjustment. If you continue to lock this adjustment, three new adjustments will be created (one for each receiving department). These three new adjustments are the active adjustments to be processes, whereas the initial ‘Parent’ adjustment used to create the BCT will no longer be required. It is therefore shown as ‘Closed’.
- After the system rollover takes place (ordinarily late May), to move forward to the next plans year, the adjustments shown for the previous year will disappear from view. They still exist on system, but to avoid the build up of long lists over time, only new adjustments post rollover are displayed on the homepage. To view older adjustments, you can select previous years using the ‘Creation Year Filter’ on the Manage Adjustments homepage:

Loading BCT and MOG adjustments
To donate a BCT or a MOG adjustment (i.e. send or move budget to another department), first follow the steps from Accessing the Budgeting homepage on OSCAR to create an adjustment.
This example focuses on the creation of BCTs, but the process is exactly the same for MOG adjustments. The only difference for MOGs is that users can also donate and receive outturn and income, which cannot be donated via BCT adjustments. 20) To create a BCT or MOG adjustment, click the selection in the adjustment type dropdown after selecting your department from the organisation list. Enter a description and press ‘OK’:

This should result in a data entry grid appearing:

The main difference within the BCT and MOG data entry grids is the field to enter a ‘CPID’. This should be the organisation code for the department that are receiving the budget. Once the adjustment has been validated, you can check the department name by switching to the ‘Name View’ as shown in the above guidance in the Data Entry step. Enter the codes for the rows of data that are to be transferred or have expenditure donated from. For BCT adjustments, this number should always be negative. Figures should also always be negative for MOG expenditure, unless the value is income (and needs to be submitted as a positive number to remove the budget from the department totals).
BCT and MOG validation errors
- As mentioned above, a common validation error for BCTs will be the entry of positive values against expenditure codes. This will produce a validation error at the top of the screen that reads ‘Inputs by Control Total Level validation errors - please check individual CT Adj lines for details’ as shown in the first example of the image below. When navigating to the ‘Control Total – Transfers’ view, the screen then indicates that this is an issue due to ‘Sum of input by Control Totals must be negative or zero’.

- For BCT adjustments, attempting to donate income adjustments will also result in validation errors.
- For BCT and MOG adjustments, the use of organisation codes that are not the core department codes will result in a validation error. Users should not donate MOGs or BCTs to ALBs or other organisations within departments.

- For both BCTs and MOGs, if the total amount loaded to transfer exceeds the amount that is already on OSCAR, it will ask for the control totals to be checked. For example, if a department only has a control total of 100k RDEL Programme non-ringfenced, but tries to donate more than 100 (e.g. 200), this error as shown below will appear. This example attempts to load 200,000 RDEL for a control total of 146,762:

Locking and Submitting BCT and MOG adjustments
Please note that locking and submitting BCT and MOG adjustments is only relevant to donating departments. For how to process a BCT or a MOG adjustment as a receiving department, please review the guidance further down.
Locking BCT and MOG adjustments (donating departments)
21) To lock a BCT or a MOG adjustment, this follows the same process as shown here. This process will result in the creation of new adjustments: a donating adjustment and a receiving one for every department included within the initial adjustment.
Other considerations of locking an adjustment specific to BCT and MOG adjustments
- As the donating department, only the donating adjustment ID (ending in ‘D’) will be listed on the Data Input homepage. At this stage, the receiving department will also have an adjustment ID listed on their homepage (ending in ‘R’). The receiving department cannot reject, confirm, or disaggregate the BCT or MOG adjustment whilst it is still in ‘Locked’ Status’.
- Once the BCT or MOG has been locked, as a donating department you will see results similar to the below image. In this example, the status filter is set to ‘All’ to demonstrate the entire workflow. The ‘parent’ adjustment which has just been processed is ‘ADJ_087_TYPE_BCT_0085’ (now showing as closed). As the donating department, you can see ‘ADJ_087_TYPE_BCT_0085_CAB010_D’ for Cabinet Office and ‘ADJ_087_TYPE_BCT_0085_HMR041_D’ for HMRC. This is because the ‘parent’ adjustment loaded a donation for both CO and HMRC, and therefore two donating adjustment IDs have been created for each separate department.

- Once a BCT or a MOG adjustment is locked, the ‘parent’ adjustment will move to closed status. Once the ‘parent’ adjustment is locked, it has created the donating adjustments to process separately. It is therefore no longer required for processing (its only purpose is to create the initial BCT or MOG adjustments). However, for audit trail purposes the closed ‘parent’ adjustment can still be reviewed either on OSCAR (by clicking the Review/Edit button) or within Data Extract reports. The status filter must be set to ‘All’ on the Manage Adjustments page to view Closed adjustments.
Unlocking BCT and MOG adjustments (donating departments)
Users can still review and unlock and edit locked donating adjustments ahead of submitting them as shown in step 16.
Submitting BCT and MOG adjustments (donating departments)
23) To submit a BCT or a MOG adjustment, select the adjustment so it is highlighted in green, and click ‘Lock/Submit’. This will result in the BCT or MOG moving to submitted status. Please note: If you have multiple departments that are receiving budget (such as HMRC in the example below), these will all have to be submitted separately.

Resubmitting Rejected BCT and MOG adjustments
Once a donating department has submitted a BCT or a MOG, there is no further workflow action required. The receiving department will either confirm the BCT, or reject it. If the BCT is rejected, it will move from ‘Submitted’ to ‘Rejected’, and may also include a ‘Rejected’ comment left by the receiving user.
Once a BCT or MOG adjustment is confirmed, it cannot be edited or returned to the donating department. If an adjustment has been incorrectly confirmed, options are either to disaggregate the data and then create a BCT/MOG and donate the amount back, or surrender the amount confirmed (and have the donating department add the expenditure back in). Your estimates advisor should be able to help with further guidance in this situation.
Reviewing, Confirming and Rejecting BCT and MOG adjustments
Confirming a BCT adjustment (receiving departments)
Once donating adjustments are submitted, it is for the receiving department to review and then confirm/reject the adjustment. Users should receive an email notification once a BCT or MOG has been received. It will also show with a status as ‘Submitted’ on the homepage, and the adjustment ID will end in an ‘R’ to indicate it is a receiving adjustment type.
Reviewing the BCT or MOG adjustment
To review a receiving BCT or MOG adjustment ahead of approval or rejection, navigate to the Adjustment Management screen and select the adjustment so it is highlighted in green. Then click the ‘Review/Edit’ button:

This will show a grid containing the control totals submitted by the donating department. In the above example, this shows a BCT for RDEL Programme Non-ringfenced Budget from COM085. The adjustment ID is available to view on the right hand side of the screen. Users can also review the data within the Budgeting Data Extract as set out in the reporting guidance.
The adjustment cannot be edited on this page. If there is an issue, the adjustment should be rejected (see guidance below). To confirm or reject the adjustment, click on the pencil icon circled in the above screenshot to navigate back to the Adjustment Management homepage.
Note: Once a BCT or MOG adjustment is confirmed, it cannot be edited or returned to the donating department. If an adjustment has been incorrectly confirmed, options are either to disaggregate the data and then create a BCT/MOG and donate the amount back, or surrender the amount confirmed (and have the donating department add the expenditure back in). Your estimates advisor should be able to help with further guidance in this situation.
Rejecting a BCT or MOG adjustment (receiving departments)
To reject an adjustment, navigate to the Adjustment Management page and select the adjustment to reject. Click on the ‘Unlock/Reject’ button as highlighted in the screenshot below. Users are prompted to leave a comment to give a brief summary as to why the adjustment is being reject (e.g. if it is the wrong amount). This comment will appear for users when editing/reviewing the adjustment.

Once ready, click ‘OK’ for the pop-up shown above. The Adjustment ID on the Adjustment Management homepage for both the donating and receiving departments should now show as ‘Rejected’. Once in rejected status, the donating department can edit the adjustment and lock/submit repeatedly until it becomes confirmed.

Confirming a BCT or MOG adjustment (receiving departments)
To confirm a receiving adjustment, users can follow the step as shown above for rejection, but instead clicking ‘Submit’ and without leaving a comment. After clicking ‘continue’ a pop-up message should display to say it has been successfully confirmed, and the status on the homepage should’ve adjusted also.

This will also update the workflow of the donating adjustment to show as confirmed.
For the receiving department, the adjustment now needs to be disaggregated using the ‘BCT Disaggregation’ or ‘MOG Disaggregation’ adjustment types as shown in the guidance above. Users can also view the Disaggregation Section using the same process for identifying amounts to disaggregate for MOGs and BCTs.
Entering Vote on Account (VoA) Data
1) Once logged onto OSCAR, navigate to the Budgeting Homepage as set out in the Accessing the Budgeting homepage on OSCAR guidance
Note: Users do not need to ‘Create’ a Vote on Account adjustment. The adjustment will already be created for them to edit once the Vote on Account snapshot has been taken by the process owners.
2) Click on ‘Manage Adjustments’. This will take you to the Manage Adjustments homepage as shown in the guidance above
For the department selection there should be a VoA adjustment ID generated for the selected department, which should be in draft status. If there is no VoA adjustment displaying, or it is in confirmed status, that suggests the latest VoA adjustment is not yet available. As shown in the example below, users can filter the Adjustment Type to select ‘Vote on Account’ to find the adjustment, if available.

In the above example, the description is ‘Vote on Account 202627’ , although this will refer to the Vote on Account publication for 2027-28. This is because the adjustment generated is based on the system year, which at that point in time will be the year before the Vote on Account Publication in question.
4) Make sure the Vote on Account adjustment is selected. First click ‘Clear Selections’ (to ensure no other adjustments are selected outside of the Vote on Account Adjustment Type filter). Click on the ‘Select’ column dropdown and select ‘Y’, which should populate the row in green and Display a Y in the row:

Once the row is selected, click the ‘Review/Edit’ button as shown above.
5) The above steps should then populate the Vote on Account screen with the adjustment (as shown in the image below).

Based on the above example of VoA 2027-28, this should include the Organisation, Control Budget, and Economic Codes to show the separate totals required to calculate and adjust for VoA.
The Columns included within the larger red box in the image above show:
- Column 1 [2026-27 Main Estimates (Voted) Value]: These are the voted values for Main Estimates 2026-27 (the last available main estimate figures).
- Column 2 [2027-28 Initial Vote on Account Value 45%]: This is a 45% calculation of the amount in the first column for Column 1. If the voted value was negative at Mains estimate, the calculation should result in a 0 value.
- Column 3 [2027-28 Adjustment]: This column is for user input to add any additional budget to the value calculated in Column 2. Note that this will be added/taken from the 45% value, it should not replace the value as a new total.
- Column 4 [2027-28 Required on Account (Final Value)]: This will generate the total amount for the Vote on Account, summing both figures from Column 2 and Column 3.
- Column 5 [Comment]: This is an option input box to add a comment to any rows to explain the submission of additional adjustments.
6) If you require an adjustment to the 45% calculation, add the amount to Column 3 and click validate. If users don’t require an adjustment, still click the option to validate. Write any comments against adjustments in Column 5.
This is an example based on the STG environment. 200 was added to the CDEL value, along with a comment. When clicking validate (circled) the amount in Column 4 updated (371,712 + 200 = 371,912). The other columns remained the same as no adjustments were added:

7) Once content with the final Vote on Account values in column 4, and validation checks have passed, click the pencil icon as circled above (at the top left hand corner of the screen), to navigate back to the ‘Manage Adjustments’ screen.

The adjustment should still be selected and highlighted in green (if it is not, follow the steps to select the vote on account adjustment as shown in the guidance above. To lock the adjustment, click ‘Lock/Submit’ as shown in the red box above. This will move the adjustment status to ‘Locked’.
8) If users wish to edit an adjustment to make a change, this can be done by unlocking the adjustment by pressing ‘Unlock & Edit’. This will result in the adjustment returning to draft status, where users can follow from step 4 of the VoA guidance to select, edit and relock the adjustment.
9) If there are no further changes to make to the VoA figures, users can submit the adjustment by following the process shown in the image above in step 7. Make sure the adjustment is in Locked status and selected, before pressing the ‘Lock/Submit’ button. This should also update on the homepage to show as ‘Submitted’.
10) There is now no further action required from department users once in Submitted status. The adjustment now needs to be confirmed by the Spending Team. If the Spending Team rejects the adjustment, this would result in the adjustment being moved to ‘Rejected’ status. The Spending Team may also note why the adjustment was rejected in the comment section which can be seen in the Review/Data Input page. For example:

In this scenario, ‘Rejected’ Status acts in a similar way to draft status. Users can edit the adjustment by starting from step 6 of the adjustment, making any required edits and pushing the adjustment through to locked status, and resubmitting.