Your crypto, booked
in QuickBooks.
Connect your wallets and classify each transaction once. Scriply records it in QuickBooks the way your accountant would, with payments applied to the invoices and bills they settle.
Your wallets, in the books
you already keep.
Your books stay in QuickBooks. Scriply keeps the detail of every wallet transaction and records each one there once you've classified it.
Your wallets, synced
Connect your business's Solana wallets, and every transaction comes into Scriply with balances that match the chain.
- Wallets you already use, or one made in Scriply
- Each wallet its own account in your books
Classified against your chart of accounts
Your accounts, customers, vendors, invoices and bills come in from QuickBooks, so you classify each transaction against what's already there.
- Several receivable and payable accounts, as you have them
- Classify once; change it later if you need to
Recorded the way your accountant would
A customer's payment is recorded as a payment received into the wallet's account and applied to its invoice. A vendor payment is a bill payment applied to its bill. Both close out properly in QuickBooks.
- Invoices and bills show as paid, not just a lower balance
- Aging and customer statements stay right
Gains and losses
Realized gains and losses on what your business holds in crypto, worked out per wallet.
- First in, first out, for each wallet
- Cost basis tracked per wallet, as the IRS requires
Pay your QuickBooks bills
in USDC.
Your bills come in from QuickBooks. Pay them from your wallet, and each payment is held against its bill so nothing is paid twice.
Pay bills in USDC
Pay vendors from your business's Solana wallet, several bills in one transaction, with each payment recorded against its bills.
- USDC at 1:1 for US dollar bills
- Partial payments, and pay many bills at once
- Vendor addresses verified by signature or penny test before use
A wallet you control
Create a Solana wallet with your phone number, or connect Phantom, Solflare or another you already use. Scriply never sees its keys and can't move its funds.
- Protected by a backup email and a second factor
- Add funds with a card or bank transfer
- Send USDC or SOL
Your invoices,
as tokens anyone can check.
Tokenizing an invoice your customer still owes mints tokens for what's outstanding into your business's wallet. Each token stands for one dollar owed, and burns as it's paid.
One token per dollar owed
Each business has its own US dollar receivables token. Its supply always equals what's still owed on the business's tokenized invoices, so a token from one business is never mixed with another's.
Burns as invoices are paid
A payment, credit or write-off burns the same number of tokens. A tokenized invoice is locked against edits until its last token burns, and a change in QuickBooks is held back and disclosed rather than applied silently.
On Solana, with nothing private on-chain
Every mint and burn is recorded on-chain with a fingerprint of the invoice behind it. Nothing on-chain names the business, its customers or its invoices.
Minted to your wallet
Tokens go to a wallet your business proved it controls. They move only between accounts the platform allows, and Scriply, as the issuer, burns them as invoices are paid.
Opt-in, per business
An admin turns tokenizing on after the business is verified: they accept the tokenization terms and choose the wallet. Nothing goes on-chain before that.
A limit on what's out at once
Each business has a cap on how much it can have tokenized at a time. A tokenization over it is refused before anything is minted.
What we check before an invoice is tokenized.
A token is only worth the invoice behind it. Every business and every invoice goes through these steps first.
We verify the business
A business passes our review before it can tokenize: its owners with a 25% stake or more and a person who controls it are identified, and the business and its people are screened against sanctions lists.
We verify the wallet
Tokens are only minted to a wallet the business proves it controls, by signing with it.
We check every invoice
Each invoice needs a supporting document and a customer who clears sanctions screening. It's compared with every invoice already tokenized, by any business: the same invoice is refused, and one that looks alike waits for a person to review it. An invoice from QuickBooks is read again there before anything is minted.
We report on every token, publicly
Every day we publish each token's report — what's outstanding, how overdue, how concentrated, how fast it's paid, and what we verified — with its fingerprint recorded on-chain.
What a lender sees
about every token.
When tokenization launches, each token's latest report will be public, by its address, with no sign-in. It shows the totals, aging and risk, without the invoices or customers behind them.
GET /v1/public/receivables-tokens/{network}/{tokenAddress}
Example values
{
"network": "sol",
"tokenAddress": "Ah8cVgnZ8SjPzRtJoCAo26BHBjc4T7xQ6Rsk3apRXdRY",
"currency": "USD",
"reportId": "usd.2026-10-06",
"asOf": "2026-10-06T00:00:00Z",
"sha256": "a7eb512136b792d30f616ebe720f5a0c0e079ab99752a26f222faa196f5bd85f",
"attestations": { "sol": "3Vj9uCytyrTshBTim1ELkc2RH9cLA9jxUTSyemENPL8oFgfcbBFFL39gsrdLy3z1g4zQaF8tYR1YzZqv8CqiaNhZ" },
"supply": "184250",
"circulatingSupply": "184250",
"outstandingUnits": "184250",
"burnDebt": "0",
"burnDebtOverdue": false,
"reconciled": true,
"unattributedRatio": "0.012",
"aging": {
"current": "132400",
"days1To30": "38150",
"days31To60": "9800",
"days61To90": "3900",
"over90": "0"
},
"assurance": {
"kyb": "approved",
"kybApprovedAt": "2026-07-14T16:02:11Z",
"kybMethod": "manual-review",
"checks": [
"control-person-identified",
"beneficial-owners-identified",
"identities-verified",
"sanctions-screened",
"wallet-verified",
"ein-confirmed",
"business-registered"
],
"accountingSystemShare": "0.92"
},
"risk": {
"topCustomerShare": "0.22",
"topFiveShare": "0.71",
"concentrationIndex": "0.14",
"selfIssuedShare": "0.08",
"receivableTurnover": "7.9",
"daysSalesOutstanding": "46.2",
"turnoverPeriodDays": 212,
"historyDays": 212,
"settledTokenizations": 37,
"flags": ["self-issued-invoices"]
}
}
Illustrative report for a made-up business. Units are dollars of invoices still owed.
- supply · outstandingUnits · reconciled
- Tokens in existence, and dollars still owed on the invoices behind them. They match whenever the report reconciles.
- burnDebt
- Tokens owed for burning that couldn't be burned yet. While it's above zero the token is under-backed, the report says so, and the business can't tokenize anything new.
- aging
- What's owed, by days past due: current, 1–30, 31–60, 61–90 and over 90.
- risk
- How concentrated the customers are, the share of invoices made in Scriply rather than an accounting system, how fast invoices are paid, and flags from a fixed list, such as
concentration-highoraging-over-90-high. - assurance
- What we verified about the business behind the token, such as its EIN and registration, its owners and its wallet, without saying who it is.
- sha256 · attestations
- The fingerprint of the day's full report, and the Solana transaction that recorded it. A lender given the full report hashes it and compares it with the chain.
See Scriply at work.
Short walkthroughs of the product, recorded in the app.
Invoice tokenization
Turning tokenization on after verification, tokenizing an invoice and reading its memo on Solana, and the daily report on every token. 5 min.
Vendors and bills on mobile
Working with vendors and their bills from your phone.
Customers and invoices on mobile
Working with customers and their invoices from your phone.
Bring your crypto
into your books.
Connect QuickBooks and your wallets, and every transaction has a place in your books. Free for freelancers and small teams — no credit card needed.