TC 636: Separate Appropriations Refundable Credit

What the code actually does

IRS Document 6209, Section 8A defines TC 636 as a "Master File generated credit for amounts falling under Separate Appropriations," using the identical identification-number convention as its manual counterpart: "with identification number 02, indicates credit for solar or wind energy investment."

The document code column for this entry reads "Generated Transaction" rather than a specific input document code — Doc 6209's own way of marking a code the computer posts on its own, from return-line data, rather than one a human keys in directly.

Why the source matters more than the amount

For a Separate Appropriations credit, whether it came from TC 630 (manual) or TC 636 (generated) says something about where the underlying claim came from — a manual adjustment action versus data transcribed directly from the return. That provenance can matter if the credit is ever examined, since a generated credit traces back to the original return's own line items in a way a manual credit does not.

Both codes use the same identification-number scheme, so confirming "02" on a TC 636 confirms the same solar/wind energy investment category Doc 6209 documents for TC 630 — the mechanism differs, the underlying credit category does not.

Reversal follows the same paired logic

Doc 6209's TC 637 entry mirrors TC 632's: "reversal of TC 636," with "identification number 03" marking the solar/wind-specific reversal. As with the manual pair, the reversal code stays tied to the same identification-number convention, so confirming the number on a reversal transaction confirms which original credit it actually unwinds.

Because Master File generates both TC 636 and its reversal automatically, the manual-input compatibility checks IRM 21.5.8.4(11) describes for transferred credits do not apply to the original posting. But if the credit is later moved or offset, the underlying transaction-code compatibility rule in Doc 6209 Section 8A.2 still governs that subsequent transfer.

What TC 636 gets confused with

It gets confused with TC 630. The two represent the same credit category under Separate Appropriations, distinguished only by whether the posting was manual or Master File generated.

It gets confused with an ordinary refundable credit from the return's standard credit lines. TC 636 exists specifically for the Separate Appropriations funding mechanism, not the general refundable-credit codes most returns generate.

It gets confused with a routine data-processing adjustment when the identification number is not checked — the number is what actually identifies the specific appropriation item involved.

The practitioner's actual next step

Check the identification number on the transaction to confirm the specific Separate Appropriations category — do not assume from the transaction code alone.

Note whether the credit posted as TC 630 (manual) or TC 636 (generated) when documenting the account's history, since the provenance differs even though the underlying credit category does not.

Confirm a reversal's identification number matches the original credit's before assuming it fully unwinds the correct transaction.

Treat an unfamiliar TC 636 as a legitimate, narrowly scoped credit rather than a data error before investigating further.