ERPNext Invoice Validation & Confirmation Prototype

![ERP validation demonstration: validate, confirm and prepare a draft](https://www.twine.net/signin

Synthetic offline demonstration.

Automated data entry needs a dependable decision process before information reaches an ERP. Missing suppliers, conflicting totals and repeated messages should be visible and reviewable.

I built a runnable prototype for purchase bills, supplier expense bills, structured sales commands and stock queries. It maps known master data, checks required fields and decimal totals, and places valid invoices in a confirmation queue. Confirmation is tied to the exact proposed content; changed previews and reused approvals are rejected. Duplicate checks persist across a local process restart.

The sample includes a two-page walkthrough, Python program, ten input scenarios, sixteen behavior tests and inspectable output files. In ordinary evaluation, three invoice proposals paused for confirmation and zero request drafts were exported. Scripted approvals then produced three local request candidates. The run also blocked one duplicate, routed five inputs to review and returned one clearly identified stock-fixture response. Replaying the showcase left the draft count unchanged.

All sixteen behavior tests passed in the recorded run. The exported requests remain unsent local candidates. Field names reference ERPNext version 15, but no ERPNext server, n8n instance, Telegram account or OCR service was connected. This demonstrates validation and confirmation logic; live integration and acceptance require the client’s configuration and environment.

The illustrated PDF, source code, input fixtures and validation records are prepared and available for review.

[Open the illustrated workflow evidence](https://www.twine.net/signin