Turn wallet activity and your invoice ledger into explained matches, a clear exceptions list, and a close pack your finance team can review.
For teams anywhere with recurring stablecoin payments and manual matching work that their current tools leave behind.
It starts with a free written triage: one reply within 24 hours on whether your case is in scope. No payment and no data handover at this step.
We start with Base USDC and structured CSV exports. Work is performed from agreed read-only data; you keep control of your keys and funds.
Confirm the data and the problem, close one period, then continue monthly when the workflow and value are established.
Paid in full upfront
Up to 100 payment movements.
The $199 diagnostic is credited within the $750 first close when purchased within 30 days: $176 more at booking, then $375 before final delivery.
Request the diagnostic50% at booking; 50% before the final pack. With the $199 diagnostic credit: $176 more at booking and $375 before final delivery.
One entity, one period, one network, up to two wallets, one structured invoice file, and up to 500 payment movements.
Available after the first-period close; paid monthly in advance
Founding rate for the first five monthly clients, for three months.
Up to 500 movements each month, using the same entity, network, wallets, and invoice source established in the first close.
After value and delivery cost are established, standard pricing starts at $999 per month or a custom quote. Any later price and scope are agreed before renewal.
Discuss monthly closeScope boundaries: Collecting missing documents, contacting your suppliers, and adding sources or networks are outside these prices. If the sample shows greater complexity, we agree a revised scope and price before doing that work. Extra scope is quoted separately.
Prices above are in USD. Your invoice will specify the payment currency and instructions. A service enquiry does not initiate a payment.
Tell us who owns the close, your approximate monthly volume, the data you have, and where matching breaks down. We agree the scope before work starts.
After the diagnostic is paid, we review the agreed read-only data, identify gaps, and show representative matches and exceptions.
Once the scope is accepted and the booking payment is received, we check source totals, match with explainable rules, review sensitive cases, and prepare the close pack. The balance is due before final delivery.
You review the results and unresolved exceptions. For a repeatable workflow, we agree the monthly service, sources, and limits.
Fictional data only. This example contains no customer data or real transfers and is not a customer case study. It shows 12 outgoing movements across two demo wallets and 9 invoices for one fictional period.
Movement view
1,675 = 1,450 allocated + 225 unallocated
Invoice view
1,795 = 1,450 allocated + 345 outstanding
All amounts are USDC quantities, not USD valuations. The unallocated movement amount and the outstanding invoice balance are separate views; they are not a combined loss and are not automatically offset. Network fees, exchange rates and tax are outside this example.
200 USDC is allocated against a 250 USDC invoice. The remaining 50 stays outstanding; none of the payment is unallocated.
A 200 USDC movement covers a 180 USDC invoice. The extra 20 stays unallocated until a reviewer confirms its treatment.
A 75 USDC movement resembles a 75 USDC invoice, but has no invoice reference. Both stay unresolved until evidence establishes the link.
Require an explicit invoice reference, matching vendor and matching asset. Allocate only up to the invoice balance. Combine referenced partial movements, and keep excess or ambiguous amounts for review.
In this synthetic file, six invoices are fully covered, one is partially covered and two remain unpaid. Possible duplicate payments are reviewed separately from duplicate imports.
| Case / movement | Movement amount | Allocated | Unallocated | Invoice outstanding | Explanation |
|---|---|---|---|---|---|
| Exact matchDEMO-M-001 | 120 | 120 | 0 | 0 | The explicit invoice reference, vendor and asset agree. The 120 USDC movement settles the 120 USDC invoice. |
| Split settlementDEMO-M-002, DEMO-M-003 | 180 + 120 | 300 | 0 | 0 | Two movements with the same explicit invoice reference settle a 300 USDC invoice. The first partial movement is no longer a period-end exception. |
| Partial settlementDEMO-M-004 | 200 | 200 | 0 | 50 | The 250 USDC invoice has 200 USDC allocated and 50 USDC outstanding. No part of this movement is unallocated. |
| OverpaymentDEMO-M-005 | 200 | 180 | 20 | 0 | Allocate only the 180 USDC invoice balance. Keep the extra 20 USDC unallocated pending explanation; no refund or credit is assumed. |
| Possible duplicateDEMO-M-006, DEMO-M-007 | 90 + 90 | 90 | 90 | 0 | The first 90 USDC settles the invoice. A later, distinct event repeats the reference, vendor and amount. Hold the second 90 USDC for review. This is a possible duplicate payment, not a proven error or a duplicate import. |
| Missing referenceDEMO-M-011 | 75 | 0 | 75 | 75 | The movement lacks an invoice reference. Even though vendor and amount resemble invoice 009, no allocation is made. Its 75 USDC remains unallocated and the invoice separately remains outstanding. This row shows a review candidate, not a verified link. |
| Unknown recipientDEMO-M-012 | 40 | 0 | 40 | — | The recipient is absent from the invoice vendor set and no invoice reference is supplied. Keep all 40 USDC unallocated; no corresponding invoice is inferred. |
| Unpaid invoiceNo allocated movement | — | 0 | 0 | 220 | No source movement is allocated to this 220 USDC invoice. It remains outstanding in this sample; a reviewer would check source completeness. |
These selected rows explain the rules and are not an additional ledger to sum. Movements 008 and 009 also settle invoice 006 (250 + 150 = 400 USDC), and movement 010 settles invoice 007 (160 USDC).
Unallocated: 225 USDC = 20 excess + 90 possible duplicate + 75 missing reference + 40 unknown recipient.
Outstanding: 345 USDC = 50 on invoice 003 + 220 on invoice 008 + 75 on invoice 009.
This is an illustrative reconciliation, not an audit opinion or accounting certification. Delivery time and cost were not measured; no savings, customer result or revenue is claimed.
A good fit is a team with roughly 100–1,000 monthly stablecoin movements, one or more wallets, a usable invoice or obligations ledger, and a founder or finance owner responsible for the close. If matching and follow-up take ten or more hours each month, tell us how that work happens today.
The standard first-close and monthly packages cover up to 500 movements. Larger volumes need a separate scope and quote.
This service prepares a reviewable reconciliation and close pack. We do not take private keys, sign transactions, or move customer funds. We do not issue a statutory audit opinion or an accounting certification.
If a payment sits outside your platform, or its invoice is missing, we can examine the agreed read-only records and document what can be verified and what remains unresolved. You keep your existing platform. A missing invoice stays a documented exception; we do not invent a match or include collecting missing documents in the standard scope.
KushBitx is an independent, data-minimal layer between stablecoin settlement and your books. From agreed read-only records, we establish the facts, define the boundaries of the problem, and resolve what can be resolved operationally with evidence.
We do not give accounting or tax judgements, and we do not audit. Where a case needs that judgement, we say so and leave it to you and your adviser.
Each match should be supported by evidence. Missing or ambiguous information belongs on an exceptions list for review.
Describe the problem in the triage form, without names, ledgers or keys. One written reply within 24 hours tells you whether the case is in scope. Scope comes before price, and we do not request operational data until the scope is agreed.
Start with free triageUse the triage form below, or email a short description without names, ledgers or keys.Answer a few questions about the problem. You receive one written reply within 24 hours that says whether the case is in scope and what the next step would be. Scope comes before price; there is no matching or upsell at this step.
Do not send names, ledgers or keys.No personal or company names, invoice files, accounting ledgers, wallet addresses, private keys or recovery phrases. Your email is used only to send the reply.
Prefer email? admin@kushbitx.com
Token Risk, Transaction Preflight, Payment Proof and SpendGuard remain available as separate tools with their own scope and price. Tools & APIs
