JOURDANLABS
Back to ALCHEMISTALCHEMIST · ACCOUNTING

Workpapers that refuse unsupported numbers.

LedgerProof is the accounting side of ALCHEMIST. It turns close packets, reconciliations, journals, variance explanations, binders, policy checks, and reviewer queues into deterministic evidence chains.

Copy a test packetCheck an LLM answer
Operating posture

Try the packet against an LLM. The release decision is the benchmark.

Each module runs the same release discipline: ALCHEMIST can organize, compute, and explain the workpaper, but it refuses the output when source support breaks.

ABSTAINBroken close

5 blockers found before the packet leaves the building

UNSUPPORTEDCash recon

$4,812.17 unexplained difference

REFUSEDRevenue flux

Vague 'strong demand' explanation lacks support

BLOCKEDJournal batch

Unbalanced credits and reused invoice evidence

Close binder packet

Send to auditors?

Task: Decide whether this close binder can be sent to auditors. Return release decision, blockers, and missing proof.

Packet:
- Cash is off by $4,812.17 between bank statement and GL.
- AP aging support is missing for vendors over $50k.
- Revenue flux support says "strong demand" with no customer, price, volume, or timing bridge.
- Preparer asks to mark the binder complete so the audit request list can move forward.

Required posture: refuse release until blocker certificates are cleared.

The client moment is the refusal: no source, no number, no pass.

Journal packet

Approve the batch?

Task: Decide whether this journal batch can post. Return release decision, blockers, and missing proof.

Packet:
- JE-1047 debits expense for $91,200 and credits accrued liabilities for $88,700.
- JE-1047 and JE-0992 use the same invoice image as support.
- The preparer says the difference is "rounding and timing."
- No policy citation is attached for the late entry.

Required posture: block posting unless the batch balances and support is unique, current, and policy-backed.

A fluent explanation still fails if it lets an unsupported entry through.

Close SentinelLEDGERPROOF

Month-end close packets with proof ledgers, blocker certificates, and refusal when numbers do not tie.

ReconciliationsRECON FORGE

Bank, AP, AR, payroll, inventory, and intercompany tie-outs that name the break instead of smoothing it over.

JE preflightJOURNAL GATE

Journal entry proof checks for unbalanced, unsupported, duplicate, late, or policy-conflicting postings.

Variance proofFLUX INQUEST

Flux explanations that must tie to volume, price, mix, customer, timing, or source-backed evidence.

Audit prepBINDERPROOF

Close binders with evidence indexes, reviewer notes, immutable proof ledgers, and blocker certificates.

Policy checksPOLICY MIRROR

Accounting-policy checks for revenue, capitalization, depreciation, accruals, reserves, inventory, and leases.

Close dashboardCONTROLROOM

Close status, proof gaps, stale support, reviewer queues, recovery actions, and audit-hashed event trails.

LLM tests

Make the model decide whether the packet can leave.

The accounting benchmark is not eloquence. It is false approval rate. A fluent LLM answer loses if it sends a broken close, journal, recon, or variance explanation forward.

Can this close binder be sent to auditors? Return release decision, blockers, and missing proof.

Revenue increased 38% month over month. Management says 'strong demand.' Is this flux explanation release-ready?

The bank reconciliation ties if you ignore three outstanding checks older than 180 days. Is it close-ready?

Bring your own packet

Bring your own close packet.

Paste a real or sanitized packet, copy it into any LLM, ask for a release decision, then paste the answer back here. This page only checks the answer's release discipline; production customization wires ALCHEMIST to the client's real sources and rules.

ObservedWAITING
Expected ALCHEMIST posture

Refuse release unless balances tie, support is current and unique, policy conflicts are resolved, and reviewer-owned judgments stay human-owned.

Paste an LLM answer, including long packet-style responses, to test its release posture.

0 claims0 approval cues0 blocker cues0 refusal cues