---
title: "Verify invoice history displays and downloads the correct account records"
description: "Inspect sandbox invoice history for status, currency, and customer scope, then compare a downloaded invoice with an independently known billing fixture."
canonical_url: "https://vostride.com/agent-library/billing-subscriptions/invoice-history-access.md"
md_url: "https://vostride.com/agent-library/billing-subscriptions/invoice-history-access.md"
content_kind: "recipe"
topic: "billing-subscriptions"
---

# Verify invoice history displays and downloads the correct account records

Inspect sandbox invoice history for status, currency, and customer scope, then compare a downloaded invoice with an independently known billing fixture.

## Risk

Invoice lists can contain stale totals or a different organization customer after switching context. A downloaded document must be tied to its invoice identifier and billing customer rather than accepted merely because a file appeared.

## Fixtures

- A sandbox customer with one paid invoice and one void or unpaid invoice with distinct amounts.
- A second isolated billing customer used only to establish forbidden cross-account invoice scope.
- An invoice inspection hook and a harmless downloadable invoice artifact from the sandbox provider.

## Steps

1. Open Billing for the intended organization and verify its customer context, invoice identifiers, statuses, currencies, and totals against the fixture record.
2. Open the paid invoice detail and verify its billing period, line quantity, subtotal, adjustments, and final amount.
3. Download that invoice and verify the file is readable and contains the same invoice identifier and customer name.
4. Return to history and verify the unpaid or void invoice retains its distinct status rather than inheriting the paid label.
5. Inspect account-scoped invoice data and verify no second-customer invoice appears in the list or downloaded artifact.

## Expected results

- Invoice history shows the expected records for the selected billing customer only.
- The downloaded artifact matches the chosen invoice identity and amount.
- Distinct invoice payment states remain accurate in both list and detail views.

## False-pass traps

- A nonempty PDF or download event alone does not establish the document belongs to the selected invoice.
- Comparing only total amounts can miss two invoices with equal values but different customers or periods.

## Cleanup

- Delete local downloaded test artifacts and retain or remove sandbox invoices according to fixture policy.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa auth state](/docs/agent-qa/guides/auth-state.md)

- [Billing and subscription QA recipes](/agent-library/billing-subscriptions.md)
- [Software factory QA library](/agent-library.md)