Can a transaction be moved from one branch to another after it’s created?

No, a transaction cannot be moved from one branch to another after it’s created. The branch is set at the moment the transaction is created and is permanently tied to it — there’s no action to reassign the branch afterward.

The reason is that the branch isn’t just a descriptive label on the document. It’s tied to everything that follows from it: branch-level invoices, journal entries, sequential transaction numbers, employees’ branch permissions, and reports filtered by branch. Moving a transaction after creation would mean rebuilding all of these under a different branch.

This principle shows up elsewhere in the system as well. If you try to edit, delete, or close a fiscal period from a branch other than the one it was created from, a message appears explaining that the action can only be performed from the branch it was created in.

Practical workaround: If a transaction was recorded under the wrong branch, delete or cancel it from the branch it was created in, then switch to the correct branch and recreate it there. Before deleting, check for any linked documents, such as payments, returns, or stock vouchers, since they may block the deletion or need to be re-entered as well.

Note: Confirm the selected branch before saving a transaction, especially if your account has access to more than one branch. Switching branches before saving is much easier than handling it afterward.