The Revenue Report in Iteras shows revenue for a selected period. You can optionally break it down by campaigns, countries, payment method, or custom fields (e.g., salesperson).
There are two ways to view revenue: by invoice date or by delivery date (accrual/“deferred” revenue). Both are useful for accurate bookkeeping.
Revenue based on invoice date
Revenue based on the invoice date is the total of all invoices created within the selected period. Iteras creates invoices when they are due to be sent.
Some publishers recognize revenue solely on the invoice date. A more accurate picture, however, comes from recognizing revenue as the product is delivered—i.e., accruing revenue over time. That means recognizing each month (or day/issue) the portion corresponding to what was delivered. The next section covers this.
Revenue based on delivery date (accrued revenue)
When viewing revenue on a delivery (accrual) basis, subscription revenue is distributed according to what was actually delivered during the reporting period:
Time-based subscriptions: by days delivered.
Issue-based subscriptions: by issues delivered.
Some accounting systems accrue an invoice entirely into the future at creation time. Iteras does not do this. We only accrue for elapsed delivery—what has actually happened—avoiding assumptions about the future.
Conceptually, when an invoice is generated, the system creates a matching amount to be accrued over the delivery period and tracks the remaining unaccrued amount (which can be extracted from the Revenue Report for reconciliation).
Time-based: a share is accrued every time the clock passes midnight.
Issue-based: accrual happens when each issue is delivered.
Examples
6-issue subscription invoiced at 300 DKK; 2 issues delivered in the period → accrued revenue = 300 × 2 / 6 = 100 DKK.
6-month time-based subscription invoiced at 300 DKK; report interval of 60 days → accrued revenue = 300 × 60 / 180 = 100 DKK.
Rules used by the accrued revenue report
Issue delivery date: Issues count as delivered on the issue’s run date. Only deliveries registered in Iteras are included. (Manual sends not registered will not count.)
Time-based day counting: Whole days are used, based on the subscription’s registered start/end times. Start/end times of day are considered and the first/last days are pro-rated. Month length varies (e.g., February vs. March), so the daily accrued amount can differ across months.
Recognition at end of subscription: Any remaining unaccrued revenue is recognized when a subscription ends. Example: a 6-issue subscription at 300 DKK stopped after 4 issues (no credit) recognizes 300 × (6 − 4) / 6 = 100 DKK on the end date.
Extensions don’t change original accrual: Adding extra issues/time does not change the accrual for the originally billed campaign quantity. In the 6-issue example, each original issue still recognizes 300 × 1 / 6 = 50 DKK. An added 7th issue does not create additional revenue (the 300 DKK has already been fully accrued). The same applies to time-based subscriptions.
Suspensions: Suspending a subscription pauses accrual.
If you extend the end date as compensation, accrual resumes so the daily amount stays consistent over the remaining period.
If you don’t extend, the remaining amount is recognized at the end of the suspension (the value is lost to the subscriber). Suspended subscriptions carry an unaccrued amount visible in the report; we recommend routinely reviewing suspensions (Iteras supports automatic stop for suspended subscriptions).
Credits: Credits are dated by the credit note date. Issuing a credit causes the remaining unaccrued amount (up to the credit) to be recognized as revenue on that date, and the invoice is credited for the same amount.
Example: stopped after 4 of 6 issues; credit 2 × 50 DKK = 100 DKK → recognize 100 DKK revenue and credit 100 DKK.
Manual credits are not spread evenly over the remaining period. The invoice continues to accrue until the credit amount fully offsets the remaining revenue (often before the original end date). If canceled in advance with immediate credit, the offset related to a suspension is handled immediately.
Delayed invoices: Revenue is still spread across the entire subscription period but is never recognized before the invoice date, to avoid retroactive report changes.
Example: the 300 DKK invoice isn’t issued until after issue #2 → a report covering the first two issues shows 0 DKK; on the invoice date it recognizes 300 × 2 / 6 = 100 DKK to catch up.
Dunning fees: Count as delivered on the invoice date and are not accrued.