StackOSWork, organized
LibraryWorkflowsAgentsOrchestratorsIntegrationsArticles

US solo entrepreneurs who need a dependable receipt inbox without moving financial evidence into StackOS / finance

Finance Receipt Intake

One verified external receipt record with original evidence retained, safe proof refs, and an IMAP acknowledgement only after the host completes the common intake contract.

6 stages2 specialist agentsDepends on the selected path

The problem

Receipts arrive through email, chat, and manual uploads, and are easy to lose, duplicate, or acknowledge before the underlying record is durable.

An agent can coordinate bounded provider transport, duplicate checks, and host-file verification while leaving custody and accounting judgment with the selected backend and owner.

What you do

  1. Forward receipts to the configured mailbox or upload originals/screenshots in chat; the agent resolves workspace defaults.
  2. Start a manual or explicit external-trigger intake and choose IMAP, chat, or manual-upload evidence.
  3. Review one consolidated list of material exceptions; credentials belong only in Connections, while receipt uploads use the host chat attachment channel.

What the agent does

  1. Confirm the external workspace is readable and writable before any IMAP export.
  2. For IMAP, search a bounded candidate page, stage exactly one message, and validate the host handoff.
  3. Use the common external intake contract to deduplicate, atomically retain originals, update finance.json, and re-read the result.
  4. Only after verified external persistence, acknowledge the matching UIDVALIDITY/UID and clean up the staged transfer.

When this workflow helps

A reusable method, adapted to the request.

  • A receipt, invoice attachment, screenshot, or other evidence must enter the selected finance backend through the common intake protocol.
  • A dedicated receipt mailbox has a bounded candidate message that needs store-before-ack handling.

Before it starts

Depends on the selected path

  • An explicitly selected external backend and writable workspace
  • Host access to the selected workspace and the uploaded originals or IMAP staging route
  • A durable operator policy reference
  • A verified SSL or STARTTLS IMAP connection only when the IMAP route is selected

What proves it worked

Evidence, not a success claim.

  • Safe external receipt-record and host-write proof refs
  • Safe source identity and hash/path verification refs
  • Epoch-qualified acknowledgement and cleanup state when IMAP is selected

Workflow path

The reusable stages of the work.

A real run expands these stages around the request, context, selected tools, approvals, and dependencies.

6 ordered workflow stages
  1. 01

    Preflight External Backend And Route

    Resolve workspace defaults, host access, and the selected route without requiring tax classification.

    Passes to next stage
  2. 02

    Discover Or Receive One Candidate

    Obtain one bounded candidate without treating it as an accepted receipt.

    Passes to next stage
  3. 03

    Stage IMAP Evidence

    Stage exactly one IMAP message through the bounded communications connector when the IMAP route is selected.

    Passes to next stage
  4. 04

    Validate And Write External Record

    Apply the external backend's duplicate, quarantine, atomic original-write, finance.json update, and re-read protocol.

    Passes to next stage
  5. 05

    Acknowledge Verified IMAP Evidence

    Mark the exact message seen only after the host proves external persistence.

    Passes to next stage
  6. 06

    Clean Up Completed IMAP Staging

    Remove connector staging after a proven acknowledgement while preserving external evidence and safe recovery state.

    Verified outcome

Safe stopping and recovery

Useful even when the whole path cannot run.

  • Stop after a staged candidate when host verification cannot proceed.
  • Stop after the external record is verified but before acknowledgement when the mailbox epoch or provider result is uncertain.
  • If the workspace, hashes, paths, or finance.json re-read fail, stop before acknowledgement and retain only a safe exception reference.
  • If acknowledgement is unknown or fails, preserve the verified external record and transfer id, then retry the same epoch-qualified acknowledgement without re-ingesting it.

Documented follow-on work

The next workflow is conditional, not hidden.

nextFinance Bookkeeping Preparation and Reconciliation

A receipt is accepted or matched in the selected external backend and its bookkeeping work remains prepared/unposted.

Specialists inside this workflow

Clear roles for each part of the job.

AgentFinance Receipt OperatorAgentFinance Control Reviewer

Connected work

Built to use the tools you already have.

Imap

Keep exploring

Related workflows.

See all 36 →
workflowfinance

Finance Bookkeeping Preparation and Reconciliation

A reviewed, externally recorded close packet marked prepared/unposted, with matched and exception refs that can be handed to later workflows.

5 stages
workflowfinance

Finance Cashflow Management

A dated external thirteen-week forecast packet with safe evidence/proof refs, uncertainty, exception state, and tax-estimate handoff readiness.

4 stages
workflowfinance

Finance Payment Request

One external payment request linked to a safe Stripe invoice reference, with deterministic mutation recovery and separate owner-approved finalization and send gates.

7 stages