Business management · Legal and Collections
A full legal operation inside the ERP: litigation, court calendar, publication capture, pleadings, documents, collections, settlements, enforcement, labor, provisions, advisory and compliance. Intake into the pipeline is automated by plan, the desk works a portfolio instead of a blind queue and the debtor's legal capacity is verified before any measure. Every action respects its own permission, keeps an audit trail and reuses data already in the contract, installment, class and graduate record.
The problem and the fix
If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.
Cases, deadlines, documents and costs live in different spreadsheets and nobody sees the whole case.
The case file brings together parties, lawyers, docket entries, deadlines, hearings, pleadings, document management, financials, business links, access and audit trail.
A publication arrives through an official gazette or email, and the deadline depends on someone copying the date correctly.
DataJud, DJEN and push inboxes feed triage; the court calendar simulates the count and the lawyer confirms before the deadline is created.
External collection moves forward even when there is a settlement, a statute of limitations, incapacity, an unsigned contract or an incomplete address.
Locks are checked before notifying, protesting, credit reporting or filing suit; any exception requires explicit confirmation and is recorded in the audit trail.
The team puts the same effort into the entire portfolio and discovers the statute of limitations only after the debt is already lost.
Recoverability score, effort vs. return, contact lookup, aging and statute of limitations task forces prioritize where to act and show why each case is a priority.
A settlement is approved by message, but the installments never reach accounts receivable.
The proposal respects approval levels, records acceptance, issues the charge through the payment gateway and syncs compliance with the actual payments in finance.
Provisions, case costs and debt write-offs don't reconcile with accounting.
Contingencies, court fees, attorney fees, bad debt allowance, uncollectibles and debt assignments each have their own classification, approval and accrual period workflows.
The case enters the pipeline and sits there until someone remembers to draft the letter, print it, send the email and create the shipment.
The intake plan is designed once and the job runs it: letter, email, printing, Correios, label and task go out on their own, each step at most once per case.
The desk was a call collection queue and the legal analyst couldn't see the case, the deadline or the next step.
The desk lists the portfolio with urgency views and shows the ten-step legal collection schedule, the debt breakdown, the linked case and the graduate's full profile.
Collection aimed at a minor has no legal effect and comes back as a moral damages claim, but the system kept billing the graduate.
Legal capacity is checked on the signing date and today, the legal guardian becomes the effective debtor and external measures are blocked while nobody is liable for the debt.
A discount granted outside the desk comes in above what the policy allows, and only manual approval stops it.
The policy cap applies at every entry point: the desk, the settlements screen or an integration. Approval levels say who signs off, the cap says how far the policy lets you go.
In practice
Everyday situations at graduation companies, from the problem to the result, using the modules on this page.
A court summons was captured on DJEN overnight and called for a procedural step.
The publication entered the queue, AI suggested a classification and an owner, and the calendar simulated the due date considering the court's holidays and suspensions. The lawyer reviewed and confirmed.
The deadline was created with a traceable origin, a defined owner and alerts, without turning automated capture into a legal decision.
A case selected for credit reporting still had an active settlement and an address mismatch.
The capacity and lock checks blocked the action, showed each impediment and kept the case in the resolution queue.
The company avoided an irregular collection and kept a record of the reason, the handling and who released each step.
The debtor accepted a down payment and installment plan within the active negotiation campaign.
The simulator applied the discount range, routed approval through the right level and issued the installments through the configured payment gateway.
The desk now tracks promises and payments in the same workflow; payoff, cancellation and removal of credit restrictions no longer depend on a parallel control.
After the judgment, the case moved to enforcement with an asset seizure attempt and a court deposit.
Enforcement recorded the calculation worksheet, seizures, results, deposit, release order, summons and fine within the same case.
Legal and finance can now see the amount enforced, what was recovered and the cost of the case without reconciling spreadsheets.
An installment came due, the case entered the pipeline and the opening routine had always been manual: draft the letter, print it, email it and generate the postal pre-shipment.
The intake plan was designed once, simulated with a real case before turning it on and began running during business hours, with a daily cap and one run per step.
The notice goes out the same day the case opens, the physical copy lands in the print queue with its label and Correios tracking flows back into the letter's timeline.
The contract was signed when the graduate was 17, and collection had been aimed at him.
The system assessed capacity on the signing date and today, identified the guardian in the pre-registration record and flagged the missing items needed to qualify the representative.
Collection was redirected to the legal guardian, protest was locked until qualification and the statute of limitations was treated as suspended for as long as the absolute incapacity lasted.
How it works
Every step is a real module, and what comes out of one goes into the next without anyone typing it again.
Module by module
19 modules and 120 features on this page, all running on the same class, graduate and event records.
An executive view and a complete operational record for every case.
Deadline counting assisted by the court calendar and a unified team calendar.
Docket updates and summons come in from public sources or push inboxes, but only become actions after review.
Versioned drafting with separate steps for creating, reviewing, approving and filing.
Private, versioned files linked to the correct legal source.
The entire portfolio of open installments before legal steps in, not just what has already become a case.
Cadence by aging and a plan that runs the case opening routine on its own.
A portfolio with urgency views, a ten-step collection ladder and the debtor's full file on screen.
Explainable priority and a commercial policy frozen at the moment of the proposal.
Who is liable for the debt is established before collection, not discovered during a dispute.
Notices and external measures with procedure, files and responses tracked.
Negotiation within approval limits, with installments integrated into finance.
Portfolio hygiene and judgment enforcement handled as dedicated workflows.
External portfolio, SLA and legal cost measured per case.
The legal portfolio translated into accounting and financial decisions.
Labor liabilities and probable, possible or remote risk with history.
Internal requests with SLA and institutional positions reused.
Regulatory obligations and sensitive investigations with restricted access.
Per-action permissions, per-company settings and assistance without autonomous decisions.
Compare the modules and choose the setup that fits your operation.