AI clerks that run your AP,
inside BST.
Clerked's AI clerks work inside BST. They find invoices in your inbox, code every line to the company, project and task it's charged to, catch billing errors before you pay them, and draft replies to vendors. BST stays the system of record.
Every line on the right company
In BST, the company that pays an invoice often isn't the company each line charges. Clerked sets the paying company on the invoice and the line company on every line, then codes the account and organization from that company's chart.
Coded to the project and task
Each line is coded to the project, phase and task it's charged to, from the project number on the invoice or how your team coded it before. Overhead stays off projects, and a line for a closed project is held for your team.
Under a month to go live
On BST, our average customer goes live in under a month, and our integrations never take longer than two months. We helped Wade Trim get supplier invoices coded by line and drafted straight into on-prem BST.
How it works
The usual AP tools skip BST. BST does the ledger and the project books, and AP is still manual: someone keys each vendor invoice and decides, line by line, which company it charges, which project and task it belongs to, and whether it's chargeable or overhead. Clerked's clerks take that part.
They learn your vendors, projects and coding from your BST history before they start, and every correction your team makes becomes a memory in plain English that you can read, edit or delete. Approvals can stay in BST, so your auditors don't have to go into a second system.
Invoices go into BST as draft vendor invoices, coded by line. Nothing posts until it's approved, whether approvals happen in Clerked from email or in BST itself. BST stays the system of record, so nothing is migrated or replaced.
Reads vendors, GL accounts, organizations, projects, phases, tasks and payment terms from BST
Each invoice set to the BST company that pays it, and each line to the company it charges
Coded by posting type: task accounts get a project and task, non-project accounts stay off projects
Subconsultant and reimbursable lines coded to chargeable tasks, so they can be billed to the client
Duplicate invoices, inactive accounts and lines that don't add up caught before you pay them
Security and control
- Each invoice goes into BST as a draft vendor invoice, and it becomes a voucher only after it's approved.
- Approvals start with a person. They can stay in BST, and approvers outside BST answer from email with no login.
- Each invoice is checked again just before it goes into BST, and one that wouldn't go in cleanly is held for your team.
- Approved invoices go to whatever pays them today.
