Turn multiple files into a spreadsheet
Use a Kuse Project to organize multiple source files, define the fields you need, and create a spreadsheet-ready output.
When the hard part is getting several files into one usable structure, start with the source set and describe the spreadsheet you need. The result should be designed for the next task, not just for reading once.
Use this guide when
You have more than one source file, the files use different layouts or labels, and the next step needs a table that can be filtered, checked, sorted, or handed to someone else.
Prepare the Project
Create one Project for the task. Add the source files and use names that help identify their origin. If the files contain several currencies, periods, departments, or document types, make that visible in the file names or prompt.
Define the target table
Name the columns before you ask. For example: source file, account, date, description, category, amount, currency, status, and notes. Ask Kuse to preserve source references and mark gaps as “To confirm”.
Read the selected files and create a spreadsheet-ready table. Include Source File, Date, Description, Category, Amount, Currency, and Status. Normalize date and amount formatting. Preserve the source file name for every row. If a value cannot be supported by the source files, leave it blank and set Status to "To confirm". Do not add recommendations or conclusions that are not in the files.
Example input set
Imagine a Project with monthly statements from several sources, a previous reconciliation workbook, and a short note explaining the reporting period. The files do not use identical labels, and some rows may be missing a category or currency. The goal is to create one table that a reviewer can filter and check.
Decide the table before you ask
Define the columns and their meaning before Kuse creates the result. A practical schema might include Source File, Source Row or Reference, Account, Date, Description, Category, Amount, Currency, Status, and Notes. Add only the fields the next user will actually review or use.
Map every row to a source
- Keep the source file name for each row.
- Preserve a source row, page, or other reference when the input makes that possible and the reviewer needs traceability.
- Do not merge two records only because their descriptions look similar. Mark possible duplicates for review.
Normalize carefully
- Dates: choose one output format and keep the original value available when the date is ambiguous.
- Amounts: separate numeric values from currency and do not infer a missing currency from an unrelated file.
- Categories: use an approved list when one exists. Otherwise keep the source label or mark the category for review.
- Missing values: leave them blank and use Status or Notes to explain what needs confirmation.
Review exceptions before totals
Filter the result for “To confirm”, missing source references, duplicate candidates, conflicting currencies, and unusual date formats. Resolve or annotate these rows before using totals, charts, or summaries. Kuse can help organize the review, but the user confirms the accounting, compliance, or business meaning.
Acceptance checklist
- The workbook opens and the expected sheet or table is present.
- Every required column has a clear definition and consistent data type.
- Rows retain a source reference and missing values remain visible.
- Dates, amounts, and currencies follow the requested rules.
- A human reviewer checks exceptions before the output is used for reporting or decisions.