Resolving save conflicts when two people edit an invoice

ATB Invoicing prevents team members from accidentally overwriting each other's work when managing the same invoice. This guide explains why save conflict errors appear and how to review recent activity to safely re-apply your changes.

1. Why save conflict errors occur

When multiple sub-users or administrators manage invoices within the same organization, ATB Invoicing checks for updates before saving changes.

  • Form protection: If a teammate saves changes to an invoice while you are actively editing it, the system blocks your save request so their updates are not silently erased.
  • Error message: When a save conflict occurs, a red line of text appears directly under the form reading: "This invoice was changed by someone else. Refresh the page and try again."
  • Form state behavior: Your typed changes remain visible on screen, but they are not saved. Reloading the browser page will discard unsaved form entries, so any new additions will need to be retyped after refreshing.

2. How to resolve a save conflict

To ensure both your updates and your teammate's changes are captured accurately, follow these steps to reconcile the invoice:

  1. Copy unsaved entries: Before refreshing, copy any lengthy descriptions or notes you typed so you do not have to recreate them from memory.
  2. Reload the page: Refresh your browser page to pull in the latest version saved by your teammate.
  3. Check the Activity tab: Open the Activity tab on the invoice preview page to review the timestamped event history and see who edited the invoice and when.
  4. Re-apply and save: Add your updates back onto the refreshed invoice and click Save.

3. Best practices for collaborative editing

  • Save periodically: If you are making extensive mid-project adjustments or detailed line-item changes, save your progress frequently.
  • Coordinate role ownership: On shared accounts—such as a business owner and an external bookkeeper both managing invoices—agree on who owns active edits to avoid simultaneous updates.

Related articles