matchitfy
Log in

How it works

Connect once. Reconcile every payout. Close the month once, for every store.

Keep selling where you sell and keep your books where they are. We answer what neither can: did the money arrive, and what happened to the difference.

In development. This page describes what is being built, in the order it is being built. Nothing here is available to buy yet.

Three steps, and then it runs on its own

Step 01

Connect your stores and your books

Sign up, then connect from Settings. Adding a second store later costs nothing you already did.

Cloud: QuickBooks Online, Xero, Sage, FreshBooks, Odoo. Desktop: QuickBooks Desktop and Sage 50, through a small local agent, a silent background service, not something that needs Windows Admin Mode.

Your fee and SKU mappings live outside the live desktop session. If the connection drops or credentials refresh, the agent inherits them. You do not re-map hundreds of lines by hand.

Agent-On-Sync™

Most of the category is cloud-only and tells desktop merchants to migrate. The one serious desktop rival needs Admin Mode and can wipe mappings on reconnect. We do neither.

Step 02

Every payout is rebuilt down to the deposit

A payout is a bundle: orders, fees, refunds, chargebacks and tax. We pull every line and rebuild the path to the figure the bank received.

Connect a bank and we check the deposit. This one arrived. This one is three days late. This one never came.

When a line does not tie, the screen highlights it (tax, refund, shipping, fee) and you reconcile with one click. Exporting to Excel to find the variance is a product failure, not a support tip.

Gateway activity consolidates into one clearing structure per currency. We do not spawn a forest of bridge accounts for Shopify Payments, PayPal, Stripe and Square, and and every entry carries a stable document number, so a retry never creates a duplicate.

Match-On-Bank™ · clean clearing

Bank check is optional. We never hold a bank credential. Clearing stays readable on purpose.

Step 03

Close the month once, across every store

This is where the rest stops. Everyone else charges per store; nobody adds the stores back up. Here one plan covers them all.

One cost per SKU across both. One tax figure. One month that closes.

Several stores, one close

With one store it means nothing. With two it is the whole point.

Step 04

And then it acts, without you watching

The finding leaves as a signed webhook. From n8n, Zapier or your own service you take it where your team works, and read or export whatever the event carries.

An AI explains what did not tie and proposes the entry. It never computes a figure. Code does that.

How the automation and the AI work →

What Matchitfy finds

Money that already moved, and that nothing in your store or your books is looking for.

A payout that never landed

The gateway says it sent it, the books say it arrived, the bank disagrees.

A variance that used to mean Excel

The month is short by $84.12. Elsewhere that becomes a CSV and a pivot table. Here the broken line is already on screen.

Fee drift

2.7% creeping to 3.1% across a quarter. Four tenths is real money and no dashboard shows it.

A refund posted twice, or never

Refunds land on a different day and in a different payout. That is where duplicates live.

Sales tax being spent

Collected tax sits in the operating account looking exactly like revenue.

A bundle sold below cost

A combo whose components rose while its price did not. The margin goes negative quietly.

Margin measured at today's cost

A March sale costed at August prices is a guess, not a margin.

Cost on the day it sold

Every sale costed at the price on the day it sold, from the day you connect a store. Further back we use whatever your accounting system already holds.

Who it fits

Merchants selling in two places

Shopify plus Square, or a storefront plus a marketplace. Paying twice and still reconciling by hand.

Anyone on desktop accounting

QuickBooks Desktop and Sage 50, without Admin Mode, and without redoing mappings every time the connection blinks.

Anyone selling bundles or kits

Where cost of goods is a moving assembly and the spreadsheet stopped being enough.

The accountant who inherits it

Every entry traces back to the payout line that made it.

What we do not do, and why

A boundary we chose, not a gap we are filling. Everything below is work we could sell you and decided not to build.

We do not hold your stock

Holding stock means purchase orders, suppliers, receipts, transfers and write-offs. That is an ERP, and you already pay for one. We read what a unit costs, cost the sale on the day it happened, and hand the numbers to the system that owns the stock.

We do translate your bundles

Your store sells a kit as one SKU. Your ERP cannot decrement stock for something its catalogue has never heard of. We explode the kit into its components first, so what arrives is something your ERP can act on.

One system owns the cost

If your ERP costs the sale, we do not post a second cost entry on top of it. Two systems costing the same sale do not give you a second opinion, they give you two gross margins and no way to tell which one to believe.

We do not replace your ledger

The all-in-one tools ask you to move your books into them. Your books stay where they are, in the software your accountant already knows, and stay yours the day you stop paying us.

See it against your own last three payouts.

Leave an email and we write once, when it is ready for you.