Typo in the return value of the 1040 tax form recognition

Yilun Sun 5

The return value for the filing status option "Married filing separately (MFS)" in the 1040 form is currently married_filling_separately. It should be married_filing_separately with only one l.

2 answers

Avinash Devarakonda 330 Reputation points Microsoft Vendor

2024-11-15T05:29:17.9733333+00:00

Hi Yilun Sun,

Welcome to Microsoft Q&A Forum, thank you for posting your query here!

To correct the typo in the return value for the “Married filing separately (MFS)” option on the 1040 form, you need to locate the section of your code where the filing status is defined, change married_filling_separately to married_filing_separately, and then test the change to ensure it doesn’t affect other parts of your application. Once verified, you can deploy the updated code to your production environment. This ensures the correct return value is used consistently.

Kindly refer the below document for any guidance.

https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/prebuilt/tax-document?view=doc-intel-3.1.0#field-extraction-1040-tax-form

Hope this helps. Do let us know if you any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer

Thank You.
Please sign in to rate this answer.
Yilun Sun 5 Reputation points

2024-11-15T05:50:15.16+00:00

I believe this is NOT a correct solution. There are the same typos in your documentation, please fix the model's return values, including these issues. - https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/prebuilt/tax-document?view=doc-intel-3.1.0#field-extraction-1040-tax-form:~:text=%2C%20marriedFilingJointly%2C-,marriedFillingSeparately,-%2C%20headOfHousehold%2C - https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/prebuilt/tax-document?view=doc-intel-3.1.0#field-extraction-1040-tax-form:~:text=unselected%3A%20marriedFilingJointly%3Aunselected%3A-,marriedFillingSeparately,-%3Aunselected%3A%20headOfHousehold%3Aunselected
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Yilun Sun 5 Reputation points

2024-11-15T05:50:05.4233333+00:00

Please fix the model's return values
Please sign in to rate this answer.
Avinash Devarakonda 330 Reputation points Microsoft Vendor

2024-11-15T09:23:59.3666667+00:00

Hi Yilun Sun,

Thank you for your feedback, and I apologize for any inconvenience caused.

For this scenario, you might consider using a custom extraction model tailored to your use case, which could give you more control over field recognition and handling of filing status options. This approach can help ensure your data extraction aligns precisely with the formats you expect, reducing errors like the typo you encountered.

Additionally, for any improvements or specific feature requests, please consider sharing your insights in the Azure Feedback Forum. Your input directly helps us refine and enhance our services. We're here to support you in implementing any adjustments and let me know how we can assist further!

Could you please take a moment to retake the survey on the above response? Your feedback is greatly appreciated.

Avinash Devarakonda 330 Reputation points Microsoft Vendor

2024-11-18T05:42:51.4233333+00:00

Hi Yilun Sun,

Following up to see if the given response was helpful.

Thank You.

Avinash Devarakonda 330 Reputation points Microsoft Vendor

2024-11-19T04:57:27.3166667+00:00

Hi Yilun Sun,

We haven’t heard from you on the last response and was just checking back to see if the give response was helpful.

Thank You.

Yilun Sun 5 Reputation points

2024-11-20T02:20:31.62+00:00

Hi @Avinash Devarakonda

Thank you for your response, but I would like to know if you acknowledge this as one of your errors and if you are unwilling to make any modifications, instead leaving the inconvenience to the users? This is clearly a typo in the return values of the Prebuilt model; do you admit this?

Yilun Sun 5 Reputation points

2024-11-20T02:27:31.2466667+00:00

I really don't like to burden the users with this workaround.

Avinash Devarakonda 330 Reputation points Microsoft Vendor

2024-11-21T03:46:02.5133333+00:00

Hi Yilun Sun,
Thank you for bringing this to our attention. We acknowledge the issue and are currently investigating it. We appreciate your patience as we work on resolving this.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Typo in the return value of the 1040 tax form recognition

2 answers

Your answer