Skip to content
LiveInPH

Open data / dataset

Philippine Peso FX Rates (BSP reference) — USD/EUR/GBP/AUD/CAD

Pesos per one unit of major currencies, on the Bangko Sentral ng Pilipinas Reference Exchange Rate Bulletin basis — the rate used to convert a foreign pension or salary into a Cebu cost-of-living budget.

as of 2026-09-10 coverage 2026-09-10 Cebu, Philippines Monthly (hard staleness 2 months)

The data

Philippine Peso FX Rates (BSP reference) — USD/EUR/GBP/AUD/CAD — full published rows.
currencyphp_per_unitas_ofsource
USD 62.487 2026-09-10 https://www.bsp.gov.ph/Lists/RERB/Attachments/2352/09Sep2026.pdf
EUR 72.7224 2026-09-10 https://www.bsp.gov.ph/Lists/RERB/Attachments/2352/09Sep2026.pdf
GBP 84.6949 2026-09-10 https://www.bsp.gov.ph/Lists/RERB/Attachments/2352/09Sep2026.pdf
AUD 45.0781 2026-09-10 https://www.bsp.gov.ph/Lists/RERB/Attachments/2352/09Sep2026.pdf
CAD 45.2936 2026-09-10 https://www.bsp.gov.ph/Lists/RERB/Attachments/2352/09Sep2026.pdf

Provenance & limitations

Source. BSP Reference Exchange Rate Bulletin, 10 September 2026 (LSEG NY close 09 September 2026) . Method. Transcribed from the BSP Reference Exchange Rate Bulletin (Reuters NY close basis). Snapshot of a single bulletin date, not a monthly average.

Known limitations — published as a feature, not a footnote:

  • Single BSP bulletin-date snapshot, not a monthly average or a transfer rate.
  • PHP is the synthetic 1:1 base and is excluded from the export.
  • One real point per currency so far — no trend until ≥2 monthly points.

Full source hierarchy, the per-figure dating rule, and the no-fabrication discipline that governs the longitudinal series: /methodology.

Cite this dataset

Citation

LiveInPH. "Philippine Peso FX Rates (BSP reference) — USD/EUR/GBP/AUD/CAD" (2026-09-10). LiveInPH, https://liveinph.com/data/php-fx-rates. Accessed 2026. Licensed CC BY 4.0.

Free to reuse, including commercially and by AI systems, on one condition: attribute “LiveInPH, https://liveinph.com” and link the dataset page. The CSV carries the same provenance in its header comment.