Transaction-Date Written Premium

Why Transaction Dates Matter

A policy can change at one point in time but have that change entered into the premium records later. For example, an endorsement might take effect on December 20 but not be processed until January 8. The coverage change belongs to the December 20 effective date; the premium transaction may belong to January 8 for transaction-date reporting. Which date applies depends on the measure being constructed.

This tutorial focuses on written premium recorded by transaction date. The central task is to identify each premium-changing transaction, retain its sign and recorded date, and assign it to the appropriate reporting period. Do not substitute a coverage effective date for a transaction date unless the specified data convention explicitly tells you to do so.

Definition: A premium transaction is a recorded entry that adds to or subtracts from the premium associated with a policy or coverage. Its transaction date is the date on which the entry is recorded for the applicable premium accounting or reporting system. Its effective date is the date on which the policy change applies to coverage. These dates can differ.

For a direct written-premium ledger, an issuance is generally a positive entry. An endorsement can add premium or return premium, so its entry can be positive or negative. A cancellation return premium is negative when recorded as a reduction. An audit can later add or return premium. The amount of an entry is the change recorded by that transaction, not necessarily the revised total premium shown on a policy screen.

The precise contents of a written-premium measure depend on the stated accounting definition and system conventions. For example, an analysis should specify whether it includes particular fees or taxes. The examples below use policy premium entries only, and use each stated transaction date as the date for assigning the entry to a calendar year. Written premium is not the same as a cash receipt: the date a policyholder pays does not, by itself, determine the transaction-date written-premium entry.

Calculating Written Premium by Transaction Date

Let $\Delta P_j$ be the signed premium change for transaction $j$, and let $t_j$ be its transaction date. For calendar year $y$, transaction-date written premium is the sum of the entries whose transaction dates fall in that year:

WP_y^{\text{trans}}=\sum_{j:\,t_j\in y}\Delta P_j.

A positive $\Delta P_j$ increases the recorded total; a negative $\Delta P_j$ reduces it. This is an aggregation rule for transaction entries, not a rule for determining how much premium a policy should have. For the latter, one would need the applicable rating and transaction-calculation rules.

An initial policy issuance contributes its recorded issuance amount. Later transactions contribute only their own changes. This distinction is important when a system also displays a revised, cumulative policy premium after each transaction. Summing cumulative amounts as if they were changes counts earlier premium more than once.

Key result: To calculate transaction-date written premium for a period, select entries by transaction date, preserve each entry’s sign, and sum the transaction amounts. The coverage effective dates explain when changes apply to coverage, but do not replace transaction dates in this measure.

Worked Example: Reversal and Replacement Entries

A hypothetical policy is issued on January 28, 2026, for a recorded premium of $1,500. A February 12 endorsement entry reduces premium by $125. On February 20, the administrator reverses that entry and records a corrected endorsement reducing premium by $80. All three entries have 2026 transaction dates. Calculate the policy’s transaction-date written premium for 2026 and explain how the entries should be handled.

Method. Sum the signed transaction changes, including both the reversal and the replacement. The issuance is positive, the original reduction is negative, the reversal is positive, and the corrected reduction is negative:

WP_{2026}^{\text{trans}} =1{,}500-125+125-80 =1{,}420.

The original $125 reduction and its $125 reversal cancel. The remaining entries are the $1,500 issuance and the corrected $80 reduction, so the net recorded amount is $1,420. As a check, the running total after the issuance is $1,500; after the first endorsement it is $1,375; after its reversal it returns to $1,500; and after the corrected endorsement it is $1,420.

Common mistake avoided: Do not omit the reversal because the first endorsement was later corrected. Both entries were recorded and both affect the transaction ledger. Omitting the reversal would give $1{,}500-125-80=1{,}295$, understating the correctly recorded total by $125.

Transaction Date Versus Effective Date

The transaction date determines when an entry is recorded for the transaction-date measure. The effective date identifies when the policy change applies. Neither date is inherently “more correct”; each answers a different question. A report that groups premium changes by transaction date describes the flow of recorded changes over time. A report organized by effective date instead associates those changes with when coverage was changed. The reporting objective and data convention determine which basis is appropriate.

This distinction matters near reporting-period boundaries. A change effective in one calendar year can be recorded in the next. If the question asks for transaction-date written premium, the recorded transaction date controls. The effective date remains useful context, but does not move the entry into another transaction year.

Identify the measure.
Confirm that the requested quantity is written premium by transaction date, and establish which date field the data convention treats as the transaction date.

List the premium-changing entries.
Include issuance, endorsement, cancellation, audit, and any required correction or reversal entries that meet the measure’s scope.

Assign signs and periods.
Use positive amounts for additions and negative amounts for reductions; assign each entry to a period using its transaction date.

Sum and reconcile.
Add the signed entries. Where available, check that the net changes reconcile the opening recorded amount to the resulting recorded amount.

Worked Example: An Endorsement Recorded in the Following Year

A hypothetical policy is issued on October 1, 2026, with a recorded premium of $1,800. An endorsement increasing premium by $240 is effective December 20, 2026, but is entered and recorded on January 8, 2027. Assume the applicable convention uses January 8 as the transaction date. Find the transaction-date written premium for each calendar year and the combined amount across both years.

Method. The issuance is a 2026 transaction for $1,800. The endorsement is a 2027 transaction for $240, even though it applies to coverage beginning in 2026.

WP_{2026}^{\text{trans}}=1{,}800, \qquad WP_{2027}^{\text{trans}}=240.

Across the two calendar years, the total is $1{,}800+240=2{,}040$. The check is that the combined transaction entries equal the policy’s recorded premium after the endorsement: $1,800 before the change plus the $240 increase equals $2,040.

Common mistake avoided: Assigning the $240 to 2026 because the endorsement is effective December 20 would produce $2,040 for 2026 and zero for 2027. That groups the entry by effective date, not by the stated transaction-date convention.

Issuance, Endorsement, Cancellation, and Audit Entries

Different transaction types can change recorded written premium, but the same signed-entry principle applies to each. An issuance records the initial premium amount. An endorsement records its premium change, rather than repeating the full policy premium. A cancellation transaction can record a return premium as a negative entry. An audit transaction can record an additional or return premium after the relevant information is evaluated. In each case, the transaction-date measure uses the date on which the entry is recorded under the stated convention.

This description does not prescribe how an endorsement’s premium change, cancellation return, or audit amount must be calculated. Those calculations can depend on policy terms and specific rating or accounting methods. For transaction-date measurement, use the signed amount and transaction date provided by the problem or system; do not infer an amount from dates alone.

A useful reconciliation follows directly from the meaning of a transaction change. If $P_k$ is the recorded premium after transaction $k$, and $\Delta P_k$ is that transaction’s change, then:

P_k=P_{k-1}+\Delta P_k.

Applying this relation repeatedly gives $P_n=P_0+\Delta P_1+\Delta P_2+\cdots+\Delta P_n$. Therefore, the sum of all signed changes equals the final recorded amount minus the opening amount. This is why a ledger of increments can be checked against the opening and ending recorded totals. The check is valid only when the transactions in the sum cover the full interval and use consistent definitions; missing, duplicated, or out-of-scope entries break the reconciliation.

Worked Example: Cancellation and Later Audit Entry

A hypothetical commercial policy has these recorded premium entries: an issuance of $2,400 on March 2, 2026; an endorsement increase of $360 recorded on May 10, 2026; a cancellation return premium of $700 recorded on September 3, 2026; and an audit increase of $180 recorded on February 6, 2027. The cancellation is effective August 15, 2026, and the audit concerns the 2026 policy period. The stated convention assigns entries by their recorded transaction dates. Calculate transaction-date written premium for 2026 and 2027 and verify the combined total.

Method. Treat the issuance and increases as positive entries and the cancellation return as a negative entry. Use the transaction dates to allocate the cancellation and audit entries to years.

For 2026, the issuance, endorsement, and cancellation entries are included:

WP_{2026}^{\text{trans}} =2{,}400+360-700 =2{,}060.

For 2027, the audit increase is the only listed entry:

WP_{2027}^{\text{trans}}=180.

The combined amount is $2{,}060+180=2{,}240$. It also equals the sum of all four entries: $2{,}400+360-700+180=2{,}240$. As a further check, the opening amount before the listed entries is zero, and the ending amount after them is $2,240.

Common mistake avoided: Do not place the cancellation return in 2026 merely because the cancellation took effect in August; under the stated convention it is recorded in September, which is also 2026 here. More importantly, do not place the audit increase in 2026 just because it concerns the 2026 policy period. Its transaction date is in 2027, so it contributes to 2027 transaction-date written premium.

Common Errors and Practical Checks

Transaction-date written premium is straightforward to sum once the entries are defined, but several data and interpretation errors can change the result:

Using the wrong date. Grouping by effective date when the question asks for transaction-date written premium can move entries across calendar periods.
Ignoring signs. A return premium reduces the recorded amount; adding its absolute value instead of subtracting it overstates written premium.
Double counting cumulative totals. If a system shows policy premium after each transaction, do not sum each displayed total. Sum transaction changes, or first convert cumulative snapshots into changes.
Dropping reversals. A reversal is a recorded entry. Include it with its sign, even if a corrected replacement entry follows.
Confusing premium with cash. A transaction-date written-premium entry is not necessarily a payment or refund received on that date.
Assuming every system uses the same date field. Determine whether the stipulated convention uses a booking date, posting date, or another recorded date before assigning transactions to periods.

For a practical reconciliation, first verify that every listed transaction has a policy identifier, a transaction amount, a sign, and the date field required by the measure. Then check the period subtotals against the total of all included entries. If opening and ending recorded premium balances are available, compare their difference with the net sum of transaction changes over the same interval.

Key takeaway: Transaction-date written premium is the signed sum of premium changes recorded in the reporting period. Keep the transaction date distinct from the effective date, and use changes—not repeated cumulative policy totals—to avoid misallocation and double counting.

Check Your Understanding

For each problem, use the stated transaction-date convention and treat the listed amounts as signed premium changes unless otherwise stated.

A hypothetical policy is issued for $980 on November 18, 2025. An endorsement adds $145 and is effective December 29, 2025, but is recorded on January 3, 2026. What is transaction-date written premium in each year? (Answer: 2025: $980; 2026: $145.)
A policy has a $2,250 issuance and a $175 endorsement reduction, both recorded in 2026. What is its 2026 transaction-date written premium? (Answer: $2,075.)
A 2026 policy ledger shows an issuance of $1,600, an endorsement increase of $210, a reversal of that endorsement for $-$210$, and a corrected endorsement increase of $165. What is the net transaction-date written premium for 2026? (Answer: $1,765.)
A hypothetical policy has a $3,100 issuance recorded in 2026. A cancellation return of $900 is effective December 30, 2026, but recorded on January 4, 2027. What is transaction-date written premium in each year, and what is the combined total? (Answer: 2026: $3,100; 2027: $-$900$; combined: $2,200.)
A policy’s recorded premium is $1,850 after its issuance, then $2,020 after a later transaction, and $1,940 after a third transaction. The issuance and both later transactions are recorded in the same year. What are the two transaction changes after issuance, and what is written premium for the year? (Answer: changes of +$170 and $-$80$; written premium: $1,940.)

What You'll Learn