Platform

Payments

Build the payment batch, send it for approval by amount band, then deliver the approved instruction to the bank. An unapproved instruction cannot enter a batch; the same item can never enter two.

Payment batchessegregation of duties · multi-signature approval by amount band
PKT-2026-0841TRY 18,240,00048 instructionsFile ready
PKT-2026-0842TRY 9,410,00031 instructionsAwaiting 2nd approval
Instruction sources

Instructions from four sources

Instructions come from four sources; they merge into one batch and each stays on record with its source.

Source breakdown in the batch48 instructions
Manual entry6 instructionsTRY 2,140,000
Planned cash flow11 instructionsTRY 4,860,000
Loan instalments4 instructionsTRY 3,720,000
Payables27 instructionsTRY 7,520,000
Every item is bound to its source; it cannot enter a second batch.
Source
What it delivers
Fields entered
Manual entry
Single instruction
Payee, IBAN, amount, currency, value date
Planned cash flow
Selected from items already in the forecast
Item selection and value date
Loan instalments
Instalments coming due, from the repayment schedule
Automatic; only the value date is confirmed
Payables coming due
Invoices from the ERP
The counterparty IBAN is filled in automatically

Once an item enters a batch it is bound to its source; the same instalment or invoice cannot enter a second batch.

Approval

Multi-signature by amount band

One, two or three signatures are required depending on the thresholds. The number needed is frozen at request time and cannot be lowered later by changing the threshold.

A requester cannot sign their own batch; the rule is enforced in the database. Changing the band table itself is also subject to approval.

How many signatures · whyCannot be approved
Batch amountTRY 8,412,000
Amount bandAbove TRY 5,000,000 · 3 signatures
Authorised signatories defined2 people · 1 missing
Signature status
Preparer · cannot sign their own batch
CFO · signed
No third signatory defined
This is not a “pending” state: the configuration must be fixed.
Segregation of duties

The preparer cannot approve

Even if the user who built the batch is on the signature list, they cannot approve their own batch. The rule cannot be bypassed from the application layer.

Frozen signature count

The count is fixed at request time

The band table in force when the batch was opened applies. Whether the threshold is later raised or lowered, that batch keeps its signature count.

Configuration error

If there are too few authorised signatories

The batch opens but cannot be approved. It does not sit silently in the queue; it is reported as a configuration error.

Delivery

Two routes: file or direct delivery

File

ISO 20022 pain.001 and bank-format files are generated; you upload them to your bank. The download is recorded — an approved batch that was never downloaded lands on the attention list.

pain.001Bank-specific fileDownload record

Direct delivery

An approved instruction is delivered to the bank through a licensed open banking provider. Tideon holds no payment initiation licence; it produces the instruction and hands it to the provider.

Licensed providerPayment initiationPer bank

Which route is used is decided per bank and per organisation.

Response tracking

Status per instruction

The bank response is processed per instruction. If one IBAN in a batch is wrong, only that instruction is rejected and the rest go through.

Accepted and received are not the same — the bank may have received an instruction without deciding on it yet. The two are shown separately.

Bank response · per instruction7 instructions
Accepted4 instructionsTRY 6,980,000
Rejected1 instructionTRY 540,000
Received · no decision2 instructionsTRY 1,310,000
A rejected instruction stays in the batch; its reason stays on record.
Status
What it means
Next step
Delivered
The instruction reached the bank
Awaiting response
Received
The bank has logged the instruction but not decided
Stays under watch
Accepted
The bank will execute the transaction
Matched against the account transaction
Rejected
A single instruction did not go through
The reason is recorded and the item can join a new batch
Limits

What we do not do

We do not hold a payment initiation licenceInstructions are delivered through a licensed provider.
An approved batch cannot be editedA change produces a new batch; it can be cancelled but never deleted.
No total is given in mixed currenciesIf any line cannot be converted, no total is shown and approval falls to the highest band.
System approval is not bank approvalWhoever approves in the system may not be on the bank’s signature circular; the two authorities are kept separate.

Let’s build the payment flow with your own approval structure

In the meeting we define your amount bands and signatory list together.