TariffShark Tiger User Guide

Not your version?

Company

A Company in TariffShark is a FERC-regulated entity for which electronic tariff filings are made. In order to make electronic tariff filings with FERC, a company must be registered. This is not a function of TariffShark but is an important prerequisite. Once registered, FERC will assign a company identifier and a password which are used to make electronic tariff filings.

In TariffShark, you may create a Company only if the company has a valid TariffShark license. The name you enter when creating the Company must exactly match the name in the license. A company can have one of three types of licenses:

Company Name Changes

Sometimes acquisitions or restructuring can cause FERC-registered companies to change their official company name. Consult with FERC resources like Instructions for Company Registration regarding how to officially and legally change FERC company identifiers including Company Name. Since TariffShark is licensed by Company and can insert headers and footers (which may contain the name of the licensed Company) into your tariffs, any changes in Company Name must be addressed so that the software can officially and legally reflect that name change.

There are several ways that a Company Name can be changed in TariffShark. Please refer to our blog article How to Change Company Name for more details. You may wish to consult with TariffShark Support to help guide your decision:

TariffShark Tiger makes it easier than ever to update the Company name in TariffShark while preserving your existing headers and footers and using the new Company name on headers and footers prospectively only. If you choose this approach, TariffShark Support will need the following information in order to provide complete service:

  1. Current Company Name
  2. New Company Name
  3. Id of Company row to be updated
  4. Username of User requesting the update (an actual user of the software). Customers are encouraged to provide the Username of a regular TariffShark user because any TRVs that get queued for content processing will be tied to the Software Client associated with that User's most recent Login session.

See Also

FORMS

ELEMENTS