Subsidiary Group Example

Since subsidiary groups control the statement and update process, there are several ways of running statements using subsidiary group codes. Jenzabar recommends that you define a few subsidiary groups and then add groups as needed. You can begin with subsidiary groups similar to the ones in this example: one subsidiary group for statements (ST), one for non-statement subsidiaries (DD), and one for all subsidiaries (AL).

Below is a sample subsidiary group.

If we want to run monthly statements that omit or exclude the Damage Deposits account, the table below shows the subsidiary group code that would be used for these statement runs.

Since the Damage Deposit account is omitted from the monthly statement run, the status codes of the Damage Deposit transactions will not get updated. Therefore, we need at least one subsidiary group that contains the Damage Deposit account. We could create the following subsidiary group and use it to occasionally close the Damage Deposit transactions.

A subsidiary group that includes all of the subsidiary accounts could be created and used to occasionally print statements or register for all subsidiary accounts.