← Back to Our Work
Capability Brief
At 700 million mail pieces per year across regulated financial, insurance, healthcare, and government clients, operational resilience was not optional — it was a contractual, compliance, and fraud-prevention requirement. This capability brief documents the four-pillar integrity architecture built and operated at enterprise scale by Mike Preczner at RR Donnelley Canada — forming one of the most complete regulated mail integrity systems operated in Canada.
Most document integrity systems detect failures. This system resolved them automatically.
Pitney Bowes DF Works ADF monitored every piece through the production chain via 2D barcode read at insertion. Any integrity failure — wrong sequence, missing sheet, damaged piece, barcode misread — was automatically flagged by the system. DF Works automatically generated a reprint file containing only the failed pieces — no manual identification required. The reprint file was routed to the Riso or any available printer, reprinted pieces reintroduced into the job, and re-verified through the integrity loop.
Not all reprints carry the same risk. A reprinted statement is a quality event. A reprinted cheque is a potential fraud event. The notification protocol reflected that distinction.
Financial, insurance, government, and transactional statement clients. Total piece count confirmed and reconciled. Reprint detail not required — the client needs to know the job balanced, not that individual pieces were reprinted. Risk level: quality event, managed internally.
Banking, cheque production, and MICR-certified output clients. Reprinted cheque pieces formally reported to the client for fraud monitoring. A reprinted cheque number requires tracking — the original and reprint both exist until the original is confirmed destroyed or undelivered. Risk level: fraud risk — CPA compliance obligation.
Pre-printed MICR cheque stock carried an inherent and unacceptable risk: an operator loading the wrong MICR form into the wrong tray meant the wrong cheque on the wrong account — a fraud and compliance event of the highest severity in a banking environment. The solution was to eliminate pre-printed MICR stock entirely by introducing inline MICR printing — printing MICR characters on demand, on plain white stock, inline with the job. The error condition was not managed. It was removed.
The operation held formal MICR Verification Shop certification — authorized to sign off on MICR print quality using the RDM MICR Verifier to Canadian Payments Association (CPA) and ABA standards. Certification covered E-13B character geometry, magnetic ink density, and signal strength verification — the three parameters banks require for machine-readable cheque processing. Output was verified and signed off internally before delivery, without requiring external third-party verification.
The four pillars combine into a complete, layered integrity architecture — each layer addressing a different failure mode:
| # | Layer | Failure Mode Addressed | Outcome |
|---|---|---|---|
| 1 | Inline MICR Printing | Wrong MICR form on wrong account | Impossible by design — MICR is data-driven |
| 2 | 2D Barcode + Camera Integrity | Wrong document in wrong envelope | Detected and flagged at insertion |
| 3 | Closed-Loop ADF Reprint | Failed pieces entering the mail stream | Auto-isolated and reprinted — never mailed |
| 4 | Cheque Client Notification | Reprinted cheque creating fraud exposure | Client notified for fraud monitoring |
| 5 | RDM MICR Verification | MICR output below CPA/ABA standard | Verified and signed off before delivery |
At scale, failures are not a question of if — they are a question of when and how fast you recover. A closed-loop ADF with automatic reprint generation, inline MICR production, and a layered integrity architecture means failures are detected, resolved, and documented before they become client or compliance events.
If your operation is handling regulated mail, cheque production, or high-volume transactional communications without a complete integrity architecture, there is exposure you may not have fully mapped. Let’s talk about what a compliant, resilient operational design looks like for your environment.
Book a Conversation →