How we read your documents

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.

Dropping it in

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.

Checking what we read

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.

The date appears

Confirm, and the duty turns valid — here, and on the portfolio Compliance page — with the expiry showing and the days remaining counting down.

One document, two duties

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.

If a document does not read cleanly

• Uploaded a while ago and it never turned green? Look for an amber prompt above the duties — a file we could not classify waits there for you to name its type.
• A date read wrongly? Open the duty and correct it. The date matters more than the file, so fix the date even if the file is fine.
• Expired but still green? Reaching the expiry date is the one change caught overnight, not instantly, so allow a day.