# Data Upload

The Data Upload section in Udara360 enables you to perform various batch operations and bulk uploads for different banking functions. This feature is designed to handle large-scale data uploads efficiently, allowing you to process multiple records simultaneously through a standardized `.xlsx` file format.

### Types of Data Uploads

Here are all the available data upload options in Udara360 with their specific requirements and conditions:

<table><thead><tr><th width="229">Upload Type</th><th>Description</th><th>Special Conditions</th></tr></thead><tbody><tr><td>Batch Account Creation</td><td>Allows you to create multiple accounts simultaneously</td><td></td></tr><tr><td>Batch Acct Officer Reassign</td><td>Enables bulk reassignment of accounts to different officers</td><td><ul><li>Both current and new officer IDs must exist in the system.</li><li>Requires active account numbers. </li><li>You must select an active account officer before batch-assigning an officer.</li></ul></td></tr><tr><td>Batch Backdating Posting</td><td>Facilitates backdated transactions for multiple accounts</td><td><ul><li>Financial date must be within the set backdating period</li><li>Must include transaction narrative</li></ul></td></tr><tr><td>Batch Individual Customer</td><td>Handles bulk creation of individual customer profiles</td><td><br></td></tr><tr><td>Batch Loan Creation</td><td>Processes multiple loan account creations</td><td>- Customer must have active savings account<br>- Loan officer ID must be valid<br>- Requires credit score information</td></tr><tr><td>Batch Loan Disburse</td><td>Manages bulk loan disbursements</td><td>- Loan accounts must be approved<br>- Disbursement account must be active<br>- Requires disbursement approval</td></tr><tr><td>Batch Loan Termination</td><td>Processes multiple loan terminations</td><td>- Loan account must be active<br>- Requires termination reason code<br>- Settlement account must be specified</td></tr><tr><td>Batch Upload Posting Tracer</td><td>Tracks and traces batch upload transactions</td><td>- Transaction reference numbers required<br>- Date range must be specified<br>- Batch number must be valid</td></tr><tr><td>GL/Customer Upload Post</td><td>Handles bulk postings to GL or customer accounts</td><td>- GL accounts must be active<br>- Transaction codes must be valid<br>- Balanced debit and credit entries required</td></tr></tbody></table>

### Upload Process

The basic upload process remains consistent across all types:

1. Navigate to the desired upload type from the left sidebar menu
2. You can either:
   * Click "Browse" to select your file
   * Drag and drop your file directly into the designated area
3. Ensure your file is in `.xlsx` format

{% hint style="info" %}
You can download the Upload type template using the "Download Batch Upload Format" button.
{% endhint %}

### Things To Note

#### Pre-Upload Checks

* [ ] Verify that all mandatory fields are filled correctly
* [ ] Ensure all referenced IDs (Customer, Account, Officer) exist in the system
* [ ] Validate that the data follows the specified format in the template

#### Post-Upload Verification

* [ ] Check the upload status in the Batch Upload Posting Tracer
* [ ] Verify successful processing of all records
* [ ] Review any error logs for failed entries

#### Important Notes:

* Each upload type has its specific template format
* The system performs validation checks before processing the upload
* Failed records will be logged with specific error messages
* Always maintain a backup of your uploaded file
* The current financial date displayed will be used as the processing date unless specified otherwise in the template.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.udara360.io/core-features/data-upload.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.