Feature Request would be to add an option to have this count reset each time the session is closed. This count is useless if it doesn't reset for each batch.

Counting the documents in each batch. Combining a batch # and a doc # would make each document unique. This is typical behavior for entities that do batch scanning. Each time the session is closed the doc count should reset. Opening the session again would create a new batch. 

This particular entity scans hourly and names their batches with the date and hour then each document should be counted starting with 1 not a continued count infinitely. Expecting the scan clerks to navigate to this setting and reset it each time is not ideal.

I encountered this use case before as well and thought it would be an easy fix - it was not possible. 

My journey allowed me to discover that this value is stored as <Count>160</Count> in the session .qfx file which is essentially and XML formatted file.  XML nodes values can be easily altered via automation using PowerShell for example.  Unfortunately simply changing this value prior to opening the session in QuickFields does not work.  Several other XML nodes are updated when QuickFields saves a session regardless of any changes made.  These include XML nodes like <security bits>, <ProfileId>, <CipherValue> and <ParentKey>.  If you open an .qfx file, change nothing, and save it these nodes are updated and ensure the integrity of the session which is good but bad for externally modifying the file.  That is where my investigation stopped as those would require more intimate knowledge of Laserfiche algorithms that calculate those node vaues.  

Sorry that doesn't help you in your quest for a solution but I found the adventure interesting enough to share.