Last updated: November 15, 2026
The short answer, from KORE1
A credit fund’s auditor tests loan by loan, so audit preparation means a support file tying each loan’s interest, PIK accruals, amendments, and fair value inputs to the loan system and administrator cash records. A temp data analyst can build it before fieldwork. KORE1 placements start a median 3 days after an offer (KORE1 placement data, October 2026, n=1,997).
The request arrives in the second week of January. It is about one loan. Five lines. Here is the specimen, and I made up the loan.
Interest: recalculate for the year, by period, cash and PIK
PIK: roll the balance forward, opening to closing, with each capitalization date
Amendments: all three, with the date each took effect
Fair value: the December 31 input and what supports it
Cash: match each receipt to the administrator’s cash file
Source:
Due: Friday
Nobody who has been through a year-end will think I invented the request. Look at the blank on the Source line. Three places could fill it. The loan system has the payment schedule, the administrator has the cash, and the third amendment is a PDF attached to an email from a deal team member who now works somewhere else. One person is the database, and that person is on vacation until the 15th. Naturally.
Multiply it by every loan in the sample, then by every loan the auditor adds when the first answers come back slowly. Two hundred loans, say. The request list is where the days actually go. My page on contract data staffing for private credit funds gives the audit request list one paragraph, and this post gives it the rest. KORE1 sells these seats, so weigh what I say with that in mind. The file itself needs nobody’s staffing, only somebody’s weeks.

What Does a Credit Fund’s Auditor Test Loan by Loan?
A credit fund’s audit support file ties each loan’s interest, PIK accruals, amendments, and fair value inputs to the loan system and the administrator’s cash records. The auditor picks loans, then asks for the file behind each one. A fund that can hand it over the same day has fewer follow-ups to answer.
Five things get tested. They are not equally hard.
Interest first. Plain arithmetic. The auditor recalculates it from the credit agreement: the rate, the reference rate and its reset dates, the day count, the period. If your system accrued 30/360 and the agreement says actual/360, you will hear about it, and the difference on one loan is small, while across the whole portfolio it is a long afternoon.
PIK is where the support file earns its keep. Interest that never reaches the bank still has to land in the balance on a date somebody can name, and the roll-forward has to agree to the capitalization terms in the agreement or in an amendment. Every PIK loan needs its own roll-forward. Loan by loan. A portfolio-level number proves nothing about loan 0417.
Amendments and waivers. The third amendment changed the margin and moved a maturity, and the waiver two months later has a signature page and no cover note, so the file has to say which document governs which period and who confirmed the system matches it. The auditor wants each one, the date it took effect, and proof the system was updated to match. Signed copies.
Then fair value. Fair value measurement under ASC 820 means the inputs and the support for them: for a performing loan, usually a yield or a spread, where it came from, and a note on why this loan sits where it does against comparable loans. The valuation owner decides the number. The file shows where it came from. Different jobs.
Last, cash. Every receipt in the loan system should match a receipt in the administrator’s file. Each break needs a reason in writing. No shrugs.

When Is the Audit Due, and When Should the Build Start?
The date comes from the custody rule. A registered investment adviser to a private fund can rely on the audit provision of 17 CFR 275.206(4)-2(b)(4), which asks for annual audited financial statements prepared under GAAP and distributed to every investor “within 120 days of the end of its fiscal year.” The same paragraph asks for an accountant registered with, and subject to regular inspection by, the PCAOB. For a calendar-year fund, 120 days after December 31 lands on April 30.
That is the outer limit. Your fund documents may set an earlier one. Use it. Nobody plans fieldwork for April 30.
The SEC’s staff keeps a custody rule FAQ that treats a fund of funds differently, so if yours is one, read it before you count. Two other facts for the record. The SEC formally withdrew the 2023 Safeguarding proposal in June 2025, so the text above is still the text. And on October 6, 2026 the SEC published a new proposal to rework the custody rules, with comments due December 7, 2026. Among other things it would lengthen the delivery window for funds of funds. It is a proposal. I won’t guess what happens to it, and it changes nothing about this audit season.
Now count back. Ask your auditor for the fieldwork start date. If the plan is January, you have the second half of November, a Thanksgiving week that is mostly gone, and December, where the last ten days are lost to the same people being out. That leaves about five usable weeks. Five weeks is tight. The calendar below is the one I would run.
| Support item | Source system | Who builds it | Ready by | What the auditor ties it to |
|---|---|---|---|---|
| Cash tie-out, loan by loan, one quarter first | Administrator cash file, bank statements, loan system receipts | Data analyst; fund accountant reviews the breaks | Nov 30 on September 30 data; rerun Jan 11 | Cash and interest receivable in the trial balance |
| Interest recalculation by loan and period | Loan system, rate resets, credit agreements | Data analyst | Dec 7; rerun Jan 11 | Interest income in the general ledger |
| PIK roll-forward with capitalization dates | Loan system, agreements and amendments | Data analyst; fund accountant signs off | Dec 7; rerun Jan 11 | Loan balances and PIK income, per loan |
| Amendment and waiver file | Signed documents, agent notices, credit files, loan system | Deal team supplies; data analyst indexes and tests the system against each one | Dec 14; update Jan 4 | Terms and effective dates behind each recalculation |
| Fair value input pack | Valuation committee package, loan system, market data | Data analyst assembles; the valuation owner approves | Layout Dec 14; year-end inputs Jan 11 | Reported fair value, per loan, and its support |
| Tie-out log, every break and its resolution | All of the above | Data analyst keeps it; a named employee owns it | Opens Nov 30; closed before fieldwork | The auditor’s follow-up questions |
Dates assume a calendar-year fund and January fieldwork. Move them to the fieldwork date in your auditor’s plan. Year-end balances can only be final after December 31, so the build is proved on September 30 data and rerun when the year-end close lands, which these dates place by January 11.
From KORE1: Staff the audit support file before fieldwork
If the calendar above does not fit the team you have, send KORE1 the request for a contract data analyst with five things: the number of loans in the portfolio, your fiscal year end, the systems involved (the loan system and the administrator), the start date, and the length. To price the seat first, use the data project contract team cost estimator and estimate the data seats. Accounting seats for the audit itself go through contract accountants for audit season.
Which Parts Are Data Work, and Which Stay With the Accountants?
The data analyst pulls the loan-level history from the loan system and the administrator, then builds the interest, PIK, amendment, and cash tie-outs. The financial statements, the accounting judgments, and the relationship with the auditor stay with the fund’s accountants. Keep that line sharp.
Where it blurs is the break review. The analyst finds that loan 0417 has a two-day cash difference. The accountant decides whether it needs an entry. If the analyst is deciding, you hired the wrong seat, and if the accountant is hunting for the difference by hand, you are paying accountant rates for query work. Both waste money. The first thing I build is never the dashboard. Here it is the cash tie-out, because it produces the most breaks and the breaks take the longest to explain. Start there.
If your accountants are booked solid in November, and the one who is free is not the person who knows the loan system, a temp data analyst covers the part of the work that is queries. If you also need hands on the audit itself, that is a different seat, and the post on bringing in contract accountants for year-end close covers it.
A quarter of the contract assignments KORE1 has ended ran 44 days or less (n=1,887). The calendar above runs about six weeks, so a seat for this build is a short one.
Why Does the Administrator’s Export Never Match the Loan System?
“The admin and our numbers never match.” I hear it in nearly those words, and it is usually true and usually nobody’s mistake. Two systems keep the same loan on different clocks.
Cash timing first. A payment arrives on the 30th, the agent bank posts it on the 31st, and the administrator books it on the 2nd, so a payment the loan system called received in October shows up in the administrator’s November file. Three dates. One payment. A break at month-end that nobody caused.
PIK capitalization dates come next. They are worse. One system capitalizes PIK on the interest payment date. The other accrues daily and capitalizes at month-end. Both are defensible. Neither agrees with the other for a few days every month, on every PIK loan.
Amendment effective dates sit underneath. An amendment signed on the 20th, effective the 1st, retroactive to a reference date in the prior quarter. Whoever keyed it into the loan system used the signing date, because the signing date was on the cover page. Fee accruals finish the list: an upfront fee amortizing over the life in one system and sitting entirely in income in the other.
Do not fix them. Write each one down once, with its date convention, so the tie-out can expect the gap and flag only the ones it did not expect. That mapping is what the analyst leaves behind, and it is the part that cannot be bought off a shelf, since it depends on your agreements. If the administrator is changing or coming in-house this year, the same mapping has to be rebuilt, which the post on moving or insourcing fund administration covers.
What Breaks If the Support File Is Not Ready When Fieldwork Starts?
Time breaks. I’ll stay with the operational cost, because I can name it, and I won’t predict what any auditor or regulator does with a late file.
Repeat requests are first. The same loan gets asked for three times, in three formats, by three people on the audit team, and each answer is built by hand from the same three systems.
Next, sample size. An auditor who cannot test a loan from your file quickly may test more loans to get the same comfort. Every extra loan is another request like the one at the top of this page. That is a risk to plan for.
Then the fieldwork weeks themselves. Your controller spends them answering email when they should be closing the books and reviewing the statements, and the investor delivery date, the one in your fund documents, gets closer while the file is still being assembled in a spreadsheet nobody else can read.

How Do You Leave a File You Can Rerun Next Year?
Three things. Written down before the analyst’s last day.
Documented queries over the loan system and the administrator feed, so the tie-out is a run and not a rebuild, and anybody who reads the query next January can see which date convention it assumed for each of the four gaps. A tie-out log with each break, its cause and its resolution, so next year’s analyst starts with the answers to this year’s questions. 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, since the contractor leaves.
Here is a log entry. It is a plain document.
Loan: 0417 Period: Q3
Break: administrator cash booked 2 days after the loan system receipt
Cause: agent bank posting date
Resolution: no entry; value date mapped in the query
Closed by: (employee name) Date:
The same tie-out feeds the investor pack, which is why LP reporting data infrastructure and this file share a source. Access is the other half. The analyst will see loan-level borrower data, so decide what to grant before the start date, and write the end date on the request. What access to grant a contract analyst works through the tiers, the log, and the last-day steps.
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 fund can convert the analyst to its own payroll with no conversion fee from KORE1. In the words of KORE1 partner Devin Hornick: “If this person completes 1,040 hours, then they are eligible to convert over to full time with that particular company at no additional charge from KORE1.”
Budget the seat with the cost estimator, or reach out to our team and talk to a recruiter. For the wider practice, see contract staffing.
What CFOs and Controllers Ask Before Fieldwork
When are a private fund’s audited financial statements due?
Within 120 days of fiscal year end for a fund whose adviser relies on the custody rule’s audit provision, which is April 30 for a calendar-year fund. Your fund documents may set an earlier date, and a fund of funds is treated differently under SEC staff guidance. Check the delivery date in your documents first.
What support does an auditor want for PIK interest?
A roll-forward for each loan from opening balance to closing balance, an interest recalculation from the credit agreement, and the capitalization dates tied to the agreement or an amendment. The auditor recalculates it, so the file has to let them do that without a call.
Our fund administrator says it can build this. Why add a data analyst?
Because the administrator automates its own work, which is the fund’s books, and the tie-out sits between the administrator and your loan system. Someone on your side has to hold both ends, and an administrator cannot check its own export against your records.
Can the same analyst rerun the file next year?
Often, and it goes fastest when the queries, the tie-out log, and a named owner are already on file. The analyst can return on a new assignment, and after 1,040 hours the fund can convert them with no conversion fee from KORE1.
Tie One Quarter Before December
Take September 30. Pick the loan system’s receipts for the quarter and the administrator’s cash file for the same quarter, and tie them loan by loan, one receipt at a time, until every difference has a date next to it. Write every break in a log with its cause. Replay a quarter that has already closed and score it against what you know.
It takes a few days with the right person. Count the breaks. The count tells you how big the build is, and the causes tell you which of the four date rules your fund actually runs on. If the count is small, you may not need a seat at all.
If you run it, I would like to hear what the breaks looked like. Connect with me on LinkedIn.

