User Guide

1. About anuboXBRL

anuboXBRL analytics add ins bring company disclosure data directly into Microsoft Excel. Our add ins support iXBRL (inline XBRL) filings for US‑GAAP (United States Generally Accepted Accounting Principles) and IFRS (International Financial Reporting Standards) with ESEF (European Single Electronic Format).

What is XBRL?

XBRL (eXtensible Business Reporting Language) is the open international standard for digital business reporting. Being used in more than 50 countries worldwide it is today's key technology for global capital markets and the key technology of tomorrow, considering sustainability data. XBRL replaces older reports based on paper, PDF and HTML with digital versions that are more accurate, clearly defined, platform-independent and testable.

Key Benefits of anuboXBRL Analyzer

• Enabling Microsoft Excel to eliminate the conceptual weakness of being designed for unstructured data only
• Enabling Microsoft Excel to use structured data, thereby enabling the full, unrestricted, power of Artificial Intelligence and Machine Learning (in development)
• Enabling Microsoft Excel to use the world standard XBRL
• Extending the usage scenarios of Microsoft Excel
• Fundamentally reducing the organizational risk of using Microsoft Excel in professional finance

anuboXBRL Add ins

• What they do: read iXBRL (inline XBRL) reports and insert their content in Microsoft Excel sheets.
• Two editions with different approaches:
  • anuboXBRL Reader = directly inserts report's content in the sheet
  • anuboXBRL Analyzer = inserts ANUBO custom functions (which insert report's content)
  The Analyzer's approach assigns semantic meaning and context information to inserted values, which extends usage scenarios for analyzing and AI. ANUBO custom functions are Microsoft Excel formulas that automatically retrieve and calculate data from iXBRL reports.
• User Guide scope: This User Guide covers both anuboXBRL Reader and anuboXBRL Analyzer. Sections that apply to Analyzer only are marked with the Premium tag.
• Who it's for: investment, finance and sustainability professionals; no prior XBRL knowledge required.
• Where can I get iXBRL reports for US GAAP and IFRS/ESEF?: see Chapter 4
• Terminology:
  • Concept (the reported item, e.g., Revenue)
  • Period (date or date range for the reported item)
  • Link role (defines how financial statements are organized into tables, like Balance Sheet or Income Statement)
  • Axis / member (categories for breaking down data, like 'Geographic Region: North America' or 'Product Line: Software')

2. Installation Scenarios

Scenario 1 – Individual User (Single Microsoft 365 Account)

1. Open Microsoft Excel → Insert → Get Add-ins.
2. Search for anuboXBRL Reader and click Add.
3. The task pane opens automatically and guides you to the registration page: https://azan92.anubo.eu/license-api/web/public-register/.
4. On the registration page, enter your email address to create your anubo account. We also recommend adding your Microsoft 365 sign-in address. This enables convenient single sign-on (SSO) in the add-in when you open Excel while signed in with that Microsoft 365 account.
5. After confirming the email, reload the add-in (or Microsoft Excel) and start using the anuboXBRL Reader.

Scenario 2 – Company or Organization (Microsoft 365 Domain)

1. Microsoft 365 admin: Go to Microsoft 365 Admin Center.
2. Go to Settings → Integrated Apps → Upload custom apps.
3. Select Office Add-in and provide the manifest URL: https://prod.azan82.anubo.com/app/v1/manifests/anubo-addin-stable.xml.
4. In Microsoft Entra ID → Enterprise applications → anuboXBRL → Permissions, click Grant admin consent for: User.Read, Files.Read.All, email, openid, profile, offline_access.
5. Ensure Integrated Apps and user consent policies allow add-ins.
6. Users then find anuboXBRL Reader available in Microsoft Excel automatically.

3. Installation and Setup

Supported Microsoft Excel platforms

• Microsoft Excel for Windows (Microsoft 365) – Full functionality
• Microsoft Excel for Mac (Microsoft 365) – Full functionality
• Microsoft Excel for the web – Full functionality
• Microsoft Excel for Windows (Office LTSC 2024 / LTSC 2021) – Full functionality
• Microsoft Excel for Windows (Office 2019, perpetual) – Supported via Credential Login. Office 2019 update must be up to date.

Sign in and licensing

• Microsoft 365 / Office LTSC 2024 / Office LTSC 2021
  If your organization allows it, you are signed in automatically via Microsoft SSO (Single Sign-On) when the task pane opens. SSO allows you to sign in automatically using your Microsoft work account.
  If you see a consent prompt, approve it (if your organization allows user consent), or ask your company administrator to grant tenant-wide consent for the add-in.
• Single-user license policy
  The anubo Add-in license is a single-user license. If you log in again while logged in—for example, on a different device—the original login will be automatically logged out. This allows you to switch between devices and use the add-in, but it is not possible to use a single license on multiple devices simultaneously.
• Office 2019 (perpetual)
  SSO is not available. The add-in uses Credential Login instead. Credential Login requires entering your ANUBO account email and password manually.
  1. Open the task pane (Microsoft Excel ribbon → anuboXBRL).
  2. Enter the email and password you registered with.
  3. After successful login, your license is validated exactly as it is with SSO on other platforms.

Company/Microsoft 365 Administrators

Some features—such as automatic SSO sign-in—depend on your Microsoft 365 tenant configuration. A Microsoft 365 tenant is your organization's Microsoft cloud environment. Please review the following:

A) Microsoft 365 Admin Center (For organizational deployment)

1. Open Microsoft 365 Admin Center (https://admin.microsoft.com)
2. Go to Settings → Integrated Apps
3. Click Upload custom apps
4. Select app type Office Add-in
5. Provide the manifest URL: https://prod.azan82.anubo.com/app/v1/manifests/anubo-addin-stable.xml
6. Follow the prompts to complete the installation

B) App permissions & consent (Microsoft Entra ID / Azure AD)

1. Open Entra ID (formerly Azure AD) → Enterprise applications and locate anuboXBRL (or search by the Application (client) ID from the add-in manifest). Entra ID is Microsoft's identity and access management service.
2. Open Permissions (or Permissions and consent).
3. Click Grant admin consent for the required scopes: User.Read, Files.Read.All, email, openid, profile, and offline_access.
4. Confirm the status shows Granted for [Organization].
5. If your organization disables user consent, admin consent is required before first use.

C) Policies that can block SSO

• Integrated Apps / Office Add-ins must be allowed.
• User consent policy determines whether end users can accept the consent prompt themselves.
• Conditional Access (MFA / device rules) can block token issuance.
• End users must be signed into Office with their Microsoft 365 work/school account.

D) Firewall configuration requirements

To ensure reliable connectivity, allow outbound HTTPS to these domains (no inbound rules needed):

• https://azan92.anubo.eu – Main backend API server
• https://prod.azan82.anubo.com – Production application server
• https://anubo.com – Company website and support
• https://appsforoffice.microsoft.com – Office.js and add-in platform resources (Microsoft)

Ports

• HTTPS (443) required
• HTTP (80) optional, only for non-sensitive fallback requests if used by your environment (HTTPS is recommended)

Proxy / content filtering

• Ensure no proxy rule or content filter blocks the domains above.
• Allow long-running HTTPS requests (data processing and downloads may be larger).

Firewall Rules

Your IT administrator should configure the firewall to:

1. Allow outbound HTTPS (443) traffic to the domains listed above
2. Allow outbound HTTP (80) traffic to the domains listed above
3. Ensure no proxy or content filtering blocks these domains

4. Quick Start

4.1 Open the task pane

Microsoft Excel ribbon → Add‑ins → anuboXBRL. The task pane appears on the right.

[Screenshot placeholder: Task pane collapsed with section headers]

4.2 Load a report

1. In Company & Reports, choose a company and report date (closing date).
2. Click Load.

[Screenshot placeholder: Company & Reports selection]

4.3 Insert a label and a value

1. Go to Report Data – Items.
2. Select a concept (e.g., Revenue) and a period (instant = single date; duration = date range).
3. Select a cell in the sheet and click Insert Label or Insert Value.

Reader: inserts the final number. Analyzer: inserts a dynamic formula that recalculates.

[Screenshot placeholder: Insert Label/Value]

4.4 Create a table

1. Open Report Data – Tables.
2. Pick a link role (the layout of a table inside the report).
3. Optionally choose axes/members (breakdowns like region/product) and period pairs (e.g., Q vs PY).
4. Click Insert Table.

Reader: writes static, properly scaled values. Analyzer: writes dynamic formulas for labels and values.

[Screenshot placeholder: Tables setup and result]

5. Where to get US-GAAP/IFRS/ESEF iXBRL reports?

The anuboXBRL Reader & Analyzer Add-in comes with several demo reports (IFRS and US-GAAP) so you can explore its features right away.

If you prefer to analyze your own company reports, you can upload XBRL or iXBRL files directly into the Add-in.

anuboXBRL Reader and anuboXBRL Analyzer Basic require the add-in user to manually download iXBRL reports from public filing portals or company websites. Future editions of the Add-in (anuboXBRL Analyzer Classic and Professional) will include integrated data retrieval, allowing direct access to public disclosures without manual downloads.

Below you'll find the most reliable sources and short step-by-step instructions for both US-GAAP and IFRS/ESEF disclosures.

US-GAAP Filings (SEC.gov)

Source: SEC.gov | Search Filings

How to Download a Report

1. Visit SEC's Company Search and enter the company name or ticker symbol.
2. Choose a report (for example *10-K* or *10-Q*).
   If "Interactive Data" appears, XBRL data are available — click Interactive Data. Interactive Data is the machine-readable version of company disclosures. The US SEC uses this term.
3. In the displayed report, select the yellow button labeled *10-Q* or *10-K* in the top-left corner.
4. Open the Menu (top-left) and choose "Save XBRL ZIP file."
5. In the anuboXBRL Analyzer, upload the downloaded iXBRL ZIP file to start your analysis. The iXBRL ZIP file contains the structured financial/non-financial data that can be analyzed with anuboXBRL.

IFRS / ESEF Filings (European Issuers)

Source: filings.xbrl.org | Filing Index

How to Download a Report

1. Open filings.xbrl.org.
2. Search for the company you wish to analyze.
3. Click the Download button next to the desired filing to obtain the iXBRL ZIP file.
4. Upload this iXBRL ZIP file in the anuboXBRL Analyzer.

Notes

• Future editions of the Add-in (anuboXBRL Analyzer Classic and Professional) will include integrated data retrieval, allowing direct access to public disclosures without manual downloads.

6. Task Pane Tour

6.1 Company & Reports

Manage which XBRL report (the structured financial/non-financial data file) you work with in Microsoft Excel.

• Demo reports: Two demo datasets are available out of the box:
  • US‑GAAP (United States GAAP)
  • ESEF/IFRS (European Single Electronic Format / IFRS)
• Upload (ZIP file):
  • Click Upload to add your own report as a single .zip file.
  • After uploading, the report appears in the Company dropdown list.
  • Uploaded reports are stored in your personal cloud space (only you can access them). Personal cloud is your private online storage space for uploaded reports.
  • Storage limits (per user):
    • anuboXBRL Reader: up to 10 reports
    • anuboXBRL Analyzer basic: up to 100 reports
• Select a report:
  • Choose a company/report and Closing Date from the dropdowns.
  • Selection automatically triggers either:
    • Processing of the XBRL report (first time) - Processing converts the raw XBRL data into a format that Microsoft Excel can work with
    • Or retrieval of the already processed dataset from your personal cloud
• Rename:
  • You can rename a report (e.g., to a clear, short Company Abbreviation).
  • The Company Abbreviation is what appears in ANUBO custom functions (e.g., =ANUBO.XBRLValue(CompanyAbreviation, ...) or =ANUBO.XBRLValue("DEMO_MICROSOFT_10K", ...)).
• Delete:
  • Remove an uploaded report from your personal cloud when it's no longer needed.
  • This action removes it from the Company dropdown and frees personal storage.

Tip: After uploading, allow processing to complete before inserting items or tables. Processing status is shown in the task pane.

6.2 Report Data – Items

• Search/select a concept (reported item).
• Choose period (instant/duration).
• Actions:
  • Insert Label (name of the concept)
  • Insert Value (number, scaled based on decimals)
  • Insert All (batch for the current selection)

6.3 Report Data – Tables

• Pick a link role (the layout of a table inside the report).
• Choose axes and members (breakdowns like region/product).
• Select period pairs for columns (e.g., Q vs PY).
• Click Insert Table.

Reader: writes static, properly scaled values. Analyzer: writes dynamic formulas for labels and values.

[Screenshot placeholder: Tables setup and result]

6.4 Report Data – Sections

• Insert curated sections (groups of items) in one step.
• Behavior mirrors Items (Reader static / Analyzer dynamic).

6.5 Attributes Premium

• Analyzer only: Insert a professional report header; change parameters in ANUBO Custom Functions.
• In Reader, this section is visible but disabled with an upgrade prompt.

6.6 Settings and Status

• Edition badge (Reader/Analyzer), session status, diagnostics.
• Links to learn more and support.

7. Reader vs Analyzer

7.1 At a glance

7.2 When to use which edition

• Reader: final numbers for static reporting packs and speed.
• Analyzer: dynamic workbooks that should refresh/recalculate.

You can upgrade from Reader to Analyzer from within the task pane wherever premium actions are shown.

Upgrade to anuboXBRL Analyzer

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.

8.1 Core Data Functions Premium

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

8.2 Metadata Functions Premium

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

8.3 Function Syntax Premium

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"). Useful for creating readable report headers and labels in your Excel worksheets.

Syntax (preferred – using dates)
=ANUBO.XBRLLabel(CompanyAbreviation, closingDate, "", [datasetStartDate], datasetEndDate, ConceptID)

Optional (expert – using contextRef)
=ANUBO.XBRLLabel(CompanyAbreviation, closingDate, contextRef, "", "", ConceptID)

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).
• 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").
• 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.

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 is not found, returns an error message.

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.

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, with numeric values properly scaled according to the XBRL decimals information. This is the primary function for extracting financial data from XBRL reports into your Excel worksheets.

Syntax (preferred – using dates)
=ANUBO.XBRLValue(CompanyAbreviation, closingDate, "", [datasetStartDate], datasetEndDate, ConceptID)

Optional (expert – using contextRef)
=ANUBO.XBRLValue(CompanyAbreviation, closingDate, contextRef, "", "", ConceptID)

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).
• 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").
• 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.

Returns
A numeric value (properly scaled) or text value depending on the concept type. For example, revenue values are returned as numbers with appropriate scaling (e.g., millions). Text concepts return their text value. If the concept is not found, returns an error message. For abstract concepts, returns an empty string.

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.
• Numeric values are automatically scaled based on the XBRL decimals information. For example, if decimals = -6, the value is displayed in millions.
• 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.

ANUBO.XBRLTABLELABEL

Purpose: Retrieve the human-readable label for table-related elements in structured financial statements. This function returns different types of labels depending on the WhichLabel parameter: table titles, axis-member labels, row concept labels, or period labels. Useful for building comprehensive report headers and labels that match the structure of XBRL tables (presentation linkbases).

Syntax (preferred – using dates)
=ANUBO.XBRLTABLELABEL(CompanyAbreviation, closingDate, "", [datasetStartDate], datasetEndDate, TableRole, RowConcept, AxisMemberCombo, WhichLabel)

Optional (expert – using contextRef)
=ANUBO.XBRLTABLELABEL(CompanyAbreviation, closingDate, contextRef, "", "", TableRole, RowConcept, AxisMemberCombo, WhichLabel)

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).
• datasetStartDate: Optional start date (YYYY-MM-DD) for duration periods. Required when WhichLabel is "period". Leave empty for instants or when not retrieving period labels.
• datasetEndDate: Required end/instant date (YYYY-MM-DD) when contextRef is not used. Required when WhichLabel is "period".
• TableRole: Link role URL that identifies the specific table (financial statement) in the report (e.g., "http://www.microsoft.com/20250331/taxonomy/role/Role_StatementINCOMESTATEMENTS").
• RowConcept: Concept QName for the row (e.g., "us-gaap:Revenue"). Required when WhichLabel is "rowConcept".
• AxisMemberCombo: Dimension notation combining axis and member (e.g., "srt:ProductOrServiceAxis:us-gaap:ProductMember"). Required when WhichLabel is "axisMember".
• WhichLabel: Type of label to return. Must be one of: "table" (table title), "axisMember" (axis and member label), "rowConcept" (row concept label), or "period" (period label).
• contextRef: Optional expert parameter. Normally leave empty (""). Use only if you already know a specific contextRef (note: may not be fully supported for all label types).

Returns
The requested label as text, depending on WhichLabel:

• "table": Returns the table title (e.g., "Consolidated Statements of Income")
• "axisMember": Returns the axis and member label (e.g., "Product or Service – Product")
• "rowConcept": Returns the row concept label (e.g., "Revenue from Contract with Customer")
• "period": Returns the period label formatted as "YYYY-MM-DD – YYYY-MM-DD" for duration periods

Notes

• The WhichLabel parameter determines what type of label is returned and which other parameters are required.
• For WhichLabel="period", provide dates (preferred) using datasetStartDate and datasetEndDate.
• For WhichLabel="table", only TableRole is required; RowConcept and AxisMemberCombo can be empty.
• For WhichLabel="axisMember", provide AxisMemberCombo; RowConcept can be empty.
• For WhichLabel="rowConcept", provide RowConcept; AxisMemberCombo can be empty.
• The TableRole (link role URL) identifies which financial statement table to use from the report's presentation structure.

ANUBO.XBRLTABLEVALUE

Purpose: Retrieve the value for a table cell in structured financial statements. This function returns the actual data value (number or text) from a specific table cell, with numeric values properly scaled according to the XBRL decimals information. Unlike ANUBO.XBRLValue, this function works with table structures (presentation linkbases) and requires you to specify the table, row concept, and dimension member to locate the exact cell.

Syntax (preferred – using dates)
=ANUBO.XBRLTABLEVALUE(CompanyAbreviation, closingDate, "", [datasetStartDate], datasetEndDate, TableRole, RowConcept, AxisMemberCombo)

Optional (expert – using contextRef)
=ANUBO.XBRLTABLEVALUE(CompanyAbreviation, closingDate, contextRef, "", "", TableRole, RowConcept, AxisMemberCombo)

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).
• datasetStartDate: Optional start date (YYYY-MM-DD) for duration periods. Required when matching periods in tables. Leave empty for instants.
• datasetEndDate: Required end/instant date (YYYY-MM-DD) when contextRef is not used. Required to match the period in the table structure.
• TableRole: Link role URL that identifies the specific table (financial statement) in the report (e.g., "http://www.microsoft.com/20250331/taxonomy/role/Role_StatementINCOMESTATEMENTS").
• RowConcept: Concept QName for the row (e.g., "us-gaap:Revenue").
• AxisMemberCombo: Dimension notation combining axis and member (e.g., "srt:ProductOrServiceAxis:us-gaap:ProductMember"). Use empty string ("") for non-dimensional facts.
• contextRef: Optional expert parameter. Normally leave empty (""). Use only if you already know a specific contextRef (note: may not be fully supported for table-based lookups; dates are preferred).

Returns
A numeric value (properly scaled) or text value from the specified table cell. For example, revenue values are returned as numbers with appropriate scaling (e.g., millions). Text concepts return their text value. If the table cell is not found or the period doesn't match, returns an error message or empty string.

Notes

• This function is designed for working with structured table layouts (presentation linkbases) in XBRL reports.
• Provide either dates (preferred) or a contextRef (expert), not both. For table-based lookups, dates are generally required.
• With dates, datasetEndDate is required; datasetStartDate is optional but helps match the correct period in the table.
• With contextRef, leave datasetStartDate and datasetEndDate empty (note: contextRef may not be fully supported for table lookups).
• The function matches the specified period, row concept, and dimension member to find the exact cell in the table structure.
• Numeric values are automatically scaled based on the XBRL decimals information. For example, if decimals = -6, the value is displayed in millions.
• Use ANUBO.XBRLTABLELABEL in combination with this function to create readable reports with both labels and values from table structures.

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 (preferred – using dates)
=ANUBO.XBRLDimension(CompanyAbreviation, closingDate, "", datasetEndDate, ConceptID, DimensionName)

Optional (expert – using contextRef)
=ANUBO.XBRLDimension(CompanyAbreviation, closingDate, contextRef, "", ConceptID, DimensionName)

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).
• 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").
• 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.

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, returns an empty string.

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.

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(CompanyAbreviation, closingDate)

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).

Returns
The company abbreviation as text (e.g., "DEMO_MICROSOFT_10K") if the report exists for the specified company and closing date. Returns an error message if the report is not found or if required parameters are missing.

Notes

• Both parameters are required.
• 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, the function returns an error message indicating the report could not be located.

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(CompanyAbreviation, closingDate)

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).

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. Returns an error message if the report is not found, if required parameters are missing, or if the date format is invalid.

Notes

• Both parameters are required.
• 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, the function returns an error message indicating the report could not be located.

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 (preferred – using dates)
=ANUBO.XBRLDATASETPERIOD(CompanyAbreviation, closingDate, "", [datasetStartDate], datasetEndDate, ConceptID)

Optional (expert – using contextRef)
=ANUBO.XBRLDATASETPERIOD(CompanyAbreviation, closingDate, contextRef, "", "", ConceptID)

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).
• 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").
• 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.

Returns
Duration: YYYY-MM-DD – YYYY-MM-DD
Instant: YYYY-MM-DD

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.

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 (preferred – using dates)
=ANUBO.XBRLUNIT(CompanyAbreviation, closingDate, "", [datasetStartDate], datasetEndDate, ConceptID)

Optional (expert – using contextRef)
=ANUBO.XBRLUNIT(CompanyAbreviation, closingDate, contextRef, "", "", ConceptID)

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).
• 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").
• 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.

Returns
The unit information as text (e.g., "USD", "EUR", "shares", "pure"). If the concept is not found, returns an error message. For abstract concepts, returns an empty string.

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.

ANUBO.XBRLDEC

Purpose: Retrieve decimal precision information (scaling/accuracy) for a concept at a specific period. This tells you how numbers are scaled (e.g., millions, billions) and helps you understand the precision of reported values. This function is commonly used in column headings.

Syntax (preferred – using dates)
=ANUBO.XBRLDEC(CompanyAbreviation, closingDate, "", [datasetStartDate], datasetEndDate, ConceptID)

Optional (expert – using contextRef)
=ANUBO.XBRLDEC(CompanyAbreviation, closingDate, contextRef, "", "", ConceptID)

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).
• 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").
• contextRef: Optional expert parameter. Normally leave empty (""). Use only if you already know a specific contextRef and want to retrieve decimals for that context directly.

Returns
A text value describing the decimal precision and scaling, for example:

• "in millions" (decimals = -6)
• "in billions" (decimals = -9)
• "in thousands" (decimals = -3)
• "Decimals: -6" (if a specific mapping is not available)

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 information is automatically applied when using ANUBO.XBRLValue, but this function lets you inspect the scaling explicitly.

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(CompanyAbreviation, closingDate, contextRef, [includeStart])

• CompanyAbreviation: Company abbreviation (e.g., "DEMO_MICROSOFT_10K").
• closingDate: Report closing date (YYYY-MM-DD).
• 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.

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 function returns an empty result.

8.4 Error Handling Premium

• #VALUE!: Invalid parameters or concept not found
• #REF!: Company or report not loaded
• #N/A: No data available for the specified criteria

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

9. Advanced Features

9.1 Working with Dimensions Premium

XBRL reports often break down data by dimensions (axes) like product lines, geographic regions, or business segments.

• Finding dimensions: Use the task pane's table view to see available axes and members
• Dimension syntax: "AxisName:MemberName" (e.g., "srt:ProductOrServiceAxis:us-gaap:ProductMember")
• Multiple dimensions: Separate with semicolons in custom functions

9.2 Period Types Premium

• Instant: Point-in-time data (balance sheet items)
  • Use empty startDate and endDate: ANUBO.XBRLValue("COMPANY", "2024-12-31", "", "", "", "concept")
• Duration: Period data (income statement items)
  • Specify both dates: ANUBO.XBRLValue("COMPANY", "2024-12-31", "", "2024-01-01", "2024-12-31", "concept")

9.3 Link Roles (Table Layouts)

Link roles are predefined table structures that organize data into standard formats. Common types include:

• Balance Sheet (Statement of Financial Position)
• Income Statement (Statement of Income / P&L)
• Statement of Cash Flows
• Notes to Financial Statements

Use the task pane's table view to browse available link roles for your selected report.

9.4 Scaling and Decimals Premium

XBRL values include decimal information for proper scaling:

• Negative decimals (e.g., -6): Divide by 1,000,000 (millions)
• Positive decimals (e.g., 2): Round to 2 decimal places
• Pure units: No scaling applied

ANUBO functions automatically apply correct scaling based on the XBRL data.

9.5 Custom Report Headers Premium

Analyzer only: Use the Attributes section to insert professional report headers with:

• Company name and logo
• Report date and period
• Currency and units
• Regulatory information

10. Troubleshooting

10.1 Common Issues

10.2 Data Quality Issues

• Missing values: Some concepts may not have data for all periods
• Inconsistent periods: Different companies may use different reporting periods
• Label variations: Same concept may have different labels across reports

10.3 Performance Tips

• Load reports once: Keep reports loaded to avoid re-processing
• Use specific periods: Narrow date ranges for faster lookups
• Limit table size: Large tables with many dimensions can be slow
• Close unused workbooks: Free up memory for better performance

10.4 Getting Help

In order to get help please check https://anubo.com/software/resources/support/

ANUBO.ANUBO_ADD Premium

Purpose: Test function to verify that the custom functions module is working correctly. This is a diagnostic tool that simply adds two numbers together. Anubo support may ask you to perform this test if you experience issues with other ANUBO functions. This function description is placed in the Troubleshooting section because it is primarily used for diagnostic purposes rather than financial analysis.

Syntax
=ANUBO.ANUBO_ADD(number1, number2)

• number1: First number to add.
• number2: Second number to add.

Returns
The sum of the two numbers. If custom functions are not working correctly, this function may return an error or #VALUE!.

Notes

• If support asks you to test this function, enter two numbers and verify the result is their sum.
• If this function works correctly, it confirms that the custom functions infrastructure is operational.

11. Glossary

11.1 XBRL Terms

Concept

A specific financial reporting item (e.g., "Revenue", "Assets", "Cash") defined in a taxonomy. In anuboXBRL functions and documentation, we use "concept" to refer to both the taxonomy definition and the reported value (fact) in company reports, as this term is more intuitive for finance professionals.

Fact

A single piece of business information (a reported data point) in an XBRL instance document or inline XBRL document. Each fact is assigned to a concept from the taxonomy and is contextualized by dimensions such as reporting entity, period, and unit of measure. Note: In anuboXBRL user documentation and function parameters, we use the term "concept" for simplicity, referring to the reported item regardless of whether we mean the taxonomy definition or the actual fact in the report.

Taxonomy

A dictionary of concepts and their relationships used for XBRL reporting (e.g., US-GAAP, IFRS)

Instance Document

The actual XBRL report containing company data tagged with concepts

Link Role

A URL that defines how concepts are organized into tables or presentations

Dimension

An axis for breaking down data (e.g., by product line, geographic region, business segment)

Member

A specific value along a dimension (e.g., "North America" for geographic dimension)

Period

The time period for reported data (instant for balance sheet, duration for income statement)

Unit

The measurement unit for numeric values (e.g., USD, shares, pure numbers)

Decimals

Information about how to scale numeric values (negative = divide, positive = round)

11.2 anuboXBRL Terms

Reader Edition

Free version that inserts static values and labels

Analyzer Edition

Premium version with dynamic formulas and advanced features

Company Abbreviation

Short identifier used in custom functions (e.g., "DEMO_MICROSOFT_10K")

Closing Date

The report date (as-of date) for the financial statements

Personal Cloud

Your private storage space for uploaded reports

Processing

Converting raw XBRL data into anuboXBRL's internal format

11.3 Microsoft Excel Terms

Custom Function

User-defined Microsoft Excel formula (like ANUBO.XBRLValue)

Task Pane

The side panel in Microsoft Excel that provides the anuboXBRL interface

Add-in

A Microsoft Excel extension that adds new functionality (like anuboXBRL)