Monobank Webhooks vs. Statement Import: When to Use Each

Use Monobank webhooks for real-time, hands-off capture of new card transactions in FinMan. Use statement import to backfill older history from before you connected. Don't import a statement covering dates already captured by webhooks, or you'll create duplicates — keep the two methods on separate date ranges.

Two ways to get Monobank data into FinMan

FinMan can pull your Monobank spending in two different ways, and they solve two different problems. Knowing which to use keeps your records clean and your categories tidy.

Webhooks: hands-off, going forward

The Monobank integration uses webhooks: every time your card is charged, FinMan captures the transaction automatically — amount and merchant — with no manual typing. This is the method you want for everyday tracking. Once connected, new purchases flow in on their own and AI auto-categorization sorts them.

The catch: webhooks only capture transactions from the moment you connect onward. They can't reach back into history.

Statement import: backfilling the past

To bring in spending from before you connected — say the last few months — export a statement from Monobank and send the file to the FinMan bot (or upload it in the web app). FinMan's self-learning templates parse it; known formats are recognized instantly, and unknown ones get an AI-generated template on the fly.

This is your tool for a one-time backfill, not for ongoing capture.

Rule of thumb: webhooks for the future, statement import for the past — and never let the two overlap on the same dates.

Avoiding duplicates

The one mistake to avoid: importing a statement that covers dates your webhooks already handled. That creates two entries for the same purchase. Keep them on separate date ranges:

Connect webhooks first and note the date you did it.
Import statements only up to the day before webhooks went live.
If you already have overlap, review the affected days and delete the duplicate manual entries.

A clean setup, start to finish

Enable the Monobank integration so new transactions capture automatically.
Export a statement covering the earlier period you're missing.
Send the file to the bot; let AI parse and categorize it.
Spot-check the seam between imported and webhook dates.

After that, your ongoing spending is fully automatic, and your history stretches back as far as your statement went — with no double-counting in between.