# How to open and run store credit > Give wholesale customers an open account with a limit and terms, record charges and payments, watch the ageing, and auto-suspend when they fall behind. Canonical page: https://magazamhazir.com/fr/yardim/cari-hesap-kurulumu Menu path in the store admin: Müşteriler > Cari Hesap Available on every plan — no plugin required. Last updated: 2026-09-01 In a wholesale business the goods usually leave now and the money arrives at term. The Store Credit screen holds that whole relationship: each customer's credit limit, payment terms, outstanding balance and movement history. Putting an order on account raises the balance, recording a payment lowers it, and the system decides which money settles which debt — payments are applied to the oldest debt first. ## Avant de commencer - A panel account with permission to manage customers - The credit limit and payment term in days you will grant per customer - If you sell wholesale, setting up customer groups first makes this easier ## Étapes ### 1. Turn store credit on and set the defaults {#adim-1} Open Customers > Store Credit and switch on Store credit enabled under Settings. Default credit limit and Default payment terms (days) are the starting values for every customer; a customer's own setting overrides them. With Allow paying with credit at checkout on, a customer can put all or part of an order on their open account. ### 2. Open an account for a customer {#adim-2} Under Accounts click Open account, pick the customer and enter a Credit limit and Payment terms (days). Leave the terms empty to use the store default. This step is not a formality: approving an account is what allows that customer to take goods on credit. ### 3. Record charges and payments {#adim-3} The Ledger actions menu on an account row holds three operations. Charge records goods taken on credit and is refused if it would exceed the customer's limit; linking an order makes charging it twice impossible. Record payment settles money in — a positive amount reduces the balance owed. Adjust is a manual correction: it is recorded permanently, is not limit-checked, and a reason is required. ### 4. Read the ageing {#adim-4} The tiles across the top total every account into ageing bands: Total outstanding, Not yet due, Overdue, and then 1–30 days, 31–60 days, 61–90 days and 90+ days by how late they are. If a customer's balance goes negative the list shows In credit — meaning you owe them, not the other way round. ### 5. Pull a statement, and know how settlement works {#adim-5} An account's Statement gives you an Opening balance, the movements and a Closing balance for the date range you pick, with each movement typed as Charge, Payment, Adjustment, Write-off or Refund. Export CSV hands it to your accountant. The note under the table matters: payments are applied to the oldest debt first, not to a specific invoice. ### 6. Switch reminders on — in dry run first {#adim-6} Under Payment reminders in Settings, Send due-date reminders emails the customer before a charge falls due. If you are turning it on for the first time, do it with Dry run: it logs what would be sent without emailing anyone. Leave Auto-suspend after (days overdue) empty to never suspend automatically. ### 7. Review new applications {#adim-7} Under Membership approval you choose whether New signups are set to Approve automatically or Review manually. Manual review puts every new signup in the approval queue with a zero limit. In Pending applications, Approve sets their credit limit and terms; if you Reject, the reason you type is included word-for-word in the email sent to the applicant. ## Conseils ### Make exceptions per customer In a customer's own credit settings, anything left unset is inherited from the general settings and shows as General. A field you Override becomes Custom. You can turn paying on account on for a single customer even when it is off store-wide. ### Never charge the same order twice Fill in the Order field when recording a charge. Try to charge the same order again and the panel says it was already charged and adds nothing. The same protection exists in reverse: reversing an order's charge is safe to repeat and can only ever apply once. ### Do not confuse Adjust with Record payment A payment is real money and appears in the statement as Payment. An adjustment is a bookkeeping correction, is not limit-checked, and demands a reason. Outside cases like FX differences or rounding, avoid adjustments — they make a statement harder to read. ## Questions fréquentes ### What happens if a customer orders past their limit? The operation is refused and the panel says it would take the customer past their credit limit. The only ways through are raising the limit or recording a payment to bring the balance down; Adjust must not be used for this, precisely because it is not limit-checked. ### Can I apply a payment to one specific invoice? No. Payments are applied to the oldest debt first (FIFO). That is deliberate: it keeps the ageing table honest. If a payment relates to a particular order, put it in the note — it shows in the statement. ### Can an unapproved customer pay on account? No. No unapproved account may pay on open account, whatever its group — that is a separate rule and is always on. The Only approved members can order setting is a different thing and applies only to wholesale customers in a dealer group; retail customers are unaffected and can still order by card. ### What does a customer see if I suspend their account? A suspended account takes no new charges; the panel says the account is not active. The customer can still browse and pay by card — they just cannot put it on account. You can suspend by hand, or automatically once overdue if you set a day count in the settings.