Expense And Receipt UAT Journeys

Purpose

Use these journeys when a change may affect gig expenses, receipt attachments, quick receipt capture, reimbursement status, or expense statements.

Preconditions

  • You can sign in.
  • At least one client and one saved gig exist.
  • You have a small PDF or image available for receipt upload.
  • If testing expense statements, use gigs for the same client unless the journey asks for a mixed-client negative check.

Expense Receipt Journey

Automation: Partially automated UAT: Glovelly.Uat.Tests.UploadAndQuickCaptureWorkflowTests.BrowserReceiptAndAttachmentUploadsRoundTripThroughGigUi covers browser receipt upload/delete and reimbursement preservation; backend tests cover API download/storage rules.

Steps

  1. Open a saved gig with an expense.
  2. Upload a PDF or image receipt to the expense.
  3. Confirm it appears in the receipt list.
  4. Download the receipt.
  5. Delete the receipt.
  6. Confirm the receipt disappears and cannot be downloaded.

Expected Results

Receipt metadata, storage, download, and deletion all work without changing the expense reimbursement state. Each completed file action shows a terminal notification; a missing receipt file shows a persistent error notification with a clear unavailable-file message.

Receipt Analysis Journey

Automation: Backend automated; browser review remains manual until a consented Vertex test environment and fixture set are available.

Steps

  1. Open a saved gig with an existing expense receipt and select Analyse beside that receipt.
  2. Confirm the review dialog identifies the receipt and either shows a prior analysis or offers Analyse receipt.
  3. Analyse a supported test JPEG, PNG, WebP, or PDF receipt.
  4. Confirm merchant and total are clearly labelled as suggestions, confidence and warnings are visible, and date, currency, and category are labelled review-only.
  5. Select Use merchant and total and confirm the normal expense editor opens with the suggested values but does not save them automatically.
  6. Save the expense only after reviewing the populated fields.
  7. Repeat using a receipt saved through Scan receipt. Confirm Analyse receipt opens the same review dialog and only fills the editable draft fields after explicit use.
  8. Check an unsupported or oversized test attachment. Confirm the saved attachment and expense remain unchanged and the dialog gives a safe analysis failure message.

Expected Results

Receipt analysis augments, but never blocks or silently changes, the manual expense workflow.

Quick Receipt Journey

Automation: Backend and browser automated: Glovelly.Api.Tests.GigEndpointsTests.QuickReceiptDraft_* covers draft creation, candidate matching, updates, and reassignment; Glovelly.Uat.Tests.UploadAndQuickCaptureWorkflowTests.QuickReceiptFlowOpensTargetGigInViewport covers quick-capture navigation. Receipt analysis and visual capture variants remain manual.

Steps

  1. Use quick receipt capture to upload a receipt.
  2. If the app suggests a nearby gig, accept it or choose a different gig.
  3. Fill in the receipt draft description and amount.
  4. Save it.
  5. Click Go to gig and confirm the target Gig overview scrolls into view and remains selected.

Expected Results

The draft becomes a normal gig expense with its receipt attached. Existing expenses and attachments remain intact. Completion feedback remains visible after navigating to the target gig.

Expense Reimbursement Journey

Automation: Backend automated; manual UAT: reimbursement and generated-line rules have backend coverage; browser prompts and visual state remain manual.

Steps

  1. Create a gig with at least two expenses.
  2. Mark one expense as Reimbursed.
  3. Enter a reimbursed date and method or note when prompted.
  4. Save or confirm the change.
  5. Generate an invoice from the gig, or regenerate a linked draft invoice if prompted.

Expected Results

Reimbursed expenses are visually distinct and excluded from newly generated invoice lines by default. Claimable expenses still appear.

Claimable Again

  1. Change a reimbursed expense back to Claimable.
  2. Regenerate a linked draft invoice if prompted.

Expected result: the expense becomes eligible for generated invoice lines again.

Expense Statement Journey

Automation: Partially automated UAT: Glovelly.Uat.Tests.ExpenseStatementTests.CanGenerateExpenseStatementPreviewAndDownload and ExpenseStatementVariantsRespectReimbursementSelectionAndInvoiceLinks cover main preview/download, reimbursed inclusion, mixed-client blocking, and invoiced-gig projection rules; receipt-option variants remain manual/backend-covered.

Steps

  1. Create or identify multiple gigs for the same client with expenses.
  2. Include at least one receipt attachment.
  3. Mark one expense as Reimbursed.
  4. Select the same-client gigs in the Gigs list.
  5. Open the expense statement workflow.

Expected Results

The expense statement modal opens, expenses are grouped by gig, reimbursed or not-claimable expenses are visually distinct, and reimbursed expenses are excluded by default.

Invoiced Gig Selection

  1. Identify a gig that already has a linked invoice and at least one expense.
  2. Select it in the Gigs list with another gig for the same client.
  3. Open the expense statement workflow.

Expected result: invoiced gigs remain selectable for expense statements, the statement opens for the same-client selection, and invoice links are not changed.

Preview And Download

  1. Select the reimbursed expense in the modal.
  2. Toggle receipt attachment and receipt appendix options.
  3. Preview the PDF.
  4. Download the PDF.

Expected result: selected reimbursed expenses appear in the statement, receipt options affect the generated preview/download, the embedded PDF preview loads in the modal without being pushed out of view by long expense lists, and the downloaded PDF matches the preview.

Negative Checks

  1. Select a gig for one client.
  2. Try to select a gig for a different client.

Expected result: the app prevents mixed-client selections before generating the statement.

Then:

  1. Open a gig with no expenses.
  2. Try to launch an expense statement.

Expected result: the app explains that expenses are needed before a statement can be generated. No invoice state changes.

Notes

  • Receipt attachment changes should not mutate reimbursement status.
  • Reimbursement status should affect future generated documents, not old PDFs.
  • Expense statements are projections and should not create invoices or mutate gig invoice links.