WonderPhi Ledger Industrial -- Commercial License
Publicly online since 2010 · U.S. patent applications since 2012 · inventions offered since 2014. The work of Christopher Gabriel Brown, independently documented.
WonderPhi Ledger Industrial -- Commercial License
Commercial-license edition of Ledger. CSV reconciliation, 1099/W-2 generation, OFAC screening for accounting firms and finance teams.
© CRI-ONE. All rights reserved. Patents issued and pending. Unauthorized reproduction of the underlying designs is prohibited.
Extended catalog & full narrative — WonderPhi Ledger Industrial -- Commercial License
The extended dossier appended from the 2026-08-05 catalog snapshot. Prices in the body copy have been stripped; the live-store price on this page is the authoritative figure. Images have been omitted.
WonderPhi Ledger for organizations — perpetual single-organization commercial license
Everything below is identical to the retail product. What's different: your license covers the entire buying organization (unlimited machines, VMs, containers, cloud instances) with no seat count, no annual renewal, no telemetry, no activation. Redistribution / SaaS / hosted-service exposure require a separate OEM arrangement.
Easy Setup — No Package Manager, No Account, No Cloud
Single Python file. Python 3.8+ standard library only — nothing to pip install. Run with:
python wpl-recipe.py
Sample plan files ship with the download and run out of the box. Pair with WonderPhi Compute to execute the generated plans in parallel.
WonderPhi Ledger — 25 batch recipes for banking & finance operations
Twenty-five recipes for the daily finance-back-office chores: CSV reconciliation, tax-form PDF generation (1099s / W-2s), OFAC screening, ACH / NACHA file validation, depreciation and amortization schedules, statement diffing. Point at a folder of exports, get a parallel plan.
Why this exists
Finance ops runs on spreadsheets. Reconciling this month's bank export against the ledger export. Generating 300 1099s at year end. Validating an ACH batch before you push it to the bank. All of it is deterministic; almost none of it is fun; and it's the kind of work where doing 300 of something at 3am hunts for typos and misses them.
These recipes are the automation. Reconciliation is deterministic string / amount matching. 1099s are a template plus per-payee data. OFAC screening is a bulk lookup. NACHA validation is a checksum. Every one of them is a batch job dressed up as manual work.
What it is, in plain English
Give a recipe a folder of exports (CSVs from your bank, your accounting system, your payroll, your payment processor) and a config file that says how the columns line up. It emits a plan — one operation per row or per file. Compute runs them all in parallel. Results file back into your finance folder as CSVs, PDFs, or exception logs.
How you use it — three steps
- Run the recipe file.
python wpl-recipe.pyin the folder that contains your input files, or wherever you want the plan written. - Point at the target. The recipe asks (or reads from a text file) what the input is — a folder, a list of hostnames, a CSV, whatever the recipe expects. It writes a plan file: one shell command per line.
- Hand the plan to Compute. Drop the generated
plan.wpc.txtinto the WonderPhi Compute inbox, and every command runs in parallel across your cores. Read the honest log when it's done.
Worked examples — three of the 25 recipes in this library
csv-reconcile — match bank export lines against ledger export lines
Deterministic amount+date+memo matching. Prints matched / unmatched / duplicate rows to separate files.
python wpl-recipe.py csv-reconcile --bank bank-2026-07.csv --ledger ledger-2026-07.csv --output recon-2026-07/
generate-1099s — produce PDF 1099 forms for a payees.csv
One PDF per payee. Uses the current-year IRS PDF template. Fills 1099-NEC (or 1099-K, 1099-MISC) per row.
python wpl-recipe.py generate-1099 --payees payees.csv --year 2026 --output ./forms/
ofac-screen-batch — screen a list of counterparties against the OFAC SDN list
Fuzzy-matches each name/address against the downloaded SDN list. Emits a CSV of matches for review.
python wpl-recipe.py ofac-screen --counterparties parties.csv --sdn-list SDN.CSV --output screen-2026-07.csv
Verified capabilities
Recipes work with your existing exports on any Windows / macOS / Linux workstation:
- 25 operations covered: CSV reconciliation (bank vs ledger, ledger vs statement, statement vs cleared), 1099 generation (NEC / K / MISC / INT / DIV), W-2 generation, OFAC screening, NACHA / ACH validation and file structure check, depreciation schedules (straight-line, MACRS), amortization schedules, statement diffing, transaction categorization, journal-entry generation, aged-receivables report, aged-payables report.
- 300 1099 PDFs in ~45 seconds on a 16-core workstation.
- OFAC screening of 10,000 counterparties in ~90 seconds (all fuzzy-matching happens in RAM).
Every claim is testable on your own machine using the sample plans in the download.
Under the hood — the honest technical picture
Every recipe is pure Python (standard library only). Recon and depreciation logic is hand-written in ~100-line functions you can read end-to-end. PDF generation for tax forms uses the government-published PDF templates as overlays — the recipe fills the form fields, doesn't render the layout. Nothing calls out to the internet.
- Pure Python, standard library only. No dependencies, no supply-chain risk.
- Deterministic. Same inputs produce same outputs — safe for audit.
- Never modifies inputs. Every recipe reads exports and writes to a separate output folder.
- PDF forms use the IRS templates unchanged. The recipe fills form fields via the PDF's built-in AcroForm API. It does not re-render the form — if the IRS updates the layout, the current-year template just drops in.
- OFAC list must be downloaded by you (from the Treasury's public feed). Recipe screens against it locally — the list never has to leave your machine.
How it compares to the manual way
| Aspect | The typical alternative | This product |
|---|---|---|
| 300 1099s at year-end | Mail-merge in Word, or a /yr SaaS | One recipe, ~45 seconds, PDFs land in a folder |
| Reconciling last month's exports | Sort, VLOOKUP, colour cells red | One recipe, matched / unmatched / duplicates in three CSVs |
| OFAC screening | Manually enter each name into the OFAC website | Local fuzzy-match against the SDN list you downloaded |
| Portability | Your Excel workbook can't leave your machine | Every recipe is a text file. Runs anywhere Python does. |
What you need
- Windows / macOS / Linux workstation.
- Python 3.8+ to run the recipe. Standard library only — no pip installs.
- WonderPhi Compute to run the generated plan in parallel across cores.
- For OFAC screening: the current Treasury SDN list. Download it yourself — the recipe screens against it locally.
- For tax forms: the current-year IRS PDF templates. They ship inside the recipe download and get refreshed each January.
What's in the download
wpl-recipe.py— the recipe generator (Python 3.8+, standard library only)README.md— per-recipe reference for humansINDEX.md— alphabetical list of every recipe with a one-line descriptionsamples/— ready-to-run demo input files for every recipeLICENSE.txt— perpetual single-user license, personalized with your name and order number at delivery
Common questions
Q. Does it upload my financial data anywhere?
No. Every recipe is offline. Reconciliation, 1099 generation, OFAC screening — all local. Your ledger never leaves your machine.
Q. Is the tax-form output IRS-acceptable?
The recipes fill the government-published IRS PDF forms via the form's AcroForm fields, so the output is the exact IRS layout with your data in it. Print or e-file as you would any other PDF-based tax form. (Talk to your accountant about e-filing acceptance for your specific form type.)
Q. How does the OFAC screening work?
You download the Treasury's public SDN list (SDN.CSV). The recipe loads it into memory and fuzzy-matches each of your counterparties against every SDN entry (Levenshtein distance + normalized name matching). Results go to a CSV for your review — the recipe doesn't decide, you do.
Q. Can it interface with QuickBooks / Xero / NetSuite?
Only via CSV export. Every mainstream accounting system can export CSV, and every recipe here takes CSV as input. If your system doesn't export CSV, this isn't the product for you.
Glossary — every term used above, in plain English
- Recipe
- One of the ready-made plan-file templates in this library. Each recipe knows how to do one job across many inputs.
- Plan file (
*.wpc.txt) - A plain text file with one shell command per line that WonderPhi Compute reads and executes across every CPU core in parallel.
- WonderPhi Compute
- The parallel runtime this recipe library is designed for. Sold separately, or bundled in the Complete Bundle.
- Shell command
- Any line you'd normally type into a terminal / Command Prompt / PowerShell prompt.
- Standard library only
- The recipe uses only what ships with Python 3.8+ — no
pip install, no external packages. - Perpetual license
- Buy once, use forever. No renewals, no expiration, no update check.
- Reconciliation / recon
- Matching two lists of transactions (bank vs ledger, etc.) to find what agrees and what doesn't.
- 1099 / W-2
- US IRS forms for contractor payments (1099) and employee wages (W-2).
- OFAC / SDN list
- Office of Foreign Assets Control's Specially Designated Nationals list — the US sanctions list. Every US-based business must screen counterparties against it.
- NACHA / ACH
- The US Automated Clearing House system for electronic bank transfers. Files must conform to the NACHA operating rules.
- Depreciation / MACRS
- Spreading the cost of a capital asset across its useful life. MACRS is the US tax-code accelerated depreciation method.
- Journal entry
- A single accounting record: debit account A, credit account B, for amount X, on date Y.
License & support — Industrial variant
Perpetual, non-exclusive, non-transferable Industrial license. Covers all machines, VMs, containers, and cloud instances operated by a single organization (the legal entity named on the purchase receipt plus wholly-owned subsidiaries). No seat count, no machine limit, no renewals, no activation, no telemetry.
Employees, contractors, and consultants under the organization's direction may operate the software solely for the licensed organization's benefit. Rights end when their engagement ends.
Not permitted without a separate arrangement: redistributing the software; hosting it publicly; embedding it in a product/SaaS/PaaS you sell to third parties; sublicensing.
Support: email chris@cri-one.com.
Every download's LICENSE.txt is personalized at checkout with your organization name, order number, and issue date. USA sales.