05 JUNE 2025
Welcome to the Genpact AP Capture Release Notes.
What's in the Release Notes?
- About Genpact AP Capture
- Main features
- Enhancements
- Resolved issues
- Known issues
- Limitations
About Genpact AP Capture
Genpact AP Capture is a GenAI and ML supported standalone independent solution that integrates with AP Flow and other systems using the webAPI, and provides end-to-end capability to extract data. The Genpact AP Capture solution extracts not only the header data but also the line level data from different documents efficiently and automates data extraction, classification and validation.
Automating the extraction and validation reduces manual processing and error occurrence, and increases accuracy. With Genpact AP Capture, the AP process becomes faster, more accurate, and more secure, allowing the customer to focus on strategic decision-making. Efficient AP management with Genpact AP Capture enhances cash flow, reduces costs, strengthens partnerships, and helps in sustainable business growth.
Main features
- Dynamic rules in the UI: Genpact AP Capture supports dynamic control of UI field behavior in the Eyeball task module through YAML configured rules. These rules adjust visibility, availability, and mandatory status of fields in the Eyeball UI based on invoice data and user interactions.
For details, see this article. - Pre-filter popup table and Multicolumn combobox: You can dynamically add pre-filters to comboboxes, multi-column comboboxes, and popup tables, where a parent field filters the values in a child field based on relationships like parent to child, parents to children, parents to child, or parent to Childs.
Enhancements
- Updating Eyeball real-time with extraction model updates: The Genpact AP Capture functionality has been enhanced to automatically apply the YAML updates in the Eyeball task and the results documents are JSON and XML.
Resolved issues
| # | Issue | Fix | Ticket # |
|---|---|---|---|
| 1 | In an Eyeball task, the hamburger menu icon was not aligned in the tabular view. | The hamburger menu icon now appears correctly in the tabular view. | - |
| 2 | Deleted line-items were not restored if you refreshed the invoice or browser without saving the deletion. | Deleted line-items are restored if you refresh the invoice or browser without saving the deletion. | - |
| 3 | The line-item rows remained selected when the user clicked "Cancel" on the Delete Confirmation popup. | After clicking Cancel, the line-item rows are not selected. | - |
| 4 | In a table with too many columns, the Delete ( ) icon appeared misaligned and overlapped.
|
The Delete () icon appears correctly. |
- |
| 5 | In line-item description, maximum length restriction or validation didn't work. | In line-item description, maximum length restriction or validation works fine now.
|
- |
| 6 | In popup table control in an Eyeball task, the mandatory field validation message appeared even when value existed in the field. | The validation message now disappears, once the user selects a value in the popup table. | - |
| 7 | Deleting the content of a field with the 'X' didn't trigger the enrichment UI. | The 'X' triggers the enrichment UI. | - |
| 8 | When a validation message appears below the checkbox control, the control label shifts downward. | The control label position remains intact. | - |
| 9 | The tooltip of the checkbox field showed "false" for both selected and unselected states. | The tooltip displays correct checkbox state for both selected and unselected. | - |
| 10 | In Eyeball screen, polygon selection didn't populate Chinese, Japanese, and Vietnamese date formats in fields. User had to manually enter the date. | The date formats in Chinese, Japanese and Vietnamese are populated correctly when polygons are drawn. | - |
| 11 | When a field was defined as numeric in extraction-model.yaml but DocIntel returned its value as a string, the system inserted the numeric characters into the field instead of clearing it and keeping it null. | The system now clears the polygon and keeps the field null if the returned value type doesn’t match the numeric definition. | - |
| 12 | When user clicked 'X' in a date field, the value was deleted, but when the user navigated back to the field, the value showed up again. | The date field value remains cleared even after navigation. | - |
| 13 | When drawing a polygon and navigating away, the polygon was saved but not visible when returning to the field. | The system now displays polygons when the user navigates back to the field after drawing. | - |
| 14 | In popup table control, long column names were cut and didn't have tooltips or an option to widen the column. | The system now shows tooltips for long column names and allows users to widen columns in the popup table. | - |
Known issues
| # | Description |
|---|---|
| 1 | For fields with '\' or '/' characters, the value is not extracted and displayed in the eyeball task. |
| 2 | Table auto-fill adds extra text that is not line-item but is too close to the line items. |
| 3 | Uploading duplicate invoices in the AP Flow Adapter leaves the XML file in the input folder. |
| 4 | Navigation from the form fields to the line-item fields hides the first polygon. |
| 5 | A checkbox control can't be disabled. |
| 6 | In auto-rotation, the invoices are uploaded a bit zoom out. |
| 7 | A date in word format separated with comma is not supported. (for example, May,17,2024) |
| 8 | The system doesn't extract very large invoices with many line items and over 320 pages due to current limitations. |
| 9 | For large invoices with more than 150 line-items, the invoice payload isn't sent to the ADH team. |
| 10 | The system removes special characters when users type the value, not by drawing or selecting the polygon. |
| 11 | In the Eyeball task, for PDF documents some images are not displayed. |
Limitations
- The auto-fill works when the distance between the lines and the columns is less than 35 pixels.
- The auto-fill stops if the next text below the previous line item is greater than 50 pixels.
- The auto-fill currently works on a single page only.
- The polygon doesn't work for values populated with auto-fill.
- The polygon doesn't support dates for specific formats in Chinese, Japanese, and Vietnamese language. You must add the date manually.
