Sarafi software should make every movement of value explainable
A Sarafi and remittance platform connects the customer or counterparty, identity evidence, currency, rate, amount, fees, cash or bank movement, remittance instruction, agent or partner, approval, settlement and accounting record. Each balance should be traceable to authorized business events rather than unexplained manual adjustment.
Licensing, permitted services, customer due diligence, sanctions, monitoring, reporting, record retention and other AML/CFT or regulatory duties must be determined by the licensed institution with current Da Afghanistan Bank requirements and qualified legal or compliance owners. Software supports an approved programme; it cannot grant a licence or declare a person or transaction compliant.
Customer, counterparty and identity records
- Customer or organization identifier and controlled duplicate resolution
- Approved identity, contact and address information
- Authorized representatives, beneficiaries or related parties where required
- Risk classification, review dates and evidence defined by compliance
- Restricted documents and notes with purpose-based access
- Account status, limits and permitted services approved by the institution
Required fields, verification methods and refresh periods must follow current policy. The platform should preserve who verified information, when and from which approved evidence.
Currency exchange and rate governance
An exchange transaction can record source and destination currencies, amounts, rate, rate source, spread or fee, customer, cashier, location, time, payment and receipt. Rate boards, negotiated rates, tolerances and overrides need named authority. Reversals or corrections should retain the original deal and financial effect.
Remittance lifecycle and payment evidence
A remittance may pass through initiation, identity and purpose checks, funding, review, approval, transmission, agent acceptance, payout, confirmation and settlement. The record should preserve sender, beneficiary, currencies, amounts, fees, locations, references, documents and status history.
Cancellations, returns, expired instructions, failed payouts and corrections require explicit rules. A status change must not silently erase the financial or compliance history.
Cash, safe, bank and branch positions
Cash movements can be separated by currency, cashier, safe, till, branch and accountable custody. Transfers, opening and closing counts, overages, shortages, bank deposits and withdrawals need evidence and review. System balances should be reconciled with physical cash and authorized bank records.
Agents, partners and settlement
Agent or partner relationships may include limits, currencies, corridors, funding, receivables, payables, commissions, disputes and settlement statements. Every partner balance needs an agreed source of truth and reconciliation process. External messages or APIs require authentication, duplicate protection, acknowledgements, errors and support ownership.
Fees, commissions and connected accounting
Approved fees or commissions can depend on service, currency, amount, location, partner or commercial agreement. The system can connect exchange, remittance, collection, payout, reversal and settlement events to controlled journal entries. Finance approves accounts, posting, profit recognition, exchange treatment and period close.
Maker-checker, limits and exceptions
Roles should separate preparation, cash handling, review, approval, settlement, reversal, compliance review and administration. Limits may apply by user, branch, currency, amount, customer, service or risk. Overrides need reason, authority and evidence. Sensitive master-data changes should receive controls comparable to transactions.
AML/CFT evidence and regulatory reporting
The platform may support customer review dates, required documents, configured monitoring scenarios, alerts, investigations, decisions, escalation and approved reports. Rules and thresholds require current institutional authorization and secure access. An alert is not proof of wrongdoing, and the absence of an alert is not proof of compliance.
Statements, receipts and customer communication
Receipts and statements can show permitted transaction references, currencies, amounts, fees and running balances. WhatsApp, SMS, email or portals require verified recipients, approved templates, delivery-failure handling and privacy controls. Public channels should not expose sensitive identity or financial records.
Security, continuity and controlled access
The architecture may include strong authentication, device or location controls, encrypted transport, protected credentials, activity logs, backups and recovery tests. Downtime procedures must define manual references, cash custody, later entry, duplicate prevention and reconciliation. Privileged access should be limited and reviewed.
Implementation, migration and financial UAT
Implementation maps licensed services, branches, currencies, rates, cash locations, roles, limits, partners, reports and integrations. Migration should validate customers, currency balances, open remittances, agent positions and required history. UAT should cover rate overrides, insufficient cash, duplicate instructions, partial or failed settlement, reversals, limits, alerts, close and recovery.
Afghanistan regulatory reference
The governance model was cross-checked against Da Afghanistan Bank’s regulation for money-service providers and foreign-exchange dealers, including licensing and AML/CFT responsibilities. Current applicability and requirements must be confirmed directly with DAB and authorized advisers; this page is not legal advice or evidence of compliance.