All projects
03AI Automation· DataGrokr Analytics

AI-Powered Invoice Processing System

Automated financial document extraction using Vertex AI OCR and structured data parsing, improving processing efficiency by 40%.

Software Engineer · January 2021 – August 2025

40%
Processing Efficiency
Role

Software Engineer

Company

DataGrokr Analytics

Technologies

Python · Vertex AI · GCP · SQL

01 · Context

Overview

An automated pipeline that replaces manual invoice data entry with an intelligent extraction and validation workflow. Invoices in varied formats are processed through Vertex AI for OCR and structured data parsing, normalised, validated, and routed downstream.

Business Problem

Invoice data was being extracted manually from documents arriving in varied formats and layouts. The process was slow, inconsistent, and created bottlenecks in financial reporting. Rule-based extraction had been attempted but was brittle — format variations across vendors broke rules regularly.

My contribution

Designed and built the full invoice processing pipeline, including Vertex AI integration for OCR and data parsing, the post-processing normalisation layer, the validation logic, and downstream data routing.

02 · System

Solution Approach

A pipeline that ingests invoice documents, applies Vertex AI to extract text and identify structured fields through OCR and data parsing, normalises extracted data, validates it against expected schema and business rules, and routes the structured output downstream. Documents that fail validation are flagged for review.

Workflow

1

Invoice Input

Invoice documents (PDF or image format) arrive via upload or automated ingestion from storage.

2

Vertex AI OCR

Vertex AI processes the document using OCR and data parsing to identify and extract key fields.

3

Data Parsing

Extracted fields parsed and normalised — date formats, currency representations, and field mappings standardised.

4

Validation

Business rules applied to flag anomalies, duplicates, or missing required fields. Flagged items routed for human review.

5

Structured Output

Validated data written to target storage in structured, query-ready format.

03 · Engineering

Technical Decisions

  • Vertex AI selected for its ability to handle varied document layouts without per-vendor template configuration — reducing ongoing maintenance burden compared to rule-based approaches.

  • Post-processing normalisation layer built as a separate stage from OCR extraction — separating concerns so normalisation rules can be updated independently of the extraction model.

  • Validation and anomaly-flagging built before downstream routing — surfaces issues at ingestion rather than correcting incorrect data later.

Engineering Challenges

  • Invoice layout variance across vendors — OCR extraction had to be robust to significantly different document structures, fonts, table formats, and field placement.

  • Handling degraded document quality — partially visible fields, low-resolution scans, and mixed-orientation pages required resilient processing.

  • Normalisation complexity — extracted dates, currencies, and numeric formats appeared in many representations needing consistent schema mapping.

04 · Outcome

Verified Results

  • 40% improvement in invoice processing efficiency

  • Significant reduction in manual data entry effort

  • More consistent and auditable financial data extraction compared to the previous manual process

  • Reduced maintenance overhead compared to prior rule-based extraction approaches

AI-powered document extraction dramatically reduces manual effort, but the real engineering challenge lies in the normalisation and validation layer — that is what determines whether output data is reliable enough to use downstream without human verification on every record.
PythonVertex AIGCPSQL