You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| CurrencyCode | String | The Currency Code associated with an extracted amount ||
211
210
| PaymentOptions | Array | An array that holds Payment Option details such as `IBAN`and `SWIFT`||
212
211
| TotalDiscount | Number | The total discount applied to an invoice | Integer |
213
212
| TaxItems (en-IN only) | Array | AN array that holds added tax information such as `CGST`, `IGST`, and `SGST`. This line item is currently only available for the en-in locale ||
@@ -235,7 +234,7 @@ The invoice key-value pairs and line items extracted are in the `documentResults
235
234
236
235
The prebuilt invoice **2022-06-30** and later releases support returns key-value pairs at no extra cost. Key-value pairs are specific spans within the invoice that identify a label or key and its associated response or value. In an invoice, these pairs could be the label and the value the user entered for that field or telephone number. The AI model is trained to extract identifiable keys and values based on a wide variety of document types, formats, and structures.
237
236
238
-
Keys can also exist in isolation when the model detects that a key exists, with no associated value or when processing optional fields. For example, a middle name field may be left blank on a form in some instances. key-value pairs are always spans of text contained in the document. For documents where the same value is described in different ways, for example, customer/user, the associated key will be either customer or user (based on context).
237
+
Keys can also exist in isolation when the model detects that a key exists, with no associated value or when processing optional fields. For example, a middle name field may be left blank on a form in some instances. key-value pairs are always spans of text contained in the document. For documents where the same value is described in different ways, for example, customer/user, the associated key is either customer or user (based on context).
239
238
240
239
::: moniker-end
241
240
@@ -247,7 +246,7 @@ Keys can also exist in isolation when the model detects that a key exists, with
247
246
248
247
## Fields extracted
249
248
250
-
The Invoice service will extract the text, tables, and 26 invoice fields. Following are the fields extracted from an invoice in the JSON output response (the following output uses this [sample invoice](media/sample-invoice.jpg)).
249
+
The Invoice service extracts the text, tables, and 26 invoice fields. Following are the fields extracted from an invoice in the JSON output response (the following output uses this [sample invoice](media/sample-invoice.jpg)).
251
250
252
251
|Name| Type | Description | Text | Value (standardized output) |
253
252
|:-----|:----|:----|:----| :----|
@@ -266,7 +265,7 @@ The Invoice service will extract the text, tables, and 26 invoice fields. Follow
266
265
| BillingAddressRecipient | string | Name associated with the BillingAddress | Microsoft Services ||
267
266
| ShippingAddress | string | Explicit shipping address for the customer | 123 Ship Street, Redmond WA, 98052 ||
268
267
| ShippingAddressRecipient | string | Name associated with the ShippingAddress | Microsoft Delivery ||
269
-
|SubTotal| number | Subtotal field identified on this invoice | $100.00 | 100 |
268
+
|Sub​Total| number | Subtotal field identified on this invoice | $100.00 | 100 |
270
269
| TotalTax | number | Total tax field identified on this invoice | $10.00 | 10 |
271
270
| InvoiceTotal | number | Total new charges associated with this invoice | $110.00 | 110 |
272
271
| AmountDue | number | Total Amount Due to the vendor | $610.00 | 610 |
@@ -298,7 +297,7 @@ The JSON output has three parts:
298
297
299
298
*`"readResults"` node contains all of the recognized text and selection marks. Text is organized by page, then by line, then by individual words.
300
299
*`"pageResults"` node contains the tables and cells extracted with their bounding boxes, confidence, and a reference to the lines and words in "readResults".
301
-
*`"documentResults"` node contains the invoice-specific values and line items that the model discovered. It's where you'll find all the fields from the invoice such as invoice ID, ship to, bill to, customer, total, line items and lots more.
300
+
*`"documentResults"` node contains the invoice-specific values and line items that the model discovered. It's where to find all the fields from the invoice such as invoice ID, ship to, bill to, customer, total, line items and lots more.
Copy file name to clipboardExpand all lines: articles/applied-ai-services/form-recognizer/concept-receipt.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ manager: nitinme
7
7
ms.service: applied-ai-services
8
8
ms.subservice: forms-recognizer
9
9
ms.topic: conceptual
10
-
ms.date: 01/25/2023
10
+
ms.date: 02/13/2023
11
11
ms.author: lajanuar
12
12
recommendations: false
13
13
---
@@ -84,7 +84,7 @@ The following tools are supported by Form Recognizer v2.1:
84
84
85
85
### Try receipt data extraction
86
86
87
-
See how data, including time and date of transactions, merchant information, and amount totals, is extracted from receipts. You'll need the following resources:
87
+
See how data, including time and date of transactions, merchant information, and amount totals, is extracted from receipts. You need the following resources:
88
88
89
89
* An Azure subscription—you can [create one for free](https://azure.microsoft.com/free/cognitive-services/)
90
90
@@ -141,7 +141,7 @@ See how data, including time and date of transactions, merchant information, and
141
141
142
142
:::image type="content" source="media/fott-select-form-type.png" alt-text="Screenshot of the select-form-type dropdown menu.":::
143
143
144
-
1. Select **Run analysis**. The Form Recognizer Sample Labeling tool will call the Analyze Prebuilt API and analyze the document.
144
+
1. Select **Run analysis**. The Form Recognizer Sample Labeling tool calls the Analyze Prebuilt API and analyze the document.
145
145
146
146
1. View the results - see the key-value pairs extracted, line items, highlighted text extracted and tables detected.
147
147
@@ -164,11 +164,13 @@ The receipt model supports all English receipts and the following locales:
164
164
|Supported Languages| Details |
165
165
|:-----|:----:|
166
166
|• English| United States (-us), Australia (-au), Great Britain (-gb), India (-in), United Arab Emirates (-ae)|
167
-
|• Dutch| Netherlands (nl)|
168
-
|• French | France (fr) |
169
-
|• Japanese | Japan (ja)|
170
-
|• Portuguese| Portugal (-pt), Brazil (-br)|
171
-
|• Spanish | Spain (es) |
167
+
|• Dutch| Netherlands (nl-nl)|
168
+
|• French | France (fr-fr), Canada (fr-ca) |
169
+
|• German | Germany (de-de) |
170
+
|• Italian | Italy (it-it) |
171
+
|• Japanese | Japan (ja-ja)|
172
+
|• Portuguese| Portugal (pt-pt), Brazil (pt-br)|
Copy file name to clipboardExpand all lines: articles/applied-ai-services/form-recognizer/language-support.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ manager: nitinme
7
7
ms.service: applied-ai-services
8
8
ms.subservice: forms-recognizer
9
9
ms.topic: reference
10
-
ms.date: 01/25/2023
10
+
ms.date: 02/13/2023
11
11
ms.author: lajanuar
12
12
---
13
13
@@ -223,17 +223,18 @@ Language| Locale code |
223
223
>[!NOTE]
224
224
> It's not necessary to specify a locale. This is an optional parameter. The Form Recognizer deep-learning technology will auto-detect the language of the text in your image.
225
225
226
-
Receipt supports all English receipts and the following locales:
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments