2.2Bank feeds & reconciliation
Bank movements. Meaningful matches.
Bring bank movements into Nestio and find who each transfer concerns. Review the amount and apply the payment with context.
See how it worksImport. Identify. Review. Apply.
Connections & matching
Application & access
Connected accounts
See the connected bank accounts that supply transaction data. Available banks and access depend on the configured provider and the account connection.
Find the transactions that need attention.
Filter by reconciliation state, source, bank or amount, and search descriptions and references.
Use the list to separate unresolved movements from those already applied or deliberately ignored.
The product principle
The reference identifies the person. The preview explains the payment.
Refresh without losing your place.
Request a refresh of connected transaction sources. Refresh work can continue in the background while you return to the list.
Choose the right person.
Review candidate people and their building context when a movement needs manual matching.
Matched is not yet applied.
Distinguish ready-to-apply movements from applied payments. Reverted applications remain a separate state for review.
Not every debit is a resident payment.
Ignore a bank fee or other irrelevant movement so it does not remain in the reconciliation queue. Ignoring a row does not create a payment.
Confidence comes from the details.
Review the transaction against the person’s outstanding amount before deciding what to do.
RF and account-based matches can identify a resident more precisely than a name alone.
Inspect the suggested person and amount instead of applying an uncertain name match blindly.
A matched transaction and an applied payment are different states. Use the history to follow the result.