A receivables portfolio needs separate controls for the Servicemembers Civil Relief Act (SCRA) and bankruptcy. Qualifying pre-service obligations can receive SCRA protections, and a bankruptcy petition generally activates an automatic stay against covered collection activity. A military-status match or bankruptcy report should trigger a documented pause, verification, and escalation process rather than an assumption that an account is either collectible or uncollectible.

Why these protections require a separate workflow

The SCRA is a federal law that protects qualifying servicemembers in certain civil, financial, and court matters. Bankruptcy is governed by Title 11 of the United States Code and the Federal Rules of Bankruptcy Procedure. Neither subject is a simple account flag: applicability can depend on the person’s status, dates, type of obligation, court posture, notice, exceptions, and local procedure. The federal judiciary notes that bankruptcy procedure is also governed by each bankruptcy court’s local rules. Read the U.S. Courts overview of the bankruptcy process.

SCRA protections to recognize

The 6 percent interest-rate protection

For qualifying financial obligations incurred before military service, the SCRA limits the annual interest rate to 6 percent when the servicemember makes a proper request. The Department of Justice (DOJ) and Consumer Financial Protection Bureau (CFPB) explain that interest includes most service charges, renewal charges, and fees, but not bona fide insurance. Their December 2024 guidance also explains that excess interest is forgiven, not deferred, and that timing differs for mortgages and other obligations. Read the DOJ and CFPB’s SCRA interest-rate guidance.

A defensible operational response preserves the request and supporting documentation, identifies the relevant service dates and obligation dates, applies the account-specific calculation, and records any adjustment. Do not treat a database result as a substitute for a servicemember’s timely notice and documentation or for counsel’s analysis of a particular account.

Default-judgment safeguards

When a defendant has not appeared in a civil action, the SCRA requires a plaintiff seeking a default judgment to file an affidavit stating whether the defendant is in military service or that the plaintiff could not determine that status. If the court determines that the defendant is in military service, it may not enter judgment before appointing an attorney; the court can also grant a stay in the circumstances described by the statute. The federal judiciary’s SCRA guidance explains these safeguards and the potential reopening of certain judgments.

For portfolio operators, this means that a litigation file should have a deliberate pre-default review. The required filing, affidavit format, diligence, service records, and any local-court practices should be confirmed with litigation counsel; a generic “non-military affidavit” label is not a complete compliance analysis.

Use military-status verification carefully

The Department of Defense’s Defense Manpower Data Center (DMDC) SCRA service offers single and multiple record requests for reports certifying Title 10 active-duty status. See the DMDC SCRA service. The DOJ and CFPB caution that some National Guard or Reserve service that may support an SCRA benefit may not appear in the DMDC database. A no-match is therefore not a basis to disregard a servicemember’s written notice and appropriate indicator of service. See the agencies’ discussion of DMDC limits.

  • At acquisition: assess whether the transfer data can support status, notice, date, and adjustment records if an SCRA issue arises.
  • Before a default request or other high-risk litigation event: use counsel-approved diligence and retain the result used for the court filing.
  • After a notice or status change: route the account for prompt review, document the source and date of the information, and make sure downstream agencies and law firms receive any needed recall or hold instruction.

Federal law does not prescribe a universal 24-hour, 48-hour, or three-stage DMDC schedule for every portfolio. A company should set risk-based timing, ownership, evidence-retention, and exception rules with qualified counsel and test them across vendors.

Bankruptcy: the automatic stay comes first

Under 11 U.S.C. § 362, filing a bankruptcy petition generally operates as a stay of listed actions, including the commencement or continuation of a proceeding to recover a pre-petition claim, enforcement of a pre-petition judgment, and acts to collect, assess, or recover a pre-petition claim. The statute has exceptions and other qualifications. Read the official text of 11 U.S.C. § 362 on GovInfo.

Accordingly, a report that a consumer or business has filed bankruptcy should be treated as a collection-control event. Pause outbound calls, letters, new suits, enforcement activity, and third-party placements that could fall within the stay while trained staff verify the case and determine the account’s posture. Verification should be focused and documented; it should not be used as a reason to continue collection activity that may be stayed.

The automatic stay is not identical in every case. For example, the statute includes exceptions, and prior dismissed cases can affect whether a stay takes effect or how long it lasts. The official U.S. Bankruptcy Court for the District of Oregon advises creditors who are unsure whether the stay applies to seek legal advice and obtain court relief before proceeding. Read the court’s automatic-stay FAQ.

Account handling after a bankruptcy notice

  1. Capture the report: record the date, time, source, account identifiers, and any case or court information available.
  2. Place a controlled hold: stop covered activity in internal and vendor systems, then obtain acknowledgments where a placement, lawsuit, garnishment, or agency workflow is involved.
  3. Verify and classify: have trained personnel or counsel confirm the case, chapter, debtor identity, claim type, collateral status, and whether a stay, discharge, or court order changes the next step.
  4. Track court deadlines: claims processes and deadlines are case-specific. In Chapter 13, for example, creditor participation in distributions is tied to filing a claim with the court. Review the U.S. Courts Chapter 13 overview.
  5. Release only with authority: resume or change activity only after the responsible legal or compliance function documents why it is permitted, such as a court order granting relief from the stay.

Chapter 7 and Chapter 13 are not account-status codes

High-level bankruptcy distinctions for workflow triage
ChapterFederal judiciary descriptionOperational implication
Chapter 7Liquidation of a debtor’s nonexempt property, with distribution under the Bankruptcy Code.Do not assume the account is collectible, discharged, or abandoned based on the chapter label alone. Review notices, claim treatment, collateral, discharge, and any court order.
Chapter 13Adjustment of debts for an individual with regular income, generally through a three- to five-year plan.Identify the court’s notices and claims process promptly; collection outside the bankruptcy process may be barred while the case is pending.

These are general descriptions, not a prediction of recovery or a legal conclusion about any claim. Read the U.S. Courts Chapter 7 overview and Chapter 13 overview.

Build controls that can be audited

A practical portfolio protocol assigns owners and evidence at each handoff. It should reconcile the account inventory against legal holds, preserve the source of each SCRA or bankruptcy signal, route exceptions to appropriately trained personnel, and document instructions sent to agencies, law firms, and other vendors. Sample testing should confirm that a hold is effective in every contact channel and that a release has an identifiable legal or compliance basis.

Automation can make these controls more consistent, but it does not decide legal eligibility. A vendor match, a court-data feed, or an internal rule should create a reviewable event with a clear owner, not a silent decision. The Federal Rules of Bankruptcy Procedure govern bankruptcy procedure, and local court rules can add requirements that a national workflow must accommodate.

Communicate without making unsupported conclusions

When a consumer raises military service or bankruptcy, treat the statement respectfully and as a compliance escalation. Do not infer that a person is ineligible, promise that a debt has been discharged, or tell the person that a court filing has no effect before the responsible team has reviewed the facts. Consumers and creditors may both need independent legal guidance for questions about a particular case.

Frequently asked questions

Can debt buyers sue you?

Depending on the facts and governing law, a debt buyer may file a civil action, but a court determines liability. A bankruptcy filing generally stops covered collection lawsuits and other collection activity through the automatic stay, subject to exceptions and court orders. If a defendant has not appeared and may be in military service, SCRA default-judgment safeguards also apply. See 11 U.S.C. § 362 and the federal judiciary’s SCRA guidance.

Related compliance reading

For adjacent compliance topics, see The e-OSCAR Defense: Navigating Metro 2® Dispute Codes & FCRA Liability and Call Center Operations: The Contact Frequency & Compliance Mandate.

Important limits

This article summarizes federal reference points for education and workflow design; it is not legal advice. State collection law, court-local rules, the debt and creditor type, the person’s service status, bankruptcy chapter, notice, prior filings, and the specific procedural posture can change the result. Have qualified counsel review any production procedure, litigation filing, proof-of-claim decision, or decision to resume activity.