There is a line in billing automation that is worth drawing carefully, and most software draws it in the wrong place.
Generating an invoice from recorded work should be automatic. It is arithmetic over data you already hold, and doing it by hand is where errors and omissions come from. Sending that invoice to a client should not be automatic, and the reason has nothing to do with the arithmetic.
What an invoice actually is
An invoice is a communication with a client about money, arriving in their inbox with your name on it. It lands in whatever context that client is currently in, which might be a dispute about last month, a property they are about to sell, or a conversation you had yesterday that has not reached the billing data yet.
Software cannot see that context. A person can, in about four seconds of reading.
The cost asymmetry is stark. An invoice sent a day late costs nothing. A wrong invoice sent automatically costs a phone call, a credit note, an apology, and a measurable amount of the client's confidence that you are paying attention.
The draft as the handover point
MapleConcierge creates the invoice in draft. Every line, every rate, every pass-through receipt is assembled automatically from the service report and lands in the billing system ready to go. Nothing is emailed to anyone.
A person opens it, reads it, and sends it. That is the entire manual step, and for a typical monthly run across a portfolio it is minutes, not hours.
What has been automated is the part that is tedious and error-prone: pulling the right rate from the right agreement, applying the contracted markup to pass-through costs, attaching receipts, and making sure nothing was missed. What has been left to a human is the part that requires judgement about a relationship.
The boundary is enforced, not encouraged
This is stated as a design property rather than a preference. The integration that creates invoices has no capability to send one. The method does not exist.
That matters because "we always review before sending" is the kind of practice that survives until the first busy month. A boundary that lives in code does not erode under pressure, and it cannot be switched on accidentally by someone exploring settings.
Where the system does compute
Automation and judgement divide cleanly along another line too. MapleConcierge does not calculate tax. It sends invoice lines to the billing system, which computes tax from the customer record and its own configuration.
Two systems each applying their own tax logic will agree until the first time one of them is updated, and then they will disagree quietly, on invoices that have already gone out. Having exactly one system responsible for tax is worth more than the convenience of showing a total a moment earlier.
The same principle governs the totals. The caretaking system produces a local preview of the lines for the technician's benefit and labels it as a preview. The authoritative subtotal, tax and total come back from the billing system after the draft is created.
A reasonable test for any system you are evaluating
Ask what it does automatically that a client can see. Generating documents, computing charges and assembling evidence should be automatic. Anything that puts words in front of a paying client without a person reading them first should not be, and a vendor who is proud of automatic sending has optimised the wrong step.