Download Atlassian Invoices: New and Original Billing

To download Atlassian invoices, first identify whether the subscription uses the improved or original billing experience. The newer route uses Invoices in a billing account at admin.atlassian.com/billing. The original route uses Orders at my.atlassian.com. Their permission rules also differ, so a working administrator login is not enough to choose the instructions.

This guide follows Atlassian's invoice documentation and billing-permissions reference, checked on November 9, 2026. It does not report a customer-account download or a tested BrowserAct invoice collector.

Identify the billing experience before choosing a role

Atlassian says its improved experience is still rolling out. Its invoice guide distinguishes the interfaces using the left navigation: Overview appears first in the original experience, while Subscriptions appears first in the improved experience.

Use that visible account context rather than the age of your Jira or Confluence subscription. One company can have several billing arrangements, and assuming every subscription has migrated can send a finance user into the wrong account.

Download a PDF from improved billing

For the improved experience, the official procedure is:

1. Sign in at admin.atlassian.com/billing.
2. Select the correct billing account if more than one is available.
3. Open Invoices.
4. Choose Download next to the required invoice.

Atlassian says the downloaded file is a PDF. Open the saved document and verify the invoice number, creation date, billing and sold-to information, and relevant products. Selecting a valid invoice from another billing account does not complete the request for the account you intended to close.

The guide describes an individual Download control. It does not establish a one-click ZIP for every account or every historical PDF. If the task spans several billing accounts, preserve those account boundaries while collecting the required files.

Download a PDF from original billing

For the original experience, Atlassian identifies billing contacts and technical contacts as the users who can download invoices. Log in to my.atlassian.com, open Orders, find the invoice, then select PDF/Invoice.

Do not mix that role rule with the improved-billing rule. A technical contact whose original invoice route works should not be promised identical permissions after a subscription moves into the newer billing-account model.

When an expected record is missing, record which experience and account were checked. That gives the billing contact or support team a concrete starting point. Repeating the new-interface instructions against an original-billing account adds no useful evidence.

Preserve the document title and payment status

Atlassian says improved billing issues a Tax invoice / Receipt to acknowledge received payment, or a Tax invoice for pending-payment situations such as invoice terms or a failed payment attempt. Keep the title on the actual supplier document rather than renaming every file “paid invoice.”

The Invoices list also has statuses, including PAID, DUE, OVERDUE, and UNPAID. Those states provide context for the record but do not authorize a document-collection process to pay it, reactivate subscriptions, or change billing details.

An invoice may include several apps, collections, or Marketplace products. Enterprise and collection subscriptions can include linked-subscription details. Review the complete PDF when reconciliation requires those allocations; the first-page total alone may not explain the underlying products.

Reconcile across accounts and invoice versions

Use a register containing billing experience, billing account, invoice number, date, document title, status, and filename. Product or site names can be useful secondary references, but should not replace the actual invoice identifier.

After collecting, compare the expected invoice set with the PDFs. Record missing permission, wrong billing account, wrong interface, absent record, and failed download separately. If a corrected document is later supplied, keep its relationship to the original rather than counting it as a second payable transaction.

These are archive recommendations. They are not claims that Atlassian provides a built-in cross-account completeness report or automatic corrected-document matching.

Evaluate automation after the account model is settled

BrowserAct can be evaluated for repeated authorized retrieval across billing accounts. An Atlassian-specific trial would need to identify the interface, preserve the correct role and account scope, save original PDFs, and report missing documents. This guide provides no validated Atlassian Bot or guaranteed bulk-download capability.

Use the vendor-portal invoice workflow for file checks and invoice downloader comparison for selection. You can review BrowserAct if repeated account switching creates a demonstrated gap. To download Atlassian invoices, settle the billing experience and permission first, then verify the files.