Step 1 · Upload
Drag in the bank template, as-is
Upload the system template or your own workbook, with no re-keying or reformatting.
BSP FRP reporting software, ready for FRP v15 and v16
Wekalp’s FRP package takes the template your team already fills in, maps it to the BSP’s schedules, and runs the BSP’s business rules and XML schema checks before the file is uploaded to the BSP portal, so errors are fixed in the bank instead of coming back after upload. Wekalp is ready with both FRP v15 and FRP v16, for the FRP and the eight reports filed alongside it.
All schedules coveredAcross v15 and v16, from the FRP balance sheet to the Published Balance Sheet.
FRP v15 and v16Templates, validation rules and schemas for both versions.
8,500+ BSP rulesBusiness rules run with their preconditions before the file is generated.
Reports covered
What the BSP FRP package covers, in v15 and v16
The Financial Reporting Package is the BSP’s core prudential reporting: the financial statements and supporting schedules banks file each period, with related reports on capital, liquidity, branches, trust, microfinance, e-money and credit allocation filed alongside it. Both versions use the same nine reports and 105 schedules, and Wekalp is ready with v15 and v16 for all of them. FRP v16 moves to API-based submission, with live submission from the June 30, 2027 reference period.
FRP · 54 schedulesFinancial Reporting PackageThe balance sheet and income statement, with schedules behind each line: deposits, loans by status and credit-impairment stage, securities, bills payable, interest income and expense, off-balance-sheet items, maturity and repricing.
BRIS · 7 schedulesReport of Selected Branch AccountsSelected balance sheet and income statement accounts, loan aging, deposit breakdown, loans-to-deposits ratio, interest rates and long-outstanding inter-office items.
CAR15 · 5 schedulesCapital Adequacy RatioA simplified risk-based capital ratio: qualifying capital against on- and off-balance-sheet credit risk and operational risk-weighted assets.
EMONEY · 2 schedulesElectronic Money ReportE-money Form I with a schedule of e-money balances.
FRPTI · 20 schedulesReport on Trust and Other Fiduciary ServicesThe trust balance sheet and income statement, with investments, loans, unit investment trust funds, other fiduciary accounts and PERA administration, in peso and FCDU/EFCDU.
MICRO · 2 schedulesReport on Microfinance ProductsMicrofinance product balances, with an income statement on retail microfinance operations.
MLR · 3 schedulesMinimum Liquidity RatioThe ratio itself, the stock of liquid assets and the qualifying liabilities it is measured against.
MSME · 9 schedulesReport on Compliance with Mandatory Credit AllocationThe credit allocation to micro, small and medium enterprises required under R.A. 6977: loan portfolio base, eligible loans and investments, and loans to BMBEs.
PBS · 1 schedulePublished Balance SheetThe solo balance sheet for the head office and branches, published for public disclosure.
One workflow for all nine: every report runs through the same template mapping, BSP business rules, XML schema checks, maker-checker approvals and filing history. FRP v16 timelines are set by the BSP, so check current BSP issuances.
How it works
BSP FRP reporting in five steps, from bank template to BSP-ready XML
The FRP is filed as schedules of figures. The platform takes the template your team fills in, or the schedules Source-to-Report Automation computes, maps it to the BSP’s structure, and runs the regulator’s own checks before the file leaves the bank. The same steps apply to FRP v15 and FRP v16.
Step 2 · Map
Every sheet matched to its schedule
Sheets are auto-matched to BSP schedules. Anything that doesn’t map is flagged and left out.
Step 3 · Verify
Report lines counted before anything moves
Detected, expected, missing and incorrect lines per schedule, with the mapped template to download.
Step 4 · Validate
The BSP’s business rules, run in-house
Every rule runs with its preconditions, so rules that don’t apply to the period are skipped, not failed.
Step 5 · Submit
Schema-perfect XML, checked first
Each element is checked against the published XSD, approved by the submission team and filed, with regulator feedback tracked until accepted.
What changes for your team
As-isYour own workbook goes in as it is, with no re-keying into a new format
BeforeBSP rule and schema errors are fixed before the portal upload, not after it
TracedEach failed check shows the rule or schema constraint and the value that broke it
The to-and-fro problem
Run the BSP’s FRP checks before you upload, not after
On the BSP portal, the FRP XML is checked only once it has been uploaded. A failed rule or a schema error comes back as a rejection, the team fixes the template, regenerates the file and uploads again, often close to the deadline. Wekalp runs the same business rules and the published XSD inside the bank, so the file that reaches the portal has already passed.
Business rules
Every BSP rule, with its precondition and formula
Each rule shows the precondition that decides whether it applies, the formula, the values it saw and the result. Rules that do not apply to the period are skipped, not failed.
Schema
Every element checked against the published XSD
Each element is compared with its schema constraints: type, decimal places, range and pattern. Warnings such as an element defined in the XSD but empty in the data are flagged for a decision before upload.
Without and with pre-upload checks
WithoutUpload, wait for the BSP’s checks, read the rejection, fix the template, regenerate, upload again.
WithRun the BSP’s rules and schema checks, fix in the bank, upload once.
Submission
Also on the BSP Submission Platform · granularCOCREE 2.0 reporting, with record-level validation built in
Approve and file the FRP: portal upload today, API when you choose
For FRP v15, the platform produces the validated, schema-checked XML for your team to upload to the BSP portal. API submission is built in for when the bank and the BSP use it, as FRP v16 moves to API-based reporting. Either way, approvals, remarks and the filing history stay in one place.
Approve
Maker-checker before anything is filed
Reviewers approve or reject report by report or in bulk. A rejection needs a comment, so the preparer knows what to fix.
File
One filing, with its checks attached
The filing shows its validation and approval status, takes a required remark, and either downloads the validated XML for the BSP portal or submits it.
Track
Filing history across every package
Every submission to the BSP, for FRP, COCREE 2.0 and the other packages, with its approvals, remarks, validation results and the file that was sent.
The differentiator
A validation engine that speaks BSP
The BSP defines auto-generated cells, cross-schedule references and validation assertions in a specification language of its own. Wekalp executes that language natively, and absorbs each new specification straight from the source documents, release after release.
Computed cells generatedAuto-calculated figures are produced by the engine, never re-typed by hand.
Dependencies resolvedReferences between schedules are worked out before a single rule runs.
The full assertion setEvery rule runs exactly as the regulator defines it, with its preconditions.
FAQ
BSP FRP v15 and v16, answered
What is the BSP FRP?
The Financial Reporting Package (FRP) is the set of financial schedules that banks submit to the Bangko Sentral ng Pilipinas. It is filed as schedules of reported figures and checked against the BSP’s business validation rules and its XML schema.
What is FRP v16 and when does it start?
FRP v16 is the next version of the package. After the BSP extended the start, live submission begins with the June 30, 2027 reference period, and banks continue to file FRP v15 until then. Check current BSP issuances for the exact scope and dates.
Which BSP reports does the FRP package cover?
Nine reports, in both v15 and v16: the Financial Reporting Package, the Report of Selected Branch Accounts (BRIS), the Capital Adequacy Ratio (CAR), the Electronic Money Report, the Report on Trust and Other Fiduciary Services (FRPTI), the Report on Microfinance Products, the Minimum Liquidity Ratio (MLR), the Report on Compliance with Mandatory Credit Allocation (MSME) and the Published Balance Sheet (PBS).
Is Wekalp ready for FRP v16?
Yes. Wekalp is ready with both FRP v15 and FRP v16: templates, validation rules and schemas are built into the platform, so you can test against v16 during the transition window while FRP v15 filings continue as they are.
How is FRP v15 filed today, and where does Wekalp fit?
FRP v15 is filed by uploading the XML file to the BSP’s portal, and the BSP’s validations run after the upload, so errors come back as rejections that need a fix and a new upload. Wekalp runs the BSP’s business rules and the XSD checks before that, and produces the validated XML for the upload.
Do we have to submit through the API?
No. API submission is built in, for when the bank and the BSP use it as FRP v16 moves to API-based reporting. Until then, and whenever the bank prefers, the platform produces the validated XML for upload to the BSP portal. The choice is the bank’s.
Can we keep preparing the FRP in Excel?
Yes. Upload the bank’s own template as-is. Sheets are matched to the BSP schedules automatically and anything that doesn’t map is flagged. If you would rather have the schedules computed from source systems, Source-to-Report Automation builds them and hands them to the platform.