Running Agents, Branches and Corridors From One Console

Many established money transfer operators grew up behind a counter. The app came later, and with it a second way of working: digital customers screened and limited by the platform, branch and agent transfers recorded somewhere else and reconciled by hand. The two drift apart. Staff at a branch can do things nobody at head office can see, a payout partner's address is in an email, and when the regulator asks where a payout was handed over, someone goes looking. One console for every channel closes that gap.

This guide is for operations heads, network managers and compliance leads at operators that run branches, agents or both alongside a digital app.

RemitSo is one way to run this. Its Companies module holds sending and payout companies, the corridors each one operates, agencies with their channels, the locations that can transact, API configuration, each payout company's declared payout provider and address; staff users can be assigned to locations; payout channels and delivery options load from files. It does not recruit or supervise your agents: your team still decides who represents you, trains them and checks their work. This guide sets out how to structure the network well on any platform.

Before agents and branches, get the companies right. Most operators have at least two kinds.

• Sending companies: the entities that take customers' money. An operator licensed in two countries often has two, each with its own licence obligations.
• Payout companies: the entities that deliver money to recipients, whether your own subsidiary or a partner.

Two details on payout companies cause trouble when missing. First, which payout provider the company uses: in RemitSo, each payout company declares its payout provider, so nobody has to guess which connection a payout went through. Second, the company's own address: in RemitSo, each payout company carries its own address, because the regulator asks where money was handed over.

A corridor is not just a pair of countries. It is a currency, a country and the channels a particular company is allowed to use. One sending company may be licensed for bank and cash pickup payouts to a country while another is not; a payout company may handle one currency but not another.

In RemitSo, operational corridors are set per company: the currencies, countries and channels each company has enabled. The benefit is that your licence boundaries live in the configuration, not in staff memory. What each company may offer is set in one place, where compliance can review it.

Corridors still need pricing before they go live. In RemitSo, a fee rule is mandatory before a corridor can be activated, even when no fee is charged. For choosing which corridors to open, see payout corridor strategy.

An agency is a business that acts for you, such as a shop, a pharmacy or a travel agent, or a group of your own branches. A location is a place where transactions actually happen.

Agencies

In RemitSo, agencies carry their own channel enablement and lifecycle. Enable for each agency only the channels it is approved and trained for. An agent approved for cash pickup payouts should not also offer something it has never been trained on.

Locations

Under each agency sit its transaction-capable locations. Treat this list as part of your compliance record: it is the answer to "where can customers transact with you?", which regulators and banks both ask.

• Add a location only when it is ready: staff trained, signage and customer information in place.
• Keep the list current: a closed shop still listed as a location is a question you will be asked.
• Record locations at the right level: one agency with five shops is five locations, not one.

The controls that matter most at a counter are the ones on the person behind it.

• Location assignment: in RemitSo, users can be assigned to locations, so each person's work belongs to a place.
• Roles built from permissions: RemitSo has 89 separate permissions, each described in plain language. Build a branch role that can do counter work and nothing else, rather than handing out an office role.
• Field-by-field access: transaction details can be granted field by field, so counter staff see what they need to serve a customer and no more.
• Two-step sign-in and sign-in records: staff sign in with an authenticator app or email code, and every sign-in is logged with time, IP address, city, country, app and whether two-step sign-in was completed. Filter to sessions where it was not.
• Departments: RemitSo comes with an Agents and Branch Staff department pre-set. With the staff training programme, an optional add-on, a department sets who must complete a training and its head is told when someone falls behind.

With branch and agent work in the same platform as your app, it falls under the same controls: every sender and recipient is screened against sanctions lists, and the same AML and risk rules apply. For more on role design, see role-based access control for remittance operations.

A network that pays out in many countries needs many payout channels, and each one has its own rules about what recipient details are required. Typing them one by one is slow and error-prone.

• Payout channels: in RemitSo, a payout channel is a country, a currency and a delivery method, with the recipient details required and the decimal places. Channels can be set up one at a time or loaded from a CSV or JSON file.
• Delivery options: the banks and mobile money operators per country, loaded for all countries at once from a file.
• Name fields: each payout channel can ask for one, two or three name fields, so names are captured the way each channel needs, and beneficiary names are validated.

The customer benefit is direct. Recipient forms match each payout method, so fewer payouts fail for missing or badly formatted details, and status updates are worded for the delivery method, such as "Ready for Pickup" or "Sent to Bank", in the app, push, emails and statements. See reducing last-mile transaction failures.

Each partner has its own codes for banks, branches and products. In RemitSo, API configuration holds the reference mappings for integrations, so the link between your setup and a partner's codes is recorded in the console rather than buried in code. When a partner adds a bank or changes a code, the change is a configuration task, and the 3rd Party Integrations page shows whether each provider is fully configured.

Network setup goes wrong when nobody is sure who owns which part. Agree owners up front; the split below is a common starting point.

The details below are illustrative, chosen to show the reasoning rather than to describe any real operator.

An operator has a digital app, four of its own branches and an agent network of 30 shops. Branches and agents record transfers in a separate system, and head office reconciles them each morning.

Step 1: companies and corridors

The operator sets up one sending company and two payout companies, each with its declared payout provider and address. Corridors are enabled per company: bank and cash pickup to two countries, mobile wallet to one.

Step 2: agencies and locations

The four branches become one agency with four locations. The agent network becomes 12 agencies, because several owners run more than one shop, with 30 locations between them. Eight agencies are enabled for cash pickup payouts only; the rest for sending and payouts.

Step 3: people

Each of the 70 counter staff gets their own user, assigned to a location, with a branch role built from permissions and two-step sign-in. The network manager filters sign-in records weekly for sessions without two-step sign-in.

Step 4: payout options

Payout channels for the three countries load from one file, and delivery options for all countries from another. Name fields are set to match each partner.

Step 5: the first month

Head office no longer reconciles a separate counter system each morning, because every transaction is in one admin panel. A customer who sends from a shop gets the same "Ready for Pickup" wording as one who sends from the app. When the regulator asks where a sample of payouts was handed over, the answer comes from the payout company records.

RemitSo's Companies module and payout settings put your network in the same console as your digital business. See the admin features and what customers see in the customer app.

• Sending and payout companies (your team): each licensed entity and payout company set up separately, so licence boundaries are in the configuration.
• Declared payout provider and payout company address (your team): you can show which connection a payout used and where money was handed over when the regulator asks.
• Operational corridors per company (both): each company offers only the currencies, countries and channels it is allowed to, so customers are only offered what you can actually deliver.
• Agencies with channel enablement, and transaction-capable locations (both): agents offer only what they are approved for, and customers get the same service at any location.
• Location assignment, roles and field-by-field access (your team): every person's work belongs to a place, and each sees only what the job needs.
• Payout channels and delivery options from files (your team): many countries set up in one load rather than hours of typing.
• Recipient forms and status wording by delivery method (your customers): fewer payouts fail for missing details, and updates such as "Ready for Pickup" read the same in the app, push, emails and statements.
• API configuration (your team): reference mappings with partners kept in the console, so a partner's code change is a configuration task.

What your team still does: choose and supervise agents, train staff, decide which channels each agency offers, and keep the location list current. To see it with your own network in mind, book a demo.