Verifiable exchange-rate evidence for business records

Keep source attribution, selected date, document id, payload hash, and public verification together.

Evidence workflow

Keep the rate source and evidence with every important calculation

When an accounting entry, reconciliation, or close file depends on an exchange rate, keep the evidence beside the calculation. FXProof packages the official source, selected date, rate context, and verification details in a signed proof that an accountant or later reviewer can check.

From the first question to reviewer follow-up

Why a rate value alone leaves a gap

A value in a spreadsheet does not show which publication supplied it, which date was selected, or how another person can check the evidence after the close is complete.

A manual support file can combine the source link, a saved page or PDF, and a note explaining the date and rate. FXProof packages those facts in one signed proof and adds a document id, payload hash, and public verification path for repeated review work.

What to keep with the accounting record

Keep the calculation and policy basis in the accounting file. Attach the Signed FXProof Proof PDF to the entry, schedule, reconciliation, or close support that used the rate.

  • Supported source selected for the rate.
  • Date or reference period tied to the accounting file.
  • Signed proof PDF attached to the supporting record.
  • Document id and payload hash available inside the PDF.
  • Accounting policy and review notes kept in the accounting record.

How a proof helps answer later questions

The proof keeps the source, selected date, rate context, digital signature, document id, payload hash, and verification information together. A reviewer can follow the evidence without asking the preparer to recreate it.

How to distinguish a reference rate from a bank rate

Use the bank or payment-provider record when the accounting question is what was charged in a transaction. Use an official reference rate when the accounting policy or calculation calls for the published value of a supported institution.

What an auditor can verify

An auditor can inspect the source and rate context, validate the embedded digital signature, and use the document id and payload hash shown in the PDF on the public check page. This verifies the FXProof proof; it does not certify the accounting treatment or financial report.

How repeated proof work stays consistent

Use the same evidence pattern for recurring entries: record the business context, choose the required source and date, attach the signed proof, and leave the professional conclusion in the accounting file.

Year-end close

Use separate proof records for historical dates, closing observations, and reviewer-selected comparisons.

Open year-end use case

Reconcile a mismatch

Separate invoice, payment, bank, VAT, source, date, direction, and precision questions before attaching proof.

Open reconciliation use case

Software source gap

Compare a ledger rate with a chosen official source without claiming to inspect the accounting software internals.

Read software source guide

Bulk or repeated work

Use API automation only when the same proof workflow needs to repeat across many records or systems.

Open API landing

Questions

How do I attach an exchange-rate proof PDF to an accounting entry?

Attach the Signed FXProof Proof PDF to the entry or supporting schedule that used the rate. Its FXProof proof and verification fields are already inside the document.

How do I attach exchange-rate proof to a financial report?

Keep the PDF with the schedule, reconciliation, or close file supporting the reported amount. FXProof documents the rate evidence but does not certify the financial report.

Does this replace accounting policy?

No. FXProof documents the source/date/rate evidence. Your team still decides policy, source selection, and file context.

Keep the proof with the file that used the rate

Inspect a static sample first, then use an account when you need a proof bundle for a concrete dataset and date.