Expense claims
Review the amount, purpose and supporting receipts.
See an expense request →A practical workflow guide
Choose one repeatable request and define what the submitter, preparer and reviewer need to do. An expense claim is a useful first example.
Start with sample details. Check your storage and team access before using live documents.
Review the amount, purpose and supporting receipts.
See an expense request →Check specifications, estimated cost and business justification.
See a purchase request →Check dates, work coverage and the handover plan.
See a leave request →Agree which requests need review and who prepares them. For an expense claim, capture the employee, expense date, category, amount, business purpose and supporting receipt.
Check the supplied details and preview the document. Ask for missing information before sending it for review. A reviewer should be able to understand what is being requested from the document and evidence.
Select the authorized approvers and any signers. Sequential routing follows the approver order; parallel routing lets approvers decide together. Signers become ready only after approvals finish. The Inbox reflects the current turn, so someone waiting on another decision does not see a premature action.
An assigned approver can request changes with feedback. The requester’s Inbox shows a revision task. Update the editable draft, check its details and send a new review request. For expenses, use Edit expense details so the amount and document stay consistent.
Keep the completed document and activity history together. For an approved expense, Finance or an administrator can record the reimbursement date and reference after making the payment. The approved artifact stays unchanged.
Run a sample request from start to finish. Check that the reviewer can access the details and that you can find the result afterward.
Create a workspace and try a private draft with sample information before using the process with your team.
Create a workspace ↗Already have an account? Sign in