Re-upload any file below to update it in place — the date shown is the last update.

Our own fiat bank accounts as they exist in Microsoft Dynamics (not to be confused with the hot-wallet list in Reference Data). Pick Bank → Account when uploading a fiat statement and its Dynamics Account No. fills in automatically. Add or edit accounts here anytime — no code or file uploads needed.

When a fiat transaction mentions another company of the group, the matcher automatically posts it against that company's intercompany account from this table (an explicit mapping rule still wins if one matches). Recognition is case-insensitive by the "Recognise by" text, and the statement's own entity is never treated as a counterparty. Rows stay marked for review — nothing is exported without a human look.

IC journal merchant mapping

Maps a merchant to the Bal. Account used in its intercompany journal rows. Matched as a case-insensitive fragment ("BYBIT" covers BYBIT TECHNOLOGY, BYBIT GEORGIA etc.). The Bal. Account can be a G/L account, a Vendor or a Customer — pick the type and the Bal. Account No. list switches to that type's codes (all vendor/customer codes across the group). Rows without any merchant go to Interbank Transfer Control (1-10-300); rows whose merchant is NOT in this table get a journal row with an empty Bal. Account No. and Product, highlighted yellow for manual review — no guessing.

Crypto rules match on Address + Currency + Payment Type (not free text) — the Description below is generated automatically from these plus the transaction hash on import, following the agreed template.

Bank Account selected for a crypto rule: on save, this code will be moved to the front of the description, and the rule will actually post to G/L Account 1-10-210 instead.

Repeated uploads of the same file (e.g. while testing) pile up here - delete the ones you don't need. Every statement (and its transactions) is also deleted automatically 30 days after upload.