Automation with explicit review boundaries
TD Data Systems APIs are designed to assist document-processing workflows, not to replace the customer's financial controls.
Automated systems can be wrong
OCR, document parsing and record matching can be affected by damaged scans, unusual layouts, missing data and ambiguous text.
Uncertainty should be visible
Validation information and matching exceptions should be used to route uncertain cases for review.
Financial actions need controls
API output should not be the sole basis for releasing payment, posting accounts or making other consequential financial decisions.
Recommended integration pattern
- Process the document through the API.
- Check validation status, confidence and exception information.
- Apply your own business rules and approval thresholds.
- Route incomplete, ambiguous or unexpected results for review.
- Only perform consequential actions after your required controls pass.
Why we do not promise perfect accuracy
No OCR, parser, matching engine or AI system can guarantee that every document will be interpreted correctly. A safer system detects and exposes uncertainty rather than pretending every result is certain.