Accounts Payable
Live. This is the desk your AP team uses today.
For franchise and multi-store groups
AI-powered Accounts Payable automation
Drop in a vendor PDF, even one with a thousand invoices. ACCOUNT-AI learns the vendor, maps each store and GL account, and hands you a file the accounting system already understands.
How it works
- Upload the PDF. One file can hold up to 1000 invoices.
- AI groups and extracts. Samples teach the vendor, invoice number, and store.
- Review and approve. Flagged rows stay highlighted until someone checks them.
- Export or send. CSV and XLSX in your column order, or a dry-run auto-upload.
What you get
- Invoice groups learned from sample PDFs
- GL, store, and vendor mapping, including CSV import
- OCR for scanned pages, with Gemini reading the page itself
- Duplicate and validation checks
- Approval workflow and an audit trail
- Gemini, xAI, or OpenAI, including your own key
- Token cost tracked per company
- Encrypted keys and isolated company data
Modules
Accounts Receivable
Coming soon. Customer invoices will use the same review pattern.
Pricing
Every plan starts with a 14-day free trial. A card is saved up front and is not charged during the trial.
14-day free trial
Starter
$49/mo
One location group getting invoices out of email and into the books.
Start free trial14-day free trial
Pro
$149/mo
Multi-store groups, your own AI key or the platform key, and higher monthly volume.
Start free trial14-day free trial
Enterprise
$499/mo
High volume, every module, and room for the accounts receivable rollout.
Start free trialFAQ
Does the trial charge my card?
No. Stripe saves the payment method and starts the subscription with the plan’s trial days. The first charge is after the trial.
Can each company use its own AI key?
Yes. Gemini, xAI, and OpenAI keys are encrypted. A plan can also allow the platform key as a fallback.
Where does the data live?
Each company’s groups, invoices, files, and usage are stored separately. One company cannot read another.
Security
Passwords are bcrypt hashes. Sessions are HttpOnly cookies. Connector and AI keys use AES-256-GCM. Uploads stay outside the release directory. The extraction service listens only on localhost.