TariffShark Tiger User Guide

Not your version?

Filing Validation Rules

The following validation rules are verified when a user validates a Filing prior to submitting the Filing to FERC.

Rule Id Description Type Message
A001 Attachments that are provided must include a file name. Fail The file name for FERC Attachment "<Attachment.Description>" is missing.
A003 Required, non-waivable attachments must be provided. Fail The content for FERC Attachment "<Attachment.Description>" is missing.
A004 Required, waivable attachments must either be provided or a waiver requested. Fail The content for FERC Attachment "<Attachment.Description>" is missing.
A005 Attachment content cannot be larger than 50MB. Fail The content for FERC Attachment "<Attachment.Description>" is <file size in MB> in size, which is larger than the 50MB maximum allowed by FERC.
A006 Required, waivable attachments cannot be both provided AND waiver requested. Fail The content for FERC Attachment "<Attachment.Description>" has been provided and waiver is also being requested. This is ambiguous.
A007 Filing Validation Rule: Attachment Security Level is active on Filing Date. Fail The security level selected for FERC Attachment "<Attachment.Description>" is not valid for filing date <filingDate.Value.ToShortDateString()>.
A008 Filing Validation Rule: Attachment content type is active on Filing Date. Fail The content type (<file extension>) of FERC Attachment "Attachment.Description>" is not valid for filing date <filingDate.Value.ToShortDateString()>.
A009 Transmittal letter attachments must be named "Transmittal Letter". Fail FERC Attachment "<Attachment.Description>" is an attachment of type "<Attachment.AttachmentReferenceCode.Description>". You must submit it with a Description of "Transmittal Letter".
A010 FERC Attachment file name cannot be longer than 60 characters. Fail The file name "<Attachment.AttachmentFileName>" that belongs to FERC Attachment "<Attachment.Description>" is longer than the 60 character maximum.
A011 FERC Attachment Description cannot be longer than 80 characters. Fail FERC Attachment "<Attachment.Description>" has a description that is longer than the 80 character maximum.
A012 Within a Filing, the combination of attachment file name and attachment security level must be unique. Fail There is more than one FERC Attachment with file name "<Attachment.AttachmentFileName>" and security level "<Attachment.SecurityLevel.Description>" in this Filing. The combination of file name and security level must be unique within a Filing.
A013 For every attachment in a Filing that is provided with a non-Public security level a version must also be provided with a Public security level. Fail When FERC Attachment "<Attachment.AttachmentReferenceCode.Description>" is provided with a security level of "<Attachment.SecurityLevel.Description>", a Public version of the attachment must also be provided.
A014 FERC Attachments must have an associated Attachment Content Type. Fail The content type (<file extension>) of FERC Attachment "<Attachment.Description>" is not valid.
A015 FERC Attachment file name cannot contain any of the following characters: ? / *  " ' > < Fail The file name "<Attachment.AttachmentFileName>" that belongs to FERC Attachment "<Attachment.Description>" contains one or more invalid characters.
A016 Optional attachments that are provided must include content. Fail FERC Attachment "<AttachmentReferenceCode.Description>" has no content.
A017 Optional attachments that are provided must include a file name. Fail FERC Attachment "<AttachmentReferenceCode.Description>" is included in this filing but a file name has not been provided.
C001 Verify that the Company's FERC Id matches the expected FERC-established format. Fail The FERC Id for <Company.Name> is in the wrong format. It must start with an upper case "C" and be followed by six digits. For example, C001234.
F001 A Filing is typically in "Draft" Status when XML is generated. Warning The status of this filing indicates that it has already been filed with FERC. Generating the XML now is out of the ordinary.
F002 The FERC Response for every FTRV in a Filing is typically "Draft" when XML is generated. Warning This filing contains n Filed Tariff Record Versions with a FERC Response that indicates that they have already been filed with FERC. Generating the XML now is out of the ordinary.
F003 Some Filing validations are date effective. Therefore, FERC Filing Date is required. Fail The Filing cannot be validated because the Date Filed has not been provided.
F004 Make sure the Filing Type selected for the Filing is "in effect". Fail Invalid Filing Type. You must create a new filing with a valid Filing Type, move the Tariff Record Versions over to it, and recreate the FERC Attachments.
F005 Within a Tariff Database, there can be only one Filing filed where the Filing Type is New or Refiled-type. Fail Invalid Filing Type - a New or Refiled filing has already been filed with FERC. You must create a different filing with a valid Filing Type, move the Tariff Record Versions over to it, and recreate the FERC Attachments.
F006 Within a Tariff Database, a Filing of any non-New and non-Refiled-type cannot be filed until one has been filed where the Filing Type is New or Refiled-type. Fail Invalid Filing Type - a New or Refiled filing must be filed with FERC before you can file this Filing. You must create a different filing with a New or Refiled Filing Type, move the Tariff Record Versions over to it, and recreate the FERC Attachments.
F007 When making an Amendment-type Filing, Associated Filing Id or Override Associated Filing Id is required. Fail When making an Amendment filing, you must specify the filing with which your filing is associated.
F008 When making an Amendment-type Filing, the associated Filing must have a Status of "Filed". Fail When making an Amendment filing, the associated filing must have a status of "Filed" thus indicating that FERC has not yet acted upon it.
F009 When making a Motion-type Filing, Associated Filing Id or Override Associated Filing Id is required. Fail When making a Motion filing, you must specify the filing with which your filing is associated.
F010 When making a Motion-type Filing, the associated Filing must have a Status of "Filed" or "Complete". Fail When making a Motion filing, the associated filing must have a status of "Filed" or "Complete" thus indicating that it is on file with FERC.
F011 Tariff Database Title is required. Fail The Tariff Database Title is missing.
F012 Tariff Database Title cannot be longer than 100 characters. Fail Tariff Database Title is longer than the 100 character maximum.
F013 Filing Title is required. Fail The Filing Title is missing.
F014 Filing Title cannot be longer than 80 characters. Fail Filing Title is longer than the 80 character maximum.
F015 Filing Validation Email address is required. Fail The Filing Validation Email address is missing.
F016 Every attachment must include a Description. Fail One or more FERC Attachments are missing a Description.
F017 Schema Version 1 requires that there is at least one attachment. Fail FERC's eTariff XML schema requires that there be at least one FERC Attachment.
F018 When making a Withdraw-type Filing, Associated Filing Id or Override Associated Filing Id is required. Fail When making a Withdraw filing, you must specify the filing with which your filing is associated.
F019 When making a Withdraw-type Filing, the associated Filing must have a Status of "Filed". Fail When making an Withdraw filing, the associated filing must have a status of "Filed" thus indicating that FERC has not yet acted upon it.
F021 If the type of filing rules stipulate that a Suspend Motion Response is required, then the question must be answered. Fail You must specify for FERC whether or not suspended Tariff Record Versions should be made effective automatically after a suspension period.
F022 If the type of filing rules stipulate that a Filing Fee is required, then a Payment Confirmation Code must be provided for the Filing Fail A payment confirmation code is required for this filing.
F023 When making a Report-type Filing, Associated Filing Id or Override Associated Filing Id is required. Fail When making a Report filing, you must specify the filing with which your filing is associated.
F024 When making a Compliance or Refiled-type Filing, the associated Filing is optional, but if specified, the associated Filing cannot have a "Draft" Status. Fail When making a Compliance or Refiled filing, the associated filing, "<AssociatedFiling.DisplayName>" in this case, cannot have a status of "Draft" as this indicates that the associated filing has not been filed with FERC.
F025 When making a Compliance or Refiled-type Filing, the associated Filing is optional, but if specified, the associated Filing should not have a "Draft" or "Filed" Status. Warning When making a Compliance or Refiled filing, the associated filing, "<AssociatedFiling.Title>" in this case, should have a status of "Complete" as this indicates that FERC has acted on the associated filing.
F026 Withdraw-type Filing must contain zero FTRVs. Fail A withdrawal filing must not contain any Tariff Record Versions.
F027 When making a Withdraw-type Filing, the associated Filing cannot be a Withdraw, Motion, or Report-type Filing. Fail When making a Withdraw filing, the associated filing cannot be a Withdraw, Motion, or Report filing.
F028 Warn user if a Motion-type Filing contains any FTRVs that relate to a TRV where content is present. Warning You cannot propose textual or content changes to a tariff within the context of a Motion filing. If this filing contains textual or content changes, they will not be sent to FERC in the XML.
F029 Associated Filing Id or Override Associated Filing Id is invalid when making New, Normal, and Cancel-type Filings. Fail When making a Normal, New, or Cancel filing, an Associated Filing is not typically sent to FERC. You have associated this Filing with the Filing "<Filing.AssociatedFiling.DisplayName> or <Filing.OverrideAssociatedFilingId>". Please use caution in your submission of this Filing.
F030 It is invalid for an Amendment-type Filing to have a Compliance, Refiled, Motion, Withdraw, or Report-type Filing as its associated Filing. Fail You have associated this Amendment filing with filing "<Filing.AssociatedFiling.DisplayName>". Amendment filings cannot amend Compliance, Refiled, Motion, Withdraw, or Report filings.
F032 Option Codes must be provided in complete sets. This is straightforward for change type CHANGE. For change type NEW, FTRVs may appear in some option sets and not others, so NEW is omitted from this validation. For change type CANCEL, a Tariff Record could be cancelled in one change set and untouched in another, so CANCEL is omitted from this validation. Change types WITHDRAW and PRO FORMA are not subject to option set restrictions. Fail Option sets must be complete. If a filing includes an Option B, then every Tariff Record in Option A must also be in Option B. The same is true of Options C, D, and so on. This Filing violates this rule in that Option "<optionCode>" is incomplete.
F034 Standard Withdraw-type Filing warning. Warning This filing has been setup to withdraw Filing "<Filing.AssociatedFiling.DisplayName> or <Filing.OverrideAssociatedFilingId>" in its entirety. Proceed with caution as submitting this filing to FERC could withdraw more than you had intended.
F035 Optional attachments have not been provided. Warning Depending on the details of your filing, FERC may require the following attachments but none of them have been included in this filing: [list of optional attachments that are missing from the filing]. This could be completely normal or may indicate that you have left something out of your filing.
F036 When making a Withdraw-type Filing, the associated Filing should not be an Amendment-type Filing. Warning You are withdrawing an Amendment filing. The amendment, the original filing, and all other amendments of the original filing (i.e. the entire proceeding) will be withdrawn. Proceed with caution as this may not be what you intend.
F037 For oil companies, a warning must be issued if an index rate change is being submitted and a derivation of ceiling level attachment has not been provided. Warning It appears that you have chosen to file an index rate change. Please make sure you include (either as an attachment or within your Transmittal Letter) the required information regarding derivation of the ceiling level. (18 CFR § 342.3(b))
F038 For oil companies, a warning must be issued if a cost-of-service rate change is being submitted and a cost of service summary attachment has not been provided. Warning It appears that you have chosen to file a cost-of-service rate change. Such a filing requires a showing that there is a "substantial divergence" between actual costs and the rate resulting from application of the index such that the carrier would not be able to "charge a just and reasonable rate." The filing must include cost, revenue, and throughput data as required by part 346. (18 CFR § 342.4(a))
F039 For oil companies, a warning must be issued if a settlement rate change is being submitted and a verified statement has not been provided. Warning It appears that you have chosen to file a settlement rate change. Please make sure that you attach the required verified statement by the carrier that the proposed rate change has been agreed to by all current shippers. (18 CFR § 342.4(c))
F040 Verify that the Filing's Payment Confirmation Code matches the expected FERC-established format. Fail The payment confirmation code for Filing "<Filing.DisplayName>" is in the wrong format. It must start with eight digits, followed by a hyphen, followed by four more digits. For example, 12345678-1234.
F042 A Filing cannot be associated with itself. Fail Filing "<Filing.DisplayName>" is associated with itself.
F043 Filing Validation Email address cannot be longer than 100 characters. Fail Filing Validation Email is longer than the 100 character maximum.
F044 When making a Compliance or Refiled-type Filing, the associated Filing is optional. If one is not specified, warn the user that the Filing will be assigned a unique Docket Number. Information This Filing is not associated with an earlier eTariff Filing. Therefore, FERC will assign it a unique docket number.
F045 New, Refiled, Normal, Amendment, and Motion-type Filings must include at least one FTRV. Fail When making a Normal, New, Refiled, Amendment, or Motion filing, the Filing must contain one or more FTRVs. This Filing does not have any FTRVs.
F046 Validate FTRV Proposed Effective Dates for New And Refiled-type Filing. Fail When making a New or Refiled filing, you must include at least one FTRV with a proposed effective date (even if you do not yet know the date you wish to propose). It is acceptable to FERC if the date of the filing submittal is used.
F047 A Cancel-type Filing must have one and only one FTRV. In the oil industry, however, a Cancel-type Filing must have one or more FTRVs. Fail NON-OIL: A Cancel Filing must include exactly one FTRV. This Filing has <Filing.FTRV.Count> FTRVs. OIL: A Cancel Filing must include one or more FTRVs. This Filing has <Filing.FTRV.Count> FTRVs.
F048 A Cancel-type Filing must have an FTRV of Record Change Type CHANGE. Fail The FTRV in a Cancel Filing must have a Record Change Type of "Change". This Filing's FTRV has a Record Change Type of "<Filing.FTRV.RCT.Description>".
F049 Warn if the Effective Date of a Cancel-type Filing falls prior to any other FTRV's Effective Date in the Tariff Database. Warning The Effective Date of this Cancel Filing is expected to be later than all other FTRVs in the Tariff Database. There is at least one other FTRV that falls later than <Filing.FTRV.EffectiveDate>.
F050 Within a Tariff Database with an Approved Cancel-type Filing, only Compliance-type Filings are allowed and all Effective Dates within must fall on or prior to the date on which the Tariff Database was cancelled. Fail Within a cancelled Tariff Database, only Compliance Filings are allowed and all Effective Dates within must fall on or prior to the Tariff Database cancellation date.
F051 When a Filing has an associated Filing, warn the user if the associated Filing is in a different Tariff Database and that Tariff Database is cancelled. Warning The associated Filing ("<Filing.AssociatedFiling.DisplayName>") is in Tariff Database ("<Filing.AssociatedFiling.TariffDatabase.Title>"), which was cancelled effective <Filing.AssociatedFiling.TariffDatabase.CancelledEffectiveDate>. Make sure you have made the correct Filing association.
F052 Associated Filing Id was entered manually. Information You have manually entered the Id of the filing to which this Filing is associated. This should only be done when the associated filing does not exist within TariffShark. Proceed with caution.
F060 When making a Motion-type Filing, the associated Filing cannot be a Withdraw, Motion, or Report-type Filing. Fail When making a Motion filing, the associated filing cannot be a Withdraw, Motion, or Report filing.
F061 When making a Compliance or Refiled-type Filing, the associated Filing cannot be a Withdraw, Motion, or Report-type Filing. Fail When making a Compliance or Refiled filing, the associated filing cannot be a Withdraw, Motion, or Report filing.
F062 When making a Report-type Filing, the associated Filing cannot be a Withdraw, Motion, or Report-type Filing. Fail When making a Report filing, the associated filing cannot be a Withdraw, Motion, or Report filing.
F063 When making a Report Filing, the associated Filing must have a Status of "Filed". Warning When making a Report filing, the associated filing must have a status of "Filed" thus indicating that FERC has not yet acted upon it.
F064 Child Cancel FTRV Omitted From XML. Information This Filing contains Cancel-type FTRVs for both Parent and Child Tariff Records. The Tariff Database is configured to omit the Child Cancel FTRVs from the FERC XML file, so TariffShark will not send the Child ones to FERC. Though it is harmless to send Child Cancel FTRVs to FERC, it is not necessary since FERC will cancel Children when cancelling Parents. On the other hand, TariffShark needs the Child Cancel FTRVs in order to provide accurate historical Tariff Timelines. You MUST NOT delete the Child Cancel FTRVs from this Filing as doing so will break the Tariff Timeline.
F065 Added in Release 5.1.3
Ensure that Filings using the "Normal" or "Amendment" Type of Filing codes contain at least one actual (non-Pro Forma) tariff record.
Fail When making a Normal or Amendment filing, the Filing cannot contain exclusively FTRVs of Record Change Type "Pro Forma".
R001 Make sure FTRV's Record Change Type of NEW are appropriate. Fail Filed Tariff Record Version "<FTRV.DisplayName>" cannot be sent to FERC with Record Change Type of "New" because the Tariff Record was previously filed with FERC.
R002 Make sure FTRV's Record Change Type of CHANGE are appropriate. Fail Filed Tariff Record Version "<FTRV.DisplayName>" cannot be sent to FERC with Record Change Type of "Change" because the Tariff Record has not been previously filed with FERC.
R003 Make sure FTRV's Record Change Type of CANCEL are appropriate. Fail You cannot cancel Tariff Record "<TR.DisplayName>" because it has already been cancelled in the Filing "<Filing.DisplayName>".
R005 Validate Record Change Type for New and Refiled-type Filing Fail "Change", "Withdraw", and "Cancel" are not a valid Change Types for this filing.
R008 FTRV Proposed Effective Date is required Warning The proposed effective date for Filed Tariff Record Version "<FTRV.DisplayName>" is missing. Filing this way sends FERC the message that you don't yet know the desired effective date. If this is not what you intended, you should enter a proposed effective date. Proceed with caution.
R009 FTRV Effective Priority Order must be unique among "Filed" FTRVs under the same Tariff Record with the same Effective Date. Fail Regarding "<FTRV.DisplayName>": There is more than one version of this Tariff Record filed with an effective date of FTRV.ProposedEffectiveDate. In the event that FERC approves these, a unique priority must be assigned to each.
R010 Validate Record Change Type for Motion-type Filing. Fail "Change" is the only valid Change Type for this filing.
R011 The Version value filed for a TRV must be unique. Fail Tariff Record Version "<FTRVx.TRV.DisplayName>" must be filed with a unique Version value. Version <FTRVx.TRV.Version> has been filed before or exists more than once within this Filing.
R012 FTRVs in a Motion-type Filing can only propose a different Effective Date for FTRVs that are "Suspended". Fail Filed Tariff Record Version "<FTRV.DisplayName>" is invalid in this filing because Tariff Record Version "<TRV.DisplayName>" isn't suspended in an earlier filing.
R013 FTRVs in a Motion-type Filing must have an Associated FTRV Id that points to a "Suspended" FTRV from an earlier Filing under the same TRV. Fail Filed Tariff Record Version "<FTRV.DisplayName>" must be associated with Tariff Record Version "<TRV.DisplayName>" which has been suspended in an earlier filing.
R017 Withdraw-type FTRVs must have an Associated FTRV Id that points to an FTRV with a FERC Response of "Pending", "Pending Tolled", or "Conditionally Accepted" and belongs to the same TRV in an earlier Filing (use FERC Filing Date). Fail Filed Tariff Record Version (FTRV) "<FTRV.DisplayName>" must be associated with an FTRV from an earlier filing that is pending before the Commission.
R018 Within non-Cancel-type Filings, verify that Tariff Record binary content is present for non-section-based Tariffs and non-hierarchy-enforced, section-based Tariffs. Also omit Amendment-type Filings that have a Cancel-type Filing at the end of their amendment chain. Note that no root Tariff Record can ever fail this validation. Fail Tariff Record Version "<TRV.DisplayName>" has no content.
R019 Within non-Cancel-type Filings, verify that Tariff Record plain text content is present for non-section-based Tariffs and non-hierarchy-enforced, section-based Tariffs. Also omit Amendment-type Filings that have a Cancel-type Filing at the end of their amendment chain. Note that no root Tariff Record can ever fail this validation. Fail Tariff Record Version "<TRV.DisplayName>" has no plain text content.
R020 Make sure a cancellation is not done for Tariff Records that have never been filed with FERC. Fail You cannot cancel Tariff Record "<TR.DisplayName>" because it has not been filed with FERC.
R021 Verify that a Section Number / Collation Value being filed appears to be unique. Warning Tariff Record Version "<FTRV.TRV.DisplayName>" has been assigned a section number that is already in use by "<collision TRV.DisplayName>". Due to the complexity of this validation rule, this is noted as a warning. Please use caution in your submission of this Tariff Record Version.
R022 Verify that a Tariff Record Version isn't being filed under a Tariff Record that has been cancelled. Fail Filed Tariff Record Version "<FTRV.DisplayName>" is invalid in this filing because Tariff Record "<TR.DisplayName>" has been cancelled in Filing "<Filing.DisplayName>".
R023 For oil companies, a warning must be issued if any FTRV in the Filing proposes an Effective Date less than 31 days from the FERC Filing Date. Warning Tariff Record Version "<FTRV.TRV.DisplayName>" has a proposed effective date that does not meet the Commission’s standard notice period filing requirements in 18 CFR §341.2(b). Make sure your filing materials meet the requirements for special permission for tariff publications issued on short notice. (18 CFR §341.14(a))
R024 TRV Effective Date should not fall prior to Filing Date (applies to all Filings except for New-type, Refiled-type, and Cancel-type Filings). Warning You are requesting an effective date (<FTRV.ProposedEffectiveDate>) for Filed Tariff Record Version "<FTRV.DisplayName>" that falls prior to the Filing Date (<FTRV.Filing.FERCFilingDate>).
R025 Verify that a Tariff Record isn't being cancelled more than once in a Filing and Option set. Fail Tariff Record "<TR.DisplayName>" is being cancelled more than once in this filing under Option "<FTRV.TRV.Option>".
R026 For Whole Document Tariff Records, the FTRV Tariff Record Content Type must match the content type of the associated TRV DBF, except in the case of withdrawals for which this is normal and expected. Fail The content for Tariff Record Version "<TRV.DisplayName>" was uploaded in <RTF/PDF> format. The "File as:" selection for Filed Tariff Record Version "<FTRV.DisplayName>" must match.
R027 Validate that a TRV is filed only once with Record Change Type NEW or CHANGE or CANCEL, unless being subsequently filed in a Motion-type Filing. Omit WITHDRAWN FTRVs as, logically, these have not been filed. Warning Tariff Record Version "<TRV.DisplayName>" was previously filed in Filing "<secondary FTRV.Filing.DisplayName>" Generally, once a Tariff Record Version has been filed, submitting further changes would be done using a different Tariff Record Version that belongs to Tariff Record "<TRV.TR.DisplayName>".
R028 It is out of the ordinary and may be incorrect to file a TRV in PDF format it is was most recently filed in RTF format. Warning Filed Tariff Record Version "<FTRV.DisplayName>" was recently filed in RTF format and you are proposing to file it in this filing in PDF format. Generally speaking, FERC encourages the filing of RTFs and discourages the filing of PDFs. Changing from RTF to PDF may raise eyebrows at FERC and could cause this part of your filing to be rejected.
R029 Option Codes must be filed in consecutive alphabetic sequence. Fail Tariff Record Version "<FTRV.TRV.DisplayName>" has an Option Code "<FTRV.TRV.OptionCode>" but a Tariff Record Version belonging to the same Tariff Record Version is not present in this Filing with an Option Code "<FTRV.TRV.OptionCode minus 1 letter>".
R030 Report-type Filings can only contain FTRVs with Record Change Type of PRO FORMA Fail This type of filing can only include Filed Tariff Record Versions with Record Change Type of "Pro Forma". Filed Tariff Record Version "<FTRV.DisplayName>" has a Record Change Type of "<FTRV.RCT.Description>".
R031 Record Change Type PRO FORMA is not a true tariff proposal. As such, it is not subject to Option Set restrictions. Warning Pro Forma submissions are not true tariff proposals. It is not necessary to submit them first as an Option A, then as an Option B, etc. As FERC considers Option A to be the "primary" option, the safe play is to submit Pro Forma tariff records with an Option other than A.
R032 Root Tariff Record must be filed with FERC when filing a non-root Tariff Record in a non-hierarchy enabled Tariff Database or a non-root, sheet-based Tariff Record in a hierarchy enabled Tariff Database. Fail Tariff Record Version "<FTRV.TRV.DisplayName> is part of Tariff "<TRV.TR.Tariff.DisplayName>", however, the Tariff Record that represents this Tariff has not been filed with FERC and is not represented in this Filing.
R033 Parent Tariff Record must be filed with FERC when filing a non-root, section-based Tariff Record in a hierarchy enabled Tariff Database. Fail Tariff Record Version "<FTRV.TRV.DisplayName> is a child of Tariff Record "<TRV.TR.parentTR.DisplayName>", which has not been filed with FERC and is not represented in this Filing.
R034 Tariff Record Version binary data cannot be larger than 10MB Fail The content for Tariff Record Version "<FTRV.TRV.DisplayName>" is <file size in MB> in size, which is larger than the 10MB maximum allowed by FERC.
R035 For oil companies, a warning must be issued if any TRV in the Filing contains the string "342.2(a)" Warning It appears that you have chosen to file initial rates justified by filing cost, revenue, and throughput data for Tariff Record Version "<FTRV.TRV.DisplayName>". Please make sure you attach the supporting data required by part 346. (18 CFR § 342.2(a))
R036 For oil companies, a warning must be issued if any TRV in the Filing contains the string "342.2(b)" and it is a non-Embargo Filing Warning It appears that you have chosen to file initial rates supported by a sworn affidavit that the rate is agreed to by at least one non-affiliated person for Tariff Record Version "<FTRV.TRV.DisplayName>". Please make sure you attach the required affidavit. (18 CFR § 342.2(b))
R037 For oil companies, a warning must be issued if any TRV in the Filing contains the string "342.4(b)" Warning It appears that you have chosen to file a market-based rate change for Tariff Record Version "<FTRV.TRV.DisplayName>". The title page of the tariff must include the specific Commission order pursuant to which the tariff is issued. (18 CFR § 342.4(b))
R038 For oil companies, an error must be issued if any FTRV in the Filing proposes an Effective Date greater than 60 days from the FERC Filing Date. Warning Tariff Record Version "<FTRV.TRV.DisplayName>" is proposed to be effective more than 60 days after the filing date. Tariffs must be filed 60 or fewer days before the Effective date. (18 CFR § 341.2(b))
R039 Tariff Record Version plain text cannot be larger than 10MB. Fail The plain text content for Tariff Record Version "<TRV.DisplayName>" is <file size in MB> in size, which is larger than the 10MB maximum allowed by FERC.
R040 FTRVs that have an Associated FTRV Id cannot be associated with an FTRV that was rejected. Fail Filed Tariff Record Version "<FTRV.DisplayName>" is associated with Filed Tariff Record Version "<FTRV.AssociatedFTRV.DisplayName>", which was rejected in an earlier filing.
R041 Verify that Tariff Record plain text content is non-blank. Warning The plain text content of Tariff Record Version "<TRV.DisplayName>" contains no printable characters. This can happen if the document consists of nothing more than an image, such as a map. This condition may result in a FERC warning or error when the filing is submitted.
R042 Verify that FTRVs that are associated with other FTRVs have a common Tariff Record. Fail Filed Tariff Record Version (FTRV) "<FTRV.DisplayName>" is associated with another FTRV, namely "<FTRV.AssociatedFTRV.DisplayName>". These FTRVs belong to different Tariff Records. There are no known circumstances under which this is an appropriate association.
R043 Validate Associated FTRV Id for New and Refiled-type Filings. Fail Filed Tariff Record Version "<FTRV.DisplayName>" is associated with another Filed Tariff Record Version, but this is not valid for New and Refiled filings.
R044 The combination of a TRV's Description and Title should be unique across Tariff Records within a Tariff Database. Warning Generally, the combination of a Tariff Record Version's Description and Title must uniquely identify the record being filed. This Filing contains Tariff Record Version "<FTRV.TRV.DisplayName>", which could be confused with "<TRVx.DisplayName>". Submitting the Filing as is might result in a FERC rejection or instructive order to update the Description or Title to better distinguish these records.
R045 Warn user if FTRVs that have an Associated FTRV Id are associated with an FTRV that is "Pending", except in the case of withdrawals for which this is normal and expected. Warning Filed Tariff Record Version (FTRV) "<FTRV.DisplayName>" is associated with another FTRV that appears to be pending before the Commission. If the associated record is indeed pending at FERC, submitting this Filing will cause the associated record's status at FERC to become OBE (overtaken by events). Proceed with caution as this may not be what you intend.
R046 An FTRV in a non-oil industry Filing does not have an Associated FTRV Id and there exists a "Pending" FTRV under the same Tariff Record. Warning Filed Tariff Record Version (FTRV) "<FTRV.DisplayName>" is not associated with another FTRV, yet one or more FTRVs appear to be pending before the Commission.  If you intend to submit this FTRV as a replacement for another, then you must associate this FTRV with the one you wish to replace.
R047 In a section-based Tariff in a hierarchy-enabled Tariff Database an FTRV is associated with another FTRV under a Tariff Record that has children. Warning [1] Filed Tariff Record Version (FTRV) "<FTRV.DisplayName>" is associated with another FTRV. [2] Tariff Record "<FTRV.AssociatedTR.DisplayName>" has child Tariff Records. Submitting this Filing will cause the associated record to become moot and its status at FERC to become OBE (overtaken by events). This automatic update in FERC's software cascades to child Tariff Records also pending at FERC from earlier Filings. Under certain circumstances, this causes the child records to disappear...as if they hadn't been filed. Proceed with caution!
R048 An FTRV cannot be associated with itself. Fail Filed Tariff Record Version "<FTRV.DisplayName>" is associated with itself.
R049 For hierarchy-enforced, section-based Tariffs, issue warning if Tariff Record binary content is not present. NOTE that this validation is a variation of R018 and, as a result, is quite similar. Also omit Amendment-type Filings that have a Cancel-type Filing at the end of their amendment chain. Note that all root Tariff Records are subject to this warning validation. Warning Tariff Record Version "<TRV.DisplayName>" has no content, which is OK if it is merely a placeholder parent of child sections.
R050 For hierarchy-enforced, section-based Tariffs, issue warning if Tariff Record plain text content is not present. NOTE that this validation is a variation of R019 and, as a result, is quite similar. Also omit Amendment-type Filings that have a Cancel-type Filing at the end of their amendment chain. Note that all root Tariff Records are subject to this warning validation. Warning Tariff Record Version "<TRV.DisplayName>" has no plain text content, which is OK if it is merely a placeholder parent of child sections.
R051 [Tariff Cancel] An FTRV with Record Change Type CANCEL and a FERC Response of "Draft" must be a TRV-level FTRV and have an associated TRV. Fail Filed Tariff Record Version "<FTRV.DisplayName>" is a request to cancel Tariff Record "<FTRV.TR.DisplayName>". This FTRV must have an associated TRV, but it doesn't. To resolve this issue, delete the FTRV and recreate it by cancelling the Tariff again.
R052 [Tariff Record Cancel] An FTRV with Record Change Type CANCEL and a FERC Response of "Draft" must be a TRV-level FTRV and have an associated TRV. Fail Filed Tariff Record Version "<FTRV.DisplayName>" is a request to cancel Tariff Record "<FTRV.TR.DisplayName>". This FTRV must have an associated TRV, but it doesn't. To resolve this issue, delete the FTRV and recreate it by cancelling the Tariff Record again.
R053 Within a Tariff Database with a "Draft" Cancel-type Filing, issue a warning if the Effective Date of an FTRV with Record Change Type of NEW, CHANGE, CANCEL, or PRO FORMA falls after the Tariff Database cancellation. Warning Filed Tariff Record Version "<ThisFiling.FTRV.DisplayName>" has an Effective Date (<ThisFiling.FTRV.EffectiveDate>) that falls after the date on which this Tariff Database may be cancelled by Filing "<Fn.DisplayName>".
R054 Within a Tariff Database with a "Pending" Cancel-type Filing, issue a validation failure if the Effective Date of an FTRV with Record Change Type of NEW, CHANGE, CANCEL, or PRO FORMA falls after the Tariff Database cancellation. The one exception to this rule is an Amendment-type Filing that is associated with the "Pending" Cancel-type Filing. Fail Filed Tariff Record Version "<ThisFiling.FTRV.DisplayName>" has an Effective Date (<ThisFiling.FTRV.EffectiveDate>) that falls after the date on which this Tariff Database is proposed to be cancelled by Filing "<Fn.DisplayName>".
R055 For oil companies, all FTRVs with lower TRV Version values must have Effective Dates that fall on or prior to FTRV Effective Date. Warning Tariff Record Version "<FTRVx.TRV.DisplayName>" has a Version greater than FTRV "<TRVz.FTRV.DisplayName>", but its Effective Date falls prior. This scenario is non-standard for the oil industry. Proceed with caution.
R056 Within Cancel-type Filings, TRV effective date should not fall prior to Filing Date. Fail You cannot request an effective date (<FTRV.ProposedEffectiveDate>) for this Cancel Filing that falls prior to its Filing Date (<FTRV.Filing.FERCFilingDate>).
R057 FTRV Effective Priority Order must be unique among FTRVs in a Filing under the same Tariff Record with the same Option Code. Fail FTRV "<FTRVx.DisplayName>" is not the only representation of Tariff Record "<FTRVx.TRV.TR.DisplayName>" in this Filing within Option "<FTRVx.TRV.OptionCode>". All such FTRVs must have unique Effective Priority values.
R058 FTRV Effective Priority Order must be unique among FTRVs in a Filing under the same Tariff Record with different Option Codes. Fail FTRV "<FTRVx.DisplayName>" is not the only representation of Tariff Record "<FTRVx.TRV.TR.DisplayName>" in this Filing with different Option Codes. All such FTRVs must have unique Effective Priority values.
R059 An Effective Date cannot be proposed that falls prior to the earliest Proposed Effective Date found in the baseline Filing that established the Tariff Database. Warning Filed Tariff Record Version "<FTRV.DisplayName>" has a Proposed Effective Date that falls prior to the earliest allowed proposal (<EPED>).
R060 Root records submitted in PDF format must include a title page that conveys metadata information about the tariff. Information  Tariffs that are filed in PDF format must include a title page that contains specific data about the Company and the Tariff. "<TRV.DisplayName>" in this Filing is just such a Tariff. Refer to the OSEC Implementation Guide on or around pages 7 and 8.
R061 FTRV Effective Priority Order must be unique among "Draft" FTRVs under the same Tariff Record with the same Effective Date. Warning Regarding "<FTRV.DisplayName>": There is more than one Draft version of this Tariff Record with a proposed effective date of FTRV.ProposedEffectiveDate. A unique priority should be assigned to each.
R062 Associated Tariff Record fields were entered manually. Information You have manually associated FTRV "<FTRV.DisplayName>" with a previously filed tariff record. This should only be done when the associated FTRV does not exist within TariffShark. Proceed with caution.
R063 FTRV's Collation Value was entered manually at Tariff Record level. Information FTRV "<FTRV.DisplayName>" will be sent to FERC in the XML with Collation Value "9,999,999" because this override value was entered as a Custom Field on Tariff Record "<FTRV.TRV.TR.DisplayName>". Proceed with caution.
R064 FTRV's Collation Value was entered manually at TRV level. Information FTRV "<FTRV.DisplayName>" will be sent to FERC in the XML with Collation Value "9,999,999" because this override value was entered as a Custom Field on Tariff Record Version "<FTRV.TRV.DisplayName>". Proceed with caution.
R065 A Withdraw-type FTRV must have an Associated FTRV. Each of these FTRVs must relate to a different TRV, and each TRV must belong to the same TR. Fail Filed Tariff Record Version (FTRV) "<FTRV.DisplayName>" must be associated with an FTRV that belongs to the same Tariff Record.
R066 TRV Effective Date should not fall prior to Filing Date (applies only to New-type, Refiled-type, and Cancel-type Filings). Fail FTRV "<FTRV.DisplayName>" requests an effective date (<FTRV.ProposedEffectiveDate>) that falls prior to its Filing Date (<FTRV.Filing.FERCFilingDate>). This is not allowed for New, Refiled, and Cancel types of Filings.
S001 Within a Filing, there can be no more than 200 FERC Attachments in any given Security Level. Fail You may supply no more than 200 FERC Attachments with the same Security Level. Within this Filing there are <n> FERC Attachments with Security Level "<security level>".
T001 TRV Option Code is required for every TRV in the Filing Fail Option Code is missing from Tariff Record Version "<TRV.DisplayName>".
T002 TRV Title is required on root Tariff Records. Fail Title is missing from Tariff Record Version "<TRV.DisplayName>".
T003 TRV Description is required. Fail Description is missing from Tariff Record Version "<TRV.DisplayName>".
T004 TRV-level FTRVs must include a version number. Fail Version is missing from Tariff Record Version "<TRV.DisplayName>".
T005 TRV Title cannot be longer than 60 characters Fail The Title of Tariff Record Version "<TRV.DisplayName>" is longer than the 60 character maximum.
T006 TRV Description cannot be longer than 25 characters Fail The Description of Tariff Record Version "<TRV.DisplayName>" is longer than the 25 character maximum.
T007 TRV Version cannot be longer than 10 characters Fail The Version of Tariff Record Version "<TRV.DisplayName>" is longer than the 10 character maximum.
T008 TRV Narrative Name cannot be longer than 254 characters Fail The Narrative Name of Tariff Record Version "<TRV.DisplayName>" is longer than the 254 character maximum.
T011 Last TRV Processing attempt failed Fail TRV content processing for Tariff Record Version "<TRV.DisplayName>" failed in its last attempt and because of that it may contain incomplete or inaccurate information in its content, header, or footer.
T012 TRV has unprocessed item in queue Fail TRV content processing is pending for Tariff Record Version "<TRV.DisplayName>" and because of that it may contain incomplete or inaccurate information in its content, header, or footer.
X001 Required attachments must be included in the Filing Fail FERC Attachment <AttachmentReferenceCode.Description> is missing.
X004 For some Attachments, FERC specifies a mandatory Security Level. For such attachments that are included in the Filing, make sure that at least one is provided with the mandatory Security Level. Fail FERC Attachment "<Attachment.Description>" is an attachment of type "<Attachment.AttachmentReferenceCode.Description>". In order to include this type of attachment in your Filing, a FERC Attachment must be provided with security level "<Attachment.AttachmentReferenceCode.RequiredSecurityLevel.Description>".
Z002 A Tariff Record (via its FTRV) can be present no more than once in an Option Set. Warning A Tariff Record should appear only once within an option set. Tariff Record "<TR.DisplayName>" is included within Option "<FTRV.TRV.OptionCode>" more than once. You appear to be working around a Commission restriction that would require multiple Filings to be submitted. WARNING: Any subsequent Filing in which an FTRV level association is made referring back to Tariff Record "<TR.DisplayName>" and Option "<FTRV.TRV.OptionCode>" in this Filing must include all FTRVs under the Tariff Record and Option.

See Also

ELEMENTS