Junior · high volume
Classifies everything
Every payout line, fee and adjustment mapped to an account. Thousands a month at a cost that rounds to nothing.
When it is not confident it says so instead of guessing. That is what triggers the next tier.
Automation
Reconciliation that only makes a report leaves the work with you, reading the report. We connect what we find to what happens next.
In development. The flow engine and the n8n connector already exist in the platform this is built on. Everything on this page describes how they are being wired into reconciliation, not a shipped feature.
The first question an accountant asks.
Deterministic code
Matching, arithmetic, dates, currency, tax, fees, cost of goods. Same input, same output, every run. Re-run last March and you get last March.
The AI
Reading a fee nobody has seen before. Explaining, in a sentence you can check, why a payout is $84.12 short. Proposing the entry. Saying what it is unsure about.
The AI never computes a figure
Not the match, not the total, not the tax, not the margin. It reads and proposes; it does not calculate. A model that can change a number makes your books unauditable.
Two models, sized to the question. Everything through an expensive one is how AI becomes an add-on; a hard case through a cheap one is how it becomes wrong.
Junior · high volume
Every payout line, fee and adjustment mapped to an account. Thousands a month at a cost that rounds to nothing.
When it is not confident it says so instead of guessing. That is what triggers the next tier.
Senior · low volume
Only what the deterministic pass could not close. Out of four thousand lines, usually a handful.
Not a score. A sentence: this payout is short because a refund from last period settled inside it, here is the entry, and here is what I am unsure about.
A Slack message and a journal entry are not the same kind of thing. A product that treats them alike is one no accountant turns on.
| Level | What it can do | Example | Approval |
|---|---|---|---|
| Informational | Sends a message. Changes nothing, anywhere. | Post the unexplained total to a Slack channel | None needed |
| Operational | Writes inside Matchitfy only. Reversible, and logged. | Tag a payout for review, open a task, hold a batch | Once, per flow |
| Fiscal | Writes to your accounting system. | Post a journal entry, reclassify an account, close a period | Per action, and never a blanket switch |
Finding the gap is our job. Where it lands is yours, and it should land where your team already works.
The channel accounting already lives in, with the figure and a link back to the payout.
Certain rather than planned: the platform underneath already ships an n8n connector, and self-hosted means your data never leaves your infrastructure.
A trigger, for the thousands of apps we are never going to integrate one by one.
A task, assigned, with the amount and the deadline. A discrepancy nobody owns survives the quarter.
Signed with HMAC. The escape hatch, so you are never blocked waiting for us.
The person who most needs to know a payout never arrived is often the one not in Slack.
Honest about the order. The signed webhook and n8n are certain — the engine exists. Slack, task boards and Zapier are planned, and the order depends on what early users ask for.
Built by dragging, not by writing code.
Flow 01
A payout is off by more than $50 → explain why → post to #finance → open a task for whoever closes the month.
Flow 02
A gateway rate moves more than 0.3 points in 30 days → email the owner. Four tenths on $50,000 is $200 nobody was looking for.
Flow 03
A bundle's margin turns negative → hold the entry and ask for approval. This one is fiscal, so it waits for a person.
The order these ship in is genuinely undecided. Say what your team uses and it moves up.