<\/p>\n
\n Understand how an external OCR or document capture process reads supplier invoices, prepares approved invoice data and the source document for Jobpac, and supports the creation of a Registered Pending Invoice.\n <\/p>\n
\n Optical character recognition (OCR) can reduce manual invoice entry by reading visible information from supplier invoices and converting it into structured data. For Jobpac users, an external OCR or document capture process can prepare approved invoice data and the source document for transfer to Jobpac, where the invoice can become a Registered Pending Invoice.\n <\/p>\n
\n This article explains the workflow, what happens when validation fails, and why OCR alone cannot resolve information that is missing or unclear on the invoice.\n <\/p>\n
\n OCR is the technology used to recognise printed or digital text in an invoice and convert selected values into machine-readable data. An invoice capture solution may use OCR together with document classification, data extraction, validation and verification tools.\n <\/p>\n
\n For a supplier invoice, the captured values may include the supplier name, ABN, invoice number, invoice date, Purchase Order reference, net amount, GST, total amount and selected line information. The exact fields depend on the document layout, capture configuration and information visible on the invoice.\n <\/p>\n
\n Supplier invoices can enter an external capture process through an agreed intake channel. Depending on the implementation, this may include an accounts-payable mailbox, document upload, scanned PDF or supported image file. The capture process should retain the source document so users can compare extracted values with the invoice when review is required.\n <\/p>\n
\n A well-designed intake process also separates invoices from unrelated attachments and supporting documents. Classification determines the document type and sends it to the appropriate processing path before field extraction begins.\n <\/p>\n
Invoice and attachments enter the agreed intake channel.<\/p>\n<\/p><\/div>\n
The document is identified as an invoice or another document type.<\/p>\n<\/p><\/div>\n
Visible invoice fields are converted into structured data.<\/p>\n<\/p><\/div>\n
Confidence, format and available reference checks are applied.<\/p>\n<\/p><\/div>\n
Uncertain or invalid values are reviewed against the source document.<\/p>\n<\/p><\/div>\n
Approved data and the source document are sent using the agreed method.<\/p>\n<\/p><\/div>\n
The accepted record becomes a Registered Pending Invoice in Jobpac.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n
\n Figure 1: OCR invoice processing workflow from supplier invoice intake to a Jobpac Registered Pending Invoice.\n <\/p>\n
\n The capture stage creates a usable document image or reads the digital invoice file. Classification then identifies whether the document is an invoice, credit note, supplier statement or another document type. After classification, the extraction engine reads the configured fields and presents them as structured data.\n <\/p>\n
\n Modern capture environments may use ABBYY FlexiCapture or configurable document AI technologies, including Google Cloud Document AI, Azure Document Intelligence and DocAI Fabric. The capture technology can vary without changing the basic requirement: the extracted values must be checked, approved and transferred in a format the Jobpac process can accept.\n <\/p>\n
\n DataDevice describes the common capture stages as input, classification, recognition, data extraction, verification and export. These stages provide a useful foundation, but they do not by themselves determine whether an invoice is complete for Jobpac processing.\n <\/p>\n
\n Validation checks whether extracted information meets the configured rules and available reference data. A capture solution may check whether a required field is present, whether a value follows the expected format, whether totals balance, or whether an extracted supplier or Purchase Order can be found in the available data.\n <\/p>\n
\n Confidence scores can also identify values that the capture engine could not read with sufficient certainty. These values should be compared with the source document rather than accepted automatically.\n <\/p>\n
\n Jobpac documentation describes external OCR systems reading incoming invoices and preparing invoice data and the scanned image for Jobpac. In a configured WareConnect workflow, the approved invoice data and source document are transferred to Jobpac using the agreed integration method.\n <\/p>\n
\n The exact handoff method depends on the customer environment and implementation. The important outcome is that Jobpac receives the approved record and source document in the expected form, rather than users having to re-enter the same invoice information manually.\n <\/p>\n
\n After Jobpac accepts the information, the invoice can become a Registered Pending Invoice. It is then available for the next applicable Jobpac processing stage, which may include further coding, matching, approval or posting depending on the organisation\u2019s configuration.\n <\/p>\n
\n Trimble\u2019s Jobpac Help explains that an invoice that fails validation during the OCR intake process can be displayed in the e-invoice Edit Screen. A user can review the invoice, correct the relevant information and then register it as a Pending Invoice.\n <\/p>\n
\n The specific error and permitted correction depend on the Jobpac configuration and the data supplied by the external system. A failed validation should therefore remain visible and traceable rather than being silently ignored or replaced with an unconfirmed value.\n <\/p>\n
\n Related Jobpac source:<\/strong> \n OCR is valuable when the objective is to reduce repeated typing and create a consistent starting point for invoice processing. When the invoice is readable and the capture configuration is suitable, OCR can:\n <\/p>\n \n These benefits can make invoice intake more consistent and easier to review. They do not guarantee that every invoice contains the business references needed for correct allocation in Jobpac.\n <\/p>\n \n OCR can only read information that appears on the invoice and can be recognised from the document. It cannot extract an exact Job Number, Purchase Order number or Location when the supplier has omitted it. It may also read a partial site address, project description or contact name without knowing which Jobpac record the clue relates to.\n <\/p>\n \n This creates an important distinction between extraction accuracy<\/strong> and allocation accuracy<\/strong>. An invoice can be read accurately and still be incomplete for the Jobpac process.\n <\/p>\n \n Figure 2: OCR can capture visible invoice values, but a wider process is required to resolve missing or ambiguous Jobpac references.\n <\/p>\n \n The terms OCR, invoice automation and accounts-payable automation are related, but they describe different levels of capability.\n <\/p>\n \n Table 1: Difference between OCR capture, invoice automation and accounts-payable automation.\n <\/p>\n \n An OCR solution should be assessed as part of the complete invoice process, not only by how many fields it can read. Before selecting or modernising a Jobpac OCR approach, confirm the following:\n <\/p>\n Jobpac documentation describes external OCR systems reading incoming invoices and preparing the invoice data and scanned image for Jobpac. This means the recognition and extraction process may occur in an external capture platform, while Jobpac receives the prepared record for further processing.<\/p>\n<\/details>\n A Registered Pending Invoice is an invoice record that has been accepted into the Jobpac Pending Invoice process for the next applicable processing stage. Registration does not necessarily mean that all later coding, matching, approval or posting steps are complete.<\/p>\n<\/details>\n Trimble\u2019s Jobpac Help states that a failed OCR invoice can be displayed in the e-invoice Edit Screen. The user can review and correct the relevant information before the invoice is registered as a Pending Invoice.<\/p>\n<\/details>\n No. OCR can read the text and clues present on the invoice, but it cannot extract a Job Number that the supplier did not provide. A wider invoice automation process may use approved Jobpac reference data and controlled review to suggest or confirm the correct allocation.<\/p>\n<\/details>\n No. OCR is the capture and recognition component. Invoice automation adds classification, validation, verification, workflow and system handoff. Accounts-payable automation extends further into controls, exceptions, evidence, reconciliation and reporting.<\/p>\n<\/details>\n The capture technology depends on the agreed implementation. WareConnect can support ABBYY FlexiCapture and configurable document AI technologies, including Google Cloud Document AI, Azure Document Intelligence and DocAI Fabric. The capture engine should remain separate from the business rules, validation and Jobpac workflow wherever practical.<\/p>\n<\/details>\n \n OCR creates a structured starting point for Jobpac invoice processing. The next challenge is resolving missing or ambiguous references, applying business controls, managing exceptions and preparing complete Jobpac-ready data without unnecessary double handling.\n <\/p>\n \n Read Beyond OCR: Accounts Payable Automation for Jobpac<\/strong> to understand allocation, validation, exception handling and Jobpac-ready data.\n <\/p>\n \n WareConnect for Jobpac is available for demonstration and implementation. See how OCR-assisted capture, controlled validation and Jobpac-ready processing can support your invoice workflow.\n <\/p>\n
\n OCR Entry of Pending Invoices in Trimble Help<\/a>\n <\/p>\nWhat OCR does well<\/h2>\n
\n
Where OCR reaches its limit<\/h2>\n
Visible on the invoice<\/h3>\n
\n
May be missing or unclear<\/h3>\n
\n
OCR, invoice automation and accounts-payable automation<\/h2>\n
\n\n
\n \nCapability level<\/th>\n What it does<\/th>\n What it does not guarantee<\/th>\n<\/tr>\n<\/thead>\n \n OCR capture<\/strong><\/td>\n Reads visible invoice text and converts selected values into structured data.<\/td>\n That the invoice contains every Jobpac reference required for processing.<\/td>\n<\/tr>\n \n Invoice automation<\/strong><\/td>\n Adds classification, validation, verification, routing and system handoff.<\/td>\n That every missing or ambiguous allocation can be resolved without approved reference data or business judgement.<\/td>\n<\/tr>\n \n Accounts-payable automation<\/strong><\/td>\n Coordinates the broader process, controls, exceptions, evidence, reconciliation and reporting.<\/td>\n That every customer will use the same workflow, fields or approval rules.<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n What to check when selecting Jobpac OCR<\/h2>\n
\n
Frequently asked questions<\/h2>\n
Does Jobpac include OCR?<\/summary>\n
What is a Registered Pending Invoice in Jobpac?<\/summary>\n
What happens when an OCR invoice fails validation?<\/summary>\n
Can OCR find a Job Number that is not on the invoice?<\/summary>\n
Is OCR the same as invoice automation?<\/summary>\n
Which capture technologies can be used?<\/summary>\n
Next step: move beyond extraction<\/h2>\n
Continue the Jobpac automation series<\/h3>\n
\n Read Beyond OCR: Accounts Payable Automation for Jobpac
\n <\/a>\n <\/div>\nRelated resources<\/h2>\n
\n
See WareConnect for Jobpac in action<\/h2>\n