A clear record of your work.

This is a synthetic demo. It uses made-up records only. Synthetic data only. Do not add real transactions, addresses, identities, passwords or keys. This page runs in your browser tab. It does not upload the files you choose and does not save anything in the browser; refreshing or closing the tab clears it. A source status or manual link does not verify a payment, a payer, or taxable income. This is not tax, accounting or legal advice, and nothing here verifies a payment, a payer or income.

Known limits

• Records are kept in memory only. Refreshing or closing the page clears them, and your browser may ask before you leave. Export first if you want a copy. Files you download stay on your device until you delete them.
• A file of more than 1,000,000 bytes is always refused, and a file of 5,000 records was never accepted in testing. In testing, files were first refused at different numbers of records, depending on the length of the rows, the length of the file name and what was already loaded. When a file is refused, the records already loaded are unchanged. Try a file with fewer records or a shorter file name, or export, use 'Clear this session' in section 04, and try again.
• The page reads one made-up asset: chain synthetic:chain-A, token synthetic:token-A. It reads its own made-up 16-column source CSV format and its own exports. A record with any other chain or token id is excluded as out of scope. No real chain, token or provider format is supported.
• Checked only by automated runs in one version of Chrome on one computer. Not checked by a person in a normal browser window. Safari, Firefox, screen readers and touch devices have not been checked.
• Not tested: opening the exported files in a spreadsheet application, saving them there and opening them again. Also not tested: real browser zoom, drop-down lists used by keyboard, the browser's own file chooser and a real phone. Not done by using the page: building a session in the recorded order of actions, and adding the same recorded source file a second time, because the page's file forms take CSV files only and the recorded test files are in another format. The page does not show how many rows are in the import history; that count was taken from the exported history file.
• When the page writes its own six files, the limit of 5,000 rows for the import history table and for the operations table cannot be reached, because the size check on each of those files, 1,000,000 bytes, comes first. Each of those two row limits was checked only on its own, outside a full session. Files loaded into the page are checked for rows separately.