Get in touch

About CYOP

We audit the space between documents.

Every ERP checks a purchase order, a receipt and an invoice one at a time. Almost none of them checks the three against each other, line by line, every time. That gap is where money leaks and deliveries stall. CYOP exists to close it, without replacing the system you run.

Why we started

It starts with one invoice that doesn't match.

An invoice arrives without its PO number, or billing more than was received. AP holds it. The supplier, unpaid, holds the next shipment. A rack that was ready to go doesn't ship, and a customer date slips. Nobody did anything wrong; the documents just never agreed, and nothing compared them.

Underneath are setups nobody designed. Rapid growth, acquisitions and knowledge that lives in people's heads leave procure-to-pay workflows undefined. Consultants quote $2M and more to untangle a single one, once.

We think the checks should be continuous, explainable and cheap enough to run on every record. So we built an engine that sits on top of the ERP, reads what is already there, and says plainly what disagrees, how sure it is, and what to do.

Principles

Five rules for the rules.

Advise, never act
CYOP suggests the fix and names the records. A person decides, every time. Nothing is auto-remediated.
Show the working
Every confidence score is deterministic and comes with its reasons in plain English. If we cannot explain a finding, we do not raise it.
Read-only by design
Data flows one way, into CYOP. Checks on a draft run in a transaction and roll back. We never need write access to your ERP.
Work with the ERP you have
No migration, no replacement project. An export is enough to start, and your column names map to our fields.
Say when we can't check
A rule without the fields it needs switches off and tells you why, rather than burying you in false alarms.
The records CYOP checks against each otherPurchase orders, receipts, invoices, the vendor master, bills of materials and RFQs on one ring, with the twelve rules around them. A scanner sweeps the ring; each record lights as it is checked, with the rules that read it.POReceiptInvoiceVendorBOMRFQR1R2R3R4R5R6R7R8R9R10R11R12CheckingEvery recordR1 – R12

Where we are

Built, and next.

The engine is built and tested. The way it reaches your ERP today is an export file; direct connections are what we are building next.

Built

  • The audit engine and its twelve rules
  • Findings with confidence, exposure, fix and root cause
  • Import from CSV and Excel, with column mapping and custom fields
  • Draft and what-if checks that save nothing
  • Findings, vendor risk and first-pass yield views

Next

  • Direct connectors to ERP systems
  • Checks inside the ERP's own save step
  • Scheduled runs on new documents
  • Approved corrections pushed back into the ERP
The full availability table

How it is tested

Real orders, planted errors.

The engine is developed against 300 real federal purchase-order awards from USAspending.gov: real amounts, dates and agencies. Invoices, receipts, RFQs and BOMs are synthesized from those orders, with errors planted on purpose so that every rule has something real-looking to find.

The test suite asserts that each rule catches exactly what was planted and raises nothing on clean records, that a check leaves the database unchanged, and that an example export goes through the import with the same findings as the data it came from.

Customers, partners, investors: talk to us.

Tell us what you run and where it hurts. We'll reply by email.

Read-only. CYOP never writes to your ERP.