Building a validation notice from a placement file

Pick the itemization date first, because everything else on the notice hangs off it. Section 1006.34(b)(3) gives five reference dates — last statement, charge-off, last payment, transaction, judgment — and you may use any one "for which a debt collector can ascertain the amount of the debt". The notice then has to carry the amount owed on that date, an itemization of interest, fees, payments and credits since it, the current amount, the account number as of that date, the creditor names, the end date of the validation period with its three consumer-protection statements, and the response prompts. Use Model Form B-1 and you receive a safe harbour for the information and form requirements of 1006.34(c) and (d)(1); build your own form and you do not, whatever else it may achieve.

Which of the five dates can this placement file actually prove?

Section 1006.34(b)(3) defines the choice: "Itemization date means any one of the following five reference dates for which a debt collector can ascertain the amount of the debt". The five are the last statement date, the charge-off date, the last payment date, the transaction date and the judgment date. There is no hierarchy among them and no preferred answer. The condition is evidentiary: you must be able to state what was owed on that date.

That turns the first step into a data question rather than a legal one. Charge-off date is the common answer for bank placements because the charge-off balance is the one field almost every placement file carries reliably. Last statement date is attractive because it is the date the consumer will recognise, but comment 1006.34(b)(3)(i)-1 narrows what qualifies: "a statement or invoice provided by a debt collector is not a last statement for purposes of § 1006.34(b)(3)(i), unless the debt collector is also a creditor." A prior agency's dunning letter does not create a last statement date.

Transaction date is the one that hides ambiguity. The commentary notes a debt may have more than one transaction date — a contract executed on one day, the service performed on another — and permits the collector to use any such date, provided it is used consistently. That flexibility is a liability at scale: if the field can be populated two ways, two different notices for the same portfolio will disagree, and the disagreement will surface in a dispute rather than in a review.

Lock the date, then never move it

The consistency rule is short and unforgiving. Comment 1006.34(b)(3)-1 provides that "Once a debt collector uses a reference date for a debt in a communication with a consumer, the debt collector must use that reference date for that debt consistently" when providing the information required by section 1006.34(c). The commentary's own example is the trap: a firm that uses the last statement date to derive the account number under 1006.34(c)(2)(iv) may not then use the charge-off date to derive the amount of the debt under 1006.34(c)(2)(vii).

This is a schema constraint, not a drafting instruction. The itemization date belongs to the account record and every derived field has to read from it. Where a firm assembles the notice from several source systems — account number from one, balance from another — the date used by each has to be the same date, and the only reliable way to guarantee that is to store the choice once and derive everything from it.

The rule does not bind you to your predecessor. Comment 1006.34(b)(3)-2 says that when selecting an itemization date "a debt collector may use a different reference date than a prior debt collector who attempted to collect the debt." Useful when a placement arrives with a charge-off balance but no statement history, and worth noting on the account, because a consumer holding two notices with two different dates will read them as two different debts.

The money block

Four required items carry the arithmetic, and they only make sense together. Section 1006.34(c)(2)(vi) requires the itemization date itself. Section 1006.34(c)(2)(vii) requires "The amount of the debt on the itemization date", which the commentary confirms "includes any fees, interest, or other charges owed as of that date" — it is the whole balance then owing, not principal. Section 1006.34(c)(2)(viii) requires "An itemization of the current amount of the debt reflecting interest, fees, payments, and credits since the itemization date." Section 1006.34(c)(2)(ix) requires the current amount.

So the block is two anchors and four categories of movement between them: the balance on the itemization date, then interest, fees, payments and credits, arriving at the balance today. Any category with no activity still has to be dealt with; a firm that suppresses empty rows is making a formatting decision that departs from the model form, which has consequences discussed below.

Section 1006.34(c)(2)(viii) also allows the itemization to sit on a separate page in the same communication, provided the notice carries a statement, where the itemization would have appeared, referring the consumer to that page. This is the practical answer for long-running accounts with many post-charge-off transactions. It is not free — the safe harbour treats the separate page differently, which the safe-harbour section below sets out.

What else the placement file has to supply

Beyond the money, section 1006.34(c)(2) requires the collector's name and the mailing address at which it accepts disputes and requests for original-creditor information; the consumer's name and mailing address; "The account number, if any, associated with the debt on the itemization date, or a truncated version of that number"; and the name of the creditor to whom the debt currently is owed. For a consumer financial product or service as defined in section 1006.2(f), it also requires "the name of the creditor to whom the debt was owed on the itemization date" — which for a purchased account is a different name from the current creditor, and for a firm collecting for the originating bank is the same one.

That historical creditor name is the field most often missing from a placement file, because it is the field the placing party has least reason to think about. It has to be the name as of the itemization date, which means it moves if the itemization date moves. Sorting this out at boarding is cheap; sorting it out after a notice has gone out is a correction letter.

Section 1006.34(c)(1) adds the disclosure required by section 1006.18(e) — the statement that the communication is from a debt collector — and section 1006.34(c)(4) adds the consumer-response block, which must be segregated from the rest and carry specific prompts "listed in the following order, and using the following phrasing or substantially similar phrasing, each next to a prompt". The wording of those prompts is prescribed. It is not a place for house style.

Computing the end date you print

Section 1006.34(c)(3)(i) requires the notice to state "The date that the debt collector will consider the end date of the validation period and a statement that, if the consumer notifies the debt collector in writing on or before that date that the debt, or any portion of the debt, is disputed, the debt collector must cease collection of the debt, or the disputed portion of the debt, until the debt collector sends the consumer either verification of the debt or a copy of a judgment." Paragraphs (c)(3)(ii) and (iii) require the same date again, attached to the original-creditor right and to the assumption of validity.

The date is computed, and the rule supplies the assumption you may use. Section 1006.34(b)(5) provides that "For purposes of determining the end of the validation period, the debt collector may assume that a consumer receives the validation information on any date that is at least five days (excluding legal public holidays identified in 5 U.S.C. 6103(a), Saturdays, and Sundays) after the debt collector provides it." Five business days to presumed receipt, then thirty calendar days.

Because the assumption sets a floor rather than a fixed value, a firm may print a later date, and printing a later date is generally the safer error — it gives the consumer more time than required rather than less. What it must not do is drift between templates. The date on the notice is the date your own suppression logic must honour when a dispute arrives on day 34, and the two have to be computed by the same code.

The Model Form B-1 safe harbour, and its edges

Section 1006.34(d)(2)(i) is the whole reason to use the model form: "A debt collector who uses Model Form B-1 complies with the information and form requirements of paragraphs (c) and (d)(1) of this section", and keeps that protection whether it omits the optional disclosures shown on the form or adds optional disclosures not shown, provided the additions are no more prominent than the required information.

The form tolerates change. Section 1006.34(d)(2)(iii) provides that a collector using the form "may make changes to the form and retain a safe harbor for compliance with the information and form requirements of paragraphs (c) and (d)(1) of this section provided that the form remains substantially similar to Model Form B-1." The commentary's permissible examples include relocating the consumer-response block to suit an envelope, adding barcodes or QR codes, adding the generation date, and embedding hyperlinks in an electronic version.

What it does not tolerate is starting somewhere else. Comment 1006.34(d)(2)-1 states that a collector whose notice is neither the model form nor a substantially similar one "does not receive a safe harbor for compliance with the information and form requirements of § 1006.34(c) and (d)(1)." And where the itemization goes on a separate page, section 1006.34(d)(2)(ii) grants the safe harbour "except with respect to the disclosures on the separate page" — the separate page is on its own. A firm that has inherited a legacy letter and layered the Regulation F content onto it has a notice that may well be compliant, but it will have to prove that on the merits.

If you offer the Spanish disclosure, you have bought an obligation

Section 1006.34(d)(3)(vi) permits two optional Spanish-language disclosures on an English notice — a statement in Spanish about how to request a Spanish notice, and a translated statement of the notice's purpose. They are genuinely optional. Including one is not.

Section 1006.34(e)(2) provides that a collector who includes either or both of those optional disclosures "and who thereafter receives a request from the consumer for a Spanish-language validation notice, must provide the consumer a validation notice completely and accurately translated into Spanish." The obligation attaches on request, and it is for the complete notice, not the part the consumer asked about.

Section 1006.34(e)(1) sets the surrounding rule for any language: a translated notice may be sent if an English notice goes in the same communication or has previously been provided, and the translation must be complete and accurate. The commentary treats a translation obtained from the Bureau's website as complete and accurate. If your firm intends to offer the Spanish prompt, the fulfilment path — who produces the notice, from which source, within what interval — needs to exist before the prompt ships, not after the first request arrives.

This is an informational reference, not legal advice, and using it creates no attorney-client relationship. Limitations periods turn on facts this page cannot know — which state's law governs, the contract type, when the claim accrued, and whether anything tolled or revived it. Confirm against the primary source and your own counsel before acting.