Only entities with an approved beneficiary appear here.
Beneficiary *
Paying into — from the approved register
Bank details come from the beneficiary register and cannot be typed here. Changing them is a separate, separately approved action.
What authorises this payment *
Why is this being paid? *
There is no invoice and no mandate behind this payment, so what you write here is the only record of why the money left.
What this settles
Exchange rate *
Every outgoing payment must name what it settles. This is what the approver sees.
Aspira has never seen this invoice. The payable came from a ledger extract or was
typed in without a document. You can raise the payment anyway — the approver will be told there
is nothing to check it against.
Which flow is this *
What an agent charges is agreed per flow, so this decides which rate applies.
How will this be paid *
Approved source accounts only. An account must be approved by a second person before it can pay.
What this channel costs
Is the money there?
Amount *
Value date *
Defaults to five working days out.
Payment reference *
What the beneficiary will see, and what this reconciles against.
What will be created
USD0.00
From—
Tonot selected
Via—
Value date—
Reference—
Approval this will need
1
You raise itRecorded against your Microsoft account
2
A second person approvesCannot be you — four-eyes
3
Board releaseOnly above the threshold
∥
Sign-off lanes
This will need a board member woken up
Paid in partsin one piece
Add an account
The certificate
An account certificate or a bank statement showing these details, issued by the bank.
If there is none, say why — an account with no document and no explanation is a record nobody can check later.
The call-back
Has anybody rung the beneficiary to confirm these details?
Ring a number you already held — a contract, their website, a previous statement.
The number printed on the document that carries these details reaches whoever sent it.
With no call-back the account is recorded BLOCKED. Nothing can be paid to it.
Somebody senior to you can sign for the omission afterwards, in writing — and whoever signs
cannot then approve the account.
Add a beneficiary
Beneficiary name *
The name the bank holds for the account. A mismatch is the commonest reason a payment is returned.
Paying company *
Registered company *
The register entry this beneficiary belongs to (1.2.94). The payee name above is what the bank holds; this is WHO the company is.
IBAN
SWIFT / BIC
Account number
Bank name
Currency
Special note about this beneficiary
Shown in full to whoever approves this, and kept with the record afterwards. This is where "confirmed by phone with the CFO on 3 March, not by email" belongs.
Correspondent bank, addresses and remarks
Intermediary bank
Intermediary SWIFT / BIC
Bank address
Beneficiary address
Remarks
What will be created
—
Company—
Account—
Country—
Bank—
Approval this will need
1
You propose itRecorded against your Microsoft account
2
A treasury manager approvesCannot be you, and they confirm it with their own authenticator code
3
Only then can it be paidUntil then it cannot be chosen on a payment
Add beneficiaries from a spreadsheet
Nothing is saved until you have seen what the file contains
ASPIRA TREASURY
SECURE ACCESS · MULTI-ENTITY PLATFORM
Sign-in is not configured
This application could not read its sign-in settings from the server, so it
cannot start. It will not fall back to a local sign-in.
Check that ENTRA_TENANT_ID and ENTRA_CLIENT_ID are set
on the app service, and that the backend is running.
Your role and entities come from your Microsoft account. Contact your administrator if access is missing.
Select your role
Your entity
Select user
/
CTA Commodities DMCC
Treasury Operator
Good morning.
Meridian Junior
On: —
×
Hi — I’m Meridian Junior, your day-to-day helper. I can explain what’s on your screen, help you draft a payment, find data, or take you somewhere. I always work within your permissions and the platform’s controls. What do you need?