Transactions

The ledger of all PesaLink transfers (mfi.pesalink.transaction), inbound and outbound, with their settlement status and bank references. Each record tracks the ISO 20022 message exchange from instruction through acknowledgement to final settlement. Operations staff monitor it to confirm funds reached the counterparty bank.

Transactions
Transactions — live screen from the BridgeERP MFI Suite.

Workflow

  1. Open Transactions under PesaLink to list all interbank transfers.
  2. Filter by direction, status or counterparty bank.
  3. Open a record to view the ISO 20022 references and status history.
  4. Confirm settlement acknowledgement from the destination bank.
  5. Raise a dispute from any transfer that settled incorrectly.

Fields reference

Every field on this screen, drawn from the live data model.

FieldTypeRequiredDescription
End-to-End ID
end_to_end_id
TextStable client reference echoed by the rail.
Bank Reference
bank_reference
TextSponsor-bank side reference / FT ID.
Savings Transaction
savings_transaction_id
Link → mfi.savings.transactionThe mfi.savings.transaction created for the money-leg.
Counterparty Bank Code
counterparty_bank_code
TextLocal Pesalink bank code (3-digit).
Direction
direction
Choice: Outbound, InboundYesDirection
Provider
provider_id
Link → mfi.pesalink.providerYesProvider
Counterparty Name
counterparty_name
TextYesCounterparty Name
Counterparty Account
counterparty_account
TextYesCounterparty Account
Amount
amount
MoneyYesAmount
Currency
currency_id
Link → res.currencyYesCurrency
State
state
Choice: Draft, Sent, Settled, Failed, ReversedYesState
Has Message
has_message
Yes/NoHas Message
Reference
name
TextReference
Member
member_id
Link → mfi.memberMember
Savings Account
savings_account_id
Link → mfi.savings.accountSavings Account
Counterparty Bank BIC
counterparty_bank_bic
TextCounterparty Bank BIC
Counterparty Bank Name
counterparty_bank_name
TextCounterparty Bank Name
Purpose Code
purpose_code
TextPurpose Code
Remittance Info
remittance_info
TextRemittance Info
Initiated At
initiated_at
Date & timeInitiated At
Settled At
settled_at
Date & timeSettled At
Failed At
failed_at
Date & timeFailed At
Failure Reason
failure_reason
Long textFailure Reason
pacs.008 XML
pacs008_xml
Long textpacs.008 XML
Raw Request (masked)
raw_request
Long textRaw Request (masked)
Raw Response
raw_response
Long textRaw Response
Disputes
dispute_ids
ListDisputes
Dispute Count
dispute_count
NumberDispute Count
Company
company_id
Link → res.companyCompany

Actions & buttons

Buttons available on this screen and what they do:

  • Initiate Transfer
  • Query Status
  • Mark Settled
  • Open Dispute

Status lifecycle

Records on this screen move through these statuses:

Draft → Sent → Settled → Failed → Reversed

Notes & rules

  • Holds both inbound credits and outbound debits over PesaLink.
  • Status follows the ISO 20022 acknowledgement lifecycle.
  • Bank reference ties the record to the counterparty's statement.
  • Failed or returned transfers are flagged for reconciliation.

Technical model: mfi.pesalink.transaction · Record: Pesalink Transaction

Was this page helpful?