Extraction returned wrong data
The AI read your contract and got something wrong — bad date, wrong party, missed a contingency. Happens, especially on:
- Scanned / photographed contracts with OCR noise
- Unusual formatting (handwritten edits, state-specific forms BuyerFlo hasn't seen before)
- Old contract versions where the AI expects newer field names
Here's how to fix it without breaking the engine.
Easiest: fix on the review screen
If you catch it during the extraction review step (before you confirm and hit "Activate deal"), just edit it directly. Every field is editable on the review form. The AI's read goes into the form prefilled; you correct, confirm, and the deal activates with your corrected data.
This is the cheapest time to fix misreads.
After the deal is active: edit the deal
If you catch it later, go to the deal → Edit in the top-right. The edit page shows every tracked field with the current value. Change what's wrong, hit Save.
The reconciler runs automatically when you save. It:
- Writes your corrected values to the deal
- Re-plans every task affected by the change (date shifts re-compute due dates; contingency flips add or skip tasks)
- Shows a preview of what will change before you confirm save, so you can back out if the cascade looks wrong
When the wrong field has already driven wrong actions
Worst case: the AI had the closing date as May 15 when it was actually May 29. The engine sent an inspection-period reminder based on the wrong date. A party acted on it. Now you're trying to fix.
Path:
- Edit the field to the correct value. Save. The reconciler re-plans forward.
- Review any blocked / proposed-complete tasks. Some may be blocked because the old date already passed.
- Email affected parties manually. Apologize for the confusion, give the correct date. Use the deal's address so the correction threads into Activity.
- Mark incorrectly-completed tasks as reopened if any AI auto-completes fired on the wrong data.
Re-extracting the contract
If the extraction is so bad that fixing field-by-field is more work than starting over, we can re-run extraction. Email us with the deal id and we'll trigger a fresh pass on the same PDF.
This is relatively rare — the most common issue is a single bad field, which is easier to fix by editing.
When the original PDF has the wrong data
Sometimes the contract itself has an error that got corrected in an addendum. The extraction is right for the original; the addendum changes it. Apply the addendum — the scanner detects the change and re-plans.
Common misreads to watch for
- Date formats — "4/5/26" could be April 5 or May 4 depending on country. US forms should be MM/DD; the extractor assumes this but can get confused on international format hints.
- Money — "$450,000" vs "$450,000.00" usually fine; "$450k" or "four hundred fifty thousand" are harder.
- Names on signature lines vs. printed names — the AI prefers printed name; if the printed name is illegible and the signature is clear, it may pull neither correctly.
- Contingency periods — "10 days" vs "10 business days" vs "10 days after Effective Date" — the extractor usually gets these right but review the focused-flow step.
When it's truly wrong, file a bug
If you see the same kind of misread twice, email us with the deal ids + the field. We use these patterns to improve the extractor. Your feedback directly moves the accuracy curve for every future deal.