Business books & allocation intelligence
Business books with provable period close — allocation when you need it
Start with business books — from $49/mo.
Bank feeds, canonical reconciliation truth, deterministic readiness, and optional attest. Add allocation monitoring when you need it — self-serve purchase or subscription.
Not ready to register? Try the guided sandbox →
Lawenots is software for keeping clean business ledgers when you hold both cash and digital assets. Connect your banks, match transactions, and finish each month with a simple checklist. You stay in control of the rules — we do not give investment advice.
Anyone can start bookkeeping from $49 per month. Allocation monitoring is available with a self-serve purchase or subscription — Snapshot through Signal on the allocation ladder. Prefer to look first? Use the guided sandbox, then compare plans on the pricing page.
Operators and practices use Lawenots to shorten month-end, hand clearer files to a CPA, and keep tax schedules tied to the same lots and transactions you already recorded. Export receipts include a content hash so you can prove what was generated.
Digital-asset bookkeeper · Self-serve signup
Bank feeds, Close Graph reconciliation, deterministic readiness, and tax-ready statements — from $49/mo.
Starter
$49 / mo
Professional
$129 / mo
Firm
$299 / mo
Unified book
Bank feeds and on-chain activity reconcile into one chart of accounts and one Close Graph. Period close, tax schedules, and optional attestation share the same lots and transactions — not a separate crypto spreadsheet.
Product spine
A period-close model where each close input is a weighted readiness gate with evidence — not scattered checklist folklore.
In production today, Close Graph readiness is computed from DB-backed gates: categorized transactions, pending review, bank reconciliations, ledger balance, open AR (SENT invoices), and open AP (APPROVED bills). Imported Stripe/payroll expectation feeds and hash-chained carry-forward notes are on the roadmap — shown below as such, not as shipped workspace features.
Transaction
shippedPlaid row, CSV import, exchange/on-chain activity
Reconciliation item
shippedBank reconciliation difference, duplicate suspect, feed gap
Invoice / AR expectation
shippedCustomer invoices in SENT status (AR posted to GL until paid)
Bill / AP expectation
shippedVendor bills in APPROVED status (AP posted to GL until paid)
Compensation expectation
roadmapGusto/Deel/ADP/PEO register import, contractor accrual (import evaluators)
Settlement anchor
roadmapShould-settle vs did-settle evidence (Plaid ACH, Stripe payout, on-chain) via the Verify evaluator
Tax remittance expectation
roadmapStripe Tax report import (manual CSV or auto-fetched via report-ready webhook) vs filing/remittance evidence
readiness = round((sum(weight for passed nodes) / sum(all node weights)) * 100)
Shipped gates block close when they fail. Roadmap node types (compensation imports, hashed carry-forward) are labeled separately and do not yet change the production score.
Planned as a first-class graph transition with hashed operator notes in the evidence package. Today, open AR/AP and recon items must be cleared (paid/voided/completed) or they block close.
[
{
"id": "check_categorized",
"type": "transaction",
"state": "settled",
"label": "All period transactions categorized",
"weight": 20,
"maturity": "shipped"
},
{
"id": "check_reconciliation",
"type": "reconciliation_item",
"state": "matched",
"label": "Bank reconciliations completed",
"weight": 20,
"maturity": "shipped"
},
{
"id": "check_ar",
"type": "ar_expectation",
"state": "open",
"label": "SENT invoice INV-12 unpaid",
"weight": 10,
"maturity": "shipped"
},
{
"id": "check_ap",
"type": "ap_expectation",
"state": "open",
"label": "APPROVED bill BILL-4 unpaid",
"weight": 10,
"maturity": "shipped"
}
]{
"period": "2026-05",
"closePolicyVersion": "close-graph-v1-shipped-gates",
"readinessFormula": "readiness = round((sum(weight for passed nodes) / sum(all node weights)) * 100)",
"canonicalLedger": "single books ledger for transactions and AR/AP journals",
"shippedGates": [
"categorized",
"pending",
"reconciliation",
"ledger",
"ar_expectation",
"ap_expectation"
],
"evidencePackage": "readiness checks + locked trial balance + AR/AP GL refs + export receipts + optional attestation metadata"
}Publishable methodology: Close Graph formula and evidence model →
Close feeds
Lawenots is not a bill-pay rail, payroll tax engine, or tax remittance service. Customer invoices and vendor bills post to the GL and feed shipped AR/AP readiness gates. Imported Stripe/settlement/comp/tax expectation evaluators exist for Verify; settlement, compensation, and tax remittance import nodes remain roadmap for the production close score.
Expectation objects
Shipped: invoices and bills as AR/AP close gates with GL journals. Roadmap: imported provider expectations (Stripe MRR, payroll registers, Stripe Tax collected-vs-remitted) as the same weighted readiness rollup.
Revenue / AR
nodeType: ar_expectation
shippedExpected: Customer invoices (Mark Sent posts AR)
Observed: Mark Paid applies cash against AR; bank deposits remain in the ledger
Blocker: SENT invoices unpaid at close
Shipped GL + readiness gate — not a full invoicing suite
Settlement reconciliation
nodeType: settlement_anchor
roadmapExpected: Imported settlement events that should couple to GL
Observed: GL references on settlement anchors
Blocker: Should-settle vs did-settle / missing GL refs
Roadmap for production close score — Verify evaluator today
Compensation reconciliation
nodeType: comp_expectation
roadmapExpected: Comp run-rate and provider register imports (Gusto, Deel, ADP, PEO)
Observed: Posted GL and register rows (evaluator path)
Blocker: Register / GL discrepancy by close
Roadmap for production close score — Verify evaluator today
Tax remittance reconciliation
nodeType: tax_expectation
roadmapExpected: Tax collected per jurisdiction/period (Stripe Tax report import)
Observed: Filing/remittance confirmation evidence per jurisdiction
Blocker: Collected-but-unremitted tax at close / remittance amount variance
Roadmap for production close score — Verify evaluator today
Crypto legs carry tx hash + FMV as evidence, reuse the lot and 8949 machinery, and can emit an outflow event into allocation drift when that module is provisioned.
{
"id": "exp_settlement_usdc_2026_05_01",
"module": "settlement",
"provider": "Ethereum",
"closeGraphNodeType": "settlement_anchor",
"expectedAmount": 1200,
"currency": "USD",
"expectedAt": "2026-05-28T17:00:00Z",
"evidence": {
"txHash": "0x7e3a...91bc",
"fmvUsd": 1200,
"ledgerReference": "gl_44291"
}
}Lawenots can review any books — and close them
Import QuickBooks, Xero, or CSV. Lawenots Verify surfaces close blockers, scores readiness, and returns a hashed readiness report that looks like a real close package. Works even if the client never migrates.
Import is the top of the funnel. Close Graph is the destination.
Visual proof of correctness
The brand is auditable artifacts, not neon dashboards. Step through what Close + Attest produces — then verify offline with open verification tooling.
Every close input becomes a graph node with a reproducible state: open, matched, settled, attested, or carried forward.
{
"period": "2026-05",
"closePolicyVersion": "close-graph-v1",
"canonicalLedger": "matched/unmatched source of truth",
"nodeStates": {
"open": 1,
"matched": 14,
"settled": 9,
"attested": 4,
"carried_forward": 1
}
}Free first attested close
Bring your books native or import from QuickBooks. We deliver one real evidence package for your first period — a locked trial balance, issue list, matched/unmatched ledger, export receipts, and attestation metadata — with a live verify link anyone can check.
Any org, any source
Start in Lawenots books or import QB-sourced data. The first period's attested close package costs nothing.
One real evidence package
Not a demo. A serialized period subgraph with a Merkle-root attestation and a public verify link you can hand to a CPA.
The CPA becomes the salesperson
A signed, independently verifiable close package beats a spreadsheet. Your CPA sees it once and wants it every period.
Free covers period one. Close + Attest ($399/yr) covers ongoing anchoring, batch closes, and firm workflows.
Specialized entry points
Public integration reference — MCP server for Claude, OAuth 2.0 flow, REST endpoints, and Labs Flywheel R/R gate tools (private beta).
Signed-in access when: Docs are public. Sign in after Labs Flywheel or practice access is provisioned to create MCP OAuth credentials and keys.
Firm ($299/mo), QuickBooks/Xero Migration Kit, and close-native books built for digital-asset and treasury clients.
Signed-in access when: Sign in to start Firm onboarding, switch client orgs, or run period close in a client ledger.
Firm API for practice ledgers — programmatic sync, lot-level gain/loss, and Form 8949 exports.
Signed-in access when: Overview is public. Sign in to create scoped credentials, run sync jobs, and use the practice dashboard.
Allocation intelligence
Standalone or books add-on — drift, tax-aware preview, evidence export
For individuals
Targets vs reality — with tax-aware next steps you decide
Use allocation as a standalone policy tool, or attach it to Lawenots books. Drift alerts, tax-aware rebalance previews, and a downloadable Allocation Evidence package — without turning Lawenots into a generic crypto dashboard.
Essential
Drift + target vs actual
Differentiator
Tax-aware rebalance preview
Strong
Allocation Evidence (paid deliverable)
Link your portfolio policy to this closed period so drift alerts and Allocation Evidence follow your books close cycle.
Open verification
Lawenots publishes verification tooling for Close + Attest so operators, firms, and auditors can independently validate evidence packages without a Lawenots account.
Offline Ed25519 signature checks, Merkle root rebuilds, and export-receipt hash verification for proof bundles.
View on GitHub →JSON Schema for pipeline attestation, export receipts, period-close checklist items, and evidence manifests.
View on GitHub →Versioned OpenAPI 3.1 and MCP tool/connector schemas for the public API and Claude connector surface.
View on GitHub →These are verification and contract artifacts — not the full product. Reconciliation matching, allocation drift logic, and Labs Flywheel covenant implementations remain proprietary.
Explore
Tax-ready methodology · Open verification · Verify a package · Lawenots Verify · Platform status · Security · llms.txt