The diary gathers details from two sources: AR events that have been created but are not yet marked as "Completed" or "Lodged with CRO," and the Next ARD listed on the General2 tab of the company profile for cases where the event has not yet been created.
On the General2 tab, the Previous ARD refers to the last AR event created in the system, regardless of whether it is in progress or closed. Therefore, the Next ARD should be the date following the last created or completed ARD. When a B1 event is created, this date automatically rolls forward to the next year, which should trigger an alert to create the event.
If the Next ARD on the company's General2 screen is manually adjusted to match an existing AR event date, the diary becomes confused. It will report the company's Next ARD along with the status of the event on the same date. This practice should be avoided, as it prevents the diary from accurately tracking the next ARD, potentially leading to missed ARDs and resulting in penalties and loss of audit exemption.
This issue can cause some companies to appear twice in the AR Diary or to appear even if the AR has been received and registered with CRO. To correct these inconsistencies, ensure that all registered events are marked as completed and that the Previous ARD on the General2 tab accurately reflects the most recent AR event.