Who this is for
Your AP team keeps correcting the same fields, an important invoice type has stopped processing reliably, or you need to understand an existing WFR project before changing it. You may also be planning an upgrade or comparing a replacement extraction service.
ECMWorks reviews the recognition process in the context of the work around it: document capture, validation, review, coding and the ERP handoff. See Forms Recognition, explained for the background.
What we examine
| Area | What the review needs to establish |
|---|---|
| Project and recognition configuration | How documents are classified and fields extracted, including scripts or supplier-specific handling where used |
| Runtime processing | How documents enter processing, where failures occur and whether environments differ |
| Image preparation and reference data | Whether conversion preserves usable input and the supplier or purchase-order lookups used by the process are current |
| Operator review | Which fields and invoice types create correction work, and how review decisions affect the result |
| Validation and handoff | How extracted values are checked and delivered to imaging, workflow and ERP integration |
The project's value is in the behavior it supports. Preserve the configuration, scripts and learning-related assets present in the implementation so their role can be assessed and tested. Their portability depends on the source and target versions and the proposed design.
Four situations that bring a team to us
The people who built the project have moved on. The system still runs, but the team needs to understand its rules and dependencies before making a change.
New invoice types create more manual work. Review which documents fail, which fields need correction and whether the cause lies in recognition, validation or reference data.
A previously reliable invoice type stops working. A layout change, poor image quality or an upstream configuration change can prompt an investigation. Reproduce the problem with representative samples before choosing a correction.
A replacement is being considered. Establish what the existing process handles and the outcomes a candidate must match. Include exceptions and human review in the comparison.
How we review a WFR project
- Establish the baseline. Review the installed version, available project and configuration, integrations and the issue the team wants to solve.
- Inspect extraction and validation. Trace relevant fields through recognition, scripts, checks and operator review. Identify supplier-specific handling where it exists.
- Compare behavior with the invoice mix. Use representative successful and unsuccessful documents. Identify which cases account for repeated correction or failures.
- Trace the handoff. Check how the resulting data and images reach the next stage, including field mappings and exception handling.
- Test the proposed change. Compare results against the baseline and record any differences that matter to AP users or downstream systems.
The WFR template analyzer is an optional starting point for exploring project information. A processing assessment also needs sample documents and observed results.
Including WFR in an upgrade or OCI move
Start with the exact WFR release, its runtime requirements and the versions of the products it connects to. Establish the applicable support position and upgrade options before committing to a target design.
A wider 14c program needs specific checks for project compatibility, processing behavior, review and integration. Any proposed change to the extraction engine or handoff is assessed separately. See the WebCenter upgrade guide for the surrounding program and Forms Recognition modernization for the extraction decision.
Rehearse with representative documents and retain a recoverable baseline. For an OCI move, include connectivity, document access and the treatment of incoming batches in the cutover plan. The project and configuration need validation in the target environment.
Where old and new environments run alongside each other, give each intake source a clear owner. Plan the switch for mailboxes, watched folders and downstream exports so competing consumers do not take work intended for the other environment. Verify the handoff with controlled samples before production intake changes.
Compare extraction approaches on the work users do
Measure both the extracted data and the effort needed to make it usable. Useful comparisons include:
- Which required fields are correct before review.
- How much correction or manual entry each invoice needs.
- How validation handles missing or inconsistent values.
- Whether downstream coding and import receive the expected data.
- How exceptions are investigated and resolved.
Evaluate the current project and any candidate on the same representative sample, including difficult cases. The WFR and OCI Document Understanding comparison introduces the wider decision; the outcome still depends on your documents and integration requirements.
Ongoing WFR care
A standing support engagement can cover recurring exceptions, targeted project changes, validation tuning and patch planning. Changes are tested against an agreed sample before promotion, with the outcome and recovery approach recorded.
The work may also uncover issues in Enterprise Capture, WebCenter Imaging or the workflow and ERP integration. Those findings become part of the diagnosis and agreed scope.
How ECMWorks does this
We start with the problem and the evidence available. A focused review produces findings, recommended changes and test cases. An upgrade or replacement assessment adds target compatibility, integration requirements and cutover planning. Ongoing support keeps recurring issues and changes in a shared work list.
The scope can remain within WFR or extend to the surrounding invoice process where the investigation requires it.