rwa-filer
Validate regulatory returns against the published supervisory rules and write them in the format the regulator accepts.
It carries the Bank of England's validation rules for banking taxonomy v4.1.1
and evaluates them as the Bank's gateway does, for 14 reporting modules
(PRA001, PRA116, Capital+, leverage, MREL and financial statements).
Documentation: https://openafterhours.github.io/rwa_calculator/rwa-filer/
rwa-filer is a standalone package. It lives in the
rwa_calculator repository as a
uv workspace member and is released separately from rwa-calc: it depends on
Polars and, for its dashboard, a small web stack (Starlette, uvicorn, Jinja2), and
never imports rwa_calc. rwa-calc uses it to validate the
returns it generates; any other system that can produce template-level figures
can use it the same way.
Run it with uv, naming @latest:
uvx rwa-filer@latest --help
@latest makes each run check PyPI and use the newest release, so a return is
always checked with the newest rules and taxonomy rwa-filer carries. Without
it, uvx may run a copy it already has: one it fetched recently, or one
installed with uv tool install, for as long as that stays installed. Extras go
in quotes, so the shell leaves the brackets alone: a command that reads or
writes a workbook runs as uvx "rwa-filer[excel]@latest" ....
The manifest build writes records the version that wrote it. To repeat a run
on that version, name it in place of latest: uvx rwa-filer@0.1.0 ....
# As a library in a uv project (then run the command as `uv run rwa-filer`).
# The lock file holds it at one version; `uv lock --upgrade-package rwa-filer`
# moves it to the newest release
uv add rwa-filer
# As a command on your PATH, for a machine that has to run it offline. It
# stays on the version installed until you upgrade it
uv tool install rwa-filer
uv tool upgrade rwa-filer
# The dashboard: open a return in the browser and walk from the verdict to the
# broken rules to the cells on the template grid that broke them
uvx rwa-filer@latest dash return.xbrl
# Check a return: structure against the taxonomy, then the published rules
uvx rwa-filer@latest validate return.parquet \
--entity 5493001KJTIIGC8Y1R12 --reference-date 2027-03-31 --module PRA001
# Validate it and write the XBRL submission file, with a manifest
uvx rwa-filer@latest build return.parquet --out filing/ \
--entity 5493001KJTIIGC8Y1R12 --reference-date 2027-03-31 --module PRA001
# Record an approval against the file's checksum, and check it before upload
uvx rwa-filer@latest signoff filing/<name>.manifest.json --approver "C. Approver" --role "Head of Reporting"
uvx rwa-filer@latest verify filing/<name>.manifest.json
# What changed since the version already filed
uvx rwa-filer@latest diff filed.xbrl resubmission.xbrl
# A second opinion: have the Arelle XBRL processor check the written file
# against the Bank's taxonomy package, and compare its verdict on every rule
# with this package's own (needs the Bank's package)
uvx "rwa-filer[arelle]@latest" referee filing/<name>.xbrl --taxonomy-package boe-banking-v411.zip
# A blank workbook in the template layout, to fill in and validate
uvx "rwa-filer[excel]@latest" template --module PRA001 --reference-date 2027-03-31 --out return.xlsx
uvx rwa-filer@latest --help
A return is a table with one row per reported cell (table, sheet,
open_key, row, column, value), read from Parquet or CSV, or an Excel
workbook in the template layout (needs rwa-filer[excel]), or an XBRL instance
written by any system.
The regulator's own validation on upload is authoritative. A clean result from
rwa-fileris evidence a return is well-formed, not a guarantee that it will be accepted.
See CHANGELOG.md for release notes.
Metadata
Release files for rwa-filer 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rwa_filer-0.1.1.tar.gz | 2.1 MB | With provenance | Details for rwa_filer-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rwa_filer-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for rwa_filer-0.1.1-py3-none-any.whl |
Total release size: 4.2 MB
Release files / rwa_filer-0.1.1.tar.gz
| Download URL | rwa_filer-0.1.1.tar.gz |
|---|---|
| Size | 2.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a28ca9219859e551cd2332dbdc1719e411dfa3db4130b4c1388d31a9025de0d
|
|
BLAKE2b-256 checksum How to use checksums |
86f957e961ce7ba829ba57f320275925f8f6f022b2604a934b8e2ea380ad321c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logRelease files / rwa_filer-0.1.1-py3-none-any.whl
| Download URL | rwa_filer-0.1.1-py3-none-any.whl |
|---|---|
| Size | 2.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5295951de2c9ebf0402a8dd5607fb5ff20736ce4de40e3f629100c3b7fdd308b
|
|
BLAKE2b-256 checksum How to use checksums |
ed695fcba3348158390d8d6599a5b1bb9ba98af2b4dd723ba6650fe45542733e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logSecurity for rwa-filer 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for rwa_filer-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.