CONNECTED BUSINESS OPERATIONS
Import bank statements with duplicate review
Bring supported bank CSV rows into a reviewable import linked to the correct bank account.
Know which rows the statement import accepted
Account identity, source rows and duplicates are checked before reconciliation.
A clear responsibility in your daily work
A transaction file needs more than an upload button. The team must know which account it represents, whether the same statement was imported before and which rows still require review. Tsumira retains import identity and row counts so reconciliation starts from identifiable evidence.
Choose the correct account first
Bank imports are attached to a bank account with its own identity. Review institution and account details before selecting a statement. A familiar file name is not enough to establish the account, particularly when one colleague handles several accounts or receives files from another person. Amounts use whole Japanese yen and Japanese consumption-tax categories. Check whether the document is tax-inclusive or tax-exclusive, which tax treatment applies, and which customer or case it concerns. This finance workflow is designed for that scope; it does not establish suitability for another country's accounting obligations.
- Check account identity before importing rows.
Inspect what the import accepted
The import records source rows, accepted rows and duplicate counts. Supported CSV parsing normalises statement information rather than assuming every bank export has the same structure. A file-level content identity and transaction identities help identify repeated material. Investigate unexpected totals before proceeding to payment allocation. Preparation, permission to act and the final financial result are separate checks. Review the relevant document state and any approval requirement before issuing, correcting or recording a financial action. AI assistance stays subject to review and the user's permissions; an explanation or proposed action is not proof of execution.
- Compare source, imported and duplicate row counts.
Preview the statement rows and duplicate
Compare source, imported and duplicate row counts before trusting the transaction list.
| Booking date | Direction | Amount | Import review |
|---|---|---|---|
| Nov 1 | Incoming | 50,000 | Accepted |
| Nov 2 | Incoming | 30,000 | Accepted |
| Nov 1 | Incoming | 50,000 | Duplicate · review |
Separate imported evidence from paid invoices
An imported transaction does not automatically prove which invoice was paid. Review incoming and outgoing directions, transaction details and duplicate questions, then use reconciliation for a proposed allocation. Keep the original statement available to the people responsible for investigating a disputed match. Keep the source reference and inspect the resulting document, payment or evidence record. Changes in outstanding amounts need a business explanation, particularly when several people work on the same case. Agree who checks exceptions and who reconciles the final result with the accounting process used by your business.
- Import first; confirm the payment allocation separately.
A concrete workflow
Prepare the context
Select the intended bank account and prepare a supported CSV, retaining the original file as the basis for review.
Review the decision
Inspect import results and duplicate information. Resolve an unexpected row count before treating the transaction list as complete.
Check the result
Open the relevant incoming transaction for reconciliation and review the invoice relationship before confirming any payment effect.
An illustrative working example
Illustrative working example
A finance colleague receives the same month-end statement twice under different file names. The team checks the account identity and import evidence rather than trusting the names. Duplicate information guides review; a remaining incoming payment is then assessed against the appropriate invoice.
Questions about this topic
Does this connect directly to every bank?
No. This workflow imports supported CSV statement data; it does not claim universal live bank connectivity.
Are duplicates considered?
Import and transaction identities support duplicate handling and review. Inspect the reported counts and any review items.
Does importing mark invoices paid?
No. Statement import and confirmed payment allocation are separate stages. Review the relevant reconciliation proposal.
Can the file be in any currency?
The current finance workflow uses whole JPY. Confirm supported file structure and account scope before importing.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Microsoft Excel
Workflow concept: Inspect bank CSV columns and duplicate source rows before planning a controlled import.
Google Drive
Workflow concept: Retain the original statement file with its bank-account context.
Google Sheets
Workflow concept: Compare import row counts with a reviewed source checklist.