Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.kwentra.com/llms.txt

Use this file to discover all available pages before exploring further.

Prevent changing store account after transactions are submitted. Business Value
  • Prevents balance sheet discrepancies from account changes after posting.
  • Ensures historical JVs remain aligned with store balance.
  • Provides clear validation message on blocked changes.
  • Allows changes on new stores with no transactions.
Use Cases
  • Admin attempts change on store with existing orders; system blocks it.
  • New hotel sets up stores and can freely change accounts initially.
  • Accountant gets alert when trying to separate shared store account.
How It Works Accessing Store Settings
Back Office → Inventory → Stores → [Select Store] → Edit
When Account Changes Are Blocked
  • If the store has any submitted transactions with JVs — including Receiving Orders, Stock Transfers, Stock Usages, POS Invoices, or Return Requests — the Inventory Account field cannot be changed.
  • Attempting to save a different account triggers a validation error message explaining that the account cannot be changed because existing inventory transactions are linked to it.
When Account Changes Are Allowed
  • New stores with no transactions: account can be freely set or changed.
  • Stores with only unsubmitted transactions (no JVs created yet): account can still be changed.
  • Keeping the same account as the current value is always allowed regardless of transaction history.
This validation protects the accuracy of store closing reports and the balance sheet. If you need to change a store account that has existing transactions, consult your finance team for the proper reconciliation process.