# Feature Request: Option for Date Field to Default to Last Used Date Instead of Today

**URL:** <https://forum.manager.io/t/feature-request-option-for-date-field-to-default-to-last-used-date-instead-of-today/67237>\
**Category:** Uncategorized\
**Created:** [March 7, 2026, 2:49am UTC](https://forum.manager.io/t/feature-request-option-for-date-field-to-default-to-last-used-date-instead-of-today/67237 "2026-03-07T02:49:08Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Wallis](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/michael_wallis/32/53246_2.png) [@Michael\_Wallis](https://forum.manager.io/u/Michael_Wallis)\
**Post date:** [March 7, 2026, 2:49am UTC](https://forum.manager.io/t/feature-request-option-for-date-field-to-default-to-last-used-date-instead-of-today/67237/1 "2026-03-07T02:49:08Z")

</div>

Hello,

I would like to request a feature that allows the **date field to default to the last used date** , rather than always defaulting to **today’s date**. Ideally this would be a **configurable option in Settings** , so users could choose between:

- Default to **today’s date** (current behaviour)

- Default to **last used date**

### Why this would be useful

**1. Batch data entry efficiency**

Many users enter transactions **in batches** , often working through a stack of documents from the same day (for example invoices, receipts, or bank transactions).  
If the system always defaults to today’s date, the user must manually change the date **for every entry** , which slows down data entry and increases repetitive work.

If the date defaulted to the **last entered date** , users could process a batch quickly without repeatedly correcting the date.

**2. Reduces data entry errors**

When entering historical transactions (for example catching up on bookkeeping for prior days or weeks), it is easy to accidentally leave the default **today’s date** , which creates incorrect transaction records.

Using the **last used date** as the default reduces the risk of this mistake.

**3. Aligns with typical bookkeeping workflows**

Many accounting systems use one of these approaches:

- remember the **last used date**

- remember the **session date**

- allow a **user-configurable default date behaviour**

These approaches better support real-world bookkeeping workflows where work is often done **chronologically rather than in real time**.

**4. Particularly useful for manual bookkeeping**

Manager is often used by small businesses doing manual entry rather than importing data automatically. In these workflows the user frequently enters **multiple transactions for the same date** , so remembering the previous date would significantly improve usability.

### Suggested implementation

A simple approach could be:

**Settings → User Preferences → Default transaction date**

Options:

- Today’s date (current default)

- Last used date

Alternatively, Manager could automatically remember the last date used during the session.

### Summary

Allowing the date field to default to the **last used date** would:

- speed up batch entry

- reduce mistakes when entering historical transactions

- better support real bookkeeping workflows

Thank you for considering the suggestion.