Field 25 in SWIFT Messages: Format, Examples & How to Use It
Field 25 is used to identify the sender or receiver account in SWIFT messages like MT103, MT202, and MT940. It must be accurate to avoid errors and delays.
What Is Field 25 in SWIFT Messages?
Field 25 is the “Account Identification” field used in SWIFT messages. It shows the account number of the sender, receiver, or intermediary involved in a transaction. Using it correctly helps avoid delays, errors, and compliance issues.
Why Field 25 Matters
- Accuracy: Ensures funds are directed to the correct account.
- Compliance: Meets international banking standards.
- Efficiency: Reduces processing time and manual intervention.
Field 25 Format (Structure)
Field 25 typically follows this structure:
- Up to 35 alphanumeric characters
- Usually just the account number
- May include a slash (e.g.
/1234567890)
Example: 25:1234567890
This identifies the account involved in the payment.
Where Field 25 Appears
| Message Type | Purpose of Field 25 |
|---|---|
| MT103 | Sender’s account number |
| MT202 | Intermediary bank’s account |
| MT940 | Account linked to the statement |
Examples of Field 25 in Use
MT103 Example:
makefileCopyEdit:25:/1234567890
:50K:/1234567890
Here, Field 25 shows the sender’s account.
MT202 Example:
makefileCopyEdit:25:/0987654321
:52A:/0987654321
This identifies the intermediary account for a bank transfer.
Best Practices for Field 25
- Double-check account numbers to avoid misrouting.
- Follow format rules exactly as outlined in SWIFT standards.
- Keep account info up to date to avoid rejections.
Common Issues and How to Fix Them
| Issue | Fix |
|---|---|
| Wrong account number | Verify against official records |
| Invalid format | Follow correct character rules |
| Field left blank | Ensure Field 25 is always completed |
Technical and Security Considerations
- Length: Up to 35 characters
- Allowed Characters: Alphanumeric + certain symbols
- Security: Use encryption and access control for sensitive data
- Audit Trail: Maintain logs for compliance reviews
Developer Tip
If integrating SWIFT messages into banking systems:
- Ensure Field 25 is correctly parsed
- Set up automated validation
- Log errors and trigger alerts for invalid values