Matter type configuration in Onit is the setup that decides, for each kind of legal work, which fields a matter shows, which tasks it creates, which budget and billing rules apply, and which reports it feeds. Area of law tells you the legal domain. Matter type tells the platform how the work should actually run. A clean set of matter types turns every new matter into a predictable process, and a sprawling set turns the matter form into a guessing game for the people filling it in.
This guide covers how many types to build, what each one should hold, and how to keep the list under control.
What is matter type configuration in Onit?
Matter type configuration in Onit is the definition of each matter type as a reusable package of fields, workflow steps, tasks, and rules that loads when a user selects that type. It sits one level below the area of law and one level above any sub-type.
Each matter type usually controls two kinds of behavior. The first is what the matter looks like: the fields shown, which ones are required, the page layout, and the documents expected at each stage. The second is how the matter runs: the tasks created, the approvals required, the budget format, and the billing rules applied to invoices. When a matter type has no behavior of its own, it is only a reporting label, and it may belong in a separate attribute.
How many matter types should an Onit build have?
Most Onit builds work well with three to eight matter types per area of law, and 30 to 80 in total for a mid-size or large department. The right number is the smallest set where each type genuinely runs differently.
- Split when the process differs. Litigation, an internal investigation, and a piece of advice need different fields, tasks, and budgets, so they are separate types.
- Merge when only the label differs. “Supplier contract review” and “vendor agreement review” follow the same steps and belong in one type.
- Watch the catch-all. If an “Other” type grows past 5 percent of new matters, it is hiding a type you need.
A quick test helps: if two types would share an identical template, they are one type. Start a new build with the 10 to 15 types that cover most of your volume, run them for a quarter, and add more only when users keep asking for a type that does not exist.
How should matter types link to areas of law and sub-types in Onit?
Matter types in Onit should link to exactly one area of law each, and sub-types should link to exactly one matter type. That strict hierarchy is what makes cascading lists and roll-up reports reliable.
- Cascade the picklists. Users choose an area of law first and then see only the matter types that belong to it, and sub-types appear only when the matter type needs them.
- Reuse names deliberately. “Litigation” can appear under Employment and Commercial as two separate matter types, each with its own value in the master list.
- Keep one master list. Every matter type row names its parent value from the area of law classification, so a new type can never be created without a home.
Anything that describes a matter without changing how it runs, such as a business unit or a risk rating, fits better among the custom matter attributes that sit beside the classification fields.
What should each Onit matter type template include?
Each Onit matter type template should include the fields, page sections, documents, and starting tasks that every matter of that type needs on day one. A good template means a new matter is ready to work in under five minutes.
- Fields and layout. Required fields for that type only, grouped into sections that match how the team reviews the matter, with a target of 10 to 20 fields on the main view.
- Documents and tasks. A starting document checklist and three to eight standard tasks with owners and due dates that calculate from the open date.
- Reviewers and followers. Default reviewers and followers for the type, so the right people see the matter and its invoices from day one.
The forms behind these templates are built in the same way as any other Onit form, and the guidance on building custom app forms with Onit Forms Builder applies to matter templates too.
How should matter types drive workflows and task automation in Onit?
Matter types in Onit should select the workflow a matter follows, including its stages, approvals, reminders, and deadline tracking. Building the workflow once per type means the department runs each kind of work the same way every time.
- Stages and approvals. Each type has its own stage list, such as Intake, Active, Settlement, and Closed for litigation, with approval steps only where the type needs them.
- Automated tasks and reminders. Due dates, reminders, and deadline checks are created automatically, so routine follow-up stops depending on someone’s calendar.
- Key date tracking. Dates such as a limitation period or a closing date trigger reminders at set intervals before they fall due.
Aim for 80 percent or more of matter types to have at least one automated task. The types that remain manual are usually low-volume advice work.
How should budgets and fee arrangements vary by matter type?
Budgets and fee arrangements in Onit should be set per matter type, because the right budget format for a lawsuit is different from the right one for a transaction or a piece of advice. Matter type is the natural place to store the default.
Fee arrangements already vary by type of work. A 2025 benchmarking survey of law departments found that 25 percent used fixed or flat fees for some intellectual property work and 14 percent used capped fees on M&A matters, which is exactly the kind of choice a matter type default should carry.
Set a default budget format per type, such as phase-based budgets for litigation, a single fixed amount for routine advice, and life-of-matter budgets for transactions. Preset the fee arrangement the same way, hourly, capped, or fixed, with a reviewer able to change it on an individual matter.
How should UTBMS codes and billing rules map to matter types?
UTBMS code sets and billing rules in Onit should map to matter types, so invoices on each matter are validated against the codes that fit the work. A litigation invoice and a transaction invoice should be checked against different task codes.
The standard provides several families to choose from, with published UTBMS code sets for litigation, bankruptcy, counseling, project, workers’ compensation, criminal law, and real estate work. Point each matter type to the code set its invoices must use, and flag invoices with codes from the wrong set. Rules such as staffing limits or expense caps can then apply only to the matter types where they make sense.
How should intake default the matter type in Onit?
Intake in Onit should default the matter type from the business user’s request type, so the user describes the problem in plain language and the system sets the classification. Business users rarely know which matter type fits their request.
Map each intake request type to a default area of law and matter type for when the request becomes a matter, and have the legal triage owner confirm or change the default, with every change logged. A well-mapped build defaults the right matter type for 90 percent or more of requests, with manual overrides at 10 percent or below. A rising override rate is the clearest sign that a request type needs remapping.
How do you test and govern Onit matter type configuration?
You test Onit matter type configuration by scripting each type end to end before go-live, and you govern it with a single owner, a change process, and a quarterly review. A build with 40 matter types typically needs 60 to 100 test scenarios.
- End-to-end tests. For each type, create a matter from intake, confirm the template, tasks, workflow, budget, and code set, submit a test invoice, and close the matter.
- Ongoing governance. New types need a business case and sign-off, retired types stay on historical matters, and any type with no new matters in 12 months is reviewed for retirement.
- Change log. Every added, renamed, or retired type is recorded with a date and an approver, so shifts in historical reports can be explained.
Plan one to two weeks of user acceptance testing with users from each area of law.
Conclusion
Matter type configuration works best when each type earns its place by running differently, links cleanly to one area of law, and carries its own template, workflow, budget format, and billing code set. Default the type from intake, review the overrides, and give the list a single owner who reviews it each quarter. The result is a matter form users can fill in quickly and a set of reports that compare like with like.
How Basla can help
Basla provides delivery teams for Onit implementation, covering business analysis, taxonomy and matter type design, template and workflow configuration, budget and billing rules, intake mapping, testing, documentation, and post-go-live support. Basla brings legal technology consulting and hands-on configuration through staff augmentation or a Basla-managed delivery unit, so your program can scale without slowing down.
Basla teams have delivered matter management and eBilling across 10 or more global jurisdictions and doubled delivery team size to meet compressed implementation timelines.
Frequently asked questions
What is matter type configuration in Onit?
Matter type configuration in Onit is the setup that gives each type of legal work its own fields, tasks, workflow, budget format, and billing rules. Selecting a matter type loads that package onto the new matter.
How many matter types should a legal department have?
Most departments need three to eight matter types per area of law, or 30 to 80 in total. Two types that would share an identical template should be merged.
What is the difference between matter type and area of law?
Area of law names the legal domain, such as employment or commercial. Matter type names the kind of work within it, such as litigation, advice, or an investigation, and decides how the matter runs.
Should each matter type have its own template?
Each matter type with recurring volume should have its own template with fields, documents, and starting tasks. Low-volume types can share a general template until volume justifies a dedicated one.
How do UTBMS codes relate to matter types?
UTBMS code sets should be mapped to matter types so invoices are checked against the right task codes. Litigation, counseling, project, and bankruptcy work each have their own code set.
How often should matter types be reviewed?
Matter types should be reviewed every quarter by a single owner in legal operations. Types with no new matters in 12 months are candidates for retirement.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*