Certificate of Currency Bulk Validator — Renewal Cross-Check avatar

Certificate of Currency Bulk Validator — Renewal Cross-Check

Pricing

$20.00 / 1,000 certificate validateds

Go to Apify Store
Certificate of Currency Bulk Validator — Renewal Cross-Check

Certificate of Currency Bulk Validator — Renewal Cross-Check

Cross-checks already-extracted certificate of currency data against a broker renewal schedule. Field-by-field matching of insurer, policy number, expiry and coverage limits with tolerant normalisation. Does not read PDFs. One dataset item per certificate validated.

Pricing

$20.00 / 1,000 certificate validateds

Rating

0.0

(0)

Developer

Christopher Smith

Christopher Smith

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

a day ago

Last modified

Share

Cross-check batches of already-extracted certificate of currency data against your renewal schedule in seconds. Every certificate is compared field-by-field — insurer, policy number, expiry date, coverage limit, class of insurance — and comes back as a clear PASS/FAIL with the exact mismatches listed. In the US these are certificates of insurance (COI) - same documents, same checks; only the name changes.

Built for insurance brokers, MGAs, corporate risk managers, and insurance ops teams - AU certificate of currency and US COI workflows alike - who spend renewal season re-keying and eyeballing dozens of certificates against a schedule.

This tool does not read PDFs. It takes structured records you have already extracted (by your OCR or document-AI step, or by hand) and does the tedious cross-checking half of the job — consistently, every field, every certificate.

What does the Certificate of Currency Validator check?

  • Insurer name — case-insensitive match
  • Policy number — tolerant of dashes and spaces (POL-2024-001 matches POL2024001)
  • Expiry date — many formats accepted; expired certificates are flagged even when the dates match
  • Coverage limit — normalises $5,000,000, 5M, and 5 million before comparing
  • Class of insurance — case-insensitive match
  • Unmatched certificates — anything missing from the schedule is FAIL by default (set strict_unmatched: false to downgrade to WARNING)

How do I validate certificates in bulk?

  1. Provide certificates (extracted data) and schedule (what the renewal schedule says), matched by id.
  2. Optionally set today for point-in-time expiry checks.
  3. Run. One dataset row per certificate with PASS/FAIL and per-field results; aggregate stats in the run's SUMMARY record.

Input example

{
"certificates": [
{"id": "C001", "insurer": "Allianz Australia", "policy_number": "POL-2024-001",
"expiry_date": "31/12/2026", "limit": "$5,000,000", "class_of_insurance": "Public Liability"}
],
"schedule": [
{"id": "C001", "insurer": "allianz australia", "policy_number": "POL2024001",
"expiry_date": "31/12/2026", "limit": "5M", "class_of_insurance": "public liability"}
]
}

Output example (one dataset row per certificate)

{
"id": "C001",
"status": "PASS",
"issues": [],
"field_results": {
"insurer": {"match": true},
"policy_number": {"match": true},
"expiry_date": {"match": true, "expired": false},
"limit": {"cert_parsed": 5000000, "sched_parsed": 5000000, "match": true},
"class_of_insurance": {"match": true}
}
}

What's new in v2 — renewal cycle support

  • renewal_window_days input (default 30): certificates expiring inside the window are flagged renewal_due with days_until_expiry on every result row — your renewal chase list falls out of the validation run.
  • Client-ready summary: each run also produces a plain-text CLIENT_SUMMARY (key-value store) that a broker can forward to the client or insurer as-is - validation results, renewal flags, and issues in plain English.

Pricing (pay-per-event)

EventPrice
Certificate validatedUSD $0.02 per certificate (one dataset row each)

You pay only for certificates actually validated: a 300-certificate renewal cycle costs USD $6.00. No subscription.

FAQ

Does it read the certificate PDFs? No — and that's deliberate. PDF extraction quality varies wildly; you keep control of that step. This Actor guarantees the checking is exhaustive and consistent once the data exists.

Is this an AI tool? No. Deterministic field comparison with tolerant normalisation — same input, same result, auditable every time.

What counts as a FAIL? Any field mismatch, an expired certificate, or (by default) a certificate with no schedule entry. Every FAIL lists its exact reasons in plain English.

Where do my certificates go? Nowhere. Validation happens inside the run; no external services are called.

Support & feedback

Questions or feature requests? Open an issue on this Actor's Issues tab — responses are prompt, and the roadmap only advertises what actually ships.