Nexto
Rial routing & transfers

Deposit Request

Deposit Request

Requests to "deposit into a specific bank account via IBAN" are managed here: a customer has given an IBAN and wants their money sent to that account. The request is recorded, and its payment — all at once or in stages — is carried out and tracked.

When Do You Come to This Page?

  • The customer has sent an IBAN (if they sent it in the WhatsApp group, the Operations inbox itself suggests “Create deposit request” with the IBAN and the account holder's name).
  • You want to see which requests have not been paid in full yet.

Where This Page Fits

  • Record a request: "New deposit request". Each request's page: payment status and related staged deposits.
  • Unfinished deposit requests show up in Reports → Open items.
  • Fee income from deposit requests is shown in Reports → Fee Income, broken out under "Deposit request".

Working With the List

  • The form above the table carries a date range, status, and grouping; the currency (a selector defaulting to "All currencies"), the requester, the amount range, and the text search live in the filter row under the column headers. Excel/PDF export is built with those same active filters.
  • The "Assigned", "Unassigned remainder", "Paid", and "Remaining to pay" columns have a numeric filter and sorting; the "Status" column is sortable only.
  • If no rows are left under the current filters (for example the default “Awaiting allocation” chip), the table no longer says “not registered yet” but that no requests match these filters; the “Show all” link clears every filter and shows all statuses. “No deposit request has been registered yet” appears only when there really are none.

Notes

  • The status filter is a calculated one, so it stays in the form at the top of the page. It defaults to “Awaiting allocation”: open requests whose full amount has not yet been assigned to staged deposits. “Allocated” lists requests whose full amount is assigned to staged deposit(s) and only the parts remain to be paid; once fully paid they move to “Completed”. The status column shows the two states with amber and blue badges. A request with only part of its amount assigned shows an amber “Partially allocated” badge and stays under the “Awaiting allocation” tab until the full amount is assigned.
  • Paying a deposit request uses the Staged Deposit (payment commitment) mechanism: the request's amount is allocated to staged deposits and paid as their parts.

Status Columns

For each request you see five numbers: total amount, assigned, unassigned remainder, paid, and remaining to pay — one glance is enough to know how much of the request hasn't been handed to anyone yet and how much still hasn't been deposited.

Table Filtering and Sorting

  • There is a filter row right under the column headers: in a text column type part of the value, in a numeric column give a "Min" or a range ("100-500" means between the two, "-500" means at most 500), in an option column pick from the list. The filter applies to every record on the server, not just the page you are looking at.
  • Column headers carrying the ⇅ mark sort when you click them: ⇅ neutral, ▲ ascending, ▼ descending.
  • Changing a column filter, the sorting, the page or "per page" happens without reloading the page: only the table body is swapped, so your filters and scroll position stay put. The page address only changes with the filters in the form at the top of the page (date range and grouping).
  • Active filters are kept while you page through the list, and the Excel/PDF export sees exactly the same ones — including the status filter, so finished requests are exported only when they show in the table — with the same columns in the same order as the table; when all rows are in one currency, the export also ends with the table's two total rows, “Total with account” and “Total without account”. To clear one, empty the field or leave the "All" option.
  • On phones each row is a card: the counterparty and amount in large type, a few key details and the action buttons at the bottom; "Show more" opens the rest. Less-used filters are behind "More filters", column filters behind "Column filters", and the round + button at the bottom of the screen creates a new item.
  • On the staged deposit/request page itself, each party’s account name carries Customer stats and Statement icons that open in a new tab.

Document code

Besides its row number, every deposit request has a code written with its family prefix: DRQ12, DRQ403, and so on. The prefix says which form the code belongs to, so a code written on paper or sent in a message is never ambiguous.

Deleting a request

As long as no part has been registered on any allocated staged deposit, the request page shows a Delete request button; deleting also removes its attached staged deposits that have no parts. Once a single part exists, deletion is refused. If the request has assignments, the delete confirmation states their count and total explicitly; to remove just one assignment, delete it from the assignments table rather than deleting the request.

  • Urgent tag: urgent requests get a red badge and row tint, always sit at the top of the list, and come first in readiness allocation. Set or remove the tag when registering or from the request page ("Urgent" button).

Receipts in the requester’s group: send all, reply and ✅

  • On each request page, above “Allocations”, the “📤 Send all receipts to the recipient’s group” button sends the receipts of all staged deposits of this request (in booking-time order) to the requester’s group, with two options: “Separately” (each receipt + a summary message) or “PDF — all in one file with a summary page” (a summary page with the total paid, the remaining deposit and a table of all receipts, then one page per receipt, with the summary as its caption); each receipt’s format follows the “Receipt format sent to the recipient group” setting. The total paid in the summary covers all staged deposits of the request. Payer names are not included in these messages.
  • “Receipts” column and sending history: In the deposit requests list, the “Receipts” column shows whether the receipts of all staged deposits of each request have been sent to the requester’s group: green “✓ 3/3” means all sent, amber “2 not sent”, red “Failed” (the last send failed), blue “Queued”, and “—” means no receipts. The column’s filter (“Has unsent”, “Failed”, “All sent”, “No receipts”) is handy each morning to see what still needs sending. Clicking the badge opens a small panel: the history of each receipt (amount, tracking number, status and the last send — date and time, type “Single receipt”, “All — separately” or “All — one file”, and who sent it; hover to see all previous sends), followed by buttons that send only the unsent receipts: “Separately — n unsent receipts” or “One file — n unsent receipts” (for one receipt: “Send the unsent receipt”). Receipts already sent are never re-sent automatically; if the recipient says they didn’t get them, “🔁 Send all again (one file)” resends everything after a confirmation that shows when they were last sent. After sending from the list you stay on the list with the same filters. The same history appears on the request page under the send-all button, in the collapsible “Receipt sending history”.
  • If the “Your deposit request has entered the payment process” message was sent to the group when the request was registered, the single receipt sent when booking a part, the all-in-one PDF and the summary message are sent as replies to that message, so everything about one request stays under one message. Requests without that message are sent normally.
  • When the full amount of the request has been paid, a ✅ reaction is added to that message automatically; if a payment is reversed and the request is no longer complete, the ✅ is removed.
  • Reply priority: if the request was registered from the customer’s own IBAN message in the inbox, receipts, the combined PDF, the summary message and the “entered the payment process” message itself all reply to that customer message, and the ✅ for full payment lands on it too — the customer sees on their own message which IBAN was paid. If we don’t have the IBAN message (a manual request or one created from a trade document) or the receipt goes to a different group, our “entered the payment process” message is used; if that’s missing too, the receipt is sent without a reply.

Preview before sending to WhatsApp

When you filter the list to one customer with status open / in progress, a “Preview and send to …” button appears next to the row count: it shows that customer's open-items card before sending and sends it to their WhatsApp from here. The card contains all of that customer's open items, not only the rows on the current page.

Total rows, the “Account” column and currency memory

  • When every result of the filter is in one currency (for example, you filtered by currency), the last two rows of the table are totals: “Total with account” and “Total without account”, each with count, total amount, allocated, unallocated, paid and remaining to pay, across the whole filtered result (not just the current page). This shows how much of the balance is still waiting for the customer's account number; clicking a row's title filters the list to those requests. With several currencies these rows are hidden, since adding different currencies is meaningless.
  • The “Account” column: ✓ means an IBAN/destination account or a destination file (Alipay QR) is on record; the amber “No account” badge means none has arrived yet. The column filter is “Yes / No”.
  • The currency you filter by is remembered: next time you open this page the same currency is filtered. Clearing the currency filter or pressing “Clear” forgets it. The memory is per user.

Due badge

A deposit request recorded for a trade's deferred delivery that is still open gets a Due … badge next to its document code: amber until the due date, red after it. Such a request is usually created from the “+ Destination account” button of the obligations card on the statement.

Status tabs: above the table each status has a tab with its count, so the active status is always visible. Any other active filter appears as a chip with × in the “Active filters” row above the table.

Columns and number filters: “Account holder”, “Bank” and “Unallocated” are hidden by default and can be turned on from the “View” menu. In the filter box of a number column, one number means a minimum and “100–500” means a range.

Phone and going back: On the phone card, “Unassigned balance” and the date share one line and the bank sits with the other details. When you return with the browser's back button, the list and the request page refresh themselves, unless you have typed something in a form and not sent it.

Saving twice: Sending the same form again creates nothing and takes you to the saved request. A new form with the same amount saves normally, with only the yellow warning if the IBAN repeats. The same assignment is not sent to WhatsApp again within one minute.

This guide comes straight from the in-app help and refreshes with every update. Video tutorials · Free demo
Chat on WhatsApp