LedgerGuard.

Ariel Magalso · AI Engineer · Philippines · Remote

AI invoice automation that never moves money on a guess.

LedgerGuard is a solo-built accounts-payable workflow where AI reads variable invoices, deterministic code enforces financial controls, and people retain approval authority.

End-to-end ownership Full-stack implementation Evaluation & operations Remote · Philippines

Solo

End-to-end ownership

Product design through deployment

5/5

Controls visible

Every decision stays inspectable

0.0%

Critical false clearances

Unsafe invoices cleared incorrectly, held-out set

$0

Payment authority

Public workflow cannot execute payment

Recruiter snapshot

What I owned, how I built it, and where the proof lives.

Problem

Manual invoice preparation is repetitive, slow, and financially sensitive.

Solution

Evidence-linked AI extraction wrapped in deterministic controls and human approval.

My role

Solo product design, full-stack engineering, evaluation, operations, and deployment.

Stack

FastAPI, PostgreSQL, Claude, Docker, and a QuickBooks-style sandbox adapter.

Safety boundary

The workflow prepares work for review; it never authorizes payment.

Inspectable proof

Live demo, evaluations, architecture, operations, and source code are public.

Business case

Invoice operations · controlled automation · human authority

Why invoice review is worth automating.

Built for organizations managing meaningful invoice volume across suppliers, locations, purchase orders, and approval routes—where speed matters, but accountable human judgment still matters more.

01 / 03

Operational risk

The problem

Accounts-payable teams repeatedly enter invoice data, reconcile purchase orders and receipts, check duplicates and supplier details, and route exceptions. The work is repetitive, but one missed discrepancy can delay operations or create financial loss.

Manual work · fragmented evidence · financial exposure

02 / 03

Controlled response

The solution

LedgerGuard uses AI to read variable invoice documents, then hands every financial decision to deterministic arithmetic, evidence matching, policy controls, and human approval.

AI extracts · code verifies · people approve

03 / 03

Operational value

Why automate it

Automation reduces manual preparation, surfaces exceptions sooner, preserves an inspectable audit trail, and gives finance teams more time for supplier communication and judgment-heavy review.

Faster preparation · clearer exceptions · visible audit trail

Where it fits

Built for invoice-heavy operations.

One control pattern, adapted to each company’s documents, policies, systems, and approval structure.

6 potential contexts Illustrative—not customer claims
01

Facilities & property

Reconcile recurring supplier invoices across buildings, cost centers, and property approvers.

Adaptable controls
02

Construction

Compare subcontractor and materials invoices with purchase orders, receipts, and project controls.

Adaptable controls
03

Hospitality & multi-site retail

Standardize invoice intake and exception routing across many locations and local managers.

Adaptable controls
04

Manufacturing & logistics

Match high-volume supplier charges against orders, deliveries, and approved commercial terms.

Adaptable controls
05

Healthcare administration

Prepare non-clinical supplier invoices for controlled review while retaining human authority.

Adaptable controls
06

Professional services

Reduce repetitive invoice preparation for growing organizations with lean finance teams.

Adaptable controls
Integration-ready API · Webhook · Adapter

Designed to work around the finance systems a company already uses.

LedgerGuard can connect to accounting, procurement, document-intake, collaboration, and supplier-master systems. This portfolio build demonstrates a sandbox accounting adapter; external OAuth connectors are integration patterns, not deployed claims.

Featured scenario · LedgerGuard demo

A clean match should be boring—and completely inspectable.

Ready for approval Exception review Duplicate hold Blocked
See the project

The system extracts a Brightway invoice, aligns every field to evidence, recalculates the money, matches the purchase order and receipt, checks identity and duplicates, then prepares a draft for a human.

5/5

Deterministic controls visible

$0

Payment authority in the public workflow

Process

From variable document to controlled review.

01 AI

Extract

Read variable document layouts and propose structured fields.

02 Code

Verify

Align evidence, recalculate money, match identities, and detect duplicates.

03 Code

Route

Assign a controlled outcome and the right reviewer using explicit policy.

04 Human

Review

Inspect evidence, correct fields, and approve or reject the prepared work.

About the builder

Ariel Magalso
AI Engineer
Philippines · Remote

One builder across product, AI, controls, evaluation, and deployment.

I independently designed the workflow, data model, extraction schema, deterministic control engine, approval experience, evaluation harness, operational dashboard, and deployment.

Product and workflow design
Full-stack implementation
Evaluation and failure analysis
Database, operations, and deployment

Illustrative business case

Explore the operating model—not a customer claim.

Adjust the fictional inputs to understand the potential workflow effect. These values are intentionally separated from measured technical results.

Inputs — illustrative, adjust freely

Illustrative monthly outputs

160 hrs

AP hours potentially returned

$5,280

Estimated net monthly savings (labor returned minus automation cost)

Prepared without manual entry
1,200 invoices
Remaining manual preparation
40% (800/mo)
Automation cost
$160/mo
Blended cost per invoice
$1.89
Illustrative first-pass target
Under 30s

Demonstration assumptions, not customer outcomes. Defaults reproduce this project’s own stated fictional baseline (2,000 invoices/mo, 8 min manual prep, 60% straight-through → 160 AP hours/mo).

FAQ

The important questions, answered directly.

No. Keystone Facilities Group, every supplier, invoice, and dollar figure is fictional. The public workflow cannot execute a payment or accounting write.
Nothing financial. The model proposes document data; deterministic code decides whether it satisfies financial controls, and humans approve.
A labeled fictional dataset runs through the real pipeline. Held-out proof, development metrics, per-case failures, latency, and cost remain separate and public.
Yes. The guided workbench, architecture, evaluation runner, operational evidence, and source code are all linked from this site.

Open to opportunities

Need AI automation that can explain itself?

I build measurable AI-assisted workflows with deterministic safeguards, visible evaluation, and human review where the risk demands it.

Contact Ariel