AP Match
Match the invoice to the purchase order and the receiving record. Quantity and price gaps are flagged before anyone pays.
WorkUnit Labs
Companies need the work done. They do not need to hire engineers, keep models, or supervise a stack of agents. WorkUnit Labs takes a defined process, runs it on shared infrastructure, and returns completed work. You pay for what passes, not for seats, tokens, or hours.
The documents, records, or events a unit receives. For invoices, that is a PDF, scan, or photo.
AI reads the work. Deterministic rules check it. The model does not get the last word.
A unit finishes only when the checks are true. Totals, duplicates, required fields, dates.
Anything that cannot be verified is flagged and reviewed. It is never guessed and never billed.
A finished deliverable. For invoices, a file ready for QuickBooks Online or Xero.
Accuracy, turnaround, and cost are counted on accepted work. That is the record.
Add-ons
These do not run on a bare invoice. They run when you send the purchase order and receipt, the payment, or the close file. A gap in those documents is flagged. It is not invented.
Match the invoice to the purchase order and the receiving record. Quantity and price gaps are flagged before anyone pays.
Match payments to open invoices, read the remittance, and separate a short pay from cash that does not apply.
Prepare the month-end file. Missing support, breaks, and exceptions are listed before the close, not after it.
The units
Invoices are the work you can start today. AP Match, Cash Match, and CloseReady are add-ons. Everything else on this map is not offered yet.
Extract every field, math-check the totals, catch duplicates, and return an entry ready for QuickBooks Online or Xero.
Match the invoice to the purchase order and the receiving record. Quantity and price gaps are flagged before payment.
Match incoming payments to invoices, read remittance advice, and separate short pays from cash that does not apply.
Read receipts, match them to card transactions, check policy, and catch a duplicate before the report is approved.
Gather the support for month-end. Missing records, breaks, and exceptions are listed before the close.
Pull supplier details, check required fields, catch a duplicate vendor, and prepare a record the ERP can take.
Normalize a spreadsheet, name the duplicates, and flag rows that fail the rules you already use.
Pull the dates, parties, amounts, and renewal terms. Incomplete clauses are flagged, not filled in.
Check a file against a schema. Bad types, missing keys, and conflicting rows come back as a list.
Classify each incoming request, set a priority, and route it. Unresolved cases are escalated, not closed.
Draft the response from the case and the policy. A person sends it. The unit does not.
Confirm the case has the fields a resolved ticket requires, and send back the ones that do not.
Compare the order, the invoice, and the delivery. Mismatches are listed before anyone pays.
Clean account records, fill only what a source supports, and write a short summary of what changed.
Check onboarding documents for completeness and keep the employee record to the fields you approved.
Extract a claim file, confirm the required documents, and flag an inconsistency instead of deciding it.
Read delivery documents, reconcile them to the order, and list the exceptions.
Classify a refund request against the order and the policy, and hold anything the documents do not support.
Collect the evidence, check that each item is present, and assemble the package. Gaps stay visible.
Validate a lead against the fields sales already requires, and drop duplicates before they enter the CRM.
One intake, several units, one report of what finished and what was sent back.
High-volume extraction across the document types you name, with the same pass-or-flag rule.
Watch the units that are running, score them against the checks, and stop a run that drifts.
A process you define: the input, the checks, the exception path, and the file you get back.
You pay for accepted work. Not for seats, tokens, or hours. An invoice that fails a check is the model. Later units will be priced the same way, once each one can prove the same thing.