LEDES XML E-Billing Ver. 2.2

LEDES XML E-Billing Ver. 2.2 - LEDES XML E-Billing Ver. 2.2 is a standardized format for electronic billing used in legal practice, which includes various segments such as tax, expense, fee, and matter information, and is a child of the Standards Compatibility class.

Class Information

JSON JSON-LD OWL XML Markdown

Identification

Label (rdfs)
LEDES XML E-Billing Ver. 2.2
Preferred Label
None
Alternative Labels
N/A
Identifier
N/A

Definition and Examples

Definition
LEDES XML E-Billing Ver. 2.2 is a standardized format for electronic billing used in legal practice, which includes various segments such as tax, expense, fee, and matter information, and is a child of the Standards Compatibility class.
Examples
  • N/A

Translations

N/A

Class Relationships

Is Defined By
N/A
See Also
N/A

Additional Information

Comment
N/A
Description
N/A
Notes
  • N/A
Deprecated
False

Metadata

History Note
N/A
Editorial Note
N/A
In Scheme
N/A
Source
N/A
Country
N/A

Graph

LEDES XML E-Billing Ver. 2.2LEDES XML E-Billing Ver. 2.2 - LEDES XML E-Billing Ver. 2.2 is a standardized format for electronic billing used in legal practice, which includes various segments such as tax, expense, fee, and matter information, and is a child of the Standards Compatibility class.Standards CompatibilityStandards Compatibility - Existing standards (e.g., UTBMS, LEDES, PACER) and their components' mappings (relationships) to their FOLIO counterparts.tax_matter_disc_cred segmenttax_matter_disc_cred segment - "The specific taxes relevant to the parent MATTER_DISC_CRED items. There will be 0 or more TAX_MATTER_DISC_CRED segments for each MATTER_DISC_CRED segment. Note that the EXTEND_HEADER option was purposely omitted from this segment. "expense segmentexpense segment - Expense segment refers to a specific component within the LEDES XML E-Billing Ver. 2.2 standard, which includes information such as charge date, units, work location, expense code, and total amount for billing purposes.tax_tier_summary segmenttax_tier_summary segment - "Summarizes the Tiered Taxes charged on this matter/invoice detailed in TAX_TIER_DETAIL by tx_id. There will be 0 or more TAX_TIER_SUMMARY segments per INVOICE segment. There will be 1 TAX_TIER_SUMMARY segment for each TAX.tx_id where TAX.'tax_tiers = ""Y"". Note that the EXTEND_HEADER option was purposely omitted from this segment. "tax_summary segmenttax_summary segment - "Summarizes the taxes charged on this matter/invoice. There will be 0 or more TAX_SUMMARY segments per MATTER segment. Note that the EXTEND_HEADER option was purposely omitted from this segment. "matter_disc_cred segmentmatter_disc_cred segment - The "matter_disc_cred segment" is a component of the LEDES XML E-Billing Ver. 2.2 standard that includes information related to discounts or credits applied to a matter, such as the type, amount, and category of the discount or credit.fee segmentfee segment - "The fee items included in the matter/invoice. There will be 0 or more FEE segments per MATTER segment. All fee items are subject to the same MATTER_DISC_CRED.disc_cred MISF (Matter/Invoice Shared Fee) and MIDB (Matter/Invoice Discounted Bill) as all expense items for this matter/invoice. If fee items are not subject to the same MISF or MIDB, they should be billed in a separate invoice. E-Billing system rules that limit law firms to submitting only one invoice per quarter (or other time period) will need to change their logic so that bills of this type will be accommodated."tax_tier_detail segmenttax_tier_detail segment - "There will be 0 or more TAX_TIER_DETAIL segments per file. If no TAX.tax_tiers is defined, no TAX_TIER_DETAIL section would be included in the file. This segment must fully define each of the tiers involved in the tax calculation, even if the invoice total is less than the tax tier. This segment defines the tax tiers specified in TAX.tax_tiers and tallies the amount of tax at each tier for this invoice. Unlike regular taxes, Tiered Taxes roll up to the invoice level whereas regular taxes roll up to the matter/invoice level. A Tiered Tax is one where the tax rate can vary depending on the total of the file. As compared to other kinds of taxes where a flat tax rate applies to the taxable item total, multiple tax rates apply. All tiers associated with the Tiered Tax as set forth by the tax authority must be represented in this segment, even if the tier exceeds the total of taxable items in the file. Illustration: Let's say there is a Tiered Tax where the tax rate is 10% for $0 to $25,000, 12.5% for $25,000 to $50,000, 15% for $50,000 to $100,000, 17.5% for $100,000 to $200,000, and 20% for amounts above that amount. Let's also say that an invoice includes $125,000 in taxable items subject to the Tiered Tax. For $125,000 in taxable detail, the TAX_TIER_DETAIL segment would include 5 lines for each of the 5 defined tiers as follows: tier 1 ($0 >= $25,000) = $25,000.00 * 10% = $2,500.00 tax due tier 2 ($25,000.01 >= $50,000) = $25,000.00 * 12.5% = $3,125.00 tax tier 3 ($50,000.01 >= $100,000) = $50,000.00 * 15% = $7,500.00 tax due tier 4 ($100,000.01 >= $200,000) = $25,000.00 * 17.5% = $4,375,00 tax due tier 5 ($200,000.01 and above) = $0 * 20% = $0.00 tax due Every tier must be defined in the file regardless of whether it exceeds the amount of taxable items. Using the example above, the TAX_TIER_DETAIL segment must include a representation for tier 5. The total tax due on this tiered tx_id then is $17,500.00 (the sum of the amounts above in blue). "contact_info segmentcontact_info segment - "This is not an actual segment of the file, per se, like the rest of the segments listed above. This segment contains a list of fields that will be used to represent contact information. When a contact is requested in a segment, that element will be listed and all fields in this segment will be the children of that element. The EXTEND_HEADER segment was purposely omitted from this segment. "regulatory_statement segmentregulatory_statement segment - "As e-billing expands around the world, it is likely that local, regional or national regulations require specific information to be included on electronic invoices. This section is designed to accommodate those requirements, to the extent that they apply to the matter/invoice level, without needing to adjust the format. In that this information is required by statute or regulation to be provided, all information provided in this segment should be captured by the receiving system and displayed during bill review. There will be 0 or more REGULATORY_STATEMENT segments per INVOICE segment. The EXTEND_HEADER option was purposely omitted from this segment. "tax segmenttax segment - "A lookup segment for the taxes charged in the file. There will be 0 or more TAX segments per file. If items are not taxed, no TAX section would be included in the file. The EXTEND_HEADER option was purposely omitted from this segment. "fee_item_disc_cred segmentfee_item_disc_cred segment - "All discounts, credits and Alternate Fee Agreement items applied to the parent fee line item. There will be 0 or more FEE_ITEM_DISC_CRED segments per FEE item. Note that the EXTEND_HEADER option was purposely omitted from this segment. "matter segmentmatter segment - A matter segment is a component of LEDES XML E-Billing Ver. 2.2 that includes various details related to a legal matter, such as matter ID, description, billing type, associated line items, and contact information.tax_item_fee segmenttax_item_fee segment - A tax_item_fee segment is a component of the LEDES XML E-Billing Ver. 2.2 standard that includes information about a specific tax or fee charged in a legal matter, identified by a unique transaction ID and file item number.tax_item_expense segmenttax_item_expense segment - A tax_item_expense segment is a component of the LEDES XML E-Billing Ver. 2.2 standard that includes information about a specific tax expense, such as a tax identification number and file item number.firm segmentfirm segment - "Information on the firm whose invoices have been submitted. There will be 1 or more FIRM segments per file. Allows for the submission of invoices for more than one firm in the same invoice file. Each file should begin with the FIRM segment. "invoice segmentinvoice segment - "Information on the Invoices submitted by the Firm for the Client. There will be 1 or more INVOICE segments per CLIENT segment. "extend_header segmentextend_header segmentexpense_item_disc_cred segmentexpense_item_disc_cred segment - "All discounts, credits and Alternate Fee Agreement items applied to the parent expense line item. There will be 0 or more EXPENSE_ITEM_DISC_CRED segments per EXPENSE item. This segment excludes discounts taken at the MATTER_DISC_CRED level. Note that the EXTEND_HEADER option was purposely omitted from this segment. "client segmentclient segment - "Information on the Client(s) for whom bills are submitted by the Firm. There will be 1 or more CLIENT segments per FIRM segment. "extend_data segmentextend_data segment - "The EXTEND_DATA segment is the child of EXTEND_HEADER segment. There will be 1 or more EXTEND_DATA segments per EXTEND_HEADER. It is not intended that the EXTEND_DATA include a file_item_nbr. Note that the data definition in this segment is for readability and not formatting. The EXTEND_DATA elements, ext_name and ext_value appear on the same line, the former as the XML field tag and the latter as the field value, in the EXTEND_HEADER segment. Each EXTEND_DATA segment may contain multiple rows of data that extend the applicable segment. "tksum segmenttksum segment - A "tksum segment" is a component of the LEDES XML E-Billing Ver. 2.2 standard that includes information such as the timekeeper's first and last name, ID, and billing rate.address_info segmentaddress_info segment - "This is not an actual segment of the file, per se, like the rest of the segments listed above. This segment contains a list of fields that will be used to represent address information. When an address is requested in a segment, that element will be listed and all fields in this segment will be the children of that element. The EXTEND_HEADER option was purposely omitted from this segment."sub_class_ofparent_class_ofsee_alsois_defined_byselfsub_class_ofparent_class_ofsee_alsois_defined_by