See how ScaleXP works with Xero or QuickBooks.
In a 15- or 30-minute demo, we’ll show the relevant workflows using example data and discuss how they could apply to your finance process. Complex requirements? Discuss them with us first.
Key takeaways
Short answer: When a SaaS contract starts mid-month, recognize revenue for the part of the first month in which the customer had access, then run the schedule to the matching part-month at the end of the term. Daily proration follows the service most closely; half-month or full-month conventions are simpler and acceptable when the result is not materially different.
The choice matters less than the consistency. A finance team that prorates one contract by day, another by half-month and a third from the first invoice date will produce monthly revenue that nobody can reconcile. This guide compares the conventions, shows the first and last partial periods, and gives an illustrative schedule.
A mid-month start creates two partial periods because the contract term and the calendar months no longer line up. A twelve-month contract starting on January 16, 2026 runs to January 15, 2027. It touches thirteen calendar months: a partial January 2026, eleven full months, and a partial January 2027.
Under ASC 606 and IFRS 15, revenue is recognized as the promised service is transferred to the customer. For a subscription, that transfer happens continuously across the term, so each calendar month should carry the revenue for the service delivered in it. A schedule that books the whole first month in January, or ends in December, moves revenue between periods. Our overview of revenue recognition methods explains why subscriptions are recognized over time, and the IFRS 15 guide for SaaS companies covers the five-step model.
For a single contract, the difference is small. Across a customer base where most deals close in the second half of the month, and where quarter-end deals cluster in the last week, a convention that ignores the start date can shift a visible amount of revenue between months and quarters.
Daily proration divides the transaction price by the number of days in the term and recognizes that daily rate for each day of access. It is the convention that most closely follows how the service is delivered.
The cost of daily proration is operational. Monthly revenue moves with the calendar, which makes revenue per customer vary month to month and complicates comparison with MRR. That is a presentation issue, not an accounting one, but it is the main reason teams look at simpler conventions.
Monthly conventions recognize revenue in equal monthly amounts and apply a simple rule to the first and last months. The two common versions are:
Both produce clean, equal monthly amounts that match MRR. Both are approximations, and the full-month rule is the coarser of the two: a contract starting on the 16th recognizes nothing for sixteen days of service. These conventions are accepted in practice when the difference from daily proration is not material to the financial statements. That is a judgment to document and agree with your auditors, not an assumption.
A proration policy is a short written rule that says which convention the business uses, when it applies and who can approve exceptions. Without one, the convention is set by whoever builds each schedule.
A workable policy covers:
Consistency also protects the balance sheet. When invoices are raised on the contract anniversary and revenue follows a different convention, the difference sits in deferred revenue or accrued revenue at each month-end, and it should be explainable from the policy.
The first and last months are where proration errors show up, because they are the only months that differ from the standard monthly amount.
Illustrative example: a customer signs a $12,000 annual plan with service from January 16, 2026 to January 15, 2027, a term of 365 days. The daily rate is $12,000 divided by 365, or about $32.88.
The table below shows the revenue each convention recognizes in each calendar month.
| Month | Days of service | Daily convention | Half-month convention | Full-month rule (15th) |
|---|---|---|---|---|
| Jan 2026 | 16 | $526.03 | $500.00 | $0.00 |
| Feb 2026 | 28 | $920.55 | $1,000.00 | $1,000.00 |
| Mar 2026 | 31 | $1,019.18 | $1,000.00 | $1,000.00 |
| Apr 2026 | 30 | $986.30 | $1,000.00 | $1,000.00 |
| May 2026 | 31 | $1,019.18 | $1,000.00 | $1,000.00 |
| Jun 2026 | 30 | $986.30 | $1,000.00 | $1,000.00 |
| Jul 2026 | 31 | $1,019.18 | $1,000.00 | $1,000.00 |
| Aug 2026 | 31 | $1,019.18 | $1,000.00 | $1,000.00 |
| Sep 2026 | 30 | $986.30 | $1,000.00 | $1,000.00 |
| Oct 2026 | 31 | $1,019.18 | $1,000.00 | $1,000.00 |
| Nov 2026 | 30 | $986.30 | $1,000.00 | $1,000.00 |
| Dec 2026 | 31 | $1,019.18 | $1,000.00 | $1,000.00 |
| Jan 2027 | 15 | $493.14 | $500.00 | $1,000.00 |
| Total | 365 | $12,000.00 | $12,000.00 | $12,000.00 |
Source: illustrative figures prepared for this article; daily amounts rounded to the cent, with January 2027 absorbing the rounding difference.
The three conventions each recognize $12,000 over the term, but the timing differs. For the first quarter of 2026, the daily convention recognizes $2,465.76, the half-month convention $2,500.00 and the full-month rule $2,000.00. The full-month rule understates the quarter by about $466 against daily proration on this one contract, which is why the policy needs a materiality check.
ScaleXP builds revenue schedules from the invoices in Xero or QuickBooks Online, using the service dates on each invoice, and spreads the revenue across the relevant months. Where an invoice does not carry the contract dates, ScaleXP reads deal and contract dates from HubSpot, Salesforce or Pipedrive, so the schedule starts from the service period rather than the invoice date.
In the ScaleXP demo company below, an invoice dated September 23, 2026 recognizes a part-month of $3,130 in September, $11,618 in each full month, and a final part-month of $3,634 in December.
ScaleXP prepares the revenue journals each month, and they are posted once finance approves them. The proration policy itself remains a finance decision. See the revenue recognition automation page for how the schedules and journals fit together.
A SaaS contract that starts mid-month earns revenue for the days of service in its first month and finishes with a matching partial month at the end of the term. Daily proration follows the service most closely; half-month and full-month conventions are simpler and acceptable when the difference is not material. Choose one, write it into the revenue policy, start from the service date and apply it consistently.
Not necessarily. ASC 606 and IFRS 15 require revenue to follow the transfer of the service, and daily proration is the closest match. Many SaaS businesses use a half-month or full-month convention instead, which is generally accepted when the result is not materially different from daily proration. Document the convention in your revenue policy and agree it with your auditors.
The service start date starts the schedule, because revenue follows the transfer of the service to the customer. A contract signed on January 28 with access from February 1 has no January revenue, even if it is invoiced in January. Where the invoice is raised before service starts, the amount sits in deferred revenue until the service period begins.
A free trial with no payment and no commitment usually earns no revenue, so the paid term starts on the conversion date and the first month is prorated under your normal convention. If the free period sits inside a signed paid contract, such as a first month free on an annual plan, it is usually treated as a discount spread across the whole term.
A twelve-month contract starting after the first of a month ends partway through the same month a year later. A contract starting on January 16, 2026 ends on January 15, 2027, so it has a partial first month, eleven full months and a partial last month. Schedules that stop after twelve calendar months recognize the final days too early.
Co-termed add-ons should be prorated from their own start date to the main contract's end date, using the same convention as the main contract. A seat add-on starting on June 10 for a contract ending January 15, 2027 earns revenue over that shorter period. Using one convention for both keeps the schedules consistent and easy to reconcile.
Sources (checked October 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers.
More revenue recognition scenarios
How ScaleXP does this
ScaleXP builds revenue recognition schedules from your CRM contracts and prepares the journals for Xero or QuickBooks. Finance approves them before they’re posted. See how revenue recognition works in ScaleXP →
Close-time estimator
Your accounting system
How long does your close take today? Working days, roughly
Which of these do you still do manually? Select all that apply
Which of these takes the most time? Pick one
Your estimate
Your 3–5 day Xero or QuickBooks close could be closer to 2.5 days
Deferred revenue is where you would feel it first. ScaleXP prepares the schedules and journals for each task you selected from your live Xero or QuickBooks data. What stays with your team is the review and the posting decision.
Cue Technology saves 3–5 finance-team days a month. Xero customer
““Making the month-end revenue recognition process simplified.”
Revenue recognition
See how ScaleXP builds revenue schedules and journals from your invoice data.
In a 15- or 30-minute demo, we’ll show the relevant workflows using example data and discuss how they could apply to your finance process. Complex requirements? Discuss them with us first.