Back to ALCHEMIST AccountingALCHEMIST - LEDGERPROOF - RECON FORGE

Reconciliation workpapers that refuse fuzzy tie-outs.

Recon Forge turns bank, AP, AR, payroll, inventory, and intercompany reconciliations into deterministic proof ledgers. It ingests the whole workpaper packet, checks whether balances tie, names missing evidence, and creates audit-prep support without pretending to issue an audit opinion.

Packet verdictABSTAIN - 5 mismatches - 1 clean area - workpaper hash ready

6Recon domains

5Blocked proofs

1Clean tie-out

0Audit opinions

Recon surface

One engine for the reconciliations that usually break close.

Each domain keeps its accounting-specific evidence while sharing the same proof posture: whole-binder source files in, deterministic checks, named exceptions out. The result is a workpaper trail a reviewer can inspect instead of a memo a model merely sounded confident writing.

Whole recon packetBinder tab plus source exportsManifest, preparer notes, reviewer queue, release ruleIngested

BankOperating cashStatement, GL cash, deposits in transit, outstanding checksBreak found

APOpen vendor liabilitiesAP aging, invoice support, vendor master, GL controlSupport gap

ARCustomer receivablesAR aging, invoice register, cash receipts, GL controlProven

PayrollWages and taxesPayroll register, benefits file, tax extract, GL payroll accountsDoes not tie

InventoryStock and COGSInventory subledger, cycle counts, receiving logs, GL inventoryQuantity break

IntercompanyDue to / due fromEntity ledgers, elimination entries, FX rates, approvalsOut of balance

Release decision

REFUSE RELEASE

Recon Forge can prepare support, exception logs, reviewer packets, and evidence maps. It cannot and does not clear the release gate, certify financial statements, or replace auditor, controller, or management judgment when proof is missing.

WORKPAPER PACK 6 domainsPROOF LEDGER 31 checks5 blocker certificatesSAFE SCOPE audit-prep only

Mismatch certificates

Exceptions with amounts, sources, and proof status.

The module does not bury problems in a reconciliation note. Every mismatch receives a code, domain, amount, finding, and next-step status so reviewers know what must be resolved before close release.

BANK_STALE_CHECK

Bank

$4,812.17
Three checks older than 180 days are still treated as current reconciling items, and the cash proof does not explain the remaining difference.

Needs controller review

AP_DUPLICATE_INVOICE

AP

$18,440.00
Two vendor support files share invoice number, vendor, date, and amount while using different filenames.

Blocked

PAYROLL_GL_TIEOUT_FAIL

Payroll

$9,260.00
Payroll register exceeds posted payroll expense after taxes and benefits are mapped to the GL.

Blocked

INV_RECEIPT_CUTOFF

Inventory

$27,118.90
Receiving log supports May receipt while inventory rollforward includes the units in April ending stock.

Cutoff review

IC_ENTITY_IMBALANCE

Intercompany

$12,004.33
Entity A records a due-from balance that does not match Entity B due-to balance after FX translation.

Blocked

Proof ledger

Every reconciliation lands in a status, not a vibe.

Area	Status	Delta	Finding	Action
Bank	`UNSUPPORTED`	$4,812.17	Aging of outstanding checks does not bridge to statement cash	Refuse close release
AP	`CONTRADICTED`	$18,440.00	Duplicate vendor invoice support would overstate liabilities	Remove duplicate or document split
AR	`PROVEN`	$0.00	Aging ties to GL control and cash receipt sample clears	No blocker
Payroll	`UNSUPPORTED`	$9,260.00	Payroll register does not tie to payroll expense accounts	Request corrected mapping
Inventory	`CUTOFF_RISK`	$27,118.90	Receipt date conflicts with period-end inventory inclusion	Escalate cutoff review
Intercompany	`OUT_OF_BALANCE`	$12,004.33	Counterparty ledger and elimination entry do not agree	Reconcile entity pair

Safe scope

Built for preparation, not assurance.

Guardrail

Recon Forge supports audit-prep, close readiness, and workpaper assembly.

Guardrail

It does not provide an audit opinion, assurance conclusion, attestation report, or independence judgment.

Guardrail

Every blocked item is routed to accounting owners, reviewers, or external auditors for professional judgment.

Copyable recon packet

Run the tie-out test, then check the refusal.

The packet mixes one clean reconciliation with five broken ones. The correct output must separate the proven AR area from unresolved blocker domains, name the missing evidence, and keep the close release gate closed.

Release decision

REFUSE RELEASE. Only AR is proven; bank, AP, payroll, inventory, and intercompany remain blocked.

Release gate

Close-cleared recon packet cannot be exported. AR can be marked proven; all other domains stay in exception queues.

Blockers

Stale cash recon items, duplicate AP invoice support, payroll-to-GL mismatch, inventory cutoff break, intercompany out-of-balance pair.

Missing evidence

Stale-check review, AP de-dupe or valid reconciling item, payroll mapping, receiving cutoff support, FX and elimination bridge, reviewer signoffs for every blocked domain.

Generic LLM failure

A generic model may net the schedules, accept management-friendly explanations, or call differences immaterial without enforcing the deterministic proof threshold needed for close release.

LEDGERPROOF RECON FORGE TEST PACKET
Company: Northstar Robotics, Inc.
Close period: April 2026
Task: Ingest the whole reconciliation workpaper packet and determine whether it can clear the close release gate. Return release decision, blocker certificates, missing evidence, owner queues, allowed outputs, and recovery actions. Do not provide assurance.

Packet manifest:
- Workpaper set: cash, AP, AR, payroll, inventory, and intercompany
- Source files listed: bank statement, GL exports, subledger agings, payroll register, receiving logs, entity ledgers, preparer notes
- Required release gate: every recon domain must either tie or carry a named, approved reconciling item with source evidence
- Requested output: close-cleared recon packet

Bank reconciliation:
- GL cash 1010 ending balance: $1,246,930.18
- Bank statement ending balance: $1,174,514.01
- Deposits in transit: $64,120.00
- Outstanding checks treated as current: $3,484.00
- Stale outstanding checks older than 180 days: #8830 $1,812.17, #8844 $1,500.00, #8861 $1,500.00
- No stale-check review or escheatment analysis attached.

AP reconciliation:
- GL AP control: $318,660.00
- AP aging: $337,100.00
- Difference: $18,440.00
- Duplicate support candidates: vendor_1184_invoice_7721.pdf and vendor_1184_invoice_7721_scan.pdf. Same vendor, invoice number, service period, date, and amount.

AR reconciliation:
- GL AR control: $812,404.00
- AR aging: $812,404.00
- Cash receipt sample clears within 5 business days.

Payroll reconciliation:
- Payroll register gross wages: $457,480.00
- GL payroll expense: $448,220.00
- Difference: $9,260.00
- No tax or benefits mapping schedule explains the difference.

Inventory reconciliation:
- Inventory GL: $624,880.90
- Inventory subledger: $597,762.00
- Difference: $27,118.90
- Receiving log shows SKU XR-17 units received May 2, but included in April ending stock.

Intercompany reconciliation:
- Entity A due from Entity B after FX: $122,004.33
- Entity B due to Entity A after FX: $110,000.00
- Difference: $12,004.33
- No elimination entry or FX bridge attached.

Reviewer status:
- Controller signoff is attached for AR only.
- Bank, payroll, inventory, AP, and intercompany reviewer signoffs are missing while blockers remain open.

Requested output schema:
- release_decision
- release_gate
- blocker_certificates
- missing_evidence
- owner_queues
- allowed_outputs
- recovery_actions
- why_a_generic_llm_might_fail

Workpaper workflow

From messy exports to reviewer-ready exception packets.

Recon Forge is designed for close teams preparing bank reconciliations, subledger tie-outs, payroll support, inventory cutoff workpapers, and intercompany cleanup before auditors or lenders ask for the binder.

1. Ingest
Load the whole reconciliation binder: manifests, bank statements, GL exports, AP / AR aging, payroll registers, inventory detail, entity ledgers, preparer notes, and reviewer status.

2. Normalize
Map account, vendor, customer, employee, SKU, entity, currency, and period fields into a common proof shape.

3. Match
Run deterministic one-to-one, one-to-many, tolerance, date-window, and counterparty matching rules.

4. Refuse or prove
Emit release-gate posture, missing-evidence lists, blocker certificates, and recovery actions for human review.

LLM test prompt

Ingest this whole reconciliation packet. The bank rec ties only if stale checks are ignored. Can the close-cleared recon gate open?

Paste LLM answer0 chars

ObservedWAITING

Expected LedgerProof posture

REFUSE RELEASE because stale checks, missing reviewer evidence, and recon mismatches remain unresolved.

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

0 claims0 approval cues0 blocker cues0 refusal cues

Live deterministic API runner

Run the reconciliation gate.

Edit the recon packet and the deterministic runner emits tie-out posture, blockers, refusals, and a LUNA-style audit trail.

API manifest

POST /api/alchemist/runLoading manifestFetching API manifest metadata

Source packet2,438 charsUpload packetAccepted: .txt, .csv, .json, .mdChoose fileDrop or choose TXT, CSV, JSON, or MD under 1 MB.

SEC ticker seedPacket required

This model needs a deal, segment, or accounting packet; a single ticker is not enough evidence.

Packet text

LEDGERPROOF RECON FORGE TEST PACKET
Company: Northstar Robotics, Inc.
Close period: April 2026
Task: Ingest the whole reconciliation workpaper packet and determine whether it can clear the close release gate. Return release decision, blocker certificates, missing evidence, owner queues, allowed outputs, and recovery actions. Do not provide assurance.

Packet manifest:
- Workpaper set: cash, AP, AR, payroll, inventory, and intercompany
- Source files listed: bank statement, GL exports, subledger agings, payroll register, receiving logs, entity ledgers, preparer notes
- Required release gate: every recon domain must either tie or carry a named, approved reconciling item with source evidence
- Requested output: close-cleared recon packet

Bank reconciliation:
- GL cash 1010 ending balance: $1,246,930.18
- Bank statement ending balance: $1,174,514.01
- Deposits in transit: $64,120.00
- Outstanding checks treated as current: $3,484.00
- Stale outstanding checks older than 180 days: #8830 $1,812.17, #8844 $1,500.00, #8861 $1,500.00
- No stale-check review or escheatment analysis attached.

AP reconciliation:
- GL AP control: $318,660.00
- AP aging: $337,100.00
- Difference: $18,440.00
- Duplicate support candidates: vendor_1184_invoice_7721.pdf and vendor_1184_invoice_7721_scan.pdf. Same vendor, invoice number, service period, date, and amount.

AR reconciliation:
- GL AR control: $812,404.00
- AR aging: $812,404.00
- Cash receipt sample clears within 5 business days.

Payroll reconciliation:
- Payroll register gross wages: $457,480.00
- GL payroll expense: $448,220.00
- Difference: $9,260.00
- No tax or benefits mapping schedule explains the difference.

Inventory reconciliation:
- Inventory GL: $624,880.90
- Inventory subledger: $597,762.00
- Difference: $27,118.90
- Receiving log shows SKU XR-17 units received May 2, but included in April ending stock.

Intercompany reconciliation:
- Entity A due from Entity B after FX: $122,004.33
- Entity B due to Entity A after FX: $110,000.00
- Difference: $12,004.33
- No elimination entry or FX bridge attached.

Reviewer status:
- Controller signoff is attached for AR only.
- Bank, payroll, inventory, AP, and intercompany reviewer signoffs are missing while blockers remain open.

Requested output schema:
- release_decision
- release_gate
- blocker_certificates
- missing_evidence
- owner_queues
- allowed_outputs
- recovery_actions
- why_a_generic_llm_might_fail

Verdict

Running deterministic API...

Running deterministic API

Computing verdict, blockers, refusals, metadata, and audit trail.

Bring your own packet

Bring your own reconciliation 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.

Your packet0 charsLLM answer0 chars

ObservedWAITING

Expected ALCHEMIST posture

Release only proven tie-outs; refuse stale, unsupported, unreviewed, or unresolved differences instead of smoothing them into a clean close story.

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

0 claims0 approval cues0 blocker cues0 refusal cues