Landscapt (CRM)

Contracts

Ongoing billing agreements — monthly amounts, seasonal overrides, sub-properties, and how signing and invoicing actually work.

What a contract is

A Contract (Landscapt → Accounting → Contracts) is the ongoing billing agreement behind recurring service — a monthly amount, a billing day of month, and whether it bills a month ahead of service. Contracts don't renew automatically: when one ends, create the next season's contract. It's separate from a Package, which defines the service cadence template, and from the Invoices the contract actually generates — see the See also section below.

Each contract belongs to one client and is built from three pieces:

  • Invoice line items — one or more entries pulled from the services catalog (or typed as a custom line) that set the wording on every invoice this contract generates. Both billing paths use it the same way: the lines become the invoice description, and the invoice's single line item is named after them (several lines are joined with commas). With no lines, the contract title is used. The wording is set once per contract and is the same on every invoice; only the amount can vary by month.
  • A billing frequency and amount — Monthly contracts get a twelve-field grid, one per calendar month (January–December), each the amount of that month's invoice. "Auto Fill" copies January's amount into all twelve if you want a flat rate; otherwise leave months at $0 to skip billing entirely in that month. The line above the grid shows what the contract bills in a year. Every other frequency (Quarterly, Annual, Weekly, Every 2 weeks, One time) has a single Amount per invoice field instead — see Billing frequency options.
  • Billing settings — billing day of month, whether to bill a month in advance, payment type, PO number (copied onto every invoice the contract generates, so the client's accounts-payable team can match it), and two switches: Auto Generate (eligible for the automatic invoicing cron) and Active.

A contract's end date can't be earlier than its start date — a save with reversed dates is rejected.

Status lifecycle & signing

Status is a dropdown on the contract itself — there is no e-signature integration behind it. Marking a contract "Signed" is a manual confirmation, not a document that gets sent out for a client to click and sign.

StatusWhat it means
DraftJust created. Nothing has been sent or agreed to yet — safe to edit freely. Nothing bills, and completed visits on its jobs are held (see “Unsigned contracts” below).
SentThe proposal went to the client. Like a draft, nothing bills yet and completed visits on its jobs are held. Editing a signed contract’s terms does NOT move it back here — it stays Signed/Active with a “changed since signed” flag (see the callout below).
SignedYou (or the client) confirmed the terms. Sets signed_at and signed_by, and fires the “Contract Signed” automation/Zapier trigger.
ActiveThe contract is live and, if Auto Generate is on, eligible for automatic monthly invoicing.
ExpiredPast its end date. The expiry-warning email/notification fires 3 days before the end date for every signed or active contract (cancelled, expired, draft and sent contracts get no warning) — contracts never renew automatically, so every one is warned about. A retry never posts a duplicate in-app notification.
CancelledTerminated before or at its end date. No further invoices generate. Cancelling offers to void draft invoices already raised for dates after today.
Changing a signed contract's terms flags it — billing keeps running. If you actually change the monthly amount, the monthly-amounts grid, the invoice line items, the start/end dates, the client, the billing day / frequency, the mid-cycle start setting or the storms-outside-the-contract-dates setting (or its price per storm) on a contract that's already Signed or Active, the contract stays Signed/Active and the daily invoicing cron bills the new terms from then on. A "Changed since signed — needs client approval" banner appears on the contract until you click Client approved — clear flag (which re-stamps the signed date). The edit itself is recorded in the Audit Trail tab (the contract's tabs are Overview, Contract Details, Other Details, Jobs Under Contract, Included Services, Notes, Attachments and Audit Trail). Saving without changing any of those values — say, editing only the title, PO number or sales rep — doesn't flag anything.

Because the signed-date is a tracked field, it's also one of the Zapier/automation triggers — "Contract Signed" fires the moment a contract's status is set to Signed, which is what makes contract signing a distinct, reportable event rather than just a status label.

Billing mechanics

Two paths create an invoice from a contract, and both use the same logic:

  1. Automatic, via a daily cron. Every contract that is Active, has Auto Generate on, and whose Billing Day of Month matches today (or the last day of the month, if the configured day is higher than the month has days) gets an invoice created.
  2. Manual, via the "Create Invoices" bulk action on the Contracts list — select one or more contracts and bill them right now, ignoring their configured billing day (but not the active/amount checks below).

Both paths follow the same rules:

  • The invoice amount comes from that calendar month's entry in the monthly-amounts grid; if a month was never explicitly set, it falls back to the contract's flat monthly amount. A month explicitly set to $0 is skipped — no invoice is created for it.
  • Bill 1 Month in Advance shifts everything one calendar month forward: the invoice is dated and amount-matched to next month instead of the current one. This is what lets a contract invoice in, say, late June for July's service.
  • Idempotency is enforced per contract, per calendar month — a contract already invoiced this month is skipped, so re-running the cron or clicking Create Invoices twice can never double-bill. A contract invoice later consolidated or merged into another invoice still counts as billed.

Starting mid-cycle. A contract never bills before its start date: no invoice is dated before it, and no invoice pays for a billing cycle that began before it (a contract starting Jan 15 that bills on the 1st is not invoiced for the cycle that began Jan 1). What happens to the days between the start date and the first full cycle follows the contract's If Start Is Mid-Cycle setting. Start on first full cycle (the default) leaves them unbilled and starts at the first cycle that begins on or after the start date — a monthly contract running Jan 15 to Jan 14 with billing day 1 bills twelve times, Feb 1 through Jan 1. Quarterly and annual cycles start on the first billing day on or after the start date and repeat every 3 or 12 months from there: an annual contract starting Mar 15 with billing day 1 bills on Apr 1 each year, and a quarterly one starting Jan 15 bills Feb 1, May 1, Aug 1 and Nov 1. Once a contract has started billing its months are fixed, so editing its start date later never moves them (contracts already billing before this rule keep the months they have always billed in). Prorate first period also bills the partial stretch from the start date to the day before that first cycle, as its own invoice: the period's amount × days in the stub ÷ days in the full cycle, rounded to the cent (a contract at $1,000 a month starting Oct 20 with billing day 1 bills $387.10 for Oct 20–31, then $1,000 from Nov 1). The invoice line names the stub period and shows the formula. It's generated once — by the cron or Create Invoices, whichever comes first, as soon as the contract is signed and has started — and applies to Monthly, Quarterly and Annual contracts (a contract starting exactly on a billing day has no stub, and weekly, biweekly and one-time contracts never prorate). A contract that starts before its billing day (say Oct 20 with billing day 25) bills Oct 20–24 as the stub and its first full cycle on Oct 25 — monthly, quarterly and annual alike. An annual contract starting Mar 15 with billing day 1 bills Mar 15–31 as the stub (17 of 365 days), then the full year from Apr 1. The last cycle that starts on or before the end date is billed in full — that same contract ending Mar 14 the next year bills only the one Apr 1 invoice, covering through Mar 31. Turning proration on for a contract that has already started regular billing doesn't bill a stub after the fact. The stub uses the starting month's entry in the monthly-amounts grid when there is one, otherwise the flat amount. The stub invoice is dated the day it is created and its due date counts from then — a contract signed after its stub period has already ended gets its stub dated that day, not back-dated (so it isn't overdue the moment it's made). It can share a date with that day's regular invoice.

Billing in advance with a mid-month start. With Bill 1 Month in Advance on, a contract that starts after this month's billing day (billing day 1, start Oct 20) is picked up on the next run for the month it covers, so its first full month (November) is invoiced instead of being skipped until the following billing day. One signed before its start but after the advance run for its first cycle (start Oct 20, billing day 25, signed Oct 5 — the Sep 25 run predates it) gets that first cycle (Oct 25) invoiced as soon as it's signed, and the Oct 25 run then bills November as usual. In prorate mode the stub and the first advance invoice meet with no gap; the stub is still billed even though the first cycle was invoiced before the start date. Quarterly and annual contracts billed in advance keep the same cycle months; each cycle is just invoiced a month before it starts (start Jan 1, quarterly, billing day 1: the Jan 1 cycle is invoiced on Dec 1, the Apr 1 cycle on Mar 1).

Why bill a month in advance? For recurring service, invoicing after the work is done means chasing payment on a moving target — the crew has already spent the labor and materials, and now collections is racing next month's visits. Billing a month ahead flips that: the client pays before the month's visits happen, so a late or disputed payment is caught before more service gets delivered on an unpaid account, not after. It's a cash-flow and collections-risk decision, not just a scheduling preference.

A stop worked by two crews counts as one visit used against a contract's included visits. Both crews' hours still count toward the job's labor cost.

Billing frequency options

Every contract has a Billing Frequency, and both billing paths (the daily cron and Create Invoices) honor it. Set it in the contract's Contract Details tab, at the top of the Invoice Details settings; new contracts default to Monthly. It can also be set through the API, the MCP connector and the contract CSV import. It's shown in Contract reports, as the Frequency column on the Invoices list, and in the contracts list's Amount column ("$3,000.00 / quarter").

For any frequency other than Monthly, the twelve-month grid is replaced by one Amount per invoice field and a line saying when the contract will bill: the months for Quarterly and Annual ("Invoices in Feb, May, Aug, Nov", starting from the first billing day on or after the start date — or the signed or created date when there's no start date — and fixed once the contract has billed), the 7- or 14-day cadence for Weekly and Every 2 weeks, and the first date for One time. Settings that don't apply are hidden: Weekly and Every 2 weeks have no Billing Day of Month, Bill 1 Month in Advance or mid-cycle proration, and One time has no Billing Day of Month or proration. Switching frequency carries the amount across (a flat monthly grid becomes the single amount and back; a seasonal grid is kept as it is). If a non-monthly contract created through the API or import had different amounts for some months, the dialog says so, and saving replaces them with the one amount.

Changing the frequency or start date after the contract has billed. The period already invoiced runs out first, then the new schedule begins with its first cycle after that — nothing is billed twice and no month is skipped. Switching a quarterly contract billed through March to monthly starts the monthly invoices in April; switching monthly to quarterly starts the first quarter with the next month. Before you save, the Contract Details tab shows an amber note such as "The new schedule takes effect after the period already billed, ending Mar 31 — its first cycle starts Apr 1." A contract that has never billed simply uses the new settings from the start.

Weekly and every-2-weeks contracts keep their weekday. Once one of these has billed, its 7- or 14-day cycle is fixed to the day it started billing on, so editing the start date later doesn't slide the cycle or bill days an earlier invoice already covered. The dialog names that date ("counted from …, the period it is already billing on"). Changing the frequency itself follows the rule above.

If a billing day is missed (an outage, or the cron failing that morning), the contract is billed later in the same period rather than skipped — for Weekly, Biweekly, Monthly, Quarterly and Annual contracts alike, as long as that period hasn't already been invoiced. A run missed at the very end of a month (billing day 28–31) is still made up in the following month, up until that month's own billing day, dated its original billing day. The same goes for a contract entered, signed or switched to Active a few days after its billing day (start Jan 1, billing day 1, entered Jan 3): the next run bills the current cycle, but the invoice is dated the day it's created (Jan 3) rather than back-dated to the billing day, and its due date counts the client's terms from that date. When you mark a contract Signed or Active, make it active again, or save one that is, after that cycle's billing day, the contract window asks first: Bill January now (dated today) creates the invoice right away, and Start billing with February skips the cycle — nothing is billed for it and the first invoice is the next cycle's.

Signed late: every missed cycle is listed. A contract signed well after its start date (start Aug 1, signed Nov 10) has several cycles no billing run will ever bill on its own. Signing it lists every unbilled cycle since the start date with its amount, and asks: Bill all (the current cycle as its normal invoice, the earlier ones on one catch-up invoice with a line per cycle, all dated today), Bill the current cycle only (the earlier ones are never billed), or Start billing with the next cycle. Visits done in a cycle you choose not to bill are still covered by the contract — they aren't billed per visit. The same list appears after Make Active (one contract or a selection) if any cycle from before the pause was never billed. A cycle counts as billed when it has a contract invoice — even a void one — exactly as the billing runs count it. Contracts recorded through the API or an import as already Signed/Active are treated as already billed for the cycle in progress (see below), so nothing is asked.

Make Inactive / Make Active. While a contract is inactive it doesn't bill, and its jobs' visits bill per visit (except visits inside a cycle the contract had already invoiced). Making it active again starts contract billing with the next cycle: the cycle in progress isn't billed again, and visits until that next cycle starts keep billing per visit.

Contracts activated another way (the API, an import) follow the late-start rule above. A cycle is only ever billed once, whatever date its invoice carries — a later run or a Create Invoices click in the same period is skipped. Two exceptions are not back-billed: a client reactivated after the billing day (billing resumes at the next cycle), and a contract imported or created through the API as Signed or Active, which is marked as billed for the period in progress unless you give its last billed date (counted from the import day when it has no start date). A contract whose client is cancelled, inactive, lost or still a lead (or deleted) stops billing, matching the visits, which also stop; reactivating the client (or converting the lead) resumes billing on the next cycle.

FrequencyWhen it makes sense
WeeklyBills every 7 days, counted from the contract’s start date. Billing Day of Month doesn’t apply.
BiweeklyBills every 14 days, counted from the contract’s start date. Billing Day of Month doesn’t apply.
MonthlyThe default and by far the most common — matches how most maintenance and package programs are sold; bills on the Billing Day of Month. The only frequency with the 12-month grid, so it’s also the one for seasonal contracts whose months bill different amounts.
QuarterlyBills every third month, counted from the contract’s start month, on the Billing Day of Month.
AnnualBills once a year, in the contract’s start month, on the Billing Day of Month — e.g. a lump-sum snow contract.
One-timeBills exactly once, on the first run on or after the start date; once any invoice exists on the contract it never bills again.
The amount is per invoice, not per month. The contract's monthly amount (and each month in the monthly-amounts grid) is what gets charged every time the contract bills, at any frequency — it isn't annualized or divided. A quarterly contract worth $3,000 a quarter should store $3,000, and an annual $12,000 contract stores $12,000. Quarterly and annual contracts can't double-bill: a manual Create Invoices click mid-period bills that period and the cron then skips it. Bill 1 Month in Advance only applies to monthly, quarterly, annual and one-time contracts.

Seasonal contracts with different monthly amounts. A contract that bills, say, April through November at different amounts stays on Monthly: enter each billed month's amount in the grid and leave the other months at $0. It sends eight invoices a year, each for its own month's amount. Because no single amount describes it, the contracts list, the client's contract badge and the snow-billing contract picker show its yearly total instead — "$4,100.00 / yr · 8 months (varies)". A seasonal contract with the same amount every billed month reads "$500.00 / month · 8 months".

Exporting. The contracts list's Export button writes Billing Frequency, Billing Day (blank for weekly, every-2-weeks and one-time contracts), Amount per invoice ("varies by month" for a seasonal grid with different amounts) and Yearly Total (blank for one-time contracts). Export needs the Export Lists permission. Make Active / Make Inactive on a selection applies to every contract it can and reports how many couldn't be changed, with the reason.

Ending or cancelling a contract

Unsigned contracts hold their visits. A job can be linked to a Draft or Sent contract (the job's contract picker shows each contract's status and warns you; cancelled contracts aren't offered). Visits completed on it from the start date on are held — not invoiced. When the contract is signed, they're covered by it (the missed-cycles question above bills the cycles they fall in, if you choose). If it's cancelled without ever being signed, the held visits are billed per visit straight away, on the client's usual invoicing.

Materials on contract jobs. The contract covers the services on its jobs, not automatically every material used. Each product on a contract-linked job has an In contract checkbox (on by default) on the job's Products table and the dispatch board's job panel. A product that's in the contract bills only what's used above the planned quantity — 10 yd of mulch planned, 15 yd used bills 5 yd; 10 or fewer used bills nothing and the product is marked "Used, not billed". Untick it and the full quantity bills. Either way the materials go on a normal per-visit invoice when the visit is completed (the services stay inside the contract price). Chemical-program products follow the same checkbox.

While a contract is Signed/Active its jobs' visits are billed inside the contract price and don't auto-invoice — from the start date on (a visit dated before the start date bills per visit), and past the end date through the last billing cycle the contract invoiced in full. Once the contract is Cancelled, Expired or switched inactive, a completed visit still counts as covered if it falls inside a billing cycle the contract already invoiced, so it isn't billed twice; visits after that cycle bill like normal per-visit work, on the client's usual invoicing frequency. When you cancel or end a contract that has linked jobs, the app tells you how many will now bill per visit before you confirm.

Cancelling voids future drafts on request. With Bill 1 Month in Advance (or an early Create Invoices), a contract may already have a draft invoice for time after the day you cancel it. The cancel confirmation lists every draft invoice dated after today with a checkbox (all ticked); the ticked ones are voided as the contract is cancelled, and the contract stops counting their cycles as paid for — so any work in that time bills per visit. Sent or paid invoices are never touched: credit or refund those by hand if needed.

Cancelling or deleting a contract cancels its upcoming visits. Visits on its linked jobs from today on that are still scheduled or dispatched and haven't been started are marked Cancelled, with a note on each. A visit a crew is clocked in to, and visits already skipped or completed, are left as they are. If some visits can't be cancelled you get an error saying how many — cancel those from the Dispatch Board.

Snow contracts and storms outside the dates. Tick This contract includes snow service (under the start and end dates; it stays locked on while a snow job is linked) to show the snow settings, including Storms outside the contract dates, for storms before the start date or after the end date: Don't service (the contract's snow jobs aren't offered for those storms on the Snow Jobs board), Included in the flat rate (dispatched and covered by the contract price) or Bill per event (the default — dispatched and billed in Snow Invoicing). With Bill per event, enter a Price per storm: that's what a Monthly Flat Rate snow job bills for each of those storms (a job with its own snow rate bills that rate instead). Without a price, Snow Invoicing holds the storm with a warning rather than billing $0. A cancelled, expired or inactive contract covers only storms inside a billing cycle it already invoiced; later storms bill per event the same way.

Contract templates

If you set up many contracts the same way — the same name, invoice description lines, monthly amounts and billing terms — save that setup as a template instead of retyping it.

  • Save one. Fill in the Details tab the way you want it, then click Save as template at the top of the tab and give it a name. A template stores the contract name, invoice line items, default service, the twelve monthly amounts, billing day of month, bill-a-month-in-advance, payment type, auto-generate invoices, and include sub-properties. It does not store the client, the start and end dates, or the billing frequency — applying a template keeps whatever frequency the contract already has.
  • Use one. On a new contract, choose it from Start from a template…. The form fills in and you can change anything before saving.
  • Editing and deleting. A contract keeps no link to the template it came from, so deleting a template (use Delete template after picking it) never changes existing contracts.

Worked example: multi-property commercial contract

A property management company owns 5 sites and wants one contract, one monthly invoice, and a summer-heavy price — full mowing season rate April–October, a reduced fall/winter rate the rest of the year.

  1. Add each of the 5 sites as a Property on the ONE client record first (More menu → Add Property, on the client's detail page — see the Clients guide, linked below). This is a single client billed as one account across multiple addresses, not several separate client records — if the sites actually need independent jobs, invoicing, or estimates instead of one shared bill, that's the parent/child client hierarchy (sub-accounts) instead, a different feature covered in the Clients guide.
  2. Create the contract against that client. In Contract Details, check Include Sub Properties by Default — this is on by default and documents that the contract covers every property on the client's account, not just one address.
  3. Set the invoice line items to the services covered across the sites (e.g. "Weekly Mowing — 5 Properties", "Spring Cleanup — 5 Properties").
  4. In the monthly-amounts grid, enter the combined total for all 5 sites in each month — April through October at the full mowing-season rate, November through March at the reduced rate. There's no per-property line-item breakdown on the invoice itself; the grid holds one number per month, so that number needs to already be the sum across every site the contract covers.
  5. Set Billing Day of Month and, if the management company expects to be invoiced ahead of each month's service, turn on Bill 1 Month in Advance.
Sub-properties is a billing-scope flag, not an auto-aggregation feature. Turning it on tells the contract it's meant to cover every property on the client's account instead of issuing a separate contract per site — but the monthly amount you enter is still one flat number per month. It won't sum up per-property pricing for you, so double-check the combined total by hand whenever a property is added to or removed from the client.

See also

  • Jobs & Packages — a package defines the recurring service cadence and visit counts; a contract defines the ongoing billing terms on top of it.
  • Invoicing — what a contract actually produces: the draft invoices created by the cron or the manual "Create Invoices" action.
  • Clients — adding properties to a client, and when to use the parent/child (sub-account) hierarchy instead.

Good to know

  • Why Create Invoices skipped a contract. When Create Invoices doesn't create an invoice it says why: already billed, a draft or unsigned contract, a contract that hasn't started, a $0 month, not a billing month, or an inactive client.
  • Prorated first invoice. The prorated first-period invoice's due date counts from its own invoice date, so its terms read correctly.
  • Visit usage. The Used counts against a contract's included visits leave out visits on deleted jobs.

More in Landscapt (CRM)

Clients, Properties & Leads
Client accounts, commercial hierarchies, service properties, and the activity timeline that ties it all together.
Estimates & the Budget Engine
How an estimate is built, how its numbers are actually calculated, and how it becomes a job.
Jobs & Packages
The six job types, how a job's status differs from a visit's status, and how a Package template turns into a billed job.
Services & Pricing
The service catalog, bulk catalog price changes, and Price Adjustment runs — which prices seed new work and which ones actually bill.
The Dispatch Board
The daily scheduling screen crews and dispatchers live in — visits, crews, status, and how actual hours get calculated.
The Crew App
What a crew sees on their phone — the day's stops, clocking on and off, breaks, photos, and sending work back to the office.
Sales Meetings
Booking appointments per sales rep, the double-booking warning, and the split between a rep's direct reminder and the client-facing automation trigger.
The Waiting List
Jobs with a date range instead of a date, held for opportunistic scheduling — and how to actually get them dispatched.
Snow Jobs & Storm Dispatch
Storm events, priority dispatch, and the invoicing flow built specifically for snow.
Invoicing & Payments
How an invoice is born, how its status moves, and where the client's own PO number actually goes.
Communication Automations
How sequences, triggers, and events work — and how Automations differ from Sales Campaigns.
Forms & Lead Capture
Building, publishing, and sharing public forms — and what happens to a submission once it lands.
Document & Email Templates
Building the reusable emails and text messages that go out with invoices, estimates, campaigns and automations — blocks, merge tags, buttons, previews and test sends.
Tickets
Support and service tickets — where they come from, how they're worked, and how they connect to the rest of a client's record.
Damage Cases
Tracking property damage and warranty claims tied to a job — what a case captures, how cost rolls up, and a real current limitation in how it connects to a client record.
Warranties
Tracking the warranties you give on walls, walkways, patios and renovations — when each starts and ends, how claims tie back to it, and expiry reminders.
Commissions
Paying sales reps a percentage of what they sell — plans and rules by service and sale type, how earnings are calculated, and locking a quarter into a statement.
Injury & Near-Miss Cases
Reporting injuries, illnesses and near misses from the field, following them up in the office, tracking self-paid costs, supervisor alerts, and the Accident Free Workdays KPI.
Job Photos
Field photo documentation, annotation, and before/after comparisons — attached to a job site, not a person.
Online Payments & Stripe
How a client actually pays an invoice online, how Stripe Connect keeps every org's money in their own account, and how the platform takes zero cut.
Browse all guides
© 2026 Landscapt. All rights reserved.