Billing automation from finished work to the invoice each customer will accept.

Three inputs, in every industry. Each bill on this page is built from the contract that sets the price (a schedule of values, a fee schedule, a rate sheet or a service agreement), the record of what was done (a PM's percent complete, locked timesheets, a signed ticket, a technician's checklist), and the customer's rules for what a bill must carry. The third is the one teams underrate. FAR 52.232-25, the federal prompt payment clause for supplies and services, spells it out: a proper invoice names the contract with its order and line item numbers, describes the work with quantity, unit of measure, unit price and extended price, and gives the name, title and phone number of the person to contact if the invoice is defective. The billing office has 7 days to send a defective one back, and payment falls due 30 days after the later of a proper invoice arriving and the work being accepted. Private customers put the same kind of rules into their AP policies and portals.

Each billing type needs its own proof. Progress billing asks for a statement about the money as well as the work. On federal fixed-price construction, FAR 52.232-5 requires a certification with every progress payment request: the amounts are only for work done under the contract, subcontractors and suppliers have been paid from earlier payments, and the request includes nothing the prime means to withhold from a sub. Time and materials asks for the hours themselves. Under FAR 52.232-7, vouchers are backed by evidence of payment and by daily job timekeeping records, or records showing each person meets the labor category billed, and except for small businesses they go in no more than once every two weeks. A service agreement bills its price on a schedule and its extras by the visit, and a work order bills by the visit, the push or the square foot. A draft has to know which kind each line is before it adds anything up.

Where a line falls changes the tax. Texas shows how much rides on the split. Under 34 TAC 3.357, scheduled, periodic maintenance on real property is a nontaxable service, repair, remodeling and restoration of nonresidential property are taxable, and new construction is not. A maintenance contract whose repair charges grow past a small share of the total, and aren't separately identified in the contract or the bill, becomes taxable in full, and work done job by job with no written contract is presumed to be repair. Under 34 TAC 3.356, lawn and yard maintenance, landscaping and janitorial work are taxable real property services. So in one state a scheduled maintenance visit, the repair the technician found on it, a janitorial invoice and a new wing on a building can each be taxed differently. Other states draw other lines. The test follows the treatment your team applied on the sample bills and flags any line whose split looks off; none of this is tax advice.

The customer picks the channel. General contractors bring their own billing portals, facility customers their work order systems, state DOTs their own forms and progress reports, and federal contracts name an electronic system of their own. In each case the bill is judged in the customer's format, so the proof of concept drafts in that format from examples you send. It never logs in, never uploads and never submits.

The calls stay where they are. Percent complete belongs to the project manager on a construction job or an engineering phase, an NTE increase to whoever asks the customer for one, an agreement change to the service manager, and the release of each bill to whoever releases it today. The draft carries their decisions into the bill, checks the arithmetic and the rules, and lists what is missing. It never estimates progress, writes off time, changes a rate or certifies a pay application. Pick the card that looks most like your own billing desk; each page sets out what to send, how its test is scored and its one hard limit.