TyMetrix 360 for Law Firms: Invoice Submission Guide

Introduction

TyMetrix 360 is an e-billing portal used by corporate legal departments and insurance carriers to receive, validate, and review outside counsel invoices. For law firms submitting invoices through the platform, understanding how TyMetrix 360 processes submissions — and what causes rejections — determines whether an invoice moves to payment or returns for correction.

In navigating the complexities of invoice submission through TyMetrix 360, understanding the nuances of LEDES file structures and carrier guidelines is crucial. The platform accepts invoices in LEDES 1998B format, the standard defined by the LEDES Oversight Committee, but portal validation rules and client-specific outside counsel guidelines layer additional requirements on top of the base specification. When a file clears technical validation but violates a guideline provision — block billing, prohibited task codes, or missing pre-approvals — the invoice enters the bill review queue, where reductions and appeals follow.

The TyMetrix 360 Appeals Module streamlines the back-and-forth when a line item is reduced or rejected. According to Wolters Kluwer's published materials, the module is designed to efficiently handle large volumes of invoice appeals, eliminate time spent reconciling resubmitted invoices, and improve communication with outside counsel. For firms submitting dozens of invoices each month, that communication channel becomes the difference between a quick resolution and a protracted dispute over a single 0.3-hour entry.

Most invoice problems surface at one of three checkpoints: file validation when the LEDES file is uploaded, guideline compliance review when the bill reviewer applies the client's outside counsel guidelines, and narrative sufficiency review when the reviewer determines whether a line item's description supports the time or expense claimed. Each checkpoint has its own rejection codes, its own appeal path, and its own documentation requirements. Knowing which checkpoint flagged an entry tells you what evidence to submit in response.

When reviewing carriers' published guidelines, the most common reasons for invoice reductions follow a consistent pattern: entries for travel, intra-office conferences, and administrative tasks billed at attorney rates appear on nearly every carrier's prohibited or disfavored list. These are not arbitrary preferences — they reflect the billing standards that carriers enforce through TyMetrix 360 and similar e-billing portals. A firm that bills 0.5 hours for an intra-office conference without a guideline exception will see that entry reduced, regardless of how detailed the narrative is.

The sections that follow walk through the common problems firms encounter when submitting invoices via TyMetrix 360, the solution steps for avoiding and resolving rejections, and the appeal mechanics when a reduction reaches the firm's desk.

Problem Statement

Law firms submitting invoices through TyMetrix 360 encounter rejections that disrupt billing cycles and delay payment. A rejection is not the same as a mark-down. When a client rejects an invoice, they are required to include a comment explaining the reason. Clients generally reject an invoice when the issue cannot be resolved with a simple mark-down (reduce and approve). Contact the client if the reason for rejection is not apparent to you.

Why Invoices Get Rejected Instead of Reduced

A reduction adjusts a line item's dollar amount without sending the invoice back to the firm. A rejection returns the entire invoice for resubmission. The distinction matters: a reduced invoice still moves to approval, while a rejected invoice stops the workflow entirely. Rejections typically stem from structural problems — missing required fields, incorrect UTBMS task codes, or narrative deficiencies that prevent the reviewer from evaluating the work at all.

Our team frequently encounters scenarios where the LEDES 1998B format, as defined by the LEDES Oversight Committee, is not fully adhered to by some e-billing portals. These portals may accept files that omit fields marked as required by the specification, leading to potential rejections or validation issues when the file reaches the client's bill review system.

Common Structural Deficiencies That Trigger Rejection

Block billing — combining multiple distinct tasks into a single narrative — is one of the most frequent causes of rejection. A single entry reading "research motion, draft brief, confer with client, 6.5" gives the reviewer no basis to evaluate each activity separately. Most carrier guidelines prohibit block billing outright, and reviewers cannot reduce what they cannot itemize. The result is rejection with instructions to resubmit itemized entries.

Missing or incorrect UTBMS codes also force rejections. When a timekeeper uses a generic task code or leaves the activity code field blank, the client's system cannot route the charge to the correct budget category. Some clients' systems auto-reject invoices with placeholder codes; others flag them for manual review, which delays approval and often results in rejection if the firm cannot clarify the coding within the review window.

Narrative insufficiency is another structural barrier. An entry that reads "review documents, 2.3" does not identify which documents, for what purpose, or in what context. The reviewer cannot determine whether the work was necessary, duplicative, or within the scope of the engagement. When the narrative does not permit evaluation, the line item is rejected, and if enough line items fail, the entire invoice is returned.

The Resubmission Burden

Once an invoice is rejected, the firm must locate the rejection notice, interpret the client's comment, correct the underlying issue, and repost the invoice through TyMetrix 360. The reposting process requires accessing the rejected invoice from the Action Items section of the portal, making the necessary changes, and resubmitting the file. Each resubmission restarts the review clock, delaying payment by days or weeks depending on the client's review cycle.

Rejections also create internal coordination problems. The timekeeper who originated the entry may not be the person who handles resubmission. The billing coordinator must reconstruct the work from memory or contemporaneous records, re-code the entries, and ensure the revised invoice matches the client's guideline requirements. If the firm does not maintain detailed time records, resubmission becomes guesswork, and the second submission may be rejected for different reasons.

A rejected invoice stops the workflow entirely, and each resubmission restarts the review clock.

Understanding these common rejection triggers allows firms to address structural deficiencies before submission. For a detailed breakdown of how block billing causes rejections and what constitutes sufficient narrative detail, consult the client's outside counsel guidelines and cross-reference them against the LEDES file before upload.

Solution Steps for Effective Invoice Submission

Submitting invoices through TyMetrix 360 requires attention to detail at every stage. The platform's validation logic mirrors the requirements set by the carrier or corporate legal department that mandated its use, which means a rejection is often a signal that the invoice violates a guideline provision rather than a portal error. Following a structured approach reduces rejection risk and shortens the approval cycle.

Tips and Tricks for Navigating Invoice Rejections

An invoice rejection in TyMetrix 360 does not close the matter. The platform provides structured workflows for appeals and resubmissions, and law firms that understand the timing and procedural requirements can recover line items that were initially reduced or rejected. The key is to act within the allowed window and to address the underlying issue that triggered the rejection.

Know Your Appeal Deadline

Most carriers impose a strict deadline for appeals. Markel, for example, allows appeals up to forty-five calendar days after payment of the original invoice is processed. Appeals submitted after that window will not be considered. The appeal must be submitted through the e-billing system's appeal module — in Markel's case, Legal Exchange — and not by email or separate correspondence. TyMetrix 360 similarly displays a Final Approval Date and an Appeal Allowed Until date on each invoice. As long as the current date falls within that window, the Appeal button remains active. Once the window closes, the reduction is final.

Contact the Client When the Rejection Reason Is Unclear

Clients are required to include a comment explaining the reason for rejection. When a rejection occurs, the comment field should state whether the issue is a missing narrative, an unsupported UTBMS code, a guideline violation, or another specific defect. If the comment is vague or absent, contact the client before resubmitting. Thomson Reuters Legal Tracker help documentation states that clients generally reject an invoice when the issue cannot be resolved with a simple mark-down, and that firms should contact the client if the reason for rejection is not apparent. A five-minute clarification call can prevent a second rejection and preserve the appeal window.

Use the Platform's Appeal Module, Not a New Invoice

When appealing a reduction, do not create a new invoice with the same line items. TyMetrix 360 and similar platforms include a dedicated appeal module that ties the appeal to the original invoice number. Markel's process, for instance, requires firms to log into Legal Exchange, navigate to the invoice in question, and click the Appeal button to launch the Adjusted Line Items Dialog. The dialog allows the firm to provide additional detail or documentation for each reduced line item. Submitting a new invoice instead of using the appeal module creates reconciliation problems for the client and may result in duplicate payment tracking or outright rejection of the new submission.

Provide Specific Detail in the Appeal Narrative

The appeal narrative is not the place to restate the original line-item description. It is the place to explain why the reduction was incorrect or to supply the missing information that caused the rejection. If the reduction code indicates block billing, break out the individual tasks and their durations. If the reduction code indicates an unsupported activity code, cite the carrier guideline provision that permits the code or explain why the task falls within an allowed category. If the reduction code indicates excessive time, provide contemporaneous records or a breakdown showing the work performed. Generic appeals — "we believe the time was reasonable" — do not move the needle.

For more guidance on how to structure narratives that satisfy carrier requirements, see our article on Block Billing: Reasons for Carrier Rejections and Solutions.

Track Reduction Codes and Patterns Across Invoices

If the same reduction code appears on multiple invoices, the issue is systemic, not isolated. Review the carrier's outside counsel guidelines to identify the provision being violated, then adjust time-entry practices firm-wide. Common reduction patterns include entries for travel time billed at attorney rates, intra-office conferences without detail, and administrative tasks that fall below the guideline's staffing-ratio requirements. Tracking reduction codes by timekeeper and task code allows the firm to address the root cause rather than appealing each invoice individually.

Repost Rejected Invoices Promptly

When an invoice is rejected outright rather than reduced and approved, the firm must repost a corrected version. Thomson Reuters Legal Tracker allows users to access rejected invoices from the homepage Action Items section. The reposted invoice should address every item listed in the rejection comment. Do not resubmit the same file hoping for a different result. If the rejection cited a LEDES validation error, correct the file structure. If it cited a missing matter number or incorrect billing increment, fix those fields before reposting. Each resubmission restarts the client's review clock, and repeated rejections delay payment and damage the firm's standing with the client.

Conclusion

TyMetrix 360 serves as the submission destination for invoices from panel counsel and independent counsel across dozens of carriers and corporate legal departments. The platform's validation logic, rejection workflows and appeals module are not optional features—they are the path every submitted invoice travels. Law firms that understand LEDES 1998B field semantics, UTBMS task and activity code assignment, and the narrative detail standards embedded in carrier outside counsel guidelines will see fewer rejections and faster payment cycles.

In navigating the complexities of invoice submission through TyMetrix 360, understanding the nuances of LEDES file structures and carrier guidelines is crucial. The most common reasons for invoice reductions include entries for travel, intra-office conferences and administrative tasks billed at attorney rates. This pattern is consistently flagged across the guidelines we analyze. By aligning invoice submissions with these insights, law firms can better anticipate and mitigate potential rejections in TyMetrix 360.

The Appeals Module within TyMetrix 360 empowers legal bill review units to proactively resolve billing issues and handle large volumes of invoice appeals without requiring full invoice resubmission for every line-item dispute. Firms that track reduction codes, preserve contemporaneous records and respond to rejections with pinpoint corrections—rather than defensive narrative—will recover more write-downs and maintain stronger panel relationships.

For law firms seeking to optimise their invoice management workflow, the path forward is straightforward: read the controlling guideline, validate the LEDES file against the published specification, and submit invoices that require no interpretation. TyMetrix 360 processes what it receives; the responsibility for compliance, accuracy and narrative sufficiency belongs to the timekeeper and the billing coordinator. Additional guidance on common rejection causes and resolution strategies is available in our article on E-Billing Portal Invoice Rejections: Common Causes and Fixes.