An invoice, bill or tab is a commercial document issued by a seller to a buyer, relating to a sale transaction and indicating the products, quantities, and agreed prices for products or services the seller had provided the buyer.
Payment terms are usually stated on the invoice. These may specify that the buyer has a maximum number of days in which to pay and is sometimes offered a discount if paid before the due date. The buyer could have already paid for the products or services listed on the invoice. To avoid confusion, and consequent unnecessary communications from buyer to seller, some sellers clearly state in large and/or capital letters on an invoice whether it has already been paid.
Nearly 80% of invoice payments arrive within one day of sending the invoice. And, after your customer pays, your money is generally in your PayPal account within minutes. Get started by clicking the Preview and Send button at the top right of this page - we’ll generate an invoice. Use Google, Facebook, Windows live, Yahoo or your email to sign in. Don't have an Invoice Home account yet? No worries, joining is easy. Invocie2go is the all-in-one solution for small businesses. Manage customer relationships, send professional invoices and estimates, accept payments, improve. An invoice template is a document that makes it simple to create new invoices. An invoice template outlines the necessary fields included on an invoice. Use the fillable invoice template to create an invoice by completing the blank fields in the template with your business, sale, and customer information. What do you write on an invoice? Invoices do more than ensure you get paid. They’re also an effective way to showcase your brand. As possibly the last touchpoint you’ll have with a customer, it’s important to leave a positive impression with a clean, professional-looking document. Bill clients using visually appealing documents with Canva’s invoices templates.
From the point of view of a seller, an invoice is a sales invoice. From the point of view of a buyer, an invoice is a purchase invoice. The document indicates the buyer and seller, but the term invoice indicates money is owed or owing.
Within the European union, an invoice is primarily legally defined by the EU VAT directive as an accounting voucher (to verify tax and VAT reporting) and secondly as a Civil law (common law) document.
History[edit]
Invoices appear as one of the very earliest manifestations of written records in ancient Mesopotamia.[1]
Invoices[edit]
I N V O I C E Company Name 123 Fake Street Springfield | |||||
---|---|---|---|---|---|
Invoice No | Terms | ||||
Description | Amount Owed: | ||||
Invoice Total | [Currency] |
A typical invoice may contain:[2][3]
- The word invoice (or tax invoice);
- A unique reference-number (in case of correspondence about the invoice);
- Date of the invoice;
- Credit terms;
- Tax amounts, if relevant (e.g., GST or VAT);
- Name and contact details of the seller;
- Tax or company registration details of the seller, if relevant e.g. ABN for Australian businesses or VAT number for businesses in the EU;
- Name and contact details of the buyer;
- Date of sending or delivery of the goods or service;
- Purchase-order number (or similar tracking numbers requested by the buyer to be mentioned on the invoice);
- Description of the product(s);
- Unit price(s) of the product(s), if relevant;
- Total amount charged with currency (symbol or abbreviation);
- Payment terms (including one or more acceptable methods of payment, date the payment is expected, and details about charges for late payments, i.e. payments made after this date);
In countries where wire transfer is the preferred method of settling debts, the printed bill will contain the bank account number of the creditor and usually a reference code to be passed along with the transaction identifying the payer.
The US Defense Logistics Agency requires an employer identification number on invoices.[4]
The European Union requires a VAT (value added tax) identification number for official VAT invoices, which all VAT-registered businesses are required to issue to their customers. In the UK, this number may be omitted on invoices if the words 'this is not a VAT invoice' are present on the invoice. Such an invoice is called a pro-forma invoice, and is not an adequate substitute for a full VAT invoice for VAT-registered customers.[5]
In Canada, the registration number for GST purposes must be furnished for all supplies over $30 made by a registered supplier in order to claim input tax-credits.[6]
Recommendations about invoices used in international trade are also provided by the UNECE Committee on Trade, which involves a more detailed description of the logistics aspect of merchandise and therefore may be convenient for international logistics and customs procedures.[7]
European Union[edit]
EU VAT union invoice definition[edit]
Within the European Union Value Added Tax directive,[8] Article 226 gives a concise definition of invoices within the European Union's member-states.
Without prejudice to the particular provisions laid down in this Directive, only the following details are required for VAT purposes on invoices issued pursuant to Articles 220 and 221:
- the date of issue;
- a sequential number, based on one or more series, which uniquely identifies the invoice;
- the VAT identification number referred to in Article 214 under which the taxable person supplied the goods or services;
- the customer's VAT identification number, as referred to in Article 214, under which the customer received a supply of goods or services in respect of which he is liable for payment of VAT, or received a supply of goods as referred to in Article 138;
- the full name and address of the taxable person and of the customer;
- the quantity and nature of the goods supplied or the extent and nature of the services rendered;
- the date on which the supply of goods or services was made or completed or the date on which the payment on account referred to in points (4) and (5) of Article 220 was made, in so far as that date can be determined and differs from the date of issue of the invoice;
- where the VAT becomes chargeable at the time when the payment is received in accordance with Article 66(b) and the right of deduction arises at the time the deductible tax becomes chargeable, the mention ‘cash accounting’;
- the taxable amount per rate or exemption, the unit price exclusive of VAT and any discounts or rebates if they are not included in the unit price;
- the VAT rate applied;
- the VAT amount payable, except where a special arrangement is applied under which, in accordance with this Directive, such a detail is excluded;
- where the customer receiving the supply issues the invoice (instead of the supplier) the mention 'self-billing';
- in the case of an exemption, reference to the applicable provision of this Directive, or to the corresponding national provision, or any other reference indicating that the supply of goods or services is exempt;
- where the customer is liable for the payment of the VAT, the mention 'reverse charge';
- in the case of the supply of a new means of transport made in accordance with the conditions specified in Article 138(1) and (2)(a), the characteristics as identified in point (b) of Article 2(2);
- where the margin scheme for travel agents is applied, the mention 'margin scheme – travel agents';
- where one of the special arrangements applicable to second-hand goods, works of art, collectors' items and antiques is applied, the mention 'margin scheme – second-hand goods'; 'margin scheme – works of art' or 'margin scheme – collector's items and antiques' respectively;
- where the person liable for payment of VAT is a tax representative for the purposes of Article 204, the (VAT identification number, referred to in Article 214, of that tax representative, together with his full name and address.
EU VAT union receipt (simple invoice) definition[edit]
Article 226b of the EU VAT Directive is a concise definition of receipts within the EU member-states.
As regards simplified invoices issued pursuant to Article 220a and Article 221(1) and (2), Member States shall require at least the following details:
- the date of issue;
- identification of the taxable person supplying the goods or services (VAT identification number);
- identification of the type of goods or services supplied;
- the VAT amount payable or the information needed to calculate it;
- where the invoice issued is a document or message treated as an invoice pursuant to Article 219, specific and unambiguous reference to that initial invoice and the specific details which are being amended.
They may not require details on invoices other than those referred to in Articles 226, 227 and 230.
Australian Tax Office Tax invoice definition[edit]
Details about the Australian Tax Office (ATO) requirements for a tax invoice can be found on their website.[9][10]
For all GST purposes, a seller must issue a tax invoice to the buyer regardless of whether the sale involves cash or credit. Hence a tax invoice in Australia serves as an invoice as well as a receipt in the conventional sense. The words 'paid' or 'payable' differentiate meaning. The tax invoice must contain seven facts as per the GST Tax Law.
Variations[edit]
There are different types of invoices:
- Pro forma invoice – In foreign trade, a pro forma invoice is a document that states a commitment from the seller to provide specified goods to the buyer at specific prices. It is often used to declare value for customs. It is not an actual invoice, and thus the seller does not record a pro forma invoice as an account receivable and the buyer does not record a pro forma invoice as an account payable. A pro forma invoice is not issued by the seller until the seller and buyer have agreed to the terms of the order. In a few cases, a pro forma invoice is issued to request advance payments from the buyer, either to allow production to start or for security of the goods produced.
- Credit memo - If the buyer returns the goods, the seller usually issues a credit memo for the same or lower amount than the invoice, and then refunds the money to the buyer, or the buyer can apply that credit memo to another invoice.
- Commercial invoice - a customs declaration form used in international trade that describes the parties involved in the shipping transaction, the goods being transported, and the value of the goods.[11] It is the primary document used by customs, and must meet specific customs requirements, such as the Harmonized System number and the country of manufacture. It is used to calculate tariffs.
- Debit memo - When a company fails to pay or short-pays an invoice, it is common practice to issue a debit memo for the balance and any late fees owed. In function, debit memos are identical to invoices.
- Self-billing invoice - A self billing invoice is used when a buyer issues the invoice to themselves (e.g. according to the consumption levels he is taking out of a vendor-managed inventory stock).[12] The buyer (i.e. the issuer) should treat the invoice as an account payable and the seller should treat it as an account receivable. If there is tax on the sale, e.g. VAT or GST, then the buyer and seller may need to adjust their tax accounts in accordance with tax legislation.[13] Under Article 224 of the EU VAT Directive, self-billing processes may only be used 'if there is a prior agreement between the two parties and provided that a procedure exists for the acceptance of each invoice' by the supplier.[14] A Self-Billing Agreement will usually provide for the supplier not to issue their own sales invoices as well.[15]
- Evaluated receipt settlement (ERS) - ERS is a process of paying for goods and services from a packing slip rather than from a separate invoice document. The payee uses data in the packing slip to apply for the payments. 'In an ERS transaction, the supplier ships goods based upon an Advance Shipping Notice (ASN), and the purchaser, upon receipt, confirms the existence of a corresponding purchase order or contract, verifies the identity and quantity of the goods, and then pays the supplier.'[16]
- Timesheet - Invoices for hourly services issued by businesses such as lawyers and consultants often pull data from a timesheet. A timesheet invoice may also be generated by Operated equipment rental companies where the invoice will be a combination of timesheet based charges and equipment rental charges.
- Statement - A periodic customer statement includes opening balance, invoices, payments, credit memos, debit memos, and ending balance for the customer's account during a specified period. A monthly statement can be used as a summary invoice to request a single payment for accrued monthly charges.
- Progress billing used to obtain partial payment on extended contracts, particularly in the construction industry (see Schedule of values)
- Collective Invoicing is also known as monthly invoicing in Japan. Japanese businesses tend to have many orders with small amounts because of the outsourcing system (Keiretsu), or of demands for less inventory control (Kanban). To save the administration work, invoicing is normally processed on monthly basis.
- Continuation or Recurring Invoicing is standard within the equipment rental industry, including tool rental. A recurring invoice is one generated on a cyclical basis during the lifetime of a rental contract. For example, if you rent an excavator from 1 January to 15 April, on a calendar monthly arrears billing cycle, you would expect to receive an invoice at the end of January, another at the end of February, another at the end of March and a final Off-rent invoice would be generated at the point when the asset is returned. The same principle would be adopted if you were invoiced in advance, or if you were invoiced on a specific day of the month.
- Electronic Invoicing is not necessarily the same as EDI invoicing. Electronic invoicing in its widest sense embraces EDI as well as XML invoice messages as well as other formats such as pdf. Historically, other formats such as pdf were not included in the wider definition of an electronic invoice because they were not machine readable and the process benefits of an electronic message could not be achieved. However, as data extraction techniques have evolved and as environmental concerns have begun to dominate the business case for the implementation of electronic invoicing, other formats are now incorporated into the wider definition.
Electronic[edit]
Some invoices are no longer paper-based, but rather transmitted electronically over the Internet. It is still common for electronic remittance or invoicing to be printed in order to maintain paper records. Standards for electronic invoicing vary widely from country to country. Electronic Data Interchange (EDI) standards such as the United Nation's EDIFACT standard include message encoding guidelines for electronic invoices. The EDIFACT is followed up in the UN/CEFACTebXML syntax cross industry invoice.
EDIFACT[edit]
The United Nations standard for electronic invoices ('INVOIC') includes standard codes for transmitting header information (common to the entire invoice) and codes for transmitting details for each of the line items (products or services). The 'INVOIC' standard can also be used to transmit credit and debit memos.
In the European Union legislation was passed in 2010 in the form of directive 2010/45/EU to facilitate the growth of Electronic Invoicing across all its member states. This legislation caters for varying VAT and inter-country invoicing requirements within the EU, in addition to legislating for the authenticity and integrity of invoices being sent electronically. It is estimated that in 2011 alone roughly 5 million EU businesses will have sent Electronic Invoices.[17]
Open Application Group Integration Specification from OAGi[edit]
The XML message format for electronic invoices has been used since the inception of XML in 1998. Open Application Group Integration Specification (OAGIS) has included an invoice since 2001. The Open Applications Group (OAGi) has a working relationship with UN/CEFACT where OAGi and its members participate in defining many of the Technology and Methodology specifications. OAGi also includes support for these Technology and Methodology specifications within OAGIS.
CEFACT and UBL[edit]
There are two XML-based standards currently being developed. One is the cross industry invoice under development by the United Nations standards body UN/CEFACT and the other is Universal Business Language (UBL) which is issued by Organization for the Advancement of Structured Information Standards (OASIS). Implementations of invoices based on UBL are common, most importantly in the public sector in Denmark as it was the first country where the use of UBL was mandated by law for all invoices in the public sector. Further implementations are underway in the Scandinavian countries as result of the North European Subset project. Implementations are also underway in Italy, Spain, and the Netherlands (UBL 2.0)[18] and with the European Commission itself.
The NES work has been transferred to European Committee for Standardization (CEN), the standards body of the European Union), workshop CEN/BII, for public procurement in Europe. The result of that work is PEPPOL. There UBL procurement documents are implemented between various European countries.
An agreement was made between UBL and UN/CEFACT for convergence of the two XML messages standards with the objective of merging the two standards into one before end of 2009, including the provision of an upgrade path for implementations started in either standard.
ISDOC[edit]
ISDOC is a standard that was developed in the Czech Republic as a universal format for electronic invoices. On 16 October 2008, 14 companies and the Czech government signed a declaration to use this format within one year in their products.
Payment[edit]
Organizations purchasing goods and services usually have a process in place for approving payment of invoices based on an employee's confirmation that the goods or services have been received.[19][20][21][22]
Typically, when paying an invoice, a remittance advice will be sent to the supplier to inform them their invoice has been paid.
Standardization[edit]
Invoices are different from receipts. Both invoices and receipts are ways of tracking purchases of goods and services. In general the content of the invoices can be similar to that of receipts including tracking the amount of the sale, calculating sales tax owed and calculating any discounts applied to the purchase.[23] Invoices differ from receipts in that invoices serve to notify customers of payments owed, whereas receipts serve as proof of completed payment.
Invoice finance[edit]
Invoice credit is a line of business credit secured by customer invoices.
See also[edit]
References[edit]
- ^McClellan III, James E.; Dorn, Harold (2006). Science and Technology in World History: An Introduction (2 ed.). Baltimore: The Johns Hopkins University Press. p. 47. ISBN9780801883606. Retrieved 21 April 2020.
The archaeological discovery of what amount to ancient Mesopotamian invoices — insignia sealed in clay — underscores the economic and utilitarian roots of writing and reckoning. Eighty-five percent of cuneiform tablets uncovered at Uruk (3000 BCE), for example, represent economic records, and Egyptian temple and palace records are similar.
- ^Invoice illustration adapted from Meigs and Meigs Financial Accounting 4th Ed. (McGraw-Hill, 1970), p.190 ISBN0-07-041534-X
- ^Woodford, William; Wilson, Valerie; Freeman, Suellen; Freeman, John (2008). Accounting: A Practical Approach (2 ed.). Pearson Education. pp. 4–10. ISBN978-0-409-32357-3.
- ^US Defense Logistics Agency - Required information in invoicesArchived 10 July 2007 at the Wayback Machine
- ^Conn, Frances (15 August 2017). 'VAT Invoice Essentials'. Figure Weave Accountancy. Retrieved 12 May 2019.
- ^Input Tax Credit Information (GST/HST) Regulations, SOR/91-45, at s. 3(b)(i)
- ^Recommendation No. 06: Aligned Invoice Layout Key for International Trade (UN/CEFACT; 2000; 7 pages) ID: ECE/TRADE/148; Topic: Trade Facilitation and e-Business
- ^Council Directive 2006/112/EC of 28 November 2006 on the common system of value added tax
- ^Requirements of tax invoices https://www.ato.gov.au/Business/GST/Issuing-tax-invoices/
- ^How to set out tax invoices and invoices 'Archived copy'. Archived from the original on 9 February 2015. Retrieved 18 January 2015.CS1 maint: archived copy as title (link)
- ^DHL | Global | Customs PaperworkArchived 17 April 2015 at the Wayback Machine
- ^ControlPay, Self-billing, accessed 26 April 2018
- ^HMRC. 'Self-billing and VAT'.
- ^Consolidated VAT Directive, 2006, Article 224
- ^Notice 700/62 - Self-billing)
- ^SCM | What is Evaluated Receipt Settlement?
- ^The European Electronic Invoicing ExpertsArchived 11 January 2012 at the Wayback Machine
- ^'Elektronisch factureren' (in Dutch). Government of the Netherlands. Archived from the original on 22 November 2011. Retrieved 5 January 2012.
- ^Michigan state Bureau of Transportation Invoice processing
- ^US Department of the Navy Commercial Invoice Payments History SystemArchived 3 July 2007 at the Wayback Machine
- ^Commercial Contracting Guidelines - US Defense Contract Management AgencyArchived 26 June 2007 at the Wayback Machine
- ^US Office of Federal Procurement Policy - Best Practices for Contract AdministrationArchived 12 June 2007 at the Wayback Machine
- ^'WorkingPoint Help'. Workingpoint.com. Archived from the original on 19 August 2013. Retrieved 24 May 2013.
External links[edit]
Wikimedia Commons has media related to Invoices, bills and receipts. |
Look up invoice in Wiktionary, the free dictionary. |
[This topic is pre-release documentation and is subject to change.]
The invoice processing prebuilt AI model extracts key invoice data to help automate the processing of invoices. The invoice processing model is optimized to recognize common invoice elements like invoice ID, invoice date, amount due and more.
Use in Power Apps
For information on how to use the invoice processing prebuilt model in Power Automate, see Use the invoice processing prebuilt model in Power Apps.
Use in Power Automate
For information on how to use the invoice processing prebuilt model in Power Automate, see Use the invoice processing prebuilt model in Power Automate.
Supported languages and files
Invoice Download
Only English invoices from the United States are currently supported.
To get the best results, provide one clear photo or scan per invoice.
- The image format must be JPEG, PNG, or PDF.
- The file size must be less than 20 MB.
- The image dimensions must be between 50 x 50 pixels and 10,000 x 10,000 pixels.
- PDF dimensions must be at most 17 x 17 inches, which is the equivalent of the Legal or A3 paper sizes or smaller.
Model output
If an invoice is detected, the invoice processing model will output the following information:
Property | Definition |
---|---|
Amount due (text) | Amount due as written on the invoice |
Amount due (number) | Amount due in standardized number format. Example: 1234.98 |
Confidence of amount due | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Billing address | Billing address |
Confidence of billing address | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Billing address recipient | Billing address recipient |
Confidence of billing address recipient | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Customer address | Customer address |
Confidence of customer address | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Customer address recipient | Customer address recipient |
Confidence of customer address recipient | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Customer ID | Customer ID |
Confidence of customer ID | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Customer name | Customer name |
Confidence of customer name | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Due date (text) | Due date as written on the invoice |
Due date (date) | Due date in standardized date format. Example: 2019-05-31 |
Confidence of due date | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Invoice date (text) | Invoice date as written on the invoice |
Invoice date (date) | Invoice date in standardized date format. Example: 2019-05-31 |
Confidence of invoice date | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Invoice ID | Invoice ID |
Confidence of invoice ID | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Invoice total (text) | Invoice total as written on the invoice |
Invoice total (number) | Invoice total in standardized date format. Example: 2019-05-31 |
Confidence of invoice total | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Purchase order | Purchase order |
Confidence of purchase order | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Remittance address | Remittance address |
Confidence of remittance address | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Remittance address recipient | Remittance address recipient |
Confidence of remittance address recipient | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Service address | Service address |
Confidence of service address | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Service address recipient | Service address recipient |
Confidence of service address recipient | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Shipping address | Shipping address |
Confidence of shipping address | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Shipping address recipient | Shipping address recipient |
Confidence of shipping address recipient | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Subtotal (text) | Subtotal as written on the invoice |
Subtotal (number) | Subtotal in standardized number format. Example: 1234.98 |
Confidence of subtotal | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Total tax (text) | Total tax as written on the invoice |
Total tax (number) | Total tax in standardized number format. Example: 1234.98 |
Confidence of total tax | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Vendor address | Vendor address |
Confidence of vendor address | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Vendor address recipient | Vendor address recipient |
Confidence of vendor address recipient | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Vendor name | Vendor name |
Confidence of vendor name | How confident the model is in its prediction. Score between 0 (low confidence) and 1 (high confidence). |
Detected text | Line of recognized text from running OCR on an invoice. Returned as a part of a list of text. |
Page number of detected text | Page on which the line of recognized text was found. Returned as a part of a list of text. |
Note
Extraction of line items and invoice tables is currently not supported.
Limits
The following applies to calls made per environment across form processing models including prebuilt models: receipt processing and invoice processing.
Action | Limit | Renewal period |
---|---|---|
Calls (per environment) | 360 | 60 seconds |
Create a custom invoice processing solution
The invoice processing prebuilt AI model is designed to extract common fields found in invoices. Because every business is unique, you might want to extract fields other than those included in this prebuilt model. It can also be the case that some standard fields are not well extracted for a particular type of invoice you work with. To address this, there are two options:
- View raw OCR results: Every time the invoice processing prebuilt AI model processes a file you provide, it also does an OCR operation to extract every word written on the file. You can access the raw OCR results on the detected text output provided by the model. A simple search on the content returned by detected text might be enough to get the data you need.
- Use form processing: With AI Builder, you can also build your own custom AI model to extract specific fields and tables you need for the documents you work with. Just create a form processing model and train it to extract all the information from an invoice that doesn’t work well with the invoice extraction model.
Once you train your custom form processing model, you can combine it with the invoice processing prebuilt model in a Power Automate flow.
Here are some examples:
Use a custom form processing model to extract additional fields that are not returned by the invoice processing prebuilt model
In this example, we have trained a custom form processing model to extract a ‘Loyalty program number’ only present in invoices from providers Adatum and Contoso.
Invoice Generator
The flow is triggered when a new invoice is added to a SharePoint folder. It then calls the invoice processing prebuilt AI model to extract its data. Next, we check if the vendor for the invoice that has been processed is either from ‘Adatum’ or ‘Contoso’. If it’s the case, we then call a custom form processing model that we’ve trained to get that loyalty number. Finally, we save the extracted data from the invoice in an Excel file.
Use a custom form processing model if the confidence score for a field returned by the invoice processing prebuilt model is low
In this example, we have trained a custom form processing model to extract the total amount from invoices where we usually get a low confidence score when using the invoice processing prebuilt model.
The flow is triggered when a new invoice is added to a SharePoint folder. It then calls the invoice processing prebuilt AI model to extract its data. Next, we check if the confidence score for the 'Invoice total value' property is less than 0.65. If it’s the case, we then call a custom form processing model that we’ve trained with invoices where we usually get a low confidence score for the total field. Finally, we save the extracted data from the invoice into an Excel file.
Use the invoice processing prebuilt model to handle invoices that a custom form processing model hasn’t been trained to handle
One way to use the invoice processing prebuilt model is to use it as a fallback model to handle invoices that you haven’t trained in your custom form processing model. For example, let's say you built a form processing model, and trained it to extract data from your top 20 invoice providers. You could then use the invoice processing prebuilt model to process all new invoices or lower volume invoices. Here’s an example of how you could do it:
This flow is triggered when a new invoice is added to a SharePoint folder. It then calls a custom form processing model to extract its data. Next, we check if the confidence score for the detected collection is less than 0.65. If it’s the case, it probably means the provided invoice is not a good match for the custom model, so we then call the prebuilt invoice processing model. Finally we save the extracted data from the invoice in an Excel file.
Note
Invoice Viettel
Can you tell us about your documentation language preferences? Take a short survey.
The survey will take about seven minutes. No personal data is collected (privacy statement).