SalesSummary Report

Aside from a few of its supplementary figures, all data in this report comes directly from the SalesJournal (accessible in terms of its raw entries via the SalesRead form, quickkey shortcut is F4).  In other words, to produce this report, ServiceDesk reads directly from applicable records within that file/journal, tabulates the results, and displays them to you.

The main body of the report is divided into four columns.  The first column tabulates the total of Paycode 1 and Paycode 2 SalesEntries, and is intended to display totals for work actually completed during the period (regardless of whether paid or not).  The second column tabulates the Paycode 1 and Paycode 3 SalesEntries, and is intended to show the total of work paid for in the period (regardless of when actually completed).  The third column is, simply, the total of Paycode 2s, and fourth of Paycode 3s (these columns are there for review if wanted, but it’s typically the first or second that you’ll pay most attention to).

The second section applies a series of adjustments to work out such matters as true total of money received, changes in A/Rs, and so on.  This adjustment process is needed because the SalesJournal, in and of itself, only reflects money received when the entirety of a sale is paid.  A/Rs, in turn, may be partially paid, but that fact does not show in the face of any SalesJournal entry.  To make the adjustments as applicable in this section (and arrive at the figures provided), ServiceDesk augments it’s reading of entries in the SalesJournal with reading of entries in the Applications Journal (quickkey shortcut is Alt-F9).

You’ll note there is an option to either display on-screen or print this report.  If you take the option to print, you’ll have a further option to include line-by-line entries, concerning each sale that went into the report.  That option simply is not present if electing to display on-screen.

There are also several Export options associated with this report—accessible via buttons that appear when the report is displayed.

One matter of occasional confusion concerns the section in the report where there is a distinction between “ServiceCalls” and “Tickets.”  Basically, each entry in SalesJournal represents a “ticket,” so far as any applicable column of display is concerned.  The intent is to classify the entry also as a “service call” if it is an entry reflecting in-field service (as opposed to POS activity), and if it’s the first (typically only) such entry as applicable on a given job.  In other words, we want to exclude (as defined “service calls”) entries if they involve going back (for recall or continuation work) after the initial work was supposedly completed.

The actual method that’s used in effort to achieve the above outcome is as follows:

  1. ‍If the S.Call amount column in the SalesEntry is unequal to zero, the entry is tallied as a ServiceCall.
  2. ‍If the Name column is in the form XX-Xxxxx (as in, say, WP-Smith), and if the Labor amount is at least $60, the system tallies the entry as a ServiceCall.  The logic here is that for warranty work it’s common to leave the S.Call field blank, and to put all labor in the Labor field.  Thus, if from the Name field it appears to be a likely warranty client, and from the amount in the Labor field it appears it was likely the entry on a job that reflected charging for the totality of the repair, the entry is tallied as an S.Call.