8. ANUBO Custom Functions Premium

ANUBO custom functions are Microsoft Excel formulas that retrieve XBRL data directly. They’re available in the Analyzer edition and provide dynamic, recalculating data.

General Notes on Custom Functions: Normally, users don’t need to worry about the parameters of custom functions, as they are created automatically in the background based on selections made in the task pane. However, it is possible to modify these parameters manually or with automatic assistance at any time. This flexibility proves particularly useful when creating reports with time series or when transferring existing analyses to another company.

Note on Terminology: In anuboXBRL documentation and function parameters, we use the term “concept” to refer to both taxonomy definitions and reported values (facts) in company reports. This simplified terminology is more intuitive for finance professionals. Technically, XBRL distinguishes between concepts (taxonomy definitions) and facts (actual values in reports). For more details, see the Glossary in Chapter 11.

8.1 Core Data Functions Premium

These functions retrieve the main financial/non-financial data from XBRL reports:

Function	Purpose	Returns
`ANUBO.XBRLLabel`	Get human-readable label for a concept	Text (e.g., “Revenue from Contract with Customer”)
`ANUBO.XBRLValue`	Get value for a concept and period	Number or text. With dates, numbers are scaled by the Inline XBRL `scale` attribute (for example 6 is in millions), not by XBRL `decimals`
`ANUBO.XBRLFACTLABELBYDIMENSIONS`	Get label for a fact matched by concept, period, and dimensions	Text
`ANUBO.XBRLFACTVALUEBYDIMENSIONS`	Get value for a fact matched by concept, period, and dimensions	Number or text, scaled by the Inline XBRL `scale` attribute (for example 6 is in millions), not by XBRL `decimals`
`ANUBO.XBRLFACTDIMENSIONBYDIMENSIONS`	Get formatted dimension text for a matched fact	Text

The BYDIMENSIONS functions above are the strategic fact-resolution path used by Report Data – tables, Report Data – items (Standard plus dimensional items), Report Data – dimensional analysis, and Attributes headers derived from dimensional facts. Report Data – items (Standard line items only) continues to use ANUBO.XBRLLabel and ANUBO.XBRLValue.

8.2 Metadata Functions Premium

These functions provide additional information about the XBRL report and its data, useful for headers, footnotes, and data validation:

Function	Purpose	Returns
`ANUBO.XBRLReportCompany`	Get the company abbreviation for the report	Text (the company abbreviation)
`ANUBO.XBRLReportDate`	Get the report closing date	Text like “Report on: YYYY-MM-DD”
`ANUBO.XBRLDATASETPERIOD`	Get dataset period information	Text (period description)
`ANUBO.XBRLUNIT`	Get the unit for a specific concept	Text (e.g., “USD”, “shares”, “pure”)
`ANUBO.XBRLDEC`	Get the display scale of a fact as tagged in the Inline XBRL report (`scale`, not XBRL `decimals` accuracy)	Text such as “in millions”, or ”-” when the fact has no `scale`
`ANUBO.XBRLCONTEXTPERIOD`	Get context period information	Text (period context details)
`ANUBO.XBRLDimension`	Get dimension member for a concept	Text (dimension member value)
`ANUBO.XBRLFACTPERIODBYDIMENSIONS`	Get period text for a fact matched by dimensions	Text (human-readable period)
`ANUBO.XBRLFACTUNITBYDIMENSIONS`	Get unit for a fact matched by dimensions	Text (unit QName)
`ANUBO.XBRLFACTDECBYDIMENSIONS`	Get the display scale of a fact matched by dimensions (`scale`, not XBRL `decimals` accuracy)	Text such as “in millions”, or ”-” when the fact has no `scale`

8.3 Function Syntax Premium

About the CompanyAbbreviation parameter Uploaded reports: after you upload an XBRL report, you assign the company abbreviation. That value is what you pass as CompanyAbbreviation (for example “DEMO_MICROSOFT_10K”). You can see and select it in Company & Reports → Select. To change it later, use Rename in Company & Reports. The new abbreviation is the value to use in your formulas. Reports from the anuboXBRL Database: the abbreviation is taken from the database, and you can change it with Rename. Do not put the report type in the abbreviation (for example 10-K or 10-K/A). Form and FilingDate are filled from the database.

Report identity

CompanyAbbreviation and ClosingDate select the report. Form and FilingDate follow those two arguments. ReportReference, when the formula includes it, is the last argument.

The function does not choose a report when more than one report matches the report arguments you passed. That includes a call where Form and FilingDate are "".

The cell shows #N/A with the message Ambiguous report — add Form, FilingDate, or select a report version.
When a ReportReference is present and that reference matches more than one report, the cell shows #N/A with the message Ambiguous report — ReportReference matches multiple reports in My Reports.
Use "" for Form and FilingDate when one report matches the abbreviation and closing date. When more than one report matches, set Form (for example 10-K or 10-K/A). If that form still matches more than one report, also set FilingDate.
ReportReference is optional. The Formula Builder appends it only when the other report parameters are still ambiguous. Do not type it yourself.

Other report results are in Error handling.

Core Data Functions Premium

`ANUBO.XBRLLabel`

Purpose: Retrieve the human-readable label for a concept at a specific period. This function returns the display name (e.g., “Revenue from Contract with Customer, Excluding Assessed Tax”) instead of the technical concept ID (e.g., “us-gaap:RevenueFromContractWithCustomerExcludingAssessedTax”).

Syntax =ANUBO.XBRLLabel(CompanyAbbreviation, ClosingDate, Form, FilingDate, contextRef, datasetStartDate, datasetEndDate, ConceptID, [ReportReference])

CompanyAbbreviation: Company abbreviation (e.g., “DEMO_MICROSOFT_10K”).
ClosingDate: Report closing date (YYYY-MM-DD).
Form: Optional report form or type, used only when needed to distinguish reports that share the same abbreviation and closing date (for example 10-K and 10-K/A). Use "" when not required.
FilingDate: Filing date, used only when needed to distinguish reports. Use "" when not required.
contextRef: Optional expert parameter. Normally leave empty (""). Use only if you already know a specific contextRef and want to retrieve the label for that context directly.
datasetStartDate: Optional start date (YYYY-MM-DD) for duration periods. Leave empty for instants.
datasetEndDate: Required end/instant date (YYYY-MM-DD) when contextRef is not used.
ConceptID: Concept QName (e.g., “us-gaap:Revenue”).
ReportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns A text value with the human-readable label for the concept (e.g., “Revenue from Contract with Customer, Excluding Assessed Tax”). If the concept id contains abstract and the report has a presentation linkbase, the cell shows the presentation label for that concept, or the concept id when that label is not found. The cell is not empty. If the concept is not found, the cell shows the text Label not found for ConceptID: …. Report results are in Error handling.

Notes

Provide either dates (preferred) or a contextRef (expert), not both.
With dates, datasetEndDate is required; datasetStartDate is optional and helps disambiguate when multiple duration periods share the same end date.
With contextRef, leave datasetStartDate and datasetEndDate empty.
This function returns labels that are typically used in financial statements, making your Excel reports more readable than using raw concept IDs.
If you pass a linkRole URI (starting with “http://”) as the ConceptID, the function returns the table definition for that link role.

Example – Duration period (preferred)

=ANUBO.XBRLLabel(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","", “2024-01-01”,“2024-12-31”,“us-gaap:RevenueFromContractWithCustomerExcludingAssessedTax”)

Returns: Revenue from Contract with Customer, Excluding Assessed Tax

Example – Instant period (preferred)

=ANUBO.XBRLLabel(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","","",“2024-12-31”,“us-gaap:Assets”)

Returns: Assets

Example – Expert (using contextRef)

=ANUBO.XBRLLabel(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","",“D2024FY”,"","",“us-gaap:Revenue”)

Returns: Revenue from Contract with Customer, Excluding Assessed Tax

`ANUBO.XBRLValue`

Purpose: Retrieve the value for a concept at a specific period. This function returns the actual data value (number or text) instead of the label. When dates are used, numeric values are scaled by the Inline XBRL scale attribute (for example, scale 6 returns the value in millions). This is not the XBRL decimals accuracy. ANUBO.XBRLDEC returns that same scale as text. This is the primary function for extracting financial data from XBRL reports into your Excel worksheets.

Syntax =ANUBO.XBRLValue(CompanyAbbreviation, ClosingDate, Form, FilingDate, contextRef, datasetStartDate, datasetEndDate, ConceptID, [ReportReference])

CompanyAbbreviation: Company abbreviation (e.g., “DEMO_MICROSOFT_10K”).
ClosingDate: Report closing date (YYYY-MM-DD).
Form: Optional report form or type, used only when needed to distinguish reports that share the same abbreviation and closing date (for example 10-K and 10-K/A). Use "" when not required.
FilingDate: Filing date, used only when needed to distinguish reports. Use "" when not required.
contextRef: Optional expert parameter. Normally leave empty (""). Use only if you already know a specific contextRef and want to retrieve the value for that context directly.
datasetStartDate: Optional start date (YYYY-MM-DD) for duration periods. Leave empty for instants.
datasetEndDate: Required end/instant date (YYYY-MM-DD) when contextRef is not used.
ConceptID: Concept QName (e.g., “us-gaap:Revenue”).
ReportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns A numeric value or text value depending on the concept type. When dates are used and the fact has a scale, the number is scaled by that attribute (for example, scale 6 returns the value in millions). Text concepts return their text value. If the concept id contains abstract, the cell is empty. If the concept is not found, the cell shows text beginning with Error:. Report results are in Error handling.

Notes

Provide either dates (preferred) or a contextRef (expert), not both.
With dates, datasetEndDate is required; datasetStartDate is optional and helps disambiguate when multiple duration periods share the same end date.
With contextRef, leave datasetStartDate and datasetEndDate empty.
With dates, numeric values are scaled by the Inline XBRL scale attribute. For example, scale 6 returns the value in millions. This is not the XBRL decimals accuracy. ANUBO.XBRLDEC returns that same scale as text. When the fact has a scale, the value is rounded to (scale + decimals) decimal places, at least 0. Example: scale 6 and decimals -3 returns the value in millions rounded to 3 decimal places; scale 6 and decimals -6 returns whole millions. If decimals is missing, INF, or not a number, it counts as 0. The function returns a number; Excel’s cell format controls how many decimal places are displayed.
This is the most commonly used function for extracting actual financial data from XBRL reports into Excel.
Use ANUBO.XBRLLabel in combination with this function to create readable reports with both labels and values.

Example – Duration period (preferred)

=ANUBO.XBRLValue(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","", “2024-01-01”,“2024-12-31”,“us-gaap:RevenueFromContractWithCustomerExcludingAssessedTax”)

Returns: 51556 (properly scaled, in millions)

Example – Instant period (preferred)

=ANUBO.XBRLValue(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","","",“2024-12-31”,“us-gaap:Assets”)

Returns: 364840 (properly scaled)

Example – Expert (using contextRef)

=ANUBO.XBRLValue(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","",“D2024FY”,"","",“us-gaap:Revenue”)

Returns: 51556 (properly scaled)

`ANUBO.XBRLFACTLABELBYDIMENSIONS`

Purpose: Resolve the human-readable label for a concept using semantic aspect matching (concept, period, dimensions, optional unit, optional link role). Used by Report Data – tables, Report Data – items (dimensional mode), and Report Data – dimensional analysis.

Syntax =ANUBO.XBRLFACTLABELBYDIMENSIONS(companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions, lang, labelRole, unit, linkroleURI, [reportReference])

companyAbbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
closingDate: Report closing date (YYYY-MM-DD).
form: Optional report form or type, used only when needed to distinguish reports that share the same abbreviation and closing date (for example 10-K and 10-K/A). Use "" when not required.
filingDate: Filing date, used only when needed to distinguish reports. Use "" when not required.
conceptQName: Concept QName (e.g., "us-gaap:Revenue").
period: Period selector for the fact (instant, duration, or forever — as inserted by the task pane).
dimensions: Dimensions string or two-column range identifying the fact’s dimensional qualification. Use an empty string ("") for non-dimensional facts.
lang: Optional label language. Default "en" when omitted or empty.
labelRole: Optional label role. Default "standardLabel" when omitted.
unit: Optional unit selector for disambiguation when multiple facts match.
linkroleURI: Optional link role URI for disambiguation within a presentation table.
reportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns The resolved label text. If no fact matches, or a fact matches and no label is found, the cell shows text Error: NOT_FOUND: …. Report results are in Error handling.

Notes

The task pane builds these formulas automatically; manual edits are for power users and time-series workbooks.
Fact and parameter errors are plain text Error: <code>: <message>. Report results are in Error handling.

`ANUBO.XBRLFACTVALUEBYDIMENSIONS`

Purpose: Resolve a fact value using concept, period, dimensions, optional unit, and optional link role. This is the primary value function for table output, dimensional item insertion, and dimensional analysis.

Syntax =ANUBO.XBRLFACTVALUEBYDIMENSIONS(companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions, unit, linkroleURI, [reportReference])

companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions: Same meaning as for ANUBO.XBRLFACTLABELBYDIMENSIONS.
unit: Optional unit selector for disambiguation.
linkroleURI: Optional link role URI for disambiguation.
reportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns A numeric value or text value. When the fact has a scale, the number is scaled by that Inline XBRL attribute (for example, scale 6 returns the value in millions). If no fact matches, the cell shows Error: NOT_FOUND: No matching fact found for the specified concept, period, and dimensions. Report results are in Error handling.

Notes

Numeric values are scaled by the Inline XBRL scale attribute, consistent with ANUBO.XBRLValue when dates are used. For example, scale 6 returns the value in millions. This is not the XBRL decimals accuracy. ANUBO.XBRLDEC returns that same scale as text. When the fact has a scale, the value is rounded to (scale + decimals) decimal places, at least 0. Example: scale 6 and decimals -3 returns the value in millions rounded to 3 decimal places; scale 6 and decimals -6 returns whole millions. If decimals is missing, INF, or not a number, it counts as 0. The function returns a number; Excel’s cell format controls how many decimal places are displayed.
Attributes → Insert report header can derive header columns from a selected ANUBO.XBRLFACTVALUEBYDIMENSIONS formula.

`ANUBO.XBRLFACTDIMENSIONBYDIMENSIONS`

Purpose: Return formatted dimension member text for a fact identified by concept, period, dimensions, optional unit, and optional link role.

Syntax =ANUBO.XBRLFACTDIMENSIONBYDIMENSIONS(companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions, lang, labelRole, unit, linkroleURI, [reportReference])

companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions, lang, labelRole, unit, linkroleURI: Same meaning as for ANUBO.XBRLFACTLABELBYDIMENSIONS.
reportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns Formatted dimension qualification text for the matched fact. If no fact matches, the cell shows Error: NOT_FOUND: No matching fact found for the specified concept, period, and dimensions. Report results are in Error handling.

`ANUBO.XBRLDimension`

Purpose: Retrieve the dimension member value for a specific concept at a given period. Dimensions break down data into categories (e.g., by geographic region, product line, or business segment). This function returns the specific member value for a given dimension on a concept.

Syntax =ANUBO.XBRLDimension(CompanyAbbreviation, ClosingDate, Form, FilingDate, contextRef, datasetEndDate, ConceptID, DimensionName, [ReportReference])

CompanyAbbreviation: Company abbreviation (e.g., “DEMO_MICROSOFT_10K”).
ClosingDate: Report closing date (YYYY-MM-DD).
Form: Optional report form or type, used only when needed to distinguish reports that share the same abbreviation and closing date (for example 10-K and 10-K/A). Use "" when not required.
FilingDate: Filing date, used only when needed to distinguish reports. Use "" when not required.
contextRef: Optional expert parameter. Normally leave empty (""). Use only if you already know a specific contextRef and want to retrieve the dimension member for that context directly.
datasetEndDate: Required end/instant date (YYYY-MM-DD) when contextRef is not used.
ConceptID: Concept QName (e.g., “ifrs-full:Revenue”).
DimensionName: Dimension axis name (e.g., “ifrs-full:GeographicalAreasAxis”).
ReportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns The dimension member value as text (e.g., “North America”, “Asia”, “Product A”). If no dimension member is found for the specified concept and period, the cell is empty. Report and parameter results are in Error handling.

Notes

Provide either dates (preferred) or a contextRef (expert), not both. Exactly one must be provided.
With dates, datasetEndDate is required to identify the period.
With contextRef, leave datasetEndDate empty.
The DimensionName should be the axis name (e.g., “ifrs-full:GeographicalAreasAxis”), not the member name.
This function is useful when you need to know how data is broken down by dimensions, for example to categorize revenue by region or product line.

Example – Using dates (preferred)

=ANUBO.XBRLDimension(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","",“2024-12-31”,“ifrs-full:Revenue”,“ifrs-full:GeographicalAreasAxis”)

Returns: Asia (or the appropriate geographic member for that revenue concept)

Example – Expert (using contextRef)

=ANUBO.XBRLDimension(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","",“D2024FY”,"",“ifrs-full:Revenue”,“ifrs-full:GeographicalAreasAxis”)

Returns: Asia

Metadata Functions Premium

Metadata functions provide information about the data in XBRL reports. This type of information about data is used for labeling, for example in row headers and tables. The anuboXBRL Analyzer creates these UDFs automatically based on the data in the XBRL reports. The following documentation is intended for power users.

`ANUBO.XBRLReportCompany`

Purpose: Retrieve the company abbreviation for a specific report. This function returns the company identifier to display context information in your Excel worksheets. This function is commonly used in column headings and report headers to clearly identify which company’s data is displayed in each column.

Syntax =ANUBO.XBRLReportCompany(CompanyAbbreviation, ClosingDate, Form, FilingDate, [ReportReference])

CompanyAbbreviation: Company abbreviation (e.g., “DEMO_MICROSOFT_10K”).
ClosingDate: Report closing date (YYYY-MM-DD).
Form: Optional report form or type, used only when needed to distinguish reports that share the same abbreviation and closing date (for example 10-K and 10-K/A). Use "" when not required.
FilingDate: Filing date, used only when needed to distinguish reports. Use "" when not required.
ReportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns The company abbreviation as text (e.g., “DEMO_MICROSOFT_10K”) if the report exists for the specified company and closing date. If the report is not found, see Error handling. If the company abbreviation is missing, the cell shows an error text stating that the company abbreviation is required. If the abbreviation is present and the closing date is missing, the cell shows an error text stating that no report was found for that company at that closing date.

Notes

CompanyAbbreviation and ClosingDate select the report. Form and FilingDate stay "" unless more than one report matches. See Report identity.
Use this function in report headers and column headings to clearly identify which company’s data is displayed in each column, especially when working with multiple companies in the same workbook.
If the report is not found, see Error handling.

Example – Basic usage

=ANUBO.XBRLReportCompany(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","")

Returns: DEMO_MICROSOFT_10K

Example – In column heading

=ANUBO.XBRLReportCompany(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","")

Use this in a header row to display the company abbreviation above data columns for that company.

`ANUBO.XBRLReportDate`

Purpose: Retrieve the report closing date for a specific report. This function returns the report closing date to display context information in your Excel worksheets. This function is commonly used in column headings and report headers to clearly identify which reporting period’s data is displayed in each column.

Syntax =ANUBO.XBRLReportDate(CompanyAbbreviation, ClosingDate, Form, FilingDate, [ReportReference])

CompanyAbbreviation: Company abbreviation (e.g., “DEMO_MICROSOFT_10K”).
ClosingDate: Report closing date (YYYY-MM-DD).
Form: Optional report form or type, used only when needed to distinguish reports that share the same abbreviation and closing date (for example 10-K and 10-K/A). Use "" when not required.
FilingDate: Filing date, used only when needed to distinguish reports. Use "" when not required.
ReportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns A text value formatted as “Report on: YYYY-MM-DD” (e.g., “Report on: 2024-12-31”) if the report exists for the specified company and closing date. If the report is not found, see Error handling. If the company abbreviation or the closing date is missing, the cell shows an error text stating that the company abbreviation and the closing date are required.

Notes

CompanyAbbreviation and ClosingDate select the report. Form and FilingDate stay "" unless more than one report matches. See Report identity.
The ClosingDate must be in YYYY-MM-DD format (e.g., “2024-12-31”).
Use this function in report headers and column headings to clearly identify the reporting period for each column, especially when working with multiple reports or time series in the same workbook.
If the report is not found, see Error handling.

Example – Basic usage

=ANUBO.XBRLReportDate(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","")

Returns: Report on: 2024-12-31

Example – In column heading

=ANUBO.XBRLReportDate(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","")

Use this in a header row to display the report closing date above data columns for that report period.

`ANUBO.XBRLDATASETPERIOD`

Purpose: Resolve the actual period used by the selected dataset for a concept. Useful for displaying context information (e.g., report header period) or verifying which dates are in effect.

Syntax =ANUBO.XBRLDATASETPERIOD(CompanyAbbreviation, ClosingDate, Form, FilingDate, contextRef, datasetStartDate, datasetEndDate, ConceptID, [ReportReference])

CompanyAbbreviation: Company abbreviation (e.g., “DEMO_MICROSOFT_10K”).
ClosingDate: Report closing date (YYYY-MM-DD).
Form: Optional report form or type, used only when needed to distinguish reports that share the same abbreviation and closing date (for example 10-K and 10-K/A). Use "" when not required.
FilingDate: Filing date, used only when needed to distinguish reports. Use "" when not required.
contextRef: Optional expert parameter. Normally leave empty (""). Use only if you already know a specific contextRef and want to resolve that context’s period directly.
datasetStartDate: Optional start date (YYYY-MM-DD) for duration periods. Leave empty for instants.
datasetEndDate: Required end/instant date (YYYY-MM-DD) when contextRef is not used.
ConceptID: Concept QName (e.g., “us-gaap:Revenue”).
ReportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns Text like Dataset period: 2024-01-01 - 2024-12-31 or Dataset period: 2024-12-31.

Notes

Provide either dates (preferred) or a contextRef (expert), not both.
With dates, datasetEndDate is required; datasetStartDate is optional and helps disambiguate when multiple duration periods share the same end date.
With contextRef, leave datasetStartDate and datasetEndDate empty.

Example – Duration (preferred)

=ANUBO.XBRLDATASETPERIOD(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","", “2024-01-01”,“2024-12-31”,“us-gaap:Revenue”)

Returns: Dataset period: 2024-01-01 - 2024-12-31

Example – Instant (preferred)

=ANUBO.XBRLDATASETPERIOD(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","","",“2024-12-31”,“us-gaap:Assets”)

Returns: Dataset period: 2024-12-31

Example – Expert (contextRef)

=ANUBO.XBRLDATASETPERIOD(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","",“D2024FY”,"","",“us-gaap:Revenue”)

`ANUBO.XBRLUNIT`

Purpose: Retrieve the measurement unit for a concept at a specific period. This function returns the unit information to display context information in your Excel worksheets. This function is commonly used in column headings and report headers to clearly identify which unit of measure applies to the data in each column.

Syntax =ANUBO.XBRLUNIT(CompanyAbbreviation, ClosingDate, Form, FilingDate, contextRef, datasetStartDate, datasetEndDate, ConceptID, [ReportReference])

CompanyAbbreviation: Company abbreviation (e.g., “DEMO_MICROSOFT_10K”).
ClosingDate: Report closing date (YYYY-MM-DD).
Form: Optional report form or type, used only when needed to distinguish reports that share the same abbreviation and closing date (for example 10-K and 10-K/A). Use "" when not required.
FilingDate: Filing date, used only when needed to distinguish reports. Use "" when not required.
contextRef: Optional expert parameter. Normally leave empty (""). Use only if you already know a specific contextRef and want to retrieve the unit for that context directly.
datasetStartDate: Optional start date (YYYY-MM-DD) for duration periods. Leave empty for instants.
datasetEndDate: Required end/instant date (YYYY-MM-DD) when contextRef is not used.
ConceptID: Concept QName (e.g., “us-gaap:Revenue”).
ReportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns The unit information as text (e.g., “USD”, “EUR”, “shares”, “pure”). If the concept id contains abstract, the cell is empty. If the concept is not found, the cell shows text beginning with Error:. Report results are in Error handling.

Notes

Provide either dates (preferred) or a contextRef (expert), not both.
With dates, datasetEndDate is required; datasetStartDate is optional and helps disambiguate when multiple duration periods share the same end date.
With contextRef, leave datasetStartDate and datasetEndDate empty.
This function returns the unit of measure that applies to the concept’s values, which is essential for understanding what the numbers represent (currency, shares, etc.).
Common units include currency codes (USD, EUR, GBP), “shares” for share-based metrics, and “pure” for unitless values.

Example – Duration period (preferred)

=ANUBO.XBRLUNIT(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","", “2024-01-01”,“2024-12-31”,“us-gaap:Revenue”)

Returns: USD

Example – Instant period (preferred)

=ANUBO.XBRLUNIT(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","","",“2024-12-31”,“us-gaap:Assets”)

Returns: USD

Example – Expert (using contextRef)

=ANUBO.XBRLUNIT(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","",“D2024FY”,"","",“us-gaap:Revenue”)

Returns: USD

`ANUBO.XBRLDEC`

Purpose: Returns the display scale of the fact as tagged in the Inline XBRL report (scale attribute, for example 6 is shown as “in millions”). This is not the XBRL decimals accuracy.

Syntax =ANUBO.XBRLDEC(CompanyAbbreviation, ClosingDate, Form, FilingDate, contextRef, datasetStartDate, datasetEndDate, ConceptID, [ReportReference])

CompanyAbbreviation: Company abbreviation (e.g., “DEMO_MICROSOFT_10K”).
ClosingDate: Report closing date (YYYY-MM-DD).
Form: Optional report form or type, used only when needed to distinguish reports that share the same abbreviation and closing date (for example 10-K and 10-K/A). Use "" when not required.
FilingDate: Filing date, used only when needed to distinguish reports. Use "" when not required.
contextRef: Optional expert parameter. Normally leave empty (""). Use only if you already know a specific contextRef and want to retrieve the display scale for that context directly.
datasetStartDate: Optional start date (YYYY-MM-DD) for duration periods. Leave empty for instants.
datasetEndDate: Required end/instant date (YYYY-MM-DD) when contextRef is not used.
ConceptID: Concept QName (e.g., “us-gaap:Revenue”).
ReportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns A text label for the fact’s display scale (scale). Examples:

in thousands
in millions
in billions

The cell shows - when the fact has no scale (for example a text fact, or a report whose facts have no Inline XBRL scale).

Notes

Provide either dates (preferred) or a contextRef (expert), not both.
With dates, datasetEndDate is required; datasetStartDate is optional and helps disambiguate when multiple duration periods share the same end date.
With contextRef, leave datasetStartDate and datasetEndDate empty.

Example – Duration period (preferred)

=ANUBO.XBRLDEC(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","", “2024-01-01”,“2024-12-31”,“us-gaap:Revenue”)

Returns: in millions

Example – Instant period (preferred)

=ANUBO.XBRLDEC(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","","","",“2024-12-31”,“us-gaap:Assets”)

Returns: in millions

Example – Expert (contextRef)

=ANUBO.XBRLDEC(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","",“D2024FY”,"","",“us-gaap:Revenue”)

Returns: in millions

`ANUBO.XBRLCONTEXTPERIOD`

Purpose: Retrieve the period information for a specific context reference (contextRef). Returns either the end/instant date or both start and end dates. Useful when you already know a contextRef and need to display its period details, for example in report headers or verification.

Syntax =ANUBO.XBRLCONTEXTPERIOD(CompanyAbbreviation, ClosingDate, Form, FilingDate, contextRef, [includeStart], [ReportReference])

CompanyAbbreviation: Company abbreviation (e.g., “DEMO_MICROSOFT_10K”).
ClosingDate: Report closing date (YYYY-MM-DD).
Form: Optional report form or type, used only when needed to distinguish reports that share the same abbreviation and closing date (for example 10-K and 10-K/A). Use "" when not required.
FilingDate: Filing date, used only when needed to distinguish reports. Use "" when not required.
contextRef: Required expert parameter. The context reference identifier (e.g., “D2024FY”, “I2024-12-31”). You must know the exact contextRef from the report to use this function.
includeStart: Optional. If TRUE, returns both start and end dates. If omitted or FALSE, returns only the end/instant date as text.
ReportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns If includeStart is omitted or FALSE: A text value with the end/instant date (e.g., "2024-12-31"). If includeStart is TRUE: Both start and end dates are returned, which Excel displays as a two-column result (e.g., start: "2024-01-01", end: "2024-12-31" for duration contexts, or empty start and end: "2024-12-31" for instant contexts).

Notes

This function requires a contextRef parameter. Unlike ANUBO.XBRLDATASETPERIOD, you cannot use date parameters with this function.
Use includeStart=TRUE when you need both start and end dates, for example when building period labels that show full ranges.
Use includeStart=FALSE or omit it when you only need the end date, for example for column headers showing just the period end.
If the contextRef does not exist in the report, the cell is empty. With includeStart true, the result is two empty cells.

Example – End date only (includeStart omitted or FALSE)

=ANUBO.XBRLCONTEXTPERIOD(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","",“D2024FY”,FALSE)

Returns: 2024-12-31

Example – Start and end dates (includeStart=TRUE)

=ANUBO.XBRLCONTEXTPERIOD(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","",“D2024FY”,TRUE)

Returns: Start date in first column, end date in second column (2024-01-01, 2024-12-31)

Example – Instant context

=ANUBO.XBRLCONTEXTPERIOD(“DEMO_MICROSOFT_10K”,“2024-12-31”,"","",“I2024-12-31”,TRUE)

Returns: Empty first column, end date in second column (empty, 2024-12-31)

`ANUBO.XBRLFACTPERIODBYDIMENSIONS`

Purpose: Resolve the reporting period of a fact matched by semantic dimensions. Returns a human-readable period string (without a Dataset period: prefix). Used by Attributes → Insert report header when the source cell contains a BYDIMENSIONS value formula.

Syntax =ANUBO.XBRLFACTPERIODBYDIMENSIONS(companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions, unit, linkroleURI, [reportReference])

companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions, unit, linkroleURI: Same positions and meaning as for ANUBO.XBRLFACTVALUEBYDIMENSIONS.
reportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns Human-readable period text. If no fact matches, the cell shows Error: NOT_FOUND: No matching fact found for the specified concept, period, and dimensions. Report results are in Error handling.

`ANUBO.XBRLFACTUNITBYDIMENSIONS`

Purpose: Resolve the unit of a fact matched by semantic dimensions.

Syntax =ANUBO.XBRLFACTUNITBYDIMENSIONS(companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions, unit, linkroleURI, [reportReference])

companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions, unit, linkroleURI: Same positions and meaning as for ANUBO.XBRLFACTVALUEBYDIMENSIONS.
reportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns Unit QName. If no fact matches, the cell shows Error: NOT_FOUND: No matching fact found for the specified concept, period, and dimensions. Report results are in Error handling.

`ANUBO.XBRLFACTDECBYDIMENSIONS`

Purpose: Returns the display scale of a fact matched by semantic dimensions, using the same scale label as ANUBO.XBRLDEC. This is not the XBRL decimals accuracy.

Syntax =ANUBO.XBRLFACTDECBYDIMENSIONS(companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions, unit, linkroleURI, [reportReference])

companyAbbreviation, closingDate, form, filingDate, conceptQName, period, dimensions, unit, linkroleURI: Same positions and meaning as for ANUBO.XBRLFACTVALUEBYDIMENSIONS.
reportReference: Optional technical report reference, used only when the other report parameters are still ambiguous. The Formula Builder appends it. Do not type it yourself.

Returns A display-scale label such as in millions, or - when the fact has no scale. If no fact matches, the cell shows Error: NOT_FOUND: No matching fact found for the specified concept, period, and dimensions. Report results are in Error handling.

8.4 Error Handling Premium

Report results are the same for every function in this chapter. The cell shows #N/A or #VALUE! with the message in the table.

Report selection (all functions)

Situation	What the cell shows	What to do
Report not found	`#N/A`. Message: `Report not found in My Reports.`	Check the company abbreviation and closing date.
More than one report matches, including empty `Form` and `FilingDate`	`#N/A`. Message: `Ambiguous report — add Form, FilingDate, or select a report version.`	Set `Form`, then `FilingDate`, or select the report version.
`ReportReference` matches more than one report, is invalid, or names an unsupported version or kind	`#N/A` or `#VALUE!`. Messages: `Ambiguous report — ReportReference matches multiple reports in My Reports.`; a resolver text such as `Invalid ReportReference syntax.` or `Invalid upload ReportReference hash.`; a message that names the version or kind, for example `Unsupported ReportReference version '…'.`	Do not type `ReportReference`. Select the report version again so the Formula Builder writes it.
Report is outside My Reports, not ready, the reference does not match the other arguments, or the call is not authorized	`#N/A`. Message: `Report is not available in My Reports.`, `Report is not ready / available yet.`, `ReportReference does not match report parameters.`, or `Not authorized.`	Read the message. Do not type `ReportReference`.

Standard and metadata functions

Situation	What the cell shows	What to do
`XBRLLabel` / `XBRLValue`: dates and `contextRef` both set, or end date missing	Text `XBRLLabel Error: …` or `XBRLValue Error: …`	Pass dates or a `contextRef`, not both. With dates, pass `datasetEndDate`.
`XBRLLabel`: concept not found	Text `Label not found for ConceptID: …`	Check the concept id, dates, or `contextRef`.
`XBRLValue`: concept not found	Text `Error:` followed by the resolver message	Check the concept id, dates, or `contextRef`.
`XBRLValue`: concept id contains `abstract`	Empty cell	Expected for an abstract concept.
`XBRLDimension`: concept or dimension member not found	Empty cell	Check the concept, period, and axis name.
`XBRLDimension`: not exactly one of `contextRef` or `datasetEndDate`	Text `Error: Provide exactly one of contextRef or datasetEndDate`	Pass one of those two arguments.
`XBRLReportCompany`: company abbreviation missing	An error text stating that the company abbreviation is required.	Pass `CompanyAbbreviation`.
`XBRLReportCompany`: abbreviation present and closing date missing	An error text stating that no report was found for that company at that closing date.	Pass `ClosingDate`.
`XBRLReportDate`: company abbreviation or closing date missing	An error text stating that the company abbreviation and the closing date are required.	Pass `CompanyAbbreviation` and `ClosingDate`.
`XBRLDATASETPERIOD`, `XBRLUNIT`, `XBRLDEC`: bad date/`contextRef` combination or concept not found	Text `Error: …` or, for dataset period, `XBRLDatasetPeriod Error: …`	See the message. Pass dates or a `contextRef`, not both.
`XBRLUNIT`: concept id contains `abstract`	Empty cell	Expected for an abstract concept.
`XBRLCONTEXTPERIOD`: `contextRef` not in the report	Empty text. With `includeStart` true, two empty cells.	Use a `contextRef` from the report.

BYDIMENSIONS functions

Situation	What the cell shows	What to do
Missing or invalid argument	Text `Error:` with `INVALID_DIMENSION_FORMAT`, `INVALID_QNAME`, or `INVALID_TYPED_DIMENSION`. The message names the argument.	Correct that argument. An empty `dimensions` string is accepted.
No matching fact, or `XBRLFACTLABELBYDIMENSIONS` finds a fact but no label	Text `Error: NOT_FOUND: No matching fact found for the specified concept, period, and dimensions.` or `Error: NOT_FOUND: No matching label found after language and label role fallback.`	Check concept, period, and dimensions. For a missing label, check language and label role.
More than one fact matches	Text `Error: AMBIGUOUS_MATCH: Multiple matching facts found. Details: units=[…]`	Set `unit` or `linkroleURI`.

Tip: Use the task pane to insert functions automatically with correct parameters, then copy the formula to other cells.