For Counterparties
You received a PacSpace verification link or a proof root on an invoice. Here is what it is and what you can check.
Someone you do business with sent you a verification link, put a proof root on an invoice, or shared a PacSpace record with you. This page is for you. You do not need a PacSpace account, and nothing on this page requires writing code.
What You Are Looking At
Your vendor records usage with PacSpace before invoicing it. Each recorded change is committed: once written, it reads the same for both sides and neither side can revise it. The link you received opens that record.
PacSpace records; it does not judge. The record shows what was committed and when. It does not decide whether a number is commercially right; it gives you the evidence to check that yourself.
Verification requires evidence the verifier did not produce, cannot modify, and does not need permission to access. That is what the link gives you.
What You Can Check, With Nothing But the Link
Open the link. The summary view shows the record exists, its period, and its verification status.
If your vendor gave you an access code, enter it to see the detail: individual recorded deltas, the running balance, period history, exports, and the compare tool. The code is how the vendor scopes detail to you; if you did not receive one, ask your vendor for it.
There is no signup. The link is scoped to the relationship between you and this vendor. What was consumed and how much stays between the two of you, and showing it to anyone else is a choice the record holder makes.
Checking a Proof Root From an Invoice
An invoice may carry a proof root, a single fingerprint covering every recorded delta in the billing period. Anyone can check a proof root without authentication:
GET https://app.pacspace.io/api/v1/verify/:proofRootThe response confirms the proof exists, when it was recorded, and the summary it covers. See Verifying Proofs for the full walkthrough.
When Your Number Differs
Run your own count for the period, then use the compare view in the shared record (or ask your vendor to run Compare with your figure). The result identifies the specific days where the two views diverge, so the conversation starts from a concrete recorded delta rather than a disputed total.
If a genuine error is found, the correction will appear in the record as a new entry alongside the original, with its reason stated. Nothing is ever silently rewritten, which is what makes the record worth checking in the first place.
What to Ask Your Vendor For
Three things cover every situation: the shared record link, the access code, and the period's proof root. With those, your finance team can watch usage mid-period, verify the invoice at close, and resolve any question from the same record the invoice was built from.
Related
- Verifying Proofs - checking a proof root step by step
- How Verification Works - what the proof establishes
- Shared Record Language - what the words on the record mean