Skip to content

Interactive example · fictional data

From expense to an organized expense report

See how a receipt, a justification and a cost center affect the handoff of an expense report.

Conceptual demonstration. It does not represent a customer case or prove available features.

Objective Prepare a travel expense report for manager review and handoff to finance.

Team Employee · Manager · Finance

Explore the scenario. No action reaches a real system.

  1. 01Organize
  2. 02Review
  3. 03Forward
  4. 04Receive
T-03

Transport · R$ 180.00

Awaiting selection.

Purpose

Visit to Project Atlas

Fictional employee statement.

Cost center

Unclassified

Classification must be related to the purpose.

Document linked to the process
Cost center

What we know now · v1

Receipt not yet selected.

Example inputs, parameters and limits

Inputs

  • Expense report RC-307
  • Transport: R$ 180.00
  • Receipt T-03 and purpose of the trip

Fictional parameters

  • Two illustrative cost centers: Project Atlas and Operations
  • Classification must match the stated purpose
  • This is not an actual expense policy

Exploration history

Choices and handoffs will appear here, only in this session.

How this work continues

NebulaWorks

Brings together the work, owners, pending items and process artifacts.

NebulaOS and integrations

Supports context, integrations and controls at the points defined by the deployment. Confirmation comes from the destination system.

Starya / FDE

Identify ambiguous classifications and improve the expense reporting form.

Features, rules and integrations must be confirmed for each deployment.

Prepare this workflow with your team →