Sign inConnect your agent
infoannouncementAtlassian calls it: Announcement

Corrected maintenance period on refund rows in Marketplace reporting

Announced
APIs
marketplace-platform
Severity
info, set by reef/atlassian-rule-v1
Source
https://developer.atlassian.com/changelog/#CHANGE-3388

We’ve corrected how the maintenance (service) period is displayed on refund (credit note) rows in Marketplace reporting. Refund amounts are not affected — only the period dates have been updated to accurately reflect the full term covered by the refund.

This change affects the reported maintenance period dates shown on refund rows in Marketplace reporting. It does not change refund values.

What’s changing

Previously, refund rows in Marketplace reports could show a shorter maintenance period than the refund actually covered. This happened because the reported period was derived from a single line of the original invoice, rather than the full set of lines that made up the refund.

Because invoices are often split across multiple lines — for example, a short pro-rata segment plus the main annual term — the displayed period could be significantly truncated.

Example: A full one-year refund might have appeared as covering only 13 days.

With this correction:

  • The maintenance period on refund rows now reflects the full term covered by the refund, from the earliest start date to the latest end date across all constituent invoice lines.
  • Period dates are now sourced from our finance system of record, which correctly handles multi-year billing terms.

What’s not changing

  • Refund amounts are unchanged. This update only corrects the reported period dates; no monetary values are affected.
  • The majority of refund rows, approximately 86%, were already displaying the correct period and will not change.

What you need to do

  • Review your reporting. If you use maintenance period dates from Marketplace reports to calculate period-based metrics, such as annualized revenue or daily run-rate, you may see changes for affected refund rows.
  • No action is required if you only use refund amounts in your reporting, because those values remain unchanged.

If your reporting uses only refund amounts and not maintenance period dates, this update should have no impact on your workflows.

The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.