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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

We request comment on our proposed requirement that three distinct types <strong>of</strong><br />

reports be submitted for each calendar year, specifically whether these reports could be<br />

simplified or whether a smaller number <strong>of</strong> reports could provide the same information.<br />

3. Recordkeeping<br />

The proposed recordkeeping requirements for renewable fuels producers support<br />

the enforcement <strong>of</strong> the use <strong>of</strong> RINs for compliance purposes. Product transfer documents<br />

(PTDs) are central to tracking individual RINs through the fungible distribution system<br />

when those RINs are assigned to batches <strong>of</strong> renewable fuel. PTDs are customarily<br />

generated <strong>and</strong> issued in the course <strong>of</strong> business (i.e. issuing them is a “customary business<br />

practice”) <strong>and</strong> are familiar to parties who transfer or receive fuel. As with other fuels<br />

programs, PTDs may take many forms, including bills <strong>of</strong> lading, as long as they travel<br />

with the volume <strong>of</strong> renewable fuel being transferred. Specifically, we propose that on<br />

each occasion any person transfers ownership <strong>of</strong> renewable fuels subject to this proposed<br />

regulation that they provide the transferee documents identifying the renewable fuel <strong>and</strong><br />

containing identifying information including the name <strong>and</strong> address <strong>of</strong> the transferor <strong>and</strong><br />

transferee, the EPA-issued company <strong>and</strong> facility IDs <strong>of</strong> the transferor <strong>and</strong> transferee, the<br />

volume <strong>of</strong> renewable fuel that is being transferred, the location <strong>of</strong> the renewable fuel at<br />

the time <strong>of</strong> transfer, <strong>and</strong> the unique RIN associated with the volume <strong>of</strong> fuel being<br />

transferred, if any. PTDs are used by all parties in the distribution chain down to the<br />

retail outlet or wholesale purchaser-consumer facility that dispenses it into motor<br />

vehicles.<br />

Except for transfers to truck carriers, retailers or wholesale purchaser-consumers,<br />

product codes may be used to convey the information required for PTDs, as long as the<br />

codes are clearly understood by each transferee. Therefore, renewable fuels producers<br />

may use codes. The RIN would always have to appear on each PTD in its entirety before<br />

it was separated from the batch, since it is a unique identification number <strong>and</strong> cannot be<br />

summarized by a shorter code.<br />

<strong>Renewable</strong> fuels producers would have to keep copies <strong>of</strong> PTDs <strong>and</strong> <strong>of</strong> all<br />

compliance reports submitted to EPA for a period <strong>of</strong> not less than five (5) years. They<br />

would also have to keep information related to the sale, purchase, brokering <strong>and</strong> trading<br />

<strong>of</strong> RINs. Upon request, renewable fuels producers or importers would be responsible for<br />

providing documentation <strong>of</strong> PTDs to the Administrator or the Administrator’s authorized<br />

representative in a usable format.<br />

D. Requirements for Other Parties Who Own RINs<br />

1. Registration<br />

We propose that other parties who intend to own RINs, <strong>and</strong> who are not obligated<br />

parties, exporters <strong>of</strong> renewable fuels, or renewable fuels producers or importers, must<br />

- 109 -

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

Saved successfully!

Ooh no, something went wrong!