What's New In RemitSo

The console dashboard now counts a transfer from the day the customer's payment cleared, so transfer counts and amounts sent no longer read low while money waits between payment and payout. Revenue still counts delivered transfers only, so it keeps agreeing with the books. No downtime.

• Transfers paid for, counted from the day the payment clearedThis month so far, Transfers and volume and Where the money went now include transfers in review, on hold or waiting for payout. Your team sees the real day's business, not just what has already landed.
• Revenue still counts deliveries onlyRevenue is counted on the day a transfer is delivered, so the dashboard and your books keep telling the same story. The card now labels its figures "Transfers paid for", "Sent" and "Revenue on deliveries".
• Where the money went shows payout amountsEach destination shows the amount to be paid out, including transfers not paid out yet.
• Sending Forecast reads rhythms more carefullyA customer who sends less often than about every 35 days is listed as occasional, with no expected day. A high-confidence prediction needs at least six sending days behind it and a medium one four, and a monthly pay-day is read from the last four months first.

Operators can ask an AI Assistant inside the console why a transfer is stuck, why a customer cannot send, or whose side a failure is on, and have it prepare a PDF report. A new Sending Forecast page shows which customers are likely to send next. Both are switched on per installation. No downtime.

• Ask the AI Assistant from the consolePlain questions get answers from your own data, limited to what the asking operator may see. Email addresses, phone numbers and long numbers typed into a question are removed before it is sent. An optional add-on, switched on with a licence.
• PDF reportsA transfer diagnosis, a customer's standing or a payout partner's health, built by the console from its own data with no personal data in it. Every download is in the audit log.
• AI creditsEach question spends one credit and a question that fails spends none. The balance, top-ups and spends sit on one System Utilities card, and an alert warns once a day when credits run low.
• Rate every answerAnswers can be copied and rated, and a poor rating asks what was wrong, so the assistant keeps improving on the questions your team really asks.
• Sending ForecastRead every night from each customer's paid transfers over the last six months: how often they send, how regularly, and whether on the same date each month. Tiles count who is overdue, due today, due within 7, 10 and 30 days, and who has lapsed. Switched on by RemitSo after scoring it against your past transfers.
• API documentation matches the APIOver thirty statements app developers build from were corrected. Nothing the API does has changed.
• Sign-in pages with an animated backgroundA slowly turning galaxy or a field of stars, chosen per console. On a device set to reduce motion, it stands still.

Super administrators can move a payout to any step again, and a refused update now says why. Identity checks a customer passed are recorded even where a document type has been removed. Sign-in pages load faster. No downtime.

• A refused payout update explains itselfThe reason appears on the form above its buttons, where before nothing happened.
• Identity checks recorded after a document type is removedA customer verified at a level a removed document type still carried now gets their document, so their transfer stops asking for one.
• Lighter, clearer sign-in pagesEach console shows its own, much smaller background, and every sign-in, password and two-step page reads clearly in both themes.
• Dialogs open above the top barA tall dialog no longer slides under the bar with its title hidden.

Sanction screening now checks every list for freshness on its own, so a list that stops updating is named the day it falls behind. The side menu collapses to icons and any page is a keystroke away. No downtime.

• Per-list freshnessThe daily check compares each list's own date with how long that list normally goes without an update. The out-of-date alert names the late list, and the Sanction Lists page shows each list's verdict.
• A planned signing-key changeThe platform was made ready to move the published sanction lists to a new signing key, as planned maintenance and not because of any compromise.
• Collapse the menu, jump to any pageA button beside the logo shrinks the menu to icons. Jump to, or Cmd+K (Ctrl+K on Windows), lists every page you may open.
• Easier navigationHover and the current page look different, the three transaction lists sit under Transactions, and the top bar names the page you are on. On a phone there is one menu button and a working Sign Out.

Fees are set, reviewed and charged from one place, with every change reviewed before it is saved and kept as history. The transactions area is one list with full filters on every desk, and exports and bulk payout updates build in the background.

• Every fee change reviewed and keptA change to a rule's slabs or a payment method's terms shows what customers would pay at each step before it is saved. Every change records who made it, what it was, what it became and why.
• Fee windows run by the clockA rule or slab scheduled for a date starts and stops on that date, instead of waiting for an unrelated save.
• Payment method charges and limits at checkoutA method's own charge is added to the customer's total, and an amount the method does not accept is refused with a message naming the limit.
• One transactions listFull filters on every desk, up to 500 rows a page, and payout actions only where they belong.
• Exports in the backgroundAn export carries the list's filters, masks values exactly as the screen does for that role, arrives from the Export button and no longer times out.
• Bulk payout updates, previewed row by rowUpload a file of up to 500 transfers with their new payout status. Every row shows what it would do or why it is refused before anything changes. A payout the partner may still hold is refused rather than updated.
• Brands with their own fees, rates and limitsA fee rule, an exchange rate rule, a way to pay, a receiving account and an AML rule can each be pinned to one app, so a brand running as its own app can be priced and controlled on its own.
• Disabling really stopsDisabling a payment interface or an app now stops it, not just how it looks in the console.
• Quotes refuse instead of quietly adjustingA currency, payout method, partner or amount that is not offered is refused, naming the field, instead of being priced on something else.
• Fewer false sanction matches on initialsA name with an initial no longer matches every listed name sharing its one full word, and re-screening no longer stalls on a very long listed name. Lists load only when their signature verifies.

Payouts are no longer failed in front of a customer unless the payout partner itself refuses them, and none is left stuck in Processing. Customers can send feedback from the app, and a changed mobile number must be confirmed.

• Faults on our side stop for staff, not the customerA refused credential, a partner outage, a timeout or an answer that could not be read now stops the payout in Error, with the reason and whose side the fault was on. The customer is not told it failed.
• No payout stuck in ProcessingAn unrecognised partner status stops the payout in Error and raises the payout error alert. It is not sent again until someone has checked with the partner, so nobody is paid twice.
• The partner's own reason on a refused accountA recipient account refused at the partner's name check shows the partner's reason, instead of a generic failure.
• Re-screening finishes on large booksNightly sanction re-screening now finishes on large customer books and finds everyone screening would match.
• Customer feedback from the appCustomers give a rating from 1 to 5, a topic and a message. Staff filter by topic, rating and whether it was answered, and mark each one answered.
• A changed mobile number must be confirmedA different number leaves the customer unverified and sends a code to it, so a verified customer can no longer sit on a number nobody confirmed.
• Clear messages at a sending limitA customer who has used up their limit sees what they can still send, instead of an error.

The console home page now reports money one payment currency at a time, revenue includes the fees charged as well as the exchange margin, and the highest-risk customers match the Compliance Dashboard. No downtime, and every role keeps the figures it could see.

• Every currency you take payment inChoose the currency at the top of the page and the browser remembers it. Amounts are never converted from one currency into another, and figures refresh every five minutes.
• Revenue includes your feesRevenue is the fee, less any coupon discount, plus the margin on the exchange rate, valued the way your books value it.
• Real risk scoresThe highest-risk customers on the dashboard show the same customers and scores as the Compliance Dashboard.
• A permission per sectionEight dashboard permissions instead of seventeen, so a role can be given the business figures without the risk sections, or the other way round.

Sanction screening stops flagging every listed name that shares a word with a repeated or single-word customer name, and the screening ledger opens in well under a second. Twelve reference lists share one page with spreadsheet import and export, and a glossary explains the console's terms.

• Whole-name matchingA repeated or single-word name is matched as a whole, and a partial match covers whole words only. Expect far fewer hits to clear by hand.
• A fast screening ledgerIt opens in well under a second instead of up to a minute on a busy installation.
• Reference data on one pagePurposes, relationships, occupations, sources of funds and eight more lists export to a spreadsheet and import back, with a preview of every change before anything is saved. An import never deletes anything.
• A real glossary23 console terms explained, with a search and a link to the page each belongs to.
• For customers: when money will arrive, receipts and searchCustomer apps can show the window the money should arrive in, download a PDF receipt in the customer's language, and search and filter the transfer list.
• Middle names on documentsAdding, editing and approving a document offers an optional middle name, and names from a proof of identity land in the right fields.
• Same-currency transfers priced at exactly oneA transfer paid out in the currency it is paid in needs no exchange rate, so it earns only its fees.

For a payout partner that sends no notifications, paid payouts show as paid within minutes again: the platform asks every five minutes for the first 15 hours, then less often. No downtime.

• Status checks paced to how payouts really settleFrequent checks while a payout is new cover about 19 in 20 bank transfers. A cash pickup is still checked for its full 30 days.
• Company recipients sent under the right ID typeA partner-specific ID mapping was corrected, and refused company payouts can be retried from the console.

Recipients identified by passport are paid on a partner that had been refusing them, the sign-up email explains its code again, and transfer emails name your business instead of a placeholder. No downtime.

• ID type follows the ID numberFor one payout partner, the recipient's ID type now follows the first letter of the ID number, so passport holders are paid.
• Customer emails read as intendedThe sign-up email tells customers to use the code below, in English and Spanish, and transfer emails name your business.
• AML tiers rearranged in one saveMoving one tier past another now saves as reviewed.

Operators can connect their own AI assistant to the console and ask about a transfer or a customer. Customers are told a payout failed only when the partner refused it, every payout is chased on a schedule that fits it, and sign-in and code requests are rate-limited.

• AI Assistant AccessA staff member connects their own assistant, for example Claude, with a token issued and revoked under AI Assistant Access. It sees only what that person could open in the console, never receives personal data, and says whose side a failure was on. An optional add-on.
• Every payout chased on a fitting scheduleA payout is asked about often while it is new and less often as it ages. One the partner stops answering about appears on Scout, and is never cancelled blindly.
• Never paid out before the payment clearsA payout is never sent for a transfer whose payment has not cleared, however it reached Available for Payout.
• Rate limits on sign-in and codesSign-in, sign-up, verification codes and password resets are rate-limited in the apps and the console, and codes can no longer be guessed.
• High-risk countries from published listsEach listing says who published it and how serious it is. Watched names, email addresses, domains and countries share one page, import and export as files, and can expire.
• A page for every outside providerWhether it is fully configured, what uses it and its calls in the last hour, with every secret masked.
• Broadcast to a chosen audienceThe console shows how many customers will receive a message before it is saved.
• Exact payout amountsRecipients receive the exact amount quoted, decimals included.

A new generation of the customer-facing web app, rebuilt from the ground up on modern foundations and built to be configured per tenant from the start.

• A Modern App ShellEvery API call now goes through one consistent client, with a dead session renewed automatically, a wrong credential reported clearly, and framework-level error messages never reaching a customer.
• Sign-In, VerifiedA rebuilt sign-in flow carries a customer through multi-factor verification and back to exactly where they were, with a resend option offered only when a code can actually be resent.
• Sign-Up and Onboarding, Configurable Per TenantA new sign-up and onboarding journey checks password rules as a customer types, captures consent to the right terms, and asks for only the profile fields each tenant actually requires.
• Account Verification, RebuiltA new verification flow shows exactly which documents are still owed, accepts an upload or steps a customer through a guided provider session, and shows a customer only the review comment meant for them — never a provider's internal note.

A significant rework of the interactive Platform Map introduced earlier this year, making it clearer to read, smoother to explore, and noticeably faster.

• Labels That Stay ReadableLabels are now tiered by relevance and placed to avoid overlapping, so the map stays legible at every zoom level instead of crowding together.
• A Clearer Station ViewSelecting a part of the platform now opens a focused panel that leads with a plain-language summary, with the technical detail available but tucked away.
• Built-In LayersSwitch between the transfer flow, supporting systems, external partners, and exceptions — with your chosen view remembered for next time.
• Meaningfully FasterRendering work was cut by more than a third, with no drop in frame rate.
• Respects Reduced MotionBackground animation now honours a viewer's reduced-motion preference instead of always animating.

Two reliability fixes closing gaps that could leave a payout cancellation silently stuck, or let sensitive details slip into an integration's own logs.

• Payout Cancellation, FixedCancelling a payout from the console now completes correctly end to end, instead of silently failing to recognise a partner's response.
• Every Status RecognisedA payout partner reporting that a transfer is still in progress is now recognised correctly, instead of leaving the payout stuck with no way to cancel it.
• Credentials and Personal Details Fully Masked in LogsOutbound integration logs now redact sensitive fields correctly across every message format, closing a gap where credentials and personal details nested inside a document could appear in the log unmasked.

A customer who starts paying for a transfer and changes their mind is no longer stuck. Cancelling a payment now releases it cleanly, wherever it's held, so a new attempt can be made immediately.

• Cancel From the AppA customer can cancel a payment that's waiting to complete directly from the app, without contacting support. The transfer itself stays open, ready for a new payment.
• Cancel From the ConsoleOperators can cancel a customer's waiting payment from the transfer page, with the action fully audited.
• Pay Again, ImmediatelyOnce a payment is cancelled, the customer can try again straight away — no waiting for an old attempt to time out first.
• Clean Release at the ProviderCancelling now tells the payment provider, not just our own records, so the customer's account is genuinely freed up rather than still being held behind the scenes.
• Cancellation Only Where It's Actually SafeCancellation is offered only where a payment can truly be withdrawn before money moves, or where nothing was ever held with a provider in the first place — preventing a cancelled payment from accidentally still going through.

Third-party integrations are easier to find, understand, and manage safely, with a clear view of what's configured, what's missing, and where each provider is actually used.

• Integrations by CategoryProviders are now grouped into category cards, with each category page listing its providers alongside their configuration status at a glance.
• A Clear Provider PageEvery provider has its own page showing its configuration, usage, and health — with every secret safely masked.
• Safer Provider ManagementA provider that's actively in use can no longer be deleted by accident, and removing one now requires typing its name to confirm. A previously removed provider code can be added again cleanly.

The watched names, email, domain, and high-risk country lists that power risk screening have been rebuilt on faster, more accurate matching — with one shared console, bulk import and export, and a clear audit trail.

• Graded High-Risk CountriesCountries are now listed from authoritative sources (FATF and the EU), each with its own publisher, grade, and reason, rather than a single hand-maintained on/off list.
• Smarter Name MatchingWatched names are now matched using the same proven engine behind sanctions screening, replacing a slow, less accurate lookup — with existing customers automatically re-checked whenever a name is added to the list.
• Email and Domain Matching That Catches SubdomainsWatched email domains now correctly catch their subdomains, with normalisation so near-identical addresses can't slip through formatting differences.
• One Console for Every ListAll risk reference lists now share a single, consistent console page, with CSV import and export available across all of them.
• Full Audit TrailEvery change to a risk reference list — adding, editing, or switching a country on or off — is now recorded for audit.

A platform-wide pass on sign-in and verification brings consistent rate limiting to every login, password reset, and verification code across both the console and the customer-facing API.

• Consistent Rate Limiting EverywhereSign-in, password reset, MFA, and verification codes are now rate-limited consistently across the console and the Client API — closing gaps that previously let these be attempted without limit.
• Verification Codes, Properly GuardedVerification codes now have a limited number of attempts before expiring, and are drawn from the full range of possible codes, making them significantly harder to guess.
• Real Caller Identity, Not a Spoofable HeaderRate limiting is now enforced against a caller's real network address rather than a value a request could set itself, closing a gap that let the limits be bypassed entirely.
• Clear, Localised RefusalsA rate-limited request now receives a clear, translated explanation and a wait time, instead of a bare technical error.

Sanction lists are published every day and signed, and every installation checks the signature before loading them. Operators are warned when an exchange rate stops moving or pricing has not been reviewed, and customers can cancel a bank-transfer payment they no longer mean to make.

• Signed, daily sanction listsNew listings no longer wait to be published by hand, and each version is checked as genuine before it loads.
• Stale pricing warningsA standard rate that stops moving raises an alert, and fees left unreviewed for too long raise a prompt. Scout shows both.
• Customers can cancel an unpaid bank transferFrom the app, or an operator from the console, wherever the payment provider can be told.
• New customers graduate to standard pricingCustomers move from the New group to Default after their first completed transfer.

Sanction lists load themselves every night from one published dataset, everyone on the books is re-screened whenever they change, and an officer can confirm a match rather than only dismiss it. AML rules move to one page, every change is reviewed before saving and kept as history, and a rule set moves between installations as a file.

• Nightly lists, everyone re-screenedCustomers, recipients, account holders and staff are re-screened after each nightly load. A hit already ruled "not this person" stays ruled unless somebody revokes it.
• Confirm a match, undo any rulingConfirming a match asks for a reason and raises an alert. Nothing is blocked automatically: blocking, holding and reporting stay decisions a person takes.
• Sanction EntitiesSearch and read every loaded entry, everyone on your platform who matched it and the rulings made.
• AML rules on one page, with historyPolicies, tiers and documents change together behind a review that says what each change means for customers. Every change is kept with who made it and what it was before.
• Rule sets as filesExport AML rules and load them into another installation. An import never removes anything and nothing is written until a typed phrase confirms the preview.
• Clear limit messages for customersA customer who reaches a sending limit is told so, instead of being told to contact support, and their limit card shows the limits that really apply.

Provide a centralized, live-connected reference for the RemitSo Client API used by mobile apps and the web client, covering authentication, customer onboarding, transfers, payments, payouts, wallets, exchange rates, and supporting client functionality.

• Live API ReferenceThe API documentation is served for the /client/v1 Client API and uses the deployed route table as its source for HTTP methods, paths, and authentication tiers, keeping the endpoint catalogue aligned with the deployed API.
• Client API CoverageDocument the complete customer-facing API flow, including registration and authentication, KYC onboarding and document verification, customer profiles and tasks, corridor pricing and transaction quotes, recipient management, checkout and confirmation, payments and statements, transactions and tracking, promotion coupons, exchange rates and alerts, payment and payout channels, device management, wallet enrolment, balances, and spending, plus client utilities and reference data.
• Authentication DocumentationClearly document the three authentication tiers used across the API: Public, App Token, and Session Token. The documentation also covers MFA requirements, device-bound authentication, PIN and biometric enrolment, and push-token registration.
• Developer-Specific GuidanceProvide guidance for different API users, including mobile engineers, web SPA engineers, QA teams, and support teams, with relevant information about authentication flows, request behaviour, state codes, errors, and response fields.
• Endpoint ReferenceGroup endpoints by functional area, with each endpoint documenting the HTTP method and path, authentication tier, request parameters, response fields and types, enum values, programmable vs. free-text fields, behavioural notes, example payloads, and endpoint status such as Deprecated, Undocumented, or Route Removed where applicable.
• API Integration WorkflowDocument the recommended customer journey from initial application access through a completed transfer: obtain application access, register or sign in, complete the customer profile, discover payment and payout corridors, price and persist a transfer quote, select or create a recipient, confirm and pay, and track and manage the transaction.
• Error Handling and API SemanticsProvide centralized documentation for API status codes, failure headers, authentication behaviour, state codes, and response semantics so engineering, QA, and support teams can consistently interpret API responses.
• API TerminologyInclude a shared glossary defining core Client API concepts such as App Token, Session Token, MFA, Corridor, Quote, Transaction, Payment, Payout, Recipient, Payout Method, Payout Channel, Delivery Option, Purpose, CRN, and Programmable vs. Free Text fields.
• Documentation AccuracyKeep the endpoint catalogue synchronized with the deployed route table while allowing engineering to curate descriptions, parameters, response details, notes, and examples alongside API changes.

An optional add-on. Everything a supervisor asks about staff training lives here: what people must complete, who must complete it, how often, and the signed record that they did. Write the material, decide who it is for, and the platform assigns it, reminds people, and keeps the evidence.

• MaterialsWrite the training itself: text, documents, videos and the quiz at the end. Each published version is frozen so the record always shows what a person read.
• AssignmentsDecide which material is required of which audience, how long people have, and how often it repeats. Assigning enrols the audience straight away.
• AudiencesName who gets trained: a department, a role, a location, everyone, or named people, with anyone left out recorded with a reason. New hires are picked up automatically.
• ReviewsWritten quiz answers are marked by a person. Read each answer against the model answer and award the points; the attempt decides itself once every answer is marked.
• Sign-offPassed training waits here for the compliance officer. Signing writes the permanent record a supervisor is shown; several can be signed at once.
• ReportsWho has done what, who is overdue, and one person's full history, with the signed records available as a file for a supervisor.
• CategoriesThe headings materials are filed under, such as anti-money laundering, sanctions or data protection.

Bring accounting records and wallet-service controls into one place, with balanced journal entries, controlled wallet availability, and versioned customer terms.

• Chart of AccountsView every account maintained by the business and its current balance, with access to the underlying entries that produced each balance.
• Journal ManagementView all accounting postings in one place, with the newest entries first and the underlying debit and credit lines available for review. Manual accounting corrections can also be posted directly from the journals.
• Balanced Multi-Currency JournalsPost manual corrections and adjustments by entering both sides of the accounting entry. Debits and credits must balance separately for each currency, with no automatic currency conversion used to make an entry balance.
• Permanent Accounting RecordsOnce a journal is posted, it cannot be edited or deleted. If a correction is required, it must be made through a new reversing entry, keeping both the original and correction visible in the books.
• Controlled Journal PostingManual journals require a description explaining the purpose of the entry, detailed entry lines, account, debit or credit side, currency, amount, and memo. A deliberate confirmation step is required before the journal is permanently posted.
• Wallet Country AvailabilityControl where the wallet service is offered by country. Enabling or disabling wallet availability is recorded as a dated decision with its history preserved.
• Existing Wallet ProtectionTurning wallet availability off prevents new wallet enrolments without affecting existing wallets, ensuring that changing country availability does not remove or alter existing stored-value accounts.
• Versioned Wallet TermsCreate and publish wallet terms separately for each country and language. Every published version is permanently preserved and cannot be edited or removed after publication.
• Exact Customer Acceptance RecordsCustomer acceptances remain linked to the exact version of the wallet terms that was published, preserving the text customers agreed to.
• Controlled Terms UpdatesChanges to wallet terms require publishing a new version rather than editing an existing one. This maintains a complete version history of the terms presented to customers.
• Customer Re-Acceptance ControlsWhen a new terms version requires existing subscribers to accept it, their wallets can be paused until they provide the new acceptance. During this period, wallet activity such as loads, spending, and adding new value is held.
• Country and Language SupportWallet terms can be published for individual countries and languages, with customers served their available language version and English used where a local-language version has not been published.

Give different customer groups, platforms, payment routes, payout destinations, methods, or partners their own exchange rates while keeping the standard rate for everyone outside the rule.

• Standard Exchange Rate VisibilityView the current standard exchange rate for every supported currency pair, including the buy rate, sell rate, rate source, and information about who last changed it. The standard-rate page provides visibility without directly changing rates.
• Targeted Exchange Rate RulesCreate rules that apply a special exchange rate to specific transaction criteria, including customer groups, platforms, payment currencies, payment locations, payout countries, payout currencies, payout methods, and payout partners.
• Flexible Rule TargetingA rule can combine multiple criteria to precisely define which transfers receive a particular rate. Criteria can be left as Any when the rule should apply broadly.
• Route-Aware Rule OptionsOnly options that correspond to routes actually operated on the platform are available when configuring a rule, helping prevent rules from being created for routes that cannot match a transfer.
• Rule PriorityWhen multiple rules could apply to the same transfer, the more specific rule takes precedence, allowing broad rules and more targeted exceptions to operate together.
• Scheduled Rate RulesSet a start date for a rule so that the special rate begins automatically at the required time. An end date can also be configured, with the rule remaining active through its specified final day.
• Controlled Rate AssignmentCreating a rule defines who the rule applies to, but does not immediately change their quoted rate. The exchange rate provided by the rule is configured separately on the rule itself.
• Rule Visibility and ManagementView active and scheduled exchange rate rules from a central list, including which rules are currently running, which are waiting for their start date, and how many operating routes each rule currently covers.
• Rule DocumentationAdd a name and optional internal note to each rule, allowing teams to record why the rule exists and retain the business context behind the pricing decision for future reference.

Organise staff into departments and assign clear ownership for required training, giving department heads visibility when team members fall behind.

• Department ManagementCreate departments to reflect how staff are organised within the business. Each department can have its own name and description to make it easy for administrators to identify and manage teams.
• Department HeadsAssign a head of department who is notified when someone in their department becomes overdue on required training.
• Training AccountabilityUse department membership to determine who must complete required training, making it easier to manage training requirements across different parts of the organisation.
• Persistent Department HistoryDepartments can be switched off without removing their members or historical information, preserving organisational and training history while preventing the department from continuing as an active organisational unit.

Generate the AUSTRAC IFTI-E (v1.0) report directly from transfer data in RemitSo, with the required reporting scope, fixed report structure, completeness checks, and a record of every report produced.

• AUSTRAC IFTI-E Report GenerationProduce an AUSTRAC IFTI-E v1.0 report for a selected reporting period using transfers already recorded on the platform.
• Defined AUSTRAC Reporting ScopeRemitSo determines which transfers fall within the AUSTRAC IFTI-E report. A transfer becomes reportable once its money has been received and the instruction has been accepted. It remains reportable even if the payout later fails or is reversed. Cancelled transfers and transfers still awaiting payment are excluded.
• AUSTRAC-Specific DataThe generated report contains the information required for the AUSTRAC IFTI-E report without adding unrelated platform data such as agent references, transfer status, exchange rates, or payout partner references.
• Report Completeness CheckEvery AUSTRAC IFTI-E report run is checked against the transfers that were within scope for that reporting period. Operators can therefore see whether any reportable transfers were missed before lodging the report.
• Excel and CSV ExportGenerate the AUSTRAC IFTI-E report in either Excel workbook (.xlsx) or CSV (.csv) format for downstream use and submission.
• Saved AUSTRAC Report ConfigurationSave the AUSTRAC report configuration as a named report. The saved configuration retains the report definition, columns, and format, while the reporting period can be selected each time the report is run.
• Consistent Report StructureEach run of a saved AUSTRAC report keeps the same columns in the same order, including periods where some fields contain no data. This ensures the report structure does not change between reporting periods.
• AUSTRAC Report HistoryEvery generated AUSTRAC IFTI-E report is retained with its reporting period, status, completeness result, producer, and production timestamp, providing a record of reports produced for submission.
• Download the Generated ReportOnce the report is produced, operators can download the completed AUSTRAC IFTI-E file directly from RemitSo.

Bring everything that needs an operator’s attention into one place — from transfers and payouts to compliance, payments and system health.

• Centralized Operational VisibilityScout gathers action-required items from across the platform into a single operational view, so operators can quickly see what is waiting and go directly to where it needs to be handled.
• Role-Based Action QueuesOperators only see the groups and actions they have permission to work on. This keeps the operational view focused on the tasks relevant to each role.
• Transfers Needing ActionMonitor transfers that are waiting for an operator because of missing documents, compliance decisions, currency conversion, payout release, failed payouts, holds, or other intervention points.
• Payouts Needing ActionSurface payout issues that require intervention, including failed reversals, payouts stranded before dispatch, payouts left in error, and payouts that have remained with a partner longer than expected.
• Payments Needing ActionTrack incoming payments that require attention, including payments awaiting a provider response, payments where automated polling has stopped, and failed transfer refunds.
• Compliance Decisions in One ViewBring compliance work into the same operational workflow, including screening hits awaiting decisions, customers exceeding risk thresholds, customer and recipient documents requiring review, expiring or expired documents, and suspicious activity reports awaiting review.
• System Health MonitoringIdentify operational issues affecting the platform itself, including failed background jobs, unapplied provider messages, failing partner API calls, automatically stopped rate feeds, and active maintenance windows.
• Automatic MeasurementsEvery operational figure is measured automatically at regular intervals and shows when it was last measured, giving operators a current view of what is waiting without requiring manual checking across multiple areas of the platform.
• Direct Action From ScoutEach actionable figure links directly to the relevant operational screen, allowing teams to move from identifying an issue to handling it without searching through the platform.

Put the platform into a controlled maintenance state during upgrades — without taking customers offline or leaving background processing to guesswork.

• Operator-Controlled Maintenance WindowsA maintenance window now holds until an operator explicitly lifts it. The time entered when opening a window is treated as guidance for customer messaging, not a deadline — so an upgrade that runs long no longer has service resume underneath it unannounced.
• Background Job SuspensionTwenty of the platform's own scheduled routines — chasing payment and payout results, closing unpaid transfers on their deadline, wallet expiry sweeps, exchange-rate feeds — now pause automatically for the duration of a window and resume exactly where they left off once it lifts.
• Full Payment-Path CoverageMaintenance windows now extend across every way money moves on the platform, not a partial set of endpoints.
• Advance SchedulingMaintenance windows can be scheduled ahead of time instead of being opened at the moment of deployment.
• Pre-Upgrade Readiness CheckA new readiness check reports what a window is holding and how much work is still in flight — payments awaiting a provider answer, payouts already sent, unprocessed provider messages — so an upgrade can begin on evidence instead of a guess.
• Customer Wait-Time MessagingCustomers affected by a maintenance window can now be told how long they have to complete a payment, and shown the payment partner's own terms while they wait.

A first-class, double-entry accounting engine now sits under the platform — the financial system of record that wallets, payouts, and settlement all post against.

• Posting Engine for the Remittance LifecycleEvery stage of a transfer's lifecycle — funds in, fees, FX, payout, refund and reversal — now generates a proper double-entry posting, rather than balances being inferred after the fact.
• The BooksA full chart of accounts and general ledger now underpins the platform, giving every deployment an authoritative set of books rather than derived reporting views.
• Unified Accounting ConsoleAdministration of the ledger, postings, and financial reporting has been brought into a single console entry point, replacing several previously scattered screens.
• Settlement-Aware Payout PostingPayout postings to the ledger now reflect what the partner actually debited, rather than an assumed figure.
• Legacy Build RetiredThe earlier, pre-ledger accounting build has been retired now that the new engine is live.

Building on the Wallet Programme Foundation introduced this cycle, and running on top of the new Accounting engine, stored-value wallets are now feature-complete and verified live end-to-end.

• Verified-Identity Deposit AccountsWallet funding now requires a verified identity, and a deposit account is provisioned automatically the moment verification completes.
• Local Payment Identifier DisplayWallet deposit accounts now display a local payment identifier alongside the routing/branch code, matching how customers expect to see their own account details.
• Reliable Deposit ConfirmationDeposit confirmation now fails loudly if webhook verification cannot be completed, rather than silently dropping the notification — closing a gap where a funded wallet could otherwise go uncredited without anyone noticing.
• Plain-Language Wallet StatementsWallet statement line items are now written in plain customer language instead of internal ledger terminology.
• Wallet Balance in the Accounting HubWallet administration now lives inside the same unified accounting console introduced above, rather than as a separate screen.
• Funding Reconciliation & NotificationsWallet funding now reconciles automatically against provider records, and customers receive a notification the moment their funding clears.

A cross-cutting reliability pass so every payment gateway on the platform behaves the same, safe way — regardless of what its underlying provider actually does.

• Universal Payment RecordingEvery way a customer can pay into their account is now captured and recorded consistently across gateways.
• Open Banking Completion AccuracyOpen banking payments now complete only once the funds have actually arrived, rather than on an earlier provisional signal.
• Retry Protection Against Double ChargesA retry can no longer prompt a customer to pay twice for the same attempt.
• Payment Outcome HandlingThe platform now correctly acts on the full range of outcome callbacks a payment provider can send, rather than a limited subset.
• Card Gateway Safety Net ParityCard payments now carry the same duplicate-protection and reconciliation safety net already applied to every other payment method.
• Bank Transfer Crediting AccuracyCustomers paying by ordinary bank transfer are now credited correctly and consistently.
• Payout Provider Authority ConsolidationEach company's payout provider configuration now has a single, authoritative source of truth instead of records that could drift apart.

Strengthened identity verification workflows, provider integrations, and document handling for more reliable onboarding and compliance operations.

• Resume Incomplete VerificationsCustomers can now resume an identity verification they'd already started, instead of being forced to begin again from scratch.
• Provider Request/Response Audit TrailEvery request sent to an identity verification provider, and the answer received, is now logged for audit purposes — with the record itself hardened so it no longer holds readable personal data.
• Verification Session CleanupIdentity verification sessions no longer leave orphaned state behind once they complete.
• Provider Callback ReliabilityA batch of provider-integration fixes: callbacks are now authenticated before being trusted, decline reasons are preserved accurately, a repeated provider message can no longer create a duplicate customer document, and a refused callback is no longer misreported in a way that causes the provider to retry it indefinitely.
• KYC Document Desk RewriteThe customer- and recipient-facing KYC document review screens have been rewritten.
• Document Requirement Recalculation SafeguardsRecalculating a transaction's document requirements now also adds any newly-required documents, and refuses to run once a transaction is already over its limit.
• Document Freshness Re-VerificationA transfer now automatically reverts to requesting documents if the document it relied on stops being valid in the meantime.

A new, unified compliance dashboard bringing together the views a compliance team needs in one place.

• Executive Compliance OverviewA single summary view across the compliance programme.
• Customer Due Diligence (CDD/KYC) ViewCustomer-level due-diligence status at a glance.
• Sanctions Screening ViewScreening results and match history in one place.
• Transaction Monitoring ViewFlagged-transaction activity surfaced for review.
• AML Risk OverviewPortfolio-level AML risk visibility.
• High-Risk Customer ManagementA dedicated workflow for managing high-risk accounts.
• Remittance-Specific Compliance MonitoringMonitoring tuned to remittance transaction patterns specifically.
• Risk Radar & Risk Rules Presentation RewriteThe risk-trigger review screen has been rewritten to present indicators in readable, reviewer-friendly language instead of raw underlying data.
• Compliance Audit Log EnhancementsCustomer audit logs now surface AML transaction-limit overrides directly.

Refinements to the promotional coupon system introduced this cycle, following initial rollout feedback — sharpening targeting and usage controls rather than adding new campaign mechanics.

• Sharper Targeting & Usage ControlsFollow-up improvements to promotional coupon targeting rules and usage limits based on initial rollout feedback.

Per-module licensing and deployment version tracking give operators clearer control over what is enabled on each deployment.

• Per-Module Feature LicensingIndividual platform modules can now be license-gated per deployment — starting with promotional coupons — with expiry warnings surfaced at deploy time and current license status visible from a dedicated utility page.
• Deployment Version TrackingEach deployment's running platform version is now tracked centrally.

New console utilities that streamline onboarding, integration, and day-to-day administration.

• Configurable Customer PIN LengthEach deployment can now set its own required customer PIN length.
• Self-Service API DocumentationA new in-console documentation area lets integrating teams browse API flows and modules directly, with access controls, rather than relying on emailed reference material.
• Payout Channel & Delivery Option ImportPayout channels and delivery options can now be bulk-imported (CSV/JSON) during onboarding instead of being entered one at a time.

Improved customer-facing notifications, analytics accuracy, and in-app engagement flows.

• Delivery-Method-Aware Status MessagingCustomer-facing transfer status wording now adapts automatically to the selected delivery method.
• Notification Analytics AccuracyFixed push notifications reporting the wrong event type to analytics.
• In-App Ratings & Notification Deep-LinkingCustomers can now be prompted for in-app ratings and reviews, and notification links now open directly to the relevant transaction, document, or detail screen instead of a general dashboard.

New system utility pages and tools for operators to understand, audit, and maintain their deployment.

• Software Bill of MaterialsA new page under System Utilities lists the full software bill of materials for the running deployment.
• Infrastructure Architecture PageA new reference page documents the infrastructure architecture underlying a deployment.
• Interactive Platform MapA new interactive map under System Utilities visualises how the platform's modules connect.
• Rewritten Audit Log ViewerThe audit log viewer has been rewritten and relocated into System Utilities.
• Command RunnerA new utility lets authorised administrators run supported maintenance commands directly from the console.

Introduced a flexible promotional coupon system (an optional add-on) that enables marketing teams to create targeted campaigns, offer fee discounts or improved exchange rates, and manage usage controls without engineering involvement.

• Campaign Creation & ManagementMarketing teams can create and manage promotional campaigns with configurable discount types, customer-facing terms, effective dates, and activation controls.
• Flexible Discount OptionsCoupons can provide monetary discounts on applicable fees or payment amounts, or offer an improved exchange rate for eligible transactions.
• Targeted Promotion RulesPromotions can be targeted by platform, payment country, currency, payment method, customer, payout country, currency, payout method, and payout partner.
• Usage & Customer ControlsConfigure global usage limits, per-customer limits, cooling-off periods, and campaign validity windows to control promotional usage.
• Coupon Validation & ApplicationCustomers can enter promotional codes during the quote journey, with eligibility validated before the coupon is applied and the quote repriced accordingly.
• Margin ProtectionExchange rate improvements are capped against the market buy rate to prevent promotional pricing from creating negative margins.
• Controlled Coupon LifecycleCoupon usage is reserved when applied, released for abandoned quotes after the configured period, and permanently locked when checkout is completed.
• Transparent Transaction PricingApplied discounts and promotional rates are recorded with the transaction while retaining the original rate and fee information for margin analysis and audit purposes.

Introduced wallet functionality that allows customers to hold stored value, view live balance updates in the app, and use their available wallet balance to pay for remittance transfers.

• Wallet Balance ManagementCustomers can now hold stored value in their wallet, with the available balance accessible within the remittance payment flow.
• Real-Time Balance UpdatesWallet balance changes are reflected live in the customer app, providing an up-to-date view of available funds.
• Pay with Wallet BalanceCustomers can use their available wallet balance to pay for a remittance transfer directly.
• Connected Payment ExperienceConnects stored value with the remittance payment journey, creating a foundation for more flexible payment experiences.

Introduced admin capability to withdraw KYC document approvals and delete identity documents. This allows operational teams to resolve stalled onboardings and clear duplicate account blocks when customers re-register.

• Withdraw KYC Document ApprovalAdmins can now revoke the approved status of submitted identity documents, resetting the document state if operational issues or data inaccuracies arise.
• KYC Document DeletionProvides admins with the ability to permanently remove uploaded documents from stalled or abandoned customer profiles.
• Prevention of False Duplicate TriggersClears historical document records on abandoned profiles so that customers who forgot their original account can successfully register a new profile without triggering false duplicate alerts.
• Enhanced Admin Operational ControlEmpowers compliance and support teams to resolve edge-case identity bottlenecks directly through the admin portal without requiring database interventions.

An optional add-on: automate exchange rate updates using live market data, configurable pricing rules, and built-in validation and monitoring to keep platform rates accurate and up to date.

• Automated Rate Feeder ConfigurationAdministrators can configure one automated rate feeder for each currency corridor, allowing exchange rates to be updated automatically using supported market data providers.
• Live Market Rate ProvidersThe Base Rate Feeder supports market rate providers to retrieve live market exchange rates for configured currency corridors.
• Configurable Margin & SpreadAdministrators can apply configurable margin and spread values to the market rate to calculate the platform exchange rate used by RemitSo.
• Hourly Automated Rate UpdatesAll active rate feeders are processed automatically on an hourly basis, ensuring platform exchange rates remain aligned with current market data.
• Automatic Rate PublishingCalculated platform rates are automatically published to the existing exchange rate tables using the same process as manual rate updates. Raw market rates are also retained for audit and reporting purposes.
• Unchanged Rate HandlingWhen the newly calculated rate has not changed, the existing rate is skipped to avoid unnecessary processing. Threshold rate alerts are automatically generated when exchange rates change.
• Rate Deviation ProtectionTo protect against incorrect market data, fetched rates are validated against the previously accepted rate. Rates that deviate beyond the configured tolerance are automatically rejected and are not published.
• Automatic Feeder DisablementWhen a market rate is rejected because it exceeds the configured deviation tolerance, the affected feeder is automatically disabled until it is reviewed and re-enabled by an administrator.
• Rate Rejection AlertsBackend users subscribed to notifications receive an email alert when a market rate is rejected. The alert includes the rejected market rate and the previously accepted rate for review.
• Dry Run ModeDry Run mode allows administrators to validate feeder configurations without updating exchange rates. This supports safe testing of new corridors and troubleshooting provider integrations before production updates are enabled.
• Automated Monitoring & ControlThe Base Rate Feeder combines automated rate updates, deviation validation, feeder disablement, rate rejection alerts, and Dry Run testing to provide greater operational control over automated pricing.
• Reduced Manual Effort & RiskThe Base Rate Feeder reduces the manual effort required to maintain exchange rates while keeping rates accurate and up to date. Automated monitoring and deviation protection help prevent incorrect market rates from being published, improving operational efficiency, reducing risk, and providing greater confidence in automated pricing.

Enhanced document identity name matching with strict middle name comparison when ignore_middle_names is set to none.

• Strict Middle Name ComparisonWhen ignore_middle_names is set to none, customer profile and identity document names must contain the same set of middle names for validation to succeed.
• Order-Independent MatchingMiddle names may appear in a different order, but all names must be present on both sides with no additions or omissions.
• Missing or Extra Names RejectedValidation will fail if either the customer profile or identity document contains missing or extra middle names while strict mode is enabled.
• Existing Matching Behaviour UnchangedExisting behaviour for party and counter-party name matching remains unchanged, ensuring full backwards compatibility.
• Improved Identity VerificationThis enhancement provides greater control over identity verification policies, improves matching accuracy and consistency, and reduces false-positive matches caused by incomplete or inconsistent middle names.

A rebuilt payment polling engine, stronger reconciliation and expiry handling, and fixes that keep payment outcomes accurate across providers.

• Seamless ExperiencePIN verification is smoothly integrated into the profile update and user authentication processes to keep your workflow frictionless.
• Rebuilt Payment Status PollingPer-provider status-enquiry commands have been replaced by a single, generic polling engine with a shared state store that tracks attempts, last attempt, next attempt and lifecycle status for every payment. Polling intervals and backoff are now configurable rather than hard-coded per provider.
• Polling Stops Once AuthorisedAuthorisation is now treated as the provider's final answer, removing pointless status calls on payments that already have an outcome.
• Provider Settlement ReconciliationA new read-only reconciliation tool compares our records against provider settlement data and reports discrepancies — including captures that never cleared the transaction, and transactions closed without a matching successful capture. It reports; it never silently rewrites financial state.
• Consistent Expiry Across ProvidersUnpaid transactions were previously closed out by separate per-provider code paths whose state lists and expiry windows had drifted apart. All providers now share one cancellation path with consistent timing.
• Paid When Any Attempt SucceedsA transaction is paid when any of its payment attempts succeeds. Previously only the single attempt the transaction pointed at was considered, so a customer who succeeded on a retry could still be shown as unpaid.
• Duplicate-Capture Alerting & Retry ProtectionOperations are now alerted whenever a payment capture needs a human decision, and the retry endpoint is guarded so it can no longer produce a double-payment scenario. Alerts are delivered through the standard alert-event registry, so subscriptions are managed in the console alongside every other alert.
• Missing Polling Rotation VisibilityA new report lists pollable payments that have no polling record, grouped by provider and state.
• International Character Address HandlingAddresses containing accented and special characters are now transliterated and sanitised before being sent to the payment gateway, fixing payment failures for affected customers.
• Payment Page Language & Compliance IdentifiersThe hosted payment page now honours a configured default language, and the required merchant identifier is included in the transfer description on applicable Canadian bank-transfer requests, meeting the provider's updated operational requirements.

More reliable payout processing with clearer error states, atomic claiming, receipt printing, and smarter beneficiary name validation.

• New Error Payout StateNew error payout state, so failed payouts are distinguishable from those still in flight.
• Retry After Payout ErrorRetry after a payout error now reprocesses the transaction as expected.
• Manual Processing OptionManual processing option for transactions sitting in available for payout.
• Atomic Payout ClaimingRace condition fixed in payout processing. Claiming a payout is now an atomic state transition, so only one worker can move a payout from created to processing.
• Correct Location Data in WorkflowPayouts no longer fail on missing transaction data — the correct location information is now used throughout the payout workflow.
• Stuck Processing FixFixed payouts intermittently stuck in processing, caused by a missing stored document asset.
• Payout Receipt PrintingPayout receipt printing, with receipt print activity recorded in an audit log.
• Payer Recorded on PayoutThe payer is now recorded against each payout transaction.
• Automatic Partner Status PollingAutomatic payout status polling for a partner network that reports status asynchronously.
• Smarter Beneficiary Name ValidationBeneficiary name validation now ignores honorific titles and formatting differences, removing a common source of false validation failures before payout.
• Country Code in Name LookupName lookup now sends the country code prefix across all supported markets.

Stronger identity verification, smarter sanctions handling, clearer mismatch reviews, and more reliable transaction limit controls for compliance teams.

• New Identity Verification ProviderA new identity verification provider integrated, including document capture and webhook handling.
• KYC Data Pre-Fill in Customer AppKYC document data now flows back to the customer app, so supported profile fields can be pre-filled from the verified document instead of being retyped. Document parsing was restructured to support configurable providers.
• Sanctions False-Positive MemorySanctions screening remembers reviewed false positives. A match previously cleared by a reviewer is recognised on subsequent screenings, so the same match no longer has to be dismissed again and again.
• Identity Mismatch Risk IndicatorNew identity mismatch risk indicator, comparing the customer profile against the verified identity document.
• Human-Readable Mismatch ResultsMismatch results rewritten for compliance reviewers — clear, human-readable comparisons of name, date of birth and nationality, replacing raw technical validation output.
• Strict Middle-Name ComparisonStrict middle-name comparison is now supported in document identity matching for firms whose policy requires it. Existing behaviour is unchanged by default.
• Risk Assessment Without Date of BirthRisk assessment no longer fails for customers with no date of birth on file.
• Configurable Transaction LimitsConfigurable customer transaction limits (daily, weekly, monthly), with the calculation now correctly honouring each policy's active window — previously an expired or not-yet-active limit could be applied.
• Global & Individual Limits with Manual ReleaseGlobal and individual transaction limits with a manual release workflow, allowing transactions over a threshold to be held for compliance review and released by an administrator.

A significant piece of work this period, driven by corridors that require a middle name and corridors that require a single full name.

• Flexible Payout Channel Name FieldsPayout channels can be configured with one, two or three name fields, so each corridor asks for exactly the name structure it needs.
• Country-Level Name ConfigurationCountry-level customer name configuration now supports the same one, two or three parts, and can be changed in either direction — previously a middle name could only be added to a country that already had first and last name.
• Automatic Name Field MigrationExisting customers and recipients are migrated automatically whenever the configuration changes, so saved details never end up in the wrong field.
• Customer App & API AlignmentCustomer app and API updated to match, with the second name optional and correct handling of an absent third name.

Smarter, localisation-aware transactional email — with per-notification timing, customisable templates, and fixes for branding, links, and delivery.

• Customer-Language EmailsEmails are now sent in the customer's own language. The notification locale is applied to the message itself rather than switching the global application locale, and is now also carried into queued mail. This fixes language selection across registration, document received / verified / rejected, password changed, password reset, account locked out, MFA one-time-passcode and transaction emails.
• Per-Notification Delivery TimingEach notification can define its own delay instead of every notification inheriting a single global delay — which had been suppressing some transaction emails entirely.
• Payment Lifecycle Email NotificationsTransactional email notifications for payment lifecycle events.
• Translated Email Markup FixFixed HTML markup appearing as visible text in translated emails.
• Configurable Email Logo DimensionsConfigurable email logo dimensions, so branding renders at the right size across clients.
• Customisable Email TemplatesEmail templates are now customisable per deployment. Partial templates have moved into the customisable templates directory, and existing templates are migrated automatically on upgrade — so individual sections can be overridden without forking the whole template.
• Direct Transaction Alert LinksEmail alert links now open the transaction directly rather than landing on the dashboard.
• Notification Link Session FixLinks from notification emails no longer bounce users to the login screen, resolved by correcting the session cookie's SameSite configuration.

Faster, more consistent reporting with reusable export templates and a fix for customer export downloads.

• Transaction Export TemplatesTransaction export templates — predefined, reusable column layouts, removing manual column selection for recurring reports.
• Standard Export Template ProvisioningAn additional standard export template provisioned automatically across environments.
• Customer Export Download FixFixed a server error when downloading a customer export.

Streamlined admin workflows for user access, authentication, and location management — plus key fixes across payouts, branding uploads, and customer profiles.

• Location Assignment & ManagementLocation assignment for users, plus an updated location management screen.
• User Creation with DefaultsUser creation with a default role and company assignment.
• Standard Username AuthenticationStandard username authentication with default password support.
• Passwordless Sign-InPasswordless sign-in for the customer app.
• Four-Digit PIN SupportFour-digit PIN support in PIN validation.
• Agency Payout Channel FixFixed an authorisation error when enabling an agency payout channel.
• Logo Upload Permission FixFixed a permission error when uploading delivery option and wallet logos.
• Date of Birth Timezone FixFixed date of birth displaying a day early for customers in timezones behind UTC.

Infrastructure and corridor enhancements that improve performance, pricing clarity, and payout reach across the RemitSo platform.

• Temporary File URL CachingTemporary file URLs are now cached — and regenerated only when they expire, cutting repeated signing requests to object storage.
• Exchange Rate in Payout MethodsExchange rate is now included in each payout method in the quote response, giving clearer pricing visibility at quote time.
• New Payment Corridors & CurrenciesNew payment corridors and currencies enabled — including additional Nordic currencies and new cash pickup destinations.