LocalLedger AI: A Private, Local-First Bookkeeper for Freelancers

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

What I Built

LocalLedger AI is a local-first AI assistant that helps freelancers organize invoices and receipts without sending sensitive financial documents to a third-party AI service.

Freelancers often waste time manually entering invoice numbers, dates, vendor names, tax amounts, and expense categories into spreadsheets. LocalLedger AI automates much of that repetitive work.

The workflow is simple:

1. Upload an invoice or receipt.
2. Extract relevant information using an open-weight AI model.
3. Review and correct the extracted fields.
4. Categorize expenses and export the results to CSV.

The goal is to make basic bookkeeping less tedious for independent workers who cannot justify paying for a complicated accounting platform.

Demo

[Add a link to the working demo or a short screen recording.]

Code

harsh4944 / Tic-Tac-Toe

Tic-Tac-Toe

View on GitHub

How I Built It

LocalLedger AI is designed around open-weight models and local inference rather than a proprietary AI API.

The application combines document text extraction, structured data processing, and an open-weight language model to turn unstructured invoice and receipt content into consistent records.

Potential components include:

• Ollama: Run a compatible open-weight model locally.
• Qwen or another suitable open-weight model: Extract and normalize invoice fields into structured JSON.
• Python: Handle document processing, validation, and CSV export.
• Streamlit: Provide a simple interface for uploading documents and reviewing results.
• SQLite: Store extracted records locally.

The exact model and document-processing pipeline can be changed as the project evolves. Extracted financial values are validated where possible, and users can review results before exporting them.

Why Does Open Innovation Matter?

Privacy is central to this project. Invoices and receipts can contain client names, addresses, transaction details, and other sensitive information. A local-first architecture gives users control over where those documents are processed and stored.

Open-weight models also make the economics more attractive for a small side hustle. Instead of paying for a hosted inference API on every document, users can run supported models on their own hardware, subject to its capabilities and energy costs.

Open innovation provides several practical advantages:

• Data ownership: Documents can remain on the user's machine.
• Control over costs: Local inference avoids per-request API charges, although hardware and electricity are not free.
• Model flexibility: A user can replace the underlying model as better options become available.
• Customization: The extraction pipeline can be adapted to specific invoice formats, regional tax fields, and recurring business workflows.
• Less vendor lock-in: The application does not have to depend on a single AI provider's pricing or API availability.

A closed API might offer stronger results on some documents or require less setup. The open approach is valuable when privacy, customization, predictable running costs, and user control matter more than outsourcing all the infrastructure.

My First User

[Add your real first-user experience here: who tried the tool, what task they completed, what feedback they gave, and whether they would pay for it.]

I want to validate whether freelancers find the time saved and privacy benefits valuable enough to pay for a polished version.

Prize Categories

[Add the partner prize categories that apply to the completed project, based on the challenge rules.]