An edited invoice, disputed contract, or forged certificate can look completely legitimate. Anchor the exact file when it becomes final and give anyone a signed fingerprint they can verify later, without ever sending the document to Invoance.
When someone asks “is this the original?”, the answer should take seconds, not a support ticket, an email search, and someone’s word.
VERIFY / vendor-bank-details.pdfNW-AP-10423b0c44f5c8e1a7d2…d91aaa82f9700d14b3c9…20e6Storage proves you have a file now. It does not give an outsider strong evidence that the file was not edited after approval, issue, or submission.
Which copy did your team actually issue before the payment was sent?
Keep Drive, S3, SharePoint, your DMS, and every workflow you already use. Invoance adds the independent proof layer beside them.
Add the anchor at the point your application already knows a document is final: after signing, approval, generation, filing, or issue.
Compute SHA-256 where the file already lives. The document can remain inside your application, storage bucket, or customer environment.
file → sha256: 3b0c…d91aSend the fingerprint when the document becomes final. Invoance timestamps it, signs it with your organization key, and stores an append-only record.
fingerprint → signed anchorShare a proof link or verify offline. Re-hashing the file answers whether the copy is byte-for-byte identical to the anchored original.
copy + proof → match / mismatchEvery supported SDK can anchor a fingerprint. Keep the event ID beside your document record and place the verification link wherever customers, auditors, or counterparties will need it.
import { createHash } from "node:crypto";
import { readFileSync } from "node:fs";
import { InvoanceClient } from "invoance";
const client = new InvoanceClient();
const bytes = readFileSync("contract.pdf");
const proof = await client.documents.anchor({
documentHash: createHash("sha256").update(bytes).digest("hex"),
documentRef: "msa-acme-v3",
});
console.log(proof.event_id);Give accounts payable a way to check invoices and bank-detail letters before money moves.
invoices · remittance letters · statementsPreserve the exact contract, policy, or disclosure that existed at approval time.
contracts · policies · board minutesLet recipients and third parties validate certificates without waiting for your team.
certificates · licenses · reportsShow that today’s file is the same file retained or submitted months ago.
filings · audit packs · control evidenceNo. Anchor only the SHA-256 fingerprint and keep the file in your existing storage. Optional managed storage is available when you explicitly want it.
A SHA-256 fingerprint is one-way. It is used to compare an existing file, not reconstruct the file’s contents.
The new bytes produce a different fingerprint. Anchor the new approved version as a new record; the earlier proof remains intact.
No. Public proof pages can be checked without signing in, and exported records can be verified offline with the issuer’s public key.
Start with one invoice, contract, certificate, or filing. Keep the file where it is and add the signed proof beside it.