Kimble API

Background to Kimble PSA

Kimble is a Professional Services Automation (PSA) solution which can handle the modelling and definition of customer engagements, resource management, project & delivery management, time, expenses, procurement of external services, customer invoicing, sales and project forecasting, and operational analysis and reporting.

The Kimble application is a managed package on the Salesforce Force.com cloud platform. Kimble’s customers have their own Salesforce org into which they install Kimble alongside other Salesforce applications such as Sales Cloud and other Salesforce platform or off-platform customer applications such as SAP Finance or Workday HR.

It is typical for Kimble to exist in an ecosystem of external applications with which it needs to exchange data in order to support end-to-end business processes which span these applications. Examples include the onboarding and update of employee information which will typically take place in an HR application and require flows of employee data into Kimble so they can become resources that can be assigned to engagements as well as submit time and expenses; or the flow of invoice / credit note or expense information which originates in Kimble and needs to impact the customer’s financial accounts, so needs to flow into their finance application.

While there are typical flows illustrated below, Kimble allows the flexibility for customers to conduct parts of the business processes Kimble could support in other external applications, for example in circumstances where these applications are already incumbent or where some business units are transitioning to using Kimble (e.g. time entry which can take place outside Kimble but needs to flow into Kimble for invoicing purposes).

Kimble customers can also have very specific interface requirements which require Kimble to provide generic mechanisms for interfacing which can be configured according to customer requirements.

Kimble includes an Interfacing Framework which can be used to configure variations of the typical flows we see in customers but also configure specific interfaces for customers based on their unique requirements. The Kimble Interface Framework exposes both file import and export interfaces as well as RESTful APIs exchanging JSON formatted message bodies.

Business Use Cases

The business use cases below cover the scope of the interfaces included in the Kimble MuleSoft Connector.

Get Invoices / Credit Notes

Gathering dispatched invoices to be inserted into an Accounts Receivable ledger within a Finance application.

Get Expense Items

Gathering approved expense items to be inserted into an Accounts Payable ledger within a Finance application.

Get Project Details

Gathering project details to be synchronized with another application which is handling aspects of a delivery engagement process such as time entry.

Get Generic

Allowing for the request to a custom configured interface to gather data to specific customer requirements.

Create Expenses

Inserting Expense Items originating from an Expense application such as SAP Concur, so they be accounted for against projects in Kimble and form part of Invoices.

Create Invoice Payments

Inserting details of the Payments recorded against Invoices in a Finance Application which originated in Kimble, so the payment status of Invoices related to a Project is visible to delivery managers.

Create Resource

Inserting or updating details of Employees originating from a HR application into Kimble so those resources can be subject to project assignments, time recording etc.

Create Time Entry

Inserting details of Time Entries originating from a Time Entry application, so they can be accounted for against projects in Kimble and form part of Invoices.

Create Generic

Allowing for the request to a custom configured interface to insert data to specific customer requirements e.g. employee planned absences from an HR application based on Sales Opportunities originating in a CRM Sales Application.