Turn uploaded receipt files into accounting expenses
Whenever a staff member uploads a new receipt in Mercury, generate an unposted expense in Wave for rapid reconciliation.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Mercury Explore Mercury →
TriggersFires when an employee submits a new expense in Mercury.
Fires when an expense in Mercury is approved.
Fires when an expense in Mercury is rejected.
Fires when a receipt is attached to an expense in Mercury.
Creates a new expense report in Mercury.
Approves a pending expense in Mercury.
Rejects a pending expense in Mercury.
Syncs an approved expense in Mercury to the general ledger.
Wave Explore Wave →
TriggersFires when a new invoice is created in Wave.
Fires when a payment is recorded in Wave.
Fires when an invoice in Wave passes its due date unpaid.
Fires when a new expense is recorded in Wave.
Creates a new invoice in Wave.
Records a payment against an invoice in Wave.
Creates a new expense entry in Wave.
Syncs a customer's billing record in Wave.
More Mercury + Wave workflows
See all Mercury + Wave integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Turn uploaded receipt files into accounting expenses” between Mercury and Wave?
Yes — describe it in the box above and Knit's Integrations Agent researches Mercury and Wave's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
What's the most common Accounting + Expense Management automation?
Creating a bill or journal entry in Wave the moment an expense is approved in Mercury, with the receipt and category carried over automatically.
Does this only fire on approved expenses, not every submission?
Yes — the Agent can be scoped to only act once an expense clears Mercury's own approval flow, so unreviewed submissions never hit the books.