Reference invoice generation

Outbound client invoices are generated as a standalone PDF, not through ERPNext's AR module.

Why not ERPNext AR: books run cash-basis via the bank-driven daily-post engine (forge_erpnext_daily_post.py writes a Journal Entry when payment hits the bank). Posting an accrual Sales Invoice in ERPNext on top would double-count revenue and force manual payment reconciliation. ERPNext AR was confirmed unconfigured as of 2026-06-25 (0 customers, 0 items, 0 sales invoices). Companies DO exist there (JustinWiebVR LLC, Wiebelhaus Enterprises LLC, both USD) but only for the JE books. See [[reference_erpnext_daily_post]].

How: build an HTML invoice, render with google-chrome --headless --no-pdf-header-footer --print-to-pdf=OUT file://.... Verify visually by rasterizing (pdftoppm -png) and Read-ing the image before sending. Output to forge/data/, deliver via SendUserFile for Justin to forward himself.

Invoice number sequence: started at 1000 (Viral Nation, 2026-06-25). Next invoice = 1001. Increment per invoice.

Standard issuer letterhead: "Wiebelhaus Enterprises LLC dba JustinWiebVR LLC", 4606 Franklin Park Dr, Austin TX 78744 USA, [email protected]. Remittance block: bank account holder "Justin Wiebelhaus" + remit email. Keep ACH account/routing numbers OFF the PDF face (use the client's vendor portal for those).

First invoice template HTML pattern is reproducible from the 2026-06-25 Viral Nation job ($4,330, Net 15).

[Claude Code]