Note: All text describes the page image that follows it.




This is the normal login page.




This is the login page after a user has experienced an error logging in. There is a button to help for common login problems.




This is controllers e-Forms menu - currently Journal Voucher Entry is the only option. The Controllers Office hopes to add several forms to this menu in the future.




After choosing the JVE from the e-Forms menu, the Journal Voucher Menu is displayed. These menu options will also be accessible via the buttons found at the top of the screen.     Note: Template functions will not be deployed with the initial release of the JVE form.




This is the entry form for a Journal Voucher Entry. Some fields will not be displayed for a typical JVE initiator. The screen image here reflects additional fields that a 'Super User' would only have access to. These fields: are the Transaction Code, and 'Other' Reason Type. The 'Other' reason type will allow year-end entries that break normal editing rules to be entered by authorized users. A typical user will see the 'Other' option greyed out, and the Transaction Code will not be entered, but calculated by the system.




This is the form for a Journal Voucher Entry showing there were errors based on standard edits. Most edits refer back to the Reason Type selected at the top of the form. For example, if Budget Reallocation was selected, a Fund Type must also be selected. Account numbers and object codes must then be valid for that specific Fund Type. Only JVE's passing edits will be submitted to the FTU.




This is the confirmation screen for a Journal Voucher Entry. A person is allowed to view all that has been entered in a clear format prior to committing it to the database.




This is the final confirmation of the Journal Voucher Entry initiation process. At this point, the JVE has entered the FTU process. The initiator is then given the option to view a the JVE in a printable format, and print it for their records.




This is the printable version of the JVE.




This page lists the Journal Voucher Entries created by the initiator logged in. Clicking on the Pre-Ledger ID takes you to a screen where you can edit the information. This results in the existing route being cancelled, and the initiation of a new JVE. The new JVE would then start a new routing process.




This is the form to Edit a Journal Voucher Entry. All data fields are edited and all fields will be checked for changes.




This page allows confirmation of an edit to a Journal Voucher Entry. If a field was modified, a message will display showing this.




After completing an edit to a Journal Voucher, the Journal Voucher menu is displayed again, with a message summarizing the results of the edit.




A Journal Voucher Template may also be created. To use this option, choose "Save as Template" on the JVE Entry form. This option saves time so users do not have to re-enter information that is always the same for certain types of JVE's. The Template function is expected to be released as Phase II of this project.




The user is prompted for a description of a new template before it is saved.




A list of templates is available if a user wants to start a JVE from a template rather than start from a blank form. Information will be edited as if entered through the entry screen.




The user may search the JVE Archive in a variety of ways as shown on the Search Options Menu.




To search by MSUNet ID of the JVE initiator, enter their MSUNet ID in the search box.




This page shows results of an MSUNet ID search.




To search archived JVE's by date range, enter the 'From Date' and 'To Date' you wish to search on. You may also specify an MSUNet ID and number of records to return per results page.




This page shows results of a date range search with 'sfarrell' as the MSUDNet ID.




Clicking on any of the search results data will display a Journal Entry Archive Review page showing the detail for that specific JVE.




To search by Pre-Ledger ID, enter the Pre-Ledger ID in the search box.




This page shows results of a Pre-Ledger ID search.




After the JVE has been submitted, the FTU Dashboard notifies approvers via email that there is a JVE waiting for their approval. The JVE appears in the FTU Dashboard Pending Actions list which is the default view when an approver logs into the FTU Dashboard. The following page illustrates a list of pending actions in the FTU Dashboard.




Clicking on the Title of any item in the Pending Actions list will take the user to the Routing Slip Content page. The frame on the right side of this page displays the JVE application's review page. This review page allows the user to see the details of the item they have been asked to approve. The user may simply add a comment, or approve or disapprove with or without a comment.




Entering a comment in the text box and clicking the "Comment Only" button attaches a comment that other approvers will see when they go into the dashboard to review the item.




After a comment has been added, it appears on the Routing Slip Content page just before the JVE's review page where approvers will see it..