# Complete the first request and verify its history

> Follow Acme's $6,000 request through return, correction, independent decision and a saved result.

_Updated: 2026-10-07_

## Continue the Acme case

Use the company and people from [company setup](/en/learn/core-company-setup). Tom requests the $6,000 machine for the customer project. At this stage we prove a decision route. Core approval does not by itself create a supplier obligation, an asset or a bank payment.

## Role and prerequisites

The process owner has validated and published a supported coordination route in [Studio](/en/learn/railbase-studio), with required quotation, business reason, independent review and correction steps. Tom is the requester; Eva and Maya receive only the decisions assigned by the published route. Accounting's purchase process is used later, after that Product is installed.

## Submit, correct and decide

1. As Tom, use **Start process**, choose the published training route and confirm Acme. Enter the machine, $6,000, currency and project purpose. Attach Aster's quotation; deliberately omit the required justification to check validation before submission.
2. Add the justification and submit once. In **Started by me**, reopen the request and check its documents, current step and responsible person.
3. As the assigned reviewer, open the dossier in **My work**. Return it with the specific question: “Which customer project requires this machine?” Do not approve from a notification alone.
4. As Tom, attach the $9,000 project order and correct the explanation. Resubmit the same request; retain the earlier revision and return reason.
5. As each assigned independent reviewer, inspect the current evidence and take the permitted decision. Tom must not approve his own request. An expired delegation or missing authority must be resolved through its governed change path.

## Verify the saved result

Reopen under both identities. The requester sees the final outcome; the dossier retains original submission, return, correction, pinned documents and decisions. There is one process, no duplicate created by retry. Cancelling a separate draft leaves no executed purchase; a completed action needs its supported compensating route rather than editing history.

Write the evidence as **Tom → submit/correct → final result → one retained request and decisions**. If an action fails, reopen and check the saved state before retrying. Company and object restrictions apply even to a direct link.

Continue with [decision evidence](/en/learn/decisions-and-evidence), then [Accounting's first period](/en/learn/accounting-first-period) to turn supported domain work into accounting results.