> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Payables works

> The path of a supplier invoice from the purchase order to a settled invoice: where each record comes from, what Coverbase checks, who owns each kind of difference, and what stays in your ERP or AP ledger.

For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt). This page is also available in markdown by appending .md to the URL.

> [!NOTE]
>
> This guide is part of the [User Guides](https://docs.coverbase.com/user-guides/overview.md) collection. It is the first of the Payables guides. Next, [set up Payables](https://docs.coverbase.com/user-guides/payables-setup.md), then read [how matching works](https://docs.coverbase.com/user-guides/payables-matching.md) and [how to work exceptions](https://docs.coverbase.com/user-guides/payables-exceptions.md). The product page is [Payables](https://docs.coverbase.com/products/payables.md).

Payables follows one supplier invoice from the PO it bills to the moment your ledger reports it paid. Coverbase owns the part in the middle: checking the invoice, turning each difference into an owned case, and keeping the supplier informed. Your procurement system still issues POs and records receipts, and your ERP or AP ledger still books, approves and pays.

The mistake people make most often is treating **Accept invoice** as approval for payment. It records that a person in Coverbase accepted the match. The invoice is approved and paid in your ledger, by your AP team, as before.

## Where each record comes from

| Record | Comes from | What Coverbase does with it |
| - | - | - |
| Purchase orders and PO lines | Your procurement system | Reads them. Never writes back. |
| Goods receipts | Your procurement system | Reads them. Never writes back. |
| Booked invoices, finance status, payment dates, payments | Your ERP or AP ledger | Reads them. Never initiates a payment or edits a financial record. |
| Invoices forwarded by email or uploaded as a PDF | Your intake address, or the intake API | Reads them with AI, then checks them like any invoice. They wait for your ledger to book them. |
| Invoices sent as EDI or JSON | The intake API | Checks them like any invoice. They wait for your ledger to book them. |
| Invoices and corrected invoices from suppliers | The supplier portal | Checks them at once, so the supplier and AP see whether they would pass. They wait for your ledger to book them. |
| Match results, cases, clocks, statements, scorecards, onboarding waves | Coverbase | Owns them. |

Every synced field keeps its source and when it was last synced. The screens print the source beside the value, so you can tell a figure your ledger sent from one Coverbase worked out.

## The flow

```mermaid theme={null}
flowchart TD
  PO["PO issued in the procurement system"] --> GR["Goods received and recorded"]
  INV["Invoice arrives: ledger, email, PDF, EDI, API or portal"] --> ID{"Supplier and PO found?"}
  ID -- "PO not received yet" --> WAITPO["Waiting for PO"]
  WAITPO -- "PO arrives" --> CHECK
  WAITPO -- "no PO after 72 hours" --> CASE
  ID -- yes --> CHECK["Checks against PO and receipts"]
  GR --> CHECK
  CHECK -- "every check passes" --> MATCHED["Matched"]
  CHECK -- "a line matched by description only" --> LINE["Case: line needs review (AP)"]
  CHECK -- "a difference" --> CASE["Case per reason, routed with a clock"]
  CASE --> OWNER{"Who owns it"}
  OWNER -- "price" --> PROC["Procurement"]
  OWNER -- "no goods receipt" --> OPS["Operations"]
  OWNER -- "billing error" --> SUP["Supplier: corrected invoice"]
  OWNER -- "everything else" --> AP["AP"]
  SUP --> CHECK
  OPS -- "receipt recorded" --> CHECK
  PROC --> DECIDE["AP accepts, or asks for a correction"]
  AP --> DECIDE
  LINE --> DECIDE
  MATCHED --> LEDGER["Ledger approves and pays"]
  DECIDE --> LEDGER
  LEDGER --> PAID["Paid status read back from the ledger"]
  PAID --> STMT["Monthly statement to the supplier"]
```

Those are the default owners. Your routing rules decide them, and the overdue path sends a case to a manager. See [Routing](https://docs.coverbase.com/user-guides/payables-setup.md#who-owns-each-exception).

## Who does what

> [card] AP
>
> Works the **Exceptions** tab. Accepts invoices that are right despite a difference, asks suppliers for corrected invoices, decides possible duplicates and confirms lines matched by description. Answers statement differences and scorecard disputes. Approves and pays in your ledger.

> [card] Procurement
>
> Owns price differences by default. Decides whether the invoiced price was agreed, or asks the supplier to reissue at the PO price. Amends the PO in your procurement system when the PO was wrong.

> [card] Operations
>
> Owns missing goods receipts by default. Records the receipt in your procurement system. When it arrives, Coverbase checks the invoice again and closes the case by itself.

> [card] Manager
>
> Receives cases whose clock ran out, and cases above an amount if your rules say so. May accept matches above AP's limit, and can be the second person who signs off when your rules require one. Reads the **Performance** tab.

> [card] Supplier
>
> Sees their invoices and why one is on hold in the supplier portal. Sends corrected invoices, replies on a mismatch, checks the monthly statement and can dispute a scorecard figure. Never sees internal notes, owner names or match details.

> [card] Admin
>
> Connects sources, maps fields, names your procurement system and AP ledger under **Source names**, and sets tolerances, routing, clocks, what suppliers see and onboarding requirements on the **Payables rules** page.

The people behind each role are set under **Team roles** on the **Payables rules** page. A case sent to a role with one person goes straight to them. With several, it waits for one of them to pick it up.

## The tabs

Open **Payables** in the left navigation. **Rules**, at the top right, opens the **Payables rules** page.

| Tab | What it is for | Guide |
| - | - | - |
| **Exceptions** | Every case, filtered to what waits on your team, on suppliers, or is resolved. | [Working exceptions](https://docs.coverbase.com/user-guides/payables-exceptions.md) |
| **Invoices** | Every invoice from every channel, with its match state and finance status. | [Invoices and statements](https://docs.coverbase.com/user-guides/payables-invoices-and-statements.md) |
| **Statements** | Monthly supplier statements and their responses. | [Invoices and statements](https://docs.coverbase.com/user-guides/payables-invoices-and-statements.md#statements) |
| **Performance** | Team metrics and supplier scorecards. | [Performance and scorecards](https://docs.coverbase.com/user-guides/payables-performance.md) |
| **Onboarding** | Supplier onboarding waves. | [Supplier onboarding](https://docs.coverbase.com/user-guides/payables-supplier-onboarding.md) |
| **Sources** | Where data comes from, its health, field mappings and every inbound and outbound event. | [Setting up Payables](https://docs.coverbase.com/user-guides/payables-setup.md) |

## What people are told, and when

Notifications go to the person who owes the next step, never to a whole team, and never to the person who just acted.

| Notification | Who receives it | When |
| - | - | - |
| A case was assigned to you | The new assignee | A case opens, is routed or is assigned to them |
| A clock is running out | The assignee, or everyone in the owner role when nobody is assigned | The clock passes its reminder point (75% by default) |
| A case escalated | The new assignee, the clock's escalation people, and everyone in the escalation role | The clock runs out, or someone escalates by hand |
| A supplier responded | The assignee | The supplier replies, disputes or sends a corrected invoice |

Suppliers receive an email, addressed to their portal's members, once when a case opens with them as its owner, when you ask for a corrected invoice or a document, when their own clock reaches its reminder point and again when it runs out, and when a statement or an amended statement is issued. Each email carries only what the portal already shows them and a link to it. Nothing is emailed to suppliers unless the **Invoices and statements** section of your supplier portal is on.

## Troubleshooting

| Problem | What to check |
| - | - |
| An invoice shows **Matched** but the supplier says it is not paid | Matching is Coverbase's check. Payment is your ledger's. Look at **Finance status** on the invoice. |
| An emailed invoice shows **Duplicate** | Expected once your ledger books the same invoice. The booked copy becomes the invoice and the emailed copy is linked to it. See [Duplicates](https://docs.coverbase.com/user-guides/payables-matching.md#duplicates-credit-notes-and-corrected-invoices). |
| An invoice sits on **Waiting for PO** | The PO it names has not arrived from your procurement system. It is checked as soon as it does. After 72 hours by default, a **PO not found** case opens for AP. |
| A case went to the wrong team | Your routing rules decide owners, first match wins. See [Who owns each exception](https://docs.coverbase.com/user-guides/payables-setup.md#who-owns-each-exception). |
| Nobody was notified about a new case | The owner role has several people or none, so nobody is assigned. Set one person under **Team roles**, or pick the case up from the queue. |

## Related

> [card] [Payables](https://docs.coverbase.com/products/payables.md)
>
> The product page: what Payables does and its limits.

> [card] [Setting up Payables](https://docs.coverbase.com/user-guides/payables-setup.md)
>
> Sources, mappings and rules.

> [card] [How matching works](https://docs.coverbase.com/user-guides/payables-matching.md)
>
> Every check and every exception reason.

> [card] [Invoices in the supplier portal](https://docs.coverbase.com/user-guides/supplier-portal-invoices.md)
>
> What your suppliers see.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.