Billing Timing

Each component of a price says when it is billed: in advance (for the period ahead) or in arrears (for the period that has just ended). Use in arrears for anything the customer should pay for after using it, such as usage, or seats billed for the month just used.

What is billed when

Component typeBilling timingWhen it is billed
RecurringIn advance (default)At purchase and at each renewal, for the period ahead.
RecurringIn arrearsAt each period boundary and on the final bill, for the period that ended. At purchase it shows as ₹0 with the text billed at end of period.
UsageAlways in arrearsAt each period boundary and on the final bill.
EventAlways in arrearsOn the next invoice, after you charge it with the charges API.
One-timeNot applicableOnce, on the order of its trigger.

Before this feature, usage was billed one period late: the renewal invoice for the next period was raised about five days before the period ended, and the usage of the period that just ended went on the order after it. Now one invoice carries both.

Set the timing in the rate plan builder

Turn on the Per seat tile

In the rate plan builder, under Pricing pieces in this plan, click Per seat.

Pick when seats are billed

Next to Billed choose one of two options:

  • At the start of the period (in advance, the default)
  • At the end of the period (in arrears)

The note Applies to this price only means the choice is saved for the active price point (for example INR · Monthly) and not for the other currencies or periods in the plan.

Check the preview

In the sample invoice, in-arrears seats are shown under Billed at end of period.

Publish

Click Publish plan.

The Base price is always a flat amount in advance. A Usage piece is always in arrears, and so is a Per-event fee, so neither shows a timing choice.

Settings

SettingAPI fieldAllowed valuesDefaultRules
Billing timingbillingTimingIN_ADVANCE, IN_ARREARSThe type’s default (recurring in advance, usage and event in arrears)An unknown value gives Component N has an invalid billingTiming.
IN_ARREARSOnly on RECURRING, USAGE or EVENTComponent N billingTiming IN_ARREARS is only allowed on RECURRING, USAGE or EVENT components
IN_ADVANCEOnly on RECURRINGComponent N billingTiming IN_ADVANCE is only allowed on RECURRING components

Boundary invoicing

A subscription whose price has at least one in-arrears line (any usage component, or a recurring component in arrears) renews at the period boundary:

  1. The expiring-soon step sends the reminder but raises no invoice.
  2. On the renewal date BillHive works out the period that ended, rates its in-arrears lines, and adds them, together with any pending charges, to the renewal order.
  3. It invoices the order. The invoice carries the next period’s in-advance lines and the ended period’s in-arrears lines.
  4. It activates the next term.
  5. It collects payment.

See Boundary Invoicing for the invoice, due date and payment rules.

A subscription with only in-advance recurring lines is not changed. It keeps the early renewal invoice, with the same amounts and timing as before.

Example, usage on the boundary invoice

The base plan is ₹15 a month, plus Emails at ₹0.004 after 15,000 included. The customer sends 18,000 emails in March.

The renewal invoice raised on 1 April:

LineBilledAmountCGST 9%SGST 9%
Rate plan, AprilIn advance₹15.00₹1.35₹1.35
Emails, March (3,000 × ₹0.004)In arrears₹12.00₹1.08₹1.08
Subtotal₹27.00
GST₹4.86
Total₹31.86

It is one invoice. If the renewal step is retried, the emails are not billed again: the usage rows of March are marked as billed with the order’s id.

Example, seats in arrears

A seat costs ₹100 a month, billed in arrears, and the customer buys 3 seats halfway through a 30-day month (15 of 30 days).

InvoiceSeat lineAmount
Purchase invoiceSeats, billed at end of period₹0
First boundary3 × ₹100 × 15/30₹150
Next boundaries3 × ₹100₹300

Short periods and plan changes

  • In-arrears recurring components cover the days actually in the period. A first period that starts in the middle of a cycle, or a period cut short by a change or a cancellation, is prorated by days, as in-advance recurring is.
  • On a plan or frequency change that takes effect now, the in-arrears recurring and usage of the closed period are billed on the change order, prorated where recurring. The change order is invoiced at once, so they bill at once.
  • Usage is never prorated.

Payment and access

  • The invoice is due at the boundary plus the larger of the account’s net term days and the tenant’s renewal grace days.
  • The subscription stays Active until then, as on the existing Access Continuity and net terms path.
  • If the invoice is still unpaid after that, the normal dunning path applies.
  • With Auto Collect, the payment is attempted at the boundary. For an in-arrears plan the payment wait follows the mandate schedule.
  • An in-arrears renewal cannot be paid before it is invoiced, so BillHive does not expire the subscription for lack of an advance payment.

Limits

⚠️
  • PERIODIC mandates, in-arrears recurring add-ons, the coupon credit base and unbilledChargeHandlingPolicy are not covered by this release.
  • End of Term changes: usage recorded on the last day after the 00:00 timer is not billed. A pass-through line after a renewal-mode End of Term change takes its GST setting from the cart’s price.
  • Unbilled days: a few days can go unbilled when the boundary has already run and a change is cancelled before it is invoiced. Voiding an invoice after a cancel does not hand the usage or pending charges back.
  • Every component shares the price’s billing period. There is no per-component period.