# Pull your Coles remittances and claims into your systems

> Read your remittances and your claims and transactions from the Coles Supplier Portal with one API call per supplier group. A workflow can then hand each new remittance to accounting every weekday morning, before anyone matches payments by hand.

Page: https://fous.com/automate/coles-supplier-portal
Updated: 2026-11-12

Works with your own Coles Supplier Portal account. Fous is an independent product.

## What you can build on the Supplier Portal

### Get remittances

Reads the remittances on the Coles Supplier Portal for one supplier group, with the invoices each payment covers.

- Takes: Supplier group, paid since (optional)
- Returns: Remittance reference, payment date, amount paid, invoices covered, deductions

### Get claims and transactions

Reads claims and transactions on the Coles Supplier Portal for one supplier group, from a date you choose.

- Takes: Supplier group, since (optional)
- Returns: Claim or transaction reference, date, type, description, amount

### List users and permissions

Reads View and manage users / contacts on the Coles Supplier Central dashboard for one supplier group, including who is the Super User.

- Takes: Supplier group
- Returns: Name, email address, user type, status

### Send a General Enquiry

Fills in the General Enquiry form on Coles Supplier Central with your subject and question, and submits it.

- Takes: Supplier group, subject, question
- Returns: Confirmation shown, submitted at

## Automate the Supplier Portal with a workflow

A [workflow](/product/workflows) 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.

### New Coles remittances, handed to accounting

Starts: Every weekday at 8:00

1. For each supplier group you name, get the remittances paid since yesterday.
2. Keep the remittances that were not there on the last run, and stop when there are none.
3. Post each one, with its invoices and deductions, to your accounting system's webhook.

### New claims and transactions, every weekday morning

Starts: Every weekday at 9:00

1. For each supplier group, get the claims and transactions from the last 30 days.
2. Keep the ones that were not there on the last run.
3. Email you the list, one section per supplier group, with each amount.

### Monthly review of Supplier Central users

Starts: On the 1st of every month at 9:00

1. For each supplier group, list the users and their user type.
2. Keep the users added, removed or changed since the last run.
3. Email you the changes, with who the Super User is.

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](/product/methods), it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get remittances” 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": "supplierportal.coles.com.au/get_remittances",
    "input": {
      "supplier_group": "Acme Foods",
      "paid_since": "2026-11-02"
    }
  }'
```

Example response:

```
{
  "status": "completed",
  "data": {
    "supplier_group": "Acme Foods",
    "remittances": [
      {
        "reference": "RM-204817",
        "payment_date": "2026-11-10",
        "amount_paid": 48215.6,
        "currency": "AUD",
        "invoices": [
          {
            "invoice_number": "INV-55102",
            "amount": 31480
          }
        ],
        "deductions": [
          {
            "reference": "CL-90331",
            "description": "Promotional claim",
            "amount": -1184.4
          }
        ]
      }
    ],
    "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.

## The Supplier Portal’s own options

Coles documents no API for the Supplier Portal or Supplier Central. Its electronic trading is EDI: purchase orders, despatch advices and invoices, by EDI or by Colladium webforms, once you pass Coles accreditation testing with its eCommerce implementation team. Remittances, claims and transactions, and bank details stay on the Supplier Portal.

| Option | What it covers | What it takes |
| --- | --- | --- |
| Coles EDI | Purchase orders from Coles, and despatch advices and invoices back to Coles. | Coles accreditation testing first, with the eCommerce implementation team: Coles sends a test purchase order, then gives the go-live date. |
| Colladium webforms | The same purchase orders, despatch advices and invoices, keyed into web forms instead of your own EDI system. | Your supplier details with your GLN, five sample products, and the accreditation tasks done with Colladium and Coles. |
| The Supplier Portal and Supplier Central by hand | Remittances, claims and transactions and bank details on the Supplier Portal; users, enquiries and Cost Price Alteration requests on Supplier Central. | Your email address as username, or a user ID for each supplier group if you belong to several. |

Read on November 12, 2026: [Coles Supplier Portal](https://www.supplierportal.coles.com.au/), [Coles accreditation testing (Colladium)](https://support.colladium.com/support/solutions/articles/7000061494), [Coles Supplier Central: Supplier Information](https://suppliercentral.coles.com.au/s/knowledge-centre).

## Signing in to the Supplier Portal

Coles signs you in with a username and password. Your username is your email address if you belong to one supplier group, or a separate alphanumeric user ID such as ABC123 for each supplier group if you belong to several. With Fous you sign in once through Coles's own sign-in with your own account: the login is sealed with AES-256, and an expired session is signed back in.

## Worth knowing

- **One user ID per supplier group**: If your email address is linked to several supplier groups, it no longer works as a username. Each group has its own alphanumeric user ID, and the Supplier Portal for a group needs that group's ID, so a method takes the group as an input.
- **Two sites: Supplier Portal and Supplier Central**: Remittances, claims and transactions, bank details and your accounts receivable email are still on the Supplier Portal. Users, enquiries, Cost Price Alteration requests and dashboard reports are on Coles Supplier Central.
- **Your Super User manages access**: Each organisation has a Super User (Administrator), shown with that user type in View and manage users / contacts on the Supplier Central dashboard. Your other user IDs are listed under My Permissions.
- **EDI starts with accreditation testing**: Before B2B scan receiving and electronic invoicing, you pass Coles accreditation testing: Coles sends a test purchase order, you return a despatch advice and an invoice, and you ship no goods.

## More in Retail: vendor portals (international)

- [Asda Supplier Portal](https://fous.com/automate/asda-supplier-portal.md)
- [Kaufland Business Partner Portal](https://fous.com/automate/kaufland-business-partner-portal.md)
- [Morrisons Supplier Portal](https://fous.com/automate/morrisons-supplier-portal.md)
- [REWE Group Supplier Portal](https://fous.com/automate/rewe-group-supplier-portal.md)
- [Tesco Partners Toolkit](https://fous.com/automate/tesco-partners-toolkit.md)
- [Woolworths Partner Hub](https://fous.com/automate/woolworths-partner-hub.md)
- [Cenconline B2B](https://fous.com/automate/cenconline-b2b.md)

Other industries: [T-Mobile for Business Account Hub](/automate/t-mobile-for-business-account-hub), [GreenSky merchant portal](/automate/greensky-merchant-portal), [Basware Portal](/automate/basware-portal), [Comarch ERP Optima](/automate/comarch-erp-optima), [微信公众平台](/automate/wechat-official-accounts-platform), [AutoZonePro](/automate/autozonepro).

## Frequently asked questions

### Does the Coles Supplier Portal have an API?

No, Coles documents no API for the Supplier Portal. Purchase orders, despatch advices and invoices can go by EDI or Colladium webforms once you pass Coles accreditation testing. Remittances, claims and transactions stay on the Supplier Portal, where you read them by hand.

### Why can't I sign in to Coles Supplier Central with my email address?

Your email address works as a username only if it is linked to one supplier group. If it is linked to several, you sign in with the alphanumeric user ID for one of those groups, in the format ABC123. Your other user IDs are listed under My Permissions.

### Where do I find Coles remittances and claims?

On the Coles Supplier Portal, not on Supplier Central. Remittances, claims and transactions, bank account details and your registered business address are among the functions still on the Supplier Portal.

### How do I start sending Coles invoices by EDI?

You pass Coles accreditation testing first. You complete registration tasks such as your supplier details with your GLN and five sample products, Coles sends a test purchase order, and you send back a despatch advice and an invoice. Questions go to the Coles eCommerce implementation team.

### Is Fous affiliated with Coles Group?

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

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Coles Supplier Portal (Coles Group). 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.
