Download notebook

Select the reporting year and aggregation level. Detail-level tables are available for benchmark years.

Import#

import mario

db = mario.parse_bea(path="/path/to/SUPPLY-USE.xlsx", year=2024, level="summary")

Result · A MARIO database. Inspect db, db.get_index("all") and db.units before selecting quantities for your analysis.

Inputs and options#

Where the files come from

Relevant official pages:

MARIO currently supports only the SUPPLY-USE bundle. It does not yet parse:

  • MAKE-USE-IMPORTS (BEFORE REDEFINITIONS)

  • TOTAL AND DOMESTIC REQUIREMENTS

Supported levels and years

The parser currently supports three aggregation levels:

  • summary: 1997 to 2024

  • sector: 1997 to 2024

  • detail: 2007, 2012, 2017

These ranges were verified directly on the current official workbook bundle.

Accepted path inputs

parse_bea(...) accepts any of these:

  • the official SUPPLY-USE.zip

  • one extracted directory containing the BEA workbooks

  • one workbook path inside that directory

In all cases you still provide:

  • year=

  • level=

Expected extracted structure and matrix mapping

Typical extracted SUPPLY-USE bundle:

SUPPLY-USE/
├── Supply_Summary.xlsx
├── Use_Summary.xlsx
├── Supply_Sector.xlsx
├── Use_Sector.xlsx
├── Supply_Detail.xlsx
└── Use_SUT_Detail.xlsx

level= selects the workbook pair and year= selects one year inside that pair.

MARIO reads the bundle as a split-native SUT: S from the domestic-industry block of the supply workbook, U and Yc from the use workbook, Va from the use-workbook footer rows, and Vc from the supply-side columns such as imports, margins, and product taxes. The result should therefore be treated as a mixed-valuation SUT: basic-price supply and purchaser-price use.

import mario

db = mario.parse_bea(
    path="/path/to/SUPPLY-USE",
    year=2024,
    level="summary",
)

db

db = mario.parse_bea(
    path="/path/to/SUPPLY-USE",
    year=2024,
    level="sector",
)

db = mario.parse_bea(
    path="/path/to/SUPPLY-USE",
    year=2017,
    level="detail",
)
What the parser builds

MARIO reads the BEA bundle as a split-native SUT:

  • S from the BEA Supply workbook

  • U and Yc from the BEA Use workbook

  • Va from the use-workbook footer rows

  • Vc from the supply-workbook commodity-side columns for imports, CIF/FOB adjustments, trade and transport margins, and product taxes

This is therefore a mixed-valuation table:

  • supply is read at basic prices

  • use is read at purchaser prices

base = db["baseline"]
for name in ["S", "U", "Yc", "Va", "Vc"]:
    print(name, base[name].shape)
Caveats

  • table="SUT" is the only supported mode right now.

  • The parser does not yet expose the separate MAKE-USE-IMPORTS (BEFORE REDEFINITIONS) bundle.

  • The parser does not treat TOTAL AND DOMESTIC REQUIREMENTS as raw database inputs.

  • detail coverage is much narrower than summary and sector in the current official release.

Continue with Inspect and query a database or Calculate matrices.