Payment Types & CashBook Hierarchy¶
Purpose¶
This reference catalogs all payment rails, cashbook types, and ledger account hierarchies used for monetary transactions in Cashy-Hub.
1. Payment Rail Architecture (CashBookType)¶
Cashy-Hub distinguishes between store-level cash accounts and corporate centralized accounts:
graph TD
Trans["Monetary Transaction"] --> Type{"CashBook Type"}
subgraph StoreLevel ["Shop Level (Physical Custody)"]
Type -->|CASH| CashDrawer["CASH: Counter Till (Kassa) & Safe (Reserve)"]
Type -->|CARD| CardTerminal["CARD: In-Store POS Card Terminal"]
end
subgraph CompanyLevel ["Company Level (Centralized Banking)"]
Type -->|BANK| BankAccount["BANK: Corporate Bank Account (SEPA Transfers)"]
Type -->|UNZER| UnzerGateway["UNZER: Online Payment Gateway & Web Portal"]
Type -->|PAYPAL| PayPalAccount["PAYPAL: Corporate Digital Wallet"]
end
CashBook Type Classification:¶
CASH(Shop Level):- Manages physical banknote and coin transactions at the branch counter.
- Divided during daily closing into
KASSA(counter till float) andRESERVE(vault safe reserve). CARD(Shop Level):- Card transactions processed via physical POS card terminals at the counter.
- Reconciled against electronic terminal end-of-day batch settlement slips (Kassenschnitt).
BANK(Company Level):- Bank wire transfers and SEPA credit disbursements.
UNZER(Company Level):- Integrated digital payment service provider for borrower online extensions.
PAYPAL(Company Level):- Digital disbursements and purchase deal acquisitions.
2. Mandatory CashBook Validation Rules¶
Whenever a transaction moves funds at the branch counter: - Deal Verification / Payout: The operator must bind the disbursement voucher to a specific CashBook. - Deal Extension: Confirming an extension requires binding fee collection to an active store CashBook. - Deal Payback: Confirming collateral redemption requires selecting the receiving CashBook.