> For the complete documentation index, see [llms.txt](https://docs.udara360.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.udara360.io/core-features/data-upload/batch-backdating-posting.md).

# Batch Backdating Posting

The Batch Backdating Posting page allows you to post transactions against a past financial date by uploading a pre-formatted spreadsheet file. This is used when transactions need to be recorded against an earlier date than the current financial date; for example, to correct or complete postings that should have been processed on a previous date. This guide will walk you through the batch backdating posting process.

## Accessing Batch Backdating Posting

1. Log into the application using your credentials.
2. From the dashboard, navigate to **Data Upload** in the side menu.
3. Expand **Data Upload** and Select **Batch Backdating Posting**  from the dropdown list

## Processing Backdated Postings in Bulk

1. Click **Download Batch Backdating Posting Format** to download the pre-formatted spreadsheet template
2. Populate the template with your transaction data and save the file in [**.xlsx**](/core-features/data-upload/batch-backdating-posting.md#processing-backdated-postings-in-bulk) **format**
3. Click **Browse** or **drag and drop** the completed file into the upload area
4. Enter the **Financial Date**, this is the past date the transactions will be posted against
5. Toggle **Enable Preview** to review the file contents before submission if required
6. Click **Upload** to submit the file and process the backdated postings

<figure><img src="https://4148303057-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJO1GSxhJIrS0metPeFt%2Fuploads%2FquE5IxgHXDvlg8lrGIJ2%2Fimage.png?alt=media&amp;token=90c76ee2-83a3-4f5c-ba87-de87cded9ffd" alt=""><figcaption></figcaption></figure>

> :pushpin:The Financial Date must fall within the permitted backdating period configured in your system settings. Each transaction in the file must include a transaction narrative.