Skip to content

Commit a491431

Browse files
Merge pull request #246045 from BemaBonsu/main
Update concept-invoice.md
2 parents 46b667c + 625dc23 commit a491431

File tree

1 file changed

+54
-2
lines changed

1 file changed

+54
-2
lines changed

articles/ai-services/document-intelligence/concept-invoice.md

Lines changed: 54 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ monikerRange: '<=doc-intel-3.0.0'
2424
[!INCLUDE [applies to v2.1](includes/applies-to-v2-1.md)]
2525
::: moniker-end
2626

27-
The Document Intelligence invoice model uses powerful Optical Character Recognition (OCR) capabilities to analyze and extract key fields and line items from sales invoices, utility bills, and purchase orders. Invoices can be of various formats and quality including phone-captured images, scanned documents, and digital PDFs. The API analyzes invoice text; extracts key information such as customer name, billing address, due date, and amount due; and returns a structured JSON data representation. The model currently supports both English and Spanish invoices.
27+
The Document Intelligence invoice model uses powerful Optical Character Recognition (OCR) capabilities to analyze and extract key fields and line items from sales invoices, utility bills, and purchase orders. Invoices can be of various formats and quality including phone-captured images, scanned documents, and digital PDFs. The API analyzes invoice text; extracts key information such as customer name, billing address, due date, and amount due; and returns a structured JSON data representation. The model currently supports invoices in 27 languages.
2828

2929
**Supported document types:**
3030

@@ -174,6 +174,58 @@ See how data, including customer information, vendor details, and line items, is
174174
| &bullet; Italian (it) | Italy (it)|
175175
| &bullet; Portuguese (pt) | Portugal (pt), Brazil (br)|
176176
| &bullet; Dutch (nl) | Netherlands (nl)|
177+
| &bullet; Czech (cs) | Czechoslovakia (cz)|
178+
| &bullet; Danish (da) | Denmark (dk)|
179+
| &bullet; Estonian (et) | Estonia (ee)|
180+
| &bullet; Finnish (fi) | Finland (fl)|
181+
| &bullet; Croation (hr) | Bosnia and Herzegovina (ba), Croatia (hr), Serbia (rs)|
182+
| &bullet; Hungarian (hu) | Hungary (hu)|
183+
| &bullet; Icelandic (is) | Iceland (is)|
184+
| &bullet; Japanese (ja) | Japan (ja)|
185+
| &bullet; Korean (ko) | Korea (kr)|
186+
| &bullet; Lithuanian (lt) | Lithuania (lt)|
187+
| &bullet; Latvian (lv) | Latvia (lv)|
188+
| &bullet; Malay (ms) | Malasia (ms)|
189+
| &bullet; Norwegian (nb) | Norway (no)|
190+
| &bullet; Polish (pl) | Poland (pl)|
191+
| &bullet; Romanian (ro) | Romania (ro)|
192+
| &bullet; Slovak (sk) | Slovakia (sv)|
193+
| &bullet; Slovenian (sl) | Slovenia (sl)|
194+
| &bullet; Serbian (sr-Latn) | Serbia (latn-rs)|
195+
| &bullet; Albanian (sq) | Albania (al)|
196+
| &bullet; Swedish (sv) | Sweden (se)|
197+
| &bullet; Chinese (simplified (zh-hans) | China (zh-hans-cn)|
198+
| &bullet; Chinese (traditional (zh-hant) | Hong Kong (zh-hant-hk), Taiwan (zh-hant-tw)|
199+
200+
| Supported Currency Codes | Details |
201+
|:----------------------|:---------|
202+
| &bullet; ARS | United States (us) |
203+
| &bullet; AUD | Australia (au) |
204+
| &bullet; BRL | United States (us) |
205+
| &bullet; CAD | Canada (ca) |
206+
| &bullet; CLP | United States (us) |
207+
| &bullet; CNY | United States (us) |
208+
| &bullet; COP | United States (us) |
209+
| &bullet; CRC | United States (us) |
210+
| &bullet; CZK | United States (us) |
211+
| &bullet; DKK | United States (us) |
212+
| &bullet; EUR | United States (us) |
213+
| &bullet; GBP | United Kingdom (uk) |
214+
| &bullet; HUF | United States (us) |
215+
| &bullet; IDR | United States (us) |
216+
| &bullet; INR | United States (us) |
217+
| &bullet; ISK | United States (us) |
218+
| &bullet; JPY | Japan (jp) |
219+
| &bullet; KRW | United States (us) |
220+
| &bullet; NOK | United States (us) |
221+
| &bullet; PAB | United States (us) |
222+
| &bullet; PEN | United States (us) |
223+
| &bullet; PLN | United States (us) |
224+
| &bullet; RON | United States (us) |
225+
| &bullet; RSD | United States (us) |
226+
| &bullet; SEK | United States (us) |
227+
| &bullet; TWD | United States (us) |
228+
| &bullet; USD | United States (us) |
177229

178230
## Field extraction
179231

@@ -234,7 +286,7 @@ The invoice key-value pairs and line items extracted are in the `documentResults
234286

235287
### Key-value pairs
236288

237-
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.
289+
The prebuilt invoice **2022-06-30** and later releases support the optional return of key-value pairs. By defualt the return of key-value pairs is disabled. 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.
238290

239291
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).
240292

0 commit comments

Comments
 (0)