Receipts from people who will never install your app
Technicians, cleaners, subcontractors, vendors: send them a link, get back a coded receipt. No account, no password, no app. OCR and auto-coding take over exactly as if the receipt came from a full user.
A link, and nothing else to ask of anyone
One link, zero onboarding
A lightweight page where they snap or upload the receipt. Done before the app store would have finished loading.
Share a transaction, not your account
Send a link to one transaction or to someone’s pending list. They see only what you shared, nothing else.
Coded like everything else
OCR and auto-coding treat a share-link receipt exactly like one from a full user: matched, coded, in your books.
The whole flow is a link
Some of the people who buy things for your jobs will never create an account in your finance tool. The cleaner with receipts from three properties. The subcontractor who bought materials on your behalf. The vendor with a delivery ticket. For them, Clyr makes the entire experience one link: it opens a lightweight page, they snap or upload the receipt, and they are done.
On your side, nothing changes. OCR reads it, auto-coding assigns the job, property, and account, and the receipt lands in your books exactly as if a full user had submitted it.
Show one transaction without granting access
Need a cardholder or a sub to explain a charge? Send a link to that one transaction, or to their list of pending ones. They see only what you shared: not your dashboard, not other people’s spend, not your account.
Getting an answer about one receipt no longer requires creating a user, assigning a role, and revoking it a week later.
What a link can and cannot do
Each link is tokenized and scoped: it exposes only the specific submission page or transaction view you shared, not your account. And submission links are exactly that, submission links. They accept receipts; they do not show books.
Which means the failure mode of a forwarded link is an extra receipt in your review queue, not a stranger looking at your finances. Anyone with the link can submit, and nothing more.
A link can
A link cannot
Three ways in, one system
Share links
For: subs, vendors, cleaners, anyone outside Clyr
One link, no account, snap and done.
SMS capture
For: your cardholders
Clyr texts at the swipe; they reply with a photo.
See receipt capture →Reimbursements module
For: out-of-pocket spend and mileage
Text a receipt or the word “miles”.
See reimbursements and mileage →Whichever door the receipt walks through, the same OCR, the same coding rules, and the same books.
Why no-login beats another portal
Portals assume the other side wants a relationship with your software. They do not. Every account you force on a subcontractor is a password reset you will eventually be asked to do. A link asks for nothing, works immediately, and gets you the only thing you actually wanted: the receipt.
Frequently asked questions
Do people need a Clyr account to submit?
No. The link opens a lightweight submission page; there is nothing to install and no account to create.
What does the link expose?
Only the specific submission page or transaction view you shared. Each link is tokenized and scoped; it does not open your account.
What happens if a link gets forwarded?
Anyone with the link can submit to that page, and that is all they can do. Submission links accept receipts; they do not show your books.
Can subcontractors and vendors use this?
Yes. That is who it is for: people who buy things for your jobs but will never be users in your finance tool.
Can people log mileage through a link?
Yes, through the no-login mileage page. The full mileage story lives on Reimbursements and Mileage.
Do share-link receipts get coded like everything else?
Yes. OCR and auto-coding treat them exactly like receipts from full users: matched to transactions, coded to jobs and properties, receipt attached in your books.
See it on your own spend
Book a 20-minute demo. We will send you a live share link during the call; submit a receipt from your phone and watch it land coded.
