NetDocuments: What Data Fields Do You Sync?

NetDocuments: What Data Fields Do You Sync?



Introduction

In this article, we explore the data fields shared between Matters.Cloud and NetDocuments during integration. Understanding which fields are included is essential for ensuring seamless data synchronisation and a streamlined workflow.

By knowing which information is exchanged between these two platforms, you'll be better equipped to set up, troubleshoot, and optimise the integration for your firm's needs. This guide covers the key fields involved in the integration, offering clarity on how client, matter, invoice and financial data flows from Matters.Cloud to NetDocuments and vice versa.

Data Fields: Clients

Clients are published from Matters.Cloud to NetDocuments both when they're first created and whenever updates are made.




client.client_code
client.client_key
client.name
(contact = first name + last name, organization = name)
client.client_description
client.inactive_date
client.close_date

Notes:

The integration between Matters.Cloud and NetDocuments uses the workspace attribute for the selected cabinet to determine the appropriate attributes to populate as part of the integration. If the workspace attribute defined on the cabinet is a child attribute, Matters.Cloud will automatically populate the parent attribute with the appropriate client information defined above.

The example given above uses an example naming convention where the parent attribute is called 'Client', this will automatically change if the installation of NetDocuments uses an alternative naming convention for the parent attribute. (for example Business Unit would be Business Unit Key, Business Unit Description and Close Date


Data Fields: Matters

Matters are published from Matters.Cloud to NetDocuments both when they're first created and whenever updates are made.




matter.matter_code
matter.matter_key
matter.name
matter.matter_name
matter.type.description
matter.type
matter.close_date
matter.close_date


Notes:

The integration between Matters.Cloud and NetDocuments uses the workspace attribute for the selected cabinet to determine the appropriate attributes to populate as part of the integration. If the workspace attribute defined on the cabinet does not have a parent attribute, Matters.Cloud will only populate the workspace attribute with the Matter information defined above.

The example given above uses an example naming convention where the workspace attribute is called 'Matter', this will automatically change if the configuration of NetDocuments uses an alternative naming convention for the workspace attribute. (for example Project would be Project Key, Project Description, Type and Close Date
(none)

    • Related Articles

    • FreeAgent: What Data Fields Do You Sync?

      Overview The following data is included within the integration: Data Fields: Clients The following data is exported to FreeAgent: Contact / Organization contact.first_name contact contact.first_name contact.last_name contact contact.last_name ...

    • Xero: What Fields Do You Sync?

      Introduction In this article, we explore the data fields shared between Matters.Cloud and Xero during integration. Understanding which fields are included is essential for ensuring seamless data synchronisation, accurate reporting, and a streamlined ...

    • FreeAgent: How Often Does The Data Sync Occur?

      Overview Once the you have enabled the integration between Matters.Cloud and FreeAgent the following schedule will apply: Process Frequency Export Clients from Matters.Cloud to FreeAgent Real Time Export Matters from Matters.Cloud to FreeAgent Real ...

    • Document Automation: Merge Fields

      Overview The following section uses the notation«=client.name»to refer to Word MailMerge fields which are available to be included as part of templates uploaded to Matters.Cloud Fields: Document The following merge fields are available for the ...

    • FreeAgent: Setting Up Your Initial Data

      Overview There are two options when setting up your initial integration with FreeAgent: Import existing Projects from FreeAgent into Matters.Cloud . Export existing Clients & Matters from Matters.Cloud to FreeAgent. Option 1: Import From FreeAgent If ...