---
sourceDocument: Australia Finance and Supply Chain
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/source-to-pay-operations

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Finance and Supply Chain

ft:clusterId :

    - stpop

bundleId :

    - stpop

workflow :

    - Employee


---

# How Accounts Payable Operations integration with Document Intelligence works

# How Accounts Payable Operations integration with Document Intelligence works {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of How Accounts Payable Operations integration with Document Intelligence works

The integration between Accounts Payable Operations and Document Intelligence automates the extraction of invoice data from email attachments to streamline invoice processing.
When invoices are received via email, Document Intelligence uses automated workflows to extract data, create invoice records, and initiate invoice processing within Accounts Payable Operations.
Show full answer Show less  

## Invoice Ingestion Process Flow

The process varies based on the confidence level of data extraction by Document Intelligence:

* **High extraction confidence:** Document Intelligence extracts invoice data, stores it in staging tables, and creates an invoice in Draft state linked to an invoice processing case. The system verifies required fields and invoice lines. If fields or lines are missing, the Accounts Payable Specialist must manually enter missing data before submitting the invoice. Currency codes are derived from purchase orders or user locale if missing, with manual correction required if necessary. Upon submission, the invoice state changes to Received, triggering further processing.
* **Low extraction confidence:** No invoice is created automatically. An invoice processing case is created with an error message. The Accounts Payable Specialist must review the invoice in Document Intelligence, enter required data, and submit it. The subsequent steps mirror the high confidence flow, including verification and manual corrections as needed.
* **Transformation failure:** If the entire Document Intelligence transformation process fails, an error message prompts contacting the administrator to resolve the issue.

## Key Requirements and Validation

* Mandatory invoice and invoice line fields must be populated for invoice creation.
* Currency codes are validated and transformed using purchase order data or user locale settings.
* The integration enforces data formats compatible with downstream processing systems.

## Localization

Accounts Payable Operations supports multiple languages, but the current Document Intelligence model is trained only for English invoice extraction. Customers needing multi-lingual invoice processing must train their own Document Intelligence models accordingly.

## Practical Implications for ServiceNow Customers

* This integration significantly reduces manual data entry by automating invoice data capture and processing.
* Accounts Payable Specialists play a critical role in handling exceptions when extraction confidence is low or data is incomplete.
* Understanding required fields and currency transformation logic helps ensure accurate invoice processing and compliance with accounting standards.
* Administrators should be prepared to troubleshoot transformation failures and support Document Intelligence model training for multi-language needs.  
Document Intelligence uses automated workflows to extract invoice data from email attachments and populate invoice records in Accounts Payable Operations.

## Invoice ingestion process flow when extraction confidence is high {#apm-docintel-how-it-works__section_e2q_nps_xvb}

When you receive an invoice as an attachment via email from a supplier or an employee, the following occurs:

1. An invoice case is created with category Invoice automation and subcategory Invoice processing in Accounts Payable Operations.
2. If Document Intelligence determines that the extraction confidence is higher than the threshold value, it extracts the invoice data and stores the data in temporary staging tables.
3. The Document Intelligence transformation process imports the invoice data from the staging tables, creates an invoice in the Draft state, and associates the invoice with the invoice processing case.
4. The application verifies the following:
   * The required fields are populated on the invoice.
     * If the required fields aren't populated on the invoice, the Accounts Payable Specialist is required to open the invoice, manually enter the required values in the required fields, and submit the invoice.
     * If the required fields are populated on the invoice, the invoice is auto-submitted.
     {#apm-docintel-how-it-works__ul_l3v_myf_jwb}
   * At least one invoice line record exists for the invoice. If not, the Accounts Payable Specialist must add an invoice line record and submit the invoice.
   * If a unique currency code isn't identified during currency transformation, the process uses the currency mentioned in the purchase order. If the currency is missing in the purchase order, the transformation process uses the session currency based on the user's locale. In this case, the Accounts Payable Specialist is required to open the invoice processing case, and enter the correct currency code in the invoice fields and submit the invoice. For more information, see [Invoice data transformation logic](https://www.servicenow.com/docs/aa_LTZ1vvfKCy9rFa2utwg "Accounts Payable Operations integration with Document Intelligence transforms invoice and invoice line field values into formats supported by downstream processing systems.").

   {#apm-docintel-how-it-works__ul_hfw_vfk_zwb}

   For more information about the required fields for invoice and invoice lines, see [Required fields for creating an invoice](https://www.servicenow.com/docs/6cif7OsFCpmIMf~l5ENlvg "Mandatory invoices and invoice lines fields that the Accounts Payable Operations integration with Document Intelligence application checks before creating an invoice.").

   After the invoice is submitted, its state changes to Received. The invoice processing begins from this point. For more information, see [Work on an invoice processing case](https://www.servicenow.com/docs/dIq71E7tYkNFcZbp1DVPig "Perform manual actions to review, update, and resolve invoice processing issues during the invoice lifecycle.").
{#apm-docintel-how-it-works__ol_dwh_kxq_lvb}

## Invoice ingestion process flow when extraction confidence is low {#apm-docintel-how-it-works__section_tmk_fng_hwb}

When you receive an invoice as an attachment via email from a supplier or an employee, the following occurs:

1. An invoice case is created with category Invoice automation and subcategory Invoice processing in Accounts Payable Operations.{#apm-docintel-how-it-works__ip-case-low}
{#apm-docintel-how-it-works__ip-case-low}
2. If Document Intelligence determines that the extraction confidence is lower than the threshold value, it doesn't extract the invoice data and as a consequence an invoice isn't created.
3. In this scenario, the Accounts Payable Specialist must do the following:
   1. Open the invoice processing case created in Step1.The case displays the following error message: Invoice has a data extraction error. Review invoice with automation to continue processing.

   2. Select Review invoice, which opens Document Intelligence and displays the invoice fields.
   3. Enter the required values into the invoice fields, and select Submit.
   {#apm-docintel-how-it-works__ol_mbf_5tg_hwb}
4. The Document Intelligence transformation process imports the invoice data from the staging tables, creates an invoice in the Draft state, and associates the invoice with the invoice processing case.
5. The application verifies the following:
   * The required fields are populated on the invoice.
     * If the required fields aren't populated on the invoice, the Accounts Payable Specialist is required to open the invoice, manually enter the required values in the required fields, and submit the invoice.
     * If the required fields are populated on the invoice, the invoice is auto-submitted.
     {#apm-docintel-how-it-works__ul_kcz_g3k_zwb}
   * At least one invoice line record exists for the invoice. If not, the Accounts Payable Specialist must add an invoice line record and submit the invoice.
   * A unique currency code exists on the invoice. If a unique currency code isn't identified during currency transformation, the process uses the currency mentioned in the purchase order. If the currency is missing in the purchase order, then the transformation process uses the session currency based on the user's locale. In this case, the Accounts Payable Specialist is required to open the invoice processing case and enter the correct currency code in the invoice fields and submit the invoice. For more information, see [Invoice data transformation logic](https://www.servicenow.com/docs/aa_LTZ1vvfKCy9rFa2utwg "Accounts Payable Operations integration with Document Intelligence transforms invoice and invoice line field values into formats supported by downstream processing systems.").

   {#apm-docintel-how-it-works__ul_jcz_g3k_zwb}

   For more information about the required fields for invoice and invoice lines, see [Required fields for creating an invoice](https://www.servicenow.com/docs/6cif7OsFCpmIMf~l5ENlvg "Mandatory invoices and invoice lines fields that the Accounts Payable Operations integration with Document Intelligence application checks before creating an invoice.").

   After the invoice is submitted, its state changes to Received. The invoice processing begins from this point. For more information, see [Work on an invoice processing case](https://www.servicenow.com/docs/dIq71E7tYkNFcZbp1DVPig "Perform manual actions to review, update, and resolve invoice processing issues during the invoice lifecycle.").
{#apm-docintel-how-it-works__ol_rd3_xvj_lwb}

## Invoice ingestion process flow when the entire transformation process fails {#apm-docintel-how-it-works__section_hc5_fbq_kwb}

When the Document Intelligence transformation process fails entirely, the following error message is displayed on the invoice processing case:

Invoice automation is experiencing issues. Please contact the administrator.

You must collaborate with the administrator to resolve this issue.

## Localization information {#apm-docintel-how-it-works__section_ztw_3fk_2cc}


Accounts Payable Operations supports multiple languages. The current DocIntel model is trained to extract invoices in the English language only. If you want to process the invoice in multi-lingual languages supported by DocIntel, you must train the DocIntel model on your own.

For more information on Document Intelligence, see [Document Intelligence (Legacy)](https://www.servicenow.com/docs/access?context=document-intelligence-landing&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US).
* **[Required fields for creating an invoice](https://www.servicenow.com/docs/6cif7OsFCpmIMf~l5ENlvg)**   
  Mandatory invoices and invoice lines fields that the Accounts Payable Operations integration with Document Intelligence application checks before creating an invoice.
* **[Invoice data transformation logic](https://www.servicenow.com/docs/aa_LTZ1vvfKCy9rFa2utwg)**   
  Accounts Payable Operations integration with Document Intelligence transforms invoice and invoice line field values into formats supported by downstream processing systems.

