Hi Ivan,
Thanks but I understand what LPCD is and why the timer is used - it polls by using LPCD mode and then goes back to standby again.
What would save even more power is that the LPCD keeps on running in the background while the main processor is in standby and on detection of a Tag, the LPCD component interrupts the processor to wake it up like it does with devices like CLRC663:

We have now spend plenty of time to reduce current consumption and this is the lowest figures that we have got:
With 1 second polling interval (that timer you mentioned):
Overall average current is 90uA.
75uA of this current is taken by the processor (cycling between standby and waking up every second)
13uA is taken by RF/LPCD (TVDD)
2uA is drawn by P_VDD
With 0.35 second polling interval which is what we need (that timer you mentioned):
Overall average current is 200uA.
175uA of this current is taken by the processor (cycling between standby and waking up every second)
13uA is taken by RF/LPCD (TVDD)
2uA is drawn by P_VDD
As you can see that the bulk of the consumption is the processor waking up, manually initiating the LPCD and manually checking LPCD status. Is it not possible with PN7462 or are we doing something wrong in the firmware?

For the project that we are working on, we expect to produce about 10k devices by end of Sep. If we can't use the LPCD the way it is supposed to be used then we will have to move away from PN7462.
Thanks