STARBUCKS CORP
COMPANY
10-K
FORM
2024-11-20
FILING DATE
2024-09-29
FY PERIOD END
1919
FACTS
SIC 5810
Filing Software Workiva
CIK 0000829224
Taxonomy US GAAP 2024  
SIC 5810
CIK 0000829224
Filing Software Workiva
Taxonomy US GAAP 2024  
Standard Concepts
548
Extended Concepts
108
16%
Extended Concepts
Errors
0
What are errors?
What are errors?
Indicate problems with an XBRL formatted filing that are sufficient grounds for SEC rejection of the XBRL portion of the filing.
Data Quality Errors
13
ERROR
The statement 9952152 - Statement - Consolidated Statements of Comprehensive Income includes an inconsistent calculation. The value of the concept us-gaap:OtherComprehensiveIncomeLossNetOfTax of 349,400,000 in the default should be equal to the sum of its child components defined in the calculation linkbase. The sum of these child components is 377,600,000. The values of the addends is determined by adding the values of the child concepts with a decimal value of -5. All values in the financia...
ERROR
The statement 9952152 - Statement - Consolidated Statements of Comprehensive Income includes an inconsistent calculation. The value of the concept us-gaap:OtherComprehensiveIncomeLossNetOfTax of 216,600,000 for us-gaap:AccumulatedTranslationAdjustmentMember should be equal to the sum of its child components defined in the calculation linkbase. The sum of these child components is 217,100,000. The values of the addends is determined by adding the values of the child concepts with a decimal val...
ERROR
The element us-gaap:DerivativeAssetsNoncurrent has been used in the filing but does not appear in the financial statements of the filing. This disclosure should appear in the face financials unless it is included in another account caption. If this is the case the following element(s) us-gaap:DerivativeAssetNoncurrentStatementOfFinancialPositionExtensibleEnumeration should be used to identify the account where the financial statement element us-gaap:DerivativeAssetsNoncurrent is included. ...
ERROR
The element us-gaap:DerivativeLiabilitiesNoncurrent has been used in the filing but does not appear in the financial statements of the filing. This disclosure should appear in the face financials unless it is included in another account caption. If this is the case the following element(s) us-gaap:DerivativeLiabilityNoncurrentStatementOfFinancialPositionExtensibleEnumeration should be used to identify the account where the financial statement element us-gaap:DerivativeLiabilitiesNoncurrent is...
ERROR
The element us-gaap:DerivativeLiabilitiesCurrent has been used in the filing but does not appear in the financial statements of the filing. This disclosure should appear in the face financials unless it is included in another account caption. If this is the case the following element(s) us-gaap:DerivativeLiabilityCurrentStatementOfFinancialPositionExtensibleEnumeration should be used to identify the account where the financial statement element us-gaap:DerivativeLiabilitiesCurrent is included...
ERROR
The element us-gaap:DerivativeInstrumentsGainLossReclassifiedFromAccumulatedOCIIntoIncomeEffectivePortionNet with a value of -2,000,000 has been used in the filing with the axis IncomeStatementLocationAxis. This is the only fact reported with this element. Rather than using the IncomeStatementLocationAxis the filer should use the extensible enumeration element to indicate the location of the item in the financial statements. In this case the element us-gaap:DerivativeInstrumentGainLossRecla...
ERROR
The element us-gaap:DerivativeInstrumentsGainLossReclassifiedFromAccumulatedOCIIntoIncomeEffectivePortionNet with a value of -12,300,000 has been used in the filing with the axis IncomeStatementLocationAxis. This is the only fact reported with this element. Rather than using the IncomeStatementLocationAxis the filer should use the extensible enumeration element to indicate the location of the item in the financial statements. In this case the element us-gaap:DerivativeInstrumentGainLossRecl...
ERROR
The element us-gaap:DerivativeInstrumentsGainLossReclassifiedFromAccumulatedOCIIntoIncomeEffectivePortionNet with a value of -4,000,000 has been used in the filing with the axis IncomeStatementLocationAxis. This is the only fact reported with this element. Rather than using the IncomeStatementLocationAxis the filer should use the extensible enumeration element to indicate the location of the item in the financial statements. In this case the element us-gaap:DerivativeInstrumentGainLossRecla...
ERROR
The element us-gaap:HedgedLiabilityFairValueHedge with a value of 332,200,000 has been used in the filing with the axis BalanceSheetLocationAxis. This is the only fact reported with this element. Rather than using the BalanceSheetLocationAxis the filer should use the extensible enumeration element to indicate the location of the item in the financial statements. In this case the element us-gaap:HedgedLiabilityStatementOfFinancialPositionExtensibleEnumeration should be used to identify the a...
ERROR
The element us-gaap:HedgedLiabilityFairValueHedge with a value of 1,060,000,000 has been used in the filing with the axis BalanceSheetLocationAxis. This is the only fact reported with this element. Rather than using the BalanceSheetLocationAxis the filer should use the extensible enumeration element to indicate the location of the item in the financial statements. In this case the element us-gaap:HedgedLiabilityStatementOfFinancialPositionExtensibleEnumeration should be used to identify the...
ERROR
The element us-gaap:DerivativeInstrumentsGainLossReclassifiedFromAccumulatedOCIIntoIncomeEffectivePortionNet with a value of -3,800,000 has been used in the filing with the axis IncomeStatementLocationAxis. This is the only fact reported with this element. Rather than using the IncomeStatementLocationAxis the filer should use the extensible enumeration element to indicate the location of the item in the financial statements. In this case the element us-gaap:DerivativeInstrumentGainLossRecla...
ERROR
The element us-gaap:DerivativeInstrumentsGainLossReclassifiedFromAccumulatedOCIIntoIncomeEffectivePortionNet with a value of 6,500,000 has been used in the filing with the axis IncomeStatementLocationAxis. This is the only fact reported with this element. Rather than using the IncomeStatementLocationAxis the filer should use the extensible enumeration element to indicate the location of the item in the financial statements. In this case the element us-gaap:DerivativeInstrumentGainLossReclas...
ERROR
The element us-gaap:DerivativeInstrumentsGainLossReclassifiedFromAccumulatedOCIIntoIncomeEffectivePortionNet with a value of 1,400,000 has been used in the filing with the axis IncomeStatementLocationAxis. This is the only fact reported with this element. Rather than using the IncomeStatementLocationAxis the filer should use the extensible enumeration element to indicate the location of the item in the financial statements. In this case the element us-gaap:DerivativeInstrumentGainLossReclas...
What are data quality errors?
What are data quality errors?
Indicate areas that may not meet the standards set by the Data Quality Committee (DQC), and may reveal areas where the XBRL can be improved.
Possible Issues
4
WARNING
Submission type 10-K should have a non-empty value for DocumentFinStmtErrorCorrectionFlag in the Required Context.
WARNING
10 fact(s) appearing in ix:hidden were eligible for transformation: dei:CurrentFiscalYearEndDate, dei:IcfrAuditorAttestationFlag, us-gaap:CommonStockParOrStatedValuePerShare, us-gaap:CommonStockSharesAuthorized, us-gaap:CommonStockSharesIssued, us-gaap:CommonStockSharesOutstanding
WARNING
Presentation relationship set role http://www.starbucks.com/role/IncomeTaxesNarrativeDetails has multiple (2) root nodes. XBRL allows unordered root nodes, but rendering requires ordering. They will instead be ordered by their labels. To avoid undesirable ordering of axes and primary items across multiple root nodes, rearrange the presentation relationships to have only a single root node.
WARNING
Presentation relationship set role http://www.starbucks.com/role/SupplementalBalanceSheetInformationScheduleofAccruedLiabilitiesTables has multiple (2) root nodes. XBRL allows unordered root nodes, but rendering requires ordering. They will instead be ordered by their labels. To avoid undesirable ordering of axes and primary items across multiple root nodes, rearrange the presentation relationships to have only a single root node.
What are possible issues?
What are possible issues?
Indicate areas of interest as to the quality of an XBRL formatted filing, and in some cases reveal opportunities for improvement of the XBRL filing.
SEC: Filing | Interactive Data