Create Staged Deposit
Defining a new "staged deposit": who owes whom, in what currency, for what total, at what fee. After creating it, you record the actual payments (items) one by one from the batch's own page.
Step by Step
- Choose the obligor ("from account") and the beneficiary ("to account").
- Enter the currency and the total staged amount — this is the cap on the items.
- If a fee has been agreed, enter it; create.
- Now, from the batch page, record each payment as an item until the progress bar fills up.
Fields
| Field | Description |
|---|---|
| From account / to account | The obligor and the beneficiary. |
| Currency and total staged amount | The cap on the sum of the items. |
| Fee amount | The agreed fee on the whole staged deposit (separately for each side). |
| Description | Description of the staged deposit. |
Notes
- Once the sum of the items is complete, the batch becomes "Complete".
- Multi-line notes: press Enter in the description field to start a new line; in the WhatsApp message each line is sent with a bullet (•) — e.g. national ID, receipt terms and payment deadline each on its own line.
Customer Deposited More Than the Commitment? — Overpayment
Sometimes the payer (by mistake or by arrangement) pays in more than the commitment's remaining balance. You don't have to block the entry:
- Record the item with its real amount. The system posts a real transaction up to the remaining commitment cap (the commitment becomes complete) and holds the excess as a separate "Pending" row — this excess hasn't landed in anyone's account yet and isn't a real voucher.
- Next to each excess row are two buttons: Accept and Reject (each excess independent). If the recipient accepted the excess, click "Accept" — a real transaction is posted for the excess and the total commitment amount rises by that much. If they didn't accept it (e.g., it was a walk-in customer's account), click "Reject" — no voucher is posted and it just stays on record.
- In the commitments list, commitments with a pending excess get an "Overpayment" tag and can be found by filtering for it.
Direct, or via Assignment?
If, when you see the customer's request, you already know who you're handing this account to, you can create the staged deposit directly here; otherwise, record a "Deposit request" first and assign it later from there (or from the payment readiness list) — assigning it creates the staged deposit itself and copies over the banking details.
The IBAN field now validates itself: a malformed sheba/IBAN gets an immediate red message and no inquiry is spent; for foreign IBANs, or when the inquiry is off or fails, the bank name is derived from the number itself for a dozen-plus countries (Iran, Türkiye, UAE, Iraq, …) and fills the bank field. Input that is not IBAN-like at all (e.g. a card number) gets no warning.
One bank receipt, several documents (continuing the same receipt)
Sometimes a single receipt must become two documents — like a commitment overpayment confirmed separately. Duplicate tracking codes are normally blocked, but when the second document truly continues the same receipt: confirming a commitment overpayment links it automatically, and in manual entry, when you see the "duplicate code" error, a compact "This continues receipt ..." checkbox appears under the same field; tick it and the second document is saved with the same code, linked to the first. Chained documents count as one receipt in funds verification: changing the status of one changes them all. A code belonging to a different receipt remains blocked.
Per-part fee: in the part form you can record a fee for that specific part (received or paid, with amount and currency). When filled, it replaces the commitment's overall fee for that part; when left empty, the previous behaviour holds: the commitment's overall fee is booked once on the first fee-less part. Overpayments are still recorded without a fee.
Closing a commitment: the header-edit panel has a "Close commitment" button. A closed commitment — even with a remainder — leaves every in-progress list: the account's open-items chip, the inbox receipt suggestions, the dashboard, the WhatsApp card and the night report. The commitment amount and its recorded parts stay untouched and remain visible on the document. You can add a reason when closing (no longer needed, customer cancelled, merged into another commitment), stored with your name and time and shown in the badge tooltip. No new part can be added to a closed commitment; "Reopen commitment" brings everything back. This is also the way to finish a commitment whose only part was cancelled and which cannot be deleted because it has documents. Wrong receiver or payer: while the commitment has a live part, the parties and currency are locked. Once every part is reversed, the parties and currency become editable again in this header panel and the commitment can also be deleted (reversed parts remain as documents; only their link to the commitment is removed).
Destination file (Alipay QR/invoice)
Destinations without an IBAN — an Alipay QR, a remittance invoice — can be attached as a file to the staged deposit itself: on this form, or later from its page while it is open. The "send account number to payer" button then sends that very file with the message as its caption. When the staged deposit is created from an inbox file and you don't pick one, the inbox file is attached automatically. The file is stored in the customer's folder and included in their documents ZIP export. For Alipay destinations also fill "Account/email" and the holder name (Latin + Chinese in the same field); when a file exists, the WhatsApp message uses the separate "assignment with destination file" template.