Terms
The shape a service agreement takes. Placeholder text in a template, not legal advice.
Last reviewed 24 September 2026
About this page
Placeholder text in a template. Coffer is HTML, CSS and JavaScript with no server behind it, so there is no service to agree terms about. What follows is the shape a real agreement takes, so you have the headings and the layout ready. Have a lawyer write the words.
Your account
Who may open one, what they promise about the details they give, and that they are answerable for what happens under their sign-in. In a product where one firm keeps another's books, say clearly which of them owns the account and which is a guest on it.
Acceptable use
What the service may not be used for, and what happens when it is. Keep the list short and specific; a long one that is never enforced is worse than none.
Paying
What it costs, when it is charged, what happens if a payment fails, and whether anything is refundable. Say how much notice is given before a price changes, and state whether tax is included in the figure shown.
Your records
The accounting records belong to the customer, not to the service. Say so, say how they can be exported at any time in a usable format, and say for how long they remain available after an account ends.
Availability
What is promised, how planned maintenance is announced, and what is owed if the promise is missed. Promise only what can be measured and shown.
Where liability sits
Bookkeeping software records what it is told. It does not file a return, give tax advice, or take responsibility for a figure entered wrongly — and it should say so in as many words rather than burying it. Set out clearly what is excluded and what cap applies.
Ending it
How either side ends the agreement, how much notice is needed, what is refunded, and what happens to the records afterwards — which has to agree with the retention period in the privacy policy.
Changes
How these terms change, how much warning is given, and what a customer can do if they do not accept the new ones.