An expired contract rarely warns you in advance. You discover it when a shipment is stuck at customs, an inspector asks for paperwork, or the bank refuses a payment on a lapsed agreement. In most small and mid-sized businesses, contract deadline tracking works the same way: a spreadsheet someone filled in six months ago, plus the memory of one particular employee. As long as that person is around and the sheet is current, the system appears to work. But let one person take a vacation and the other file go stale, and the company meets its next expired deadline after the fact — with a fine, downtime, or a blown shipment. In this article, we break down how the HORUVIA deadline engine works: a single registry of dates across every document in the company, plus Telegram alerts at 60, 30, and 7 days before each date. And most importantly, how documents land in that registry from email and scans instead of being keyed in by hand.
Why a deadline always seems to expire "out of nowhere"
The first reason is that dates live inside documents, not out in the open. A contract's expiry date sits on page five of a PDF, a certificate's validity is printed in the corner of a scan, and an insurance end date is buried in a broker's email from three months ago. To keep those dates under control, someone has to open each document regularly and copy the dates into a spreadsheet. In practice this happens exactly once — at signing. After that the sheet ages, and new documents make it in only every other time.
The second reason is blurred ownership. A manager handles contracts, a logistics person handles certificates, accounting handles insurance. Nobody holds the full picture, and the question "what expires in the next two months?" turns into a round of calls across three departments.
The third reason is that deadlines expire quietly. A contract doesn't send a notice that it ends in a month. If a system doesn't remind you of the date, the date reminds you itself — already in the form of a problem: a halted shipment, rejected paperwork, an awkward conversation with an auditor.
How contract deadline tracking usually works — and where it breaks
The typical toolkit looks like this: a spreadsheet of deadlines, calendar reminders on one or two employees' accounts, and a verbal agreement that "everyone watches their own patch." Each piece has a predictable point of failure.
- The spreadsheet stays current only as long as someone keeps filling it in. A new contract signed during peak season often never makes it into the sheet.
- The calendar is tied to a person. When that employee leaves or switches accounts, the reminders leave with them.
- Memory works well for frequent documents and fails on rare ones: insurance renews once a year, and that's exactly the kind of deadline that's easiest to miss.
The shared weakness across all three is manual entry. A date has to be found in the document, read correctly, and copied into the spreadsheet without a typo. Every step is a chance for error, and a wrong date is worse than a missing one: the spreadsheet shows "all clear" when the clear has already run out.
One deadline registry instead of scattered spreadsheets
The HORUVIA deadline engine is built on a simple principle: every date in the company lives in one registry, regardless of document type. The registry takes in:
- supplier and customer contracts — expiry dates and auto-renewal terms;
- customs declarations and permits;
- insurance policies — cargo, liability, property;
- conformity and origin certificates with their validity periods;
- employee health permits — for food service and manufacturing;
- shelf-life dates on product batches.
Each entry is a document, a counterparty, and a date. The registry answers "what expires and when" across the whole company at once, not one department at a time. You don't need to remember which spreadsheet holds insurance and which holds certificates: the horizon of the coming months shows up as a single list, sorted by date. Alongside it runs a kanban task board: when a deadline calls for action — request a new version of a contract, order a policy renewal — the task is created right there and doesn't dissolve into email threads.
60/30/7 alerts: a contract renewal reminder that's hard to miss
A registry without reminders is just a tidier spreadsheet. So the second half of the mechanism is a ladder of Telegram alerts at 60, 30, and 7 days before each date. The intervals are chosen to match different depths of response.
At 60 days, the first contract renewal reminder arrives — time to calmly renegotiate terms, request a new draft, and compare offers from other counterparties. At 30 days comes the working checkpoint: it's time to request documents, because issuing a new certificate or policy takes weeks. At 7 days comes the last signal: if nothing has been done by then, the matter needs the attention of a manager, not just the person assigned to it.
Alerts arrive in Telegram rather than email — deliberately. In companies that live in supplier correspondence, the inbox is overloaded: dozens of messages a day, and a deadline notice would sink among them. Telegram stays a channel for the short and the important: the same bot sends alerts about invoices, time-limited offers, and emails left unanswered for more than a few hours, so the team gets used to reading it.
A separate principle is the system's own honesty. If email processing stops for any reason, a "down" signal is sent, and once it recovers, a mandatory paired "back up" signal follows. You can trust a deadline registry only when you know it's alive — not sitting silent because of a failure.
How documents reach the registry without manual entry
The key question for any registry is who fills it. If dates are entered by hand, the registry repeats the fate of the spreadsheet: six months of discipline, then gaps. That's why in HORUVIA documents reach the registry through three automatic paths.
The first is email. The system connects to a mailbox over IMAP and sorts incoming supplier messages by brand and document type. If an attachment is a contract, certificate, or policy, the document is saved to that supplier's memory, and the extracted dates flow into the deadline registry.
The second is scans. Paper documents, once run through OCR, are handled the same way as email attachments: the system pulls dates and details out of the text. Why this is more reliable than retyping by hand, and what errors manual entry introduces, we covered in the article on OCR and manual-entry errors.
The third is a desktop agent. A small program watches a chosen folder on a work computer: anything an employee drops there is sent to the server and runs through the same processing. The extracted data stays visible next to the document — you can check and correct it — but the starting work is done by the machine, not by a person at a keyboard.
When a certificate's validity expires at customs
For an importer, the most expensive version of this problem is certificates. A conformity or origin certificate has a limited validity, and cargo travels for weeks. If the certificate's validity expires while the container is in transit, the document is already useless by the time the declaration is filed — and the batch stalls until a new one is obtained. Every day of downtime means storage fees, missed deliveries to customers, and money frozen in goods.
That's exactly why HORUVIA stores each supplier's certificates together with their validity dates in memory, and the deadline engine treats them as registry entries just like contracts. The 60-day alert gives enough of a buffer to request and issue a new document before the next batch ships. The system itself grew out of a real case in import operations, where correspondence involves dozens of brands and documents arrive in a continuous stream. Which certificates apply in the EAEU and what to watch for in their validity periods is covered in a separate article on EAEU certificates and their deadlines.
Not only import: health permits, insurance, and shelf life
Tracking document deadlines isn't only for importers. In food service and manufacturing, the same mechanism covers employee health permits and raw-material shelf life: an expired permit found during an inspection costs the business no less than a lapsed certificate at customs. How the AI operator works in this segment we showed in the piece on HoReCa and manufacturing.
In services and logistics, the registry takes in insurance policies, lease agreements, and driver powers of attorney. In retail — product conformity declarations. So you don't have to configure deadline types from scratch, HORUVIA ships with onboarding presets by segment: on setup the system suggests a standard set of documents and deadlines for import, retail, services, HoReCa, or logistics, and the set is then refined to fit your specific company.
Where to start: the first week with a registry
An honest note: the registry won't fill itself retroactively. The initial load has to be done once, and it makes sense to plan it as a short project.
- Gather your active contracts, policies, and certificates — from email, network folders, and paper archives.
- Run the paper documents through a scanner: OCR and processing will take it from there.
- Connect the work mailbox over IMAP so new documents land in the registry on their own.
- Review the extracted dates and fix any that look off — it's faster than entering everything by hand.
- Wait for the first alerts and confirm they reach the right people.
After that the registry maintains itself: new documents come in by email or through the agent's folder, dates are extracted automatically, and the 60/30/7 ladder keeps any deadline from quietly burning down.
What's next
If deadlines in your company currently live in spreadsheets and people's heads, start with a simple exercise: add up how much time the team spends manually processing email and documents — there's a calculator on the site for exactly that. Answers to common questions about connecting email and data security are gathered in the FAQ section. And to see the deadline registry and 60/30/7 alerts on live data, request a demo on the HORUVIA home page — we'll show how documents from your inbox turn into registry entries without any manual entry.