The Guild Bank Audit: A Double-Entry Ledger for WoW and ESO Treasuries

The guild bank fails quietly. Nobody announces a theft. What happens is smaller and worse: a stack of flasks is gone, the log shows the deposit but not the withdrawal, and the officer team cannot answer a simple question — where did it go? That is not a trust problem. It is a record problem. And record problems have mechanisms.

This is a procedure for treating your WoW or ESO treasury as a reconciliation system. The in-game log is a cross-check, not the primary record. The primary record is a ledger your officers maintain, with every withdrawal paired to a named purpose. When the log breaks — and in WoW it has broken — the ledger still answers the question.

What the games actually give you

Start with the mechanics, because the audit has to fit them.

ESO. The guildmaster sets permissions per rank for depositing and withdrawing from the guild bank, and bank access is controlled by moving members between ranks. ZeniMax’s support page on guild bank permissions describes exactly this: the guildmaster selects each rank and sets permissions for managing resources, depositing and withdrawing, and store activity, then promotes or demotes members to apply them (Elder Scrolls Online Support, “How do I set the permissions in the guild bank?”). The Guild History tab records information about withdrawals and deposits to the guild bank, alongside joins, leaves, and store activity (ESO Academy guild overview). The guild bank itself is available to guilds with more than ten members and is accessed at any banker.

WoW. Permissions are set per tab, and the bank log is the record of movement. The log can fail. In a May 2023 US forum thread, a player reported that a deposit of 400 Feasts was recorded but the items went missing with no log of who withdrew them, during a period when guild bank logs were not updating (Blizzard US forums, “Guild Bank Log Broke, Items Stolen, Support Won’t Help”). In that thread, a respondent argued the incident traces back to how the guild master configured permissions — because the guild master sets them, anything that happened happened under that configuration. That is the correct framing, and it is the reason this article exists.

We cannot verify log retention windows or exact log scope across regions and datacenters from the sources available here. Treat the in-game log as a source that can be incomplete, delayed, or broken. Design around that.

The double-entry translation

Double-entry bookkeeping is not a game mechanic. It is an organizational practice you impose on top of the game. The translation is simple:

Every withdrawal is a debit to a named tab (the account the item left).
Every withdrawal is a credit to a named purpose (raid consumables, new-player kit, repair fund, recruitment rewards).
Every deposit is the reverse: a credit to the tab, a debit to the source (member donation, guild event surplus, store proceeds).

The point is not accounting purity. The point is that an unexplained movement shows up as an unbalanced line — a withdrawal with no purpose attached — rather than a vague sense that stuff is missing. A vague shortage produces suspicion. An unbalanced line produces a question with a name attached.

Design tabs as accounts

Your tab structure is your chart of accounts. Design it before the incident, not after.

A workable three-tier schema for a 20–200 member roster:

Public consumables tab. Small stacks. The forum advice in the WoW thread — split stacks into smaller ones, because the bank counts withdrawals by stacks — is a design recommendation worth adopting. A member who needs four flasks takes four flasks, not a stack of twenty. The tab’s permission tier is the widest you are willing to grant.
Officer materials tab. Crafting mats, enchants, repair funding. Withdraw permission limited to officer ranks. Every withdrawal logged to a purpose in the ledger.
Locked high-value tab. Rare drops, expensive consumables, anything you would notice missing. Withdraw permission limited to the guildmaster and one or two named officers. This tab is reconciled weekly, not monthly.

In ESO, this maps cleanly onto ranks: the guildmaster sets deposit and withdraw permissions per rank, so the locked tab corresponds to a rank only the guildmaster and trusted officers hold. In WoW, the mapping is per tab, and the 2024 EU forum thread is a useful warning: a guild leader reported buying a fourth tab they could access but their officers could not, and another poster noted each tab has its own permissions. When you add a tab, set its permissions explicitly. Do not assume they inherit.

The weekly reconciliation pass

One officer, one hour, once a week. The ritual has four steps:

Opening balance. Record what the ledger says each tab should hold at the start of the week.
Logged movements. Pull the in-game log for the week. For each movement, confirm a matching ledger line exists with a named purpose.
Closing balance. Record what the ledger says each tab should hold at the end of the week.
Variance note. Any difference between the ledger and the in-game state gets a dated note: what is missing, what the log shows, what the log does not show, and what action was taken.

The variance note is the artifact that survives officer turnover. It is also the document you hand to a new officer on day one, so they inherit a record instead of a rumor.

When the log itself is broken

The WoW forum case is the template. Deposits logged, withdrawals not. Support declined to treat it as theft because the characters had permission to withdraw — which is the correct reading of the rules and the wrong answer for the guild. The guild’s protection was never support. It was the ledger.

When the log is broken, the response is mechanical:

Freeze high-value withdrawals. Lock the high-value tab to the guildmaster and one officer until the log is confirmed working.
Switch to manual receipts. Every withdrawal from the officer and high-value tabs gets a written receipt in the ledger — who, what, when, purpose — before the item leaves the bank.
Do not rely on support to reconstruct the record. In the WoW thread, support stated it could not provide names or details. Plan for that answer.

For context on how other games handle this: the Guild Wars 2 wiki states that a log is automatically maintained of all guild vault deposits and withdrawals, that players may withdraw up to 500g a week as a combined total across all sections, and that ArenaNet cannot replace items or wealth lost from a guild bank. The GW2 rules do not apply to WoW or ESO, but the pattern is instructive: the game provides a log and a cap, and the operator provides the discipline. Your WoW and ESO setup should assume the same division of labor.

Copy-paste artifact: the ledger sheet

Build this as a shared spreadsheet. Columns:

Date | Game | Tab (account) | Direction (in/out) | Item or gold amount | Quantity | Character | Purpose (credit) | Log confirmed (Y/N) | Variance note | Reconciled by

Tab mapping table:

Tab name | Account type | Permission tier | Reconciled | Owner
Public consumables | Expense | All members | Weekly | Quartermaster
Officer materials | Expense | Officer+ | Weekly | Raid lead
High-value locked | Asset | GM + 1 officer | Weekly | Guildmaster
Repair fund (gold) | Asset | Officer+ | Weekly | Treasurer

Permission matrix, to be filled in per game and per rank:

Rank | Deposit | Withdraw (public) | Withdraw (officer) | Withdraw (locked) | View log
Guildmaster | Y | Y | Y | Y | Y
Officer | Y | Y | Y | N | Y
Member | Y | Y | N | N | N
Recruit | N | N | N | N | N

In ESO, this matrix is applied through rank permissions in the guild panel. In WoW, it is applied per tab. The matrix is a recommendation, not a game rule — adjust the tiers to your roster size and activity level.

Why the ritual matters more than the investigation

A one-time investigation after a loss produces a report nobody wants to read and a conclusion nobody trusts. A weekly reconciliation produces a habit. The habit is the governance. It means that when an officer leaves, the ledger is current. When a new officer joins, the handover is a document. When a member asks where the raid consumables went, the answer is a line in a sheet, not a memory.

Publish the norm to members before any incident: we reconcile weekly, and every withdrawal has a purpose. That sentence reduces the social cost of asking questions later. It also makes the audit what it should be — a routine, not an accusation.

FAQ

Does ESO have a separate gold ledger from the item log? The Guild History tab records information about withdrawals and deposits to the guild bank, and ESO’s rank permissions include a distinct withdraw-gold permission. We cannot verify from the available sources whether the history separates gold movements from item movements in a dedicated view. Treat gold as its own account in your ledger regardless.

Can I recover items through support? In the WoW forum case, support declined to treat the incident as theft because the characters had permission to withdraw, and stated it could not provide names or details. The GW2 wiki states ArenaNet cannot replace items or wealth lost from a guild bank. Plan for the answer that support will not reconstruct your record.

What if I only have ten members? ESO’s guild bank is available to guilds with more than ten members. Below that threshold, the ledger still applies to whatever storage you use — the discipline does not depend on the bank existing.

How often should the locked tab be reconciled? Weekly. Monthly is too slow for high-value items; a month of unlogged movement is a month of unanswerable questions.