Back to Blog

Statutory Annual Statement Preparation: The Data Work an Insurer Can Staff on Contract Before March 1

AccountingBig DataHiring

Last updated: November 19, 2026

The short answer, from KORE1

Statutory annual statement preparation splits into data work and accounting judgment: a temp data analyst can own the December pulls and January tie-outs for investment, reinsurance, and claims schedules while the statutory accountant keeps sign-off. KORE1 placements start a median 3 days after an offer (KORE1 placement data, October 2026, n=1,997).

The investment schedule is off by 74,677. It is the second week of January and the number has been off since Tuesday. Three systems. Each believes it is right. Here is the tie-out sheet. I made the figures up. I did not make up the shape.

SCHEDULE D, BONDS, BOOK/ADJUSTED CARRYING VALUE, DECEMBER 31
Investment accounting system: 412,806,119
Custodian file: 412,806,119
General ledger: 412,731,442
Difference to the ledger: 74,677
Cause: open
Owner:

Two of the three agree. The ledger is the odd one out. That sounds like good news until you ask who posted December’s amortization entries, and in which period. An accountant can spend a day finding the answer by hand, opening one extract after another and checking each against the ledger line by line, while someone with all three extracts already open can often find it in an afternoon, because it is a query and not a judgment. The split between those two jobs is the whole subject of this post.

KORE1 places contract data seats for carriers, and its insurance staffing and insurance IT staffing pages say how. It also sells them, so weigh what I say about them with that in mind. The sequencing below holds whether you staff it or not.

Three closed ledger notebooks in gray, white and tan, each with an orange ribbon bookmark on a wooden desk, the three source systems behind an insurer's statutory schedules

What Is Due, and When?

An insurer’s annual statement is its yearly financial filing with the insurance department of its home state, prepared on statutory accounting principles in the NAIC annual statement format. In New York it is due on or before March 1. The audited statutory financial report follows by June 1 under the NAIC model rule.

New York’s version is section 307(a)(1) of the Insurance Law. Insurers “shall file in the office of the superintendent, annually on or before the first day of March” a statement of their condition at year end. The statute also has the statement verified under oath by at least two of the insurer’s principal officers, a detail worth holding onto, because it decides later in this post who can do what and who cannot. Remember it.

The audit comes after. Model 205, the NAIC Annual Financial Reporting Model Regulation, says insurers “shall file an audited financial report with the commissioner on or before June 1 for the year ended December 31 immediately preceding.” That is Section 4A of the model. A model is not a statute. What binds you is your domicile’s adoption of it, and I read New York’s statute and the model, not yours. Check yours.

Quarterly statements are also required. I am not printing a date for them, since the date comes from the NAIC quarterly instructions and your filing state, and I have not read your state’s.

Now count back from March 1. In 2027 it is a Monday, which makes the weekend before it the real deadline. December 1 is a Tuesday. Because the year-end close will not finish until well into January, the work has two windows, December to build the pulls against a quarter you have already tied and January to rerun them on the real year-end numbers. The calendar below is the one I would run.

StepSource systemSeatSign-off ownerWeek due
List every schedule with its source system and the person who can pull itYour annual statement checklist, system ownersData analyst drafts it; the controller fills the blanksControllerNov 30
December pull: investment detail tied to the ledger, proved on the latest quarter you have already tiedInvestment accounting system, custodian file, general ledgerData analystStatutory accountantWeek of Dec 7
December pull: reinsurance recoverables by treaty and counterpartyTreaty file or reinsurance system, general ledgerData analystStatutory accountantWeek of Dec 14
December pull: claims extracts for the schedulesClaims system, general ledgerData analyst; the claims lead confirms the extractStatutory accountantWeek of Dec 14
January tie-outs: all three rerun on year-end data, every break logged with its causeThe three pulls above, the tie-out logData analyst keeps the log; a named employee owns itStatutory accountantWeeks of Jan 11 and Jan 18
Break review, admitted and nonadmitted asset calls, schedules lockedThe tie-out logStatutory accountant; no contract seatStatutory accountantWeeks of Feb 1 and Feb 8
Annual statement filedThe locked schedulesOfficers and statutory accountant; no contract seatPrincipal officers, under oath in New YorkMonday, Mar 1
Audited statutory financial report filedAuditor’s workpapers, the tie-out workbook handed overStatutory accountant with the auditorStatutory accountantTuesday, Jun 1

Dates assume a calendar-year insurer and the 2027 calendar, and count back from March 1. The weeks are my planning proposal, not a regulatory standard. Year-end balances are final only after the December 31 close, so the build is proved on a quarter you have already tied and rerun when the year-end close lands. March 1 and June 1 come from the sources above; no quarterly date is printed.

From KORE1: Staff statutory season data work before December

If the calendar above does not fit the team you have, send KORE1 the request for a contract data analyst with five things: your line of business, the schedules in scope, the source systems involved, the start date, and the length. To price the seat first, use the data project contract team cost estimator. If the accountants are the bottleneck instead, that is a different seat, covered under contract accountants for audit season.

Which Parts Are Data Work a Contract Analyst Can Own?

Four jobs, and the first carries the most rows. Investment detail. The analyst pulls every holding from the investment accounting system, rolls it up to the Schedule D totals for bonds and stocks in the NAIC annual statement blank, and ties those totals to the general ledger. Each difference gets a cause or an open flag. That is the sheet at the top of this page. It is a query job.

Reinsurance recoverables are second, by treaty and by counterparty. On a property and casualty statement they land in Schedule F, and on a life statement the reinsurance schedules are Schedule S. The data job is getting the treaty file, the claims system, and the ledger to agree on who the counterparty is, what it owes on each treaty and as of which date, a job that sounds simple until you open the treaty file. Whether a recoverable is collectible is an accounting call, and not the analyst’s.

Claims extracts feed the loss schedules. On a property and casualty statement that means Schedule P, the analysis of losses and loss expenses, organized by line of business and year. The analyst builds the extract and ties paid amounts to the ledger. The reserve numbers belong to other people, and their reasoning is outside this post.

The fourth is the tie-out log. Every break. Its cause. Who closed it. It is the one deliverable that outlasts the season.

None of this is exotic. In the statutory teams I have worked with, a lot of it is still done by hand, by whoever knows which extract is current and which extract only looks current because someone refreshed it on a Friday afternoon. The first thing I would ask a controller is which schedule has a name next to it, and which has a shrug.

Which Parts Stay With the Statutory Accountant?

Keep the line sharp.

Statutory accounting judgment stays with the accountant: how a transaction is treated under statutory accounting principles, which is not always how the ledger treats it, and which no query will settle for you. So does the admitted and nonadmitted call, which moves surplus. The analyst can pull the list of items that might qualify. The accountant decides which ones do. The auditor relationship stays too, since the auditor needs one person who answers for the numbers.

And the signature. Under the New York statute above, at least two principal officers verify the statement under oath. A contractor can build every number they swear to. The person who swears is an officer.

Where it blurs is the first break. The analyst finds the 74,677 and the likely cause. Whether it becomes an adjusting entry is the accountant’s decision, made with the cause already in hand instead of a hunt for it. That is a better use of a statutory accountant’s December than reading three extracts side by side to find a number that a query would have found in an afternoon.

Why Do the Schedules Never Tie on the First Pass?

Each one starts somewhere else. Investments live in the investment accounting system and the custodian’s file. Reinsurance lives in a treaty workbook and whatever feeds the ceded entries. Claims live in a system that was built to pay claims on time, with footing to a ledger somewhere far down its list of jobs, and the extract it produces reflects that.

Cutoffs disagree next. A bond sold on December 29 is booked on the trade date in one system and the settlement date in another, so it sits in December’s balance in one place and January’s in another. Nobody made a mistake. Both systems are doing what they were set up to do.

Names are worse. The treaty file says Acme Reinsurance Company Ltd. The claims system says ACME RE. The ledger sub-account says Acme Re Co. Three names, one counterparty, and the schedule wants one row for it. Somebody has to build the crosswalk, and until they do, every reinsurance tie-out is a manual match on a name.

Two aligned stacks of blank paper with a steel ruler laid across both and an orange tab on one, a statutory schedule tie-out between two systems

Then there is the person. Every statutory team has one. They know that the claims extract run on the third double counts reopened claims, that the tab called FINAL v7 is not final, and that one reinsurer’s balance needs a manual adjustment every quarter before it ties. None of it is written anywhere, and it walks out the door at a vacation, a resignation, or a retirement. One person is the database. Ask them to write it down. Now, while they are still here. Put it in the log.

What Breaks If the Schedules Are Not Tied Before Filing Week?

Time breaks, and I will stay with the operational cost, because that is the part I can name. I will not predict what any regulator does.

The review turns into the tie-out. The accountant was supposed to spend February on judgment, and ends up spending it reconciling schedules nobody has tied. At least two officers then swear to a statement that was tied in the last week.

The weekend. A team that starts tying schedules the week of February 22 is working the weekend of February 27, with March 1 on a Monday behind it.

Then corrections. Whatever you catch after filing moves into an amended filing, which means the same schedules rebuilt by the same tired people after everyone believed the season was over and the controller had already told the CFO it was done. I can’t tell you how a state insurance department will treat one. I can tell you who rebuilds it, and it is the same people who just finished.

Empty office desk at dusk with a lit orange lamp, three gray binders and a pushed-back chair, the filing weekend before the March 1 annual statement

How Do You Leave a Build the Same Contractor Can Rerun Next Season?

Three things. Written down before the analyst’s last day. Documented queries, so the schedule pull is a run and not a rebuild, and so whoever reads one next December can see which cutoff rule it used. A tie-out workbook with each break and its fix. And a named owner, an employee, who is the person the auditor calls. A contractor can build all of it. An employee should own it. The contractor leaves.

Here is what an entry looks like, and it closes the sheet at the top of this page. Made up again.

TIE-OUT LOG, ENTRY 9
Schedule: D, bonds   As of: December 31
Break: 74,677, general ledger below investment system
Cause: December amortization entry posted in the January period
Resolution: correcting entry approved by the statutory accountant; query now compares by accounting period, not posting date
Closed by: (employee name)   Date:

Access is the other half. The claims extract carries policyholder names, so scope the grant to the tables the schedules need and put an end date on the request before day one, which means nobody has to remember to revoke it in March. Keep it narrow. Policyholder data access for contractors works through the tiers, the log, and the last-day steps. If your season also includes valuation filings, that is a separate workstream, and I cover it under life and annuity data operations.

From KORE1: How a temp data seat works

KORE1 is the W2 employer. It pays the contractor weekly, on Fridays, and carries the insurance and the paid sick leave. The seat bills hourly. After 1,040 hours the carrier can convert the analyst to its own payroll with no conversion fee from KORE1. The median KORE1 contract assignment runs 116 days (KORE1 placement data, n=1,887), which is longer than the 90 days between December 1 and March 1.

Some KORE1 contractors stay with a client for years. In the words of KORE1’s Robert Ardell: “We’ve had contractors with us for probably some 10 years plus.” A returning seasonal analyst is a normal pattern.

To budget the seat, estimate a statutory season data seat with the cost estimator, or reach out to our team and talk to a recruiter. For the wider practice, see contract staffing.

What Controllers Ask Before December

So when is the annual statement actually due?

March 1 under New York Insurance Law 307(a)(1), and the audited statutory financial report follows by June 1 under NAIC Model 205. Other domiciles set their own dates, so check the filing state’s statute. Quarterly statements are also required, and this post prints no date for them.

Can a contractor sign or file any of it?

Not the signing part. Filing and the officers’ attestation stay with the carrier’s officers and statutory accountant. A contractor builds the pulls and tie-outs behind the numbers, and an employee owns the schedules those numbers land in.

What access does a statutory data contractor need?

Read access to the investment, reinsurance, and claims extracts the schedules draw on, scoped to those tables, with an end date written on the request. Claims data can carry policyholder detail, which is the part to settle before the start date. The tiers are in what to grant, log and revoke.

Does the same analyst come back next season?

Often. The second season starts from the queries and the tie-out log instead of a blank page. The analyst can return on a new assignment, and after 1,040 hours the carrier can convert them to its own payroll with no conversion fee from KORE1.

List Every Schedule’s Source System and Owner Before December 1

Open a sheet. One row per schedule in your annual statement, and for each one write the source system and the name of the person who can pull it. Where the name is a vendor ticket queue, or blank, you have found where the days actually go.

It takes an afternoon. What you get back is the answer to whether you need a seat for the season or a conversation with the person who is the database.

If you run it, I would like to hear what the blanks looked like. Connect with me on LinkedIn.