Skip to content

FousCommBiz

Pull your CommBiz transactions into your own systems

Build methods that read CommBiz Transaction History, Online Statements and Pending authorisations with one API call each. Or have a workflow post each account's previous-day transactions to your accounting system before the working day starts.

Start building freeBook a demo

Works with your own CommBiz account. Fous is an independent product.

What you can build on CommBiz

  • Get transaction history

    Build this

    Reads Accounts, then Transaction History for the account you pick, searched over a date range: the date, description and amount of each transaction.

    Takes
    Account, from date, to date
    Returns
    Account, date, description, amount, debit or credit

  • List online statements

    Build this

    Reads Accounts, then Online Statements for one account and statement type, such as account, merchant or corporate card statements, over a statement period.

    Takes
    Account, statement type, statement period
    Returns
    Account, statement type, statement period

  • Check pending authorisations

    Build this

    Reads the Pending authorisations list on the CommBiz homepage: the payments and requests created by your users that are waiting for an Authoriser.

    Takes
    Nothing
    Returns
    Payment type, pay from account, payee, amount, payment date

  • Create a Fast Payment for authorisation

    Build this

    Goes to Payments, then Fast Payment, fills in the pay from account, the pay to method and the payment details, and submits it for your Authorisers.

    Takes
    Pay from account, BSB and account number or another pay to method, amount, description
    Returns
    Payee, amount, pay from account, status

Automate CommBiz 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.

  • Previous-day transactions, posted to your accounting system

    Build this
    Starts
    Every weekday at 7:00, Sydney time
    Step 1
    For each account you name, get the transaction history for the previous business day.
    Step 2
    Stop when no account has a new transaction.
    Step 3
    Post each transaction, with account, date, description and amount, to your accounting system's webhook.

  • Payments still waiting for an Authoriser, before cut-off

    Build this
    Starts
    Every weekday at 15:00, Sydney time
    Step 1
    Check the Pending authorisations list.
    Step 2
    Stop when nothing is waiting.
    Step 3
    Email you the list, with payment type, pay from account, payee, amount and payment date.

  • New monthly statements, each account

    Build this
    Starts
    On the 3rd of every month at 9:00, Sydney time
    Step 1
    For each account you name, list the online statements for the last statement period.
    Step 2
    Keep the statements that were not there on the last run.
    Step 3
    Email you one line per statement, with account, statement type and statement period.

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 “Get transaction history” 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": "my.commbiz.commbank.com.au/get_transaction_history",
    "input": {
      "account": "Acme Operating Account",
      "from_date": "2026-11-10",
      "to_date": "2026-11-11"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "account": "Acme Operating Account",
    "bsb": "062-000",
    "account_number": "1234 5678",
    "transactions": [
      {
        "date": "2026-11-11",
        "description": "Direct Credit Northwind Pty Ltd INV 2291",
        "amount": 18450,
        "type": "credit"
      }
    ],
    "count": 1,
    "currency": "AUD"
  }
}

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.

CommBiz’s own options

CommBank offers APIs for NameCheck, Foreign Exchange, Fast Payments and PayTo, subject to its eligibility criteria and set up with its onboarding team. CommBiz Automated exchanges payment, account information and reporting files over SFTP for eligible customers, arranged through a Relationship Manager. In CommBiz itself you export transactions as files.

OptionWhat it coversWhat it takes
CommBank payment APIsNameCheck account checks, FX quotes and trades, Fast Payments and PayTo agreements and payments, with status updates.CommBank's eligibility criteria, its onboarding team to complete the integration, and the Bank's fees and charges.
CommBiz Automated (SFTP)BPAY, Bulk Fast Payments, Direct Entry, International Money Transfer and Priority Payments files, plus account information and reporting files.Eligible customers only, through your Relationship Manager, with SFTP connectivity, optional PGP and testing with an Implementation Manager.
CommBiz by handTransaction History exports as CSV or PDF per account, File Transfer exports as BAI2, QIF or PDF, and up to 7 years of online statements.A CommBiz service on an eligible CommBank account, and a user with permission to view the accounts.

Read on November 12, 2026: CommBank APIs, CommBiz Automated, How do I export transactions in CommBiz?.

Signing in to CommBiz

CommBiz signs you in with your log on ID and password. A security token, the eToken in CommBiz Mobile or a physical token, gives a one-time password for tasks such as authorising a transaction or Admin work, and users with only View or Create permissions do not need one. With Fous you sign in through CommBiz's own sign-in with your own account, and the login is sealed with AES-256.

Worth knowing

Exports are generated, not instant
An export from Transaction History takes a few minutes to generate: you select Refresh, then View Report. Exports reach back 25 months, each PDF export holds up to 5,000 lines, and older items are in statements.
A View user is enough for reading
Administrators set what each user sees. View users see statements, transactions and balances. With custom permissions, newly added accounts stay hidden until an Administrator updates that user's access.
Payments wait for an Authoriser
Create users can create payments, and Authorisers approve them under your authorisation rules. Authorising needs a token password, which expires after 30 seconds on a physical token and 32 in eToken.
Cut-off times, Sydney and Melbourne time
Direct credits to other banks received by 7pm are processed that day, BPAY by 5:55pm, Priority payments by 4pm and AUD international payments by 4:00pm. Fast payments have no cut-off.

More in Finance: corporate banking and credit

Other industries: CAFS, RD e-Filing, MCA21, Airbnb hosting dashboard, IESS - Portal de Empleadores, uFiling.

Frequently asked questions

Not for the CommBiz screens themselves. CommBank offers separate APIs for NameCheck, Foreign Exchange, Fast Payments and PayTo, subject to eligibility and onboarding, and CommBiz Automated exchanges payment and reporting files over SFTP for eligible customers through your Relationship Manager.

Use File Transfer, then Export, and select Request Transaction History File. It exports one or more accounts at once, in BAI2, QIF or PDF. Transaction History under Accounts exports one account at a time, as CSV or PDF.

Transaction History exports cover up to 25 months, and Online Statements go back up to 7 years. Some account statements are only available to the account owner, who must be an identified user.

No, not with View or Create permissions only. Tokens are needed by Administrators, Authorisers and Service Delegates, and for tasks that require multi-factor authentication, such as authorising a transaction.

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

Put CommBiz 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.

Start building freeBook a demo

Read nextDBS IDEALFABeAccessICICI Corporate Internet BankingCAFSHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of CommBiz (Commonwealth Bank of Australia). 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.