Describe the change precisely
Record whether a sender moved a field, renamed a label, added a column, changed page size or introduced a new document type. These are different changes. Save the last accepted example and the new example in your authorized workspace. Do not overwrite the original while tuning. Without both versions, a reviewer cannot tell whether a proposed repair improves coverage or simply trades one failure for another.
Create a small regression set
Run the changed route against the new sample and representative previously accepted cases. Include the case most likely to be confused by the new rule. A fictional new address block should not replace the document reference simply because it appears in the former reference position. Compare required fields and row pairings, not only file-level success. Record which configuration produced each output and which cases remained unresolved.
Separate recognition from acceptance
A workflow may recognize that a document is different yet still produce unsuitable fields. Conversely, it might accept a familiar-looking layout with altered meaning. Your process needs an explicit unknown-layout or review path appropriate to the available tooling. Do not assume a vendor supplies such a safeguard automatically. Inspect the actual configuration and permitted product behavior before relying on it for unattended processing.
Release the smallest change
Change only the affected mapping or route when a demonstrated cause supports that repair. Preserve a known prior configuration and the evidence needed to restore it through an authorized process. If the change affects many document classes, widen the review before enabling downstream writes. Continue to the pilot guide for a review-only rollout. A patch that passes one example is not a reason to remove all ongoing exception checks.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Parsio: documented parsing options — Merchant documentation · parsio.io · Merchant-controlled · checked 2026-09-30
- Docparser: documented feature set — Merchant documentation · docparser.com · Merchant-controlled · checked 2026-09-30