Save Changes to a File

Use this guide when you want to be sure your current work is really preserved.

Before you start #

Know whether your current session is attached to a real save target or is still acting like a working copy.

What you will do #

Use save or save-related actions intentionally, confirm the file is bound the way you expect, and create an export when you need a stronger checkpoint than ordinary autosave.

1. Check whether the current file is bound normally #

The first question is not “did I click save?” It is “what kind of session am I in?”

In ordinary day-to-day use, a normal bound file has a real save target and Common Cents can autosave it in the background.

If you are working in an imported copy or another temporary working copy, Common Cents may still hold your changes, but the session is not bound the same way. That is the moment to think about Save As instead of assuming ordinary autosave is enough.

2. Let autosave do the normal work when the file is bound #

When the current file has a real save target, Common Cents saves in the background after a short pause and on a repeating timer during longer sessions.

The simplest signal is the Save button in the top-right area of the app.

• if it is blue, your data is saved
• if it is not in the saved state, pause and make sure the app has had a chance to finish writing

In a normal session, you do not need to manually save after every field edit.

3. Use manual save when you want an immediate write #

If you want to force the save intentionally, run save from the app controls or from the Combo Palette.

This is useful when you:

• just finished a dense cleanup session
• want a clean stop point before you switch tasks
• want to confirm the file is written before closing the app or the browser tab

4. Use Save As when you need a new working file #

Use Save As when you want the current document to become a newly named .cents file.

This is the right move when:

• you want to branch into a new working file
• the current session is an imported copy and needs a real saved file name
• you want the new file to become the active document you keep editing

After Save As, Common Cents switches your session to the new file.

5. Use Create Backup when you want a checkpoint but do not want to switch files #

Use Create Backup when you want a safety copy while keeping the current file open.

This is usually the best choice before:

• a large import
• major transaction cleanup
• category or payee reorganization
• any change where you want an easy return point

This writes another .cents copy, but it does not move your active session away from the file you were already editing.

6. Do not confuse CSV exports with your primary save flow #

CSV exports are useful handoff and reporting tools, but they are not a replacement for saving the actual .cents file.

Use CSV exports when you want:

• external analysis
• a reporting file
• an import-ready CSV for another workflow

Use autosave, Save As, or Create Backup when your goal is preserving the real Common Cents file itself.

7. Remember what undo and redo can and cannot do #

Undo and redo are for recent mistakes in the current session.

They are not:

• version history
• a substitute for backups
• a guarantee after reload or restart

If the change matters enough that you want a reliable checkpoint, create a backup file instead.

8. Use recovery only when normal file access is gone #

If something went wrong with the file target and the startup screen shows Recover Data, Common Cents still has browser-held data it may be able to save back out to a new .cents file.

Use that button when the original file is no longer available or no longer trustworthy.

Quick decision rule #

Use this shortcut when you are not sure which save-related action you actually need:

• let autosave handle normal bound-file editing
• use manual save when you want an immediate write now
• use Save As when you want a new active file
• use Create Backup when you want a safe return point
• use CSV export only when the goal is reporting or external data use

See also: Saving, Autosave, and Recovery, File / Export, and Exporting Data and Backups.