The Collections Compliance Pack composes two debt-collection nodes: checking a call log against the Regulation F call-frequency presumptions, and checking a validation notice's content elements and response-period math. Each returns a receipt binding an execution_hash to its declared inputs and its arithmetic. Read this before handing a receipt to counsel or a regulator, or receiving one from a servicing vendor, so the claim it makes — and the claim it does not make — is unambiguous.
Stage 1 is the entry point and reviews the declared call log. Stage 2 continues by reviewing the validation notice for the same collections file.
A declared call log (timestamps, debt ids, connected y/n) checked against 12 CFR 1006.14(b): more than seven calls per debt within any seven consecutive days, and a call within seven days after a telephone conversation on that debt. Pure interval counting under a declared timezone offset — both presumptions are rebuttable.
A validation-notice element checklist against 12 CFR 1006.34 / Model Form B-1 (itemization date, amounts, dispute-rights statement, and more), plus the 30-day response-period math from a declared mailing date under a declared mailing-to-receipt assumption. Checks presence and form, not the truth of any disclosed amount.
| The receipt proves | The receipt does NOT prove |
|---|---|
| Whether the declared call log crosses the 7-in-7 or quiet-period call-frequency thresholds, and which specific calls trip them. | That harassment occurred, or that a presumption survives a rebuttal under 1006.14(b)(3). |
| Whether the declared validation-notice elements are present and well-formed, and the 30-day response deadline that follows from a declared mailing date. | That the notice's disclosed debt amount, itemization, or other figures are accurate. |
That a third party can independently replay the arithmetic from the same declared inputs and reach the same execution_hash. | Any legal determination, compliance opinion, or finding of fact whatsoever. |