06.08.2013 Views

Regulation of Fuels and Fuel Additives: Renewable Fuel Standard ...

Regulation of Fuels and Fuel Additives: Renewable Fuel Standard ...

Regulation of Fuels and Fuel Additives: Renewable Fuel Standard ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

also register before ownership <strong>of</strong> any RINs is assumed. The registration requirements are<br />

the same as those for other parties discussed previously in Sections IV.B.1 <strong>and</strong> IV.C.1<br />

above, <strong>and</strong> require the registrant to provide very basic information about the company, its<br />

facility or facilities, <strong>and</strong> a contact person. The registration is on very simple forms<br />

provided by EPA. A variety <strong>of</strong> parties may own RINs including (but certainly not limited<br />

to) marketers, blenders, terminal operators, <strong>and</strong> jobbers. (As is mentioned in the previous<br />

two sections, obligated parties <strong>and</strong> renewable producers may also own RINs but have<br />

other reporting responsibilities, as well.)<br />

It is possible to own RINs separately from batches <strong>of</strong> renewable fuel. For<br />

example, a broker might be expected to own RINs in this fashion. Any party who is not<br />

currently registered with us <strong>and</strong> who intends to own RINs would have to submit a simple<br />

registration form, as described above. We anticipate about 1,500 new registrants as a<br />

result <strong>of</strong> this proposed registration requirement, although an exact estimation <strong>of</strong> the<br />

number <strong>of</strong> parties that will constitute this group is difficult to make. As with the other<br />

parties described in this Section, we will issue a 4-digit company identification number<br />

<strong>and</strong>, for each facility registered, a 5-digit facility identification number. If a party<br />

becomes subject to this proposed regulation after the effective date, then we propose that<br />

they must register with us <strong>and</strong> receive their EPA-issued company <strong>and</strong> facility<br />

identification numbers prior to owning any RINs.<br />

2. Reporting<br />

Parties who own RINs would be required to submit two types <strong>of</strong> annual reports by<br />

February 28, representing activity in the previous calendar year. The first report would<br />

document RIN transactions. This report is akin to the credit trading reports submitted by<br />

refiners <strong>and</strong> importers under other fuels programs in 40 CFR Part 80 <strong>and</strong> is the same as<br />

the second report described for obligated parties in some detail in Section IV.B.2 above.<br />

The second type <strong>of</strong> report would summarize RIN activities for the previous year,<br />

including the total number <strong>of</strong> RINs owned, transferred, <strong>and</strong> expired. This report would<br />

not include details <strong>of</strong> every RIN owned or used, since this information would be included<br />

in the transactional report. Instead, this report would simply summarize the total number<br />

<strong>of</strong> RINs falling into different categories.<br />

All reports would have to be signed <strong>and</strong> certified as true <strong>and</strong> correct by a<br />

responsible corporate <strong>of</strong>ficer. This can be done electronically. As discussed above, we<br />

plan to utilize a highly simplified electronic method <strong>of</strong> reporting via the Agency’s Central<br />

Data.<br />

As discussed above, we are seeking comments on the frequency <strong>of</strong> reporting,<br />

especially with regard to RIN transactions. We are proposing annual reporting, but are<br />

seeking comments on whether reporting should be quarterly.<br />

- 110 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!