What's New in RemitSo: AI Assistant, Sending Forecast and Safer Payouts

RemitSo shipped ten releases between 8 and 21 October 2026, numbered 2026.10.1 to 2026.10.10, plus 2026.09.5 on 7 October. None of them needed downtime. This round-up is for operators who want the short version: what changed, who it helps, and what to plan for. Each release also has a full business note that says what changed, whether it needs downtime and what to do after.

RemitSo, a white label remittance platform, gives every client their own deployment. Each release goes to your staging first, you check it with us, and then we move it to production.

Operators can now ask the console a question in plain words, such as "why is this transfer stuck?", "why can't this customer send?" or "is the partner down, or is it us?", and get an answer from their own data, limited to what they are allowed to see. Personal data typed into a question is removed before it is sent. The assistant can prepare a PDF report on a transfer, a customer or a partner. Each question spends one AI credit. Teams that prefer their own assistant can connect it with a personal token. An optional add-on. Read the full guide.

Every night the Sending Forecast reads each customer's paid transfers from the last six months and works out their rhythm. Tiles show who is overdue, due today, or due within 7, 10 and 30 days, and who has lapsed. Slow senders are listed as occasional rather than guessed at. It is switched off until you ask, and RemitSo scores it against your past transfers first. Read the full guide.

A payout is now failed, and the customer told, only when the payout partner refuses it. A fault on our side, an outage or a timeout stops the payout in Error for your team, with the reason and whose side it is on. Retry asks you to check with the partner first wherever they may hold the money. No payout is left in Processing, and a refused payout update now says why. Read the full guide.

Repeated and single-word names are matched as whole names, partial matches cover whole words only, and names with initials stop matching every listed name sharing one word. The screening ledger opens in well under a second. Re-screening finishes on large books, and each list is checked for freshness on its own. Read the full guide.

• Every fee change previewed before it is saved, and kept with who, what and why.
• Fee windows start and stop by the clock.
• Fees, rates, ways to pay and AML rules can be pinned to one app, so each brand can be priced on its own.
• One transactions list with full filters on every desk; exports build in the background and never time out.
• Bulk payout updates are previewed row by row before anything changes.
• Disabling a payment interface or an app now really stops it.

Read the guide to changing fees, rates and limits safely.

The console home page reports money one payment currency at a time and never converts between them. Revenue includes your fees as well as the exchange margin, and counts delivered transfers only, so it agrees with your books. Transfer counts and amounts sent now count from the day the payment cleared, so they no longer read low while money waits for payout. The highest-risk customers match the Compliance Dashboard.

• Apps can show the window when money should arrive.
• A PDF receipt for any transfer, in the customer's language.
• Search and filter the transfer list.
• Send feedback with a rating, a topic and a message; your team answers it on a Feedback page.
• A changed mobile number must be confirmed by code, which protects the account.
• A customer at a sending limit is told what they can still send, instead of seeing an error.

Some of these need your app team to add a screen. The release notes say which.

• The side menu collapses to icons, and Cmd+K (Ctrl+K on Windows) jumps to any page.
• Twelve reference lists share one page, with spreadsheet import and export and a preview of every change; a glossary explains 23 console terms.
• Same-currency transfers are priced at exactly one and earn only their fees.
• The API documentation was corrected in over thirty places to match what the API does.
• Sign-in pages are lighter, readable in both themes, with an optional animated background.

Every release goes to your staging first, with a business note in plain language. You check it, then it moves to production. Read every release in the release notes, see the admin features and customer app features, or book a demo.