What happens between dropping a certificate in and a date appearing against a duty.
When you add a certificate, Abodient reads the dates off it so you do not have to type them. Here is what happens between dropping the file in and the duty turning green.
Drop a file onto the zone above, or use the Upload on a specific duty's row.
Uploading against a duty tells us the type already, so we go straight to reading it.
Drop a file in generally and we work out the type first: if we are confident we carry on, and if we are not, we store it and ask you.
While it reads, the row shows Extracting…. A certificate takes around twenty seconds.
What we read is a proposal, not a decision. A box shows the dates we found, and nothing on the property changes until you confirm them.
Check the expiry date especially — it is the date that drives your reminders.
Confirm, and the duty turns valid — here, and on the portfolio Compliance page — with the expiry showing and the days remaining counting down.
You can save a certificate whose expiry date is in the past. Leave the real date in the box. It says "That date has passed — this will be saved and shown as Expired."
Press Save, and the duty reads Expired, with how many days overdue it is. That is the true position, and it keeps the duty on your list until the renewal arrives.
Do not type a future date to make the row green. Your reminders and the exposure figure would then be wrong.
An expired certificate is never confirmed along with others in one go. It opens on its own screen so you see it.
Sometimes one certificate covers two duties. We never assume that. You tell us, by ticking "this also covers…" when you confirm, or by uploading the same file against the second duty.
