DemandFlow Support Centre

CLIENT: Client

ReferenceEntity Reference16/04/2026Updated 16/04/2026
A client organisation with an active or prospective commercial relationship, including contacts, billing, and ownership.

CLIENT: Client

A client organisation with an active or prospective commercial relationship, including contacts, billing, and ownership.

Default definition. This article describes the default CLIENT definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches CLIENT.

Entity properties

PropertyValue
Entity codeCLIENT
Display nameClient
PluralClients
Level11000
ExtendsCOM. See Entity Extension.

Use cases

CLIENT represents organisations the business has a direct commercial relationship with. It is structurally similar to COM (Company) but exists separately because CLIENT records carry additional billing, credit, legal entity, and ownership fields that are irrelevant to generic company records. COM is a broader universe of companies (prospects, research targets, market data) whereas CLIENT is reserved for organisations that have reached the stage of needing financial administration. Both link to PPL via comboKey for contacts, but CLIENT also links to VAC and PLACE for recruitment workflows.

Fields

Because this entity extends COM, some fields may actually be stored on the linked base record rather than on this record directly. See Entity Extension.

General: Basics

FieldTypeRequiredNotes
nametextYesName.
df_extendObjectreference → COMParent company.
isParentbooleanIs this a Parent account for other Client accounts?
parentClienttextParent client.
knownAstext (multi-line)Client known as.
primaryContactreference → PPLPrimary contact.

General: Primary address

FieldTypeRequiredNotes
pri_add_typeenumType. Valid ids: 1 (Bill to), 2 (Ship to), 3 (Primary), 4 (Other).
pri_add_nametextName.
pri_add_street1textStreet 1.
pri_add_street2textStreet 2.
pri_add_street3textStreet 3.
pri_add_citytextCity.
pri_add_countytextCounty.
pri_add_postcodetextPostcode.

General: Contact details

FieldTypeRequiredNotes
contact_main_phonetextMain phone number. Placeholder: Provide a telephone number.
contact_faxtextFax number.
contact_websitetext (URL)Website.
contact_careers_websitetext (URL)Dedicated careers / vancies webpage

General: Comments

FieldTypeRequiredNotes
comments_commenttext (multi-line)
roereference → ROERules of engagement.
credit_holdbooleanCredit hold.
email_structuretextEg. firstname.lastname@domain.com
sicreference → SICSIC.

General: Last contact

FieldTypeRequiredNotes
lc_lastcontacttextRead-only. Last contacted.
lc_lastcontactbytextRead-only. Last contacted by.
lc_lastcalltextRead-only. Last called.
lc_lastcallbytextRead-only. Last called by.
lc_lastemailtextRead-only. Last emailed.
lc_lastemailbytextRead-only. Last emailed by.

General: Client ownership

FieldTypeRequiredNotes
client_ownerreference → userClient owner.
client_keyownerreference → userKey account owner.
client_contractownerreference → userContract.
client_owner_preference → userPermanent.
client_owner_treference → userTemporary.

Company information

FieldTypeRequiredNotes
indreference → INDIndustry.
ownreference → COMPOWNCompany ownership.
revenuenumberAnnual revenue.
tickertextCompany ticker.
empcountnumberNumber of employees.
origLeadreference → PPLOriginating lead.

Company information: Client audit history

FieldTypeRequiredNotes
createddatetimeRead-only. Created on.
ownerIdreference → userRead-only. Created by.
updateddatetimeRead-only. Updated on.
updatedIdreference → userRead-only. Updated by.

Company information: Description

FieldTypeRequiredNotes
descriptiontext (multi-line)

Administration: Billing information

FieldTypeRequiredNotes
creditHoldbooleanCredit hold.
checkedByreference → userChecked by.
accountsContactreference → PPLAccounts contact.
creditLimitnumberCredit limit.
creditDatedateCredit check date.
currencyreference → CURRENCYCurrency.
cratereference → CRATECredit rating.
accountreftextFinance account ref.
lentityreference → LENTITYLegal entity.
timesheetsbooleanCreate timesheets.
taxcodereference → TAXCODETax code.
taxcodereference → INVINSTRInvoice instructions.

Administration: Internal information

FieldTypeRequiredNotes
regnumbertextReg. number.
vatnumbertextVAT number.
clienttypereference → CLIENTTYPEClient type.
countryregreference → COUNTRYRegistration country.
countrytradereference → COUNTRYTrading country.
selfbillbooleanSelf bill.

Administration: Additional information

FieldTypeRequiredNotes
add1text (multi-line)Additional information 1.
add2text (multi-line)Additional information 2.
add3text (multi-line)Additional information 3.

Administration: Email restrictions

FieldTypeRequiredNotes
emaillimitreference → EMAILLIMITEmail limit definition.

Administration: Dimensions

FieldTypeRequiredNotes
repbureference → REPBUReporting BU.
clientpjreference → CLIENTPJClient project.

Administration: Off limits

FieldTypeRequiredNotes
offlimitsreference → OFFLIMITOff limits reason.
offdatedateOff limits expiry date.
offdesctext (multi-line)Off limits description.

Relationships

  • Lookups: df_extendObject points at a COM record; primaryContact points at a PPL record; roe points at a ROE record; sic points at a SIC record; ind points at a IND record; own points at a COMPOWN record; origLead points at a PPL record; accountsContact points at a PPL record; currency points at a CURRENCY record; crate points at a CRATE record; lentity points at a LENTITY record; taxcode points at a TAXCODE record; taxcode points at a INVINSTR record; clienttype points at a CLIENTTYPE record; countryreg points at a COUNTRY record; countrytrade points at a COUNTRY record; emaillimit points at a EMAILLIMIT record; repbu points at a REPBU record; clientpj points at a CLIENTPJ record; offlimits points at a OFFLIMIT record.
  • Extends: this entity extends COM. See Entity Extension.
  • Related lists: PPL (format SUB|CLIENT|PPL), VAC, PLACE.
  • Activity: activity timeline panel attached.

Creating a Client via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "CLIENT",
  "level":    11000,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Name",
  "description": "Example",
  "parentClient": "Parent client",
  "knownAs": "Client known as"
}

Listing Clients records

GET /v1/entities/CLIENT/SUB

See also

clientclientscom

Was this article helpful?

← Back to Knowledge Base