Sample deliverables
These are the artifacts BeanStack produces each month — the same board packs, certificates, and close workpapers a finance department would hand you. Each is built from your live books, and every figure traces back to its source entries.
Below: one full illustrative template, then the structure of every deliverable. Templates use a fictional company and fictional amounts — they are not customer results. Book a walkthrough to see the same structure populated from your own books.
Matched entries are listed in full in the delivered report; each difference links to the evidence behind both treatments.
Vendor invoice #4471 (PDF) → policy “Prepaid software > $2,500 amortized over term” → posted 1450 · Prepaid expenses → reviewed by named controller → no subsequent changes.
The pass/fail bar is set with you before the shadow month starts: which difference causes are acceptable, what must reconcile to the dollar, and who signs off. You judge the packet against criteria you agreed to — not a moving target.
The board package — financials, KPIs, variance, and a flux narrative — assembled from your live ledger every month.
Sample available on requestThe certificate a lender expects — covenant ratios and headroom computed from live books, ready before it is asked for.
Sample available on requestThe full close workpapers — trial balance, reconciliations, schedules, and the exception log — behind every period you close.
Sample available on requestIncome statement, balance sheet, and cash flow — prepared on your books and tied back to the source entries behind every line.
Sample available on requestCurrent-versus-prior and budget-versus-actual, with the drivers behind each material movement written up — not just the delta.
Sample available on requestA structured response to an auditor or acquirer — each request drafted with source-linked documentation and the policy trail behind it, routed for your approval before delivery.
Sample available on requestThe fastest way to evaluate the output is a parallel shadow close on your own books — the same structures above, populated from your live data.