> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ruloans.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Autonomous approval and logs documentation

**Autonomous Approval & Request Logs**

*Process Documentation*

Purpose: Document on autonomous payment configuration, approval request flow, and audit/request logs

# **1. Overview**

The Autonomous Approval flow allows a user to configure autonomous payment settings for a vendor/partner and submit the change for approval. The system records the request status and configuration changes in Autonomous Req Logs for audit and tracking.

# **2. Autonomous Payment Settings**

From the vendor/partner profile, the user opens the Autonomous Payment Settings option. The following information is entered or reviewed before submitting the change:

!\[]\[image1]

*Figure 1*

* Unsecured Payout – autonomous payout rate for unsecured cases.
* Secured Payout – autonomous payout rate for secured cases.
* Start Date – date from which the configuration is applicable.
* End Date (optional) – date until which the configuration remains applicable.
* Acknowledgement checkbox – confirms that changing the global autonomous settings will update the master payout autonomous configuration, including rate, ratio, and dates.

!\[]\[image2]

*Figure 2 – Autonomous Payment Settings*

# **3. Submit Configuration for Approval**

**1.** Enter/verify the Secured Payout and Unsecured Payout values.

**2.** Select the Start Date and, if required, the End Date.

**3.** Review the acknowledgement statement and select the checkbox.

**4.** Click Continue.

**5.** The system opens the Approval Required dialog because the action requires approval.

!\[]\[image3]

*Figure 3 – Approval Required dialog*

# **4. Approver Selection & Approval Request**

The Approval Required dialog displays the Autonomous Activation Request and asks the requester to select an approver who will review the request.

* Search for an approver by name or email.
* Select the required approver from the available users.
* Click Request Approval.
* The request is then submitted for review.

# **5. Request Status After Submission**

After the request is submitted, the vendor/partner profile can show an approval-pending state. In the recording, the status notification displayed is “APPROVAL\_PENDING”, indicating that the request has been raised and is awaiting the required approval.

!\[]\[image4]

*Figure 4 – Approval Pending status*

# **6. Autonomous Request Logs**

The Autonomous Req Logs tab provides the audit trail of autonomous activation requests. Each request is listed with its current status and the users involved in raising, approving/rejecting, and updating the request.

!\[]\[image5]

*Figure 5 – Autonomous Req Logs*

# **7. Log Fields**

| Field            | Description                                                           | Purpose                                |
| :--------------- | :-------------------------------------------------------------------- | :------------------------------------- |
| Action           | Type of autonomous request, shown as “Request Autonomous For Vendor”. | Identifies the action performed.       |
| Status           | Current state such as Pending, Approved, or Rejected.                 | Tracks approval outcome.               |
| Raised By        | User who initiated the request.                                       | Identifies the requester.              |
| Raised To        | User selected to review/approve the request.                          | Identifies the approver.               |
| Updated By       | User who last updated the request status.                             | Provides update/audit ownership.       |
| Secured Payout   | Old value → new value.                                                | Shows the payout configuration change. |
| Unsecured Payout | Old value → new value.                                                | Shows the payout configuration change. |
| Disb Date From   | Previous date → new date.                                             | Shows the effective date change.       |

# **8. Status Interpretation**

| Status   | Meaning                                                                            |
| :------- | :--------------------------------------------------------------------------------- |
| Pending  | Request has been raised and is awaiting approval/action.                           |
| Approved | Request has been approved by the assigned approver and the log records the update. |
| Rejected | Request has been rejected by the approver.                                         |

# **9. End-to-End Flow**

**1.** Open Vendor/Partner Profile

**2.** Open Autonomous Payment Settings

**3.** Enter/Update payout rates and applicable dates

**4.** Accept acknowledgement

**5.** Click Continue

**6.** Select Approver

**7.** Click Request Approval

**8.** Request moves to Approval Pending

**9.** Approver reviews request

**10.** Request is Approved / Rejected

**11.** Autonomous Req Logs retain the request and configuration change history

# **10. Audit & Tracking**

The Autonomous Req Logs provide traceability by retaining the request action, status, requester, approver, updater, payout value changes, and effective date changes. This enables the team to verify who initiated a configuration change, who was responsible for approval, what values changed, and the resulting approval status.

# **11. Approver Workflow – Autonomous Approval**

Once the requester submits the Autonomous Activation Request, the selected approver can review and approve the request from the Approval Center.

## **11.1 Open Approval Center**

**1.** Log in with the user account selected as the approver.

**2.** Navigate to Home → Approvals.

**3.** The Approval Center opens with the list of approval requests.

**4.** Use the Status filter and select Pending to view requests awaiting approval.

**5.** Open the Requests For Me tab to view requests assigned to the logged-in approver.

!\[]\[image6]

*Figure 6 – Approval Center with pending Autonomous Request*

## **11.2 Review the Autonomous Request**

The request card displays the request type, request number, submission time, requester, assigned approver, current status, and available actions.

* Request Type: Request Autonomous For Vendor.
* Request status: Pending.
* Requested By: user who raised the request.
* Approver: user currently logged in and responsible for approval.
* View Data Payload: expands the request payload so the approver can verify the submitted configuration values.
* Available actions: Reject and Approve.

!\[]\[image7]

*Figure 7 – Request details and data payload*

## **11.3 Verify Request Data**

Before approving, the approver should expand View Data Payload and verify the autonomous configuration submitted by the requester. The payload shown in the recording contains the DSA identifier, autonomous secured payout, autonomous unsecured payout, and global autonomous disbursement date range.

## **11.4 Approve the Request**

**1.** Click the green Approve button on the request card.

**2.** The Approve Request confirmation dialog opens.

**3.** The dialog displays the request reference and an Add remarks (optional) field.

**4.** Enter remarks if an approval comment is required. The remarks field is optional.

**5.** Click Confirm to complete the approval.

!\[]\[image8]

*Figure 8 – Approve Request confirmation dialog*

## **11.5 Approval Completion**

After the approver confirms the action, the pending request is removed from the Requests For Me list. The Approval Center displays an “All clear!” message with “No requests awaiting your approval,” confirming that there are no remaining pending requests for the approver.

!\[]\[image9]

*Figure 9 – Approval completed / no pending requests*

## **11.6 End-to-End Approval Flow**

**1.** Requester submits Autonomous Activation Request.

**2.** Selected approver receives the request in Approval Center.

**3.** Approver opens Home → Approvals.

**4.** Approver selects Pending and checks Requests For Me.

**5.** Approver reviews requester, approver, request status, and request details.

**6.** Approver expands View Data Payload and verifies the autonomous configuration.

**7.** Approver clicks Approve.

**8.** Approve Request dialog opens.

**9.** Approver optionally enters remarks.

**10.** Approver clicks Confirm.

**11.** Request is approved and removed from the pending approval list.

**12.** Approval Center shows All clear when no further approval requests are pending.

# **12. Complete Autonomous Approval Lifecycle**

| Stage         | Performed By | System / User Action                                                     |
| :------------ | :----------- | :----------------------------------------------------------------------- |
| Configuration | Requester    | Enter autonomous payout rates and applicable dates.                      |
| Submission    | Requester    | Continue → select approver → Request Approval.                           |
| Pending       | System       | Request status becomes Approval Pending.                                 |
| Review        | Approver     | Open Approval Center and review the request/payload.                     |
| Approval      | Approver     | Approve → optionally add remarks → Confirm.                              |
| Completion    | System       | Request is approved and no longer appears under pending approvals.       |
| Audit         | System       | Autonomous Req Logs retain the request and configuration change history. |

***

## **13. Approver Eligibility & Configuration**

### **13.1 Users Authorized to Raise Autonomous Approval Requests**

The ability to raise an Autonomous Approval request is directly available to the following roles:

* **CEO**
* **Lead Admin**
* **Business Head**

These users can raise the Autonomous Approval request directly without any additional configuration.

### **13.2 Configuring Other Users as Approvers**

Apart from **CEO, Lead Admin, and Business Head**, other users can be configured as approvers through **Global Configuration**.

To configure an additional approver:

1. Navigate to **Global Configuration**.
2. Locate the **specific configuration key used for Autonomous Approval approver mapping**.
3. Enter the **mobile number of the user** who needs to be configured as an approver in this key.
4. Save/update the configuration.
5. Once the mobile number is added, the corresponding user becomes eligible to be selected as an **Approver** for Autonomous Approval requests.

### **13.3 Complete Permission Flow**

**CEO / Lead Admin / Business Head** → Can directly raise the request.

**Other Users** → Their mobile number must be added in the designated **Global Configuration key** → User becomes eligible as an **Approver** → Can be selected during the Autonomous Approval request submission.

### **13.4 Automatic Approval for Configured Users**

In case the mobile number of a **CEO, Lead Admin, or Business Head** is added in the designated **Global Configuration key**, any Autonomous Approval request raised by that user will be **automatically approved by the system**.

* If the requester is a **CEO, Lead Admin, or Business Head** and their mobile number is configured in the Global Configuration key, the request does not require a separate manual approval.
* The system automatically approves the request after it is raised.
* This ensures that requests raised by specifically configured users can bypass the manual approval step.

### **13.5 Complete Permission & Approval Flow**

**CEO / Lead Admin / Business Head**\
→ Can directly raise the Autonomous Approval request.

**CEO / Lead Admin / Business Head whose mobile number is configured in Global Configuration**\
→ Raise request → **Automatically Approved**

**Other Users**\
→ Mobile number added in the designated Global Configuration key → User becomes eligible as an **Approver** → Can be selected during request submission → Approver manually reviews and approves/rejects the request.

***

**Prepared By:** Aparmita Srivastav