matchitfy
Money-First Finance™ · In development, early access
Reconcile your stores against your books, then verify the money actually landed in the bank.
$1,247
unexplained across 3 payouts
Interface being built. Figures are illustrative.
Your stores
Your payment gateways
Your books
Half-tone means not connected yet: WooCommerce, then Amazon, then NetSuite.
Fees, refunds and tax sit between what you sold and what the bank paid you. We rebuild that path for every payout.
With your permission we read your bank and confirm each payout arrived. Not an entry saying it did. A statement you can check.
Match-On-Bank™
Matchitfy™ runs on Money-First Finance™: the money moves first, the record follows. Connecting the bank is optional and you control it.
Two thirds of merchants sell on more than one channel — that is Webgility's own research, not ours.
Some of them will put several stores on one bill. None of them adds the stores back up: it stays one account, one report and one close per store. Selling on Shopify and Square still means two of everything and a spreadsheet.
Here the second store is neither a second subscription nor a second report. One plan for the business, one margin, one tax figure, one month that closes.
Several stores, one close
Never a tier, never an add-on.
QuickBooks Desktop and Sage 50 connect through a silent agent on the machine that already runs them. No Windows Admin Mode, and no remapping fees and SKUs when the connection drops.
Agent-On-Sync™
Cloud too: QuickBooks Online, Xero, Sage, FreshBooks, Odoo. Mappings persist outside the live session.
Elsewhere a month-end variance means CSV exports and pivot tables. Here the screen highlights the exact tax, refund, shipping or fee line, and from there you build the entry that closes it.
And the chart of accounts stays clean: one clearing structure per currency, not a bridge account for every gateway. And retrying a post never duplicates the entry: the document number is the same.
Close without leaving the product
Exporting to Excel to find a variance is a product failure.
It watches while you are not looking.
Every hour it measures your payouts, your fees and your books. When something does not add up it does not file a report: it tells you what happened, what it costs you, and what it would do. You decide.
A fee spike, a payout that does not tie, a margin going negative. Send it to Slack, n8n, Zapier or your own webhook, where your team already works.
An AI explains why a payout is $84.12 short and proposes the entry. Code does every number.
Needs an answer
The AI never computes a figure
Actions that write to your books need approval, one by one. In every plan. How the automation and the AI work →
One plan per business, unlimited stores. Annual is ten months, so two are free.
| Plan | Orders / month, all stores combined | Per monthPer year |
|---|---|---|
| Starter | 200 | $29$290 |
| Lite | 500 | $39$390 |
| Business | 2,000 | $69$690 |
| Professional | 5,000 | $109$1,090 |
| Enterprise | 10,000 | $149$1,490 |
| Growth | 20,000 | $219$2,190 |
| Scale | 30,000 | $349$3,490 |
| Max | 50,000 | $499$4,990 |
We are building with a small group of merchants and accountants. Leave an email and we write once, when it is ready.
From the same team
Sell wholesale, on terms or by contract and that money never reaches this screen. It is not a payout. RemindLedger covers it, and reads it from the bank the same way we do.