RevQL

The work between the contract and the ledger

An invoice tells you what was billed. It does not, by itself, tell you what was earned. That answer can depend on contract terms, performance obligations, usage, delivery, amendments, and accounting judgments.

When those facts live in different systems, the accountant becomes the integration layer. A contract changes, a schedule is rebuilt, an entry is adjusted, and the explanation has to be reconstructed at close or during an audit.

RevQL is designed to keep the facts, the treatment, and the resulting accounting connected. The scope is deliberately revenue recognition—not quoting, billing, collections, or a new general ledger.

OpenRevRec: the accounting application

OpenRevRec is the free, open-source foundation: a local-first desktop application being built around ASC 606 revenue recognition. It should be useful as accounting software before anyone connects an AI model.

Its core is contracts, performance obligations, allocations, schedules, modifications, and journal entries. Accountants establish the treatment; deterministic code handles the calculations. The goal is to make each result traceable to its inputs and supporting evidence.

The design makes the same accounting operations available through the desktop application, APIs, and a command-line interface. Use the interface directly, write your own scripts, or connect external tools and agents. There is one accounting model, not a separate version for each way of using it.

OpenRevRec stands on its own. It does not require Clerk, a model provider, or a RevQL service engagement.

Clerk: help alongside the work

Clerk is the optional, commercial desktop companion. It runs in its own window beside OpenRevRec, contracts, spreadsheets, and other finance tools—not as a chat panel inside the accounting application.

We are designing it to extract terms, assemble evidence, investigate differences, prepare proposed changes, and carry out approved actions through supported interfaces. OpenRevRec maintains the accounting record; Clerk helps the accountant work with it.

The planned model is an annual software license with bring-your-own-key inference. You pay RevQL for the workspace and workflows, and your selected provider for AI usage. Choose among supported providers without replacing the application.

Choose where the intelligence runs

Using your own API key does not make inference private. An external provider still receives the context sent to it. Local accounting and private AI are separate choices.

For teams that need a different boundary, we plan to publish an open-source private inference stack, deployable in customer-controlled infrastructure and usable by Clerk or other tools. Self-deployment would be free; setup, evaluation, and customer-specific tuning would be paid implementation work. Compute remains a separate cost.

Private AI is an infrastructure option, not a prerequisite for using the accounting software or another mandatory subscription.

Software, with implementation

A working revenue operation needs more than a download. Existing schedules need to carry forward. Contracts and source data need mapping. Approved accounting policies need to become configuration. Outputs need to reconcile to the ledger.

This is RevQL's commercial role: implementation, integrations, workflow automation, and support around the software. That includes private deployment and specialized model tuning when an evaluation shows a reason to do it.

The aim is a substantial initial setup followed by software-driven operation, with support and changes as needed. Repeatable work should become automation, not a permanent manual service.

Where things stand

OpenRevRec and Clerk are in development. The immediate focus is the accounting model, the desktop workflows, and the programmatic interfaces that make them useful together or independently. The open private AI stack is planned for a later stage.

OpenRevRec.com will be the home for downloads and documentation. In the meantime, follow OpenRevRec on GitHub.

I'm Chris Davis, the founder. I'm looking for revenue accountants, controllers, and fractional CFOs who want to help shape the product around real contract and close workflows.

For design partnerships or implementation discussions, write to chris@revql.com.