PRA Branch Return: Half-Yearly Reporting for UK Bank Branches

ByRegReportingDesk

The PRA Branch Return is the half-yearly return through which a UK branch of a non-UK bank tells the Prudential Regulation Authority what it is doing in the United Kingdom. From the 30 June 2026 reference date, in-scope firms complete a revised version of the form (template version 1.2), the product of policy statement PS6/25, whose branch-reporting changes took effect on 1 March 2026. For a third-country branch, this return, rather than the full COREP and FINREP suite that UK-incorporated banks file, is the main structured picture the PRA holds of the branch’s UK balance sheet, deposits and whole-firm liquidity.

The stakes are practical. The return has a fixed calendar of 30 June and 31 December reference dates and is collected through BEEDS. Branch Return submissions are XML files generated against the published Branch Return schema; BEEDS performs schema-conformity and other validation checks, with some failures blocking submission and others potentially leading the PRA to request resubmission. It also feeds a live supervisory question for many international banks: whether the scale of a branch’s UK retail and small-company deposit-taking is approaching the point at which the PRA expects the group to weigh a UK subsidiary. The numbers a branch reports here are read in that light.

Related reading: UK FINREP reporting: PRA requirements, which sets out the separate returns that UK-incorporated banks file.

The Branch Return calendar at a glance

  • Reference dates: 30 June and 31 December each year (half-yearly).
  • Remittance: within 30 business days of each reference date.
  • Revised template (version 1.2) applies from the 30 June 2026 reference date.
  • PS6/25 branch-reporting changes took effect on 1 March 2026.
  • Template, schema and validation files were refreshed in March 2026; the Branch Return Common problems note is dated 1 March 2026.
  • Submission channel: the Bank of England Electronic Data Submission (BEEDS) portal.

The Branch Return is a firm-specific regulatory return that captures the UK activities of PRA-authorised banks that are not headquartered in the United Kingdom. The PRA introduced it in 2015, after consulting in 2014 on its approach to branch supervision, precisely because a branch is part of a single overseas legal entity and does not produce the standalone prudential returns that a UK-incorporated bank does. The return gives supervisors a recurring, comparable read of what the branch actually books and funds in the UK.

The obligation lives in the PRA Rulebook. The Branch Return obligation sits in the PRA Rulebook Regulatory Reporting Part. SS34/15 sets out broader PRA expectations for branch reporting and links to the separate Reporting guidance for the Branch Return, which provides the field-level completion instructions. The supervisory approach that frames the return is set out in the current SS5/21, ‘International banks: The PRA’s approach to branch and subsidiary supervision’. As of September 2026, the current version was published on 22 April 2026 and became effective on 24 April 2026; PS6/25 was the May 2025 amendment that introduced the branch-reporting changes discussed here.

The return has evolved rather than appeared fully formed. The original 2015 form was revised in 2019, and PS6/25 then added a new part and reshaped the deposit and liquidity content. That history matters for anyone reusing an old mapping: fields have moved and been added across versions, and the version 1.2 template is not a cosmetic update of the earlier form. The legal character of the return is also worth keeping in view. It is a rulebook reporting obligation, so completing it accurately and on time is a rule requirement, but it is a supervisory information return rather than a capital or liquidity adequacy calculation that the branch must pass. The adequacy assessment for the whole firm rests with the home-state supervisor.

One point of confusion is worth settling early. The Branch Return is a banking return supervised by the PRA and administered through the Bank of England’s reporting systems. Third-country insurance branches report under the separate Solvency UK and insurance-branch regime, not through this return. Treating the two as interchangeable is a scoping error that surfaces in group compliance functions covering both banking and insurance operations.

Who must report: UK branches of international banks in scope

Scope follows the branch, not the group’s size. The Branch Return applies to all PRA-authorised branches of banks and designated investment firms with a registered office, or if none a head office, outside the UK; the reporting guidance does not set a minimum size threshold for that obligation. A small branch and a large branch of an international bank both file. That is different from the questions of authorisation and subsidiarisation, which are threshold-driven and sit in SS5/21.

The formal Branch Return population also includes PRA-authorised branches of designated investment firms headquartered outside the UK; this article otherwise focuses on bank branches. The branch is the UK establishment of one overseas legal entity, which is why the return asks about the UK activity of that entity rather than a standalone set of UK accounts. Where a group has several UK touchpoints, the relevant question for each collection is which authorised entity it belongs to, and the Branch Return attaches specifically to the authorised UK branch of the non-UK bank.

The distinction that changes the filing answer is the branch-versus-subsidiary line. A UK subsidiary of an overseas bank is a separately incorporated UK entity and files the standard UK prudential returns as any UK bank does. A branch has no separate UK legal personality, so it files the Branch Return instead. Firms operating both a UK subsidiary and a UK branch of the same group need to be clear about which entity a given data collection belongs to, because the two populate different returns on different rulebook bases.

Post-Brexit, the population is effectively the UK branches of third-country banks. Former EEA banks that once operated on passporting rights and continued in the UK did so by becoming authorised third-country branches, and they report on the same footing as any other non-UK bank branch. The EU regime uses a different legal and technical framework. Directive 2013/36/EU as amended by CRD VI contains harmonised third-country-branch reporting requirements, and Commission Implementing Regulation (EU) 2026/1757 now specifies EU reporting formats, definitions and frequencies; that Regulation applies from 28 March 2027. The UK Branch Return and the EU regime therefore must not be conflated, but it is no longer accurate to say that the EU has no equivalent third-country-branch reporting regime.

What the report contains: the Branch Return template parts and data points

The Branch Return is organised into parts that build a picture of the branch’s UK footprint. Across the form, firms report total assets and liabilities; deposits; loans and advances; financial guarantees and other commitments; derivatives; payments, settlement, custody and clearing; third-party services; intragroup assets and liabilities by counterparty for systemic branches; and whole-firm liquidity. Version 1.2 does not contain a profit-and-loss part. The PS6/25 revision added detail on deposits and brought whole-firm liquidity into the form, so that the return now carries summary liquidity coverage ratio (LCR) and net stable funding ratio (NSFR) information for the firm as a whole.

Amounts are reported in sterling, and the form’s memo items ask firms to record the exchange rates used where figures have been converted, so that supervisors can trace a number back to its underlying basis. The reporting guidance published with the template is the field-level authority for units, sign conventions and how each part is completed, and firms should follow it rather than carry across conventions from a different PRA return. Part 1 captures total assets and liabilities. Parts 8a and 8b apply only where total gross assets exceed £15 billion and require the five largest intragroup asset and liability exposures by counterparty; version 1.2 contains no profit-and-loss part.

The deposit part is where much of the recent policy attention landed. Firms report mandatory information on instant-access deposit balances and customer numbers. Transactional-account balances and customer numbers are no longer routinely mandatory: firms must be able to identify transactional accounts if the PRA requests that information, may report it voluntarily, and the PRA monitors instant-access customer numbers as an indicator that may trigger closer supervisory investigation as the retained 5,000 transactional-customer threshold is approached or exceeded.

The whole-firm liquidity information is a common source of misreading. It is a summary of the liquidity position of the entire overseas firm, not the UK branch in isolation, because a branch draws on the liquidity of the legal entity it belongs to. Reporting only UK-slice liquidity numbers where the form asks for the whole-firm position understates the very thing the return is designed to show. For the broader liquidity metrics themselves, our explainer on LCR, NSFR and ALMM liquidity reporting sets out how the ratios are constructed.

Two mechanical conventions catch preparers. The revised template greys out cells that are not required, and firms should leave those blank rather than force a zero. And several memo items ask for the reporting period end date and, where relevant, exchange rates used, so that supervisors can interpret figures that may be drawn from a home-state reporting date. For branches with total gross assets over £15 billion, Parts 8a and 8b require the five largest intragroup asset and liability exposures by counterparty; this is distinct from the granular UK large-exposures reporting suite for incorporated firms, and our large exposures reporting guide shows what that fuller regime looks like for UK-incorporated firms.

Consistency across the two half-years is its own quiet requirement. Because the PRA reads the return as a time series, unexplained swings between the 30 June and 31 December positions invite supervisory questions, and a change driven by a reclassification rather than real activity should be traceable in the firm’s own records. Preparers who keep a mapping note from each field to its source system make both the current filing and the next one easier to defend.

Reference dates, frequency and remittance deadlines

The Branch Return is half-yearly. The reference dates are 30 June and 31 December, and firms submit within 30 business days of each reference date. The calendar is fixed rather than rolling, which is the point of an evergreen return: the branch reports its position as at each half-year end, and the return for the half-year now closing is due within 30 business days after that period end. Reading the deadline as 30 calendar days is a recurring error; the count is in business days, which shifts the effective due date across Saturdays, Sundays, Christmas Day, Good Friday and bank holidays in England and Wales.

The first reference date on the revised form is 30 June 2026. Firms in scope complete template version 1.2 for that period and thereafter. Because the branch-reporting changes commenced on 1 March 2026 but the first collection on the new form falls at the 30 June 2026 half-year, there is a short window in early 2026 where the rule change is live but the first revised submission has not yet fallen due. Building the mapping for the new template before the 30 June 2026 close is the practical task in that window.

The half-yearly rhythm shapes the internal calendar. Durable practice is to run a dry build shortly after each half-year end, resolve validation failures early, and reserve the remaining days for review of the substantive numbers rather than for firefighting the file format.

PS6/25 added a timing accommodation for branches whose home-state reporting calendar does not line up with the PRA’s. Where data for the 30 June or 31 December period end is not available within the PRA’s submission window, the form allows a firm to provide the most recent data points it has submitted to its home-state supervisor and to state, in the designated memo rows, the reporting period end date actually used. This is a defined carve-out for genuine calendar mismatch, not a general licence to file late or to substitute a preferred date.

Submission channel and format: BEEDS, the schema and file rules

The Branch Return is collected through the Bank of England Electronic Data Submission portal (BEEDS). Other PRA reporting is not all submitted through BEEDS; the PRA states that CRD firms submit most reports required by the Regulatory Reporting, Close Links and Change in Control Parts through RegData, while specified collections use BEEDS. A firm needs an active BEEDS account and a registered principal user to file, and access administration is a prerequisite that is easy to leave until too close to the deadline for a new or newly in-scope branch.

Practical account mechanics repay attention. The principal user administers access and adds the people who prepare and submit, and a newly authorised branch needs that set up well ahead of its first reference date. Firms should also generate and check the file in good time, because schema-conformity or blocking failures can prevent acceptance, while other validation failures may result in the PRA contacting the firm and asking for a resubmission.

For Branch Return submissions, firms complete the current Excel template, generate an XML Data file and upload that XML file to BEEDS; the Excel workbook itself is not permitted as the BEEDS submission file. The Branch Return XML schema is version 1.2 from March 2026, and BEEDS checks conformity to the schema version valid for the relevant reference date. The revised template and its accompanying reporting guidance, published with PS6/25 and updated in early 2026, are the authoritative specification for field-level completion.

The Branch Return guidance provides for resubmission and requires the submission number to be increased by one for each resubmission. Firms should follow the current PRA and BEEDS instructions when correcting an accepted return.

Validation rules and the common rejection causes

BEEDS applies the PRA’s published validation rules to a Branch Return before it is accepted, and the Bank maintains a dedicated Branch Return validations file, refreshed in March 2026, that sets out the checks. A return that fails a blocking validation is not accepted, so the validation set is best treated as part of the build specification rather than a post-submission afterthought.

The Bank’s Branch Return Common problems note is dated 1 March 2026. It explains XML-file generation and identifies issues including removed or invalid XML mappings, datatype and enumeration errors, empty numeric fields, incorrect UTF-8 encoding, incorrect template or schema versions, and mandatory fields not reported. Because the detailed list lives in that primary note and the underlying files are data tables rather than narrative, this guide points to them rather than reproducing rule-level detail that would date quickly.

A validation pass is a floor, not a ceiling. A return can clear every automated check and still be wrong on substance, for example if whole-firm liquidity is populated with UK-only figures or a home-state reporting date is used without being flagged. The automated rules catch structure; the analytical accuracy of the numbers remains the filer’s responsibility.

Caveats and interactions: proportionality, subsidiarisation and adjacent returns

The Branch Return interacts directly with the supervisory judgements in SS5/21, and the deposit data in particular informs the PRA’s assessment of whether a branch’s UK retail and small-company transactional deposit-taking is reaching the levels at which it expects the group to consider a UK subsidiary. Filing the return does not itself trigger subsidiarisation, and the return is an input the supervisor reads alongside the firm’s business model and booking arrangements. Firms weighing the subsidiarisation question should check the current thresholds and expectations directly in SS5/21 rather than infer them from the return.

The return also connects to how the PRA supervises the branch’s booking arrangements and its reliance on the wider group. SS5/21 sets expectations about what a branch books in the UK and how it is funded, and the Branch Return is one of the ways the PRA sees those arrangements in numbers over time. That is why the whole-firm liquidity items sit in a UK branch return at all: the branch’s resilience is inseparable from the entity behind it.

The Branch Return is distinct from the full COREP and FINREP reporting applicable to UK-incorporated firms, but it is not the only PRA reporting obligation for a third-country bank branch. SS34/15 paragraphs 5.7-5.14 describe additional reporting used to comply with Regulatory Reporting 22.4, including information on own funds available to the branch, deposit-protection arrangements, risk-management arrangements, governance and key function holders, and recovery plans. Statistical collections run by the Bank are a separate stream again; a branch may face Bank of England statistical returns that are distinct from the Branch Return, as our note on the Bank of England Form BT statistical reporting illustrates.

Proportionality shows up inside the form rather than as an exemption from it. The greyed cells, the home-state data accommodation and the summary (rather than granular) liquidity items are how the PRA keeps the branch’s burden proportionate while still collecting the UK-specific data it needs. That design choice is why the return looks lighter than a UK bank’s full reporting stack. Keeping the Branch Return obligation distinct from statistical reporting in the compliance calendar avoids the assumption that a single submission covers both.

Recent and upcoming changes: PS6/25, version 1.2 and the Future Banking Data review

The defining recent change is PS6/25, the PRA’s 2025 policy statement on international firms, which updated SS5/21 and the branch-reporting framework, added a new part to the Branch Return Form, revised the completion guidance and revoked the older standalone liquidity-reporting supervisory statement by folding that guidance into SS34/15. The implementation date for the branch-reporting changes was set at 1 March 2026, and the revised template version 1.2, the version 1.2 schema, the updated validations and the common-problems note followed in early 2026. The first reference date on the new form is 30 June 2026.

Looking further out, the PRA is reconsidering how it collects banking data more broadly through its Future Banking Data programme, set out in a February 2026 discussion paper. The discussion paper proposes four broad principles for Future Banking Data, including proportionality and collecting data from a firm ‘once and well’ by minimising the data collected while maximising its use. For this paper, the PRA uses ‘banks’ to include PRA-authorised banks, building societies and designated investment firms, including subsidiaries of overseas firms and branches. It is a discussion paper on the PRA’s broader strategic approach to banking data. It does not amend the Branch Return or announce a Branch Return-specific change to its scope, content or frequency.

The discussion paper frames the wider programme around proportionality and reusing data the PRA already holds, and it applies to PRA-authorised banks and their subsidiaries and branches. The discussion paper does not announce a Branch Return-specific reform. Any subsequent change should be assessed against later PRA policy or rulemaking; the current Branch Return remains version 1.2. Nothing in the Future Banking Data material displaces the 30 June and 31 December calendar or the current template.

The current Branch Return remains template and schema version 1.2. The Bank publishes a Branch Return reporting schedule giving the business-day-exact last submission date for each half-year; firms should consult that schedule for the current cycle. The current March 2026 technical artefacts and the 1 March 2026 Common problems note remain the applicable specifications.

Frequently Asked Questions

Does a UK subsidiary of an overseas bank file the Branch Return?

No. A UK subsidiary is a separately incorporated UK entity and files the standard UK prudential returns for a UK bank. The Branch Return is for the UK branch of a non-UK bank, which has no separate UK legal personality. A group running both a UK subsidiary and a UK branch files each on its own basis.

Is there a size threshold below which a branch does not have to file?

The policy does not set a size threshold that excuses an in-scope branch from the return. Size matters to authorisation and to the PRA’s subsidiarisation expectations in SS5/21, but an in-scope branch files the Branch Return regardless of scale.

What happens if home-state data for 30 June or 31 December is not ready within the PRA window?

The form allows a firm to submit the most recent data points it has provided to its home-state supervisor and to record the reporting period end date used in the designated memo rows. This is a defined accommodation for calendar mismatch, and it must be flagged in the form rather than applied silently.

Does the whole-firm liquidity section mean the UK branch’s liquidity?

No. The whole-firm liquidity items ask for the liquidity position of the entire overseas firm, reflecting that a branch relies on the liquidity of the legal entity it belongs to. Reporting UK-only liquidity figures where the whole-firm position is required is a substantive error that automated validation will not necessarily catch.

How is an error corrected after the return has been submitted?

Corrections are made by resubmission through BEEDS, with the submission number increased by one for each resubmission. When correcting an accepted return, firms should follow the current PRA and BEEDS instructions.

Do branches file COREP and FINREP as well?

A third-country branch does not file the full UK-incorporated COREP and FINREP suite at branch level. However, the Branch Return is not the branch’s only PRA reporting obligation: for third-country bank branches, SS34/15 paragraphs 5.7-5.14 set out additional reporting used to comply with Regulatory Reporting 22.4, alongside any other applicable PRA and Bank of England collections.

Is the deadline 30 calendar days or 30 business days?

Thirty business days after the reference date. The count excludes Saturdays, Sundays, Christmas Day, Good Friday and bank holidays in England and Wales, so the effective due date moves each period and is later than a 30 calendar-day reading would suggest.

Key Takeaways

  • The PRA Branch Return is the half-yearly return for UK branches of non-UK banks, filed as at 30 June and 31 December within 30 business days of each date.
  • Build against template and schema version 1.2 and the March 2026 validations; the first reference date on the revised form is 30 June 2026.
  • Scope follows the authorised branch: the Branch Return applies to PRA-authorised branches of banks and designated investment firms headquartered outside the UK, without a minimum size threshold in the Branch Return guidance; subsidiaries report on their separate UK-incorporated basis.
  • Whole-firm liquidity means the entire overseas firm’s position, not the UK branch alone; UK-only figures here understate the return.
  • Where home-state data is not ready in the PRA window, submit the latest home-state data and record the period end date in the memo rows.
  • Submit and resubmit through BEEDS using the current Branch Return XML schema; check the 1 March 2026 Common problems note and the current validation spreadsheet before filing.
  • The deposit data feeds the PRA’s SS5/21 subsidiarisation assessment, so accuracy in that part matters beyond the return itself.

Sources and References

  • Bank of England / PRA, PS6/25 “International firms: Updates to SS5/21 and branch reporting” (May 2025): policy statement page.
  • Bank of England / PRA, Reporting guidance for the Branch Return (PS6/25 Appendix 4): ps625app2.pdf.
  • Bank of England / PRA, Branch Return template v1.2 (March 2026): branchreturnstemplatev12march2026.xlsx.
  • Bank of England / PRA, Branch Return Validations (March 2026): branch-return-validations-march-2026.xlsx.
  • Bank of England / PRA, Branch Return Common problems (1 March 2026): branch-return-common-problems.pdf.
  • Bank of England / PRA, SS5/21 “International banks: The PRA’s approach to branch and subsidiary supervision” (current version April 2026): publication page.
  • Bank of England / PRA, SS34/15 “Guidelines for completing regulatory reports”: publication page.
  • Bank of England / PRA, “Supervising international banks: the Branch Return” (2015 origin) and “Revision of the Branch Return” (2019): 2015 publication and 2019 revision.
  • Bank of England / PRA, Future Banking Data discussion paper (February 2026): discussion paper page.
  • European Commission, Commission Implementing Regulation (EU) 2026/1757 of 20 July 2026 laying down implementing technical standards for the application of Directive 2013/36/EU with regard to third country branches reporting (published in OJ 27 July 2026, applies from 28 March 2027): EUR-Lex.

What to have ready for the next Branch Return

For the next scheduled cycle, confirm BEEDS access and the registered user for the branch, build against Branch Return template and schema version 1.2, run the current validations, populate whole-firm liquidity on the required basis, and use the Part 9 reporting-period-end fields where the prescribed home-state data is unavailable for 31 December. The Bank’s published Branch Return reporting schedule gives the business-day-exact last submission date for each reference period.

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.

Similar Posts