Charts can be built using the datasets described below. To see definitions for columns in each dataset, click here.
|Invoice Level Spend||Data for invoices in your environment, such as spend-related totals and important billing dates. Useful for reporting on aggregate amounts at the invoice-level to highlight or compare billed, adjusted, and final amounts firms have been invoicing against matters over a specific period of time.|
|Invoice Line Item Level Spend||
Data for invoice line items in your environment ranging from general attributes for associated matters to spend-related totals. Useful for reporting on line item level to determine if billed rates are consistent with billed amounts for various task, activity, and expense codes.
|Invoice Allocations Level Spend||
Data for invoice-level allocations in your environment ranging from general attributes for associated matters to spend-related totals. Useful for reporting on amounts allocated against accounting code sets to determine how respective allocation amounts are being tracked and utilized.
This is the underlying dataset used for spend-based reports built using the Adhoc Reports Builder and the baseline dataset used in out-of-the-box spend reports provided for Enhanced Reporting (e.g., Spend Grids, Billed Matters, etc.).
Data for matters in your environment ranging from Legal Entities and Vendors to important activity/billing dates. Useful for reporting back on matter attributes, both general and custom, to further break down or compare the distribution of legal entities, matter leads, and vendors across matters.
Data for vendor records in your environment, such as recent billing activity and associated Vendor Groups (if applicable). Useful for highlighting or comparing matter volume across vendors or determining distribution of matters across vendors based on location, Vendor Groups, or other attributes.
Data for timekeepers who bill for work on matters in your environment, including rates and spend totals. Useful for showcasing rates over time for comparison and providing better visibility into approvals vs. rejections for submission.
Data recorded for legal requests submitted by users in your environment, including important datapoints for requests converted into matters. Useful for quantifying the amount of work requests coming into the legal department and determining the overall volume of requests that turn into matters. This helps law departments identify ways to improve self-service and capacity planning based on trends in requests.
Data recorded for accruals in your environment ranging from linked Legal Entities and Vendors to billed amounts and activity dates. Useful for determining how much has been accrued across matters and how much has been billed and adjusted. This can be used report on accrual amounts at the matter and vendor levels and to break out amounts by cost codes.
Data for approved budgets in your environment, including information related to budget health. Useful for providing better visibility on amounts/performance for both internal and external (if applicable) budgets at the matter or firm level.
|SimpleReview (if applicable)||
Data recorded for AI rules in your environment, including rule performance and vendor insights. Only applies if SimpleReview is enabled for AI-driven invoice review. Useful for seeing potential savings attached to flagged line items and which rules provide the largest and smallest amounts of potential savings.
For best results when building or editing charts:
- Be familiar with the datasets available in your environment (including custom attributes)
- Know your goal and/or which insights your chart is intended to provide
- Determine which chart type is best suited to visualize your data
- Confirm whether any existing charts address your need or can be cloned/customized
Custom attributes can be used to build new charts for the following datasets: Invoice Level Spend, Invoice Line Item Level Spend, Invoice Allocations Level Spend, Matters, Vendors, and Timekeepers.
Go to Administration > Custom Attributes in SimpleLegal to see the list of custom attributes in your environment and relevant information, such as field type and associated record types.
To export custom attributes as a spreadsheet for reference and further filtering, click Download XLSX above the list.
Review the following notes and other considerations about custom attributes before moving forward with chart configuration:
- New custom attributes added to SimpleLegal will not be pushed into datasets until:
- The custom attribute is present in at least one record (e.g., at least one matter)
- The 24-hour data refresh cycle for Enhanced Reporting has passed
- A custom attribute will only appear as a column option if the following applies:
- It is active in SimpleLegal
- It is scoped to at least one record type (i.e., Attribute Scope)
- It is present in at least one record (e.g., at least one matter)
- If a custom attribute used in a chart is later edited or deleted in SimpleLegal, the chart will no longer work. Make sure to edit charts accordingly when custom attributes are updated.
- Whether a custom attribute is available as a column option depends on the selected dataset.
The table below shows the naming convention for custom attributes that appear in datasets. The naming convention is driven by the Attribute Scope, which can be found under the last column under Administration > Custom Attributes and refers to the type of record(s) the custom attribute is designated for in SimpleLegal. For more information about custom attributes, click here.
|Attribute Scope||Column Naming Convention|
|Matter||Matter Attribute [Attribute-Name] (e.g., Matter Attribute Department)|
|Legal Entity||Legal Entity Attribute [Attribute-Name] (e.g., Legal Entity POC)|
|Purchase Order||Purchase Order Attribute [Attribute-Name] (e.g., Purchase Order Attribute Expense Code)|
|Invoice||Invoice Attribute [Attribute-Name] (e.g., Invoice Attribute Department)|
|Vendor||Vendor Attribute [Attribute-Name] (e.g., Vendor Attribute Region)|
If a custom attribute has more than one record type under Attribute Scope, there will be separate instances of it under the column names to help users choose the relevant option. Each one will be prefixed with the record type. For example, if a custom attribute "Project Type" is scoped for both matters and vendors, the columns would show "Matter Attribute Project Type" and "Vendor Attribute Project Type." See the image below as an example: