Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
This guide is part of the User Guides collection. It is the first of the Payables guides. Next, set up Payables, then read how matching works and how to work exceptions. The product page is Payables.
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

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

Those are the default owners. Your routing rules decide them, and the overdue path sends a case to a manager. See Routing.

Who does what

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.

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.

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.

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.

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.

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.

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

Payables

The product page: what Payables does and its limits.

Setting up Payables

Sources, mappings and rules.

How matching works

Every check and every exception reason.

Invoices in the supplier portal

What your suppliers see.