Navigating the Journal Entry

When you click on the Journal Entry tab, a secondary browser tab will open. Your IBEX tab will remain open, but this tab may time out after some time.

Note: Depending on what tab you are currently viewing from in IBEX, you may not see the Journal Entry tab appear at the top of your screen. Return to the Home tab to access the Journal Entry tab if needed. 

You will see there are 3 main tabs in the Journal entry:

Pay Runs

This screen will show all Posted pay runs from a particular Start Date. Use the Date Filter in the top left corner to control what pay runs are shown, then click Apply. *Note: The table will show a maximum of 2 years worth of pay runs. 

You can Run/View Journal Entry results by clicking on the check box beside a Pay Run that has not yet been Posted, then click the Run/View JE button in the top right hand corner. You can run multiple Journal Entries for more than one pay run at a time, however the pay runs selected need to be in consecutive order (ie. you can not skip any pay runs in between). For previously posted pay runs, you can only click the View Posted Results button.

Note: There must be an available JE in the Versions tab with an effective date on or before the pay run you are selecting in order to Run the JE, otherwise you will see "No Version Exists" in the Config Version column for that pay run and the "Run/View JE" and "View Posted Results" buttons will be unavailable.

Versions

You will create your first Journal Entry Version from this screen, and add new versions if needed.

Once a new Version is Published, the previous Version status will be set to Expired and can no longer be edited.

General Ledger Codes

Before you can add a Journal Entry Version, you will need to set up the organization's General Ledger codes in this tab. Select the Add New button to add GL Codes. Once added, GL codes can be Edited, Deleted, or Disabled.

Note: GL Codes must contain numbers or a mix of letters and numbers. Plain text codes are not valid. If a dash (-) is used, both sides of the dash must independently meet this rule. For example, 123-AccountName is invalid, but 123-100AccountName or 100-Account1 would work.