Skip to main content

Batches

Important

Information and features vary according to the roles to which you belong and the permissions associated with those roles. For more information, contact your module manager or your campus support team.

This page will allow you to quickly manage all transaction groups, or batches. Depending upon the configurations and your personal permissions in General Ledger, you may be able to view, edit, print edit, summarize, reverse, unlock, delete, and post transactions.

General Ledger Accounting Hub Batch List page.

Tip

Fields and columns will update automatically based on the selected source code.

Jenzabar provides several roles for managing batches, and each role can be associated with different source codes. The table below describes which source codes are associated with each role.

Batch Type

Associated Source Codes

Accounts Payable

Note

These batches are generated in the Procurement Hub.

IM - Immediate check invoices

IV - Regular check invoices

MN - Manual check invoices

RF - Refunds from vendors

VD - Void check invoices

Adjustment

JL - Journal entries

MA - Monthly adjustments

Charge

Note

Some of these batches are generated in the Accounts Receivables Hub.

CG - Student charges (automatically created)

FC - Finance charges

IT - Interest earned

TP - Tuition paid in advance

Conversion

CV - Conversion necessary

Customized

Any custom source codes your school creates.

Development

GF - Development gifts

Disbursement

Note

These batches are generated in the Accounts Receivables Hub.

DB - Disbursements

Financial Aid

FA - Financial Aid

LD - In-House Disbursement

LO - Financial Aid Loan

Fixed Asset

FX - Fixed assets

GST Credits

TX - GST tax credits

Miscellaneous

Note

These batches are generated in the Accounts Receivables Hub.

MS - Miscellaneous transactions

Payroll

FR - Fringe benefits - Payroll

LB - Labor distribution - Payroll

Preliminary

@C - Preliminary student charges

@F - Preliminary financial aid

Receipt

Note

These batches are generated in the Accounts Receivables Hub.

RC - A/R Receipts

Tip

With a few exceptions, the permissions and associations apply to each batch access role.

Permissions and Associations

You'll need to add users to the appropriate batch access roles for each type of batch you want your user to be able to work with.

Note

Users will also need to be in a General Ledger Accounting GL Account access role with access to the GL accounts associated with batch transactions.

Permissions

Each batch role will have similar permissions for how you can work with a particular type of batch.

Each batch role will include all or most of the following permissions:

  • Can view batches

  • Can edit batches and generate Print Edit reports

  • Can create and import batches

  • Can delete batches

  • Can download to Excel

  • Can post batches and generate Post reports

  • Can post batches they created

  • Can unlock batches

  • Can summarize batches

  • Can reverse batches

Batches Generated Outside of the General Ledger Accounting Hub

Batches for certain source codes are generated by processes in the Procurement and Receivables Management hubs. In most cases, batches for these source codes cannot be created in the General Ledge Accounting hub.

  • Accounts Payable batches. Invoice batches (IM, IV, MN) are created when invoices are created or imported from the Procurement Hub. RF and VD batches are created when invoices are refunded or voided. These batches cannot be created in the General Ledger Accounting hub.

  • Charge batches. CG, FC, and TP batches are created when the generate charges, generate finance charges, and transfer student deposits processes are run in the Receivables Management hub. These batches can be created in the General Ledger Accounting hub.

  • Disbursement batches. DB batches are generated when the Create Payment process is run from the Procurement hub. These batches can be created in the General Ledger Accounting hub.

  • Miscellaneous charge batches. MS batches are generated during the Create Miscellaneous Charges process in the Receivables Management hub. These batches cannot be created in the General Ledger Accounting hub.

  • Receipt batches. RC batches are created when receipts are created or imported. These batches cannot be created in the General Ledger Accounting hub.

Module Access

This tab allows you to enable/disable access to different interactions and workflows. Codes are associated with interactions and workflows when they are defined and created. Jenzabar provides access codes based on Jenzabar modules and you can create custom ones on the Access Codes page. If a user belongs to multiple roles, they’ll have access to the interactions and workflows available with each.

Users

Use this tab to see a list of the users assigned to this role. You can add or remove users and view user details

Associations

The Associations tab is only available for select roles and options vary by role. It lets you control access to constituents and information in the system based on the user's relationship to them. Source codes are enabled for what the user should have access to.

User-Defined Fields (UDEF)

The User-Defined Fields tab controls permissions for viewing, editing, and configuring user-defined fields (UDEF) across the system. Users that belong to multiple roles will have access to the user-defined features enabled with each. Use the levels of permissions to determine what users can do with user-defined fields.

Use the filter to expand or limit the batches displayed in the list section. You can also use the filter options to search for a specific batch. Filter options include:

  • Source Code

  • Batch Description

  • Batch Number

  • Status

  • Date Range

  • GL Account Components

  • Created By

  • Created Date Range

  • Posted By

  • Posted Date Range

  • Locked Batch

  • Summarized Batch

The Batch List page allows you to view an manage all the batches you have permission to access. A row exists in the Batch List for each batch of transactions entered into the system and monitors the status of the batch (i.e., posted, unposted, and suspended).

Note

By default, the list is filtered to include batches with statuses of Ready to review (U) and Requires review (S).

There are several ways to interact with batches. Depending on what needs to be done, you can select one or more batches from the list to perform the following options:

  • Post: After transactions have been edited, they can be posted. All transactions must be edited (checked for accuracy) prior to posting them into the General Ledger system. Once a transaction has been posted, it cannot be changed. In order to correct any problems, you must perform a reversing transaction to cancel out the incorrect transaction and then replace it with the correct information.

  • Open: To open a batch and view the batch details, click on the Batch Number. You can also select one or more batch from the list using the checkbox at the beginning of a row, then click the Open button at the top of the list.

  • Download to Excel: This option will allow you to export the selected batches to an Excel spreadsheet. You can keep the spreadsheet as records, to review the batch details, and if you make changes you can upload the edited rows on the Batch Details page.

  • Generate Post Report: This report will display the batches and transaction details that have been posted for the selected batches.

  • Generate Print Edit Report: This report will show you batches and transaction details that you can review to help you make sure all details are correct and ready for posting. If you make changes, be sure to run this report again before the actual posting takes place.

  • Reverse: In order to correct any problems within a posted batch, you must perform a reversing transaction to cancel out the incorrect transaction. This process creates a new batch containing all of the Transaction History rows and cancels out the posted transaction. You will need to replace the incorrect batch with the a new batch that has the correct transactions.

    Warning

    This process cannot be undone.

  • Summarize: This process compiles all transactions within the batch that have the same source code, group number, transaction date, and account code, and summarizes them into one transaction. Summarizing a batch will combine a large number of similar transactions to be reduced in size without impacting accounting results.  It provides fewer unnecessary details and better batch processing time. In order for this to be possible, the account cannot be a subsidiary account and the Summarize checkbox must be selected on the GL Account.

    Notice

    Some General Ledger accounts, such as Accounts Receivable or Tuition Income, contain many student transactions. These transactions can be summarized on reports and windows by group and date. Summarized accounts often share department, such as tuition accounts that often use the same department code.

  • Unlock: When a batch is being used, a temporary lock in the database is created, keeping other people from accessing a batch while it is in use. When the transaction group is successfully finished being used, the lock in the database is released. This option allows you to manually unlock a batch.

    Tip

    This process is mostly used if a process ends abnormally leaving the batch locked. Be careful when unlocking batches. Any unsaved changes by the other user will be lost or may overwrite any changes you make.

  • Delete: If the batch hasn't been posted, you are able to delete the entire batch; however, once posted, the batch cannot be deleted. This process cannot be undone, so be sure you don't need the batch transactions before deleting.

    Warning

    This process cannot be undone.

  1. From the Batches page, select the checkboxes next to the rows of the batches you want to view details for.

  2. Click the Open button.

  3. When the Batch Details page opens, you will see the Select a Batch switcher at the top of the page. This switcher will allow you to move through the Batch Details pages for the batches you selected.

    Batch_Switcher.jpg
    • The Edit Edit Icon icon will allow you to add or remove batch numbers that are included in the switcher.

    • The arrows will allow you to move between the included batches.

    • The text in the switcher will let you know which batch you're viewing and how many batches are included.

  4. Move through the batches as needed. When you're finished, you can close the Batch Details page.

  1. To create a new general ledger batch, select Create batch from the Hub options drop-down or click the Create batch button on the Manage Batches page. A details spreadsheet with no information filled in displays.

  2. From the Source Code drop-down, select a source code.

  3. Enter a batch Description (optional).

  4. Enter the batch Date.

  5. Enter batch transactions into the details spreadsheet. Columns include:

    • Transaction Amount

    • GL Account Number

    • GL Account Description

    • Transaction Description

    • Transaction Date

    • Folio

    • Project Code

    • Project Description

  6. Click Create batch.

    Tip

    After a batch is created, the batch details page will open. From there you can edit and maintain the batch information. To create another batch go to Batch options and click Create.

Tip

For the summary option to work, the included accounts cannot be subsidiary accounts and the Summarize checkbox must be selected on the GL Accounts page.

  1. Select the checkboxes next to the row of the batch you want to summarize.

  2. Click the More drop-down and select Summarize.

  3. In the Summarize Batches pop-up window, you will see the selected batches listed in one of two sections:

    • Ready to Summarize: batches listed in this section will be summarized into a single transaction. You may notice a warning icon at the end of a batch row, which indicates that only part of the batch will be summarized.

    • Unable to Summarize: batches listed in this section could not be summarized. There will be an alert icon at the beginning of the batch row that will list why the batch couldn't be summarized.

  4. Click Yes, summarize.

    Tip

    If none of the selected batches can be summarized, you will see an OK button instead of the Yes, summarize.

  1. Select the checkboxes next to the row of the batch you want to reverse.

  2. Click the More drop-down and select Reverse.

  3. In the Reverse Batch pop-up window, select a new source code for the batch and write a brief description of the batch.

    Note

    The original source code and batch number values will be entered by default. The new batch number is auto-generated by the system.

  4. Click Yes, reverse.

  1. Select the checkboxes next to any rows you want to unlock.

  2. Click the More drop-down and select Unlock.

  3. In the Unlock Batches pop-up window, you will see the selected batches listed in one of two sections:

    • Ready to Unlock: batches listed here will be unlocked and made available to yourself and others. Be sure to check the User column and communicate with the user currently using the batch so they won't lose work or overwrite your content.

    • Unable to Unlock: batches listed in this section could not be unlocked.

  4. Click Yes, unlock.

  1. Select the checkboxes next to the rows you want to export.

  2. From the Options drop-down, select Download to Excel. The Download to Excel pop-up opens.

  3. Select options for the Excel format and data columns.

  4. Click Download. Your .xlsx or .zip file is saved in the file location that you have set in your browser settings.

  1. Select the checkboxes next to any rows you want to include in the Print Edit report.

  2. Click the More drop-down and select Generate Print Edit report.

  3. In the Generate Print Edit Report pop-up window, you will see the selected batches listed in one of two sections:

    • Ready to Generate: batches listed in this section will be included in the Print Edit report.

    • Unable to Generate: batches listed in this section will not be included in the Print Edit report.

  4. Click Yes, generate.

Warning

When you're ready to Generate Post Report for selected batches, be sure you're including no more than 30 batches at a time to prevent system errors.

  1. Select the checkboxes next to any rows you want to include in the Post report.

  2. Click the More drop-down and select Generate Post report.

  3. In the Generate Post Report pop-up window, you will see the selected batches listed in one of two sections:

    • Ready to Generate: batches listed in this section will be included in the Post report.

    • Unable to Generate: batches listed in this section will not be included in the Post report.

  4. Click Yes, generate.

  1. Select the checkboxes next to the row of the batch you want to delete.

  2. Click the More drop-down and select Delete.

  3. In the Delete Batches pop-up window, review the list of selected batches.

    Warning

    The delete process cannot be undone. Review the selected batches carefully.

  4. Click Yes, delete.

A journal entry records financial data for business transactions. It provides an audit trail and helps determine the effects of a transaction on an institution's financial position when it is posted to the General Ledger. A journal entry consists of at least one credit and one debit transaction. It can include multiple transactions, and the number of credit transactions does not have to match the number of debit transactions; however, the total debit amount must equal the total credit amount (i.e., the entry must have a zero net balance).

Batches (also called "transaction groups") are collections of one or more journal entries that encompass a specific time period (e.g., week or month) and are processed at one time. The net total of debit and credit transactions in a group must equal zero.

Each batch is assigned a source code. The source code identifies the office in which the transactions were generated and/or the type of transactions within the group (e.g., financial aid or purchase orders). Jenzabar provides several source codes, and the one needed for this process is "JL", which is used for journal entries entered in the general ledger.

Different status codes indicate the stage each transaction or transaction group is in. The status code updates automatically when certain system actions or processes are performed.

When batches are posted, the following occurs:

  • The amount of the transaction is applied to its account balance and is reflected in the General Ledger Account Master table.

  • The Post Transactions report is printed listing each transaction in the group.

  • The transaction status becomes current (C), no longer appears on the window, and becomes part of the month in which it was posted.

Some functions in the General Ledger system create transactions for each student.  For example, when you generate tuition charges for a student, the system creates one debit to the Accounts Receivable account and one credit to the Tuition Income account. While these transactions are necessary, they often provide more detail than required. For this reason, you can choose to summarize entries for selected accounts

Yes, Created By and Posted By are fields that are being populated and display on the Batch List page as well as within the Batch as you view the details. They are also clickable links to open that person's Summary page so you could send them a communication if needed.

You can't. Miscellaneous batches are created in Receivables Management. With the proper permissions, you can create and manage a MS batch from the Miscellaneous Charges page. MS batches can also be viewed and edited on the Batches page in the General Ledger Accounting hub.

When creating or editing a batch, be sure all the required fields are correct and there is at least one transaction in the batch.

A batch will be locked when an approved user selects one or more batch from the Batch List and clicks one of the following options:

  • Post

  • Summarize

  • Reverse

  • Delete

Any batches that appear in the Ready to... section will be locked to other users until the action is complete. If the user becomes inactive before the action is complete, the batches will be locked for 30 minutes, then become unlocked for use.