Manual Conversion
Outbound: canonical payment JSON → bank pain.001.
Inbound: parse a camt.053 / MT940 / pain.002 into normalised JSON.
No file handy? Use examples/payment.json from the project.
Paste a canonical payment JSON here.
Import a bank statement (camt.053 / MT940) or a payment status
(pain.002). We normalise it, file it in the Journal with a clear number,
and create / update the Bank Account.
Users
Manage the people in your company. Two roles drive everything: Admin manages bank setup, and Approver signs off on payments — a user can hold both. Viewer is read-only.
Invite a user
They receive an email with a secure link to set their own password.
Company settings
Settings for your company. Company-level configuration lives across these areas.
Webhooks
Receive a signed POST when something happens (payment sent, delivery failed, statement received, approval needed…) instead of polling. Admin only.
Your settings
These apply to your account only — language, date display, timezone, and email alerts.
Security · Two-factor authentication
Protect your account with a one-time code from an authenticator app — required at sign-in and when you approve payments.
Security · Active sessions
Every device currently signed in to your account. Sign out a session you don't recognise, or sign out everywhere else to end every session except this one.
Security · Norwegian approver identity
Norwegian banks require an approver's national ID number (fødselsnummer) in the payment file. Enrol yours here to approve payments for those banks. It's encrypted, only ever shown masked, and never appears in any log.
Bank Accounts
One row per account — auto-populated when statements are imported or payments are sent. H2H = host-to-host channel active (EBICS / SFTP / webservice). A balance can appear without an active channel (manually imported statements).
Payments
Every outbound payment journal. Click a row to see its payment details.
Statements
Bank statements & status files received — by manual upload or auto-fetched over a channel.
Activity Log
Tamper-evidentA tamper-evident audit trail of everything that happens in this company — conversions, sends, imports, approvals, policy changes, user invites. Retained & stored in the database for 5 years (the audit trail outlives the payment/statement payloads, which are kept 90 days).
Reconciliation
Each outbound payment matched against the bank's response — a pain.002 status or
a booked camt statement entry. Cleared = confirmed by the bank;
rejected = the bank declined it; pending = awaiting confirmation.
Pending approvals
Payments waiting for sign-off, grouped by funding account. Approvers act here; the signed-in user is recorded as the approver.
Approval policy
Design how host-to-host payments are approved. Admin only. Policies attach per bank; banks with no specific policy fall back to the default. Once you lock a policy it can no longer be changed (segregation of duties), so review it carefully first.
Supported Banks
Pick a bank to open its page — set general defaults (auto-filled into payments when missing) and run the Setup Bank Channel tool for host-to-host.
Selected banks
Banks you've started setting up. Pick one to continue.
Supported banks
Don't see your bank?
Is your bank not on the list? Request it here and we'll try to obtain it.