Judicial due diligence on Brazilian entities: the practical guide from M&A to credit

TL;DR: Judicial due diligence is the verification of court cases linked to a person or company before making a business decision — M&A, credit, supplier onboarding. In 2026 Brazil, with R$ 220 billion in M&A transactions in 2025 alone (per KPMG), ignoring a counterparty’s judicial exposure is accepting unnecessary risk. This guide covers when to do it, what to check, the real cost (manual vs API), legal coverage (LGPD art. 7, OAB Provimento 205/2021, Law 6,404 art. 158), and an actionable checklist. Estimated cost for 15 entities across 10 courts: R$ 6,000-10,000 manual vs R$ 15 automated — a 400-700x difference.

Judicial due diligence is the verification of court cases linked to a person or company before making a business decision. It’s essential practice in credit origination, mergers and acquisitions, supplier contracting, client onboarding, and any situation where the risk of inheriting hidden liabilities outweighs the cost of checking.

In Brazil, where more than 83 million active cases are in court according to the Justice in Numbers 2024 report from the CNJ, ignoring the judicial status of a counterparty means accepting unnecessary risk. And the Brazilian M&A market, which moved R$ 220 billion in 2025 per KPMG (+20% vs 2024), reflects exactly that perception: judicial due diligence became standard even in smaller transactions.

This guide covers, in depth, when to do it, what to check, what it really costs, what LGPD and OAB say, and an actionable checklist you can copy for your next deal.

For specific contexts, combine this guide with the deep dive on labor liability and Súmula 331 (the supplier and outsourcing angle) and on continuous lawsuit monitoring (what to do after the initial DD, until closing).

What judicial due diligence really is

Judicial due diligence isn’t “checking if there are lawsuits.” It’s the process of searching, analyzing, classifying, and documenting court cases to feed an informed commercial decision.

In practice, it involves 4 layers:

• Existence verification — are there cases? how many?
• Qualitative analysis — what’s the nature? labor, civil, criminal, tax, bankruptcy, administrative?
• Financial assessment — what’s the aggregate case value? are there first-instance convictions? provision reserve?
• Continuous monitoring — during the period between term sheet and closing, do new cases appear? (they frequently do — sellers often rush to settle pending matters before the deal)

Layer 4 is where many DDs fail. The first search is done at the beginning (week 1), and then the firm stops. But the deal takes another 60-90 days to close. In those 60-90 days, new cases can be filed against the target — and they’re precisely the most relevant for negotiation, because they may indicate the seller is trying to dispatch issues before closing.

When to do it — 7 typical situations

Situation	Why	Cost of not doing it
Merger or acquisition (M&A)	Identify hidden liabilities, size the indemnification reserve	Inheriting the target’s judicial debts — R$ 2-20M in medium transactions
Credit origination	Judicial score complementing the traditional bureau	Default from hidden liability the score doesn’t catch
Supplier contracting	Verify legal health and Súmula 331	Subsidiary liability, operational disruption
Client onboarding	KYC/KYB regulatory (BACEN Circular 3,978)	Fines, sanctions, license revocation
Executive hiring	Check the executive’s case history	Reputational risk, past labor claims
Commercial lease	Check lessee’s delinquency and history	Default, property damage, expensive eviction
Investment (VC, PE, private equity)	Hidden liabilities of the shareholders, litigation history	Investment in a company with hidden risk, forced impairment

Each situation has its own nuances. For M&A, scope goes far beyond the target — it includes shareholders, officers, controllers, and sometimes subsidiaries. For credit, it’s usually just the borrower’s CPF. For suppliers, it’s the CNPJ plus the shareholders’ CPFs when the contract is significant.

What to check — the structured checklist

Essential data (every DD needs this)

1. Case existence — how many cases exist in the searched database?
2. Role in cases — is the subject plaintiff, defendant, or intervenor?
3. Case type — civil, labor, criminal, tax, bankruptcy, environmental, administrative
4. Status — active, archived, on appeal, suspended, in execution
5. Case value — what amount is involved? (useful for estimating exposure)
6. Jurisdiction — in which states and courts are the cases?
7. Temporal distribution — are there recent spikes? (red flag — someone may be dispatching pending issues)

Advanced analysis (M&A, large operations, corporate credit)

8. Movement history — how has the case evolved? was there a ruling? at which instance?
9. Parties involved — is there a habitual litigation pattern? (see the specific post on vexatious litigants)
10. Decisions — was there a conviction? for what amount? did it become final?
11. Current instance — trial, appeals, special appeal, extraordinary appeal
12. Related cases — are there dependent cases (enforcement, attachments, related)?
13. Recurring lawyers — does the same opposing firm appear multiple times? may indicate a business relationship
14. Judges — what’s the reform rate on appeal? (signal of pleading technical quality)

A thorough DD answers all 14 questions. A rushed DD only answers the first 7. The difference is the quality of the red flags report delivered.

The cost of NOT doing it — 3 real scenarios

Scenario 1 — Credit without judicial verification

A fintech approves R$ 100,000 in credit for an entrepreneur based solely on the Serasa score (780 points, “good payer”). No judicial search. The entrepreneur has 8 active labor claims totaling R$ 500,000 in aggregate case value and 3 tax execution cases from the Federal Revenue. Six months later, he’s hit by a generalized judicial freeze (BacenJud tools) and the fintech becomes an unsecured creditor in the estate. Estimated recovery: 5-15% of value.

• Cost of prior verification: R$ 1.00 (10 queries × R$ 0.10)
• Cost of non-verification: R$ 85,000-95,000 in net loss
• Verification ROI: 85,000x to 95,000x

Scenario 2 — Acquisition without full judicial DD

A company acquires a mid-sized competitor for R$ 25 million. The contracted DD is “express” and covers only the target (CNPJ), not the shareholders or officers. Three months after closing, R$ 4.3 million in labor claims against the majority shareholder from previous operations are discovered — and part extends to the acquired company via subsidiary/joint liability.

• Cost of complete verification (15 entities × 10 courts): R$ 15-20
• Cost of non-verification: R$ 4.3 million in unprovisioned liability
• Earn-out impact: hostile post-closing negotiation, lawyers on both sides for 12 months

Scenario 3 — Strategic supplier with pending bankruptcy

A retailer establishes an exclusive logistics supply contract with a transport company. The contract is based on a commercial proposal and references. No judicial DD. The transport company has a judicial recovery petition filed 8 months prior (public case, searchable). Four months after contracting, the company stops fulfilling the contract due to cash shortage.

• Cost of verification: R$ 0.50 (5 queries)
• Cost of non-verification: 3-week operational disruption + emergency contracting cost + commercial losses = R$ 2-5 million depending on sector

The scaling challenge — by decision volume

Occasional DD (1 deal, 15 entities) is manageable manually. The problem appears when volume increases:

DD volume/day	Viable method	Note
1-10 verifications/day	Manual	Slow, but feasible
10-100/day	Dedicated paralegal or intermediate tool	Manual doesn’t scale anymore; errors increase
100-1,000/day	Automated API	Only viable option
1,000+/day	API with dedicated infra (webhooks, batch)	Enterprise contracts

For fintechs and credit bureaus processing hundreds of applications daily, judicial DD needs to be automatic, integrated into the decision pipeline, and with response time in seconds — not hours. Otherwise, you’re either throttling the approval funnel or operating blind.

For M&A boutiques with 5-20 deals per quarter, automation frees paralegals for analytical work instead of copying CPFs between websites — and shrinks the risk window between “initial DD” and “confirmatory” because it’s cheap to run the search twice, three times, ten times.

Real cost comparison

The math matters. Table based on real market prices:

Method	Cost per entity (10 courts)	Time per entity	Scale
Paralegal/intern (manual)	R$ 15-30 (labor hour)	30-90 min	Low
Boutique firm (partner supervising)	R$ 50-150	15-30 min + overhead	Medium
Legal software with subscription	R$ 50-200/month + variable per query	Variable	Medium-high
Vigilant (pay-as-you-go API)	R$ 1.00	< 60 seconds	High

Automation ROI — math for a mortgage credit bank

For a mortgage bank verifying 100 borrowers per day across 10 courts:

	Manual	Vigilant
Cost per verification	R$ 20.00 (paralegal time)	R$ 1.00 (10 queries)
Daily cost	R$ 2,000	R$ 100
Monthly cost (22 business days)	R$ 44,000	R$ 2,200
Monthly savings	—	R$ 41,800 (95%)
Annual savings	—	R$ 501,600

Even assuming Vigilant doesn’t eliminate 100% of paralegal work (human analysis always remains), net savings run ~R$ 30,000-40,000/month. For M&A operations, the proportional savings are even higher because volume concentrates in 2-3 month windows per deal.

For real pricing and credit packages, see /en/pricing/.

Data returned per Vigilant query

For each CPF/CNPJ searched, the API returns cases found across all requested courts, in a standardized structure:

• CNJ number (national standard case ID)
• Case class and type (Civil Procedure, Tax Execution, Labor Claim, etc)
• Parties involved (plaintiff, defendant, lawyers)
• Chronological movement history
• Subjects (CNJ topic classification)
• Case value
• Current status (active, archived, on appeal, suspended)
• Instance (trial and appellate, when applicable)
• Jurisdiction (court, chamber, district)
• Original case URL on the source portal (for manual opening when detail is needed)

All in standardized JSON, regardless of the source court. This matters for M&A because the analyst doesn’t need to learn each portal’s layout — they consume the same data shape from any covered court. To integrate into your flow, the technical docs at /en/developers/ have examples in cURL, Python, Node.js, and Go.

Legal aspects — LGPD, OAB, and administrator liability

LGPD (Law 13,709/2018)

Judicial DD falls under 3 simultaneous legal bases in Brazil’s data protection law:

• Art. 7, §4 — dispenses consent for data “made manifestly public by the subject.” Court cases whose public lookup is provided by the court fit exactly this definition
• Art. 7, VI — “regular exercise of rights in judicial, administrative, or arbitration proceedings.” For DD in regulated transactions (public company M&A with CVM, for example), this is the safest basis
• Art. 7, IX — “legitimate interests of the controller or a third party.” Covers general commercial DD (supplier, executive hire, corporate client)

Vigilant accesses exclusively public data made available by the courts themselves. No access to sealed cases, cases under judicial secrecy, or any protected information.

Keep a per-query audit log (Vigilant’s API generates this automatically and exposes it via the history endpoint) and you have an auditable trail for any challenge from ANPD or the data subject.

OAB — Provimento 205/2021

Provimento OAB 205/2021 governs legal advertising — it doesn’t affect internal automation of research. Using APIs and software for judicial DD lookup is an operational activity, fully permitted. The OAB actually encourages technology adoption by lawyers.

Administrator liability for NOT doing DD

This is the point many forget: not doing due diligence can constitute administrator fault. Law 6,404/76 (Corporations Act), art. 158, holds directors liable for acts contrary to the company’s interest. The Civil Code, art. 1,016, holds managing partners of limited liability companies liable for negligence. And art. 1,011 of the same code requires “the care and diligence that every active and honest person customarily employs in managing their own business.”

In practice: an administrator who approves a R$ 25 million acquisition without adequate judicial DD can be personally liable if hidden liabilities appear — especially in a public company transaction with disadvantaged minority shareholders. DD isn’t optional for a prudent administrator.

Judicial due diligence checklist — expanded version

• Map the universe of CPFs/CNPJs to search
  • Primary target (CNPJ)
  • Direct shareholders (CPFs)
  • Ultimate controllers (CPFs/CNPJs of individuals and entities in the control chain)
  • Statutory officers (directors, board members)
  • Relevant subsidiaries and affiliates
• Define the relevant courts
  • State court at headquarters (TJSP, TJRJ, etc)
  • State court at each branch/relevant operation
  • Federal court for the region (TRF1-TRF6)
  • Labor court (TRT for each operation’s region)
  • Administrative when applicable (CADE, ANPD, Revenue)
• Execute the search — manual or via API
• Check both instances (trial and appellate)
• Catalog cases found in a structured spreadsheet
• Classify by criticality — high/medium/low risk
• Calculate aggregate value of potential liability
• Identify patterns — recent spikes, habitual litigation, recurring lawyers
• Document results in the red flags report
• Define adjustment clauses — escrow, earn-out, indemnification cap based on calculated exposure
• Establish continuous monitoring until closing (see lawsuit monitoring)

Vigilant coverage

Vigilant covers 12 judicial sources across 10 Brazilian states today, including TJSP, TJRJ, TJMG, TJDFT, TJBA, TJCE, TJPE, TJMA, TJAP, TJAC, TJAM, TJAL — all ESAJ or PJe, both instances. The full list, status per court, and expansion plans are at /en/courts/. Pricing starts at R$ 0.10 per court queried, no subscription or contract — see /en/pricing/.

For enterprise operations with high volume (thousands of verifications per month), or for direct integration into your approval/closing engine, it’s worth talking to the team at /en/contact/.

Glossary

Term	Definition
Due diligence	Structured investigation process of a company, person, or asset before a commercial decision
Red flags report	Consolidated document listing risks identified in DD, organized by criticality
Target	The company being acquired in an M&A transaction
LOI	Letter of Intent — preliminary document formalizing interest in buying
Term sheet	Document with the deal’s main terms, pre-contractual
Confirmatory	Deep DD phase that occurs after the term sheet, before closing
Closing	Formal deal completion, with transfer of control
Earn-out	Portion of the purchase price contingent on post-closing metrics
Escrow	Deposit in a third-party account, released per contract clauses
Subsidiary liability	Secondary obligation — only becomes effective if the primary party doesn’t pay

Conclusion

Judicial due diligence in 2026 has moved from “nice to have” to operational requirement for anyone making data-driven commercial decisions. With 83 million active cases in the country, R$ 220 billion in annual M&A, and regulation (LGPD, OAB, Law 6,404) that provides clear legal basis for consultation and holds administrators who skip DD liable, the cost of not doing it has become much higher than the cost of doing it.

The difference between quality DD and checkbox DD is, today, a matter of tooling. Searching 150 entities across 10 courts manually takes 20-40 hours. Via API, it takes 15-30 minutes of processing + the analyst’s time to interpret the data. You decide where to spend the 20 saved hours — analysis, deal negotiation, or simply running more deals.

If you want to see the full commercial layer — how Vigilant fits into M&A, credit, or compliance workflows — check our M&A and due diligence solutions page. To integrate into your approval pipeline, the technical docs have the path. And for a direct conversation about enterprise volume, /en/contact/.

---

Automate your judicial due diligence. 5 free credits on signup, no credit card. Start now.