How to use Mercuryo Statements
The full cycle in one line: reference data → rules → upload → review → export. Details below.
Quick start
- Make sure reference data is fresh (Reference tab — the dates tell you).
- Upload the raw statement on the Statements tab (pick entity + type first).
- Rows matched by rules arrive labelled. Skim anything marked review, label it, and turn the label into a rule so next month it's automatic.
- Hit Export to Dynamics 365 — you get the exact 25-column upload workbook, colour-coded headers included.
Roles & access
| Role | Can do |
|---|---|
| viewer | Look and export. Nothing else. |
| user | Day-to-day work: upload, label, confirm, export. |
| admin | Everything, plus deletes, team access approvals and statement-format settings. |
New colleagues register with a @mercuryo.io email and wait for an admin to approve them (Admin Panel → Team Access).
1 · Reference data
Vendors, Customers, Merchants, Bank Accounts (hot wallets) and GL Codes — uploaded as .xlsx, most with one sheet per legal entity. Re-uploading a file updates it in place; the date next to each list shows the last update.
Codes drive everything: matching, the Bal. Account No. column, the Merchant column in the export. Keep the files in the agreed template.
2 · Rules
A rule says: "when the description contains this text, label the transaction this way" — Bal. Account, Posting Type, Merchant, Product, Cost Centres and so on. The search string matches anywhere inside the description; no wildcards needed.
Three ways to create rules:
- By hand — the Create New Mapping Rule form on the Rules tab.
- From a transaction — label a row during review and save it as a rule in one step.
- Train from history — feed a zip of past Dynamics uploads; the tool proposes rules from what your team already labelled manually.
3 · Upload
Pick the legal entity and statement type (fiat / crypto), drop the file. Formats are auto-detected — bank exports, exchange sheets (Kraken, HTX, Scrypt…), zipped archives. Repeated uploads of the same file simply pile up in Uploaded statements; delete the ones you don't need.
4 · Review
Every row gets a status:
| Status | Meaning |
|---|---|
| label | Matched by a rule — trustworthy, still glance at it. |
| review | No rule matched (or only a weak name guess). Needs a human. |
| confirmed | A person checked and confirmed the row. |
In the export, rows that still need attention are highlighted yellow so nothing slips into Dynamics unnoticed.
5 · Export
One click produces the Dynamics 365 upload workbook: fixed 25 columns, colour-grouped headers, frozen header row with filters, VENDOR/CUSTOMER/G-L ACCOUNT in caps, two decimals for fiat and five for crypto. Upload it to Dynamics as usual.
Statement formats admin
Admin Panel → Statements Format Management describes how each exchange's raw export is parsed: expected columns, sheet names, G/L account, whether the exchange is addressless, and so on. When a new exchange appears — add a row there, no code changes needed.
Housekeeping
- Uploaded statements (and their transactions) are deleted automatically 30 days after upload.
- Rules and reference data are not auto-deleted — and can be backed up in one click (Admin → Backup).
- Deleting anything asks you to wait 5 seconds — that's on purpose. Read the message.