About Initializing T&M Billings
To initialize T&M billings, contract items must be set up as ‘T&M’ or ‘Both’ bill types in JC Contract Items.
You must have selected one of the following options in the Initialize Option field in JB Billing Initialization:
B-Progress (P) and Both (B) Items – Initialize (B) Items as T&M
T-T&M (T) Items Only
You can initialize billings by contract range or by processing group. If you initialize by contract range, you can initialize a single contract or a range of contracts. If you initialize by processing group (defined in JB Processing Group), the system generates billings for all contracts assigned the specified processing group. If there are customers assigned to a processing group, initialization processes those billings first using the template assigned to the customer in JB Processing Group. Customer billings have a bill header and lines, but no Job Cost detail. (You will typically use these types of billings for monthly maintenance billings or other non-job related billings.)
You also have the option to restrict initialization by the item bill group assigned to contract items in JC Contract Items. Initialization will include only those contract items with a bill group matching the one specified here. See Related Topics below for more information on Bill Groups.
If you are using the Field Tickets feature, use the T&M Field Tickets drop-down to specify whether to include or exclude cost detail associated with approved field tickets. You can also specify an Approval Cutoff Date to control which approved field tickets are included. Once initialization is complete, cost detail records associated with field tickets are displayed in the JB T&M Bill JCDetail By Seq grid.
Use the T&M Job Cost Detail Transaction Range section to specify a beginning/ending cost detail date, and a cost detail cutoff month. These dates identify the dates/month through which cost detail will be pulled from Job Cost to include on billings. You may enter date in one or all of these fields. If you make an entry in all fields, the cost detail record must meet all requirements in order to be included in the invoice generating process.
For example, you make the following entries:
Cost Detail Beginning Date: 06/01/09
Cost Detail Ending Date: 06/30/09
Cost Detail Cut-Off Month: 06/09
The system will include all costs dated 06/01/09 through 06/30/09 that were posted through period 06/09. Any costs posted between 6/1/09 and 6/30/09, but assigned to a month later than 06/09 (e.g. 07/09) will not be included in the billing.
If you will be using a different cutoff date for labor detail, check the Use Different Labor Cutoff Date box and then specify the labor cutoff date.
If you are initializing both progress and T&M items (Initialize Option B), use the Progress Billing Date Range section to specify the beginning and ending bill date for the billings processed as progress. (Note: These dates are informational only and do not control the data included when initializing billings. For example, you might use these dates to identify the range this billing covers.)
Once you have entered the selection criteria, click the Initialize Bill button to begin the initialization process. During initialization, the system uses the template assigned to the contract in JB Contract Info to compile the appropriate cost data from the JC Cost Detail table (JCCD) based on the template specifications, and stores it in the JB files. This detail prints according to the invoice format you have created using Crystal Reports, or from any of the standard formats provided with Vista™ by Viewpoint. If you are processing both progress and T&M (option B), the system will calculate billable amounts for ‘P’ items based on completed progress and costs in Job Cost. For more information on initializing progress billings, see Related Topics below.
If the system encounters errors or problems during initialization, you will receive a message indicating that errors were found and telling you to run an error report (report suggested will depend on the errors). You will need to correct the errors and then rerun initialization as necessary. See Running the Error Report below for more information.