Invoice Detail Settings
Collaborati allows your offices to upload invoicing files in file formats:
- LEDES1998B file format, which was originally intended for domestic U.S. invoicing.
- LEDES1998BI file format, which has all of the fields of LEDES1998B, and many more fields that are related to international taxation, client profile, and office profile.
- LEDES2000 file format, which supports the XML format.
- LEDES XML 2.0 file format.
- LEDES XML 2.1 file format.
Offices can also create and edit invoices manually in Collaborati, using the Collaborati web pages designed for that purpose. They can create invoices with information equivalent to their selected LEDES format.
These formats are described in detail in the Collaborati online help file.
CSM automatically imports information contained in the LEDES1998B format into TeamConnect. The additional fields of the LEDES1998BI format are not imported automatically by CSM. But there are configuration options and procedures, performed by both you and your offices, that will allow you to receive and use the additional fields. Configuring Collaborati to Use Additional LEDES Fields describes those options and procedures.
Handling Non-U.S. Tax and International Invoicing Fields
Your offices can send non-U.S. tax information through all LEDES formats. In this case, CSM will capture the non-U.S. tax information automatically.
To accomplish this:
- Be sure that you have authorized the appropriate non-U.S. tax categories, as described in Authorizing Non-US Tax Codes Globally.
- Tell your offices to follow the procedures described in the How do I upload LEDES files with Non-US Taxes (VAT, GST)? section of their Collaborati online help file.
The following LEDES formats can also include non-U.S. taxes at the line item level:
- LEDES1998B
- LEDES XML 2.0
- LEDES XML 2.1
Configuring Collaborati to Use Additional LEDES Fields
Currently, Collaborati does not pass any of the client profile or office profile information along with invoices to TeamConnect. LEDES1998BI V2, LEDES2000, LEDES XML 2.0, and LEDES XML 2.1 formats include additional data fields, such as client tax ID, name, and location, and office tax ID, name, and location, with each invoice line item.
If your department has complex business requirements related to VAT collection and verification, you may need to store this information as part of the original invoice coming from Collaborati.
If so, you can configure the Invoice Detail Settings page of CSM Settings to specify which fields on your TeamConnect invoice would store these additional values.
You can also define and configure extended custom fields that you want to support on incoming Collaborati LEDES XML invoices. When you configure extended custom fields, offices can enter data in the @EXTEND_HEADER and @EXTEND_DATA segments.
To configure Collaborati to use invoice fields
- From CSM Settings, click the Invoice Detail Settings link from the left pane.
- Select the Store Additional Collaborati invoice information on the system invoice record check box.
- Specify the Information data you want to map by selecting the corresponding Store check box. For a list of the supported additional LEDES1998 BI fields that are available in the Information column, see Supported Additional Fields.
- From the Invoice Field Name drop-down list, select the custom field in the TeamConnect invoice that you want to map to the corresponding Collaborati field. Selected fields must be of the same datatype.
- Click a save option.
Notes:
- The drop-down lists in step 4 only show the current custom fields of the same datatype found under the Root invoice category.
- A TeamConnect invoice custom field can be mapped to only one Collaborati field, including mappings made here and on the Payments tab.
- At least one field must be enabled to allow mapping. You enable a field by checking its box in the Store column.
- You cannot map to a TeamConnect invoice field that has a default value defined.
To configure Collaborati to use extended custom fields
- From CSM Settings, click the Invoice Detail Settings link from the left pane.
- Click Edit.
- In the Extended Information field, enter the extended custom field name that you want to map.
- In the Invoice Field Name field, select the custom field in the TeamConnect invoice that you want to map to the corresponding Collaborati field. This list contains custom fields of type text/memo under the Invoice root category in TeamConnect.
- Click the Store check-box.
- Click Add.
- Repeat steps 3–6 for each custom field that you want to map.
- When you are done, select a save option.
To delete extended field mappings
Select the check-box for the mapping that you want to delete, and then click Remove. The selected fields are from this view.
To edit extended field mappings
In the Action column, click the edit icon. The current information appears above in the Extended Information and Invoice Field Name fields. Edit as necessary, and then click OK.
To copy an extended field mapping
In the Action column, click the copy icon. The current mapping details appear above in the Extended Information and Invoice Field Name fields. Change the information, click Add, and then select a save option.
Note: If you use the copy function, you must change the information. The system will not accept duplicate field information.
Supported Additional Fields
You can specify the following fields from the Information column to map to fields in LEDES invoice files:
Supported Fields on the Invoice Detail Settings Page
|
Information Column |
LEDES1998BI Fields |
LEDES2000 Fields |
LEDES XML 2.0 Fields |
LEDES XML 2.1 Fields |
|---|---|---|---|---|
|
Account Type |
|
-- |
-- |
@matter.account_ type |
|
Client Address 1 |
|
@address_info.address_1 |
@cl_address.address_1 |
@cl_address.address_1 |
|
Client Address 2 |
|
@address_info.address_2 |
@cl_address.address_2 |
@cl_address.address_2 |
|
Client City |
|
@address_info.city |
@cl_address.city |
@cl_address.city |
|
Client Country |
|
@address_info.country |
@cl_address.coun try |
@cl_address.country |
|
Client Name |
|
@client.cl_name |
@client.cl_name |
@client.cl_name |
|
Client PostCode |
|
@address_info.zip_ postal_code |
@cl_address.zip_ postal_code |
@cl_address.zip_ postal_code |
|
Client State or Region |
|
@address_info.state_province |
@cl_address.state_province |
@cl_address.state_province |
|
Client Tax Id |
|
@client.cl_tax_id |
@client.cl_tax_id |
@client.cl_tax_id |
|
Entity Billed |
-- |
-- |
-- |
@invoice.bill_to_cl_name |
|
Final Invoices? |
-- |
-- |
@matter.matter_final_bill |
@matter.matter_final_bill |
|
Invoice Net Total |
|
-- |
-- |
-- |
|
Invoice Reported Tax Total |
|
-- |
@invoice.inv_total_tax_other_iso |
@invoice.inv_total_ tax_other_iso |
|
Invoice Tax Total |
|
-- |
@invoice.inv_total_tax |
@invoice.inv_total_ tax |
|
Law Firm Address 1 |
|
@address_info.address_1 |
@lf_address.address_1 |
@lf_address.address_1 |
|
Law Firm Address 2 |
|
@address_info.address_2 |
@lf_address.address_2 |
@lf_address.address_2 |
|
Law Firm City |
|
@address_info.city |
@lf_address.city |
@lf_address.city |
|
Law Firm Country |
|
@address_info.country |
@lf_address.count ry |
@lf_address.country |
|
Law Firm Name |
|
@firm.lf_name |
@firm.lf_name |
@firm.lf_name |
|
Law Firm PostCode |
|
@address_info.zip_ postal_code |
@lf_address.zip_postal_code |
@lf_address.zip_postal_code |
|
Law Firm State or Region |
|
@address_info.state_province |
@lf_address.state_province |
@lf_address.state_province |
|
Matter Name |
|
@matter.matter_name |
@matter.matter_name |
@matter.matter_name |
|
PO Number |
|
-- |
-- |
@matter.po_number |