Schedules built from the signed contract
Each field is read from the contract, so your team reviews drafts instead of rebuilding them.
355 of 386
June invoices sent from their schedules; 31 waited for a person
Billing
Each contract, billed the way it was signed
Seats, usage, prepaid credits and milestones, invoiced from the signed contract instead of a spreadsheet.
Agents at work
Two agents turn contracts into invoices
The Contract agent reads each agreement; the Invoice agent drafts from it and holds every draft for approval.
2 agreements read by 06:00
Reads every agreement and amendment.
Extracts each term for a person to review.
214 active customers
Reads documents
31 drafts held for approval, $412,640.00
Composes each invoice from contract and usage.
Holds every draft for your approval.
41.2M usage events in June
Reads documents and Verlix AI OS
Oakum Bullace Inc
MSA-4692 read for review
Drumlin Tansy Inc
$15,340.00 proposed under clause 4.2
June billing run
355 of 386 invoices sent
What changes
Stop building invoices in spreadsheets
Catch billing errors before invoices send
Usage lines are checked against their records, and a draft that does not match waits for you.
Signed today, invoiced today
Oakum Bullace Inc's order form was signed and invoiced the same day, 12 June.
16 days
to collect in June, down from 32
What it saves
Catch under-billing and duplicate charges
June 2026 in the example workspace.
0
gap between usage and invoices across 41.2M usage records
$3,860
a month of under-billing caught at renewal on INV-6155
12,400
duplicate usage records removed before INV-6147 went out
The team
44% more invoices, same billing team
June 2026 against June 2025, in the example workspace.
In detail
How invoices get built, checked and synced
Recurring invoices drafted on schedule
Each schedule drafts its invoices when they fall due, with no template to fill in.
- Seats, usage, prepaid credits and milestones on one invoice
- Each draft held for your approval before it sends
One invoice off that run, start to finish:
- Invoice
- INV-6104
- Customer
- Fulmar Grosgrain Inc
- Plan
- Enterprise hybrid · 186 seats
- Amount
- $74,600.00
Usage billed without the spreadsheet
API calls, seats, outcomes or prepaid credit, counted as used and priced on the contract's rate card.
- Per-unit, tiered or volume pricing
- June's 41.2M usage records matched their invoices
What one month of metered usage rated to:
- API calls
- $34,820.00
- Rate
- $0.009 per call
- Prepaid credit drawn down
- $19,420.00 · 2.56M credits
- Usage records counted
- 6.43M
- Variance
- 0 against the invoice
Under-billing caught before it sends
The Invoice agent finds a term the schedule missed and proposes the fix for you to approve.
- Each change states its reason
- Unclear terms wait for a person
A correction it is holding for approval:
- Invoice
- INV-6155
- Customer
- Drumlin Tansy Inc
- Was
- $11,480.00
- Repriced to
- $15,340.00
- Reason
- Base fee rises on renewal
Seat changes priced to the day Coming soon
Add seats mid-month and the invoice bills the old count and the new one for the days each applied.
- Prorated to the day, up or down
- Lands on the next invoice, not next quarter
How one mid-cycle upgrade priced itself:
- Customer
- Fulmar Grosgrain Inc
- Changed on
- 12 June
- Seats
- 148 → 186
- Before
- $61,200.00
- After, prorated
- $74,600.00
Your ledger stays where it is
Each system you already run gives Verlix what it holds.
- Won deals read from Salesforce, contracts from Salesforce and DocuSign
What the ledger sync is doing right now:
- Writes back to
- Stripe
- Last run
- 4 min ago
- Connected
- Xero, Stripe, Salesforce, DocuSign
Xeroinvoices in
Stripepayment links out · payments in
Salesforcewon deals in
DocuSigncontracts in
Questions finance asks first
The Contract agent extracts each term for a person to review; the Invoice agent drafts from those terms and holds the invoice for approval. In the illustrative example, Oakum Bullace Inc's order form was signed and invoiced on 12 June.
To the day. In the illustrative example, Fulmar Grosgrain Inc moved from 148 to 186 seats on 12 June, so 11 days bill at 148 and 19 at 186, each line rounded once to the cent, on June's open draft.
That the draft matches its contract and its usage. Each usage line is counted against its records and duplicates come out. In the illustrative June, the check removed 12,400 duplicate usage records from INV-6147 before it went out.
Yes. The Invoice agent compares each draft with the clause that sets its price. In the illustrative example, Drumlin Tansy Inc's renewal was drafted at $11,480.00, but clause 4.2 sets $15,340.00, so the agent held it and proposed the fix.
In the illustrative example workspace, the same 2 people billed 44% more invoices than a year earlier: 386 in June, up from 268, or 193 each, up from 134.
Starter is $95 a month under $1M billed revenue a year.Get started
Keep exploring
Product
Collections
Reminders go out the day after an invoice falls due, once you turn on the Collections agent.
Solutions
Usage-based billing
Usage priced on each customer's own rate card and checked against the invoice before it sends.
Blog
Metering that reconciles
Usage billing fails between the event stream and the invoice.