Trust
Security
Where your data lives, how rules run, and why no AI model decides what gets posted.
Deployed in your environment
InvoiceIQ runs in your cloud or on your hosts, and you own the code. Documents and data stay in your storage and PostgreSQL database.
Where the AI is, and where it is not
Models write rules at authoring time. At posting, approved rules run in a sandbox with no model call, so coding is repeatable.
Nothing governs money until it passes a test
- Coding rules must reproduce their stored example invoices.
- Match rules are backtested against bills you have already posted.
- Placement rules are exercised against every charge shape the composer can produce.
- Activation is refused otherwise. Every version keeps one-click rollback and an audit row naming who changed it.
Nothing posts on its own
Every posting is a person approving shown work. The golden rule is checked again after the ERP has the bill, and every attempt goes on the Posting Log.
ERP credentials
The demo build uses an in-app demo ERP with live-ERP credentials pinned empty, so a walkthrough can never reach a real accounting system.
Access
One sign-in for both products, token sessions, secrets outside the code, either product switchable off. Self-service sign-up is off by default.
Email intake
A shared mailbox is read via Microsoft Graph or IMAP, so nothing is ingested twice and old history is never back-ingested.
Want to see it rather than read about it?
A walkthrough takes an hour and starts with your own documents.