Purpose
The Maker & Checker documents are validation checklists used to confirm that a Document Insights implementation is correctly configured and independently verified before go-live.
They follow a Maker–Checker model:
-
The Maker performs the configuration or setup activity.
-
The Checker independently validates and confirms it.
This separation improves configuration accuracy, strengthens audit and compliance readiness, and reduces deployment risk.
The Checklists
There are two checklists, grouped the same way as the rest of the implementation docs — standard document OCR vs. custom forms:
|
Checklist |
Covers |
Use for |
|---|---|---|
|
MoneyThumb, Ocrolus & Ocrolus Instant |
Bank statement, identity, and income document integrations |
|
|
Lazarus, Google Gemini |
Custom form integrations |
What Each Checklist Covers
Each checklist walks through the full implementation, grouped into these areas:
-
Environment & prerequisites — org-level settings and Remote Site Settings
-
Configuration — Custom Settings, Custom Metadata, source objects, and field mappings
-
Integration & security — API credentials, webhooks, user permissions, and access
-
Processing & jobs — batch jobs, platform events, and end-to-end processing runs
-
Verification — Lightning Web Component and analytics checks, error handling, and retry/reprocessing scenarios
-
Sign-off — final review and approval by both Maker and Checker
How Sign-off Works
Every item is marked by the Maker once complete and independently confirmed by the Checker. Both must sign off before production deployment or customer go-live. Treat these as implementation-governance artifacts for the project record.
Intended Audience
Salesforce administrators and implementation teams (Makers), and QA, compliance, and technical leads (Checkers).