Differences

This shows you the differences between two versions of the page.

--- billing:journal [2026/08/18 03:38] – [No TTSTATS Files Are Created] Scott Cunliffe
+++ billing:journal [2026/08/18 03:44] (current) – [See Also] Scott Cunliffe
@@ Line 83: / Line 83: @@
-==== Customer TTSTATS File Is Missing ====
-Confirm that:
-  * The Customer exists in TapeTrack.
-  * The Customer had Journal activity during the billing period.
-  * The Customer-ID is correct.
-  * The extraction covered the complete billing period.
-  * The file was not moved, renamed or archived.
-  * The extraction log does not contain an error for the Customer.
-A missing Customer file may be valid if the Customer had no relevant Journal activity. This should be confirmed before excluding the Customer from billing.
-==== TTSTATS File Is Empty ====
-Check that:
-  * Journal activity exists for the Customer.
-  * The selected date range includes the activity.
-  * The correct production Journal was processed.
-  * The server date and time zone are correct.
-  * The Customer activity is of a type included in the statistics extraction.
@@ Line 120: / Line 98: @@
 If the Journal appears damaged or unreadable, contact TapeTrack Support before attempting repairs.
-===== Backup and Retention =====
-The Journal supports operational history and billing reconstruction and should be included in the Framework Server backup process.
-The backup and retention policy should consider:
-  * Customer contract requirements.
-  * Accounting record-retention requirements.
-  * The ability to reproduce billing statistics.
-  * Audit and dispute periods.
-  * Available storage.
-  * TapeTrack Support recommendations.
-  * Applicable legal and regulatory requirements.
-Retain the following billing records together where possible:
-  * Billing period details.
-  * Journal backup or reference.
-  * Customer ''.ttstats'' files.
-  * Customer Description Map.
-  * Package Map.
-  * Billing Rules.
-  * Stylesheet.
-  * Billing XML.
-  * QuickBooks invoice number.
-  * Processing and approval logs.
 ===== Recommended Practices =====
@@ Line 151: / Line 103: @@
   * Treat the Journal as an authoritative operational record.
   * Do not manually edit the Journal database.
-  * Back up the Journal as part of the Framework Server backup.
   * Use non-overlapping billing extraction periods.
   * Record the exact extraction date range.
-  * Review extraction logs before processing billing.
   * Investigate missing or empty Customer files.
-  * Retain the extracted TTSTATS files with the billing output.
+  * Retain the extracted TTSTATS files with the billing output if required.
   * Restrict database access to authorized administrators.
   * Contact TapeTrack Support before attempting Journal repair.
@@ Line 169: / Line 119: @@
   * TapeTrack administrators.
   * Authorized billing staff requiring access.
-  * The account running ''TMSS10LogStatsExtractDB''.
+  * The account running [[cli:TMSS10LogStatsExtractDB]].
   * The account running authorized backup processes.
@@ Line 178: / Line 128: @@
   * [[cli:tmss10logstatsprocess|TMSS10LogStatsProcess]]
   * [[object:customer|Customer-ID]]
-  * [[billing:customer_ttstats|Customer TTSTATS File]]
+  * [[billing:ttstats|Customer TTSTATS File]]
   * [[billing:customer_map|Customer Description Map]]
   * [[billing:package_map|Package Map]]
   * [[billing:billing_rules|Billing Rules]]
-  * [[billing:tapetrack_xslt|TapeTrack XML Stylesheet]]
+  * [[billing:stylesheet|TapeTrack XML Stylesheet]]
   * [[billing:billing_process|Billing Process]]
   * [[billing:billing_xml|Billing XML]]