1. Prepare the source
Use Statement or transaction data input. Remove passwords where appropriate and choose clear, complete source material.
Finance · CORIN TOOLS
Spending Categories
Group transactions into useful categories for a clearer spending review.
Input: Statement or transaction dataOutput: Categorized transactions
See the result you’re working toward
Explore a sample result below. File upload and conversion are not enabled on this page yet.
Sample result
date,description,amount,suggested_category,review_status 2026-10-01,Office supplies,-42.50,Office expenses,Needs review 2026-10-02,Transfer to savings,-200.00,Transfer,Needs review
Sample content only. This is not a conversion of your document.
How Spending Categories fits into your work
2. Inspect the structure
Check how the content should map into Categorized transactions. Start with the example output while file processing is being connected.
3. Review before using
Compare important details with the source. Merchant descriptions are clues, not proof. Review category choices and keep transfers separate from expenses.
Where this is useful
Expense review
Group transactions into useful categories for a clearer spending review. Use the result as a starting point for editing and review.
Budget planning
Group transactions into useful categories for a clearer spending review. Keep the source available so another person can check the details.
Monthly summaries
Group transactions into useful categories for a clearer spending review. Bring reviewed information into the next step of your process.
Understand the output
Tabular data works best when each row describes one record and each column has a consistent meaning. Keep units, currency and date formats explicit. A spreadsheet import can change identifiers or leading zeros.
Merchant descriptions are clues, not proof. Review category choices and keep transfers separate from expenses.
Frequently asked questions
Can I use this tool now?
You can explore, copy and download sample output. Conversion of your own files is not enabled yet. Contact Corin if you want to discuss this capability for your workflow.
What input and output should I expect?
This page covers Statement or transaction data input and Categorized transactions output. Tabular data works best when each row describes one record and each column has a consistent meaning. Keep units, currency and date formats explicit. A spreadsheet import can change identifiers or leading zeros.
What should I check before using the result?
Merchant descriptions are clues, not proof. Review category choices and keep transfers separate from expenses.
What about scans, photos and difficult layouts?
Scans and photos require text recognition before conversion. Blur, rotation, handwriting, merged cells and multi-column layouts can introduce errors. Use the clearest source available and review the extracted information.
Are my documents uploaded or stored?
There is no upload control on this page, so it does not receive your source documents. The sample is built into the page. Processing limits, retention and deployment options must be confirmed before a live service is enabled.
Can I automate this as part of a larger process?
Talk to Corin about the tools, connectors, permissions and review steps your process requires. A standalone example does not establish a live API or guarantee compatibility with a particular system.
Related tools
Connect the next step.Bring reviewed information into a coordinated workflow with Corin.
Discuss your workflow ↗