ILTA Summer Conference, August 2023

The LEDES Oversight Committee is exhibiting again this year at ILTACon, look for us at booth #2005.
In addition, I will be speaking at a session on Monday Aug. 21st at 11:00 in Southern Hemisphere IV Ballroom for the LOC entitled “The Future of Legal Ebilling.” We are using the opportunity to discuss the LEDES API, version 2 of which is very close to posting for public comment and then ratification, as well as the testing platform that LOC is putting in place for 5 years to test API connections from Law Firm systems (sending invoices and other collateral, providing info (like rates), requesting information (like rate approval status), etc.) and from the ebilling vendor systems (to receive invoice files and other supported information, to reply back with information requested, or to acknowledge receipt information uploaded to their system).
As soon as this version of the API is ratified, our attention will turn to completing the API test platform, which we are offering to test the API connections made by both law firm systems and ebilling vendor systems. The platform will be available for a period of five years at significant cost to the organization. Our intention is to see that the API is developed as we intend, and operationally standard across vendor systems.
Imagine, a standard that is actually standard!
Lots going on that really could change legal ebilling as we know it today. If you can’t join us at the session, stop by our booth. And if you’re not at the conference, consider joining the LOC to support our financial commitment to this project. Membership is only $95 per year.


I am part of a very small team that is finalizing version 2 of the LEDES API.  Led by Sherry Askin and Robert Kraai, the rest of the team includes Jim Hannigan and me.


The idea for creating an API was the suggestion of Nicholas Puschak, a member of the LEDES Board of Directors, in 2018.  He envisioned a process that would facilitate system to system transmission of ebilling and other data required by law departments and other legal organizations that mandate their legal vendors to ebill.  The original idea was that API should allow law firm time and billing applications to communicate directly with the corporate legal department matter management and ebilling systems which would, in turn, allow law firm billing clerks to simply work within their time and billing applications to view the status of an invoice and to submit invoice, accruals and other legal data from within a single application without needing manual processing.  Nick led the effort working with a diverse group of subcommittee volunteers.  In February, 2020 version 1 of the API was released by the LOC. 

That we know of, only one law firm system, BILR by LSG, has implemented v.1 of the API; no ebilling vendors have implemented the standard.

Work on v.2 of the standard began organizing in June, 2020 again under the leadership of Nick Puschak.  The mandate was to look at issues noted in the original version and expand the functionality of the API.  Sadly, Nick’s retirement required a change in leadership and beginning in March 2023, new Co-Chairs were identified:  Sherry Askin and Robert Kraai, and a much smaller group has been meeting to work on the v.2 functionality 3 times a week since March, usually for 6-12 hours per week.

Like API v.1, API v.2 utilizes JSON, an open standard file and data exchange format. 

API v.2

API v.2 changes the name of some objects traditional to legal ebilling (business not client; vendor not law firm), reimagines the legal ebilling invoice structure (it is not visibly a relational database structure, instead it uses machine logic), and includes an automated JSON invoice format.

The updated draft v.2 specification includes the following functionality:

  • The ability for businesses to provide their information; for vendors to get information on all businesses within the system that require them to ebill; and for vendors to get information on a specific business requiring them to ebill.
  • The ability for vendors to provide their information; the ability for businesses to get information on vendors they require to ebill; and to get information on a specific vendor.
  • The ability to send or get location information.
  • The ability for businesses to send limited matter information; for vendors to get a list of matters assigned to their firm; and for vendors to get information on a specific matter.
  • The ability for vendors to send timekeeper profile information and to request profile information for a specific timekeeper.
  • The ability for vendors to send timekeeper rate information and to request rate information, including the status of rate approval, for a specific timekeeper.
  • For LEDES Invoice files, the ability to send an invoice, accrual or shadow invoice; the ability for the vendor to resubmit or replace an invoice; the ability of the vendor to send or get an invoice attachment; the ability of the business to send and for a vendor to get the status of an invoice; the ability of the business to send and for a vendor to get payment information; and the ability of a vendor to delete an invoice that has not yet been reviewed by the business. 
  • A new JSON ebilling format for use only by the API that includes the following functionality: the ability of the vendor to submit an automated invoice, to get id information on invoices sent and the ability of the vendor to query the status of a specific invoice; the ability of the vendor to resubmit an invoice; the ability of the vendor to appeal an invoice; the ability of the business to provide adjustment information on an invoice; the ability for the vendor to send an invoice attachment, for the vendor get an a list of invoice attachments, or for the vendor to get a specific invoice attachment; the ability of the business to send the invoice status, for the vendor to get a list of invoice statuses or for the vendor to get information on a specific invoice status; the ability for the business to send and the vendor to get invoice payment information; and the ability of the vendor to delete an invoice that has not yet been reviewed by the business.

We will be discussing the API in an educational session at ILTACon in August.  Check back for more information on the ILTA session, and the next steps toward ratification of the standard.

XML Ebilling Format Updates

Earlier this year, the LEDES Oversight Committee proposed revisions to the LEDES XML 2.0x, 2.1x and 2.2 ebilling standards. The public comment period for these changes closed on July 25, 2022 and there were no objections to the proposed changes.

While preparing the final paperwork to ratify these changes, additional discussion occurred on deficiencies that need correction in the XML formats. The documents presented here reflect these additional requested changes.

A new public comment period has opened and will close on December 9, 2022.

Significant to these changes are a number of requests by global ebillers to address insufficiencies in the current formats and processes. In particular, a change has been proposed that will require vendors to change the data element used for rate validation and require updating client electronic validation routines. While we have tried to minimize the number of changes required, this fundamentally changes how rate checking operates and represents a big effort on the part of vendors to enact.

Additionally, The LEDES Oversight Committee has scheduled 3 webinars on the proposed changes for which registration is required:

To attend the law firm-oriented webinar, scheduled on Wednesday, 7 December 2022 at 10:00 a.m. Eastern, register here.
To attend the law department-oriented webinar, scheduled on Wednesday, 7 December 2022 at 11:30 a.m. Eastern, register here.
To attend the vendor-oriented webinar, scheduled 7 December 2022 at 1:00 p.m. Eastern, register here.

To review the proposed changes or provide your opinion on the changes, click here.  

Proposed LEDES Standards for Public Comment

The LEDES Oversight Committee has two projects that have provided draft standards for public comment:

The first is from the Ebilling Standards subcommittee, which proposes updates to Ebilling XML 2.0x, 2.1x and 2.2x.  The changes are to correct an inadequate field length, add one field and align the standards.  You can learn more about the proposed changes and provide feedback to the LOC here.  

In addition, the IP subcommittee has proposed UTBMS codes specifically for Patent Prosecution matters.  This is a really interesting take on using UTBMS, allowing for codes that pair with the USPTO.    You can learn more about the proposed changes and provide feedback to the LOC here.  

The public comment period closes for both projects on July 25, 2022.

See you at ILTA’s Educational Conference

It is with great joy that we announce a return to the ILTA Educational Conference, 22 – 25 August, 2022. ILTA was the first supporter of the LEDES Oversight Committee and finally, as the pandemic moves into endemic phase, we will be back this year in August.

Conference participants can find the LOC in booth #534, with GLE founder and LOC President, Jane Bennitt, and Nadia Strobbia, LOC Secretary and Thomson Reuters powerhouse, on-site.

In addition, we will have a hospitality room on Tuesday, 23 August where we will be hosting:
– 11:30 – 12:300 – the LEDES Oversight Committee mid-year members’ meeting
– 1:30 – 2:30 – Open forum discussion on Ebilling Issues and Best Practices. This session is a continuation of a discussion started by our London Regional Group, and the discussion will lead to a Best Practices White Paper on for Law Departments and Insurance organizations looking to implement legal ebilling.

Both events will also be held via webinar for participation by LOC global members not at the conference.

In addition to the above, GLE Founder Jane A. Bennitt will participate in session #1714: Leveraging Technology to Manage Outside Counsel Guidelines, to be held on Wednesday, 24 August 2022 from 2:30 – 3:30. Co-participants include Scott Springer from HBR Consulting and Mark Agin from Shearman & Sterling.

LEDES API Vendor Survey Available

In October I wrote about the LEDES API initiative, for which version 2 is expected to be released in the next couple of months. To encourage development of the API, the LEDES Oversight Committee (LOC) will create an API testing platform and make this available to vendors in the legal space. A survey has been posted to establish a timeline for making the test platform available. Please go to to access the survey.

Below is background on the testing platform and project.


The purpose of the LEDES API is to facilitate system to system communication directly from the law firm to the third-party ebilling vendor. The API will facilitate the transmission of data files from the law firm to the ebilling vendor and accept notifications from the ebilling vendor back to the law firm.

 Why an API? Legal ebilling is extremely time-intensive to support at the law firm. The API will ease the burden at the law firm by automating transmission and notification processes where possible. A unified LEDES API will allow vendors to implemented solutions more quickly than if a custom API is required for each of the dozens of ebilling solutions in the marketplace. 

It is expected that several versions of the LEDES API will be released by the LEDES Oversight Committee over time, with each new version increasing the functionality supported by the API. V2 of the API is expected to be released in 2022. 

To facilitate the creation of these API connections, the LEDES Oversight Committee will create a testing platform for vendors to test their API functionality.  

Use-cases have been defined by the LEDES Oversight Committee to ensure the full breadth of functionality of the LEDES data exchange formats is supported by both types of systems. The LEDES Oversight Committee will provide written documentation to setup the test environment, including test clients, test law firms with timekeepers and rates, and test matters. Using this information, file transmissions supporting the use-cases will be tested, and based on the performance of the systems, the LEDES Oversight Committee will be able to score the quality of the API supported by the system, enforcing compliance with the full feature set supported by the LEDES formats. 

The LEDES Oversight Committee has selected LogicShark to build and support the test environment. LogicShark helps organizations design and implement digital transformation strategy to facilitate organizational change by using their low-code, application development software, the LogicShark CNECT Platform. Of importance to the LEDES Oversight Committee, LogicShark does not offer law firm or law department systems that utilize LEDES standards and is fully independent in this regard.

Understanding that vendors need to place the API on their development roadmap and secure funding and resources for its development, once the test environment goes live, it will be supported by the LEDES Oversight Committee for a minimum of five years. 

 It is important for the law firm back-office systems to consider how information can be incorporated into their data set. For example, it will be possible to

  • Note the date an ebill was submitted
  • Provide the current status of an ebill submission.
  • Note the amount approved for payment by the client
  • Calculate, based on the date a payment request is sent to Accounts Payable plus the days-to-pay specified by the client, an estimated date on which payment is expected
  • Note the actual date paid, plus the check number, transaction ID or other information associated with the payment provided by the ebilling vendor


System to system. We do not anticipate “home-grown” connections from the law firm to the ebilling vendors. Our intention is that the law firms’ back-office software (financial, time and billing, timekeeping, etc.) which generates LEDES invoice files would be the source of the law firm API. 

It may be the case that middleware could be developed as a transmission point from the law firm to the ebilling vendor, enabling support for smaller global firms that do not have the benefit of western-style back-office systems. We find it unlikely, however, that larger firms that have western-style back-office software would use this type of connection.

Notifications. The type of notifications from the ebilling vendor envisioned are those currently sent via email or via posted in the ebilling system. These include, but are not limited to, invoice submission results, rejection information, payment confirmation information, accrual requests, timekeeper/rate approvals, etc.

Increasing Functionality. v1 of the API supports the transmission of LEDES invoice files and the return of notifications on these submissions, and the ability for law firms to request the status of invoices. v1 assumed that when a legal service provider application communicates with an e-billing system it would require separate credentials for each client with which it would want to exchange information.

In v2, we are adding the ability to only require one set of credentials when communicating with an e-billing system and support a call to identify the clients for whom the legal service provider is exchanging information, facilitating more easily the submission of invoices to a specific client. The request to get the status of a set of invoices has been changed to use a “Modified Since” date/time instead of requiring the third-party ebilling vendor to support an “InvoiceStatusMarker.”   

The API subcommittee has also done some preliminary work to establish a JSON LEDES file format based on XML 2.2 and calls to exchange matters, timekeepers and rates, however these specific processes may be put off to a v3 release.

(This post was also shared on LinkedIn.)

Industry Acquisitions

While I have been busy with client work over the past few months, the legal ebilling industry has gone acquisition mad. Below are some highlights.

  • On 1 September, 2021, Bodhala was acquired by Onit
  • On 22 September, 2021, Alyne, a GRC company, was acquired by Mitratech
  • On 28 September, 2021, BusyLamp was acquired by Onit
  • On 3 November, 2021, Brightflag acquired Joinder, a corporate record keeping system
  • On 1 December, 2021, Integrum, a health, safety and environment platform was acquired by Mitratech
  • On 16 December, 2021, Continuity, a GRC provider, was acquired by Mitratech
  • On 17 December, 2021, Bottomline Technologies, a business payment conglomerate and owner of Legal-X, was acquired by Thoma Bravo
  • On 11 January, 2022, SecureDocs was acquired by Onit
  • On 19 January, 2022, Quovant was acquired by Mitratech