> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/2024.1/2024.1-marketplace/enateai-idp-enhanced-invoice-field-detection.md).

# EnateAI IDP - Enhanced Invoice Field Detection

As part of our ongoing efforts for enhancing EnateAI's capabilities in the IDP space, we've expanded the **Invoice Model's** awareness by integrating **twenty commonly used fields** into the data extraction pipeline powered by Azure Form Recognizer (AFR). These fields are designed to capture essential information from invoices, ensuring accurate and consistent data extraction.

With the addition of these fields to the **Invoice Model**, you will now see these fields appear in the Json output file structure even if there is no value to be populated.

This enhancement allows the extracted data to be seamlessly used with any integration tool (e.g., SnapLogic, Azure Data Factory, Power Automate) for slicker processing and automation. In future updates, we plan to expand the list of standard fields further to support other document types.  

We’ve focused on the key pieces of information that typically matter most in financial operations. And while these twenty fields are now standardized, you'll continue to see additional data captured, displayed under **KeyValuePairs** and **Tables**.

Here’s the full list of the standard fields for the **Invoice Model**:

* Invoice Number
* Invoice Date
* Due Date
* Vendor Name
* Vendor Address 
* Vendor Contact
* Customer Name
* Customer Address 
* Customer Contact
* Billing Address
* Shipping Address
* Purchase Order Number
* Terms
* Line Items
* Subtotal
* Tax Amount
* Total Amount 
* Currency
* Notes
* Payment Instructions

This standardized approach ensures better structure, better data consistency and smoother integration across various platforms.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enate.net/whats-new/2024.1/2024.1-marketplace/enateai-idp-enhanced-invoice-field-detection.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.