Clerked

Quick Verdict

Clerked is the renamed successor to Mod AI, positioned as an autonomous accounts-payable platform. Its AI clerk receives invoices from the AP inbox and supports extraction, GL coding, PO matching, approval routing, payment preparation, and ERP synchronization. It targets finance organizations with meaningful invoice volume, multiple entities, or complex accounting systems. The same scope that can reduce manual work also makes this high-impact automation: it touches supplier identity, bank details, accounting records, approvals, and real money.

“Touchless” should not mean removing financial controls. Deployments need least privilege, segregation between preparation, approval, and fund release, dual control for critical payments, and independent callback verification for new suppliers or bank-detail changes. Model decisions, overrides, ERP writes, and payment actions should be auditable. The public website privacy policy explicitly excludes product data, so it does not establish how invoice, ERP, email, supplier, bank, and payment data are handled in the product. Obtain a product DPA, security addendum, and subprocessors list before using production records.

Best For

• Mid-market AP teams where inbox triage, coding, and approval chasing are recurring bottlenecks
• Multi-entity or multi-ERP organizations wanting a common intake layer while retaining the ERP as system of record
• Finance teams with mature controls for role separation, payment limits, vendor-master validation, and audit
• Organizations willing to phase deployment from read-only recommendations to controlled writes and only then payment scope
• Not ideal for very low invoice volume, teams without procurement controls, unsupervised payment release, or buyers unable to obtain a product-data DPA and current security evidence

Key Features

• AP inbox and invoice processing for extracting headers, amounts, tax, line items, PO references, and payment terms
• GL coding and matching using accounting context, with two-way or three-way invoice matching and exception routing
• Approval workflows based on entity, amount, department, supplier, or anomaly, including policies expressed in natural language
• Payment orchestration around due dates, discounts, and cash plans, subject to appropriate human authorization
• Bidirectional ERP synchronization across listed integrations including QuickBooks, NetSuite, Xero, SAP, Oracle, Workday, Dynamics, and Sage Intacct
• Exceptions and audit history for document status, mismatches, approval events, overrides, and operational review

Use Cases

• Classify invoices, credit notes, statements, and supplier questions arriving in shared AP inboxes
• Extract multi-page invoices and propose GL or cost-center coding for accountant review
• Compare purchase orders, receipts, and invoices, then queue quantity, price, tax, and duplicate exceptions
• Route approvals and prepare payment batches while reserving fund release for an independent approver
• Support close and audit samples with open-item, rejection, approval-time, and override records

Pricing

Clerked is proprietary B2B software sold through sales-led, custom commercial terms. Although the website has used starting-price language, actual cost can vary with invoice volume, entities, ERP choice, integration depth, payment scope, implementation, and support. Public marketing figures should not be treated as a fixed contract price, and there is no verified permanent free plan.

Request a total-cost proposal covering implementation, migration, custom connectors, overages, support, renewal increases, and exit exports. A proof of concept should measure straight-through processing, escaped errors, handling time, and payment risk across realistic no-PO invoices, partial receipts, credits, duplicates, bank changes, cross-entity documents, and tax exceptions.

Pros

• Broad workflow from AP inbox through ERP and payment preparation can reduce handoffs between point tools
• Separating routine invoices from exception queues can focus staff on judgment-heavy cases
• A broad published integration catalog helps teams check initial ERP fit
• Natural-language policies can make finance rules easier to express when backed by explicit approvals and audit trails
• With segregation and dual control retained, automation can improve throughput without eliminating internal controls

Cons

• Custom pricing and implementation dependency make total cost hard to determine from the website
• Product-data DPA, subprocessors, retention, and invoice/ERP/payment handling cannot be established from the website privacy page alone
• Public material supports SOC 2 as pursued or in progress, not as a completed certification without current evidence
• Autonomous payment scope creates direct loss risk from configuration, identity, or master-data errors
• Accuracy depends heavily on customer documents, chart of accounts, supplier history, and integration quality
• Chinese invoicing, tax, banking, and cross-border data fit lacks sufficient public evidence

Alternatives

FAQ

What is the relationship between Clerked and Mod AI?

Clerked is the new brand and product destination for the former Mod AI. The old entry is retained only as a draft archive; they should not be treated as separate current products.

How much does Clerked cost?

It uses sales-led custom pricing. Obtain a scoped quote based on invoices, entities, ERP integrations, payment capabilities, implementation, and support rather than relying on a marketing starting price.

Is Clerked SOC 2 certified?

Available public information supports only that SOC 2 is being pursued or is in progress. Buyers should request current evidence and inspect the report scope, audit period, and exceptions.

Does the website privacy policy cover invoice and ERP data?

No. The public website policy explicitly excludes product data. Production invoices, email, ERP, supplier, bank, and payment data need a separate product DPA, security terms, subprocessors disclosure, and retention/deletion commitments.

Should Clerked approve and release payments autonomously?

Not without strong controls. New vendors, bank changes, large amounts, and anomalies should require independent verification, dual authorization, and an auditable human release.

What is a safe pilot sequence?

Start with synthetic or redacted data in read-only mode, then enable coding recommendations and low-risk ERP writes. Consider money movement only after permissions, audit logs, rollback, vendor verification, and dual payment control pass review.

Bottom Line

Clerked may be useful for high-volume AP operations, but it is a high-impact financial system rather than a routine productivity add-on. Validate the product-data contract and security evidence first, run a read-only proof of concept second, test ERP writes and exception handling third, and discuss payment scope last. If the vendor cannot clearly document DPA coverage, SOC 2 status, tenant segregation, audit logs, and exit procedures, or if the buyer lacks segregation of duties and dual control, autonomous payment access should remain disabled.