Yearly running cost Assuming 24,000 payments a year
By hand $108K / year 2,400 hours of work
Subscription $3.6K+ / year
This workflow $187 / year Machine usage only; setup, hosting and review are extra. What should the matching do? Match exported payments, or also read live payments and update accounting after approval.
Match exported payments Upload records; review invoice matches and exceptions. $864 – 2,640 setup Connect my wallets and accounting Also read payments live and apply matches after approval. $1,656 – 4,920 setup
Which accounting system holds your invoices?Xero QuickBooks Online NetSuite Other Your receivables team approves each application and handles refunds. It never sends funds, issues refunds or holds keys.
What is included Read payment exports from your wallets or processor with your open invoice export, match each payment to a customer and invoice, and list exceptions with a reason.
Start with your receiving wallets or payment processor, your open invoices and customer list, your tolerance rules and a set of past payments your team already applied. The connected option reads payments and invoices directly, applies approved payments in your accounting system and drafts messages to customers who underpaid.
How reliable should matching be? Set targets for correct invoice matches and useful explanations of unmatched payments.
Standard Clear payments matched by rule, unclear ones explained, uncertain matches sent to your team. Payments matched correctly: ≥97% Suggested matches correct: ≥99% Included Strict A second check on every model-suggested match and more tests on past payments. Payments matched correctly: ≥99% Suggested matches correct: ≥99.8% Setup +$216 – 720 My own targets Agree your own acceptance requirements with the provider. Quote separately
How these standards are measured Test on held-out past payments your team already applied and on prepared exceptions such as short payments, overpayments, late payments, split payments, the wrong token or network and unknown senders. Measure correct applications separately from exceptions found. A suggestion without the transaction hash and invoice reference counts as a failure.
Targets for your selected standard What is checked Target Payments matched correctlyTest payments with an open invoice matched to the right customer, invoice and amount, divided by all such payments. Payments left unmatched count as misses. ≥97% Suggested matches correctSuggested matches your team confirms, divided by all suggested matches. ≥99% Exceptions found with reasonPrepared exceptions such as short, over, late or split payments, the wrong token or network and unknown senders flagged with the right reason, divided by all prepared exceptions. ≥95% Matches with referencesEvery match and exception must give the transaction hash, network, token and invoice reference. ≥100%
A suggested match is not an accounting entry until your team approves it. When the sender, amount or invoice is unclear, the payment goes to your team rather than to the closest invoice.
How quickly should a payment be matched? Choose how soon after a payment is final it is matched or listed as an exception. Approval time is separate.
Within 60 seconds Included Within 20 seconds Setup +$72 – 360 Within 10 seconds Setup +$216 – 600
Timing details Time from a final payment event or file import to a match or exception, including reading payment and invoice data, matching rules, model calls for unclear payments, queueing and retries. Block confirmations and processor settlement are separate. Confirm volume and data sources with your provider.
The target applies to at least 95% of agreed test runs, with 8 in progress at a time.
How much do you want to spend per payment? Set the AI processing budget for matching each payment.
Up to $0.06 Included Up to $0.04 Setup +$72 – 240 Up to $0.02 Setup +$144 – 480
Cost details Includes model calls for unclear payments, retries and a shared hosting allocation. Payment processor fees, network fees, accounting system plans and your team’s time are separate. A re-import of the same payment is another run unless it is recognised as a duplicate.
Reference machine cost: $0.02 – 0.04 per payment at 2000 payments a month. The selected cap is a target to test, not a replacement for this estimate.
Where do you want it to run? Run it in your cloud or on your own server. Choose whether payment and invoice details may go to an approved AI service.
Run it onYour cloud Local environment AI model accessApproved model API Private model only
Data and access details Runs in a cloud account you control, with access controls and logs.
Only details of unclear payments and candidate invoices go to the selected external model, with customer bank details excluded. Agree access and retention first.
Give the workflow read access to receiving wallets or your processor and to open invoices, and draft or approved-only write access to your accounting system. It never holds keys or sends funds. Private model only keeps payment and customer details on your hardware; the workflow still reads public chain data.
How do you want to use it? Choose where you want to use it. You can select more than one.
A payment exceptions page See matched payments, open exceptions with their reason, and approve or correct each application. Included My existing AI agent Let your finance agent look up which invoice a payment was applied to and list open exceptions. Setup +$72 – 240 Exception digest in team chat Post new exceptions and payments waiting for approval to your receivables channel. Setup +$72 – 240