Ledger Transfer

When a General Journal Entry Is Not Enough

In a multi-store environment, each store maintains its own set of GL balances. A General Journal entry posts to only one store. If you need to move value between stores — for example, to allocate head-office expenses to branches, transfer accrued liabilities, or reclassify balances across locations — a simple journal entry cannot do this because it would only affect one store's books.

The Ledger Transfer solves this by creating a pair of linked transactions:

• From side (sending store): Credits the source account and debits the Transfer Account (clearing).
• To side (each receiving store): Debits the same account and credits the Transfer Account (clearing).

The Transfer Account acts as an inter-store clearing account. When both sides are posted, the clearing account nets to zero across all stores, and the balance has effectively moved between locations.

Common Use Cases:

• Accrual transfers — A head office accrues an expense (e.g., insurance, rent) centrally, then distributes the cost across branch stores.
• Expense allocation — Shared costs like advertising, IT, or corporate overhead are split proportionally to branches.
• Inter-store settlements — When one store pays an invoice that belongs to another store, the ledger transfer moves the payable to the correct store.
• Balance reclassification — Moving a balance from one account to the same or different account across stores (e.g., reclassifying a liability from Store A to Store B).
• Year-end close allocations — Distributing retained earnings or dividends across stores.

Transfer No.

Auto-generated transaction number for the sending side. Sequence numbering is by store.

Date

Posting date for the transfer. Both the sending and all receiving transactions share this date.

Store

The sending store — the store from which the balance is being moved.

Employee

Auto-filled from the current session.

Station

Auto-filled from the current session.

Memo

Free-text reason for the transfer (e.g., "Q1 insurance allocation" or "IT cost share — March"). Appears on the GL detail for both sides.

Account

The GL account being transferred. When selected, the Balance field shows the current balance of this account in the sending store as of today. This helps confirm you are transferring from the correct account and that sufficient balance exists.

Balance

Read-only. The current balance of the selected account in the sending store. Updated in real-time when the account is changed.

Amount

The total amount to transfer out of the sending store. This is the value that must be fully allocated across the receiving stores in the table below.

Reference

Optional cross-reference or note for the transfer.

Status

Posting status: Posted (live), Suspended (draft), or Voided (inactive).

Time

Posting time. Defaults to the current time.

The allocation table specifies which stores receive portions of the transferred balance. Each row creates a separate linked transaction in the receiving store. Columns:

Store — The receiving store. Select from the store lookup.
Transfer No. — Auto-generated transaction number for the receiving side (read-only).
Amount — The amount allocated to this store. When you tab from the Store column to the Amount column, the system auto-fills the remaining unallocated balance as a convenience.

You can allocate to multiple stores — for example, sending $3,000 from Head Office to three branches at $1,000 each. Each receiving store gets its own linked transaction.

Transfer Account

The GL clearing account used to bridge the inter-store movement. Defaults from the store's Transfer Account setting (configured on the Store Master). If the store does not have a Transfer Account set, this field must be filled manually; it will be saved back to the store for future use.

Allocated

Read-only. The sum of all amounts in the allocation table. This must equal the Amount field above.

Difference

Read-only, displayed in red. Shows Amount minus Allocated. The transfer cannot be saved unless the difference is zero. This ensures that the total leaving the sending store exactly matches the total arriving at the receiving stores.

Sending store (From):

• Credit the source Account by the Amount (removes balance).
• Debit the Transfer Account by the Amount (clearing — balance in transit).

Each receiving store (To):

• Debit the same Account by the allocated amount (adds balance).
• Credit the Transfer Account by the allocated amount (clears the transit balance).

Net effect: The Transfer Account nets to zero across all stores. The source account's balance has moved from the sending store to the receiving store(s).

Example: Head Office (Store A) transfers $5,000 of accrued Rent Expense to Store B ($3,000) and Store C ($2,000):

Transfer Account across all stores: $5,000 Dr − $5,000 Cr = $0.

• The transfer must balance to zero (Difference = 0) before saving.
• Ledger Transfers cannot be deleted. To reverse a transfer, create a new transfer in the opposite direction.
• The Transfer Account is saved to the store record if not already set, so future transfers default to the same clearing account.
• Reconciliation cleared dates from the original transaction are preserved when editing.