From signed contract
to invoice, without retyping

An invoice needs four things from an agreement: what the service is, how many units of it there are, what each unit costs, and how often it bills. A well-built SOW already holds all four. The question is whether it holds them as data or as prose.

When a statement of work is assembled from managed units, each unit is a record with a title, a count, a rate and a recurring flag. Generating the invoice then means reading those records: each selected unit becomes its own line, described as the unit and its count, priced at the rate the client actually agreed to including any per-line discount. One-time charges (setup fees, project labour, documentation, hardware) come across as their own non-recurring lines rather than quietly joining the monthly total.

When the same information lives in a paragraph, none of that is possible. The document is readable by a person and opaque to every system downstream of it, which is why the handoff to billing stays a human job no matter how many integrations sit around it.

A flat-fee agreement is easy: the number in the contract is the number on the invoice, every month, until the term ends. Per-unit agreements are where MSP billing gets interesting, because the count is a live quantity in the real world and a fixed one in the document.

A client onboards eleven people in March. Your RMM knows. Your PSA knows. The SOW still says the number it said in January, and so does the invoice generated from it. Nothing is broken, because the agreement is being billed exactly as written, but you are under-billing and the gap grows quietly.

The fix is not to have billing silently follow the device count, which would mean invoicing amounts nobody agreed to. It is to make the drift visible. XClause reads current counts from a connected PSA, RMM or Microsoft 365 tenant and compares them against what the agreement covers, so the variance is something you look at and act on rather than something you discover a year later. Invoices bill what the signed agreement says; the reconciliation tells you when the agreement needs amending.

The manual method is familiar because almost everyone starts there. Someone opens the signed PDF, opens the accounting or invoicing tool, and retypes the line items, quantities and rates. At five clients it takes fifteen minutes a month and works fine. The error rate is not zero, but it is low enough to be invisible.

The difficulty never changes. The surface area does. Every new SOW, every amendment, every renewal adds another document that has to be read correctly forever. Thirty clients with an amendment or two each is a few hundred numbers being re-entered a year, and the errors that slip through are the kind nobody catches: not a missing invoice, which somebody notices, but a correct-looking invoice with one wrong quantity.

A structured handoff keeps the contract data as data from the SOW stage forward, so producing the invoice is a read rather than a retype. In XClause that is one action from the contract: the invoice is drafted from the agreement, itemised by managed unit, with gapless sequential numbering allocated under a database lock so two people generating invoices at the same moment can never collide or skip a number.

Deliberately, it is not fired by the signature itself. Nothing in XClause invoices a client the instant they sign. The generation is automated; the sending stays a decision, which is the right split for most teams: you want the arithmetic done for you and the send reviewed.

One-way export pushes an invoice out to your ledger and stops. Two-way means something comes back, most usefully payment status, so the record in the contract system knows whether the invoice was paid without someone checking both places.

XClause pushes invoices and client records to QuickBooks Online and Xero, and reads payment status back from QuickBooks. Auto-sync is off until you turn it on, which is deliberate: you should decide when contract-system invoices start appearing in your books, not discover it after the fact. Xero receives invoices as drafts for you to approve.

The mismatch points are boring and they are the ones that break real migrations: customer IDs, service item names and tax codes rarely line up between two systems unless somebody maps them once at setup. Ask about that mapping before you connect anything, not after the first month of invoices lands in the wrong account.

One boundary worth stating plainly, because integration pages across this category blur it: sending an invoice out to accounting is not the same as writing billing back into your PSA. XClause does not write invoice line items into ConnectWise, Autotask, HaloPSA or SuperOps. The one outbound billing write it does have is much narrower, it applies to ConnectWise only, and it is off until you switch it on.

The exact direction of travel for every connector, meaning which records sync two ways, why RMM device counts move inbound only, and the one case where a quantity is written back into a PSA, is spelled out on the FAQ page.

An invoice generated against a lapsed agreement has nothing signed behind it. Most of the time nobody notices, because the client keeps paying and the service keeps running. It becomes a problem at exactly the moment you least want one: a dispute, an acquisition, a security questionnaire, or a client who decides in month fourteen that they never agreed to the current rate.

That is why renewal reminders and billing belong in the same workflow. A reminder 30 to 60 days out gives you room to issue a new SOW and get it signed before the next cycle runs, rather than discovering the gap after the invoice has gone. XClause sets those reminders per agreement, in any combination of 90, 60, 30, 15 and 7 days, and sends them to your team, the client, or both.

Amendments deserve the same discipline. If scope changes mid-term, the honest sequence is to amend the agreement, get it signed, and reissue billing from the current version. A billing series that quietly starts charging new numbers before anything is signed is the same problem as billing past expiry, pointed the other way.

The audit trail is what makes any of this defensible later. When a client questions a charge, an assertion is worth nothing. What answers it is the executed document, the signer, the timestamp, the IP address and the exact consent language, with the invoice traceable to that agreement.