Every customer and partner relationship in KEBS follows the same lifecycle: create the account with clean foundation data, modify it as ownership and commercial terms evolve, and deactivate it when the engagement ends — all without losing historical records.
The full lifecycle of an account in 3 actions:
Adding an Account
Every new customer or partner engagement starts with creating an account. Getting it right — the correct persona, legal entity, business unit, and owner — ensures that every downstream record (projects, invoices, timesheets) is accurately attributed from the outset.
A complete, well-structured account record eliminates data gaps that cause billing errors, misattributed revenue, and reporting blind spots. Finance raises invoices on the right entity, delivery assigns the right team, and leadership tracks account health — all without chasing the Account Manager for missing info.
How to create an account
- 1Click the global + Create button in the top navigation bar.
- 2Select Account from the dropdown menu.
- 3The Create Account form opens in a side panel.
- 4Fill in all required fields (marked in the reference below) and any relevant optional fields.
- 5Click Save. The account is created and opens immediately in the Account detail view.
Unlike BigTime PSA (which treats every entity as a generic “Client”) and Kantata (where Account is a lightweight wrapper over Salesforce), KEBS bakes persona (Customer vs. Partner), legal-entity binding, and strategic-tier semantics directly into the record — so downstream workflows (invoicing, resource allocation, forecasting) don’t need custom fields or automations to behave correctly.
Field Reference
| Field | Description |
|---|---|
| Account Name Required | The full legal or trading name of the customer or partner. Appears on all invoices and reports. |
| Customer Code Required | Unique short code for the account (e.g. NXGD). Used for project codes, invoice references, and financial identifiers. |
| Persona Required | Customer (revenue-generating) or Partner (collaborative/reseller). Determines downstream list behavior. |
| Legal Entity Required | Your organization’s legal entity contracted with this account (e.g. India entity, UK entity, North America entity). |
| Business Unit Required | The internal BU or practice responsible for this account. |
| Account Owner Required | The primary Account Manager responsible for the relationship. |
| Region Optional | Geographic region — used for segmentation and regional reporting. |
| Strategic Account Tier Optional | Platinum / Gold / Silver / Bronze — flags strategic priority; unlocks tier-specific workflows. |
| Parent Account Optional | Link a subsidiary to its parent for consolidated hierarchy reporting. |
| External Reference ID Optional | ID from an external CRM or ERP — enables cross-system reconciliation. |
| Industry Optional | Customer’s industry vertical — used for segmentation and portfolio analysis. |
| Website Optional | Customer’s primary website URL — surfaced on the Account Overview tab. |
| Annual Revenue Optional | Customer’s reported annual revenue — used for segmentation and opportunity-sizing. |
| Employee Count Optional | Rough company size indicator — feeds KAIS account-scoring model. |
Modifying an Account
Account records need to be updated when circumstances change: a new Account Manager takes over, the customer upgrades their strategic tier, they restructure under a new legal entity, or basic contact details change. Keeping records accurate ensures that invoices, reports, and stakeholder communications reflect reality.
Accurate, up-to-date account records mean finance raises invoices to the right entity, reports reflect the correct owner, and there is no confusion about who is responsible for the relationship. Stale account data is one of the most common causes of billing disputes and reporting inaccuracies in professional services firms.
- 1Go to Accounts in the left navigation.
- 2Find the account in the list. Hover over the row to reveal the action icons.
- 3Click the pencil (edit) icon in the Actions column.
- 4The Edit Account form opens in a side panel. Update the required fields.
- 5Click Save.
- 1Open the Account detail view.
- 2Click the ⋮ menu (three-dot menu) at the top-right of the Account Info section.
- 3Select Edit account from the dropdown.
- 4The Edit Account form opens. Make your changes.
- 5Click Save.
Deactivating an Account
KEBS does not permanently delete accounts — instead, accounts are deactivated. A deactivated account is hidden from active lists and cannot be selected for new projects or invoices, but its full history (projects, invoices, agreements, notes, audit log) is preserved and remains accessible for compliance reviews.
Deactivating rather than deleting ensures full historical data integrity — past revenue, project records, and agreements are never lost. Finance and leadership can still run historical reports on deactivated accounts. At the same time, the active accounts list stays clean and focused on live relationships.
How to deactivate an account
- 1Open the Account detail view for the account you want to deactivate.
- 2Click the ⋮ menu at the top-right of the Account Info section.
- 3Select Deactivate account from the dropdown.
- 4Confirm the deactivation in the prompt that appears.
- 5The account is removed from active lists immediately. Its status changes to Inactive.
Governance & Audit
Every change to an account — field updates, ownership transfers, tier changes, deactivations — is recorded in the Audit Log tab of the account’s detail view. Each entry captures who made the change, what changed (old vs. new value), and when it happened (timestamp in UTC and user’s local time).
Finance, Legal, and Compliance teams get a defensible, verifiable history of every customer record — essential for audits, regulatory reviews, and dispute resolution. No more “who changed this and when?” email trails.
- Field-level diff: Each entry shows the old value → new value for every modified field.
- User attribution: Every change is tied to the authenticated user (and SSO session, if Azure AD / Okta is integrated).
- Timestamped: Precise to the second, in both UTC and user local time.
- Immutable: Audit entries cannot be edited or deleted by any user — even Administrators.
- Exportable: Export the log to CSV or PDF for external auditors.



