> For the complete documentation index, see [llms.txt](https://docs.biscit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biscit.com/ekr-user-guide/epicor-kinetic-rentals-ekr.md).

# Epicor Kinetic Rentals (EKR)

**Epicor Kinetic Rentals (EKR)** brings equipment rental capability to the **Epicor Kinetic** platform. This is achieved using a seamless embedded strategy, which means there is no syncing or integration required between **EKR** and **Kinetic**. **EKR** leverages the same Kinetic database and existing Kinetic modules, including but not limited to **Customer**, **Account Receivables** and **Maintenance Management**.

{% columns %}
{% column %}

### Key features

**EKR** includes the following functionalities:

* Visibility of your bookings on a timeline
* Ability to create rental bookings grouped under agreements
* Ability to manage the logistics of the bookings with on and off-hire management
* Ability to streamline maintenance job creation when sending or receiving equipment
* Ability to create proposals that can serve as quotes to your customers without affecting equipment availability, while still making it visible in the visibility dashboard
* Streamline invoice generation

All the above is real-time connected to the Kinetic backend and allows the use of standard reporting.

{% endcolumn %}

{% column %}
The EKR Lifecycle from Proposal to Payment:

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FcSjE6bfirIfQaQXAvuSy%2Fimage.png?alt=media&amp;token=8ecc7d82-7499-474b-967c-28c77d2d0b52" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Value of adding EKR to your process

At **BISCIT**, we believe that by introducing **EKR** to your Kinetic Ecosystem, you can gain the following advantages:

* Maximise the utilisation of your rentable equipment
* Complete visibility of assets across the rental lifecycle
* Enable proactive action to reduce the risk of lost revenue and lost equipment
* By leveraging the existing strength of Kinetic, like customers, equipment and maintenance templates, it fits in well with your existing solution design without needless duplication of systems
* Reduced the operational burden of running a separate system and maintaining an integration

### High-Level **EKR** Process Flow

#### High-level flow of an Agreement through **EKR**

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FERvzq4BaKPtYA1TsvMEQ%2Fimage.png?alt=media&amp;token=1296553a-a085-4a49-93a5-56fc4f74d307" alt=""><figcaption></figcaption></figure>

#### Without Category-level bookings

1. A proposal is created in EKR where equipment and charges are added with initial hire periods to show the costs.
2. The proposal can then be converted to an agreement (WON), or you can create the agreement from the start with the same format as the proposal.
3. Each equipment line on the agreement represents a booking, and during these bookings, can be progressed through the logistics journey of being sent out, returned, etc. via the logistics dashboard in EKR.
4. During the lifetime of an agreement, invoices are generated periodically as per the agreement setup. Lined (equipment bookings) and charges can be added to the agreement during the lifecycle.
5. At the end of the agreement, when all equipment has been returned and booking lines are closed, the agreement is considered complete.

{% hint style="info" %}
**NOTE:** Until the booking is "SENT", a specific piece of equipment assigned is not required to the Agreement. Instead, add booking lines by equipment category. Configure default pricing at the equipment category level to help the agreement give cost estimates. The logistic dashboard will require to select the actual piece of equipment before sending it to the customer.
{% endhint %}

#### Scenario: Categories are used instead of specific Equipment

<figure><img src="https://3143154457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFuMjREj8WHcxhf8dRWZN%2Fuploads%2FDjqM6c1Db1B74ldqLmZg%2Fimage.png?alt=media&amp;token=9949ae2a-1884-41af-aff6-2eaee8cd521a" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.biscit.com/ekr-user-guide/epicor-kinetic-rentals-ekr.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
