Skip to content
Browse topics

Recurring billing: contracts that bill themselves

Create a contract with its frequency, billing day and lines, and Nori bills each period on its own, stamps it, e-mails it and collects it.

Updated November 17, 2026

On this page

A recurring contract bills a customer the same thing every so often: a rent, a retainer, support or a usage-based service. Every morning Nori checks which periods are due and makes their invoices.

Create the contract

  1. Go to Sales › Recurring billing › Recurring contracts and click New contract.
  2. Choose the Customer and give the contract a name.
  3. Set the Start date and, if it has one, the End date.
  4. In Schedule, choose the Frequency:
    • Weekly, monthly, every two months, quarterly, every six months or yearly.
    • Every N days or Every N months, for custom periods.
  5. Set the Billing day: 1 to 31; with 31 it bills on each month's last day. Weekly contracts take a weekday.
  6. Choose when it is billed:
    • In advance: on the first day of the period.
    • In arrears: the day after it ends.
  7. Keep Prorate the first and last period checked so the first and last periods bill only the days they cover.

What is billed

In What is billed add a line for each item:

  • With a Price, that price is always billed.
  • Without one, the contract's price list (or the customer's) is used on each period.
  • Metered: the quantity comes from the period's usage. In Tiers type up to:price separated by semicolons. For example, 100:0; 500:1.50; :1.20 includes 100 and bills the rest by tier.
    • All of it at the tier it reaches bills all the usage at the price of the last tier it reaches.
    • Each tier at its price makes one line per tier.

Usage is typed on the contract, under Usage, or sent through the API.

Document and CFDI

In Document and CFDI choose what is created each period:

  • Invoice, the usual one.
  • Sales order.
  • Delivery and invoice, when goods also leave the warehouse.

Also choose whether the document is posted or left as a draft to review. You can set the series, CFDI use, payment form and payment terms; whatever you leave empty comes from the customer.

Collection, notice and increases

  • E-mail the invoice to the customer: it goes with its PDF and XML.
  • Charge the customer's saved card in Recaudo: with a saved card the customer is charged; without one, the invoice goes with a payment link.
  • Cancellation notice (days): the cancellation takes effect at the end of the period in which those days are met.
  • Price increase: a fixed percent or an index (for example CPI) every so many months. Type the index values in Recurring billing settings.

Click Save and activate. A Draft contract does not bill.

Each period

  • Next run shows what will be billed, with the estimated amount and warnings (usage missing, index value missing…). Run now bills what is already due without waiting for the morning.
  • On the contract, Bill next period bills the next one even if its day has not come.
  • Billing log lists each billed period with its document, stamping, collection, e-mail and the error if there was one. Post drafts and retry failed periods from there.

Each period is billed only once: if the run goes twice or you click twice, nothing is duplicated.

Pause and cancel

  • Pause stops billing; on Resume the paused periods are not billed.
  • Cancel contract asks for the date and reason. It respects the notice days and bills up to that date; the last period is prorated.

Collections

In Recurring billing settings:

  • Reminders: the days after the due date on which a reminder of an unpaid invoice is sent, for example 3, 10, 20.
  • Pause the contract with an invoice overdue for more than (days): it pauses on its own and resumes once the customer pays.

Service contracts

When a contract in Service has an amount, frequency and item, Recurring billing bills it through its own recurring contract. Bill period on the service contract and the morning run never bill the same period twice. Once linked, the amount is changed on the recurring contract.

Reports

In Recurring revenue:

  • MRR and ARR: monthly and annual revenue of the active contracts.
  • Upcoming billings.
  • Churn: the MRR that came in and the MRR lost in the period.
  • To renew: contracts that end soon.
  • Revenue by contract: what was billed before taxes.

With an ERP connected

The contract lives in Nori. Only the invoices, deliveries and payments it creates go to the ERP, like any other document.

Related articles

Can't find something?

Tell us what you need to do and we'll get back to you. If you're already a customer, include your company's name.

Contact us