A batch is a group of like transactions.

Imagine receiving a bunch of timesheets. You enter them into the system, put a rubber band around them, and store them in a file. When you need to look at a specific timesheet, you go to the file, pull out the rubber-banded group, and find the one you want to view.

Now, replace the concept of a rubber-band with the word "batch" and you begin to understand the concept.

When you enter transactions into the system, you enter it into a group (or batch). All of the transactions in the batch are grouped together. If you want to edit a transaction before it is posted, you would find the batch and then find the transaction within the batch.

No. A batch is a group of like transactions.

Thus, you can have a batch of timesheets or you can have a batch of A/R payments, but you can't have a batch of timesheets AND A/R payments.

No. Each Timesheet Batch is associated with a single pay frequency (whether Annually, Bi-Weekly, Daily, Monthly, Quarterly, Semi-Monthly, Semi Annual, or Weekly).

If you pay your employees at different pay frequencies, create a different Timesheet batch for each different pay frequency.

No. A batch may contain 1 transaction or hundreds of transactions. Therefore, it is flexible enough to fit your needs.

Keep in mind, that batches are treated like a whole unit. Therefore, batches are proofed and posted as a whole. If you have 1000 transactions in a batch, all transactions are proofed and posted at the same time.

There are advantages and disadvantages to placing a large number of transactions into a batch. On the plus side, it is easier to post one batch of many transactions than it is to post many batches of few transactions. On the minus side, the system produces diagnostic reports when proofing and posting batches. Having fewer transactions in the batch makes it easier to find where the problems lie.

You will need to decide for yourself which is more comfortable to you.

StaffSuite supports the following transaction types:

• A/R Adjustments

• A/R Payments

• Balance Forwards

• Bank Transactions

• Position Billing

• Timesheets

• Vendor Pay

• Void Payroll Checks

• Void Vendor Check

Yes. In fact, that's one of the great advantages of working with batches.

You can enter timesheets while another person is entering timesheets (in a different batch) and another person is entering payments. Batches insure that you won't "step on each other's toes".

A batch simply insures that what you are doing is not impacted by what someone else is doing (and vice-versa).

No surprises. No accidental deletions. No worrying about what someone else is doing.

Yes. On the Batch Control Basic window, there is a Delete Batch button. Clicking on this button deletes the batch. However, a couple of rules apply.

First, for each type of batch (except timesheets), you may NOT delete a batch that has associated transactions. If you want to delete a batch with associated transactions, you should delete each transactions and THEN delete the batch.

Second, for timesheets, you CAN delete a batch and its associated timesheets, but you have to list the timesheets before doing so. Simply, display the Batch Control Basic window and click the List Transactions button. Once the timesheets are listed, the Delete Batch button will become active. Clicking on it deletes the batch AND all associated timesheets.