Saturday, 15 August 2026, 10:37 AM
Created by: Ruvenss G. Wilches
Statements Import does not work in isolation — it reads from and writes to the core NIZU modules you already use. It never stores its own copy of your financial data; it reconciles against the real records.
The primary target for money received. When you reconcile an incoming transaction, the app creates a real invoice payment against the matched invoice and refreshes the invoice status — exactly as if you had added the payment manually. The matching engine reads open invoices (their number, total and outstanding balance) to suggest matches.
Each bank account you reconcile is a NIZU payment method. The app attaches the account IBAN to that payment method, and books every reconciled payment under it, so bank-reconciled income is traceable to the exact account and distinguishable from manually entered payments in your reports.
Invoices belong to clients, so reconciled payments flow straight into each client's account and balance.
Money paid out (debits) reconciles against the Expenses module. From a money-out transaction you create an expense in one step — pre-filled with the amount, date and counterparty (as the title) and the communication (as the description) — after choosing an expense category. A default category can be set in the app's settings so it is pre-selected. The created expense is a normal NIZU expense and can be edited afterwards (provider, project, tax, billable). Reversing the reconciliation removes the created expense. Matching a debit to an existing expense is on the roadmap.
Because reconciled payments are ordinary NIZU records, they immediately feed the core financial Reports (and the AI Reports app) — cash flow, income, and outstanding balances all reflect the bank activity you imported.
Overpayments are designed to route the surplus to the customer's client wallet after paying the invoice.
When AI reconciliation is enabled, the app connects to one external AI provider of your choice — OpenAI, Anthropic (Claude), Grok (xAI) or DeepSeek — using your own API key, configured in the app's settings. It reuses NIZU's shared AI provider engine, so the setup mirrors other AI-enabled NIZU apps. The provider is only contacted to help match unmatched incoming transactions, and only receives the transaction details plus a shortlist of candidate invoices.