Which place’s debt rules apply—and who can help?

S_MN PASS-11 — Ordinary consumer collection communications, validation, and disputes

Research/access date: October 27, 2026, America/Los_Angeles. Baseline: October 22, 2026; not represented as the date of current verification. Scope: The collection-communications, contact, validation, and dispute-handling gateway—not credentials, debt-relief fees, litigation procedure, or full-state clearance.

Disposition: The principal state and federal duties are established within the source-version limits below. Significant application questions remain, including particular actor coverage, Minnesota’s application to a federal limited-content message, harmonized notice design, certain electronic-delivery facts, and the sufficiency of verification in a particular dispute.

P10 is not a premise. Necessary actor predicates were freshly researched. Earlier answers, dates, review limits, and unresolved findings remain preserved.

Throughout, S001 means S_MN-P11-S001. The source register supplies each source’s complete HTTPS URL, issuer, pinpoint, read scope, and limitations. C001–C065 are this pass’s claims.

A. Conclusions that must remain separate

A validation notice is not proof that a debt is legally enforceable. A verification response can satisfy the narrow federal dispute procedure without deciding liability, standing, limitations, admissibility, identity theft, bankruptcy, or the evidence needed to win a lawsuit. [C048–C049.] ecf.ca8.uscourts.gov

A timely written dispute creates a collection pause, not a 30-day response deadline. The collector must satisfy the applicable verification or original-creditor response condition before resuming the affected collection activity. The cited provisions do not require a response within 30 days or extinguish the debt if no response arrives. [C044–C047.] Consumer Financial Protection Bureau+1

Minnesota adds requirements that federal labels do not erase. These include licensed-business-name identification, the specified initial-mail licensing disclosure, a counseling-resource document, and particular callback and recorded-message restrictions. Federal model-form or limited-content-message treatment is not blanket Minnesota approval. [C015–C020.] MN Revisor+1

Seven calls is not general permission to harass. Regulation F establishes rebuttable telephone-frequency presumptions, subject to definitions and exclusions. Other harassment, inconvenience, representation, privacy, workplace, cease-contact, and state rules continue to apply. [C024–C038.] Consumer Financial Protection Bureau+1

B. Actor and communication gateway

B1. State and federal coverage are different tests

Sources: §§332.31, .32, .38; 15 USC 1692a; 12 CFR 1006.2 and official interpretations. [C008–C012.] MN Revisor+3

Necessary 2026 exclusion overlay

Laws 2026, chapter 124, article 1, §57 adds the licensed mortgage-servicer and student-loan-servicer exclusion only for activities subject to the applicable licensure. It became effective August 1, 2026, at 12:01 a.m., under the section, official chapter chronology, and general date rule, with the previously reviewed act-level classification retained as dated context.

The amendment is not a federal contact exemption, and no actor’s actual license or scope was checked here. The displayed §332.32 page remains a 2025 compilation with an amendment warning. [C005.] MN Revisor+2

Principal-purpose buyers and knowledge

In Reygadas v. DNF Associates, LLC, the Eighth Circuit upheld debt-collector classification on the particular principal-purpose record even though collection was outsourced. It expressly declined a universal rule covering every purchaser.

The court separately vacated the liability judgment. The buyer’s knowledge of representation did not automatically establish the independent collector’s knowledge or the necessary agency basis for imputing its conduct. Actor status, knowledge, agency, and a prohibited communication remain separate questions. [C012.] U.S. Court of Appeals+1

B2. Communication, attempt, and limited-content message

For an LCM, the business name must not indicate debt collection, and the required callback information and permitted optional elements must fit §1006.2(j). Additional debt content defeats that treatment. A message knowingly left for a third party is not the specified consumer voicemail. [C013–C014.] Consumer Financial Protection Bureau+1

Minnesota hold: Section 332.37(a)(16) requires the full licensed agency/debt-buyer name or Commerce-registered DBA when attempting collection. A federal LCM using a shortened or different name does not automatically satisfy that state requirement. Whether a particular neutral registered DBA and message satisfy all requirements needs actual records and content. No universal harmonized LCM was approved. [C015.]

C. Minnesota-specific duties and record-access boundaries

C1. Conduct and notice matrix

The buyer exceptions in §332.37(b) are limited to enumerated client/funds-related clauses; they do not create a general communications exemption merely because the buyer owns the debt. [C015–C020.] MN Revisor+1

The workplace callback exception is not affirmative permission

Minnesota’s callback clause does not override federal restrictions based on known employer prohibitions, inconvenience, third-party disclosure, representation, or a cease request. A callback message can satisfy one narrow state clause and still be impermissible under another applicable rule.

C2. Counseling-resource document: actual body and dates

The currently linked Commerce document was retrieved and visually inspected:

URL: https://mn.gov/commerce-stat/pdfs/2023_credit_counseling_all.pdf

It is one page, printed August 2023, with the required multilingual nonendorsement text and three counseling-organization contact groups. This establishes the body presently linked from the public page—not current eligibility or service quality of those organizations. [C004, C017.] mn.gov // Minnesota's State Portal+1

The statute permits updates no more than annually. No later update-notification history was established. [C003–C004.] MN Revisor

Interpretive limit: The statute’s reference to “initial written communication” and its following “if the initial communication” condition should not be silently rewritten. No controlling interpretation was located resolving every oral-first sequence. The examples include the sheet with the first mailed notice without purporting to adjudicate that wording issue.

No text-message attachment implementation, combined notice layout, or current notification recipient list was certified.

C3. Who actually receives the “reports” or “free access”?

Three provisions must not be converted into a universal debtor-file right:

No responsive body read here establishes a general Minnesota requirement to supply every original contract, assignment, creditor ledger and investigation record on any debtor request. The federal triggered verification duties remain, and stronger contractual, sector-specific, FCRA, litigation or other legal rights may apply. Those must be established under their own authority. [C021–C022.] MN Revisor+2

D. Contact, privacy, consent, and cessation

D1. Time, place, work and representation

No magic word is required to establish inconvenience. Consent for these exceptions must satisfy the rule’s direct-to-this-collector requirement; an original creditor’s generic contract is not automatically enough. [C024–C026.] U.S. Code+1

D2. Who may be contacted?

For §1006.6’s communications rules, “consumer” includes the specified spouse, parent of a minor, guardian, executor/administrator or authorized estate representative, and confirmed successor-in-interest categories. This communications classification does not establish personal liability for the debt.

Other permitted recipients include the consumer’s attorney, a consumer reporting agency when otherwise permitted, the creditor, and the specified creditor/collector attorneys. Location-information contacts have their own narrower rules. [C027–C029.] U.S. Code+2

Location inquiries

The collector must use the prescribed identification and location-confirmation approach, generally not disclose the debt, and ordinarily not contact the same third party more than once unless a specified reason permits another contact. Employer identity is disclosed only if expressly requested under the location rule. Postcards and revealing envelopes are restricted.

A request that a neighbor make the consumer call the collector is not automatically a lawful location inquiry. Minnesota’s listed-number callback restriction must also be applied.

For deceased consumers, identifying the authorized estate representative is different from demanding payment from an unverified relative. [C029, C065.]

D3. Whole-debt cessation versus medium-specific requests

The full cease/refusal notification is complete on receipt—not when placed in the mail. The limited exceptions do not extinguish the debt or authorize otherwise unlawful remedies. [C030–C031, C053.] U.S. Code+2

D4. Telephone frequency

A single abusive call can violate the general prohibition. Closely clustered calls can rebut a presumed-compliant pattern. [C032–C034.] Consumer Financial Protection Bureau+2

D5. Email, text, wrong-party and public-media controls

The email/text procedures are relevant to the specified bona-fide-error treatment for unintentional third-party disclosure. They are not general immunity or a universal consent rule. [C035–C038, C050.] Consumer Financial Protection Bureau+3

E. Initial disclosures, validation, disputes and verification

E1. Initial versus later disclosure duties

The FDCPA requires the full collection-purpose/use-of-information disclosure in the initial written communication and, when initial contact is oral, the initial oral disclosure plus the first written disclosure. Subsequent communications require the specified debt-collector identification. Formal pleadings have the stated exception. Accurate translations must satisfy the applicable rule rather than substitute incomplete wording. [C023.] U.S. Code+1

These federal duties coexist with Minnesota’s licensed-name and initial-mail requirements. This report supplies no personalized script or approved combined form.

E2. Validation notice trigger and contents

Under §1006.34, validation information is supplied in the initial communication, within five days afterward, or orally in the initial communication as the rule permits. The paid-before-follow-up exception is limited to its stated facts.

The five-day follow-up requirement is not the same clock as the five-day assumed-receipt calculation. No weekend/holiday extension for the follow-up deadline is assumed in the examples, which send the notice the next day. [C039.] U.S. Code+1

The selected itemization date must be used consistently for that collector’s disclosures for that debt. Another collector may select a different permitted date. Zero-valued required itemization categories are not silently omitted. [C040.] Consumer Financial Protection Bureau+1

Receipt and the validation period

The period begins when validation information is provided and ends 30 days after actual or permitted assumed receipt. For the assumption, the collector may use a date at least five days after providing the notice, excluding Saturdays, Sundays and the legal public holidays identified in 5 USC 6103(a).

The 30-day interval is not converted into 30 business days. A failed delivery cannot simply be treated as successful notice; the commentary addresses replacement notice and the ensuing period. [C041.] Consumer Financial Protection Bureau+2

Form safe harbor is limited

Model-form treatment under §1006.34 is limited to the specified information and format requirements. It does not establish debt validity, all communications compliance, or Minnesota compliance.

State-required disclosures can be accommodated only under the applicable additional-information placement rules and state requirements. The Minnesota relative-font requirement and resource sheet must not be omitted merely because a federal model was used. No finished form or layout was tested here. [C042.] Consumer Financial Protection Bureau+1

E3. Dispute and original-creditor request matrix

Authorities: §1692g; §1006.38 and comments 38-1 through -3, 38(c), 38(d)(2). [C043–C049, C065.] Consumer Financial Protection Bureau+3

Timeliness and receipt are different: the rule addresses a dispute or request submitted within the validation period, while the pause obligation begins on the collector’s receipt. The examples use same-day accepted email so they do not depend on an unresolved postal-boundary fact.

E4. What verification establishes under the Eighth Circuit

Dunham v. Portfolio Recovery Associates, LLC, 663 F.3d 997, 1002–04 (8th Cir. 2011) affirmed judgment on the particular verification record while rejecting the lower court’s conclusion that a mistakenly targeted person was not a consumer.

The identifying and account information in that case demonstrated that the collector had the wrong person. The court rejected the asserted need for more original-creditor material on those facts and expressly recognized that different facts might require more. It did not announce that any balance statement always suffices or that a collector may continue pursuing a person known not to owe the debt. [C048.] ecf.ca8.uscourts.gov

Therefore, this pass does not impose—or reject for every circumstance—a universal checklist consisting of an original signed contract, every assignment, complete payment history and litigation-ready evidence. The response must be evaluated against the actual dispute and controlling law.

Verification is not all of the following

It is not automatically:

• a determination of the correct defendant or ownership chain;
• proof sufficient for judgment;
• an answer to identity theft, discharge, limitations or standing;
• a credit-report correction; or
• permission to use a prohibited contact method.

Those separate legal questions remain deferred except for the necessary distinction.

E5. Known disputes and credit-information communications

Section 1692e(8) addresses communicating credit information known or reasonably known to be false, including failure to communicate that a debt is disputed.

Wilhelm v. Credico, Inc., 519 F.3d 416 (8th Cir. 2008) rejected the reporting theory on its particular record but reversed summary judgment on a threat claim. This pass does not turn that decision into a complete current FCRA furnishing/update rule. If the collector communicates credit information, the known-dispute rule must be tested; the full reporting regime remains separate. [C052.] U.S. Code+1

E6. Sending verification electronically

Section 1006.42 requires required disclosures to be sent in a manner reasonably expected to provide actual notice and in a form the consumer can retain and access.

Its express E-SIGN requirement covers the specified follow-up validation notice, original-creditor response, and verification response. An initial electronic validation notice is not simply treated as identical to every later electronic disclosure. An email opt-out or known delivery failure matters independently. [C050–C051.] Consumer Financial Protection Bureau

The underlying E-SIGN consumer-consent provision was read in an official 2024 edition after the attempted updated routes failed. It requires more than a generic contract checkbox: affirmative consent, disclosures about paper/withdrawal/scope, access requirements, and the specified demonstration of electronic access. No actual consent or 2026-complete E-SIGN source chain is certified. GovInfo

F. Published decisions, authority, and currentness

F1. Decisions actually read

All four official appellate PDFs were read in the relevant majority portions and dispositions; relevant pages were visually inspected. No unpublished opinion, headnote, dissent or quoted underlying decision is represented as a newly read controlling body. No complete subsequent-history or citator review was performed. [C012, C048, C052–C053.] U.S. Court of Appeals+3

F2. State protection and federal authority

Section 1692l(d) supplies rulemaking authority; §§1692k and 1692l address liability and enforcement separately. Section 1692n and §1006.104 preserve state law except to the extent of inconsistency and do not treat greater state consumer protection as inconsistent merely for being greater.

This does not establish that every provision of Regulation F is automatically a Minnesota licensing rule, nor that a federal safe harbor resolves every independent state obligation. Full remedies, defenses, and enforcement proceedings remain deferred. [C055, C064.] U.S. Code+3

F3. Currentness and conflict matrix

Sources: S009–S018, S038–S044. [C001–C007, C056.] MN Revisor+5

G. Sixteen new fictional postures

These are conditional applications, not actual actor findings. [C061, C065.]

H. Four fully worked fictional event examples

Common conditions

Each example assumes an ordinary unsecured consumer debt, an actor subject to the identified federal provisions, and applicable Minnesota agency/buyer conduct duties unless a branch expressly changes that fact.

No legal validity, license status, actual authorization, or consumer identity is established. Dates are fictional 2026 dates. No script, contact, submission or real deadline is produced.

Example 1 — Initial call, mailed validation, itemization and receipt calculation

Facts and arithmetic

• Tuesday, September 8, 10 a.m.: first actual consumer telephone communication, at a convenient time, without representation or cease-contact restriction.
• Required initial oral collection disclosure is assumed.
• Complete oral validation information is not assumed.
• Wednesday, September 9: complete written validation notice mailed.
• Itemization date: August 31, a permitted last-statement date.
• Starting balance: $1,000.
• Subsequent lawful interest assumed: $20.
• Fees: $0.
• Payment already credited: $100.
• Other credits: $0.

Plain text

$1,000 + $20 + $0 − $100 − $0 = $920 current balance.

The itemization does not prove the interest is lawful; that is an express model assumption.

Event analysis

Assumed receipt calculation

The model uses the permitted five-day minimum assumption, excluding Saturdays, Sundays and §6103(a) holidays:

No listed federal holiday falls in that counting interval.

The 30 days after September 16 are:

Plain text

September 17–30: 14 days
October 1–16:   16 days
Total:          30 days

Stated validation end date: October 16. Weekends and October 12 are not removed from this separate 30-day interval.

If the notice is returned undeliverable, this model’s successful-notice assumption fails; replacement delivery and a new period require analysis. There is no automatic 30-day blanket collection moratorium merely because this notice was sent, but no activity may overshadow the rights or violate another restriction. [C057; S025, S031, S033, S035, S044.]

Example 2 — Oral dispute, timely written request, pause and resumption

Use Example 1’s $920 balance and October 16 validation end date. No later payment, interest or fee occurs.

Amount reconciliation

Plain text

Disputed portion:   $120
Other portion:      $800
Total:              $920

Payments during example: $0
Balance change caused by dispute: $0
Model balance remains: $920, subject to actual substantive correction.

The $120 is not subtracted merely because disputed. Nor does the model establish that it is owed.

Adverse alternatives

• No response by October 21: there is no invented “30-day verification deadline” producing automatic extinguishment. The applicable pause remains until its condition is satisfied or collection is abandoned.
• Only a duplicate dispute: the rule’s duplicate definition and response route must actually fit; silence is not assumed sufficient.
• A separate whole-debt cease request was also received: verification does not automatically remove that independent contact restriction.
• Electronic verification instead of mail: §1006.42(b)’s E-SIGN conditions must be satisfied; the consumer’s ability to email a dispute does not itself establish those outgoing-consent conditions.

[C058; S025, S034–S035, S042–S043.]

Example 3 — Calls, conversations, workplace restrictions and third parties

Call-count branch

Assume one particular person, one debt, no excluded calls, no actual conversation, and each call rings or reaches voicemail:

The eighth call creates the applicable presumption. The first seven are not blanket approval: concentration, known inconvenience, harassment, representation or cessation could independently prohibit them.

Conversation branch—not added to the preceding facts

Assume instead a telephone conversation occurs October 7:

Plain text

Day 1: October 7
Day 2: October 8
Day 3: October 9
Day 4: October 10
Day 5: October 11
Day 6: October 12
Day 7: October 13

A collector-placed call during the restricted interval requires the relevant exclusion or faces the presumption. October 14 clears only this numerical interval, not every contact restriction.

A specific voluntary request during the October 7 conversation for an October 9 callback may fit the direct-consent exclusion. It does not authorize unlimited calls, survive revocation, or override other restrictions.

State and privacy branches

No payment occurs and no balance changes in this example. [C059; S003, S021–S022, S028–S030.]

Example 4 — LCM, email, wrong party, opt-out and state information

Main sequence

No endpoint is calculated here because the example concerns channel control, not a second assumed-receipt exercise.

Wrong-number branch

A separate text is proposed to a number obtained from an old file. The only known event is a previous voice conversation.

• That does not establish the required text procedure.
• A 60-day/reassignment-check route must be supported by the actual facts, not a database label.
• If the recipient reports “wrong person,” the collector cannot continue relying on absence of knowledge of a prohibited disclosure.
• A knowingly third-party voicemail is not converted into a consumer LCM.
• Any required notice must be redirected through an actually permissible method.

Failed-email branch

If an electronic required disclosure is returned undeliverable, §1006.42’s reasonable-expectation condition is not satisfied for that attempt. A later printed notice must be evaluated as the actual notice; an unsuccessful email is not used to shorten the validation period.

No consumer data is requested, and no live message or template is produced. [C060; S003–S004, S027–S028, S030–S035, S043.]

I. Source register

Access convention: All “fresh” entries were accessed during the October 27, 2026 research session. Individual fetch timestamps were not exposed. Repeated uses of one statute, rule, commentary or opinion are not independent corroborating authorities.

Failed routes, discovery-only material, and search limits

The bounded state search used exact combinations of 332.37, 332.365, dispute, verification, written explanation, records, and official court/Commerce/Revisor domains. No responsive Minnesota published majority or binding final administrative construction was located and opened resolving the LCM/state-name interaction, oral-first resource-sheet wording, or universal free-file/verification checklist.

That is not proof that no such authority exists. The four cited appellate opinions were recovered from official court PDFs; no primary-opinion republication is relied upon in this pass.

J. Atomic claim register

“High—text” means the opened wording supports the claim within the stated version. “Conditional” requires actual facts. “Held” identifies missing interpretation or evidence.

K. Granular coverage and exact remaining evidence

L. Contribution crosswalk—no invented P01 collection row

M. Researcher self-check and disposition

Actually read: The identified Minnesota conduct, document and record provisions; necessary actor definitions; selected enacted changes; the linked counseling sheet; relevant FDCPA bodies; operative Regulation F provisions and actual official commentary; selected adoption/correction documents; and four published Eighth Circuit majority opinions and dispositions. Relevant PDF pages were visually inspected.

Not established: A particular actor’s coverage or status, a compliant finished notice or LCM, actual consent, actual verification sufficiency, a universal state free-file right, a universal original-contract packet, complete later-law/citator coverage, or any actual debt’s validity.

The examples distinguish notice, receipt, submission, pause, response, contact permission and debt balance. A dispute is not payment; verification is not adjudication; sending information is not always receipt; and a numerical call presumption is not blanket permission.

Bottom line: Minnesota adds meaningful identification, disclosure and contact duties to the federal framework. Federal validation provides notice and conditional pauses, while known representation, inconvenience, privacy, cessation and electronic-channel rules continue independently. The unresolved state/form and fact-specific verification questions remain explicit.

No actual permission, independent review, full-state or parent acceptance, A066, A097 or A098 completion is claimed.

END S_MN PASS-11