Customer Description Map

The Customer Description Map file maps a TapeTrack Customer-ID to a readable Customer name, location, account name, or other billing description.

The map is used by TMSS10LogStatsProcess when processing TapeTrack statistics (.ttstats) files for billing.

The Customer Description Map allows the billing output to include the Customer description, such as New York Data Center instead of just US01.

The Customer Description Map does not define billing rates or determine which billing package applies to the Customer.

The Customer Description Map provides a consistent relationship between the TapeTrack Customer-ID and the description required in billing reports or invoice output.

The file can be used to:

• Display a readable customer or location name in the billing output.
• Associate a TapeTrack Customer-ID with an accounting-system customer.
• Improve the readability of billing XML and reports.
• Prevent internal Customer-IDs from being used as customer-facing descriptions.
• Maintain consistent customer descriptions across billing periods.
• Assist with mapping TapeTrack billing data to QuickBooks Desktop.

The Customer Description Map can be stored in any directory accessible to the account running the billing process.

For ease of administration, it is recommended that all approved billing configuration files are stored in a dedicated directory.

Example Windows location:

C:\Program Files\TapeTrack\TapeTrack Framework Server\etc\billing\customer.txt

Example Linux location:

/etc/tapetrack/billing/customer.txt

The location of the file is supplied to TMSS10LogStatsProcess using the -M argument.

The Customer Description Map is a plain-text file.

Each mapping contains:

• The TapeTrack Customer-ID on the left.
• The customer description on the right.

The general format is:

CUSTOMER-ID  Customer Description

Example:

When a billing record contains Customer-ID US01, the billing processor can use the description New York Data Center in the resulting billing information.

The following example contains two TapeTrack Customers.

customer_map.txt

#
# TapeTrack Billing Customer Description Map
#
# Format:
# CUSTOMER-ID Customer Description
#
 
US01 New York Data Center
US02 Los Angeles Data Center

Lines beginning with a hash character (#) are comments and are ignored during processing.

Comments should be used to document:

• The purpose of the file.
• The expected mapping format.
• Any customer-specific mapping requirements.

Check that:

• The -M argument has been included.
• The specified Customer Description Map file exists.
• The billing account has permission to read the file.
• The Customer-ID is present in the map.
• The Customer-ID matches the value in the .ttstats file.
• The mapping does not contain an unwanted leading or trailing space.

Confirm that:

• The correct Customer Description Map file was used.
• The Customer-ID is not duplicated.
• The mapping points to the intended customer.
• An old copy of the file is not being referenced by the billing script.
• The description matches the approved customer billing profile.

The Customer Description Map may be correct while the XMLQuickBooks mapping is incorrect.

Check both mappings:

1. TapeTrack Customer-ID to billing description.
2. Billing description or Customer-ID to QuickBooks customer.

• Keep the file in a controlled billing configuration directory.
• Use one authoritative Customer Description Map for each billing environment.
• Do not maintain uncontrolled copies.
• Keep descriptions consistent with QuickBooks.
• Restrict write access to authorized billing administrators.

The Customer Description Map does not normally contain passwords or authentication details. However, it may contain customer names and accounting identifiers.

Access should therefore be restricted to:

• TapeTrack administrators.
• Authorized billing staff.
• The service account that runs the billing process.

The file should not be publicly accessible or stored in an unsecured shared directory.

• TMSS10LogStatsProcess
• Adding and Maintaining Customers
• Package Map
• Billing Rules
• Billing Process
• XMLQuickBooks Mapping