Skip to main content
Matching payments to invoices is the least glamorous job in AR and the one where errors compound quietly. Ari does it continuously: every payment that lands in Stripe gets matched against your invoices by customer, amount, date, and reference, and only the genuinely ambiguous ones come to you.

What Ari does here

Reconciliation

Automatic multi-factor matching, manual matching for edge cases, unmatched-payment review, and dispute investigation.

Accounting sync

Reconciled transactions line up with QuickBooks so your books and your billing system tell the same story.

Try it

How the automatic matching works

1

Payments arrive

Customers pay through Stripe; Ari picks up new activity as it syncs.
2

Ari matches

Each payment is matched against open invoices using customer, amount, date proximity, and any invoice reference in the payment memo. Partial payments are allocated; overpayments are flagged.
3

You review only the exceptions

High-confidence matches complete on their own. Ambiguous ones are flagged, and you resolve them in Slack with a one-line instruction.

When a customer says “we already paid”

1

Search for the claimed payment

@Ari search for a payment from Acme Corp around February 10 for about $5,000
2

Get the verdict

Ari checks Stripe transaction history and reports what he finds: the payment, a near-match worth reviewing, or nothing.
3

Resolve it

Found it? Match it on the spot. Nothing there? You now have the facts for the customer conversation, with the search logged in the thread.

Month-end close

Make the close routine with a recurring Reminder, then work the exceptions list: Reports export to CSV or PDF for your accounting team and auditors, and every reconciliation action keeps an audit trail. @Ari who matched this payment and when? answers itself. See Activity history.

Powered by

Stripe (payments and invoices) · QuickBooks (accounting records) · Email (payment confirmations and customer identity)