AI clerks that run your AP,
inside NetSuite.
Clerked's AI clerks work inside NetSuite. They find invoices in your inbox, match every line to the PO and item receipt, catch billing errors before you pay them, and draft replies to vendors. NetSuite stays the system of record.
Partial receipts, matched by line
Each invoice line is matched to its PO line and item receipt in NetSuite. A line that has only partly arrived is held as waiting for receipt, and it is checked again each time a new item receipt comes in.
Coded from your NetSuite history
The clerks read the vendor bills your team has already posted in NetSuite, so each new line is coded the way your team codes it. Every correction becomes a memory in plain English that you can read, edit or delete.
Under a month to go live
On NetSuite, our average customer goes live in under a month, and our integrations never take longer than two months. We helped Curion get invoices approved before they're paid on a NetSuite instance customized since 2008.
How it works
Partial shipments are where NetSuite's own three-way match workflow stops: its documentation says the workflow doesn't support item receipts that are only partly received. Clerked compares each line with what has been received and not yet billed, so you don't pay for goods that haven't arrived. A vendor you've agreed may bill before delivery can be marked, so its bills don't wait on a receipt.
Even on NetSuite, AP is usually still done by hand around the ledger: reading the AP inbox, keying each bill, coding lines to subsidiary, department, class and location, and chasing the buyer when a price doesn't match the PO. The clerks take that work and hold what needs a person, with the reason: a price above the PO, freight nobody approved, a unit of measure the PO line doesn't use, a duplicate invoice or a missing PO number.
Invoices go into NetSuite as vendor bills, coded by line. Nothing posts until it's approved, whether approvals happen in Clerked from email or in NetSuite itself. NetSuite stays the system of record, so nothing is migrated or replaced.
Reads vendors, POs, item receipts, accounts, subsidiaries, departments, classes and locations from NetSuite
Every subsidiary in one queue, and a class or account from another subsidiary held before posting
Each PO read again from NetSuite just before the bill is written, so a closed PO line is held
Price increases, freight overcharges and duplicate invoices caught before you pay them
Vendor replies drafted from your NetSuite data, and a person reviews and sends each one
We helped Odeko replace a NetSuite tool that never learned.
Security and control
- Nothing is written to NetSuite until the invoice has passed every approval your rules call for.
- Approvals start with a person, and approvers can answer from email with no login.
- Each invoice is checked again just before it's written to NetSuite, and one that wouldn't post cleanly is held for your team.
- Approved invoices go to whatever pays them today.
