In Daylite and Billings, clients are treated as individuals. In reality, a client maybe a body corporate or a natural person. In some cases, individuals in a partnership may be regarded as a 'client' for billing and trust administration purposes.

Two critical problems emerge in connection with the above.

1. Merging is performed in external applications in relation to a 'client' being a natural person, meaning that an individual has to be selected for the merge to occur. If your client is a corporate entity or partnership, you need to create or select a single natural person, who will act as the conduit.

2. Billings cannot import organisations from Daylite, which means only natural persons may selected as client (with link to DL object).

Can I have anyone's thoughts or solutions?

Thanks

This message has been edited. Last edited by: Tim Jacka,

This isn't entirely accurate. Daylite's architecture makes logical sense because a company is not a person, and should therefore not be represented by a field in the contact's profile. A company is its own entity and, as you mentioned, can also be a client.

In Daylite people and companies (called contacts and organizations) are stored separately, as different objects in the database. We then provide the user with the ability to categorize its contacts and its organization records as clients.

I agree with you that there is a weakness here where Daylite considers only the contact record eligible for merging. That's not to say that you can't access the organization details, because you can. But you NEED to specify a contact for the actual merge.

Initially the thought was that you would always be communicating, or writing to, a person at an organization rather then simply sending a letter to the organization itself. But now we see that our users want to merge directly with organizations, and this has been added to the list of feature requests.

As you've stated, Billings also suffers from this in a different way. Also something we've noted for the engineering team.