Nanonets: document processing features and setup

Overview

For invoices and orders, text extraction is only one step toward a valid business record. With Nanonets, define which rule approves a document for the next step and which discrepancy stops it, such as a mismatch between the line-item total and the grand total. The workflow should also distinguish a new document from one submitted again, so reducing manual entry does not create duplicates in the finance system.

Features

• Processing data from business documents
• Invoice and order workflows
• Rules and integrations with business systems

Business uses

• Capturing invoice details and sending them for finance team review
• Converting an order received as a file into a system record

Getting started

• Gather examples of one document type and define the fields that must be validated.
• Check an invoice with several line items, a credit, and a different currency, and compare the subtotals and selected fields with the values accounting expects.
• Submit the same invoice in two different files and check how your system handles the duplicate, including human correction before sending it for recording or approval.

What to check

• Check line item, tax, and currency extraction on documents from your suppliers.
• Route exceptions for human review before creating a payment or making a final update.