Local AI Expense Assistant: Turn Invoices Into Organized Expense Records Without Cloud AI

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle

What I Built

Local AI Invoice & Expense Assistant

Managing invoices and receipts can be tedious for freelancers and small business owners. Manually entering merchant names, dates, taxes, and amounts into spreadsheets takes time, and sending financial documents to third-party AI services may raise privacy concerns.

I built a Local AI Invoice & Expense Assistant that uses a locally running AI model to extract structured information from invoices and receipts, categorize expenses, and save the results in a dashboard.

The goal is to help freelancers, tutors, and small business owners spend less time on repetitive bookkeeping while keeping their documents on their own computers.

Code

RHYTHMGUPTA8 / local-ai-expense-assistant

How I Built It

I built the application with a simple architecture:

• Python and Flask: Handle document uploads, processing, and application routes.
• Ollama: Runs the language model locally to extract structured invoice information.
• Qwen 2.5 3B: The default model for extracting merchant names, dates, amounts, taxes, and expense categories.
• SQLite: Stores the extracted expense records locally.
• HTML and CSS: Provide the expense dashboard and upload interface.
• PDF text extraction and OCR support: Extract text from supported documents and images.

The application requests structured JSON from the model so that extracted fields can be saved consistently in the database.

An important design goal is to keep AI inference local instead of sending each invoice to a paid cloud AI API.

Why Does Open Innovation Matter?

Open-source and open-weight AI make this project practical for users who want greater control over their financial data and operating costs.

Privacy: Documents can be processed on the user's own computer instead of being uploaded to an external AI provider.

Cost control: Local inference avoids per-request charges from proprietary AI APIs, although hardware, electricity, and maintenance still have costs.

Flexibility: The model can be replaced with another compatible model as performance and requirements change.

Customization: The extraction prompts and expense categories can be adapted for freelancers, independent professionals, and small businesses.

For this use case, open AI makes it possible to explore a private, locally operated bookkeeping assistant without requiring a recurring cloud AI API subscription.

Thanks for checking out my project!