Debt Schedules: What They Are and How to Simplify Them

A debt schedule is the operating record of an organization's debt portfolio. For public finance teams, that record sits behind bond management, fund and project allocations, refunding analysis, debt service planning, and the Annual Comprehensive Financial Report (ACFR).

That makes the schedule one of the highest-stakes records your team maintains. When it stays accurate, the same dataset can answer portfolio, planning, and reporting questions without separate workbooks or manual reconciliation. When it drifts, every downstream process drifts with it.

If your team is like most, you still maintain the schedule in spreadsheets, and that works while one person holds the formulas, tabs, and institutional knowledge. The moment your portfolio expands, a refunding restructures prior maturities, or the person who built the file moves on, the schedule starts costing more time than it saves.

This guide covers what belongs in a public finance debt schedule, shows what one looks like in practice, walks through how to build and maintain one, and clarifies how it differs from a debt service schedule and an amortization schedule. It also shows how your team can move from a hand-maintained spreadsheet to a maintained, audit-ready record.

What a debt schedule includes

A useful debt schedule starts with the core facts of each obligation, then layers in the maturity, allocation, and reporting data your team needs to answer real questions.

At a minimum, it should identify the issuer, obligation type, outstanding principal, interest treatment, payment timing, and final maturity.

For public finance teams, the schedule includes the fields below:

• Issuance details: Issue name, series, CUSIP details when applicable, delivery or closing date, original principal, premium or discount, and purpose.
• Debt type: General obligation bonds, revenue bonds, certificates of participation, direct placements, leases, subscription-based information technology arrangements when tracked alongside debt, or other long-term obligations.
• Principal by maturity: The principal amount due in each fiscal year, calendar year, or payment date view.
• Interest by maturity: Interest due for each period, including fixed or variable rate treatment, accrual conventions, and interest payment dates.
• Rates and terms: Coupon rates, variable rate reset terms, interest rate mode, amortization method, final maturity date, and call provisions.
• Fund and project allocations: The funds, departments, projects, purposes, or other dimensions tied to each issue or payment.
• Refunding lineage: Which prior issues were refunded, which maturities were refunded, and how refunding activity affects the remaining payment history.
• Reporting fields: Amounts and categories needed for long-term obligation disclosure, journal entries, debt service fund planning, and ACFR tables.
• Documents and notes: Official statements, closing transcripts, debt service schedules, continuing disclosure agreements, covenants, reminders, and notes your team needs to preserve institutional knowledge.

The exact columns depend on your organization, but the purpose stays the same. The schedule is strongest when you can trace a number from the portfolio view to the issue, maturity, fund, project, and source document without hunting through a shared drive.

A sample public finance debt schedule

The example below shows a simplified schedule for one bond issue. Real schedules often include more columns, separate tabs for payment dates, or views by fund and project, but this structure gives you the basic shape.

The most important detail is the relationship between the columns.

If a treasurer wants to see all debt service tied to a project, the schedule should support that view. If a reporting manager needs roll-forward tables by activity and fund, the schedule should support that too.

That is where many hand-maintained Excel sheets fall short. A single debt issue may need to be viewed through multiple lenses, from fund allocations and project tracking to debt service planning and financial reporting. When that information is spread across multiple tabs, files, or owners, your team has a hard time keeping a consistent, updated record.

How to build a debt schedule

Building a debt schedule gives your team a record to maintain through new issuances, refundings, staff turnover, audit requests, and year-end reporting.

Start with the source documents

A debt schedule is only as reliable as the information behind it. Begin by gathering the documents that establish each obligation and define its payment terms. For bond issues, key sources often include:

• Official statements
• Closing transcripts
• Debt service schedules
• Continuing disclosure agreements
• Bond counsel documents
• Internal allocation workpapers

Together, these documents provide the legal, financial, and reporting details that form the foundation of the debt record.

You should also capture information such as the issue name, series, original principal amount, purpose, interest rates, maturity dates, call provisions, payment frequency, and any premiums, discounts, or issuance costs required for reporting.

If an issue has been refunded, document that relationship as part of the debt record. More on that later.

Before building the schedule, also decide which obligations belong in the portfolio. You'll typically track bonds, direct placements, notes, leases, and other long-term obligations within the same debt schedule.

Add principal and interest by maturity

A debt schedule should show the payment pattern over time. For each issue, enter principal due, interest due, and total debt service for each maturity or payment period.

You'll usually need more than one view of the same payment data.

• Payment-date view: Shows each actual payment date and amount.
• Fiscal-year view: Groups payments by your organization's fiscal year.
• Calendar-year view: Groups payments by calendar year when needed for external requests.
• Maturity view: Shows principal by maturity, often useful for bond and portfolio analysis.

The view you use depends on the question. Budget planning often needs fiscal-year totals, while bond analysis often needs maturity-level principal and interest.

Map payments to funds and projects

Many public finance obligations support more than one project or funding source. A debt schedule should reflect those relationships, not just the debt itself.

For each obligation, capture the allocation information your organization uses to manage and report debt. Common categories include funds, projects, departments, purposes, revenue sources, and credit types.

For example, a bond issue used to finance multiple capital projects should be allocated across those projects within the schedule. Likewise, debt service may need to be allocated across multiple funds for budgeting, reporting, or reimbursement purposes.

These allocations help turn a debt schedule from a repayment record into a management tool. A well-maintained schedule should make it easy to answer questions such as:

• Which projects has this debt issue funded?
• Which debt issues support a given project?
• How much debt service is allocated to a specific fund next fiscal year?
• How has a refund affected historical allocations?
• What information do you need for ACFR reporting?

Record refunding lineage

Refundings are difficult to maintain in a schedule because they change the relationship between old and new obligations. Marking an issue as refunded is only the first step.

Your schedule should identify the prior issue, the affected maturities, and the payment history after the transaction.

DebtBook's true lineage refunding tracking helps your team see prior and later refunding relationships, then review the refunding date in schedule view and the impact across issue or allocation views.

That lineage will be useful years later, especially when new team members need that context, like why a project is tied to several issues or why a maturity no longer appears where an old spreadsheet says it should.

Tie the schedule to reporting outputs

A debt schedule should support reporting throughout the year, not just track balances and payments.

As you build the schedule, make sure the data can be used for the reports your organization relies on, including long-term obligation disclosures, debt roll forwards, journal entries, debt service planning, continuing disclosure filings, and ACFR reporting.

The goal is simple: enter information once and use it many times. If reporting requires rebuilding schedules, rekeying data, or maintaining separate spreadsheets, the debt record is likely incomplete.

A practical way to test a debt schedule is to see whether it can answer common reporting and audit questions without additional work:

• How much debt is outstanding by obligation type?
• What are the remaining principal and interest payments by year?
• Can you roll long-term obligations forward from beginning balance to ending balance?
• How much debt service is allocated to a specific fund or project?
• Can you trace refunding relationships across multiple debt issues?
• Can an auditor trace reported balances back to your supporting documentation?

If those questions can be answered directly from the schedule, it is more likely to serve as a reliable source of truth for the debt portfolio.

Debt schedule vs. debt service schedule vs. amortization schedule

These terms often overlap because they all involve principal, interest, and time. The difference is scope.

A debt service schedule can feed a debt schedule, and an amortization schedule can support one obligation within it. But the debt schedule is the broader operating record because it connects payment math to portfolio management and reporting.

A debt schedule is a living record

It's tempting to think of a debt schedule as a document you build once and update occasionally. In practice, it functions more like a living record of your debt portfolio.

Every major debt event affects the schedule. New issuances add obligations, debt service payments reduce balances, refundings create relationships between old and new debt, and reporting requirements introduce new allocation and disclosure needs.

If the schedule is not updated as those events occur, it becomes less reliable for planning, reporting, and audit support.

The table below shows how common debt management activities affect the debt schedule over time.

A well-maintained debt schedule shows these changes as they occur. That allows the same record to support debt service planning, refunding analysis, budget development, audit requests, and ACFR reporting without requiring separate spreadsheets or manual reconciliation.

Why manual debt schedules become risky

If the schedule has to change every time the portfolio does, the way it's maintained matters as much as what's in it. Spreadsheets are flexible, which is why most public finance teams have relied on them for years. As your portfolio grows, that flexibility makes it harder to control formulas, versions, and allocation logic.

A hand-maintained schedule can work while one person knows the issues, tabs, and formulas.

The spreadsheet becomes a bottleneck when that person retires, a refunding changes the structure, a new issue funds several projects, or auditors ask for support by fund.

As the portfolio expands, manual processes become harder to scale and verify. Common risks include:

• Version control problems: Multiple files show different balances or payment totals.
• Formula risk: A copied formula misses a row, references the wrong tab, or breaks during a schedule update.
• Allocation drift: Fund or project allocations change in one view but not another.
• Refunding confusion: Old issues, refunded maturities, and replacement issues are hard to trace.
• Reporting rework: Your team rebuilds ACFR tables manually each year because the schedule is not mapped to reporting outputs.
• Key-person risk: Your organization depends on the one person who understands the file.

UNC Charlotte's experience shows how quickly this can become operationally painful. Before DebtBook, the university managed a $500 million debt portfolio through a complex web of spreadsheets. Each debt had its own issuance tab and refunding activity, which made reporting difficult.

After moving to DebtBook, the university was able to view debt by issuance, project, and funding source while significantly reducing the time required for annual reporting.

How DebtBook simplifies debt schedules

DebtBook helps public finance teams maintain debt schedules in a single system rather than across multiple spreadsheets.

Debt Management centralizes debt schedules, allocations, payment tracking, refunding history, and reporting in one place. Your team can view debt by issue, fund, project, purpose, or other dimensions without maintaining separate versions of the same data.

DebtBook also tracks refunding relationships and allocated debt service schedules, helping your team preserve portfolio history while reducing manual reporting work. The result is that the debt schedule stops being a fragile spreadsheet that lives with one person and starts functioning as a maintained system of record, ready for the next issuance, the next refunding, the audit, and the person who eventually takes over the file.

Debt schedule FAQ

What is a debt schedule?

A debt schedule is a table that organizes an organization's outstanding debt obligations and the information needed to manage them.

For public finance teams, it usually covers bond issues and other long-term obligations, principal and interest by maturity, rates, call dates, fund and project allocations, refunding history, and reporting fields.

Is a debt schedule the same as a debt service schedule?

No. A debt service schedule shows scheduled principal and interest payments over time. A debt schedule is broader because it adds issue details, balances, rates, maturities, allocations, documents, reporting categories, and refunding history.

Is a debt schedule the same as an amortization schedule?

No. An amortization schedule shows how individual payments reduce principal and cover interest for a specific obligation. A debt schedule can include amortization information, but it usually tracks the full portfolio and connects obligations to reporting, budgeting, and allocation needs.

Who uses a debt schedule?

Treasurers, debt managers, finance directors, CFOs, accounting teams, auditors, financial advisors, and bond counsel all use debt schedule information at different points. The most frequent owners are treasury teams and debt managers because they manage the debt portfolio and payment obligations.

Should refunded debt remain on a debt schedule?

In most cases, yes. While refunded obligations may no longer be outstanding, maintaining their relationship to replacement debt supports audit requirements, historical analysis, and financial reporting.

What should a public finance debt schedule include?

A public finance debt schedule should include the issue name, original principal, outstanding principal, principal and interest by maturity, interest rates, payment dates, call dates, and final maturity.

It should also include debt type, refunding history, reporting categories, source documents, notes, and fund or project allocations when your organization reports or manages debt across those dimensions.

What information do auditors typically request from a debt schedule?

Auditors commonly request outstanding balances, debt service schedules, debt roll forwards, supporting documents, refunding information, allocation details, and evidence supporting reported balances and disclosures.

How often should a debt schedule be updated?

Update the schedule whenever your organization issues new debt, makes principal or interest payments, completes a refunding, changes allocations, updates variable rates, modifies reporting categories, or prepares year-end reporting.

Maintaining it throughout the year keeps audit season from becoming a full rebuild.

Can one debt issue be allocated across multiple funds or projects?

Yes. Many public finance obligations support multiple projects or funding sources. A debt schedule should track those allocations so debt service, reporting, and project-level analysis remain accurate.

How does a debt schedule support the ACFR?

A debt schedule supports the ACFR by organizing the long-term obligation data needed for disclosures, roll forward tables, principal and interest to maturity, debt outstanding by type, and other reporting views.

Because ACFR reporting relies on accurate, traceable data, the schedule should connect each reported number back to the underlying obligation and source document.

How can DebtBook help with debt schedules?

DebtBook helps public finance treasury teams centralize debt data, maintain schedules and allocations, track refunding lineage, automate debt accounting workflows, and generate year-end reporting outputs from a single source of truth.

That gives your team a clearer path from understanding the schedule to maintaining it without spreadsheet version-control risk.