EOD lives in spreadsheets
Fees, splits, and acquirer files are matched manually with version-control nightmares.
06 · SettlementThe controlled
The controlled
end-of-day.
Turn live transactions, fees, and beneficiary splits into single-currency batches finance can approve — then reconcile against acquirer, SWIFT, and GL files without spreadsheet bridges.
Built forFinance, treasury, and operations teams closing merchant or programme books across acquirers
Batch model
Single-currency · processing vs value date
File counterparts
Acquirer · SWIFT · GL exports
Controls
Maker-checker overrides · exception register
What buyers are solving
Framed for Finance, treasury, and operations teams closing merchant or programme books across acquirers — not generic payment pain.
Processing date ≠ value date
Treasury cannot explain SWIFT expectations when the platform only stores one date.
Silent adjustments
Ops edits settlement lines without dual control or reason codes — auditors push back.
How it works
- Capture activity
Eligible transactions and fees roll into a batch window.
- Validate
Internal totals, fees, and beneficiary splits checked.
- Approve
Maker-checker sign-off for release.
- Pay / book
Payout instructions or GL handoff per your process.
- Reconcile
Match to acquirer and bank files; manage exceptions.
settlement · 2026-05-10 · maker-checker
4 batches
CYCLEBATCHGROSSFEENETSTATUS
T+0 · openB-91823 · EGP1,420,8000.55%1,412,985open
T+0 · lockedB-91822 · EGP893,2100.42%889,459locked
T-1 · paidB-91821 · EGP1,642,0000.68%1,630,838paid out
T-1 · paidB-91820 · USD212,4000.05%212,294paid out
Core capabilities
Each capability names a concrete mechanism — not a marketing adjective.
Single-currency batches
Batch windows group eligible payment states for one settlement day and currency; fees resolved or deferred by rule.
Processing vs value date
Both dates stored so finance can align platform activity with SWIFT or local clearing expectations.
Fee & beneficiary splits
Fee engines and split instructions resolve into batch lines before approval.
Acquirer file recon
Import acquirer settlement files and match to platform totals with an exception register.
SWIFT / bank file import
CSV or bank-specific formats populate expected lines or validate platform totals.
GL export packs
Export batches in formats your GL or treasury tools consume — Flagship does not replace the GL.
Maker-checker overrides
Adjustments require approvals and reason codes; closed batches are immutable — corrections are new entries.
Assisted exception triage
Optional AI-assisted grouping of likely exception causes for analyst confirmation — it does not auto-post GL entries.
Where this sits vs alternatives
Batch immutability, multi-file recon, and dual control are a finance platform — not a nightly ETL script.
Many incumbents stop at totals. Exception registers and maker-checker overrides are first-class here.
Orchestrators optimize authorization routing. Settlement is the controlled end-of-day for finance — a different buyer and control model.
Architecture and deployment
Payment activity feeds batch construction; approval gates release; file imports close the loop against external truth.
Activity intakeGateway, wallet, and programme events
Batch engineFees, splits, processing/value dates
ControlsMaker-checker · immutable closes
External truthAcquirer files · SWIFT · GL exports
Deployment options
SaaS
Shared settlement control plane in MENA-ready regions.
Dedicated
Isolated finance workloads on dedicated or private-cloud tenancy.
File gateway options
SFTP / API file exchange with credential isolation from daily operator views; SFTP and HTTPS APIs supported.
- HA/DR for batch jobs and file gateways with retry queues and stated recovery objectives.
- Settlement files and beneficiary PII follow programme residency and retention controls.
- Bank credentials are isolated from day-to-day operator screens.
Integration experience
Integrate via batch APIs and file drops. Examples are illustrative.
Illustrative example — not a live endpoint
Request
GET https://api.flagship.example/v1/settlement/batches?status=pending Authorization: Bearer $FLAGSHIP_TOKEN
Response
{ "batches": [ { "id": "bat_01H", "currency": "EGP", "processing_date": "2026-09-20", "value_date": "2026-09-22", "status": "pending_approval" } ]
}SDKs & client libraries
Acquirer and scheme file-format catalogue issued during onboardingREST batch APIsSFTP and API ingestion with per-tenant credentials
Integrations
Acquirer filesSWIFTGL exports
Security and compliance
Settlement moves money — dual control and credential isolation are non-negotiable.
Immutable closed batches
Once closed, batches are not silently edited; adjustments are new ledgered entries.
Maker-checker
Approvals and reason codes on overrides and releases.
Credential isolation
Bank/SFTP secrets kept out of daily operator views.
Pricing orientation
Settlement is usually programme-priced on batch volume and file complexity. Numbers on request.
Monthly transactions settled
Lines flowing into batches.
File counterparts
How many acquirer/bank/GL formats you certify.
Entities / subsidiaries
Batch dimensions and hierarchies.
Deployment
Shared vs dedicated tenancy.
Commercials follow a parallel-run design with finance stakeholders.
FAQ
Deal-killing objections, answered plainly.
Do you replace our GL?
No. We prepare batches and exports your GL or treasury tools consume.
Can batches split by subsidiary?
Yes. Hierarchies and dimensions are part of the batch model.
What about partial captures?
State transitions feed settlement eligibility per your rules.
Who can override a closed batch?
Closed batches stay immutable; corrections are new entries under maker-checker — not silent edits.
Can AI post adjustments automatically?
No. Assisted triage groups exceptions for humans; posting still requires your control path.
Related products
Parallel-run your next close
Bring a sample acquirer file and fee policy. We will map batch design and sandbox access — not a recon magic demo.