FX reference workflow
Start with the decision behind the number. Each guide gives a short answer, conditional recommendation, limitations, source path, and reusable evidence workflow.
Real work scenarios
Choose the situation that matches the failure you need to fix. Each page shows the desired outcome, the FXpeek workflow, and a reproducible example.
Finance and invoicing · Bookkeepers, finance operators, and freelancers
Problem: A current-rate screenshot or a number pasted into Excel loses the invoice date, pair direction, source date, and retrieval context. Reviewers then have to reconstruct the decision later.
Outcome: One invoice row contains the chosen business date, actual data date, currency pair, reference rate, source URL, and reusable CSV or API URL.
Dated lookup · Operations, finance, researchers, and individuals
Problem: A live converter silently answers a different question. Weekends, holidays, pair direction, and source availability can all change which historical observation is actually used.
Outcome: The result distinguishes requested date from actual available data date and keeps a canonical source URL with the rate.
Stablecoin records · Freelancers, treasury operators, and finance teams
Problem: A screenshot or exchange quote mixes asset, venue, time, spread, and execution context. Later, nobody can tell which reference rate supported the recorded fiat value.
Outcome: The record preserves asset, receipt timestamp, fiat pair, reference rate, source URL, retrieval time, and the reference-only boundary.
Finance close · Controllers, accountants, and finance analysts
Problem: Calendar month-end, last business day, payment date, and monthly average are not interchangeable. Silent method changes create inconsistent revaluation and reconciliation results.
Outcome: The close file declares one method and retains the period, actual data date, pair, source URL, and exported rows used in every calculation.
Developer integration · Developers, analysts, and internal-tool builders
Problem: A quick endpoint can still become an undocumented production dependency. Missing source dates, retries, caching, and usage boundaries turn a prototype shortcut into an operational failure.
Outcome: The prototype has a reproducible JSON or CSV request, validates dates and fields, caches stable history, and documents when to move to managed access.
Cross-border commerce · Shopify merchants, marketplace sellers, and ecommerce operators
Problem: Order, invoice, capture, payout, bank-receipt, and reporting dates answer different questions. A generic rate cannot reproduce the credited amount or explain platform fees and spread.
Outcome: Each payout row retains platform_record_id, all material dates, gross, fee, net, credited amount, platform rate, same-date USD/IDR reference rate, source URL, retrieval time, and difference. Two rates are tracked separately: the transaction-date rate for revenue and fees, and the payout-date rate for cash settlement.
Period reporting · Finance analysts, researchers, and reporting teams
Problem: Without a defined date range, included observations, missing-date rule, and pair direction, two people can calculate different averages and both call them correct.
Outcome: The report states the month, pair, observation set, averaging method, source URL, and link to daily rows behind the result.
Excel and Sheets · Analysts, bookkeepers, students, and operations teams
Problem: Manual copy-paste removes the request URL, source date, pair direction, and refresh method. A changed cell can no longer be distinguished from a changed source.
Outcome: The workbook imports from a stable CSV URL and keeps a source tab with parameters, retrieval time, field definitions, and limitations.
Regional and long-tail data · Indonesia and Singapore analysts, developers, and cross-border operators
Problem: USD/IDR, IDR/USD, SGD/IDR, and IDR/SGD are not interchangeable. Mixing dates or hiding an inverse or cross-rate produces a plausible number that cannot be audited.
Outcome: Each row exposes business_date, actual_data_date, base, quote, rate, source_url, retrieved_at, frequency, fill, transform, limitation, and a repeatable CSV or API URL.
Expenses and reimbursements · Employees, travelers, bookkeepers, and expense reviewers
Problem: Using a live rate changes the historical amount and leaves no evidence for a weekend, holiday, pair direction, or chosen date convention.
Outcome: The expense record preserves receipt date, requested and actual data dates, original amount, pair, reference conversion, and source URL.
Audit evidence · Reviewers, controllers, accountants, and data teams
Problem: A rate without date basis, direction, source, retrieval time, and method cannot distinguish a valid input from a typo, stale paste, or silent formula change.
Outcome: Each material FX row carries the minimum evidence contract and links human-readable context with reproducible CSV or API output.
No-key API evaluation · Developers, students, spreadsheet builders, and evaluators
Problem: Removing authentication speeds evaluation, but it does not guarantee unlimited traffic, service continuity, complete pair coverage, or production support.
Outcome: The evaluator can run a real request immediately and records response fields, errors, cache behavior, coverage, and the trigger for managed access.
Research guides
Use these focused guides for the pair, timing, and travel context behind an exchange-rate decision.
Which date, source, direction, and transformation produced the rate?
Can another reviewer reproduce the number from a URL, row, or API response?
Is this reference data, an executed provider amount, or a rule imposed by an authority?
Open the decision that usually blocks your next step.
Preserve a dated rate, source, method, and review boundary for invoices, close, tax, or audit support.
Open workflowSeparate the public reference rate from the bank, platform, or payment-provider amount actually received.
Open workflowChoose JSON, CSV, or spreadsheet access and understand the public API boundary before integration.
Open workflowRecord the asset, timestamp, fiat reference, source URL, and limitations together.
Open workflowKeep the asset, timestamp, fiat reference, source URL, and limitations together.
FXpeek can help preserve dated reference-rate evidence, but it does not decide which rate a tax authority, auditor, or accounting policy requires. Confirm the required convention first, then save the date, pair, rate, source URL, and exported row together.
Save the dated source URL, exported row, selected convention, and retrieval context.
Start with the date required by the document or policy: invoice date for invoice recognition, payment date for cash settlement, or reporting date for period-end measurement. If the selected date has no published reference point, record the latest available business-day date rather than silently relabeling it.
Review the source chain, update timing, latest available date, and reference-only method.
FXpeek publishes regional pair pages only when the underlying reference data is available and verifiable. Users should check the source date, pair direction, missing dates, inversion method, and intended reference-only use before relying on a series.
Choose by job, not by a universal winner. FXpeek is designed for lightweight dated-reference, source-URL, CSV, spreadsheet, and selected regional/stablecoin workflows. XE and OANDA offer broader commercial currency-data products; review their official coverage, licensing, frequency, and service terms when those requirements matter.
A reference rate is a reproducible information point. A bank or payment-provider rate may include timing differences, spread, fees, liquidity, card-network rules, and customer-specific pricing. Use FXpeek for reference and evidence, and use the provider statement for the executed amount.
Coverage varies by currency pair and upstream source. Check the pair page or API response for the actual available dates; do not assume every pair starts in the same year or updates on the same schedule.
FXpeek keeps lightweight public examples available for lookup, prototypes, spreadsheets, and evaluation. No fixed public daily allowance is promised on this page; abusive or high-volume traffic may be limited, and production users should monitor responses and request a managed workflow when continuity matters.
Choose JSON, CSV, Google Sheets, or a public page according to the next workflow step.
A usable team policy states which business event selects the date, which reference source is used, how non-publishing days are handled, what evidence is saved, who approves exceptions, and when the policy is reviewed.