Practical transaction-data guide

How to convert copied transaction data to CSV

Transaction records copied from an email, PDF, accounting report, or business system often look organized on screen but paste as uneven text. A reliable conversion must recognize the intended columns, keep currency commas inside the Amount field, and preserve dates and identifiers exactly.

Recognize space-aligned transaction data

Many reports separate columns with tabs or repeated spaces rather than actual CSV commas. The records below contain four fields: Date, Transaction_ID, Amount, and Category. The commas inside the amounts are part of the values.

Date        Transaction_ID    Amount      Category
09/10/2026  TXN-9901          $1,200.50   Software SaaS
09/11/2026  TXN-9902          $2,500.00   Office Supplies

Date,Transaction_ID,Amount,Category
09/10/2026,TXN-9901,"$1,200.50",Software SaaS
09/11/2026,TXN-9902,"$2,500.00",Office Supplies

Why currency values can create the wrong columns

A basic “split on every comma” operation treats the comma in $1,200.50 as a column boundary. The result may place $1 in one cell and 200.50 in another. A correct CSV converter first identifies repeated spaces or tabs as the real boundaries, then quotes currency values that contain commas when it creates the CSV file.

The same problem can affect names written as Smith, Jordan, addresses, notes, and descriptions. Previewing the table before downloading makes these structural mistakes visible.

Convert the records with TextGleam

1. Paste the copied transaction records into the CSV and table cleaner.
2. Select Trim cells and build table.
3. Confirm that each date, transaction ID, amount, and category appears beneath the correct header.
4. Edit any shifted or incomplete cell directly in the preview.
5. Select Download clean CSV for a CSV file or Export to Excel for an XLSX workbook.

Convert transaction data into a table →

Protect identifiers and dates from spreadsheet changes

• Transaction IDs: keep identifiers such as 0001842 as text if leading zeros matter.
• Dates: confirm whether a value such as 09/10/2026 means September 10 or October 9.
• Long numbers: spreadsheet software may round long account or reference numbers.
• Negative amounts: confirm whether the source uses a minus sign, parentheses, or a separate debit column.
• Currency symbols: values containing different currencies should keep their symbols or receive a separate Currency column.

Validate the conversion before using it

Structural cleanup does not prove that the underlying records are correct. Compare the converted table with the source and perform a few simple checks:

• The number of data rows matches the original report.
• Every row contains the same expected columns.
• Transaction IDs remain unique where the source requires uniqueness.
• Currency values remain in one Amount cell.
• The sum of the converted amounts matches the source total.
• Blank rows and exact duplicates were removed only when appropriate.

Choose CSV or Excel based on the next task

CSV is widely supported and useful for importing records into another system. It stores values and rows without workbook formatting or formulas. Excel format is more convenient when the next step involves formatting, formulas, multiple sheets, or manual review. Keep the original source alongside either export until validation is complete.

TextGleam performs this conversion in your browser and does not upload the pasted records to TextGleam. Local processing does not anonymize names, account numbers, or other identifiers, so review the result before sharing it elsewhere.

Next: learn how separators and quoted values affect columns →