> ## 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.

# Working exceptions

> Work the Payables exceptions queue and a single case: read the checks and the lines, accept an invoice, ask the supplier for a corrected invoice or a document, send a note to the procurement system, route, escalate, resolve and reopen, and how response clocks pause, resume and escalate.

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. For why a case opened, see [How matching works](https://docs.coverbase.com/user-guides/payables-matching.md). For the rules that route cases and set clocks, see [Setting up Payables](https://docs.coverbase.com/user-guides/payables-setup.md). For the invoices behind the cases, see [Invoices and statements](https://docs.coverbase.com/user-guides/payables-invoices-and-statements.md).

A case is one difference on one invoice, or one question from a supplier, with one owner and one clock. The **Exceptions** tab lists them. A case page shows the evidence and every action you can take.

The mistake people make most often is messaging the supplier when the invoice is actually waiting on your own team. Read **With** and the recommendation first. A missing goods receipt is your operations team's to fix, and the supplier has already been told no action is needed from them.

## The queue

Open **Payables**. The **Exceptions** tab opens first.

![Exceptions tab with tiles for overdue, due today, assigned to you and first-pass match over 30 days, view buttons for cases waiting on us, all open, waiting on suppliers and resolved, a search box, an owner filter, and the list of cases](https://mintcdn.com/coverbase/05b6jNSp_zOf8kTZ/images/user-guides/payables/internal/01-exceptions-queue.png?fit=max\&auto=format\&n=05b6jNSp_zOf8kTZ\&q=85\&s=10a9c1ff1c68cc8de8d4353715e1dc88)

The Exceptions tab, filtered to cases that wait on your team.

The tiles count **Overdue** cases, cases **Due today**, cases **Assigned to you**, and the **First-pass match, 30 days** rate with the invoices behind it.

| View | Shows |
| - | - |
| **Waiting on us** | Open cases an internal owner owes the next step on. |
| **All open** | Every open case. |
| **Waiting on suppliers** | Open cases where the supplier owes the next step. |
| **Resolved** | Closed cases, with how each was resolved. |

Narrow the list with **Find invoice, PO, or supplier** and the **Owner** filter. Each row shows the reason and case number, the supplier with its invoice and PO, **At stake**, **With** (the owner role and the person), **Clock** and **Opened**. The clock reads the time left, the time overdue in red, **Paused**, or **No clock** when the owner has no clock in your rules.

A link from a metric on the **Performance** tab opens the queue filtered to the cases behind it. **Show all cases** clears that filter.

## A case

Click a row to open the case.

![Case page for a price difference with Accept invoice, Route to someone else and Actions at the top, the recommended next step and checks, the invoice against its PO with the price difference highlighted on one line, documents, activity with the automatic escalation, and the ownership panel showing the case with a manager, overdue, escalated, routed by the price rule, with time held by procurement and the manager](https://mintcdn.com/coverbase/05b6jNSp_zOf8kTZ/images/user-guides/payables/internal/02-case-29-overdue-buyer-escalated.png?fit=max\&auto=format\&n=05b6jNSp_zOf8kTZ\&q=85\&s=caeb09732cd583703e722ad93541b831)

A price difference past its deadline, escalated to a manager.

From top to bottom:

* **Recommended next step.** What Coverbase suggests, then each failed or warning check with what was expected and what was invoiced, then the checks that passed. See [the checks](https://docs.coverbase.com/user-guides/payables-matching.md#the-checks).
* **Coverbase AI reading.** When Coverbase AI explained the mismatch, its explanation and the fields it read. A suggestion, not a decision.
* **Invoice against PO.** The invoice and the PO, each with the system it came from and when it synced. The lines table compares **Ordered**, **Received**, **Billed**, **Quote price**, **PO price** and **Invoice price** per line, with how each line was matched. Under it: **PO total**, **Freight**, **Tax**, **Invoice total** and **Difference**.
* **Documents.** Every version of the invoice (**Current** or **Replaced**) and the channel it came by, the quotes and goods receipts on the PO, and the finance status your ledger reported.
* **Activity.** Every event on the case. Entries the supplier can read say **Shared with the supplier**.
* **Ownership.** **With**, **Clock** and how much of its target is used, **Escalated**, **Routed by** (the rule that chose the owner), **Round trips** to the supplier and back, and **Time with each owner**.
* **What the supplier sees.** The sentence on the supplier's portal for this invoice. Internal notes, owner names and match details stay hidden.

## Actions

The buttons at the top depend on the recommendation. **Ask the supplier for a corrected invoice** puts **Request corrected invoice** first. **Likely a match** puts **Accept invoice** first. Otherwise **Route to someone else** is first and **Accept invoice** sits beside it. Everything else is under **Actions**, including **Request corrected invoice** on every open case that has an invoice, and **Run the checks again**.

![Case page with the Actions menu open, listing Ask for a document, Escalate, Mark as duplicate, Resolve and Run the checks again](https://mintcdn.com/coverbase/05b6jNSp_zOf8kTZ/images/user-guides/payables/dialogs/08-case-actions-menu.png?fit=max\&auto=format\&n=05b6jNSp_zOf8kTZ\&q=85\&s=bbcd449d789e7e54c64800cd1ec145d8)

The Actions menu on an open case.

Each action opens a dialog that names its effect and says who will read your note: the supplier, or only your team.

### Accept invoice

Records that you accepted the invoice despite the differences. Write a reason, then click **Accept invoice**.

Under **Line mapping**, the dialog lists each invoice line with the PO line it was matched to. If a suggestion is wrong, pick the right PO line from the list. The checks run again with your mapping before the invoice is accepted, so a line you move is checked for price and quantity against the PO line you chose. The activity records each change, such as "Invoice line ... moved from PO line ... to PO line ...", and the line then shows **mapped by reviewer**.

![Accept as invoiced dialog explaining that it records the acceptance despite the differences and does not change the invoice in the ledger, with a required reason field](https://mintcdn.com/coverbase/05b6jNSp_zOf8kTZ/images/user-guides/payables/dialogs/09-accept-dialog.png?fit=max\&auto=format\&n=05b6jNSp_zOf8kTZ\&q=85\&s=c0159008f5ea717be375397bf2e1c6d5)

Accepting an invoice as invoiced. A reason is required.

Accepting:

* Marks the invoice **Matched** and every mapped line verified.
* Resolves every open match case on the invoice: **Price accepted** for a price difference, **Match accepted** for the rest. The supplier sees "Resolved. The invoice was accepted against the purchase order."
* Teaches Coverbase the lines you confirmed. See [Description mappings](https://docs.coverbase.com/user-guides/payables-matching.md#description-mappings).
* Sends the decision to your ledger, if **Send match decisions** is on. The activity then shows that the decision was sent to finance.

It does not change the invoice in your ledger, approve it for payment or pay it.

When your rules require a second person above an amount, the case shows "Accepted. A second person signs off before it goes to finance." Someone else with authority clicks **Sign off**. The person who accepted cannot. You can accept only up to the limit your role has under **Who may accept a match**. Above it you see "You can accept matches up to ... Route this one to a manager."

### Request corrected invoice

Asks the supplier to reissue the invoice. It is the main button when the recommendation is **Ask the supplier for a corrected invoice**, and it is under **Actions** on every other open case that has an invoice. A price difference can be the supplier's error even when the checks suggest otherwise. The message starts with the sentence the supplier already sees. Edit it to say exactly what to fix, then **Send request**.

![Request corrected invoice dialog over a price difference case, with the message to the supplier prefilled and a Send request button](https://mintcdn.com/coverbase/05b6jNSp_zOf8kTZ/images/user-guides/payables/dialogs/11-request-corrected-invoice-dialog.png?fit=max\&auto=format\&n=05b6jNSp_zOf8kTZ\&q=85\&s=dcbb69fce2561adbd391f33792d7ca96)

Requesting a corrected invoice from the Actions menu. The message is what the supplier reads.

![Price difference case with the clock paused, time split between procurement and the supplier, activity showing the request for a corrected invoice shared with the supplier and the clock pausing, and the supplier view showing the message asking them to reissue at the PO price](https://mintcdn.com/coverbase/05b6jNSp_zOf8kTZ/images/user-guides/payables/internal/03-case-30-price-mismatch-correction.png?fit=max\&auto=format\&n=05b6jNSp_zOf8kTZ\&q=85\&s=974dcd2abab6d8605ab98ba49617f32c)

A price difference where procurement asked for a corrected invoice. The clock is paused while the supplier owes the next step.

The supplier sees your message and an upload button in their portal, and their portal members are emailed. The case waits on them, and its clock pauses if your rules say so. When they send a corrected invoice, it becomes a new version, the checks run on it, and a difference it fixed resolves itself. When they reply instead, the case comes back to its owner and the clock resumes.

### Ask for a document

The same as a correction request, for a document instead: a proof of delivery, a signed quote, a credit note. The supplier uploads it in their portal.

### Message supplier and internal notes

Under **Activity**, **Internal note** is for your team only. Type `@` to mention a teammate. **Message supplier** goes to the supplier's portal. The box says which one you are writing.

### Send a note to the procurement system

The action reads **Send a note to** followed by your procurement system's name, as set under **Source names**. On a **No goods receipt** case, when your rules turn on case notes to the procurement system, this adds your note to the PO there for operations to see. It does not record a receipt or change the PO. Operations records the receipt in the procurement system, and when it arrives, the case resolves itself.

### Route to someone else

Hands the case to another owner role: AP, Operations, Procurement, Supplier or Manager. The new owner gets a new clock. Time with the previous owner stays in the history.

For an internal role, **Person** picks someone in it, or **Anyone in** the role. Only people set up for that role under **Team roles** are listed, and the person you pick is notified. With **Anyone in** the role and one person in it, the case is assigned to them. When nobody is set up for the role, the dialog says so and the case goes to the role.

![Route this case dialog with Route to set to Procurement, a Person picker reading Anyone in Procurement, a note that only people set up under Team roles are listed, and a Reason field](https://mintcdn.com/coverbase/05b6jNSp_zOf8kTZ/images/user-guides/payables/dialogs/10-route-to-person-dialog.png?fit=max\&auto=format\&n=05b6jNSp_zOf8kTZ\&q=85\&s=33bc8cd70f4147806aa3861f9448dcc8)

Routing a case to Procurement, with a Person picker for the people set up in that role.

### Escalate

Sends the case to the escalation role of its clock (a manager by default) and keeps the clock running. Escalating does not reset the deadline, so an overdue case stays overdue until someone acts.

### Mark as duplicate

The invoice stays on record and is left out of matching. Open cases on it resolve as **Duplicate voided**. The supplier sees its status as **Duplicate**. Void it in your ledger too.

### Resolve and Reopen

**Resolve** stops the clock with a **Resolution**: **Supplier sent a corrected invoice**, **Goods receipt recorded**, **Invoice price accepted**, **PO amended**, **Credit note issued**, **Duplicate voided**, **Match accepted**, **Statement confirmed**, **Scorecard figure corrected**, **Scorecard figure upheld** or **No action needed**. Use it when the fix happened outside Coverbase.

**Reopen** brings a resolved case back to its owner with a fresh clock. A reason is required. The earlier resolution stays in the history.

### Run the checks again

Reruns matching on the invoice with the latest PO, receipts and rules. Use it after changing a tolerance. Reasons that no longer apply resolve their cases.

## Line review and Coverbase AI

A **Line needs review** case means every check passed but at least one line was matched only by its description, or suggested by Coverbase AI. The lines table shows, for each such line, the PO line, the invoice's own wording under **Invoice:**, and the similarity or **Suggested by Coverbase AI**.

![Line needs review case with Accept invoice as the main action, warnings on two lines matched by description, and a lines table showing each PO line with the supplier's abbreviated description beneath it](https://mintcdn.com/coverbase/05b6jNSp_zOf8kTZ/images/user-guides/payables/internal/05-case-32-line-review-ai-assist.png?fit=max\&auto=format\&n=05b6jNSp_zOf8kTZ\&q=85\&s=4de29251bb2a40775809c625b7615147)

A line review: each line shows the PO description, the supplier's own wording and how similar they are.

Compare part numbers, units and quantities. When Coverbase AI explained the case, read its panel: it names the lines and the words or numbers it relied on. If the lines are right, click **Accept invoice**. Coverbase remembers the mapping for the next invoice from this supplier. If a line is wrong, pick the right PO line under **Line mapping** in the same dialog. If no PO line fits, ask the supplier for a corrected invoice that quotes the PO line or part number.

An **Invoice reading to check** case means AI read an emailed or uploaded invoice and was unsure of a field that matching uses. The **Invoice read with confidence** check lists the fields. Open the invoice drawer, compare those fields under **Source record** with **Open PDF**, then accept the invoice if the reading is right. If it is wrong, ask the supplier for a corrected invoice or a clearer copy. See [Reading emails and PDFs with AI](https://docs.coverbase.com/user-guides/payables-matching.md#reading-emails-and-pdfs-with-ai).

## Clocks, pauses and escalation

**1. The clock starts**

When a case opens or is routed to a new owner, it gets that owner's clock from your rules, counted in business hours on your calendar or in calendar hours. The **Clock** column's tooltip says which, such as "Counted in business hours.", and **Ownership** shows the time used against the target in business time or calendar time.

**2. It pauses while the supplier owes the next step**

When you request a correction or a document, an internal owner's clock pauses if its rule says **Pause while waiting on the supplier**. The activity shows "paused the clock". It resumes, with the time it had left, when the supplier replies.

**3. The supplier's own clock never pauses**

A case routed to the supplier runs the supplier's clock. When they reply or send a correction, the case returns to AP with a new AP clock, for AP to review what they sent.

**4. It reminds**

At the rule's **Remind at (% used)**, 75% by default, the assignee is notified, or everyone in the owner role when nobody is assigned. A supplier who owns the case is emailed and sees a reminder in their portal, and is reminded once more when the clock runs out.

**5. It escalates**

When the clock runs out, the case escalates once to the rule's **Escalate to** role: a manager for internal owners, AP for the supplier. The activity records it with the rule's name. The original deadline stays.

**6. It stops**

Resolving a case stops its clock.

Each running stretch is stored, so **Time with each owner** is measured, not estimated. Cases without a clock are left out of clock metrics, and the **Performance** tab says how many.

## Troubleshooting

| Problem | What to check |
| - | - |
| The person I want is not in the **Person** list | Only people set up for that role under **Team roles** are listed. Add them there first. |
| There is no **Accept invoice** button | The invoice was replaced by a newer version, so decide on the current one, or your role may not accept matches. |
| "Your role may not accept matches" | Your organization named who may accept under **Who may accept a match**. Route the case to AP or a manager. |
| "A newer version of this invoice replaced it" | The supplier sent a corrected invoice. The case moved to it. Reload the case. |
| "A decision is already recorded on this match" | Someone decided already. **Run the checks again** to decide afresh. |
| The supplier says they never got the request | Their portal members are emailed only when the **Invoices and statements** portal section is on. Check their team in the portal. |
| A case went to the supplier but nobody emailed them | A case that opens routed to the supplier emails their portal members once, when it opens. Nothing is sent when the **Invoices and statements** portal section is off. Use **Request corrected invoice** to email them again with your own message. |
| A case closed by itself | A rerun no longer found the difference: a receipt arrived or a corrected invoice fixed it. The activity says so. |
| The clock still shows overdue after escalating | Escalation keeps the deadline. Act on the case, or route it. |

## Related

> [card] [How matching works](https://docs.coverbase.com/user-guides/payables-matching.md)
>
> Why each case opened.

> [card] [Setting up Payables](https://docs.coverbase.com/user-guides/payables-setup.md)
>
> Routing, team roles and clocks.

> [card] [Performance and scorecards](https://docs.coverbase.com/user-guides/payables-performance.md)
>
> Where cases wait and how clocks are met.

> [card] [Invoices in the supplier portal](https://docs.coverbase.com/user-guides/supplier-portal-invoices.md)
>
> What the supplier sees when you ask them.


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