Reports

The following reports are available:

Daily Transaction Report
MT940 (for select customers only, by request)
CAMT053 Bank Statement (for select customers only, by request)
Reversal File (For the Payment Batch ABA file only and for select customers only, by request)

📘
Encryption of Daily Transaction Reports
The option to enhance the security of Daily Transaction Reports through PGP Encryption is now available. Please note that this feature is not enabled by default; however, it can be self service configured via the dashboard, or on request via a service desk ticket with our team.

Downloading reports using the dashboard

All reports are accessible via the dashboard:

Login to the dashboard
Navigate to Reports in the left navigation bar
Download the report you are looking for

Note: Using the dashboard, only the last 3 months of reports can be accessed. However, the API will provide you access to the full set of reports.

Custom date range reports

Custom date range reports allow users to enter specific dates e.g. 11/10/2023 to 20/10/2023 in order to download a report covering that period.
Please note that there is a maximum limit of 12,000 transaction records that will be returned for any given period.

Daily Transaction Report Overview

The Daily Transaction Report provides a summary of all transaction activity between 12:00 am and 11:59 pm each day.
It functions much like a bank statement, showing all inflows (Credits - CR) and outflows (Debits - DR) to your account.

Transaction Matching (Refunds, Returns, and Fund Updates)

Azupay automatically attempts to match any future inflows or outflows related to an original transaction — for example, a refund on a payment request.

In some cases, such as returns processed through third parties without the correct metadata, automatic matching may not occur.

When a future event affects an original transaction:

A new transaction will appear in the Daily Transaction Report.
The transaction type and original identifiers (e.g., TransactionId, clientTransactionId) will be retained.
The CR/DR field will update on the new transaction to reflect the new flow of funds.
A new NPPTransactionId will be assigned to the updated transaction.
The original transaction will not be impacted.

Debit and Credit Types

Transaction Type	Normal Flow	Exception/Return	Notes
PaymentRequest	CR (received)	DR (refunded)	Return Flow occurs when RETURN_COMPLETE
PaymentInitiation	CR (received)	DR (refunded)	Return Flow occurs when RETURN_COMPLETE
Payment	DR (sent)	CR (returned)	Exception Flow ocurs when RETURNED or FAILED
Sweep	DR (sent)	CR (returned)	Exception Flow ocurs when RETURNED or FAILED
Topup	CR (received)	-
ClosingBalance	NA	NA	A special transaction type that shows the current balance of the account. Only appears if no transactions were made in the report period.
BalanceAdjustment	Varies	-	Balance Adjustments are special case adjustments Azupay makes as an auditable transaction on your account.

Filename format

YYYY-MM-DD-DAILY_TXN_V2.csv; where YYYY is the year, MM is the month and DD is the date of the month. Example: 2022-01-18-DAILY_TXN_V2.csv

📘
Clients can request to configure the 'ClientID' included in the file name
For partners managing multiple client accounts, it can be helpful to include a unique identifier in the file name. This makes it easy to determine which report belongs to which client. If you would like this feature enabled. Please raise a special request a ticket through the Azupay Service Desk. Once configured the file name will appear as clientID_YYYY-MM-DD-DAILY_TXN_V2.csv

If you want your Client ID included in the file name, please contact our support team to have this configured for you. Once configured the file name will appear as your ClientID_YYYY-MM-DD-DAILY_TXN_V2.csv

Generation time

File is generated daily at 6:15PM GMT (5:15am GMT+11) by default.

File generation can be set to either:

Late: 6:15PM GMT (5:15am GMT+11 Option- Australia/Sydney time)
Early: 2:00PM GMT (1:00am GMT+11 Option- Australia/Sydney time)

Field Separator

Fields are separated by a csv comma , by default. The pipe symbol | can be supplied as a delimiter on request.

Line Separator

Lines are separated by a new line character \n

Field specifications

Field	Format	Description	Example Entry	Min Length	Max Length	Nullable
DateTime	String (ISO8601 simplified extended)	Zulu time (GMT+0) timestamp of when the event occurred.	2025-12-09T04:31:21.002Z			No
LocalTime	String (ISO8601)	Australia/Sydney time (AEST/AEDT) timestamp of when the event occured	2025-12-09 15:31:21 GMT+11			No
CRDR	Enum ['CR', 'DR']	`CR` credit or `DR` debit transaction	CR			No
Amount	Currency	Amount of transaction to two decimal places.	100.10*			No
Balance	Currency	Balance of your float account after the transaction was processed Amount to two decimal places.	1343.15			No
TransactionType	Enum ['Payment', 'PaymentRequest', 'Topup', 'Sweep', 'PaymentInitiation', 'ClosingBalance']	Type of transaction processed.	PaymentRequest			No
BSB	String	Bank State Branch - 6 digit code to identify BSB of customer participant in transaction.	123456	6	6	Yes
AccountNumber	String	Bank Account number - Typically 6 to 9 digit unique identifier of customer participant in transaction.	987654321	6	12	Yes
AccountName	String	Account name of customer participant in transaction.	John Smith	5	50	No
PayId	String	The PayId of the transaction. Typically only present for paymentRequests.	[email protected]	5	50	Yes
PayIdType	Enum ['PHONE', 'EMAIL', 'ABN', 'ORG']	The type of PayId used in the transaction.	EMAIL			Yes
PaymentDescription	String	Description provided by payer for transaction. All references to special characters have been removed (only from reports i.e. pipe, line feed, quotation marks and carriage return) Example: Payment for Product XYZ	Payment for Product XYZ	5	280	No
TransactionId	String	The unique transaction identifier generated by the API.	11aa22bb33cc44dd55ee66ff77gg88hh	5	200	No
ParentTransactionId	String	Currently corresponds to the `PaymentRequest.PaymentRequestStatus.parentPaymentRequestId` or `PaymentInitiation.paymentAgreementId` for PayTo transactions	aa11bb22cc33dd44ee55ff66gg77hh88	5	200	Yes
ClientTransactionId	String	The unique Id provided by the consumer of the API	Transaction123456789	5	100	Yes
NPPTransactionId	String	The unique identifier for the transaction within the NPP infrastructure. NPP transaction IDs are always prefixed with the 11 digit SWIFT code of the NPP participant initiating the transaction, followed by a single digit priority code, followed by 8 digits denoting the date of the transaction in format YYYYMMDD, followed by a unique transaction identifier.	AZTPAU22XXXN20220617500000000002050	35	35	Yes
*ClientBranch	String	Additional data point that can be used to identify a transaction - provided by client. *Must be enabled via the Daily Transaction Report options.	Automative Loan	5	50	Yes
*SentViaDE	Enum ['true']	Indicates if an outbound payment was routed via DE instead of settling via NPP rails. Will be blank if not true. *Must be enabled via the Daily Transaction Report options.	true			Ye
*Settled By	Enum ['PayID', 'PayTo']	Indicates if an inbound payment request or a Payment Initiation was settled via PayID or PayTo *Must be enabled via the Daily Transaction Report options.	PayID			Yes

Customising the daily transaction report

Client dashboard users can specify the fields they want to see in their daily transaction report.

In order to customise the daily transaction report, dashboard users should do the following:

Login in to the Azupay client dashboard and navigate to 'Settings' page
Scroll down to the section called 'Daily transaction report'
In the 'Selected Field' dropdown, review currently enabled fields in this list and click to unselect. To add fields to your report, click on unselected fields so that they become highlighted via the checkbox.
Select the time you wish the daily transaction report to be generated (either 1:00am or 5:15am day T+1 Australia/Sydney time)
Click on 'Save' button

How are refunds displayed on the daily transaction report?

The daily transaction report will show all inflows of payments into your account as CR (credits), and all outflows of transactions of as DR (debits). Depending on the transaction type, an inbound payment may be returned or refunded to clients. In this case

Example of how payment request refunds will display

A PaymentRequest refund occurs against a payment request. The original inbound payment request will remain in the transaction report on the original date it was processed (represented as a CR in the CRDR field), and an additional outbound transaction will be populated into the report at the date time the refund was processed (represented as a DR in the CRDR field). This new transaction will contain all of the data of the original request with the following two exceptions:

The amount may be less than the original payment request in the case of a partial refund.
The NPPTransactionId will different.

Sample of a refund on a Payment Request, when the payment request being completed and the refund occuring

DateTime|LocalTime|CRDR|Amount|Balance|TransactionType|BSB|AccountNumber|AccountName|PayId|PayIdType|PaymentDescription|PayerPaymentReference|TransactionId|ParentTransactionId|ClientTransactionId|NPPTransactionId
2022-06-17T00:05:21.000Z|2022-06-17 10:05:21 GMT+10|CR|5.00|410.00|PaymentRequest|802010|00000001|Payer details Name|[email protected]|EMAIL|Integration test payment|Payer payment reference|a75bd89b6f8bc8c04c41a35f99e05c3c||yrirzaalok8ivb82hqk5|AZTPAU22XXXN20220617500000000002050
2022-06-17T00:10:21.000Z|2022-06-17 10:10:21 GMT+10|DR|5.00|405.00|PaymentRequest|802010|00000001|Payer details Name|[email protected]|EMAIL|Integration test payment|Payer payment reference|a75bd89b6f8bc8c04c41a35f99e05c3c||yrirzaalok8ivb82hqk5|AZTPAU22XXXN20220617500000000004677

Sample

DateTime|LocalTime|CRDR|Amount|Balance|TransactionType|BSB|AccountNumber|AccountName|PayId|PayIdType|PaymentDescription|PayerPaymentReference|TransactionId|ParentTransactionId|ClientTransactionId|NPPTransactionId
2022-06-17T00:04:37.000Z|2022-06-17 10:04:37 GMT+10|CR|100.00|100.00|Topup||||[email protected]|EMAIL|Topup Description|Payer payment reference|AZTPAU22XXXN20220617300000000001661|||AZTPAU22XXXN20220617300000000001661
2022-06-17T00:04:41.000Z|2022-06-17 10:04:41 GMT+10|DR|20.00|80.00|Payment|||John-Smith Doe|[email protected]|EMAIL|Payment for wages August 2020||c241b3eece995b38e2d5b79391ded2be||1541e2f0-edd1-11ec-bc15-d1127cd0936e|BZTPAU22XXXN20220617100000000001680
2022-06-17T00:04:42.000Z|2022-06-17 10:04:42 GMT+10|DR|30.00|50.00|Payment|062000|12345678|John-Smith Doe|||Payment for wages August 2020||abb9527055f6461815ea6f16c144b95f||1611b610-edd1-11ec-bc15-d1127cd0936e|BZTPAU22XXXN20220617800000000001600
2022-06-17T00:04:43.000Z|2022-06-17 10:04:43 GMT+10|DR|40.00|40.00|Payment|062000|12345444|John-Smith Doe|||Payment for wages August 2020||c4058276027dea80b8b78041466aab33||16d0c050-edd1-11ec-bc15-d1127cd0936e|BZTPAU22XXXN20220617300000000001750
2022-06-17T00:04:43.000Z|2022-06-17 10:04:43 GMT+10|CR|30.00|80.00|Payment|062000|12345678|John-Smith Doe|||Payment for wages August 2020||abb9527055f6461815ea6f16c144b95f||1611b610-edd1-11ec-bc15-d1127cd0936e|BZTPAU22XXXN20220617800000000001600
2022-06-17T00:04:45.000Z|2022-06-17 10:04:45 GMT+10|CR|40.00|80.00|Payment|062000|12345444|John-Smith Doe|||Payment for wages August 2020||c4058276027dea80b8b78041466aab33||16d0c050-edd1-11ec-bc15-d1127cd0936e|CUSCAU2SXXXN20220617300000000001771
2022-06-17T00:04:46.000Z|2022-06-17 10:04:46 GMT+10|CR|30.00|110.00|PaymentRequest|802010|00000001|Payer details Name|[email protected]|EMAIL|Integration test payment|Payer payment reference|0791daa0510cad2f71a3d35ae3e743d0||bkbxcy1lnxzxqohqh70u|AZTPAU22XXXN20220617200000000001351
2022-06-17T00:04:52.000Z|2022-06-17 10:04:52 GMT+10|CR|95.00|205.00|PaymentRequest|802010|00000001|Payer details Name|[email protected]|EMAIL|Integration test payment|Payer payment reference|3b6a90748ddb718eff97b4bd056e21d9|e10ad2f0bd58377a556b24459723d2d9|1c578bd0-edd1-11ec-b843-bf02934eddb8|AZTPAU22XXXN20220617400000000002011
2022-06-17T00:04:55.000Z|2022-06-17 10:04:55 GMT+10|CR|25.00|230.00|PaymentRequest|802010|00000001|Payer details Name|[email protected]|EMAIL|Integration test payment|Payer payment reference|8170b769a45650522e08b97e08fbc86c|f8f065b02ad2e96458e5e99936f23ac6|1e328d60-edd1-11ec-b843-bf02934eddb8|AZTPAU22XXXN20220617100000000001811
2022-06-17T00:04:57.000Z|2022-06-17 10:04:57 GMT+10|CR|25.00|255.00|PaymentRequest|802010|00000001|Payer details Name|[email protected]|EMAIL|Integration test payment|Payer payment reference|278ca38942e96a4f6a25fb0c5999a10b|f8f065b02ad2e96458e5e99936f23ac6|1f6abf40-edd1-11ec-b843-bf02934eddb8|AZTPAU22XXXN20220617700000000002251
2022-06-17T00:05:00.000Z|2022-06-17 10:05:00 GMT+10|CR|60.00|315.00|PaymentRequest|802010|00000001|Payer details Name|[email protected]|EMAIL|Integration test payment|Payer payment reference|a75bd89b6f8bc8c04c41a35f99e05c3c||yrirzaalok8ivb82hqk5|AZTPAU22XXXN20220617700000000002271
2022-06-17T00:05:07.000Z|2022-06-17 10:05:07 GMT+10|CR|100.00|415.00|PaymentInitiation|||name|[email protected]|EMAIL|The description||869398e7e8cab0c84c826a210135a3d5|d00b985055c20190d5ad64bc49126328|24749290-edd1-11ec-bc15-d1127cd0936e|BZTPAU22XXXN20220617000000000001681
2022-06-17T00:05:21.000Z|2022-06-17 10:05:21 GMT+10|DR|5.00|410.00|PaymentRequest|802010|00000001|Payer details Name|[email protected]|EMAIL|Integration test payment|Payer payment reference|a75bd89b6f8bc8c04c41a35f99e05c3c||yrirzaalok8ivb82hqk5|BZTPAU22XXXN20220617500000000002050
2022-06-17T00:05:28.000Z|2022-06-17 10:05:28 GMT+10|DR|30.00|380.00|PaymentRequest|802010|00000001|Payer details Name|[email protected]|EMAIL|Integration test payment|Payer payment reference|0791daa0510cad2f71a3d35ae3e743d0||bkbxcy1lnxzxqohqh70u|AZTPAU22XXXN20220617900000000001710
2022-06-17T00:05:40.000Z|2022-06-17 10:05:40 GMT+10|DR|380.00|0.00|Sweep|802010|00000001|Account name|||Funds held by Azupay||AZUPAYOUTSWEEP-2D9A890D-20220617||AZUPAYOUTSWEEP-2D9A890D-20220617|BZTPAU22XXXN20220617900000000001760

Backwards compatibility

To ensure backwards compatibility as we introduce more data to this report, we recommend implementing parsing which follows these rules:

Do not rely on columns of data appearing in a particular order.
Assume that we will add columns to the report in the future. Additions of reporting fields are not considered a breaking change and should be handled by your system.

Closing Balance on Daily Report

When a Daily Report is generated, the closing balance for the day can be inferred from the last transaction made for the report period's Balance column. The balance column shows the running balance for the day across transactions, and will indicate your account liquidity at close of reporting period.

DateTime|LocalTime|CRDR|Amount|Balance|TransactionType|BSB|AccountNumber|AccountName|PayId|PayIdType|PaymentDescription|PayerPaymentReference|TransactionId|ParentTransactionId|ClientTransactionId|NPPTransactionId
2022-06-17T00:04:37.000Z|2022-06-17 10:04:37 GMT+10|CR|100.00|100.00|Topup||||[email protected]|EMAIL|Topup Description|Payer payment reference|AZTPAU22XXXN20220617300000000001661|||AZTPAU22XXXN20220617300000000001661

Closing Balance when no transactions are made in reporting period

If no transactions are made during the report period, Azupay will generate a special transaction type with no Credit or Debit action, labelled as "TransactionType" : "ClosingBalance". This will provide you a summary of the current balance of your account with us.

DateTime|LocalTime|CRDR|Amount|Balance|TransactionType|BSB|AccountNumber|AccountName|PayId|PayIdType|PaymentDescription|PayerPaymentReference|TransactionId|ParentTransactionId|ClientTransactionId|NPPTransactionId
2024-02-15T04:17:23.456Z|2024-02-15 15:17:23 GMT+11|||10000.00|ClosingBalance|||||||||||||

📘
Note for SaaS partners
If you are a SaaS provider, you manage your sub client virtual accounts and their liquidity, and Azupay does not track client liquidity on your behalf, your account may be configured to disable account balances.
This setting disables balance checks on your account, including overdraft protections.
If this flag is set, Balance will not be tracked, and Balance will appear as "0" on your Daily Report. You may wish to remove the Balance column from your daily report.
Note that if your sub client makes no transactions during the reporting period, a ClosingBalance record will still be generated, with a balance of 0. The ability to customise this behaviour may change at a later date.

SFTP Ingestion of Reports

SFTP is a popular choice for receiving daily transaction reports, as it allows you to use a traditional batch process for ingesting the report into your system of record for reconciliation and tracking purposes.

We recommend configuring SFTP ingestion of your daily report for supporting reconciliation against webhook events associated with transaction completions or reversals to supplement our webhooks, or if you have a downstream system such as an ERP or billing system where SFTP ingestion streamlines your data management requirements.

The SFTP report is identical to the transaction report you can download from the Reports page of our dashboard, or via our Reports API, and report formats follow the conventions noted in this guide.

Configuration of SFTP Reporting

You can specify the configuration details of the SFTP server where Azupay can upload your daily transaction report.

To specify the configuration details of the SFTP server for your daily transaction report:

Login to the Azupay client dashboard
Click on 'Settings' and scroll down the section called 'Daily Transaction Report'
In the section labelled 'Upload generated reports to your SFTP server', add in details for the following configuration fields: Host, Port, Username, Path, Notification email

Configuration parameters

The following table outlines valid configuration inputs for the SFTP configuration

Variable Name	What to input	Example Input
Host	An internet accessible hostname to connect to your SFTP server, for example a URL or IP address that will resolve to an SFTP server that Azupay can push the report to each day. This should not include a protocol as part of the hostname.	`sftp.azupay.com.au`
Port	The port number where your sftp server is listening for connection attempts.	`22`
Username	The username we should use when authenticating against your sftp server.	`azupay_sftp_reports`
Path	The directory where we should upload the generated reports. This should start with the path name, not a slash.	```azupay/reports``
Notification Email	Optional. We will notify this email address of successful push of reports to your SFTP server.	`[email protected]`
Encryption Public Key	Optional. Provide your OpenPGP public encryption key to encrypt the report.

Click on 'Save' button on the RHS of the page
Once you save these details, Azupay will generate an ssh-rsa public key you will need to associate with the user configured, so that we can securely access your SFTP environment. This will appear below the SFTP configuration:

IP Address Filtering

To further secure the delivery of reports to your sftp server, you can configure your network firewall to only allow connections from the following ip addresses:

Environment	Outbound source IPs	Default TCP port
Production	13.210.211.86, 13.211.183.241, 13.236.45.75	22
UAT	54.79.236.21, 54.252.111.236, 3.106.36.88	22

MT940 reports

You can enable an MT940 report for transactions in the Reports section of the Azupay client dashboard.

If you have configured SFTP Reports, the MT940 report will also be sent via SFTP.

To turn on MT940 reporting, ensure that you have the 'Enabled' checkbox ticked, select Version and Interval, before hitting 'Save' button to configure your MT940 report preferences.

For Interval settings, there are only 2 options to have your report generated: Hourly or Daily.

For Version settings, you can select "V1 (without PayID)" or "V2 (with PayID)". If "V2" is selected, Then the report includes the PayID value for each transaction in the record type 86 section.

Here is a sample of the report:

{1:A01AZTPAU22XXXX0000000000}{2:I940AZUPAYXXXXN}\{3:{118:MT940950GEN}{4:
:20:MT94050GEN000000
:25:80201010000001
:28C:00021/12
:60F:C220121AUD0,00
:62F:C220121AUD0,00
-}{5:}

{1:A01AZTPAU22XXXX0000000000}{2:I940AZUPAYXXXXN}\{3:{118:MT940950GEN}{4:
:20:MT94050GEN000000
:25:80201010000001
:28C:00021/12
:60F:C220121AUD0,00
:62F:C220121AUD0,00
-}{5:}

CAMT.053 Bank Statement

Azupay can generate CAMT.053 bank statements for you. A CAMT.053 bank statement is standard digital file format that provides a clear, structured view of your transaction activity.

Unlike a PDF statement, a CAMT.053 file is machine-readable, making it easy for your ERP, accounting, or treasury system to process automatically, no manual entry required.

To enable the CAMT.053 bank statement, please raise a request with Azupay support

Field Specifications

Group Header

XML Path	Description	Format	Mapping	Sample Value
GrpHdr.MsgId	Unique identifier for the statement message	CAMT053.00288084.date(YYYYMMDD).time(HHMMSS)	Date maps to the date of the statement	CAMT053.00288084.20250807.060000
GrpHdr.CreDtTm	Date/time the CAMT.053 message was created	(YYYY-MM-DD)T(HH:MM:SS+Timezone)		2025-08-08T05:01:12+10:00
GrpHdr.MsgRcpt.Id.OrgId.Othr.SchmeNm.Prtry	Proprietary scheme name for recipient ID	string		MAILBOX
GrpHdr.MsgRcpt.Id.OrgId.Othr.Issr	Issuer of the recipient ID	string		Azupay
Document.BkToCstmrStmt.GrpHdr.AddtlInf	Additional header-level information	string		EODY

Statement Information

XML Path	Description	Format	Mapping	Sample Value
Stmt.Id	Identifies the specific account statement	string	bsbaccountNumberAUD-date of statement	80251020000XXXXAUD-20250807
Stmt.ElctrncSeqNb	Enables chronological ordering of statements	YYYYMMDD		20250807
Stmt.CreDtTm	Date/time statement was generated	Date(YYYY-MM-DD)T(HH:MM:SS+Timezone)		2025-08-08T05:01:13+10:00
Stmt.FrToDt.FrDtTm	Defines the statement coverage period (start)	Date(YYYY-MM-DD)T(HH:MM:SS+Timezone)		2025-08-07T00:00:00+10:00
Stmt.FrToDt.ToDtTm	Defines the statement coverage period (end)	Date(YYYY-MM-DD)T(HH:MM:SS+Timezone)		2025-08-07T23:59:59+10:00

Account Information

XML Path	Description	Format	Mapping	Sample Value
Acct.Id.Othr.Id	Account identifier (e.g., account number)	string	bsbaccountNumber	802510200001234
Acct.Id.Othr.SchmeNm.Cd	Indicates the format/type of the account ID	string		BBAN
Acct.Ccy	Currency denomination of the account	string		AUD
Acct.Id.Othr.Issr	Usually the BSB in AU context	string	clientAccountBsb	802510
Acct.Svcr.FinInstnId.BIC	Identifies the bank holding the account	string		AZTPAU22

Balance Information

XML Path	Description	Format	Value
Bal.Tp.CdOrPrtry.Cd	Indicates the type of balance OPBD = Opening Balance CLBD = Closing Balance	Enum ['OPDB', 'CLBD']	OPBD CLBD
Bal.Amt	Balance amount	Number (2 decimal places)	10.00
Bal.Amt.@Ccy	Currency of the balance		AUD
Ba.CdtDbtInd	Indicates whether the balance is credit or debit CRDT = Credit DBIT = Debit	Always CRDT as Azupay balance cannot be less than 0	CRDT
Bal.Dt.Dt	Balance effective date	Date of statement(YYYY-MM-DD)	2025-08-07

Transaction Summary

XML Path	Description	Format and Calulation	Value
TxsSummry.TtlNtries.NbOfNtries	Summary count of all entries in statement	Number Calculation: Count of Ntry in the statement	4
TxsSummry.TtlNtries.Sum	Summary total value	Number Calculation: Sum of all entries (ignore debit and credit)	6924061.76
TxsSummry.TtlNtries.TtlNetNtryAmt	Sum of credits minus debits	Number (2 decimal places) Calculation: Sum of all credit entries - sum of all debit entries	0.00
TxsSummry.TtlNtries.CdtDbtInd	Indicates net result If TtlNetNtryAmt is: Less than 0: DBIT Greater than or equal to 0: CRDT	Enum ['DBIT', 'CRDT']	CRDT
TxsSummry.TtlCdtNtries.NbOfNtries	Number of credit transactions	Number Calculation: Count of Ntry in the statement where Ntry.CdtDbtInd is CRDT	2
TxsSummry.TtlCdtNtries.Sum	Total value of credits	Number (2 decimal places) Calculation: Sum of Transaction Amount for Ntry in the statement where Ntry.CdtDbtInd is CRDT	3462030.88
TxsSummry.TtlDbtNtries.NbOfNtries	Number of debit transactions	Number Calculation: Count of Ntry in the statement where Ntry.CdtDbtInd is DBIT	2
TxsSummry.TtlDbtNtries.Sum	Total value of debits	Number (2 decimal places) Calculation: Sum of Transaction Amount for Ntry in the statement where Ntry.CdtDbtInd is DBIT	3462030.88

Outbound Payment Entry

Outbound Payments are reported from a Batch level. Therefore if you have processed multiple batches in a given day, there will be an entry for each batch.

Field (XML Path)	Description	Format	Mapping	Value
Ntry.NtryRef	Unique ID for the transaction entry	String	Outbound Payments Batch File Name	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.Amt.@Ccy	Currency of the amount	String		AUD
Ntry.Amt	Amount of the transaction	Number (2 decimal places)	The total amount of the Batch	411689.93
Ntry.CdtDbtInd	Whether the amount is a credit (CRDT) or debit (DBIT)	Enum ['DBIT', 'CRDT']	Outbound Payment Entry will always be a DBIT	DBIT
Ntry.Sts	Indicates booking or pending status	String		BOOK
Ntry.BookgDt.Dt	Date when the transaction is booked	Date (YYYY-MM-DD)		2025-07-09
Ntry.ValDt.Dt	Effective date for value recognition	Date (YYYY-MM-DD)		2025-07-09
Ntry.BkTxCd.Prtry.Cd	Categorizes the type of transaction	String		699
Ntry.BkTxCd.Prtry.Issr	Provides context for interpreting the transaction code	String		BTRS
Ntry.NtryDtls.Btch.PmtInfId	Associates the entry with a batch submission	String	Outbound Payments Batch File Name	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.NtryDtls.TxDtls.Refs.AcctSvcrRef	Reference assigned by the bank	String	Outbound Payments Batch File Name	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.NtryDtls.TxDtls.Refs.EndToEndId	Sender-defined ID passed end-to-end	String	Outbound Payments Batch File Name	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.NtryDtls.TxDtls.Refs.TxId	Internal ID of the payment within the system	String	Outbound Payments Batch File Name	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.NtryDtls.TxDtls.Refs.MndtId	ID of the direct debit authorization	String	Outbound Payments Batch File Name	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.@Ccy	Amount of the specific payment	String		AUD
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.Amt	Currency of the transaction amount	Number (2 decimal places)	The total amount of the Batch	411689.93
Ntry.NtryDtls.TxDtls.AddtlTxInf	Free-text metadata	String	Outbound Payments Batch File Name	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.AddtlNtryInf	Free-text at the entry level	String	Outbound Payments Batch File Name	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request

Sweep Entry

Sweeps Payments are reported from a transaction level. Therefore if you have processed multiple sweeps in a given day, there will be an entry for each sweep.

Field (XML Path)	Description	Format	Mapping	Value
Ntry.NtryRef	Unique ID for the transaction entry	String	NPP Transaction ID	AZTPAU22XXXN20250811500000000009390
Ntry.Amt.@Ccy	Currency of the amount	String		AUD
Ntry.Amt	Amount of the transaction	Number (2 decimal places)	The total amount of the Sweep	50000.00
Ntry.CdtDbtInd	Whether the amount is a credit (CRDT) or debit (DBIT)	Enum ['DBIT', 'CRDT']	Sweep Entry will always be a DBIT	DBIT
Ntry.Sts	Indicates booking or pending status	String		BOOK
Ntry.BookgDt.Dt	Date when the transaction is booked	Date (YYYY-MM-DD)		2025-07-09
Ntry.ValDt.Dt	Effective date for value recognition	Date (YYYY-MM-DD)		2025-07-09
Ntry.BkTxCd.Prtry.Cd	Categorizes the type of transaction	String		699
Ntry.BkTxCd.Prtry.Issr	Provides context for interpreting the transaction code	String		BTRS
Ntry.NtryDtls.Btch.PmtInfId	Associates the entry with a batch submission	String	NPP Transaction ID	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.NtryDtls.TxDtls.Refs.AcctSvcrRef	Reference assigned by the bank	String	NPP Transaction ID	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.NtryDtls.TxDtls.Refs.EndToEndId	Sender-defined ID passed end-to-end	String	NPP Transaction ID	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.NtryDtls.TxDtls.Refs.TxId	Internal ID of the payment within the system	String	NPP Transaction ID	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.NtryDtls.TxDtls.Refs.MndtId	ID of the direct debit authorization	String	NPP Transaction ID	payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.@Ccy	Amount of the specific payment	String		AUD
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.Amt	Currency of the transaction amount	Number (2 decimal places)	The total amount of the Sweep	50000.00
Ntry.NtryDtls.TxDtls.AddtlTxInf	Free-text metadata	String		Funds transferred from Azupay account
Ntry.AddtlNtryInf	Free-text at the entry level	String		Funds transferred from Azupay account

Top Up Entry

Top Ups are reported from a transaction level. Therefore if you have processed multiple Top Ups in a given day, there will be an entry for each Top Up.

Field (XML Path)	Description	Format	Mapping	Value
Ntry.NtryRef	Unique ID for the transaction entry	String	NPP Transaction ID	AZTPAU22XXXN20250811500000000009390
Ntry.Amt.@Ccy	Currency of the amount	String		AUD
Ntry.Amt	Amount of the transaction	Number (2 decimal places)	The total amount of the Top Up	10000.00
Ntry.CdtDbtInd	Whether the amount is a credit (CRDT) or debit (DBIT)	Enum ['DBIT', 'CRDT']	Top Up Entry will always be a CRDT	CRDT
Ntry.Sts	Indicates booking or pending status	String		BOOK
Ntry.BookgDt.Dt	Date when the transaction is booked	Date (YYYY-MM-DD)		2025-07-09
Ntry.ValDt.Dt	Effective date for value recognition	Date (YYYY-MM-DD)		2025-07-09
Ntry.BkTxCd.Prtry.Cd	Categorizes the type of transaction	String		257
Ntry.BkTxCd.Prtry.Issr	Provides context for interpreting the transaction code	String		BTRS
Ntry.NtryDtls.Btch.PmtInfId	Associates the entry with a batch submission	String	NPP Transaction ID	AZTPAU22XXXN20250811500000000009390
Ntry.NtryDtls.TxDtls.Refs.AcctSvcrRef	Reference assigned by the bank	String	NPP Transaction ID	AZTPAU22XXXN20250811500000000009390
Ntry.NtryDtls.TxDtls.Refs.EndToEndId	Sender-defined ID passed end-to-end	String	NPP Transaction ID	AZTPAU22XXXN20250811500000000009390
Ntry.NtryDtls.TxDtls.Refs.TxId	Internal ID of the payment within the system	String	NPP Transaction ID	AZTPAU22XXXN20250811500000000009390
Ntry.NtryDtls.TxDtls.Refs.MndtId	ID of the direct debit authorization	String	NPP Transaction ID	AZTPAU22XXXN20250811500000000009390
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.@Ccy	Amount of the specific payment	String		AUD
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.Amt	Currency of the transaction amount	Number (2 decimal places)	The total amount of the Top Up	10000.00
Ntry.NtryDtls.TxDtls.AddtlTxInf	Free-text metadata	String		Funds transferred to Azupay account
Ntry.AddtlNtryInf	Free-text at the entry level	String		Funds transferred to Azupay account

Payment Request Entry

Payment Requests are reported as one entry for the given day. If you have processed multiple Payment Requests, they will all be included in the one Entry

Field (XML Path)	Description	Format	Mapping	Value
Ntry.NtryRef	Unique ID for the transaction entry	String		PaymentRequest
Ntry.Amt.@Ccy	Currency of the amount	String		AUD
Ntry.Amt	Amount of the transaction	Number (2 decimal places)	The total amount of COMPLETED Payment Requests	50000.00
Ntry.CdtDbtInd	Whether the amount is a credit (CRDT) or debit (DBIT)	Enum ['DBIT', 'CRDT']		CRDT
Ntry.Sts	Indicates booking or pending status	String		BOOK
Ntry.BookgDt.Dt	Date when the transaction is booked	Date (YYYY-MM-DD)		2025-07-09
Ntry.ValDt.Dt	Effective date for value recognition	Date (YYYY-MM-DD)		2025-07-09
Ntry.BkTxCd.Prtry.Cd	Categorizes the type of transaction	String		257
Ntry.BkTxCd.Prtry.Issr	Provides context for interpreting the transaction code	String		BTRS
Ntry.NtryDtls.Btch.PmtInfId	Associates the entry with a batch submission	String		PaymentRequest
Ntry.NtryDtls.TxDtls.Refs.AcctSvcrRef	Reference assigned by the bank	String		PaymentRequest
Ntry.NtryDtls.TxDtls.Refs.EndToEndId	Sender-defined ID passed end-to-end	String		Payment Request Deposits
Ntry.NtryDtls.TxDtls.Refs.TxId	Internal ID of the payment within the system	String		PaymentRequest
Ntry.NtryDtls.TxDtls.Refs.MndtId	ID of the direct debit authorization	String		Payment Request Deposits
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.@Ccy	Amount of the specific payment	String		AUD
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.Amt	Currency of the transaction amount	Number (2 decimal places)	The total amount of COMPLETED Payment Requests	50000.00
Ntry.NtryDtls.TxDtls.AddtlTxInf	Free-text metadata	String		Payment Request Deposits
Ntry.AddtlNtryInf	Free-text at the entry level	String		Payment Request Deposits

Payment Request Refund Entry

Payment Request Refunds are reported as one entry for the given day. If you have processed multiple Payment Requests Refunds, they will all be included in the one Entry

Field (XML Path)	Description	Format	Mapping	Value
Ntry.NtryRef	Unique ID for the transaction entry	String		PaymentRequestRefund
Ntry.Amt.@Ccy	Currency of the amount	String		AUD
Ntry.Amt	Amount of the transaction	Number (2 decimal places)	The total amount of COMPLETED Payment Requests	200.00
Ntry.CdtDbtInd	Whether the amount is a credit (CRDT) or debit (DBIT)	Enum ['DBIT', 'CRDT']		DBIT
Ntry.Sts	Indicates booking or pending status	String		BOOK
Ntry.BookgDt.Dt	Date when the transaction is booked	Date (YYYY-MM-DD)		2025-07-09
Ntry.ValDt.Dt	Effective date for value recognition	Date (YYYY-MM-DD)		2025-07-09
Ntry.BkTxCd.Prtry.Cd	Categorizes the type of transaction	String		699
Ntry.BkTxCd.Prtry.Issr	Provides context for interpreting the transaction code	String		BTRS
Ntry.NtryDtls.Btch.PmtInfId	Associates the entry with a batch submission	String		PaymentRequestRefund
Ntry.NtryDtls.TxDtls.Refs.AcctSvcrRef	Reference assigned by the bank	String		PaymentRequestRefund
Ntry.NtryDtls.TxDtls.Refs.EndToEndId	Sender-defined ID passed end-to-end	String		Refunded Payment Request Deposits
Ntry.NtryDtls.TxDtls.Refs.TxId	Internal ID of the payment within the system	String		PaymentRequestRefund
Ntry.NtryDtls.TxDtls.Refs.MndtId	ID of the direct debit authorization	String		Refunded Payment Request Deposits
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.@Ccy	Amount of the specific payment	String		AUD
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.Amt	Currency of the transaction amount	Number (2 decimal places)	The total amount of COMPLETED Payment Requests	200.00
Ntry.NtryDtls.TxDtls.AddtlTxInf	Free-text metadata	String		Refunded Payment Request Deposits
Ntry.AddtlNtryInf	Free-text at the entry level	String		Refunded Payment Request Deposits

Failed and Returned Outbound Payments Entry

Failed and Returned Outbound Payments are reported at a transaction level. Therefore if there have been multiple Top Ups in a given day, there will be an entry for each Top Up.

Field (XML Path)	Description	Format	Mapping	Value
Ntry.NtryRef	Unique ID for the transaction entry	String	clientPaymentID (batch file name + row number)	payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-5
Ntry.Amt.@Ccy	Currency of the amount	String		AUD
Ntry.Amt	Amount of the transaction	Number (2 decimal places)	The total amount of COMPLETED Payment Requests	40.00
Ntry.CdtDbtInd	Whether the amount is a credit (CRDT) or debit (DBIT)	Enum ['DBIT', 'CRDT']		CRDT
Ntry.Sts	Indicates booking or pending status	String		BOOK
Ntry.BookgDt.Dt	Date when the transaction is booked	Date (YYYY-MM-DD)		2025-07-09
Ntry.ValDt.Dt	Effective date for value recognition	Date (YYYY-MM-DD)		2025-07-09
Ntry.BkTxCd.Prtry.Cd	Categorizes the type of transaction	String		257
Ntry.BkTxCd.Prtry.Issr	Provides context for interpreting the transaction code	String		BTRS
Ntry.NtryDtls.Btch.PmtInfId	Associates the entry with a batch submission	String	clientPaymentID (batch file name + row number)	payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-5
Ntry.NtryDtls.TxDtls.Refs.AcctSvcrRef	Reference assigned by the bank	String	clientPaymentID (batch file name + row number)	payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-5
Ntry.NtryDtls.TxDtls.Refs.EndToEndId	Sender-defined ID passed end-to-end	String	Lodgement Reference (Char position 63-80 in the ABA file)	Reference1
Ntry.NtryDtls.TxDtls.Refs.TxId	Internal ID of the payment within the system	String	Lodgement Reference (Char position 63-80 in the ABA file)	Reference1
Ntry.NtryDtls.TxDtls.Refs.MndtId	ID of the direct debit authorization	String	Lodgement Reference (Char position 63-80 in the ABA file)	Reference1
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.@Ccy	Amount of the specific payment	String		AUD
Ntry.NtryDtls.TxDtls.AmtDtls.TxAmt.Amt	Currency of the transaction amount	Number (2 decimal places)	The total amount of COMPLETED Payment Requests	200.00
Ntry.NtryDtls.TxDtls.RltdPties.Dbtr.Nm	Payee Name	string	payeeName	John Smith
Ntry.NtryDtls.TxDtls.RtrInf.Rsn.Prtry	Reason for a returned transaction	string
Ntry.NtryDtls.TxDtls.AddtlTxInf	Free-text metadata	String
Ntry.AddtlNtryInf	Free-text at the entry level	String

Here is a sample of the statement

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.053.001.02">
  <BkToCstmrStmt>
    <GrpHdr>
      <MsgId>CAMT053.00288084.20250916.060000</MsgId>
      <CreDtTm>2025-09-16T10:42:55.552+10:00</CreDtTm>
      <MsgRcpt>
        <Id>
          <OrgId>
            <Othr>
              <Id />
              <SchmeNm>
                <Prtry>MAILBOX</Prtry>
              </SchmeNm>
              <Issr>Azupay</Issr>
            </Othr>
          </OrgId>
        </Id>
      </MsgRcpt>
      <AddtlInf>EODY</AddtlInf>
    </GrpHdr>
    <Stmt>
      <Id>802010158345799AUD-20250916</Id>
      <ElctrncSeqNb>20250916</ElctrncSeqNb>
      <CreDtTm>2025-09-16T10:42:55.552+10:00</CreDtTm>
      <FrToDt>
        <FrDtTm>2025-09-16T00:00:00.000+10:00</FrDtTm>
        <ToDtTm>2025-09-16T23:59:59.999+10:00</ToDtTm>
      </FrToDt>
      <Acct>
        <Id>
          <Othr>
            <Id>802010158345799</Id>
            <SchmeNm>
              <Cd>BBAN</Cd>
            </SchmeNm>
            <Issr>802010</Issr>
          </Othr>
        </Id>

        <Ccy>AUD</Ccy>

        <Svcr>
          <FinInstnId>
            <BIC>AZTPAU22</BIC>
          </FinInstnId>
        </Svcr>
      </Acct>

      <Bal>
        <Tp>
          <CdOrPrtry>
            <Cd>OPBD</Cd>
          </CdOrPrtry>
        </Tp>
        <Amt Ccy="AUD">0.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Dt>
          <Dt>2025-09-16</Dt>
        </Dt>
      </Bal>
      <Bal>
        <Tp>
          <CdOrPrtry>
            <Cd>CLBD</Cd>
          </CdOrPrtry>
        </Tp>
        <Amt Ccy="AUD">96345.44</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Dt>
          <Dt>2025-09-16</Dt>
        </Dt>
      </Bal>
      <Ntry>
        <NtryRef>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request</NtryRef>
        <Amt Ccy="AUD">1837.28</Amt>
        <CdtDbtInd>DBIT</CdtDbtInd>
        <Sts>BOOK</Sts>
        <BookgDt>
          <Dt>2025-09-16</Dt>
        </BookgDt>
        <ValDt>
          <Dt>2025-09-16</Dt>
        </ValDt>
        <BkTxCd>
          <Prtry>
            <Cd>699</Cd>
            <Issr>BTRS</Issr>
          </Prtry>
        </BkTxCd>
        <NtryDtls>
          <Btch>
            <PmtInfId>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request</PmtInfId>
          </Btch>
          <TxDtls>
            <Refs>
              <AcctSvcrRef>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request</AcctSvcrRef>
              <EndToEndId>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request</EndToEndId>
              <TxId>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request</TxId>
              <MndtId>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request</MndtId>
            </Refs>
            <AmtDtls>
              <TxAmt>
                <Amt Ccy="AUD">1837.28</Amt>
              </TxAmt>
            </AmtDtls>
            <AddtlTxInf>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request</AddtlTxInf>
          </TxDtls>
        </NtryDtls>
        <AddtlNtryInf>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request</AddtlNtryInf>
      </Ntry>
      <Ntry>
        <NtryRef>payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request</NtryRef>
        <Amt Ccy="AUD">1832.28</Amt>
        <CdtDbtInd>DBIT</CdtDbtInd>
        <Sts>BOOK</Sts>
        <BookgDt>
          <Dt>2025-09-16</Dt>
        </BookgDt>
        <ValDt>
          <Dt>2025-09-16</Dt>
        </ValDt>
        <BkTxCd>
          <Prtry>
            <Cd>699</Cd>
            <Issr>BTRS</Issr>
          </Prtry>
        </BkTxCd>
        <NtryDtls>
          <Btch>
            <PmtInfId>payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request</PmtInfId>
          </Btch>
          <TxDtls>
            <Refs>
              <AcctSvcrRef>payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request</AcctSvcrRef>
              <EndToEndId>payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request</EndToEndId>
              <TxId>payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request</TxId>
              <MndtId>payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request</MndtId>
            </Refs>
            <AmtDtls>
              <TxAmt>
                <Amt Ccy="AUD">1832.28</Amt>
              </TxAmt>
            </AmtDtls>
            <AddtlTxInf>payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request</AddtlTxInf>
          </TxDtls>
        </NtryDtls>

        <AddtlNtryInf>payment-16-9-2025-927f2577-7f7a-44c4-8a11-908a5a5cf2de-request</AddtlNtryInf>
      </Ntry>
      <Ntry>
        <NtryRef>AZTPAU22XXXN20250916900000000003490</NtryRef>
        <Amt Ccy="AUD">100000.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Sts>BOOK</Sts>
        <BookgDt>
          <Dt>2025-09-16</Dt>
        </BookgDt>
        <ValDt>
          <Dt>2025-09-16</Dt>
        </ValDt>
        <BkTxCd>
          <Prtry>
            <Cd>455</Cd>
            <Issr>BTRS</Issr>
          </Prtry>
        </BkTxCd>
        <NtryDtls>
          <Btch>
            <PmtInfId>AZTPAU22XXXN20250916900000000003490</PmtInfId>
          </Btch>
          <TxDtls>
            <Refs>
              <AcctSvcrRef>AZTPAU22XXXN20250916900000000003490</AcctSvcrRef>
              <EndToEndId>AZTPAU22XXXN20250916900000000003490</EndToEndId>
              <TxId>AZTPAU22XXXN20250916900000000003490</TxId>
              <MndtId>AZTPAU22XXXN20250916900000000003490</MndtId>
            </Refs>
            <AmtDtls>
              <TxAmt>
                <Amt Ccy="AUD">100000.00</Amt>
              </TxAmt>
            </AmtDtls>
            <AddtlTxInf>Funds added to Azupay account</AddtlTxInf>
          </TxDtls>
        </NtryDtls>
        <AddtlNtryInf>Funds added to Azupay account</AddtlNtryInf>
      </Ntry>
      <Ntry>
        <NtryRef>PaymentRequest</NtryRef>
        <Amt Ccy="AUD">15.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Sts>BOOK</Sts>
        <BookgDt>
          <Dt>2025-09-16</Dt>
        </BookgDt>
        <ValDt>
          <Dt>2025-09-16</Dt>
        </ValDt>
        <BkTxCd>
          <Prtry>
            <Cd>455</Cd>
            <Issr>BTRS</Issr>
          </Prtry>
        </BkTxCd>
        <NtryDtls>
          <Btch>
            <PmtInfId>PaymentRequest</PmtInfId>
          </Btch>
          <TxDtls>
            <Refs>
              <AcctSvcrRef>PaymentRequest</AcctSvcrRef>
              <EndToEndId>Payment Request Deposits</EndToEndId>
              <TxId>PaymentRequest</TxId>
              <MndtId>Payment Request Deposits</MndtId>
            </Refs>
            <AmtDtls>
              <TxAmt>
                <Amt Ccy="AUD">15.00</Amt>
              </TxAmt>
            </AmtDtls>
            <AddtlTxInf>Payment Request Deposits</AddtlTxInf>
          </TxDtls>
        </NtryDtls>
        <AddtlNtryInf>Payment Request Deposits</AddtlNtryInf>
      </Ntry>
      <Ntry>
        <NtryRef>PaymentRequestRefund</NtryRef>
        <Amt Ccy="AUD">5.00</Amt>
        <CdtDbtInd>DBIT</CdtDbtInd>
        <Sts>BOOK</Sts>
        <BookgDt>
          <Dt>2025-09-16</Dt>
        </BookgDt>
        <ValDt>
          <Dt>2025-09-16</Dt>
        </ValDt>
        <BkTxCd>
          <Prtry>
            <Cd>699</Cd>
            <Issr>BTRS</Issr>
          </Prtry>
        </BkTxCd>
        <NtryDtls>
          <Btch>
            <PmtInfId>PaymentRequestRefund</PmtInfId>
          </Btch>
          <TxDtls>
            <Refs>
              <AcctSvcrRef>PaymentRequestRefund</AcctSvcrRef>
              <EndToEndId>Refunded Payment Request Deposits</EndToEndId>
              <TxId>PaymentRequestRefund</TxId>
              <MndtId>Refunded Payment Request Deposits</MndtId>
            </Refs>
            <AmtDtls>
              <TxAmt>
                <Amt Ccy="AUD">5.00</Amt>
              </TxAmt>
            </AmtDtls>
            <AddtlTxInf>Refunded Payment Request Deposits</AddtlTxInf>
          </TxDtls>
        </NtryDtls>
        <AddtlNtryInf>Refunded Payment Request Deposits</AddtlNtryInf>
      </Ntry>
      <Ntry>
        <NtryRef>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-4</NtryRef>
        <Amt Ccy="AUD">2.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Sts>BOOK</Sts>
        <BookgDt>
          <Dt>2025-09-16</Dt>
        </BookgDt>
        <ValDt>
          <Dt>2025-09-16</Dt>
        </ValDt>
        <BkTxCd>
          <Prtry>
            <Cd>257</Cd>
            <Issr>BTRS</Issr>
          </Prtry>
        </BkTxCd>
        <NtryDtls>
          <Btch>
            <PmtInfId>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-4</PmtInfId>
          </Btch>
          <TxDtls>
            <Refs>
              <AcctSvcrRef>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-4</AcctSvcrRef>
              <EndToEndId>030920254</EndToEndId>
              <TxId>030920254</TxId>
              <MndtId>030920254</MndtId>
            </Refs>
            <AmtDtls>
              <TxAmt>
                <Amt Ccy="AUD">2.00</Amt>
              </TxAmt>
            </AmtDtls>
            <AddtlTxInf>Failed by Bank Pty Ltd\06200012345678\DE NO ACCOUNT</AddtlTxInf>
            <RltdPties>
              <Dbtr>
                <Nm>Failed by Bank Pty Ltd</Nm>
              </Dbtr>
            </RltdPties>
            <RtrInf>
              <Rsn>
                <Prtry>DE NO ACCOUNT</Prtry>
              </Rsn>
            </RtrInf>
          </TxDtls>
        </NtryDtls>
        <AddtlNtryInf>Return No account or incorrect account no\Failed by Cuscal Pty Ltd\030920254\DE NO ACCOUNT</AddtlNtryInf>
      </Ntry>
      <Ntry>
        <NtryRef>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-5</NtryRef>
        <Amt Ccy="AUD">3.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Sts>BOOK</Sts>
        <BookgDt>
          <Dt>2025-09-16</Dt>
        </BookgDt>
        <ValDt>
          <Dt>2025-09-16</Dt>
        </ValDt>
        <BkTxCd>
          <Prtry>
            <Cd>257</Cd>
            <Issr>BTRS</Issr>
          </Prtry>
        </BkTxCd>
        <NtryDtls>
          <Btch>
            <PmtInfId>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-5</PmtInfId>
          </Btch>
          <TxDtls>
            <Refs>
              <AcctSvcrRef>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-5</AcctSvcrRef>
              <EndToEndId>030920255</EndToEndId>
              <TxId>030920255</TxId>
              <MndtId>030920255</MndtId>
            </Refs>
            <AmtDtls>
              <TxAmt>
                <Amt Ccy="AUD">3.00</Amt>
              </TxAmt>
            </AmtDtls>
            <AddtlTxInf>Returned by payee Holdings\06200012345444\DE NO ACCOUNT</AddtlTxInf>
            <RltdPties>
              <Dbtr>
                <Nm>Returned by payee Holdings</Nm>
              </Dbtr>
            </RltdPties>
            <RtrInf>
              <Rsn>
                <Prtry>DE NO ACCOUNT</Prtry>
              </Rsn>
            </RtrInf>
          </TxDtls>
        </NtryDtls>
        <AddtlNtryInf>Return No account or incorrect account no\Returned by payee Holdings\030920255\DE NO ACCOUNT</AddtlNtryInf>
      </Ntry>
      <Ntry>
        <NtryRef>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-3</NtryRef>
        <Amt Ccy="AUD">1.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
        <Sts>BOOK</Sts>

        <BookgDt>
          <Dt>2025-09-16</Dt>
        </BookgDt>

        <ValDt>
          <Dt>2025-09-16</Dt>
        </ValDt>
        <BkTxCd>
          <Prtry>
            <Cd>257</Cd>
            <Issr>BTRS</Issr>
          </Prtry>
        </BkTxCd>
        <NtryDtls>
          <Btch>
            <PmtInfId>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-3</PmtInfId>
          </Btch>
          <TxDtls>
            <Refs>
              <AcctSvcrRef>payment-16-9-2025-9f8f2cb5-7a4b-4db6-8e21-cb6d12f2ea67-request-3</AcctSvcrRef>
              <EndToEndId>desc</EndToEndId>
              <TxId>desc</TxId>
              <MndtId>desc</MndtId>
            </Refs>
            <AmtDtls>
              <TxAmt>
                <Amt Ccy="AUD">1.00</Amt>
              </TxAmt>
            </AmtDtls>
            <AddtlTxInf>Bad Request Corp\06260370325613\DE NO ACCOUNT</AddtlTxInf>
            <RltdPties>
              <Dbtr>
                <Nm>Bad Request Corp</Nm>
              </Dbtr>
            </RltdPties>

            <RtrInf>
              <Rsn>
                <Prtry>DE NO ACCOUNT</Prtry>
              </Rsn>
            </RtrInf>
          </TxDtls>
        </NtryDtls>
        <AddtlNtryInf>Return No account or incorrect account no\Bad Request Corp\desc\DE NO ACCOUNT</AddtlNtryInf>
      </Ntry>
      <TxsSummry>
        <TtlNtries>
          <NbOfNtries>8</NbOfNtries>
          <Sum>103695.56</Sum>
          <TtlNetNtryAmt>96346.44</TtlNetNtryAmt>
          <CdtDbtInd>CRDT</CdtDbtInd>
        </TtlNtries>
        <TtlCdtNtries>
          <NbOfNtries>5</NbOfNtries>
          <Sum>100021.00</Sum>
        </TtlCdtNtries>
        <TtlDbtNtries>
          <NbOfNtries>3</NbOfNtries>
          <Sum>3674.56</Sum>
        </TtlDbtNtries>
      </TxsSummry>
    </Stmt>
  </BkToCstmrStmt>
</Document>