AI Safety

Safe bydesign,not by luck

An AI that touches your invoices needs limits. Here is how Crox checks its own work, stays within bounds and leaves a trail you can follow.

Layers of safety

Protection before, during and after

No single safeguard is enough, so Crox has several that work together.

Before

Checks before anything is filed

  • Duplicates are flagged before an invoice is filed or paid again
  • Unclear values are marked so you can confirm them
  • Key details are read for you to review, not hidden away
During

Limits while Crox works

  • Crox acts on your command
  • Sensitive actions, such as paying an invoice, stay under your control
  • You choose what each teammate is allowed to do
After

A record and a way back

  • Every step Crox takes is kept on record
  • Deleted invoices stay recoverable in Trash
  • Finished invoices are tucked away in Archive, not lost

Boundaries

What Crox does on its own, and what it does not

Routine checking happens automatically. Anything that changes your records or moves money waits for you.

Crox does on its own

  • Reads the vendor, number, date and total
  • Flags possible duplicates
  • Marks values it is unsure about
  • Files the invoice and keeps analytics up to date

Crox does when you ask

  • Fills in missing details
  • Sets due dates
  • Updates statuses
  • Pays an invoice, always under your control

When something goes wrong

Built to catch mistakes, and to recover from them

Pick a situation to see what happens and what you can do.

Unreadable file

What happens

Crox marks the values it cannot read with confidence instead of guessing silently.

What you can do

Confirm or edit the marked values, or upload a clearer copy.

See something that looks unsafe?

If Crox ever does something you did not expect, or you spot a problem, tell us right away. A real person will read it.

Last reviewed November 2026