CC Westpac Batch UML

Represents a batch of transactions as it is defined in Westpac's batch processing specification.

Optional human readable batch description.

The total amount of all the transactions in the batch (in cents).

The total number of transaction detail records (“5” Records) in the batch.

Indicates the type of transactions contained within this batch.

• CC – credit card transactions
• DD – direct debit transactions against bank accounts.

Name of the client.

The community code provided by Westpac.
Uniquely identifies the organisation within Quickstream.

The company code provided by Westpac.
Used to determine which account to process the transactions against.

Note: If required Westpac can provide with multiple company identifiers, this will allow to deposit funds into different accounts.

A human readable company name.

Currency code of the transactions within the batch.

Date when the file was created.

Time when the file was created.

Code of Merchant Account to which instance of this object is attributed to. Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.

A flag that allows to mark the batch as a refund batch.

• Set to uppercase “R” to mark all transactions in this batch as refunds. These transactions will be processed as credits to customers’ accounts.
• Leave blank to indicate all transactions in the batch are payments. These transactions will be processed as debits against your customers’ accounts.

A unique identifier for the given batch.

Note: Qvalent recommends this value to be formatted as the Unique File Identifier suffixed by the current batch number. E.g. YYYYMMDD##_NN.
Quickstream will only process a batch with a unique identifier once. Any subsequent batches with the same identifier will be rejected.

A unique identifier for the file.
QuickBatch will only process a file with a unique identifier once. Any subsequent files with the same identifier will be rejected.

Note: It is recommended to include the created date suffixed by a file sequence number to ensure the value is unique. For example, YYYYMMDD##.