Rolo de Fita Adesiva de Ledes RGB 5m 150 Leds - Manual Sonigate
LEDES Comparison List_v2.0
description
Transcript of LEDES Comparison List_v2.0
Version Ver 2.1 Field lf_vendor_id
DescriptionVersion Ver 2 Field lf_vendor_id
DescriptionVersion LEDES XML 2000Field lf_tax_id
DescriptionVersion LEDES98BI Field LAW_FIRM_ID
DescriptionVersion LEDES98BField LAW_FIRM_ID
Description
Law firm segmnet - 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.
A value that uniquely identifies the vendor. Depending on the location of the vendor, this value could be the vendor's tax id number, the vendor's VAT registration number, the vendor's DUNS number, the vendor's business registration number, or any other number or used by the vendor to uniquely identify itself, preferably to its local taxing or governmental authority.
A value that uniquely identifies the vendor. Depending on the location of the vendor, this value could be the vendor's tax id number, the vendor's VAT registration number, the vendor's DUNS number, the vendor's business registration number, or any other number or used by the vendor to uniquely identify itself, preferably to its local taxing or governmental authority.
Identifier(s) uniquely identifying the sending law firm. The law firm's Federal Taxpayer ID if operating in the U.S. or a tax identifier for non-U.S. firms. The field will accommodate up to three identification numbers through the use of a sub-delimiter (~). A null value ("") would be an error.
An identifier uniquely identifying the sending law firm. The law firm's Federal Taxpayer ID must be used if the law firm has one (i.e., at the very least, all law firms operating in the US). A null value ("") would be an error.
Ver 2.1 lf_id lf_name
The name of the law firm.
Ver 2 lf_id lf_name
LEDES XML 2000lf_id lf_name
LEDES98BI LAW_FIRM_NAME
LEDES98B
Law firm segmnet - 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.
An optional field assigned by the law firm to identify the firm.
An optional field assigned by the law firm to themselves to identify the firm.
The name of law firm.
Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
@lf_address @lf_remit_address
@lf_address @lf_remit_address
@lf_address @lf_remit_address
@lf_address
Sub Structure - Address Structure (See @ADDRESS_INFO Segment below).
Sub Structure - Address Structure (See @ADDRESS_INFO Segment below.) If not provided, then is assumed to be the same as @lf_address.
Sub Structure - Address Structure (See @ADDRESS_INFO Segment below).
Sub Structure - Address Structure (See @ADDRESS_INFO Segment below.) If not provided, then is assumed to be the same as @lf_address.
VRP: Should be derived as part of address segment. More info on fields in Address segment
@lf_billing_contact source_app
@lf_billing_contact source_app
@lf_billing_contact
Sub Structure - Contact Structure (See @CONTACT_INFO Segment below.)
The name of the program used to generate this invoice, e.g. "Elite".
Sub Structure - Contact Structure (See @CONTACT_INFO Segment below.)
The name of the program used to generate this invoice, e.g. "Elite".
VRP: In XML 2000, the billing contact information is given as fields rather than a sub structure.
app_version firm_URL
app_version firm_URL
The version of the source_app, e.g. "9.3b".
The law firm's website URL. Should always begin "http://www. …"
The version of the source_app, e.g. "9.3b".
The law firm's website URL. Should always begin "http://www. …"
file_item_nbr @extend_header
file_item_nbr @extend_header
Element Number - The item count of this data element in the invoice file submission.
Used for client and/or firm specific extensions to the @FIRM Segment (See @EXTEND_HEADER Segment below.)
Element Number - The item count of this data element in the invoice file submission.
Used for client and/or firm specific extensions to the @FIRM Segment (See @EXTEND_HEADER Segment below.)
Version Ver 2.1 Field address_1 address_2
DescriptionVersion Ver 2.0
Field address_1 address_2
DescriptionVersion XML 2000
Field address_1 address_2Description
Version LEDES98BI - Law firm AddressField LAW_FIRM_ADDRESS_1 LAW_FIRM_ADDRESS_2
DescriptionVersion LEDES98BI - Client Address
Field CLIENT_ADDRESS_1 CLIENT_ADDRESS_2
DescriptionVersion LEDES98B
FieldDescription
Address 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. For example, in the law firm segment, there can be a sub structure for @lf_remit_address and @lf_address or @cl_address in client segment. The header of the strucutre should be used to distinguish between the various address information.
The street address of parent. Optional second street address of parent.
The street address of parent. Optional second street address of parent.
The street address of the law firm. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
Optional second street address of the law firm. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
The street address of the client. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
Optional second street address of the client. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
address_3 city state_province
address_3 city state_province
address_3 city state_province
LAW_FIRM_CITY LAW_FIRM_STATEorREGION
CLIENT_CITY CLIENT_STATEorREGION
Address 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. For example, in the law firm segment, there can be a sub structure for @lf_remit_address and @lf_address or @cl_address in client segment. The header of the strucutre should be used to
Optional third street address of parent.
The city of parent. The state or province of parent. Required except in countries without an equivalent address component. Use accepted abbreviations mandated by the parent country's postal service.
Optional third street address of parent.
The city of parent. The state or province of parent. Required except in countries without an equivalent address component. Use accepted abbreviations mandated by the parent country's postal service.
The city of the law firm.Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
The state or region of the law firm. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
The city of the client. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
The state or region of the client. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
zip_postal_code country phone
zip_postal_code country phone
zip_postal_code country phone
LAW_FIRM_POSTCODE LAW_FIRM_COUNTRY
CLIENT_POSTCODE CLIENT_COUNTRY
The postal code of parent. Required except in countries without an equivalent address component.
The country of parent. Use ISO 3166 country code set forth by International Standards Organization (www.iso.org.)
The phone number parent.
The postal code of parent. Required except in countries without an equivalent address component.
The country of parent. Use ISO 3166 country code set forth by International Standards Organization (www.iso.org.)
The phone number parent.
The postal code of the law firm. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
The country code of the law firm. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
The postal code of the client. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
The country code of the client. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
fax file_item_number
fax
fax
The fax number of parent. Element Number - The item count of this data element in the invoice file submission.
The fax number of parent.
Version Ver 2.1
Field contact_lname contact_fname contact_id
DescriptionVersion Ver 2.0
Field contact_lname contact_fname contact_id
DescriptionVersion XML 2000 - Billing Contact (Firm Segment)
Field lf_billing_contact_lname lf_billing_contact_fname lf_billing_contact_idDescription
Version XML 2000 - Client Contact (Client Segment)Field cl_contact_lname cl_contact_fname
DescriptionVersion XML 2000 - LF Managing Contact (matter segment)
Field lf_contact_idDescription
Version XML 2000 -Client contact (matter segment)Field cl_contact_lname cl_contact_fname cl_contact_id
DescriptionVersion LEDES98BI
FieldDescription
Version LEDES98BField
Description
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. For example @lf_contact in Firm segment, cl_contact in matter segment etc.
The last name of the contact.
The first name of the contact.
An "id" associated with contact.
The last name of the contact.
The first name of the contact.
An "id" associated with contact.
lf_managing_contact_lname
lf_managing_contact_fname
contact_phone contact_fax contact_email file_item_number
contact_phone contact_fax contact_email
lf_billing_contact_fax lf_billing_contact_email
cl_email
lf_contact_phone lf_contact_email
cl_contact_phone cl_contact_email
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. For example @lf_contact in Firm segment, cl_contact in matter segment etc.
The phone number of the contact.
The fax number of the contact.
The email address of the contact.
Element Number - The item count of this data element in the invoice file submission.
The phone number of the contact.
The fax number of the contact.
The email address of the contact.
lf_billing_contact_phone
Version Ver 2.1 Field vendor app
DescriptionVersion Ver 2.0
Field vendor app
DescriptionVersion XML 2000
Field vendor appDescription
Version LEDES98BIField
DescriptionVersion LEDES98B
FieldDescription
If an @EXTEND_HEADER is used, the fields herein appear as attributes of the @EXTEND_HEADER. For this reason, the @EXTEND_HEADER segment does not include a file_item_number. The @EXTEND_HEADER segment allows for the optional inclusion of fields into any segment needing custom extensions. The @EXTEND_HEADER segment also allows applications which do not support custom extensions to still read and use a LEDES XML data document which contains extensions.
Used to name a vendor the data is associated with, e.g. "E-Billing Vendor" or "Realestate.com"
Used to name an application the data is associated with, e.g. "E-Billing" or "Realestate Online"
Used to name a vendor the data is associated with, e.g. "Ebilling Vendor" or "Realestate.com"
Used to name an application the data is associated with, e.g. "Ebilling" or "Realestate Online"
sequence date @extend_data
sequence date @extend_data
sequence date @extend_data
If an @EXTEND_HEADER is used, the fields herein appear as attributes of the @EXTEND_HEADER. For this reason, the @EXTEND_HEADER segment does
The @EXTEND_HEADER segment allows for the optional inclusion of fields into any segment needing custom extensions. The @EXTEND_HEADER segment also allows applications which do not support custom extensions to still read and use a LEDES XML data document which contains extensions.
Used to define a sequence of use. Used to define a date associated with the overall extend_header and associated extend_data elements in this segment.
Used to provide the name value pairs. (See @EXTEND_DATA Segment below)
Used to define a sequence of use.
Used to define a date associated with the overall extend_header and associated extend_data elements in this segment.
Used to provide the name value pairs. (See @EXTEND_DATA Segment below)
Version Ver 2.1 Field ext_name ext_value
DescriptionVersion Ver 2.0
Field ext_name ext_value
DescriptionVersion XML 2000
Field ext_name ext_valueDescription
Version LEDES98BI
Version LEDES98B
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. (VRP: Not sure about this sentence. A file item number is given in element definition)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.
Used to provide the name of the variable.
Used to provide the value of the variable.
Used to provide the name of the variable.
Used to provide the value of the variable.
file_item_nbr
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. (VRP: Not sure about
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
The item count of this data element in the invoice file submission.
Version Ver 2.1
Fieldtx_id tax_id_number
Description
Version Ver 2.0
Fieldtx_id tax_id_number
DescriptionVersion XML 2000Field
DescriptionVersion LEDES98BI Field
DescriptionVersion LEDES98BFieldDescription
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.
A unique identifier associated with the tax/rate/jurisdiction, assigned by the law firm.
Tax ID Number for law firm or vendor associated with specific tax.
A unique identifier associated with the tax/rate/jurisdiction, assigned by the law firm.
Tax ID Number for law firm or vendor associated with specific tax.
tax_type tax_rate_percent taxing_jurisdiction_country
tax_type tax_rate_percent
Tax_rate
LINE_ITEM_TAX_TYPE LINE_ITEM_TAX_RATE
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
The @EXTEND_HEADER option was purposely omitted from this segment.
Type of tax. Based on a value specified by the client. Examples in US: "Federal", "State", "Local". Examples in Canada: "GST", "HST", "PST", "TVQ".
Percentage tax rate against charge, i.e. 7.25% tax_rate_percent would be represented as "0.0725".
The country of the taxing jurisdiction. Use ISO 3166 country code set forth by International Standards Organization (www.iso.org.)
Type of tax. Based on a value specified by the client. Examples in US: "Federal", "State", "Local". Examples in Canada: "GST", "HST", "PST", "TVQ".
Percentage tax rate against charge, i.e. 7.25% tax_rate_percent would be represented as "0.0725".
VRP: Distinct Tax Rates from line items can be placed here.
Tax type indicator (e.g. VAT, GST, PST, Other). Information purposes only and not used in the invoice calculation. A null value ("") would be acceptable. - VRP: Take unique tax types grouped on rates against them used in the file
Percentage tax rate against charge. A decimal number between 0 and 1 indicating the rate of taxation on the line item. A null ("") or 0 would indicate no taxes apply to the line item. - VRP: Take unique rates for each of the tax types
taxing_jurisdiction_locality tax_on_tax
taxing_jurisdiction
The locality of the taxing jurisdiction. Use accepted abbreviations for state or province mandated by the country's postal service. For Canadian PST, taxing_jurisdiction_locality for Ontario would be "ON"; for Local tax in New York City, taxing_jurisdiction_locality would be "New York, NY"; for state tax in Georgia (USA), taxing_jurisdiction_locality would be "GA"; for VAT tax in France, taxing_jurisdiction_locality would be null.
Required "Y" or "N". "Tax-on-Tax" is a situation where one or more taxes in a tax jurisdiction are based on the sum of the corresponding invoice line item totals AND any other tax amount previously applied to those line item totals. For example, in Canada both Quebec and Prince Edward Island have specific taxes calculated on the sum of the line items plus the federal tax paid on those line items.
Name of the taxing jurisdiction. Use accepted abbreviations for state or province mandated by the country's postal service; do not abbreviate country names. For Canadian PST, taxing_jurisdiction for Ontario would be "ON"; for Local tax in New York City, taxing_jurisdiction would be "New York"; for state tax in Georgia, taxing_jurisdiction would be "GA"; for VAT tax in France, taxing_jurisdiction would be "France".
tax_on_tax_id
In a "tax-on-tax" situation (described above), the tax_on_tax_id is the tx_id of the tax that should be included in the tax calculation for the current tx_id. For example, in Canada the TVQ tax includes not only the line items taxed, but also the GST tax for these line items. The proper response to this tax_on_tax_id field would be the tx_id for the GST tax.Although we are currently not aware of any such situation, it may be the case in a jurisdiction that there is a tax-on-tax-on-tax situation. It is anticipated that this field would hierarchically grow as necessary. Using the example in the previous paragraph, say that tax3 includes TVQ and GST taxes. Since the TVQ tax already shows the hierarchical relationship with GST in the tax_on_tax_id field, tax 3 would list the tx_id for TVQ in this tax_on_tax_id field.
increase_decrease
Identifies whether the tax results in increasing or decreasing the matter/invoice. Almost all taxes are "Increase", the exception being Withholding Tax.
Withholding Tax is tax that is paid by the client to the government as opposed to being collected by the firm and paid to the government.
While taxes are itemized against individual line items on the bill, Withholding Taxes are calculated against total of fees and total of disbursements charged pre-tax and post split on the invoice. Individual line items will not associate with the @TAX.tx_id for withholding taxes.
There can be more than one Withholding Tax on an invoice, but each Withholding Tax would have a different tax rate percentage.
The total of the Withholding Tax(es) do not have to equal to the other taxes on the invoice; they could be less than or greater than the total of the other taxes charged on the invoice.
file_item_nbr
file_item_nbr
The item count of this data element in the invoice file submission.
The item count of this data element in the invoice file submission.
Information on the Client(s) for whom bills are submitted by the Firm. There will be 1 or more @CLIENT segments per @FIRM segment.
Version Ver 2.1 Field cl_id
Description
The law firm assigned client code.
Version Ver 2.0 Field cl_id
DescriptionVersion XML 2000Field cl_id
DescriptionVersion LEDES98BI Field CLIENT_ID
DescriptionVersion LEDES98BField CLIENT_ID
The law firm assigned client code.
The law firm assigned client code. A null value ("") would be an error. For each LAW_FIRM_MATTER_ID, only the first CLIENT_ID appearing for that LAW_FIRM_MATTER_ID is valid (i.e., all others after the first can be disregarded). LAW_FIRM_ID and CLIENT_ID are included as fields in order to enable automatic bill routing, should that be desired.
Description
The law firm assigned client code. A null value ("") would be an error. For each LAW_FIRM_MATTER_ID, only the first CLIENT_ID appearing for that LAW_FIRM_MATTER_ID is valid (i.e., all others after the first can be disregarded).
Information on the Client(s) for whom bills are submitted by the Firm. There will be 1 or more @CLIENT segments per @FIRM segment.
Ver 2.1 cl_lf_id cl_name
Ver 2.0 cl_lf_id cl_name
XML 2000cl_lf_id cl_name
LEDES98BI CLIENT_NAME
LEDES98B
A vendor ID that uniquely identifies the law firm, as specified by the client. Could be the law firm's tax id number or other value used by the client to uniquely identify the law firm.
Values required in this field may vary from client to client, but within a client's e-billing implementation only one such unique ID is allowed per law firm. Some client AP systems maintain multiple vendor IDs for a law firm that could be, for example, location dependant. It is not intended that multiple lf_vendor_ids for the same law firm would be supported by this field as they would be impossible to program into the law firm's time and billing software. Clients must choose only one unique identifier per law firm to be used in this field.
The name of the client as required by the client in the electronic submission. Used as a key by the receiving system.
A VendorID that uniquely identifies the law firm, as specified by the client. Could be the law firm's tax id number or other value used by the client to uniquely identify the law firm.
Values required in this field may vary from client to client, but within a client's e-billing implementation only one such unique ID is allowed per law firm. Some client AP systems maintain multiple vendor IDs for a law firm that could be, for example, location dependant. It is not intended that multiple lf_vendor_ids for the same law firm would be supported by this field as they would be impossible to program into the law firm's time and billing software. Clients must choose only one unique identifier per law firm to be used in this field.
The name of the client as required by the client in the electronic submission. Used as the key by the receiving system.
Client name. Given these display fields can be supplemented by intermediate vendor applications, a null value ("") would be acceptable.
@cl_address @client_contact cl_tax_id
@cl_address @client_contact cl_tax_id
@cl_address @client_contact cl_tax_id
@cl_address CLIENT_TAX_ID
The client's tax id number to which law firm taxes are charged.
The client's tax id number to which law firm taxes are charged.
VRP: In XML 2000, the client contact information is given as fields rather than a sub structure.
VRP: Should be derived as part of address segment. More info on fields in Address segment
The client’s identification for tax purposes. In the UK this would be the VAT number.
file_item_nbr @extend_header
file_item_nbr @extend_header
The item count of this data element in the invoice file submission.
The item count of this data element in the invoice file submission.
Used for client and/or firm specific extensions to the @CLIENT Segment (See @EXTEND_HEADER Segment below.)
Information on the Invoices submitted by the Firm for the Client. There will be 1 or more @INVOICE segments per @CLIENT segment.
Version Ver 2.1 Field inv_id inv_date
Description
Version Ver 2.0 Field inv_id inv_date
Description
Version XML 2000
Field inv_id inv_date
DescriptionVersion LEDES98BI
Field INVOICE_NUMBER INVOICE_DATE
Description
Version 1998B
Field INVOICE_NUMBER INVOICE_DATE
Description
The law firm assigned invoice number or code. Multiple inv_id's can be billed in the same LEDES e-billing file.
The invoice date.
The law firm assigned invoice number or code. Multiple inv_id's can be billed in the same LEDES e-billing file.
The invoice date.
The alphanumeric, law firm assigned invoice number or code. Multiple INVOICE_NUMBERs can be billed in the same LEDES file. A null value ("") would be an error.
The invoice date. A null value ("") would be an error.
The alphanumeric, law firm assigned invoice number or code. Multiple INVOICE_NUMBERs can be billed in the same LEDES file. A null value ("") would be an error.
The invoice date. A null value ("") would be an error.
Information on the Invoices submitted by the Firm for the Client. There will be 1 or more @INVOICE segments per @CLIENT segment.
inv_due_date inv_currency
inv_due_date inv_currency
inv_due_date inv_currency
INVOICE_CURRENCY
The law firm assigned date by which the invoice is due to be paid by the client.
The currency for this invoice. Use ISO 4217 currency codes set forth by International Standards Organization (www.iso.org.).
The law firm assigned date by which the invoice is due to be paid by the client.
The currency for this invoice. Use alphabetic codes set forth by International Standards Organization (www.iso.org.).
The submission currency by the law firm or vendor denoted by the 3 character ISO currency code (ISO 4217). The payment currency by the client is not driven from this field. A null value (“”) would be an error.
inv_other_iso inv_start_date
The starting date for the billing period.
inv_start_date
inv_start_date
INVOICE_TAX_CURRENCY BILLING_START_DATE
BILLING_START_DATE
For mixed currency situations only where it is mandated that the total tax must also be reported in a different currency ISO. This represents the ISO other than the currency used for this invoice and relates to the information provided in the fields @INVOICE.inv_total_tax_other_iso and @INVOICE.inv_total_net_due_other_iso.
Use ISO 4217 currency codes set forth by International Standards Organization (www.iso.org.)
The starting date for the billing period.
The currency of INVOICE_REPORTED_TAX_TOTAL denoted by the 3 character ISO currency code (ISO 4217). A null value (“”) would mean that the total tax on an invoice is in the same currency as the INVOICE_CURRENCY.
The starting date for the billing period. A null value ("") would be an error.
The starting date for the billing period. A null value ("") would be an error.
inv_end_date inv_desc
The ending date for the billing period.
inv_end_date inv_desc
inv_end_date inv_desc
BILLING_END_DATE INVOICE_DESCRIPTION
BILLING_END_DATE INVOICE_DESCRIPTION
A descriptive summary of work performed.
It is expected that this field will be picked up by re receiving system and displayed to bill reviewers.
The ending date for the billing period. A descriptive summary of work performed.
The ending date for the billing period. A null value ("") would be an error.
A descriptive summary of work performed which is charged on this invoice during the applicable billing period. Limited to 15KB of text.
The ending date for the billing period. A null value ("") would be an error.
A descriptive summary of work performed which is charged on this invoice during the applicable billing period. Limited to 15KB of text.
tax_invoice_cl_name
The name of the party paying VAT on the invoice.
The legal name of the party paying VAT on the invoice may be different from the value required by the receiving system in the @CLIENT.cl_name field. In some jurisdictions it may be required by law to provide this information.
inv_payment_terms
inv_payment_terms
inv_payment_terms
Optional. Can not be used if any tax is charged against any matter/invoice that is part of this inv_id.Discount applied to the invoice if it is paid within the stated number of days. "10/30" would indicate that the firm will accept a 10% discount of inv_total_net_due if paid within 30 days of the invoice_date. CAN NOT be used if any tax is charged against any matter/invoice that is part of this inv_id. Law firm can not apply this reduction to the invoice because it is dependant on the payment turnaround by the client; represents an additional discount that must be applied by the client's accounts payable system or third party e-billing vendor if the payment terms are met.
Optional. Can not be used if any tax is charged against any matter/invoice that is part of this inv_id.Discount applied to the invoice if it is paid within the stated number of days. "10/30" would indicate that the firm will accept a 10% discount of inv_total_net_due if paid within 30 days of the invoice_date. CAN NOT be used if any tax is charged against any matter/invoice that is part of this inv_id. Law firm can not apply this reduction to the invoice because it is dependant on the payment turnaround by the client; represents an additional discount that must be applied by the client's accounts payable system or third party e-billing vendor if the payment terms are met.
tax_invoice_cl_address tax_invoice_cl_id
Address Structure for the @INVOICE.tax_invoice_cl_name. (See @ADDRESS_INFO Segment).
The tax id number for the @INVOICE.tax_invoice_cl_name.
bill_to_cl_name @bill_to_cl_address
The name of the party being billed on the invoice.
The legal name of the party being billed may be different from the @CLIENT.cl_name, and the @INVOICE.tax_invoice_cl_name. In some jurisdictions it may be required by law to provide this information
Conditional Required if @INVOICE.bill_to_cl_name is not the same as @CLIENT.cl_name Address Structure (See @ADDRESS_INFO Segment)
bill_to_cl_id payable_by_cl_name
The tax id number for the @INVOICE.bill_to_cl_name.
The name of the party paying the invoice. May not be the same party that is paying VAT on the invoice.
The legal name of the party paying the invoice may also be different from the @CLIENT.cl_name, the @INVOICE tax_invoice_cl_name and the @INVOICE.bill_to_cl_name. In some jurisdictions it may be required by law to provide this information.
@payable_by _cl_address payable_by _cl_id
Conditional Required if @INVOICE.payable_by_cl_name is not the same as @CLIENT.cl_name. Address Structure (See @ADDRESS_INFO Segment)
The tax id number for the @INVOICE.payable_by_cl_name.
tax_point_date
The tax point is generally the invoice date. In instances where the tax point date is different from the invoice date, the tax point date indicates the financial period in which the tax applies.
tax_invoice
In the European Union (and possibly in other areas of the world) it is required that an invoice contain the words, "This is a Tax Invoice" or "This is not a Tax Invoice".
It would be possible for the law firm to submit an invoice containing all line items details and designated "This is a Tax Invoice" in this field, and for the receiving system to display a view of the invoice to the Client and Law Firm that satisfies the requirements for the Tax Invoice required by law in many countries. In this situation, the law firm may not need to send a separate tax invoice to the Client.
credit_note
In the European Union (and possibly in other areas of the world) it is required to indicate whether an instrument is a Credit Note if it corrects a Tax Invoice.
inv_reference
If the firm is submitting a Credit Note (an instrument required by statute or regulation that corrects a previously issued Tax Invoice -- see @INVOICE.tax_invoice for more discussion) or is submitting an invoice that corrects an invoice previously rejected by a bill reviewer, enter the inv_id of the original invoice being corrected. As described above, law firms are required by regulation to supply the Tax Invoice number being corrected. It is therefore expected that the receiving system will store this information and display it to bill reviewers. In addition, in situations where the submission corrects an invoice rejected by a bill reviewer, this field can be used by the receiving system to electronically verify the correction submitted so that these submissions could be approved electronically instead of being routed to a bill reviewer for approval.
inv_payment_terms
Discount applied to the invoice if it is paid within the stated number of days. "10.00/30" would indicate that the firm will accept a 10% discount of inv_total_net_due if paid within 30 days of the invoice_date. CAN NOT be used if any tax is charged against any matter/invoice that is part of this inv_id because there may be a legal requirement that the tax amount charged should not be modified. Law firm can not apply this reduction to the invoice because it is dependant on the payment turnaround by the client; represents an additional discount that must be applied by the client's accounts payable system or third party e-billing vendor if the payment terms are met.
inv_total_tax
inv_total_tax
INVOICE_TAX_TOTAL
The sum of all @MATTER.matter_tax_on_fees + @MATTER.matter_tax_on_exp for this inv_id.
This figure includes Withholding Taxes.
The sum of all @MATTER.matter_tax_on_fees + @MATTER.matter_tax_on_exp for this inv_id.
The sum of all LINE_ITEM_TAX_TOTAL items in this invoice. A null value would denote a tax exempt invoice. The client may request that the tax amount be only the reimbursable tax amount, such as VAT, which they often must track separately for accounting purposes. The receiving application is encouraged to allow for a reasonable variance to account for rounding errors when the sending application calculated the INVOICE_TAX_TOTAL.
inv_total_tax_other_iso inv_total_net_due
inv_total_tax_other_iso inv_total_net_due
inv_total_net_due
INVOICE_REPORTED_TAX_TOTAL INVOICE_TOTAL
For mixed currency situations only where it is mandated that the total tax must also be reported in a different currency ISO. The sum of all @MATTER.matter_tax_on_fees + @MATTER.matter_tax_on_exp for this inv_id in the ISO required by law as identified in @INVOICE.inv_total_net_due_other_iso.
This figure includes Withholding Taxes
The sum of all @MATTER.matter_total_due for this inv_id.
For mixed currency situations only where it is mandated that the total tax must also be reported in a different currency ISO. The sum of all @MATTER.matter_tax_on_fees + @MATTER.matter_tax_on_exp for this inv_id in the ISO required by law.
The sum of all @MATTER.matter_total_due for this inv_id.
The amount of tax in the national currency as reported to the tax authorities. Information purposes only and not used in the invoice calculation. A null value ("") would be acceptable
The sum of all LINE_ITEM_TOTAL values in this invoice. A null value ("") would be an error.
INVOICE_TOTAL
The sum of all LINE_ITEM_TOTAL values in this invoice. A null value ("") would be an error.
inv_total_net_due_other_iso inv_image_file_name
inv_total_net_due_other_iso
For mixed currency situations only where it is mandated that the total invoice must also be reported in a different currency ISO. The sum of all @MATTER.matter_total_due for this inv_id in the ISO identified in @INVOICE.inv_other_iso.
It may be that there is a statutory, regulatory or client-mandated requirement to also provide an electronic image (.pdf, Word, etc.) of this invoice or of receipts for expenses included in this invoice. If this is the case, use this field to indicate the name of the file with this invoice image so that it can be located by the client.
For mixed currency situations only where it is mandated that the total invoice must also be reported in a different currency ISO. The sum of all @MATTER.matter_total_due for this inv_id.
file_item_nbr @extend_header
file_item_nbr @extend_header
The item count of this data element in the invoice file submission.
The item count of this data element in the invoice file submission.
Used for client and/or firm specific extensions to the @INVOICE Segment (See @EXTEND_HEADER Segment below.)
INVOICE_NET_TOTAL
The sum of all LINE_ITEM_TOTAL values in this invoice minus the INVOICE_TAX_TOTAL. A null value (“”) would be an error. The client may request that the tax amount be only the reimbursable tax amount, such as VAT, which they often must track separately for accounting purposes.
Version Ver 2.1 Field regulation_heading regulatory_statement
DescriptionVersion Ver 2.0 FieldDescriptionVersion XML 2000
FieldDescriptionVersion LEDES98BI
FieldDescriptionVersion 1998B
FieldDescription
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 citation of the statute or regulation associated with the information provided in the next field. E-Billing vendors and clients are requested to provide instruction on how data is to be recorded in this field.
The language required by statute or regulation to be provided by a law firm on an electronic invoice.
file_item_nbr
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
In that this information is required by statute or regulation to be provided, all information provided in this segment should be captured
There will be 0 or more @REGULATORY_STATEMENT segments per @INVOICE segment.
The item count of this data element in the invoice file submission.
Summary totals for each matter billed in the invoice. There will be 1 or more @MATTER segments per @INVOICE segment.
Version Ver 2.1
Fieldcl_matter_id lf_matter_id
DescriptionVersion Ver 2.0Field cl_matter_id lf_matter_id
DescriptionVersion XML 2000
Fieldcl_matter_id lf_matter_id
DescriptionVersion LEDES98BI Field CLIENT_MATTER_ID LAW_FIRM_MATTER_ID
DescriptionVersion LEDES98BField CLIENT_MATTER_ID LAW_FIRM_MATTER_ID
The client assigned matter id or case reference number. Multiple cl_matter_id's can be billed in the same invoice.
The law firm assigned matter id or case reference number. Multiple lf_matter_id's can be billed in the same invoice.
The client assigned matter id or case reference number. Multiple cl_matter_id's can be billed in the same invoice.
The law firm assigned matter id or case reference number. Multiple lf_matter_id's can be billed in the same invoice.
The client assigned matter code. Multiple CLIENT_MATTER_IDs can be billed in the same invoice. A null value ("") would be an error, unless the client does not assign matter identifiers.
The law firm assigned matter code. Multiple LAW_FIRM_MATTER_IDs can be billed in the same invoice. A null value ("") would be an error.
Description
The client assigned matter code. Multiple CLIENT_MATTER_IDs can be billed in the same invoice. A null value ("") would be an error, unless the client does not assign matter identifiers.
The law firm assigned matter code. Multiple LAW_FIRM_MATTER_IDs can be billed in the same invoice. A null value ("") would be an error.
Summary totals for each matter billed in the invoice. There will be 1 or more @MATTER segments per @INVOICE segment.
matter_name matter_desc po_number
matter_name matter_desc
matter_name matter_desc
MATTER_NAME PO_NUMBER
The descriptive name of the matter, e.g. "Jones v. Davidson", "Jamison Contract Proposal".
Description of work performed this period
The alphanumeric, client-assigned purchase order number or code.
The descriptive name of the matter, e.g. "Jones v. Davidson", "Jamison Contract Proposal".
Description of work performed this period.
The name of the matter to which this invoice relates. THIS FIELD IS PROVIDED FOR INFORMATION ONLY AND MUST NOT BE USED BY THE RECEIVING APPLICATION AS A PRIMARY KEY FOR A MATTER.
account_type @lf_managing_contact @lf_contact
@lf_managing_contact @lf_contact
@lf_managing_contact
ACCOUNT_TYPE
An identifier indicating whether an invoice is "own account" ("O"), or "third party" ("T").
VRP: In XML 2000, the managing contact information is given as fields rather than a sub structure.
An identifier indicating whether an invoice is “own account” (“O”), or “third party” (“T”).
@cl_contact
@cl_contact
@cl_contact
VRP: In XML 2000, the managing contact information is given as fields rather than a sub structure.
matter_billing_type
matter_billing_type
matter_billing_type
Code indicating how the matter is billed. Valid values and their descriptions are: CT - Contingency Fee - When the law firm's fee is based on a percentage of the amount recovered by the law firm client in a plaintiff's action. FF - Flat Fee - When the firm is paid a flat fee on the matter only.GW - Goodwill Work - Where the firm has performed services for free for the client on a matter and provides information on the work performed in a separate $0 invoice to the client.MPF - Multi-Payor Fees - When the cost of services provided on a matter is split by multiple clients of the firm regardless of any other matter_billing_type that may apply. TM - Time & Materials - When the bill is based on hours worked, or where there may be a combination of hourly billing plus a flat fee by task arrangement.A null value defaults to "TM".
Code indicating how the matter is billed. Valid values and their descriptions are: "TM" (time & materials), "FF" (flat fee), "CT" (contingency) "MPF" (multi-payor fees). A null value defaults to "TM".
matter_final_bill matter_total_detail_fees matter_total_detail_exp
matter_final_bill matter_total_detail_fees matter_total_detail_exp
matter_final_bill matter_total_detail_fees matter_total_detail_exp
Field used to specify whether this is the final bill for the matter_id.
Sum of all @FEE.total_amounts billed to this matter/invoice.
Sum of all @EXPENSE.total_amounts billed to this matter/invoice.
Field used to specify whether this is the final bill for the matter_id.
Sum of all @FEE.total_amounts billed to this matter/invoice.
Sum of all @EXPENSE.total_amounts billed to this matter/invoice.
matter_disc_credit_fees matter_disc_credit_exp
matter_disc_credit_fees matter_disc_credit_exp
matter_adj_on_fees matter_adj_on_exp
Sum of all @MATTER_DISC_CRED.disc_credit_amount where @MATTER_DISC_CRED.disc_credit_type equals "FEE" and (@MATTER_DISC_CRED.disc_cred is not "MISF", "MIDB" or "MIFA"). Excludes discounts or credits applied to fee line items as these are already part of matter_total_detail_fees.
Sum of all @MATTER_DISC_CRED.disc_credit_amount where @MATTER_DISC_CRED.disc_credit_type equals "EXP" and (@MATTER_DISC_CRED.disc_cred is not "MISF", "MIDB" or "MIFA"). Excludes discounts or credits applied to expense line items as these are already part of matter_total_detail_exp.
Sum of all @MATTER_DISC_CRED.disc_credit_amount where @MATTER_DISC_CRED.disc_credit_type equals "FEE" and @MATTER_DISC_CRED.disc_cred is not "MISF".
Sum of all @MATTER_DISC_CRED.disc_credit_amount where @MATTER_DISC_CRED.disc_credit_type equals "EXP" and @MATTER_DISC_CRED.disc_cred is not "MISF".
matter_disc_cred_total matter_perc_shar_fees matter_perc_shar_exp
matter_disc_cred_total matter_perc_shar_fees matter_perc_shar_exp
matter_perc_shar_fees matter_perc_shar_exp
matter_disc_credit_total = matter_disc_credit_fees + matter_disc_credit_exp. Represents the total of all discounts or credits applied at the matter/invoice level, exclusive of reductions that are the result of fees shared with another client of the law firm.
Excludes discounts or credits applied to fee or expense line items.
@MATTER_DISC_CRED.disc_cred_percent where @MATTER_DISC_CRED.disc_credit_type equals "Percent" and @MATTER_DISC_CRED.disc_credit_category equals "Fee" and @MATTER_DISC_CRED.disc_cred equals "MISF"
@MATTER_DISC_CRED.disc_cred_percent where @MATTER_DISC_CRED.disc_credit_type equals "Percent" and @MATTER_DISC_CRED.disc_credit_category equals "Exp" and @MATTER_DISC_CRED.disc_cred equals "MISF"
matter_disc_credit_total = matter_disc_credit_fees + matter_disc_credit_exp. Represents the total of all discounts or credits applied to the matter/invoice, exclusive of reductions that are the result of fees shared with another client of the law firm.
@MATTER_DISC_CRED.disc_cred_percent where @MATTER_DISC_CRED.disc_credit_type equals "Percent" and @MATTER_DISC_CRED.disc_credit_category equals "Fee" and @MATTER_DISC_CRED.disc_cred = "MISF"
@MATTER_DISC_CRED.disc_cred_percent where @MATTER_DISC_CRED.disc_credit_type equals "Percent" and @MATTER_DISC_CRED.disc_credit_category equals "Exp" and @MATTER_DISC_CRED.disc_cred = "MISF"
matter_disc_bill_pct_fees matter_disc_bill_pct_exp matter_tax_on_fees
matter_tax_on_fees
matter_tax_on_fees
@MATTER_DISC_CRED.disc_cred_percent where @MATTER_DISC_CRED.disc_credit_type equals "Percent" and @MATTER_DISC_CRED.disc_credit_category equals "Fee" and @MATTER_DISC_CRED.disc_cred equals "MIDB"
@MATTER_DISC_CRED.disc_cred_percent_exp where @MATTER_DISC_CRED.disc_credit_type equals "Percent" and @MATTER_DISC_CRED.disc_credit_category equals "Exp" and @MATTER_DISC_CRED.disc_cred equals "MIDB"
Sum of all @TAX_SUMMARY.total_tax_on_fees for matter/invoice.
This figure includes Withholding Taxes.
Sum of all @TAX_SUMMARY.total_tax_on_fees for matter/invoice.
matter_tax_on_exp matter_net_fees
matter_tax_on_exp matter_net_fees
matter_tax_on_exp matter_net_fees
Sum of all @TAX_SUMMARY.total_tax_on_expense for matter/invoice.
This figure includes Withholding Taxes.
Using the Math Statement below on line 241: The total for pre-split non-taxable fee items on the bill + The total for pre-split Tax1 fee items on the bill + ... repeated for each pre-split tax fee items on the bill + The total for post-split non-taxable fee items on the bill + The total for post-split Tax1 fee items on the bill + ... repeated for each post-split tax fee items on the bill tax_total_detail_fees
Sum of all @TAX_SUMMARY.total_tax_on_expense for matter/invoice.
matter_net_fees = (matter_total_detail_fees + matter_disc_credit_fees) * matter_perc_shar_fees + matter_tax_on_fees
matter_net_exp matter_funds_applied
matter_net_exp
matter_net_exp
Using the Math Statement below on line 241: The total for pre-split non-taxable expense items on the bill + The total for pre-split Tax1 expense items on the bill + ... repeated for each pre-split tax expense items on the bill + The total for post-split non-taxable expense items on the bill + The total for post-split Tax1 expense items on the bill + ... repeated for each post-split tax expense items on the bill tax_total_detail_exp
Sum of all @MATTER_DISC_CRED.disc_cred_amount where disc_cred equals "MIFA"
matter_net_exp = (matter_total_detail_exp + matter_disc_credit_exp) * matter_perc_shar_exp + matter_tax_on_exp)
matter_total_due associated_line_items file_item_nbr
matter_total_due file_item_nbr
matter_total_due
matter_total_due = (matter_net_fees + matter_net_exp + matter_funds_applied)
Used to indicate whether there are ("Y") or are not ("N") any fee or children of fee line items, or expense or children of expense line items, associated with this invoice.
matter_total_due = (matter_net_fees + matter_net_exp)
@extend_header
@extend_header
cl_matter_var_1 cl_matter_var_2 eft_agreement_number
Version Ver 2.1 Field tx_id
Description
Version Ver 2.0Field tx_id
Description
Version XML 2000Field
DescriptionVersion LEDES98BI Field
DescriptionVersion LEDES98BFieldDescription
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.
A unique identifier associated with the tax/rate/jurisdiction. Refers to @TAX.tx_id value.
A unique identifier associated with the tax/rate/jurisdiction. Refers to @TAX.tx_id value. Could be many @TAX_SUMMARY.tx_id entries per matter/invoice.
Ver 2.1 tax_total_detail_fees total_tax_on_fees
Ver 2.0tax_total_detail_fees total_tax_on_fees
XML 2000Tax_on_charge
LEDES98BI LINE_ITEM_TAX_TOTAL
LEDES98B
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.
Total taxable amount of fees attributable to this tx_id.
Using the Math Statement below on line 241: The total for pre-split fee items for this tx_id+ The total for post-split fee items for this tx_id tax_total_detail_fees
Certain taxes are calculated not only on line items, but also include another tax for these line items -- a "tax on tax" situation. For example, in Canada both Quebec and Prince Edward Island have specific taxes calculated on the sum of the line items plus the federal tax paid on those line items. In situations like this, the tax_total_detail_fees figure should include the other tax attributable to the line items so that the math statement for total_tax_on_fees is correct.
Total of tax due on tax_total_detail_fees for this tx_id.
Total taxable amount of fees attributable to this tx_id.
tax_total_detail_fees = ((Sum of all @FEE.total_amounts where @TAX_ITEM_FEE.tx_id for the item equals this @TAX_SUMMARY.tx_id) + (sum of all @MATTER_DISC_CRED.disc_cred_amount where disc_cred_category = "Fee" and @TAX_MATTER_DISC_CRED.tx_id equals this @TAX_SUMMARY.tx_id)) * @MATTER.matter_perc_shar_fees on this matter/invoice.
Certain taxes are calculated not only on line items, but also include another tax for these line items -- a "tax on tax" situation. For example, in Canada both Quebec and Prince Edward Island have specific taxes calculated on the sum of the line items plus the federal tax paid on those line items. In situations like this, the tax_total_detail_fees figure stated should include the other tax attributable to the line items so that the math statement for total_tax_on_fees is correct.
Total of tax due on tax_total_detail_fees for this tx_id.
VRP:Summation of all Tax_on_charge for fee line items can be placed here
VRP: Summation of all Line_item_tax_total for fee line items can be placed here
tax_total_detail_expense total_tax_on_expense
tax_total_detail_expense total_tax_on_expense
Tax_on_charge
LINE_ITEM_TAX_TOTAL
Total taxable amount of expenses attributable to this tx_id.
Using the Math Statement below on line 241: The total for pre-split expense items for this tx_id+ The total for post-split expense items for this tx_id tax_total_detail_exp Certain taxes are calculated not only on line items, but also include another tax for these line items -- a "tax on tax" situation. For example, in Canada both Quebec and Prince Edward Island have specific taxes calculated on the sum of the line items plus the federal tax paid on those line items. In situations like this, the tax_total_detail_expense figure stated should include the other tax attributable to the line items so that the math statement for total_tax_on_expense is correct.
Total of tax due on tax_total_detail_expense for this tx_id.
Total taxable amount of expenses attributable to this tx_id.
tax_total_detail_expense = ((Sum of all @EXPENSE.total_amounts where @TAX_ITEM_FEE.tx_id for the item equals this @TAX_SUMMARY.tx_id) + (sum of all @MATTER_DISC_CRED.disc_cred_amount where disc_cred_category = "Exp" and @TAX_MATTER_DISC_CRED.tx_id equals this @TAX_SUMMARY.tx_id)) * @MATTER.matter_perc_shar_exp on this matter/invoice.
Certain taxes are calculated not only on line items, but also include another tax for these line items -- a "tax on tax" situation. For example, in Canada both Quebec and Prince Edward Island have specific taxes calculated on the sum of the line items plus the federal tax paid on those line items. In situations like this, the tax_total_detail_exp figure stated should include the other tax attributable to the line items so that the math statement for total_tax_on_fees is correct.
Total of tax due on tax_total_detail_expense for this tx_id.
VRP:Summation of all Tax_on_charge for expense line items can be placed here
VRP: Summation of all Line_item_tax_total for expense line items can be placed here
file_item_nbr
file_item_nbr
The item count of this data element in the invoice file submission.
The item count of this data element in the invoice file submission.
Version Field
Description
Version Field
DescriptionVersion Field
DescriptionVersion
All discounts, credits and Alternate Fee Agreement items applied at the Matter/Invoice level. There will be 0 or more @MATTER_DISC_CRED segments per @MATTER segment. It is possible for an invoice to be submitted that contains information in this segment of the file, but have no associated time and expense entries.
Field
DescriptionVersion
Field
Description
Ver 2.1 disc_cred
Ver 2.0disc_cred
XML 2000
LEDES98BI
All discounts, credits and Alternate Fee Agreement items applied at the Matter/Invoice level. There will be 0 or more @MATTER_DISC_CRED segments per @MATTER segment.
It is possible for an invoice to be submitted that contains information in this segment of the file, but have no associated time and expense entries.
The disc_credit field is used to track discounts and credits that the law firm may need to submit on the matter/invoice, and is structured in such a way that the segment supports many types of alternate fee arrangements.MIA - Matter/Invoice Adjustment - A flat adjustment (reduction or credit) applied at the matter/invoice level.MIB - Matter/Invoice Bonus - A bonus to be paid to the law firm on the matter/invoice.MICF - Matter/Invoice Contingency Fee - The contingency fee to be paid to the law firm on the matter/invoice. A contingency fee in this instance is when the law firm is paid based on a percentage of the amount awarded to the client, usually in representing a plaintiff.MICM - Matter/Invoice Credit Memo - A credit memo, as requested by the client on the matter/invoice. (In this case, it is the client who is processing the credit memo, not the law firm. The credit memo represents a miscellaneous credit to the firm.) Note that a credit memo, as used here, is not the same thing as a Credit Note as used in @INVOICE.credit_note.MIDB - Matter/Invoice Discounted Bill - Client receives a percentage discount assessed at the matter/invoice level. Should have a maximum of one for fee items and one for expense items. MIDHR - Matter/Invoice Discounted Hourly Rate - A discounted hourly rate applied at the matter/invoice level.MIFA - Matter/Invoice Funds Applied - Indicates the application of clients' funds or trust money to the total due on a matter/invoice.MIFF - Matter/Invoice is billed at a Flat Fee.MIR - Matter/Invoice Retainer - Used to bill a client for a retainer (an advance payment) to be paid to the law firm on the matter/invoice. This could occur multiple times over the life of a matter.MISF - Matter/Invoice Shared Fee - Fee is shared with another client and the client only pays a percentage of the bill, applied at the matter/invoice level. Should have a maximum of one for fee items and one for expense items.Other - Used to represent another type of AFA used by the client.
The disc_credit field is used to track discounts and credits that the law firm may need to submit on the matter/invoice, and is structured in such a way that the segment supports many types of alternate fee arrangements.
"MISF" (Matter/Invoice Shared Fee - fee is shared with another client and the client only pays a percentage of the bill, applied at the matter/invoice level), "MIDB" (Matter/Invoice Discounted Bill - client receives a percentage discount assessed at the matter/invoice level), "MIFF" (Matter/Invoice is billed at a Flat Fee), "MIA" (Matter/Invoice Adjustment - A flat adjustment (reduction or credit) applied at the matter/invoice level), "MIDHR" (Matter/Invoice Discounted Hourly Rate - a discounted hourly rate applied at the matter/invoice level), "MIR" (Matter/Invoice Retainer - a retainer to be paid to the law firm), "MICF" (Matter/Invoice Contingency Fee - the contingency fee to be paid to the law firm), "MIB" (Matter/Invoice Bonus - a bonus to be paid to the law firm), "MICM" (Matter/Invoice Credit Memo - a credit memo for a specific purpose, as requested by the client on the matter) or "Other"
LEDES98B
VRP: Since we have to deal with invoice level adjustments, a fixed value of MIA may be passed if 'IE' or 'IF' line items are present
VRP: Since we have to deal with invoice level adjustments, a fixed value of MIA may be passed if 'IE' or 'IF' line items are present
Ver 2.1 disc_cred_note disc_cred_type disc_cred_category
Ver 2.0disc_cred_note disc_cred_type disc_cred_category
XML 2000
LEDES98BI
All discounts, credits and Alternate Fee Agreement items applied at the Matter/Invoice level. There will be 0 or more @MATTER_DISC_CRED segments per @MATTER
It is possible for an invoice to be submitted that contains information in this segment of the file, but have no associated time and expense entries.
Identification of the discount or credit identified in the disc_credit field as "Other", using codes specified by the client.
Type of discount or credit, applied to the matter/invoice. Valid values are "Percent" and "Flat". If disc_cred equals "MIDHR" or "Other", disc_cred_type must be "Flat".
An indicator of whether the discount or credit applies to fees ("Fee") or expenses ("Exp").
Identification of the discount or credit identified in the disc_credit field as "Other", using codes specified by the client.
Type of discount or credit, applied to the matter/invoice. Valid values are "Percent" and "Flat"
An indicator of whether the discount or credit applies to fees ("Fee") or expenses ("Exp")
LINE_ITEM_DESCRIPTION EXP/FEE/INV_ADJ_TYPE
LEDES98BLINE_ITEM_DESCRIPTION EXP/FEE/INV_ADJ_TYPE
VRP: The discount line items' description may be passed here
An identifier indicating whether the line item is an expense ("E"), a fee ("F"), an invoice-level adjustment on fees ("IF"), or an invoice-level adjustment on expenses ("IE"). A null value ("") would be an error. VRP: Only when there are IE or IF, we need to load this segment
VRP: The discount line items' description may be passed here
An identifier indicating whether the line item is an expense ("E"), a fee ("F"), an invoice-level adjustment on fees ("IF"), or an invoice-level adjustment on expenses ("IE"). A null value ("") would be an error. VRP: Only when there are IE or IF, we need to load this segment
increase_decrease pre_post_split discount_percent
discount_percent
inv_generic_discount
Identifies whether the disc_cred results in increasing the cost of the matter/invoice (and is therefore a charge applied at the matter/invoice-level) or decreasing the cost of the matter/invoice (and is therefore a reduction applied at the matter/invoice level).
Identifies whether the disc_cred is applied before ("Pre-Split") or after ("Post-Split) the MISF and MIDB percentages are applied to the invoice. "NA" (Not applicable) should be used for splits indicated by disc_cred "MISF" and "MIDB".
A percentage number expressing the percent discount applied to this matter/invoice, i.e. "0.15" reflects a 15% discount to the matter/invoice. This value is always a reduction to the invoice.
A percentage number expressing the percent discount applied to this matter/invoice, i.e. "0.15" reflects a 15% discount to the matter/invoice. This value is always a reduction to the invoice.
VRP: From Invoice Segment. Generic discount % applied to invoice if any. We can pass a value if this field is non - zero
disc_cred_amount file_item_nbr extend_header
disc_cred_amount file_item_nbr @extend_header
The total amount discounted/credited against or additional charges incurred for this disc_cred. If @MATTER_DISC_CRED.increase_decrease equals "increase", then this value is a positive number; if @MATTER_DISC_CRED.increase_decrease equals "decrease", then this value is a negative number. I.e. "-150.0000" reflects a $150 decrease/reduction/write-down on the matter/invoice, "150.0000" reflects a $150 increase/charge/write-up on the matter/invoice.
The item count of this data element in the invoice file submission.
Used for client and/or firm specific extensions to the @MATTER_DISC_CRED Segment (See @EXTEND_HEADER Segment below.)
The total amount discounted or credited for this disc_cred. Discounts or reductions should be a negative number; credits should be a positive number. I.e. "-150.0000" reflects a $150 disc_cred, "150.0000" reflects a $150 credit.
The item count of this data element in the invoice file submission.
Used for client and/or firm specific extensions to the @MATTER_DISC_CRED Segment (See @EXTEND_HEADER Segment below.)
LINE_ITEM_TOTAL
LINE_ITEM_TOTAL
VRP: Incase the line item is 'IF' or 'IE', then the value must be passed over to this field.
VRP: Incase the line item is 'IF' or 'IE', then the value must be passed over to this field.
Version Field
Description
Version Field
Description
Version FieldDescriptionVersion Field
DescriptionVersion FieldDescription
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.
Ver 2.1 tx_id
Ver 2.0 tx_id
LEDES98BI
LEDES98BI
LEDES98B
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.
Taxes relevant to fee item. Refers to @TAX.tx_id value. Could be many @TAX_ITEM_FEE.tx_id entries per @MATTER_DISC_CRED.disc_cred item.
Taxes relevant to fee item. Refers to @TAX.tx_id value. Could be many @TAX_ITEM_FEE.tx_id entries per @MATTER_DISC_CRED.disc_cred item.Zero or more segments per @MATTER_DISC_CRED item. One segment for each type of tax on the @MATTER_DISC_CRED item. If the item is not taxed, no @TAX_MATTER_DISC_CRED would be present for the item. The segment will be nested under the appropriate @MATTER_DISC_CRED item. Note that the @EXTEND_HEADER option was purposely omitted from this segment.
VRP: The relevant Tax from Tax Segment should be passed on to calculate tax on the matter/invoice level adjustments for 'IE' or 'IF' type line items.
Ver 2.1 file_item_nbr
Ver 2.0 file_item_nbr
LEDES98BI
LEDES98BI LINE_ITEM_TAX_TOTAL
LEDES98B
The specific taxes relevant to the parent @MATTER_DISC_CRED items. There will be 0 or more @TAX_MATTER_DISC_CRED segments for each
The item count of this data element in the invoice file submission.
The item count of this data element in the invoice file submission.
Total amount of tax for the line item. This must be ((LINE_ITEM_UNIT_COST * LINE_ITEM_NUMBER_OF_UNITS) + LINE_ITEM_ADJUSTMENT_AMOUNT) * LINE_ITEM_TAX_RATE. VRP: We may add this field in to other xml types also for cross verification. In this section it will be for 'IE' or 'IF' line items tax.
Version Ver 2.1 Field tk_id
Description
Version Ver 2.0 Field tk_id
Description
Version XML2000Field tk_id
Description
Version LEDES98BI Field TIMEKEEPER_ID
Description
Version LEDES98BField TIMEKEEPER_ID
Description
Information on the timekeepers for this firm. There will be 0 or more @TKSUM segments per @MATTER segment. Note that every @FEE.tk_id and every @EXPENSE.tk_id used in this invoice must be included in this @TKSUM segment.
Unique ID of a person billing on this matter. The same tk_id may appear multiple times if the timekeeper's name, level or rate changes during the billing period. This value is assigned by the firm and should remain the same for a biller across all work done by the biller within the firm (could be biller initials if the biller initials will be unique across that firm)
Unique ID of a person billing on this matter. The same tk_id may appear multiple times if the timekeeper's name, level or rate changes during the billing period. This value is assigned by the firm and should remain the same for a biller across all work done by the biller within the firm (could be biller initials if the biller initials will be unique across that firm)
A unique identifier for the timekeeper for this line entry. Typically, the identifier used here is the primary key for a timekeeper used in a law firm’s financial system (e.g., an employee number, social security number, initials, or anything else so long as it uniquely identifies a particular timekeeper). For fee line items, a null value ("") would be an error. Most expense items probably do not have a TIMEKEEPER_ID associated with them (in which case this field would be left null). Actual timekeeper names should be avoided.VRP: This being a base segment, we can pass on the distinct Timekeeper_ID's in the invoice
A unique identifier for the timekeeper for this line entry. Typically, the identifier used here is the primary key for a timekeeper used in a law firm’s financial system (e.g., an employee number, social security number, initials, or anything else so long as it uniquely identifies a particular timekeeper). For fee line items, a null value ("") would be an error. Most expense items probably do not have a TIMEKEEPER_ID associated with them (in which case this field would be left null). VRP: This being a base segment, we can pass on the distinct Timekeeper_ID's in the invoice
Ver 2.1
Ver 2.0
XML2000
LEDES98BI TIMEKEEPER_NAME
LEDES98BTIMEKEEPER_NAME
Information on the timekeepers for this firm. There will be 0 or more @TKSUM segments per @MATTER segment.
Note that every @FEE.tk_id and every @EXPENSE.tk_id used in this invoice must be included in this @TKSUM segment.
The name of a timekeeper. Names must be entered Last name first, then a comma, followed by First name (e.g., "Arnsley, Robert"). THIS FIELD IS PROVIDED FOR INFORMATION ONLY AND MUST NOT BE USED BY THE RECEIVING APPLICATION AS A PRIMARY KEY FOR TIMEKEEPER. This field is mandatory. Most expense items probably do not have a TIMEKEEPER_NAME associated with them (in which case this field would be left null).
The name of a timekeeper. Names must be entered Last name first, then a comma, followed by First name (e.g., "Arnsley, Robert"). THIS FIELD IS PROVIDED FOR INFORMATION ONLY AND MUST NOT BE USED BY THE RECEIVING APPLICATION AS A PRIMARY KEY FOR TIMEKEEPER. This field is mandatory. Most expense items probably do not have a TIMEKEEPER_NAME associated with them (in which case this field would be left null).
Ver 2.1 tk_lname
The last name of the timekeeper.
Ver 2.0 tk_lname
XML2000tk_lname
LEDES98BI TIMEKEEPER_LAST_NAME
LEDES98B
The last name of the timekeeper.
The last name of a timekeeper. THIS FIELD IS PROVIDED FOR INFORMATION ONLY AND MUST NOT BE USED BY THE RECEIVING APPLICATION AS A PRIMARY KEY FOR A MATTER. A null value (“”) would be an error for F and IF EXP/FEE/TAX/INV_ADJ_TYPE (most expense and tax line-items probably do not have a TIMEKEEPER_NAME associated with them, in which case this field would be left null (“”)). This data is duplicative of the TIMEKEEPER_NAME field.
tk_fname
The first name of the timekeeper.
tk_fname
tk_fname
TIMEKEEPER_FIRST_NAME
The first name of the timekeeper.
The first name of a timekeeper. THIS FIELD IS PROVIDED FOR INFORMATION ONLY AND MUST NOT BE USED BY THE RECEIVING APPLICATION AS A PRIMARY KEY FOR A MATTER. A null value (“”) would be an error for F and IF EXP/FEE/TAX/INV_ADJ_TYPE (most expense and tax line-items probably do not have a TIMEKEEPER_NAME associated with them, in which case this field would be left null (“”)). This data is duplicative of the TIMEKEEPER_NAME field.
tk_level
The level of the timekeeper.
tk_level
tk_level
TIMEKEEPER_CLASSIFICATION
TIMEKEEPER_CLASSIFICATION
The level of the timekeeper. Valid values are: "Partner", "Associate", "Of Counsel", "Paralegal", "Legal Assistant", "Secretary", "Clerk", "Other" [Note: It is possible for a timekeeper to bill at more than tk_level hourly rate during a given invoice period.]
The staff classification of a timekeeper. This field must use one of the following codes: "PT" (for partner), "AS" (for associate), "OC" (for of counsel), "LA" (for legal assistant), "OT" (for other timekeeper), "SI" (for summer intern), "PL" (for paralegal), "SE" for secretary or clerk), and "NP" (for non-legal professional). THIS FIELD IS PROVIDED FOR INFORMATION ONLY AND MUST NOT BE USED BY THE RECEIVING APPLICATION AS A PRIMARY KEY FOR TIMEKEEPER. Most expense items probably do not have a TIMEKEEPER_CLASSIFICATION associated with them (in which case this field would be left null). VRP: We can pass on the first classification for a tk billing code to this item.
The staff classification of a timekeeper. This field must use one of the following codes: "PT" (for partner), "AS" (for associate), "OC" (for of counsel), "LA" (for legal assistant), or "OT" (for other timekeeper). THIS FIELD IS PROVIDED FOR INFORMATION ONLY AND MUST NOT BE USED BY THE RECEIVING APPLICATION AS A PRIMARY KEY FOR TIMEKEEPER. Most expense items probably do not have a TIMEKEEPER_CLASSIFICATION associated with them (in which case this field would be left null). VRP: We can pass on the first classification for a tk billing code to this item.
tk_rate file_item_nbr
tk_rate file_item_nbr
tk_rate
The hourly rate of the timekeeper.
[Note: It is possible for a timekeeper to bill at more than one tk_level hourly rate during a given invoice period.]
The contracted hourly rate billed by this timekeeper for this matter prior to any discounts or adjustments, e.g. "120.0000" [Note: It is possible for a timekeeper to bill at more than one tk_rate during a given invoice period.]
The item count of this data element in the invoice file submission.
extend_header
@extend_header
tk_hours tk_cost
Used for client and/or firm specific extensions to the @TKSUM Segment (See @EXTEND_HEADER Segment)
Used for client and/or firm specific extensions to the @TKSUM Segment (See @EXTEND_HEADER Segment.)
Total Hours of the TK under the rate
Total cost of the TK under the rate
Version Ver 2.1 Field charge_date tk_id tk_level
Description Date the service was performed. The level of the timekeeper.
Version Ver 2.0 Field charge_date tk_id tk_level
DescriptionVersion XML 2000Field charge_date tk_id
DescriptionVersion LEDES98BI
FieldLINE_ITEM_DATE TIMEKEEPER_ID TIMEKEEPER_CLASSIFICATION
DescriptionVersion LEDES98B
FieldLINE_ITEM_DATE TIMEKEEPER_ID TIMEKEEPER_CLASSIFICATION
Description
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.
Unique ID for the person performing the service billed by this line item.
Date the service was performed.
Unique ID for the person performing the service billed by this line item.
The level of the timekeeper. Valid values are: "Partner", "Associate", "Of Counsel", "Paralegal", "Legal Assistant", "Secretary", "Clerk", "Other".
The date the fees/expenses were incurred. Typically, this date is between the BILLING_START_DATE and the BILLING_END_DATE. A null value ("") would be an error. (VRP: For Fee Line Items)
Unique ID for the timekeeper. VRP: This field is used in TKSUM segment already but can also become a field in Fee segment (VRP: For Fee Line Items)
The staff classification of a timekeeper. VRP: This field is used in TKSUM segment already but can also become a field in Fee segment
The date the fees/expenses were incurred. Typically, this date is between the BILLING_START_DATE and the BILLING_END_DATE. A null value ("") would be an error. (VRP: For Fee Line Items)
Unique ID for the timekeeper. VRP: This field is used in TKSUM segment already but can also become a field in Fee segment(VRP: For Fee Line Items)
The staff classification of a timekeeper. VRP: This field is used in TKSUM segment already but can also become a field in Fee segment
work_location_country work_location_locality
fee_work_location
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
The country of where work associated with the fee item was performed, to support the taxes appearing in the @TAX_ITEM_EXPENSE Segment. Use ISO 3166 country code set forth by International Standards Organization (www.iso.org.)
The location where the work associated with the fee item was performed, to support the taxes appearing in the @TAX_ITEM_FEE Segment. For example, in Canada appropriate values would be the Province; if City or other local tax is charged would be City or locality. Use accepted abbreviations for state or province mandated by the country's postal service.
The location where the work was performed that supports the taxes appearing in the @TAX_ITEM_FEE Segment. For example, in Canada appropriate values would be the Province; if City or other local tax is charged would be City or locality. Use accepted abbreviations for state or province mandated by the country's postal service; do not abbreviate country names.
charge_desc task_code task_activity
charge_desc task_code task_activity
charge_desc acca_task acca_activity
LINE_ITEM_DESCRIPTION LINE_ITEM_TASK_CODE LINE_ITEM_ACTIVITY_CODE
LINE_ITEM_DESCRIPTION LINE_ITEM_TASK_CODE LINE_ITEM_ACTIVITY_CODE
Narrative description of the service provided for this line item.
Task code for this line item, e.g. "L110". Only one code per line item
Activity code for this line item, e.g. "A101". Only one code per line item
Narrative description of the service provided for this line item.
Task code for this line item, e.g. "L110". Only one code per line item.
Activity code for this line item, e.g. "A101". Only one code per line item.
Free form description of this line item. May be up to 15KB of text. If an expense item uses a LINE_ITEM_EXPENSE_CODE, this field is usually left null. VRP: For fee line items
The task code (e.g., using the UTBMS code set) for this line item. Most expense items probably do not have a LINE_ITEM_TASK_CODE associated with them (in which case this field would be left null).
The activity code (e.g., using the UTBMS code set) for this fee line item. Most expense items probably do not have a LINE_ITEM_ACTIVITY_CODE associated with them (in which case this field would be left null).
Free form description of this line item. May be up to 15KB of text. If an expense item uses a LINE_ITEM_EXPENSE_CODE, this field is usually left null. VRP: For fee line items
The task code (e.g., using the UTBMS code set) for this line item. Most expense items probably do not have a LINE_ITEM_TASK_CODE associated with them (in which case this field would be left null).
The activity code (e.g., using the UTBMS code set) for this fee line item. Most expense items probably do not have a LINE_ITEM_ACTIVITY_CODE associated with them (in which case this field would be left null)
charge_type units
charge_type units
charge_type units
LINE_ITEM_NUMBER_OF_UNITS
LINE_ITEM_NUMBER_OF_UNITS
"U" unit price, "F" fixed charge. [Note: most line items are will be unit price.]
Actual number of hours billed to this line item, e.g. "3.40". If @FEE.charge_type = "F", enter the number of units that will be multiplied by the rate necessary to equal the @FEE.base_amount charged for this line item.
"U" unit price, "F" fixed charge. [Note: most line items are will be unit price.]
Actual number of hours billed to this line item, e.g. "3.40"
The number of units billed on this line item. For fee items, this is the number of hours being billed. For expense items, this is the number of items being expensed. For invoice-level adjustments, this field is ignored. A value of zero "0" or null ("") would be an error unless the line item is an invoice-level adjustment.
The number of units billed on this line item. For fee items, this is the number of hours being billed. For expense items, this is the number of items being expensed. For invoice-level adjustments, this field is ignored. A value of zero "0" or null ("") would be an error unless the line item is an invoice-level adjustment.
rate base_amount
rate base_amount
rate base_amount
LINE_ITEM_UNIT_COST
LINE_ITEM_UNIT_COST
The timekeeper rate for this line item. E.g. "120.0000", or the fixed rate for the item
The original WIP value of the time entry before adjustments or discounts of any sort are applied. Regardless of charge_type, then base_amount = units * rate prior to any adjustments or discounts. E.g. "300.0000"
The timekeeper rate for this line item, if applicable. E.g. "120.0000"
The original WIP value of the time entry before adjustments or discounts of any sort are applied. If charge_type is "U", then base_amount = hours * rate prior to any adjustments or discounts. If charge type is "F", then base_amount is a fixed amount. E.g. "300.0000"
The standard (i.e., undiscounted) unit cost of the line item. For fees, this would be the hourly rate. For expenses, this would be the cost per unit. For invoice-level adjustments, this field is ignored. A value of zero ("0") or null ("") would be an error unless the line item is an invoice-level adjustment.
The standard (i.e., undiscounted) unit cost of the line item. For fees, this would be the hourly rate. For expenses, this would be the cost per unit. For invoice-level adjustments, this field is ignored. A value of zero ("0") or null ("") would be an error unless the line item is an invoice-level adjustment.
item_disc_cred_amount total_amount
item_disc_cred_amount total_amount
discount_amount total_amount
LINE_ITEM_ADJUSTMENT_AMOUNT LINE_ITEM_TOTAL
LINE_ITEM_ADJUSTMENT_AMOUNT LINE_ITEM_TOTAL
Sum of all @FEE_ITEM_DISC_CRED.disc_cred_amounts for this fee item. Does not include @MATTER_DISC_CRED.disc_cred_amounts.
The final billed value of the fee item after application of all @FEE_ITEM_DISC_CRED.disc_cred_amounts. Does not include @MATTER_DISC_CRED.disc_cred_amounts or taxes on the fee item. @FEE.total_amount = @FEE.base_amount + @FEE.item_disc_cred_amount
Sum of all @FEE_ITEM_DISC_CRED.disc_cred_amounts for this fee item. Does not include @MATTER_DISC_CRED.disc_cred_amounts.
The final billed value of the fee item after application of all @FEE_ITEM_DISC_CRED.disc_cred_amounts. Does not include @MATTER_DISC_CRED.disc_cred_amounts or taxes on the fee item. @FEE.total_amount = @FEE.base_amount + @FEE.item_disc_cred_amount
The numerical value of any adjustment applied to this line item. A positive value indicates a premium, a negative value indicates a discount. A null ("") or zero ("0") value indicates no adjustment.
The numerical value of this line item. This must be (LINE_ITEM_UNIT_COST * LINE_ITEM_NUMBER_OF_UNITS) + LINE_ITEM_ADJUSTMENT_AMOUNT + LINE_ITEM_TAX_TOTAL. A null value ("") would be an error.
The numerical value of any adjustment applied to this line item. A positive value indicates a premium, a negative value indicates a discount. A null ("") or zero ("0") value indicates no adjustment.
The numerical value of this line item. This must be (LINE_ITEM_UNIT_COST * LINE_ITEM_NUMBER_OF_UNITS) + LINE_ITEM_ADJUSTMENT_AMOUNT. A null value ("") would be an error.
file_item_nbr @extend_header
file_item_nbr @extend_header
cl_code_1 cl_code_2
The item count of this data element in the invoice file submission.
Used for client and/or firm specific extensions to the @FEE Segment (See @EXTEND_HEADER Segment below.)
The item count of this data element in the invoice file submission.
Used for client and/or firm specific extensions to the @FEE Segment (See @EXTEND_HEADER Segment below.)
Version Ver 2.1 Field disc_cred disc_cred_note
Description
Version Ver 2.0Field disc_cred disc_cred_note
Description
Version XML 2000Field
Description
Version LEDES98BI Field VRP: We may pass a fixed value 'FIA'
Description
Version LEDES98B Field VRP: We may pass a fixed value 'FIA'
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.
The disc_credit field is used to track discounts and credits that the law firm may need to submit on the fee item.
FIA - Fee item Adjustment - A flat adjustment (reduction or credit) applied to the fee itemFID - Fee Item Discount - Client receives a percentage discount that is assessed at the fee item levelFIFF - Fee Item is billed at a Flat FeeFIDHR - Fee Item Discounted Hourly Rate - the discounted hourly rate applied to the fee itemOther - Any other type of discount or credit applied to the line item
Identification of the discount or credit identified in the disc_credit field as "Other", using codes specified by the client.
The disc_credit field is used to track discounts and credits that the law firm may need to submit on the fee item.
"FID" (Fee Item Discount - client receives a percentage discount that is assessed at the fee item level), "FIFF" (Fee Item is billed at a Flat Fee), "FIA" (Fee item Adjustment - A flat adjustment (reduction or credit) applied to the fee item), "FIDHR" (Fee Item Discounted Hourly Rate - the discounted hourly rate applied to the fee item); or "OTHER"
Identification of the discount or credit identified in the disc_credit field as "Other", using codes specified by the client.
VRP: FID or FIA may be passed depending upon the discount type
Description
disc_cred_type increase_decrease discount_percent
disc_cred_type discount_percent
discount_type discount_percent
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
Note that the @EXTEND_HEADER option was purposely omitted from this segment.
Type of discount or credit applied to the fee item. Valid values are "Percent" and "Flat". If disc_cred = " FIDHR" or "Other", disc_cred_type must be "Flat".
Identifies whether the disc_cred results in increasing the cost of the fee item (and is therefore a charge applied to the fee item) or decreasing the cost of the fee item (and is therefore a reduction applied to the fee item).
A percentage number expressing the percent discount provided to this charge, i.e. "0.15" reflects a 15% discount to the charge.
Type of discount or credit applied to the fee item. Valid values are "Percent" and "Flat"
A percentage number expressing the percent discount provided to this charge, i.e. "0.15" reflects a 15% discount to the charge. This value is always a reduction to the invoice.
disc_cred_amount file_item_nbr
disc_cred_amount file_item_nbr
discount_amount
The total amount discounted/credited against or additional charges incurred for this disc_cred. If @FEE_ITEM_DISC_CRED.increase_decrease equals "increase", then this value is a positive number; if @FEE_ITEM_DISC_CRED.increase_decrease equals "decrease", then this value is a negative number. I.e. "-150.0000" reflects a $150 decrease/reduction/write-down on the fee item, "150.0000" reflects a $150 increase/charge/write-up on the fee item.
The item count of this data element in the invoice file submission.
The total amount discounted or credited for this disc_cred. Discounts or reductions should be a negative number; credits should be a positive number. I.e. "-150.0000" reflects a $150 disc_cred, "150.0000" reflects a $150 credit.
The item count of this data element in the invoice file submission.
LINE_ITEM_ADJUSTMENT_AMOUNT
The numerical value of any adjustment applied to this line item. A positive value indicates a premium, a negative value indicates a discount. A null ("") or zero ("0") value indicates no adjustment.
LINE_ITEM_ADJUSTMENT_AMOUNT
The numerical value of any adjustment applied to this line item. A positive value indicates a premium, a negative value indicates a discount. A null ("") or zero ("0") value indicates no adjustment.
Version Ver 2.1 Field tx_id
Description
Version Ver 2.0Field tx_id
Description
Version XML 2000FieldDescription
Version LEDES98BI FieldDescription
Version LEDES98B FieldDescription
The specific taxes relevant to the parent @FEE (and therefore its child @FEE_ITEM_DISC_CRED) items. There will be 0 or more @TAX_ITEM_FEE segments for each @FEE (and its child @FEE_ITEM_DISC_CRED) segment.
The @EXTEND_HEADER option was purposely omitted from this segment.
Taxes relevant to fee item. Refers to @TAX.tx_id value. Could be many @TAX_ITEM_FEE.tx_id entries per fee item.
Taxes relevant to fee item. Refers to @TAX.tx_id value. Could be many @TAX_ITEM_FEE.tx_id entries per fee item.
VRP: The relevant Tax ID from Tax Segment should be passed on to calculate tax on the matter/invoice level adjustments
VRP: The relevant Tax ID from Tax Segment should be passed on to calculate tax on the matter/invoice level adjustments
Ver 2.1 file_item_nbr
Ver 2.0file_item_nbr
XML 2000
LEDES98BI
LEDES98B
The specific taxes relevant to the parent @FEE (and therefore its child @FEE_ITEM_DISC_CRED) items. There will be 0 or more @TAX_ITEM_FEE segments for each @FEE (and its child @FEE_ITEM_DISC_CRED) segment.
The @EXTEND_HEADER option was purposely omitted from this segment.
The item count of this data element in the invoice file submission.
The item count of this data element in the invoice file submission.
Version Ver 2.1 Field charge_date tk_id tk_level work_location_country work_location_locality charge_desc task_code expense_code charge_type units
Description
Unique ID for the timekeeper. The level of the timekeeper. Quantity of units billed to this line item.
Version Ver 2.0Field charge_date tk_id tk_level work_location charge_desc task_code expense_code charge_type units
DescriptionVersion XML 2000Field charge_date tk_id charge_desc acca_task acca_expense charge_type units
DescriptionVersion LEDES98BI
FieldLINE_ITEM_DATE TIMEKEEPER_ID TIMEKEEPER_CLASSIFICATION LINE_ITEM_DESCRIPTION LINE_ITEM_TASK_CODE LINE_ITEM_EXPENSE_CODE LINE_ITEM_NUMBER_OF_UNITS
DescriptionVersion LEDES98B
FieldLINE_ITEM_DATE TIMEKEEPER_ID TIMEKEEPER_CLASSIFICATION LINE_ITEM_DESCRIPTION LINE_ITEM_TASK_CODE LINE_ITEM_EXPENSE_CODE LINE_ITEM_NUMBER_OF_UNITS
Description
The expense items included in the matter/invoice. There will be 0 or more @EXPENSE segments per @MATTER segment. All expense items are subject to the same @MATTER_DISC_CRED.disc_cred MISF (Matter/Invoice Shared Fee) and MIDB (Matter/Invoice Discounted Bill) as all fee items for this matter/invoice. If expense 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.
Date the service was performed The country where work associated with the expense was performed, to support the taxes appearing in the @TAX_ITEM_EXPENSE Segment. Use ISO 3166 country code set forth by International Standards Organization (www.iso.org.)
The location where work associated with the expense was performed, to supports the taxes appearing in the @TAX_ITEM_EXPENSE Segment. For example, in Canada appropriate values would be the Province; if City or other local tax is charged would be City or locality. Use accepted abbreviations for state or province mandated by the country's postal service.
Narrative description of the expense charged by this line item.
Task code for this line item, e.g. "L110". Only one code per line item
Expense code for this line item, e.g. "E101". Only one code per line item.
"U" unit price, "F" fixed charge.
Date the service was performed Unique ID for the timekeeper. The level of the timekeeper. Valid values are: "Partner", "Associate", "Of Counsel", "Paralegal", "Legal Assistant", "Secretary", "Clerk", "Other"
The location where the work was performed that supports the taxes appearing in the @TAX_ITEM_EXPENSE Segment. For example, in Canada appropriate values would be the Province; if City or other local tax is charged would be City or locality. Use accepted abbreviations for state or province mandated by the country's postal service; do not abbreviate country names.
Narrative description of the expense charged by this line item.
Task code for this line item, e.g. "L110". Only one code per line item.
Expense code for this line item, e.g. "E101". Only one code per line item.
"U" unit price, "F" fixed charge. Quantity of units billed to this line item.
The date the fees/expenses were incurred. Typically, this date is between the BILLING_START_DATE and the BILLING_END_DATE. A null value ("") would be an error. (VRP: For Expense Line Items)
Unique ID for the timekeeper. VRP: This field is used in TKSUM segment already but can also become a field in Fee segment (VRP: For Expense Line Items)
The staff classification of a timekeeper. VRP: This field is used in TKSUM segment already but can also become a field in Fee segment
Free form description of this line item. May be up to 15KB of text. If an expense item uses a LINE_ITEM_EXPENSE_CODE, this field is usually left null. (VRP: For Expense Line Items)
The task code (e.g., using the UTBMS code set) for this line item. Most expense items probably do not have a LINE_ITEM_TASK_CODE associated with them (in which case this field would be left null). (VRP: For Expense Line Items)
The expense code (e.g., using the UTBMS code set) for this expense line item. Most fee items probably do not have a LINE_ITEM_EXPENSE_CODE associated with them (in which case this field would be left null).
The number of units billed on this line item. For fee items, this is the number of hours being billed. For expense items, this is the number of items being expensed. For invoice-level adjustments, this field is ignored. A value of zero "0" or null ("") would be an error unless the line item is an invoice-level adjustment. VRP: For expense Line Items
The date the fees/expenses were incurred. Typically, this date is between the BILLING_START_DATE and the BILLING_END_DATE. A null value ("") would be an error. (VRP: For Expense Line Items)
Unique ID for the timekeeper. VRP: This field is used in TKSUM segment already but can also become a field in Fee segment (VRP: For Expense Line Items)
The staff classification of a timekeeper. VRP: This field is used in TKSUM segment already but can also become a field in Fee segment
Free form description of this line item. May be up to 15KB of text. If an expense item uses a LINE_ITEM_EXPENSE_CODE, this field is usually left null. (VRP: For Expense Line Items)
The task code (e.g., using the UTBMS code set) for this line item. Most expense items probably do not have a LINE_ITEM_TASK_CODE associated with them (in which case this field would be left null). (VRP: For Expense Line Items)
The expense code (e.g., using the UTBMS code set) for this expense line item. Most fee items probably do not have a LINE_ITEM_EXPENSE_CODE associated with them (in which case this field would be left null).
The number of units billed on this line item. For fee items, this is the number of hours being billed. For expense items, this is the number of items being expensed. For invoice-level adjustments, this field is ignored. A value of zero "0" or null ("") would be an error unless the line item is an invoice-level adjustment. VRP: For expense Line Items
rate base_amount item_disc_cred_amount total_amount payee_name file_item_nbr @extend_header
rate base_amount item_disc_cred_amount total_amount file_item_nbr @extend_header
rate base_amount discount_amount total_amount
LINE_ITEM_UNIT_COST LINE_ITEM_TOTAL
LINE_ITEM_UNIT_COST LINE_ITEM_TOTAL
The expense items included in the matter/invoice. There will be 0 or more @EXPENSE segments per @MATTER segment. All expense items are subject to the same @MATTER_DISC_CRED.disc_cred MISF (Matter/Invoice Shared Fee) and MIDB (Matter/Invoice Discounted Bill) as all fee items for this matter/invoice. If expense 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.
Rate for this line item or the fixed rate for the item. The original WIP value of the expense entry before adjustments or discounts of any sort are applied. Regardless of charge_type, then base_amount = hours units * rate prior to any adjustments or discounts. E.g. "300.0000"
Total of all @EXPENSE_ITEM_DISC_CRED.disc_cred_amount for this expense item. Does not include @MATTER_DISC_CRED.disc_cred_amounts.
The final "billed" value of the expense entry after application of all @EXPENSE_ITEM_DISC_CRED.disc_cred_amount. Does not include @MATTER_DISC_CRED.disc_cred_amounts or taxes on the expense item @EXPENSE.total_amount = @EXPENSE.base_amount + @EXPENSE.item_disc_cred_amount
The name of the payee for the expense item. If a payee name is indicated, the item is a disbursement paid to a third party and not a firm expense or soft cost.
The item count of this data element in the invoice file submission.
Used for client and/or firm specific extensions to the @EXPENSE Segment (See @EXTEND_HEADER Segment below.)
Rate for this line item. The original WIP value of the expense entry before adjustments or discounts of any sort are applied. If charge_type is "U", then base_amount = units * rate prior to any adjustments or discounts. If charge type is ""F", then base_amount is a fixed amount. E.g. "300.0000".
Total of all @EXPENSE_ITEM_DISC_CRED.disc_cred_amount for this expense item. Does not include @MATTER_DISC_CRED.disc_cred_amounts.
The final "billed" value of the expense entry after application of all @EXPENSE_ITEM_DISC_CRED.disc_cred_amount. Does not include @MATTER_DISC_CRED.disc_cred_amounts or taxes on the expense item @EXPENSE.total_amount = @EXPENSE.base_amount + @EXPENSE.item_disc_cred_amount
The item count of this data element in the invoice file submission.
Used for client and/or firm specific extensions to the @EXPENSE Segment (See @EXTEND_HEADER Segment below.)
LINE_ITEM_ADJUSTMENT_AMOUNT
The standard (i.e., undiscounted) unit cost of the line item. For fees, this would be the hourly rate. For expenses, this would be the cost per unit. For invoice-level adjustments, this field is ignored. A value of zero ("0") or null ("") would be an error unless the line item is an invoice-level adjustment.VRP: For Expense Line Items
The numerical value of any adjustment applied to this line item. A positive value indicates a premium, a negative value indicates a discount. A null ("") or zero ("0") value indicates no adjustment.
The numerical value of this line item. This must be (LINE_ITEM_UNIT_COST * LINE_ITEM_NUMBER_OF_UNITS) + LINE_ITEM_ADJUSTMENT_AMOUNT + LINE_ITEM_TAX_TOTAL. A null value ("") would be an error.
LINE_ITEM_ADJUSTMENT_AMOUNT
The standard (i.e., undiscounted) unit cost of the line item. For fees, this would be the hourly rate. For expenses, this would be the cost per unit. For invoice-level adjustments, this field is ignored. A value of zero ("0") or null ("") would be an error unless the line item is an invoice-level adjustment. VRP: For Expense Line Items
The numerical value of any adjustment applied to this line item. A positive value indicates a premium, a negative value indicates a discount. A null ("") or zero ("0") value indicates no adjustment.
The numerical value of this line item. This must be (LINE_ITEM_UNIT_COST * LINE_ITEM_NUMBER_OF_UNITS) + LINE_ITEM_ADJUSTMENT_AMOUNT + LINE_ITEM_TAX_TOTAL. A null value ("") would be an error.
Version Ver 2.1 Field disc_cred disc_cred_note
Description
Version Ver 2.0Field disc_cred disc_cred_note
Description
Version XML 2000Field VRP: We may pass 'EIA' or 'EID' based on discount type
Description
Version LEDES98BI Field VRP: We may pass a fixed value 'EIA'
Description
Version LEDES98B Field VRP: We may pass a fixed value 'EIA'
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.
The disc_credit field is used to track discounts and credits that the law firm may need to submit on the expense item.
EIA - Expense Item Adjustment - A flat adjustment (reduction or credit) applied to the fee itemEID - Expense Item Discount - client receives a percentage discount that is assessed at the expense item levelEIDHR - Expense Item Discounted Hourly Rate - the discounted hourly rate or unit rate applied to the expense itemEIFF - Expense Item is billed at a Flat FeeOther - Any other type of discount of credit applied to the line item
Identification of the discount or credit identified in the disc_credit field as "Other", using codes specified by the client.
The disc_credit field is used to track discounts and credits that the law firm may need to submit on the expense item.
"EID" (Expense Item Discount - client receives a percentage discount that is assessed at the expense item level), "EIFF" (Expense Item is billed at a Flat Fee), "EIA" (Expense Item Adjustment - A flat adjustment (reduction or credit) applied to the fee item), "EIDHR" (Expense Item Discounted Hourly Rate - the discounted hourly rate applied to the expense item); or "OTHER"
An explanation of the discount or credit, using codes specified by the client.
Description
disc_cred_type increase_decrease disc_cred_percent
disc_cred_type disc_cred_percent
discount_type discount_percent
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
Type of discount or credit applied to the expense item. Valid values are "Percent" and "Flat". If disc_cred equals "EIDHR" or "Other", disc_cred_type must be "Flat".
Identifies whether the disc_cred results in increasing the cost of the expense item (and is therefore a charge applied to the expense item) or decreasing the cost of the expense item (and is therefore a reduction applied to the expense item).
A percentage number expressing the percent discount provided to this charge, i.e. "0.15" reflects a 15% discount to the charge.
Type of discount or credit applied to the expense item. Valid values are "Percent" and "Flat"
A percentage number expressing the percent discount provided to this charge, i.e. "0.15" reflects a 15% discount to the charge. This value is always a reduction to the invoice.
disc_cred_amount file_item_nbr
disc_cred_amount file_item_nbr
discount_amount
The total amount discounted/credited against or additional charges incurred for this disc_cred. If @EXP_ITEM_DISC_CRED.increase_decrease equals "increase", then this value is a positive number; if @EXP_ITEM_DISC_CRED.increase_decrease equals "decrease", then this value is a negative number. Discounts or reductions should be a negative number; credits should be a positive number. I.e. "-150.0000" reflects a $150 decrease/reduction/write-down on the expense item, "150.0000" reflects a $150 increase/charge/write-up on the expense item.
The total amount discounted or creditedfor this disc_cred. Discounts or reductions should be a negative number; credits should be a positive number. I.e. "-150.0000" reflects a $150 discount, "150.0000" reflects a $150 credit.
LINE_ITEM_ADJUSTMENT_AMOUNT
The numerical value of any adjustment applied to this line item. A positive value indicates a premium, a negative value indicates a discount. A null ("") or zero ("0") value indicates no adjustment.
LINE_ITEM_ADJUSTMENT_AMOUNT
The numerical value of any adjustment applied to this line item. A positive value indicates a premium, a negative value indicates a discount. A null ("") or zero ("0") value indicates no adjustment.
Version Ver 2.1 Field tx_id file_item_nbr
Description
Version Ver 2.0Field tx_id file_item_nbr
Description
Version XML 2000FieldDescription
Version LEDES98BI FieldDescription
Version LEDES98B FieldDescription
The specific taxes relevant to the parent @EXPENSE (and therefore its child @EXPENSE_ITEM_DISC_CRED) items. There will be 0 or more @TAX_ITEM_EXPENSE segments for each @EXPENSE (and its child @EXPENSE_ITEM_DISC_CRED) segment.
The @EXTEND_HEADER option was purposely omitted from this segment.
Taxes relevant to fee item. Refers to @TAX.tx_id value. Could be many @TAX_ITEM_FEE.tx_id entries per fee item.
The item count of this data element in the invoice file submission.
Taxes relevant to fee item. Refers to @TAX.tx_id value. Could be many @TAX_ITEM_FEE.tx_id entries per fee item.
The item count of this data element in the invoice file submission.
VRP: The relevant Tax from Tax Segment should be passed on to calculate tax on the matter/invoice level adjustments
VRP: The relevant Tax from Tax Segment should be passed on to calculate tax on the matter/invoice level adjustments