This entry sets the defaults associated with this function used for billing Work Orders associated with Service Compute type jobs. Start Compute Service Invoice
Testing Your Registry Entries
The system does not verify the validity of registry entries. Be sure to test your registry entries after completing them to verify that they are functioning correctly.
Setting Values are Uppercase-Lowercase Sensitive:
The Setting Value is case-sensitive: be sure that you enter the value exactly as specified in the documentation. If the documentation specifies a value of true, do NOT enter True or TRUE.
Data Conversion Notes from 7.0.
Work Order Override:
If a Billing Address Id is specified in the Work Order, that record will override both the Job Billing Address Id and the Invoice Address/Invoice Email Address in the Job record.
Invoice Email Address in the Job Record:
If the auto-emailing of service invoices is enabled, the system will email invoices to this address unless this field is overridden by the Billing Address Id in the Job or Work Order record.
Registry Entry Report Service Invoice
See Specify Override Bitmap by Site's Account Manager, Service Manager, Dispatcher or Branch for details on implementing this functionality.
Registry Entry for Report Graphics, Max Lines Per Page and Autosave
Id: sys-start-ssrvcebllngcmpte
See the Standard Registry section in Registry Viewer for additional Registry Id formats to allow entries for specific Users, Branches, Security, or User Groups to override the main entry.
The following registry entry may be enabled to provide a possible performance enhancement for the Start Service Billing Compute function:
Setting Key: CostOrRevenueFilter Setting Value: true (default is false)
Note: this registry eliminates JOB EOM transactions from the calculation; this may or may not impact the performance of Start Service Billing Compute.
When Start Compute Service Invoice run ‘wide open’, old work orders that will never be billed may be included in the process, negatively impacting performance. In this enhancement, it is easy to exclude archived work orders from the Service Worksheet / Service Invoice starter functions in order to improve performance. Note that Work Orders may be set to Archived by manually adding a Technician line with status Archived, or by using the Start Archive Work Orders or Start Autoarchive Work Orders.
The Work Order Status Category in the Start Compute Service Billing and Start Computer Service Worksheets should be set to exclude archived work orders (!=archived) using the following settings:
Setting Key: InitialValueFor~wrkordr.stts-ctgry Setting Value: !=archived
Note that a similar entry should also be made for Start Service Billing Worksheet:
Id: sys-start-ssrvcebllngwrksht
Setting Key: InitialValueFor~wrkordr.stts-ctgry Setting Value: !=archived
An option to show Service Invoice detail info by Equipment is available. If the Work Order lines are not associated with an Equipment record, charges will be grouped under the heading Equipment: none specified. The following registry entry must be created to use this mod:
Setting Key: ShowDetailByEquipment Setting Value: true
Note that this functionality is only exhibited if the Equipment Detail option is set to Yes in the Service Invoice. It is suggested that the following option be set via the initial values functionality so that the Equipment Detail option is set to Yes by default:
Id: sys-start-ssrvcebllngcmpte
Setting Key: initialValueFor~srvceinvce.eqpmnt-dtl Setting Value:On
Setting Key: AutoReleaseHeldVouchers Setting Value: true
This registry option is related to ’Approval Required’ vendor invoices that are associated with service invoices. If this registry entry is not implemented, it is necessary to run the Start AP Payment Approved List function to approve AP transactions for payment that were created referencing an AP Term with the Requires Approval box checked. However, by implementing this registry option, running the Service Billing Compute function will automatically approve the ‘Requires Approval’ vendor invoices associated with the Service Invoices that you post.
Setting Key: ReportIdInvoice Setting Value: serviceinvoice_customreport
This option sets the report id of the service invoicing report called by the function (normally, this report is specified in the job and job billing item records). If your firm has switched to a custom service invoice report, replace serviceinvoice_customreport with the custom report Id; this way it is not necessary to change all the report id’s in all your jobs and billing items. Note, however, that the Report Query Id in the Job / Job Billing Item records will still be used. Therefore, if this field has been changed in your custom report, the Job / Job Billing Item records must be changed to reflect this.
Setting Key: PostReportId Setting Value: serviceinvoicepost
This option sets the posting report id of the service invoicing report called by the function. If your firm uses a custom service invoice posting report, replace serviceinvoicepost with the custom report Id.
Setting Key: DefaultDo Setting Value: true
Implementing this registry option defaults all the Do fields in the Service Compute Checklist to checked (selected). If this option is not implemented, no work orders will be selected when the checklist screen appears.
Setting Key: orderby Setting Value: sql
this option, if present, configures the Service Compute Check List. It requires a custom sql string; contact your support representative for additional information.
By default, COD Invoices are posted to both the AR Sales Journal AND the AR Cash Receipts Journal. The following registry setting may be used to restore the old behavior (just post to AR Sales): however, this also doubles the WO's COD child tab (the parent may still be used).
Setting Key: UseSJForCOD Setting Value: true
WARNING: This registry option should NEVER be set if Quotemaster is used or if a user might EVER flag a work order line as quoted. This registry entry sets the WO Ready-to-Invoice flag set to false (unchecked) during the Service Invoice Post for each invoiced WO having Date Closed <> '1900-01-01':
Setting Key: ClearInvoiceReadyForClosedWOs Setting Value: true
This release adds the ability to append TechAnywhere receipts or other documents to the PDF'd version of Service Invoices. This allows an Invoice Package to be automatically emailed to customers configured to receive Service Invoices via email. Supported document attachment file types include: .bmp, .jpg, .gif, .png, and .pdf. This functionality is suitable for scenarios where a Work Order is only invoiced once.
Important: Only the PDF'd Invoice Includes the Attachments
The .dbr version of the Service Invoice will not display the attached documents; it will however include a list of attached files. Only the PDF'd version of this document will include the 'package' of document attachments.
To enable this functionality:
1. The revised Service Invoice serviceinvoicev90b028.rpt dated 2016/02/16 or later must be installed in your database.
2. The Client Site Email Invoices field (a-clntste: clntste.eml-invce) must contain a list of the Document Categories which should be included in the Invoice Package. The included documents must be attached to the Work Order being invoiced prior to the generation of the invoice. Any documents attached to the Work Order after an invoice is generated will not be included in this package.
For example, to include TechAnywhere Receipts in the Invoice Package for a particular Site, you would enter Receipt in its Email Invoices field.
3. Verify that the xmlToPdf.jar file (located in the same directory as your SAMPro executable) is dated 2015/07/08 or later.
4. Implement the following registry entries:
Id: sys-start-ssrvcebllngcmpte:
Setting Key: IncludeInvoiceDocuments Setting Value: true (default false)
This option is required to implement the new 'package' functionality.
Setting Key: SkipPrintEmailedInvoices Setting Value: true
Implementing this registry allows emailed invoices to be 'skipped' in the print run. Processing will proceed as usual: the Invoices will be displayed and sent to the printer; the user must then confirm that the invoices have printed and post them. However, only those invoices that were not emailed will actually be printed.
Id: sys-report-serviceinvoice:
Setting Key: sectionbackerbitmap Setting Value: Pathname\whitesquare.bmp
This registry is recommended to prevent the invoice bitmap from 'stepping on' the attached documents. The bitmap may be obtained from support.
Setting Key: ShowDocumentDescription Setting Value: Y
This option should be enabled to display the Document Description of the attached graphic document on the upper left-hand corner of the page. Note that the attachments themselves (along with the Description) are only shown when the invoice is PDF'd.
The following registry option enables the users to skip the physical printing of zero dollar service invoices. If this registry is enabled:
Zero dollar invoices will still be processed and 'posted' along with the batch.
No paper forms should be printed.
Auto-saving should still happen.
IMPORTANT: This functionality also requires the revised Service Invoice serviceinvoicev90b028.rpt dated 2016/02/16 or later.
Id: sys-start-ssrvcebllngcmpte
Setting Key: SkipPrintZeroInvoices Setting Value: true (default is false)
The revised Service Invoice Report (SERVICEINVOICEv90b028) dated 2016-11-11 and this release support registries to skip printing and/or emailing service invoices with a negative total.
Id: sys-report-serviceinvoice
Setting Key: SkipEmailNegativeInvoice Setting Value: Y (default is N)
Id: sys-start-ssrvcebllngcmpte
Setting Key: SkipPrintNegativeInvoices Setting Value: true (default is false)
Registry entries may be used to clear the default initial values when running Compute Service Invoice. This allows the Billing Agent User Id range to be automatically cleared when running this function. Previously, the User Id of the user running the function would always be written to the Service Invoice report range screen.
Registry Id: sys-start-ssrvcebllngcmpte
Setting Key: initialValueFor~usr.id Setting Value:
Note that the Setting Value is blank in this case.