Bank

List bank accounts for this connection's business profile (id, provider, IBAN, currency, linked COA account).

List bank transactions for one bank account (from list_bank_accounts) - includes classification, status (imported/needs_review/matched/posted/etc), and amounts.

Import bank transactions the caller already read and extracted from a statement (PDF, CSV, screenshot, whatever - this tool does no parsing/OCR itself, pass in already-structured rows). Requires a connection with draft_write or full_post permission tier. Lands every transaction as status='imported'/'needs_review', same as any normal statement import - nothing is classified or posted yet, use classify_bank_transaction and post_bank_transaction (after preview + user confirmation) for that.

Correct a bank transaction's own fields (e.g. a bad import — wrong date/amount/description/counterparty). Requires draft_write or full_post tier. Rejected if the transaction's status is posted or reconciled - reverse the journal entry first. Does NOT touch status/classification/journal_entry_id - use classify_bank_transaction or the post/preview tools for those.

Permanently delete a bank transaction row (e.g. a duplicate or bad import). Requires draft_write or full_post tier. Rejected if the transaction's status is posted or reconciled - reverse the journal entry and void it first. Not reversible via this tool.

Classify a bank transaction (e.g. invoice_payment, expense_payment, foreign_service_purchase, shareholder_loan, bank_loan, loan_granted, loan_repayment_received, capital_contribution, stripe_payout, tax_payment, salary, bank_transfer, fee, technical_verification_deposit, other). Requires a connection with draft_write or full_post permission tier. Always leaves status='needs_review' regardless of confidence - classification alone never posts anything or marks a transaction ready.

Dry-run preview of posting a bank transaction to the ledger - shows the transaction detail and which chart-of-accounts account would be credited/debited, but posts NOTHING. Required before post_bank_transaction will succeed (same bankTransactionId+creditAccountId, within 15 minutes). Show this briefing to the user and get their explicit go-ahead before calling post_bank_transaction - never chain straight from preview to post without the user confirming in between.

Post a bank transaction to the ledger - creates a REAL journal entry, not reversible via this tool. Requires a connection with full_post permission tier, AND a matching preview_bank_transaction_posting call for the exact same bankTransactionId+creditAccountId within the last 15 minutes, AND the user has explicitly confirmed after seeing that preview. Never call this speculatively or without the user's explicit go-ahead. After posting, give the user a short briefing of exactly what was posted (accounts, amounts, date).