Urgent: Best way to persist rounding rules post-Action Center validation?

Help Document Understanding
, , , , ,
1

I’m using UiPath Document Understanding to process Chinese invoices, specifically extracting the “Total Amount” field (e.g., ¥133.99). My requirement is:

  1. Round the amount (e.g., ¥133.99 → ¥134) based on business rules.
  2. Validate the rounded value in Action Center (Human-in-the-Loop).
  3. Persist the rounding rule for future invoices if the operator confirms (e.g., always round up).

The image shows a Chinese tax invoice with most information redacted, displaying a highlighted total amount of ¥133.99 and the invoice date of March 3, 2025. (由 AI 生成标题)
The image shows a Chinese tax invoice with most information redacted, displaying a highlighted total amount of ¥133.99 and the invoice date of March 3, 2025. (由 AI 生成标题)1829×902 241 KB

2

I mean whether we can set the roundup rule in the “Action center”? I know that we can do that in our business process.

3

Hi @Stitch,

I don’t believe we have any such predefined rule, but you can always add all the required rules like rounding up etc in post processing stage before sending it to action center.

4

Hi @mrv.raj

I am not quite sure what activity can do it. I think I should do something before "create document validation action " or “wait for document validation action and resume”.

could you screenshot for me? or how can I do? thank you very much.

The image shows a workflow sequence screen from an application, detailing steps for creating and waiting for a document data validation action, including configuration settings and output handling. (由 AI 生成标题)
The image shows a workflow sequence screen from an application, detailing steps for creating and waiting for a document data validation action, including configuration settings and output handling. (由 AI 生成标题)1193×963 51.2 KB

5

Hi @Stitch,

Follow the below steps

  1. Go to Extraction Rules Check (i.e 55_ExtractionBusinessRuleValidation.xaml)

    The image illustrates a flowchart for data extraction that involves extracting data, checking extraction rules, validating and training extractors, and exporting data if successful. (Captioned by AI)
    The image illustrates a flowchart for data extraction that involves extracting data, checking extraction rules, validating and training extractors, and exporting data if successful. (Captioned by AI)1064×350 16.8 KB

  2. In 55_ExtractionBusinessRuleValidation.xaml you can create new post processing xaml and invoke it from here or you can customize the existing InvoicePostProcessing.xaml as per your requirement

    The image depicts a flowchart for Business Rule Validation post-extraction, illustrating decision pathways for processing invoices and receipts based on document type. (Captioned by AI)
    The image depicts a flowchart for Business Rule Validation post-extraction, illustrating decision pathways for processing invoices and receipts based on document type. (Captioned by AI)1271×673 32.3 KB

You can reference all the predefined rules in InvoicePostProcessing.xaml, if that’s confusing for you then you can simply use below syntax to access/update the extracted field from ExtractionResult

extractionResult.GetField(<FieldId>).GetValue.Value

FieldId you can find in Taxonomy Manager once you click on the field

The image shows a screenshot of the Taxonomy Manager interface, displaying various financial fields such as Invoice Number and Tax Amount on the left, with "Total" highlighted and detailed on the right. (Captioned by AI)
The image shows a screenshot of the Taxonomy Manager interface, displaying various financial fields such as Invoice Number and Tax Amount on the left, with "Total" highlighted and detailed on the right. (Captioned by AI)1381×664 50.5 KB

In the post processing xaml you will also need to update the out_AutoExtractionSuccess flag it its True action center task will be created otherwise skipped

1 Like
6

Hi Vishal Rajmance via:

thanks for your response.

your steps are very helpful to me. I understand you will add all of the business rule in the “extraction rules check”.

such as checking the extraction data format, type and construction. we can also chect the document type ID which is correct.

if any extraction data does not match the business rule, we can throw the exception ro step to the validate & train extractors process.

I just double check whether we cannot do any business rule setting in the action center?

I noticed a numeric variable in Action Center was recognized as '$133.99′ in Document Understanding, but the final value was ′ 133.99 ′ . Is stripping the ′$ ’ a default action? Can we apply similar rules (e.g., rounding/truncation) in Action Center?

在 2025-04-30 11:56:05，“Vishal Rajmane via UiPath Community Forum” notifications@uipath.discoursemail.com 写道：

7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.