Skip to content

FousANZ Transactive - Global

Get your ANZ Transactive transactions through an API

Read Transaction Search results, Operating Accounts balances and payment file statuses from ANZ Transactive - Global with one API call each. Or have a workflow pull yesterday's transactions every morning and hand them to accounting.

Works with your own ANZ Transactive - Global account. Fous is an independent product.

What you can build on ANZ Transactive

  • Search account transactions

    Build this

    Runs Transaction Search for the accounts you name and a Post Date range, and reads the results grid.

    Takes
    Account numbers, post date from, post date to, credits or debits (optional)
    Returns
    Narrative, post date, value date, customer reference, bank reference, account number, account name, currency, debit amount, credit amount, tran type
  • Check uploaded payment files

    Build this

    Reads the File Import Summary screen under Payments: each uploaded file, how many transactions were valid, need repair or were rejected, and its status.

    Takes
    Uploaded since (optional)
    Returns
    File ID, file name, file type, transactions, valid, needing repair, rejected, control amount, division, uploaded on, uploaded by, status
  • List your Account Reports

    Build this

    Reads the Account Reports screen: each saved balance and transaction report profile, its format, schedule and run dates.

    Takes
    Nothing
    Returns
    Profile name, report type, format, schedule, previous run date, next run date, end date, last updated
  • Get account balances

    Build this

    Reads the Operating Accounts screen under Accounts: each account's ledger balances, available funds and when they were last updated.

    Takes
    Account numbers (optional)
    Returns
    Account name, number, type, currency, opening ledger balance, ledger balance, available funds, overdraft limit, account status, last updated

Automate ANZ Transactive with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • Yesterday's transactions, handed to accounting

    Build this
    Starts
    Every weekday at 7:30
    Step 1
    Search account transactions for each account you name, with yesterday as the Post Date.
    Step 2
    Stop when there are none.
    Step 3
    Post each transaction's references, value date and debit or credit amount to your accounting system's webhook.
  • Payment files with transactions needing repair

    Build this
    Starts
    Every weekday at 10:00 and 15:00
    Step 1
    Check uploaded payment files since the start of the day on the File Import Summary.
    Step 2
    Keep the files with transactions needing repair or rejected transactions.
    Step 3
    Keep only the files not there on the last run, and email you the list.
  • Morning cash position from Operating Accounts

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    Get account balances from the Operating Accounts screen for the accounts you name.
    Step 2
    Have an AI step total the opening ledger balance and available funds by currency.
    Step 3
    Email you the totals and each account's balances.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Search account transactions” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "transactive.online.anz.com/search_account_transactions",
    "input": {
      "accounts": [
        "012345678901"
      ],
      "post_date_from": "2026-11-11",
      "post_date_to": "2026-11-11"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "transactions": [
      {
        "narrative": "Northwind Traders inv 4471",
        "post_date": "2026-11-11",
        "value_date": "2026-11-11",
        "customer_reference": "INV-4471",
        "bank_reference": "B2611110093",
        "account_number": "012345678901",
        "account_name": "Acme Operating AUD",
        "currency": "AUD",
        "debit_amount": null,
        "credit_amount": 18240,
        "tran_type": "Credit"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

ANZ Transactive’s own options

ANZ offers ANZ Fileactive: your system sends transaction files or API messages in standard or custom formats, and end-of-day statements and intraday balances are sent back to it. It is arranged through your ANZ representative, and ANZ publishes no price. In ANZ Transactive itself you can schedule Account Reports in BAI2, CSV, MT940, PDF or XLSX and have them emailed.

OptionWhat it coversWhat it takes
ANZ FileactiveTransaction files or API messages in standard or custom formats sent from your system; end-of-day statements and intraday balances sent back to it.Arranged with your ANZ representative. No published price.
Account ReportsBalance Summary, Daily Balance and Transaction Details reports in BAI2, CSV, MT940, PDF or XLSX, run Daily, Weekly or Monthly.An ANZ Transactive user with access to the accounts. Reports can be scheduled and emailed.
ANZ Transactive by handTransaction Search, Operating Accounts, e-Statements as PDF, payment file uploads and approvals, screen by screen.A User ID issued to you, a password and a security device: a Token or ANZ Digital Key.

Read on November 12, 2026: ANZ Fileactive, ANZ Transactive - Global, Account Reports screen.

Signing in to ANZ Transactive

ANZ Transactive signs you in with your own issued User ID, a password and a security device, a Token or ANZ Digital Key, and logs you out after 15 minutes of inactivity. With Fous you sign in through ANZ Transactive's own sign-in with your own account: the login is sealed with AES-256, never returned by the API or written to logs, and code and AI agents never see it.

Worth knowing

Searches cover 12 months at a time
Transaction Search reaches back five years, but one search can span up to 12 months and the Post Date defaults to the last three months. A method takes the date range as an input.
e-Statements are PDF, six months per search
e-Statements cover the past five years, and a Date Range can be up to six months. Statements over 6000 pages fail to download, so ANZ recommends smaller ranges.
Ad hoc reports are not kept
A Balance & Transaction Report requested from Operating Accounts runs ad hoc and is not saved to the Account Reports screen. Saved, scheduled reports live on Account Reports.
Who may create and approve payments
For Asia and Pacific payments, Create Payment needs Initiator access. Company administrators amend approvers' discretion limits, and ANZ recommends different users for creating and approving payments.

More in Finance: corporate banking and credit

Other industries: e-OSCAR, Edabu, EPFO Unified Portal (Employer), Travelport Smartpoint, ARCA - servicios con Clave Fiscal, eTIMS.

Frequently asked questions

ANZ offers ANZ Fileactive: your system sends transaction files or API messages, and end-of-day statements and intraday balances are sent back to it. It is arranged through your ANZ representative, with no published price. In ANZ Transactive you can schedule Account Reports in BAI2, CSV, MT940, PDF or XLSX and have them emailed.

Five years. Transaction Search covers the last five years, with up to 12 months in one search. e-Statements are also available for statements issued in the past five years.

BAI2, CSV, MT940, PDF and XLSX, depending on the report type. Account Reports covers report types such as Balance Summary Report, Daily Balance Report and Transaction Details Report, scheduled None, Daily, Weekly or Monthly.

Open the File Import Summary screen under Payments. Each uploaded file shows its valid transactions, transactions needing repair, rejected transactions, control amount, who uploaded it and its status.

No. Fous is an independent product. You use it with your own ANZ Transactive - Global account, and a method reads and does only what that account can.

Put ANZ Transactive - Global behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextAxis Corporate Internet BankingBancaNet EmpresarialBanorte en su Empresae-OSCARHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of ANZ Transactive - Global (ANZ). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.