Creytix Expenses
Policy checks before the reimbursement, not after the argument.
An expense engine with per-category policy limits, receipt requirements, mileage at a set rate, reimbursement runs, and journal entries for both the expense and the payout.
The policy answer arrives with the expense, not a week later.
What it does for you
The policy runs, it does not just exist
Category limits and receipt thresholds are checked when the expense is entered. A written policy nobody applies is the same as no policy.
Company card and personal card are different questions
A card charge is an expense. A personal payment is an expense AND a debt to the person. The engine keeps them apart and only the second creates a reimbursement.
Mileage without a spreadsheet
Distance and rate produce the expense, at whatever rate the period uses.
Capabilities
- Per-category policy limits
- Receipt-required thresholds
- Mileage at a configured rate
- Reimbursement runs by person
- Expense and reimbursement journal entries
Proof, not adjectives
- Engine ships and is tested
- src/lib/expenses/engine.ts — policy check, mileage, reimbursement runs and both journal-entry writers, covered by its own suite.
Related tools
- Creytix BooksA double-entry ledger engine — not a replacement for QuickBooks today.Learn more →
- Creytix PayrollIn-suite payroll-lite — timesheets and gross pay today, Wyoming-first.Learn more →
- Creytix PurchasingThree-way match, approval thresholds, and what you have actually committed to spend.Learn more →
Built with Creytix, on Creytix
This page itself was produced by the platform it describes — the same design tokens, module pipeline, and review gates used for every Creytix client site. Nothing here is a mockup of the product; it is the product.