SSlops Discuss pilot

Managed accounting solution

A cash P&L spine for teams that need receipts before claims.

Slops Accountant turns owned commercial events, launcher cost classes, credit obligations, and source-gated corroboration into management statements with visible basis labels and reconciliation gaps.

Cash P&L basis Credit obligations Model cost classes Source-gated evidence

What the managed spine keeps visible

The first accounting view is deliberately small: cash posture, direct usage cost, credit obligations, and the routes still needed before a number can be trusted.

Cash P&L posture

Collected revenue, direct usage cost, gross margin, and open receivable classes are labeled by basis.

  • Management cash view, not formal revenue recognition
  • Demo figures only until customer sources are onboarded
  • Every line tied to a receipt class or marked as a gap

Liability and credit spine

Credits, refunds, payables, subscriptions, and ownership questions stay visible instead of being flattened.

  • Open credit obligations separated from revenue
  • Payables held until the source route is approved
  • Personal, business, and customer obligations kept apart

Launcher cost classes

Model and runner spend is grouped by cost basis before it touches margin analysis.

  • Subscription allowance, extra credit, and pass-through classes
  • Session attribution only after a source-approved route exists
  • Estimates annotate the view; they do not become ledger fact

Source-gated accounting evidence, not raw access

Slops Accountant does not ask customers to dump inboxes, bank feeds, or finance payloads into a new warehouse. It works from owned ledger rows, approved cost classes, and receipt pointers with a visible evidence grade.

Allowed evidence Receipt-class signals

Coordinate, owner, source, timestamp, basis, class, and evidence grade.

  • Owned commercial ledger rows
  • Approved launcher and model cost classes
  • Corroboration pointers from mail or finance routes
Kept outside Payload-bearing data

Private source content stays with its owner unless a scoped customer route says otherwise.

  • No raw inbox, bank, card, or customer payload copies
  • No private journals, private operating notes, or runbooks
  • No self-serve live claim before managed onboarding

The product is a managed accounting control layer: it can say why a line is present, what source class supports it, and what is still blocked. It does not pretend a demo statement is a tax close, audit opinion, or automated accounting system of record.

Demo statement classes

These are public-safe examples of the statement shape. They are intentionally rounded and illustrative so the page demonstrates the product without exposing source values.

01 / Cash

Management cash view

Collected cash, open receivables, past-due classes, direct usage cost, and gross margin.

02 / Liability

Credits and obligations

Open customer credits, refund candidates, payables, and ownership questions remain separate.

03 / Cost

Launcher and model spend

Subscription allowance, extra credit, pass-through, and allocation classes are named before posting.

04 / Gap

Reconciliation gaps

Missing source routes, unverified estimates, unmatched receipts, and blocked joins stay on the statement.