LedgerSync uses AI to automatically extract statement dates from bank PDFs. While highly accurate, occasional errors may occur. This article explains why this happens and how to manage it.
MasterCard's API does not include statement dates in its response. LedgerSync uses AI to read PDFs and assign dates automatically.
1. Multiple Dates on Statement: Bank statements contain several dates (transaction, processing, closing, due dates). AI may select the wrong one.
2. PDF Security/Locked Files: Adobe security settings may prevent AI from reading PDFs.
3. Unusual Formats: Non-standard layouts or foreign language statements may reduce accuracy.
Note: These errors are the exception, not the norm. Most statement dates (95%+) are correct.
Common red flags:
Submit a support ticket when you notice:
New Client Onboarding: Verify statement dates for first 3 months. Document banks requiring manual corrections.
Team Training: Include statement date verification in standard procedures. Create quick reference guide.
Quality Control: Implement monthly spot-checks. Flag patterns to support. Log problematic banks.
LedgerSync continuously improves AI extraction. Machine learning models update based on reported errors. Until MasterCard includes dates in API responses, AI extraction remains necessary because:
All Statements Same Date: AI likely locked onto standard date on all statements. Manually correct and report.
Future Dates: AI selected next statement date. Open PDF, find actual date, correct manually.
Missing Dates: PDF locked/secured. Manually enter from PDF and report.
Inconsistent Formats: Verify dates are logically correct despite format differences.
Email: support@ledgersync.com
Technical Issues: maurice.berdugo@ledgersync.com