> For the complete documentation index, see [llms.txt](https://wiki.qfdevelopers.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.qfdevelopers.com/scripts/banking-v2/admin-panel.md).

# Admin Panel

Page dedicated to the admin panel of our Banking \[V2]

Everything a server owner sets in Banking V2 is set here, in game, and saved to the database. Open it with `/bankadmin`. Changes apply at once, without a restart, and open bank screens, ATMs and tablets reload by themselves.

Every module shows **Save** and **Cancel** only when something was changed. When two admins edit the same thing, a save made from an outdated copy is refused and the current values are loaded, so nobody overwrites anybody by accident. Every action is written to **History** and, when set, to the `admin` Discord webhook.

{% hint style="info" %}
Places (branches, offices, the exchange, depots and ATMs) are added with **Add here**: the place goes where you stand, facing where you face. You can fine-tune it later on the map, with **Use my position** or by teleporting to it.
{% endhint %}

## Overview

### Dashboard

The state of the whole server's economy: money in accounts, bank treasuries, cash in ATMs, clients and active cards, operations in the last 24 hours, inflow over 14 days, banks by number of clients, the week's large transactions and a list of what needs attention (insolvent banks, banks with a negative treasury, ATMs out of order, frozen accounts).

### Players

Search any account and open it. You can:

* add or take money (a reason is required and saved in the history),
* freeze or unfreeze an account,
* block cards, unlock a card locked by wrong PINs or reset its PIN,
* read and correct the credit rating,
* see the last operations of the account and the player's other accounts.

### History

Every admin action (banks, cards, accounts, market, credit, imports) with who did it and when, and the output of the console imports.

## Banks

### Banks

Add, edit and remove banks. Each bank has a name, short name, founding year, a description for clients and a story shown at the bank exchange, a logo (presets, a letter logo, your own file or a link from the allowed hosts), a bank colour and a card colour with a live card preview. Here you also set:

* **Status and owner**: whether the bank is the state's, for sale or owned by a player, and its price.
* **Fees**: the ATM fee for clients of other banks and the fee to move an account in.
* **Map blip**: sprite and colour of its branches.
* **Treasury**: add or take money from the bank's treasury, with a reason.

The state bank can never be sold. A removed bank's accounts, branches and ATMs go to the state bank.

### Branches

Every place in the city. **Add here** first asks what you are placing:

* **Branch**: a counter with a teller for accounts, cards, deposit boxes and the vault.
* **Management office**: where the owner and managers run the bank on the management tablet.
* **Bank exchange**: where banks are bought and sold, with the map of every bank in the city.
* **Convoy depot**: where cash convoys start and end.

The type stays with the place. For each place you set its name, bank, the staff ped model and scenario (or no ped, only a target zone), the interaction radius and the map marker. A branch also has its points (the ticket machine, the deposit box wall, the vault unload point), an alarm name for your bank interior, and opening hours set by its owner. An office can be run at a **desk monitor** instead of a receptionist: press **Measure in game**, look at the monitor and fit the outline.

### ATMs

* **Placed ATMs**: ATMs of a bank, placed where you stand, with a prop model, capacity, whether they take deposits and whether they work. **Fill up** fills one to capacity from the bank's treasury.
* **Models and cash**: the map's own ATM props that work as the state bank's ATMs (`prop_fleeca_atm`, `prop_atm_01`, `prop_atm_02`, `prop_atm_03` by default), deposits at ATMs, and whether ATMs hold real cash (off, player banks only, or every bank).
* **ATM on the machine's screen**: the camera moves in and the ATM runs on the prop's own screen instead of a window (off by default). Built-in screens are measured for all four default models; another model is measured with `/bankadmin atm-screen`.

### Economy

* **Overview**: the central bank reserve, cash in branch vaults, in ATMs and on the road, the last 7 days in and out and the reserve movements.
* **Central bank**: the reserve all branch vaults are supplied from. **Static** refills it to a set amount every few hours, **dynamic** only grows it with the state's income from fees and taxes.
* **Taxes**: VAT on invoices, income tax on salaries, transfer tax, a weekly wealth tax above a threshold and a weekly bank ownership fee, each with its own switch and rate, and the tax income.
* **Branch vaults**: what each branch holds (cash, cards, checkbooks, cassettes, forms, keys), the capacities and the central bank's prices. A branch with an empty vault cannot serve that item.
* **Supply orders**: delivery by the central bank (pricier, after a set time) or by the bank's own convoy, and the cargo insurance.
* **Convoys**: crew size, van model, the vehicle key script, crate model, cash per crate, time limits, the crew bonus limit, whether the crew stows the crates by hand and returns the van.

### Market

The open market rows (sales, auctions, offers), the private banks with **Seize** and **State auction**, the market rules (sale tax, opening capital, offer validity, banks per player, minimum sale price, offers for unlisted banks, trading only at the bank exchange) and every change of owner. A row stuck by a restart can be settled here (refund the buyer or close it).

### Offers

The products every bank starts with when it gets an owner, and the state bank's own offer: account, savings, term deposits and loans. Values outside the regulator's limits are shown and moved to the nearest allowed value.

### Roles and pay

The starting roles of a bank, the hierarchy levels owners pick from, and the staff rules: pay period, contract time, maximum staff, minimum duty per period, salary cap, daily bonus limit, waiting time after a rejected application and the framework job synced to bank staff.

### Regulator

The state's rules for every bank: the settlement period, limits of interest, fees and loans, the mandatory reserve, the state guarantee for savings, the profit tax, licence and upkeep fees, the notice period for worse terms, the late penalty and when a loan goes to collection, and after how many unpaid periods a bank is declared insolvent. The list of supervised banks shows each one's treasury, reserve, savings, loans and unpaid periods.

## Server

### General

Primary colour, language, currency symbol and position, number and date format and account number prefix, with a preview. **Limits**: the largest operation, personal accounts per player, the Discord log threshold, the minimum transfer and the daily ATM limit. **Security**: the transfer amount from which a one-time code is needed, request limits and the interaction distance.

### Items

The name of every item the resource uses, with a mark next to any item missing from your inventory, and the card rules: card item required at ATMs, issue fee, active cards per player, wrong PIN tries and the lock time.

### Services

* **Cheques**: checkbook fee, leaves, maximum amount, bounce fee and validity.
* **Deposit boxes**: rent, rekey fee, slots, weight, boxes per branch and per player, and when an unpaid box is sealed.
* **Documents**: statement fee, paper copies of contracts and bills, and how far and how long a held paper is shown.
* **Teller window**: the queue and the `bank_tablet` item.
* **Counter and staff benefits**: the most an owner may give clients served by staff (fee discount, loan rate cut, deposit bonus, free card on the spot, higher cash limit), the bonus per client served, and whether owners may leave a counter to staff only.
* **Conversations with bank staff**: talking to the teller, receptionist and broker before a screen opens, with the camera on their face and the game's voice lines, and how many questions owners may add.
* **Bank in the world**: who stands at the counter after hours, random ped outfits, sounds, ticket machines, the ATM camera, receipts and walk-up, and the alarm while a vault is robbed.

### Billing

* **Units**: the jobs that issue bills (job, name, society account, logo, from which grade they issue and edit the tariff, fines, invoices and custom lines), and grade names as players should see them.
* **Service tablets**: the QF MDT tablets that use the bank's tariff (see [MDT tablets](https://wiki.qfdevelopers.com/scripts/banking-v2/features.md#mdt-tablets)).
* **Bills**: the `/billing` and `/ticketbook` commands, opening bills anywhere, whether invoices must be accepted first, issue distance, amount limits and days to pay.
* **Unpaid bills**: reminders, a late fee per day, a mark in the credit history and automatic payment after some days.
* **Sale contracts**: what can be sold, the title duplicate fee and the items that can never be sold.

### Robberies

**Robbery limits** for the robbery exports (police needed, ATM and vault take, cooldowns, clean or dirty money and its account or item) and **Convoy robbery** (explosive items, police needed, fuse and grab time, bags per player, cooldown).

### Permissions

Add a framework group (`mod`) or an ace (`ace:qf.support`) and tick the modules it can open. The Permissions module itself can only be given to the admin access group from `config/config.lua`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.qfdevelopers.com/scripts/banking-v2/admin-panel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
