Skip to main content

Capability map

What Bobby Receipts is being built to do

Everything below is intended capability. Where something is planned rather than decided, it says so, and nothing here is available to use.

Bobby Receipts is being built. Everything described on this site is the intended product direction, not a live service. Nothing here can be used to upload or process documents yet.

Group 01

Capture

How documents are intended to reach your workspace.

  • Private upload

    Initial direction

    Documents are designed to go into your workspace only, visible to the people you have put there.

  • Drag and drop

    A drag-and-drop surface for adding several documents at once is part of the intended capture design.

  • PDF and image documents

    The intended direction is PDF documents and phone photographs of paper receipts. Exact accepted formats will be confirmed as capture is built.

  • Email and storage capture

    Coming soon

    Gmail, Outlook, Google Drive and workspace-owned storage are planned sources.

Group 02

Understand

What the system is intended to read from a document. Extraction is assistance for a person, not a verdict.

  • Structured field extraction

    Key fields are intended to be read from the document and presented for confirmation.

  • Merchant or supplier

    Who the document is from, where it can be read.

  • Document date

    The date of the receipt or incoming invoice.

  • Totals

    Document total, and line detail where the layout allows it.

  • Tax amounts where detectable

    Tax is extracted only where it is actually present and readable. Bobby Receipts does not compute or attest tax treatment.

  • Currency

    The currency the document was issued in.

  • Document type

    Whether the document reads as a receipt, an incoming invoice or an uploaded copy of an outgoing invoice.

  • Duplicate warnings

    Flagging a document that looks like one already in the workspace is a planned safeguard.

  • Extraction is imperfect by design

    No extraction is promised to be complete or correct. Every extracted field is designed to be reviewable and correctable by a person.

Group 03

Organize

The structure documents are intended to live in.

  • Workspaces

    Personal and company workspaces keep separate sets of documents and separate people.

  • Periods

    Documents are organized by the period they belong to, so a month or quarter can be closed as a set.

  • Categories

    Plain categories for personal use, configurable per workspace.

  • Tags

    Free-form tags for the distinctions categories do not cover.

  • Ledger accounts

    Advanced company workspaces are intended to map categories onto ledger accounts.

  • Searchable records

    Each document is intended to become a searchable record with its extracted details, status and history.

Group 04

Review and approve

The control layer between a document arriving and a document being considered done.

  • Categorization review

    Suggested categories are presented for a person to accept or change.

  • Correction

    Any extracted field can be corrected; the record keeps what changed.

  • Multi-level approval

    Workspaces that need it can require one or more approval levels before a document is complete.

  • Comments and clarification

    Asking a colleague a question on a specific document is part of the intended review design.

  • Approval history

    Who approved what, and when, is intended to be recorded and readable later.

Group 05

Export and connect

Getting the organized result out again.

  • Export

    Exporting a reviewed period, with its documents and structured details, is core to the intended product.

  • Accountant handoff

    Handing a complete, reviewed period to a bookkeeper or accountant is the main intended destination.

  • Bobby Invoice synchronization

    Future

    Pulling copies of outgoing invoices from Bobby Invoice is a future integration.

  • REST API and MCP

    Future

    Programmatic and agent access are later platform capabilities.