Transport · R$ 180.00
Awaiting selection.
Interactive example · fictional data
The receipt arrived. The work still needs to move forward.
An expense goes through documents, classification, review and confirmation by finance that it was received, without declaring payment.
Conceptual demonstration. It does not represent a customer case or prove available features.
Video
Transcript
[Illustrative example · fictional data] [“I need to submit the expenses for this trip.”] [Claim RC-307 · Transport: R$ 180.00] [Stated purpose · visit to Project Atlas] A person submits the receipt for a trip.
[NebulaOS · Starya builds and connects within the operation’s scope · Expense channel · Expense record] [Illustrative interface · Features and integrations depend on the deployment.] On NebulaOS, connected by Starya within the operation’s scope, the flow receives the expense through the channel and records it.
[Missing: cost center] [What is the cost center for this trip?] The flow links receipt and purpose, but the cost center is missing. The person gets a request for only what’s missing.
[Cost center: Project Atlas.] [Cost center · Project Atlas] [Policy and expense claim] [Review workflow · Claim RC-307 · R$ 180.00] [Mark as reviewed → Reviewed by the manager · Forward to finance] [Forwarded to finance · receipt pending] [Finance system] [The destination still needs to confirm receipt.] With the answer, the file is linked to the policy and goes to the manager. The manager reviews and forwards it. Forwarding is not receiving: the operation waits for the response.
[Finance received the claim] [No payment was requested or confirmed.] Finance confirms it received the claim. This scope ends here: payment is a separate step.
[At which handoff does your team have to ask for the same information again?] [Starya · We accelerate your AI strategy. NebulaOS is the operating foundation.] At which handoff does your team have to ask for the same information again?
What confirms completion
Finance confirms receipt of the reviewed expense claim.
What NebulaOS supports in this scenario
In this scenario, NebulaOS relates the expense channel, the expense record, the policy and expense claim, the review workflow and the finance system, connected within the operation’s scope, up to receipt confirmed by finance. The policy applied and the point where finance confirms depend on the deployment.
- NebulaWorks Brings together the work, owners, pending items and process artifacts.
- Starya / FDE Identifies ambiguous classifications and improves the expense claim form.
Try it yourself
Walk through the steps of this scenario and see what changes with each choice. Fictional data; no system is accessed.
Open the simulation
Objective Prepare a travel expense claim for manager review and handoff to finance.
Team Employee · Manager · Finance
Explore the scenario. No action reaches a real system.
- 01Organize
- 02Review
- 03Forward
- 04Receive
Visit to Project Atlas
Fictional employee statement.
Unclassified
Classification must be related to the purpose.
What we know now · v1
Receipt not yet selected.
Example inputs, parameters and limits
Inputs
- Expense claim 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.
Questions to take to your team
- Systems and data What needs to accompany each receipt?
- Authority Which policy defines the accepted purpose, limit and cost center?
- Owner Who reviews the purpose and cost center?
- Result How do you confirm the claim reached finance?
Use these questions with the guide How to choose an operation to start with
Related content
Steps
Owner, system, state and pending item of the experience’s 4 steps, with decisions and limits
Step 1 · Organize
Organize the expense and what is missing
The receipt and stated purpose reach the operation. The person receives a specific request for the cost center.
- Owner
- Employee
- System
- Expense channel and record
- State
- Information pending
- Pending
- The receipt alone does not complete the work.
Step 2 · Review
Prepare and review
The additional information is linked to the expense policy, and the manager reviews the classification.
- Owner
- Administrative team and manager
- System
- Policy and review workflow
- State
- Review completed
- Pending
- The claim has not been forwarded yet.
Step 3 · Forward
Forward to finance
The reviewed claim is forwarded and waits for a response from finance.
- Owner
- Manager
- System
- Review workflow
- State
- Forwarded
- Pending
- The destination still needs to confirm receipt.
Step 4 · Receive
Confirm receipt
Finance confirms it received the reviewed claim. The next step is identified.
- Owner
- Finance
- System
- Finance system
- State
- Receipt confirmed
- Pending
- Payment has not been demonstrated.
Decisions to explore
- Original receipt or possible duplicate
- Cost center consistent or inconsistent with the purpose
- Receipt confirmed or pending
Pending items and limits
- Receipt by finance closes this scope.
- It does not prove payment or settlement of the expense.
Text version
The main content, without depending on the video or the simulation.
Initial request “I need to submit the expenses for this trip.”
A person submits a travel expense. The flow links receipt, purpose, policy and cost center. A missing item prevents the claim from being prepared until it is provided. The manager reviews it and finance confirms receipt; payment is a separate step.
The person submits the receipt for a trip. The operation relates receipt and stated purpose, notices the cost center is missing and asks only for that. With it, the file is linked to the expense policy and goes to the manager, who reviews and forwards it. Finance confirms it received the reviewed claim. Payment is not part of this scope.