0008: Total Revenue definition: governmental funds, the 38x Other Sources treatment
Context
METRIC-03 requires a “Total Revenue” definition, decided, documented, and reconciled against a
real Orange County source file — the revenue-side counterpart to ADR-0001’s Total Expenditures
work. docs/decisions/0001-total-expenditures-definition.md already resolved the governmental-
funds scope and the transfers-out exclusion set ({581, 586, 588}) against the Florida DFS Uniform
Accounting System Manual’s own text, and named its own mirror on the revenue side: “the paired
‘381-382/386 series.’” This record resolves that mirror directly, plus the wider question ADR-0001
did not have to answer on the expenditure side in the same way: Florida’s UAS chart of accounts
groups transfers-in, debt proceeds, lease/installment-purchase proceeds, and refunding-bond
proceeds together under one 3 8 x . x x x OTHER SOURCES heading (mirrored by 3 9 x . x x x PROPRIETARY NON-OPERATING SOURCES for extraordinary/special items) — a single numeric code range
that GAAP itself splits into two different concepts: Revenues and Other Financing Sources.
Whether TaxpayerScope’s headline “Total Revenue” follows ADR-0001’s own precedent (exclude only
interfund transfers) or the stricter GAAP split (exclude every Other Financing Source) is a
credibility-level methodology choice, like SRC-08 was for expenditures — it is not decided by this
record, only measured for the maintainer’s decision in Task 2.
Decision
Governmental-funds Total Revenue excludes account codes 381 (Inter-Fund Group Transfers In) and 382 (Contributions From Enterprise Operations) — Option A, the direct mirror of ADR-0001’s 581/586 criterion. Codes 383 (Leases/Installment Purchase Proceeds), 384 (Debt Proceeds) and 385 (Proceeds From Refunding Bonds) stay in the Total Revenue headline as real financing-sourced inflows, symmetric with ADR-0001’s own choice to keep the paired codes 583, 584 and 585 in Total Expenditures. Code 386 (Intragovernmental Transfers from Constitutional Fee Officers) is not separately named in the exclusion set below because it never appears in any of the 67 counties’ revenue files, by the manual’s own design (see Rationale, “Every 38x/39x code found in the corpus”); it carries zero dollar consequence either way, and the maintainer’s reply (below) names only 381 and 382.
excluded_account_codes: 381, 382
The headline Total Revenue metric (METRIC-03) is the governmental-funds reported total — General, Special Revenue, Debt Service, Capital Projects and Permanent — summed and reduced by account codes 381 and 382, the same five-column governmental-funds scope ADR-0001 uses for Total Expenditures.
Decision sign-off
Maintainer reply, recorded verbatim: “a”, meaning option-a: exclude only 381 (Inter-Fund Group Transfers In) and 382 (Contributions From Enterprise Operations), the mirror of ADR-0001, which keeps 583/584/585 in expenditures.
Recorded: 2026-09-24T15:35:59Z (Task 2 of 03-06-PLAN.md, checkpoint:decision,
gate="blocking-human"). This reply is the sole authority for the exclusion set above — T-03-26’s
mitigation: the revenue exclusion set is never chosen by the agent alone.
Rationale
Considered Options
- Option A (chosen) — exclude only 381 and 382 (interfund transfers), the mirror of ADR-0001’s 581/586 criterion. Symmetric with ADR-0001’s own choice to keep 583, 584 and 585 (financing-funded capital spending) in Total Expenditures: debt and lease/installment-purchase proceeds count as real inflows the same year the county borrows or leases, on a basis comparable to how the matching debt-service outflow (711-716) is counted every year in Total Expenditures, including years of new borrowing.
- Option B (rejected) — exclude every 38x Other Sources code (381-385), the GAAP Revenues vs. Other Financing Sources split. The GAAP-caption counter-argument, stated rather than dismissed: the Statement of Revenues, Expenditures and Changes in Fund Balances an auditor would produce separates “Revenues” from “Other Financing Sources (Uses)” as two distinct captions, and Option B matches that caption boundary exactly — a reader comparing TaxpayerScope’s figure to a county’s own CAFR/ACFR revenue line would see Option B agree with the audited number while Option A would not. This is not rejected as meritless; it is the position a GAAP-literate reader (an auditor, a CFO) would most likely hold. It was not chosen because it is asymmetric with ADR-0001, which already counts financing-funded capital outlay (583/584) as real expenditure rather than netting it against the financing that paid for it — choosing Option B here would keep that asymmetry on the expenditure side while removing the matching inflow on the revenue side, in the opposite direction from a correction. The dollar cost of not choosing Option B is small ($158,939,799.00 over FY2015-2024, 0.74% of Option A’s cumulative Total Revenue) but concentrated in the three years Orange actually borrowed or entered lease/installment-purchase agreements (FY2015, FY2016, FY2020), where Option B would show a revenue shortfall in the same year Total Expenditures (unchanged either way) rises for genuinely financed capital spending — a pattern that can read as a deficit when the gap is financing, not overspending.
Every 38x/39x code found in the corpus, quoted from the manual
data/audit/structural-audit.csv (revenues rows, all 67 governments) shows exactly seven codes
present in the 380-399 range across the whole corpus: 381, 382, 383, 384, 385, 392, 393. Codes
386, 388, 389 are named by the manual but never appear in any of the 67 counties’ revenue files —
386 because the manual itself says so (quoted below); 388 and 389 simply do not occur in this
corpus. Every quote below is verbatim from the Florida DFS Uniform Accounting System Manual,
2024-2025 Edition (Revised 11/2025), Rule 69I-51.0012, F.A.C., fetched live from
https://myfloridacfo.com/docs-sf/accounting-and-auditing-libraries/manuals/local-government/2024-2025-uas-manual.pdf
on 2026-09-24 (HTTP 200).
The manual’s own section header for the whole range: “3 8 x . x x x OTHER SOURCES — Amounts received by the entity, which are not additions to assets of the entity, although they may be to the receiving fund. These items include Intragovernmental transfers and reimbursements… These accounts are not intended for budget cash forward transfers.”
| Code | Manual’s name | Manual’s characterization (quoted) | Present in Orange’s 10 years? |
|---|---|---|---|
| 381 | Inter-Fund Group Transfers In | “Transfers between individual fund groups within a governmental reporting entity which are not repayable and are not considered charges for goods or services provided by other funds. This includes balances of discontinued funds but does not include general government contributions of capital to a proprietary fund or payments made by an enterprise to a general government fund in support of its operation.” The manual’s own figure labels this “381+382/581 Inter-Fund Group Transfers” — 381 and 382 together are the receiving-side mirror of ADR-0001’s excluded 581. | Yes, every year |
| 382 | Contributions From Enterprise Operations | “Contributions, whether based upon a fixed amount or some percentage of enterprise receipts, made by an enterprise of the government to its general operating funds. Use this account when the primary purpose of the transfer is to subsidize the general governmental operations of the unit.” Same 381+382/581 pairing as above. | Yes, every year |
| 383 | Leases — Financial Agreements (383.100) / Installment Purchases and Capital Lease Proceeds (383.200) | “Records the revenue side of the entry required to record leases in the period the lease is initiated” (GASB Statement 87, both sub-codes). This is the revenue-side entry for the same lease/installment-purchase transaction ADR-0001 kept in expenditures at 583/584 (“Installment Purchase Acquisitions”/“Lease Acquisitions” — “a contract used to finance the acquisition of assets,” “real capital-outlay spending via financing, not a transfer”). | Yes, 6 of 10 years |
| 384 | Debt Proceeds | “Records the sale of bonds or other loan proceeds where such proceeds are deposited into a governmental fund.” | Yes, FY2015 only |
| 385 | Proceeds From Refunding Bonds | No further descriptive text beyond the 383.xxx-385.xxx PROCEEDS heading; the manual groups it with 383/384 under “Proceeds.” Pairs conceptually with 585 (“Payment to Refunded Bond Escrow Agent”), which ADR-0001 kept in expenditures because it is “paid to an external third-party escrow agent, not moved between the entity’s own funds.” |
Yes, FY2016 and FY2020 only |
| 386 | Intragovernmental Transfers from Constitutional Fee Officers | “The 386.xxx series is for internal bookkeeping purposes only and should not be reported on the Annual Financial Report to DFS.” Pairs with expenditure code 586, which ADR-0001 already excludes. The manual’s own text explains exactly why 386 never appears in this corpus (or in any EDR-compiled file): it is not meant to reach the reported file at all. | No — never reported, by the manual’s own design |
| 392 | Extraordinary Items (Gain) | “The result from significant transactions or other events that are both unusual in nature and infrequent in occurrence.” Mirrors expenditure code 592 (“Extraordinary Items (Loss)”), which ADR-0001 kept in expenditures as “a one-time loss item… not described as an interfund transfer.” | Present in the wider 67-county corpus (5 governments); never in Orange’s own 10 years |
| 393 | Special Items (Gain) | “The results from significant transactions or other events within the control of the management that is either unusual in nature or infrequent in occurrence.” Mirrors expenditure code 593 (“Special Items (Loss)”), also kept in expenditures by ADR-0001. | Present in the wider 67-county corpus (6 governments); never in Orange’s own 10 years |
Codes 388 (Proceeds of General Capital Asset Dispositions) and 389 (Proprietary Non-Operating
Sources) are defined by the manual but were not found present in any of the 67 counties’ archived
revenue files (data/audit/structural-audit.csv), so neither option below needs to decide their
treatment; the rule file’s excluded_account_codes will simply never see them in this corpus.
Orange County’s Total Revenue under each option, FY2015-2024
Computed from data/work/parsed/fl-edr-orange-revenues.totals.parquet (the governmental-funds
reported_amount, summed across the five governmental-fund columns, per fiscal year — the same
“Total - All Account Codes” row ADR-0001’s table reads) and
fl-edr-orange-revenues.records.parquet (the leaf-row amount for each of codes 381-385, in the
governmental fund group only). Codes 392 and 393 are omitted from the table below because they
are $0.00 in Orange’s own governmental columns across all ten fiscal years (confirmed by a direct
query — zero rows returned). 386 is likewise $0.00 every year, per the manual’s own explanation
above.
| FY | Governmental reported total | 381 (transfer in) | 382 (enterprise contrib.) | 383 (lease/installment proceeds) | 384 (debt proceeds) | 385 (refunding-bond proceeds) | Option A excluded (381+382) | Option B excluded (381+382+383+384+385) | Option A Total Revenue | Option B Total Revenue | B vs. A difference |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2015 | $1,770,259,968.00 | $392,655,669.00 | $7,400,000.00 | $6,512,240.00 | $5,465,000.00 | $0.00 | $400,055,669.00 | $412,032,909.00 | $1,370,204,299.00 | $1,358,227,059.00 | $11,977,240.00 |
| 2016 | $1,986,775,229.00 | $463,505,156.00 | $7,400,000.00 | $12,271,169.00 | $0.00 | $30,110,000.00 | $470,905,156.00 | $513,286,325.00 | $1,515,870,073.00 | $1,473,488,904.00 | $42,381,169.00 |
| 2017 | $2,028,035,741.00 | $455,635,514.00 | $8,200,001.00 | $181,569.00 | $0.00 | $0.00 | $463,835,515.00 | $464,017,084.00 | $1,564,200,226.00 | $1,564,018,657.00 | $181,569.00 |
| 2018 | $2,172,236,008.00 | $468,525,968.00 | $9,100,000.00 | $157,799.00 | $0.00 | $0.00 | $477,625,968.00 | $477,783,767.00 | $1,694,610,040.00 | $1,694,452,241.00 | $157,799.00 |
| 2019 | $2,309,097,789.00 | $477,956,906.00 | $8,899,999.00 | $85,742.00 | $0.00 | $0.00 | $486,856,905.00 | $486,942,647.00 | $1,822,240,884.00 | $1,822,155,142.00 | $85,742.00 |
| 2020 | $2,543,724,202.00 | $460,167,530.00 | $8,899,999.00 | $141,648.00 | $0.00 | $103,805,000.00 | $469,067,529.00 | $573,014,177.00 | $2,074,656,673.00 | $1,970,710,025.00 | $103,946,648.00 |
| 2021 | $3,059,740,868.00 | $489,487,169.00 | $9,700,000.00 | $209,632.00 | $0.00 | $0.00 | $499,187,169.00 | $499,396,801.00 | $2,560,553,699.00 | $2,560,344,067.00 | $209,632.00 |
| 2022 | $3,390,411,350.00 | $636,099,735.00 | $9,900,000.00 | $0.00 | $0.00 | $0.00 | $645,999,735.00 | $645,999,735.00 | $2,744,411,615.00 | $2,744,411,615.00 | $0.00 |
| 2023 | $3,629,096,290.00 | $689,691,418.00 | $10,200,000.00 | $0.00 | $0.00 | $0.00 | $699,891,418.00 | $699,891,418.00 | $2,929,204,872.00 | $2,929,204,872.00 | $0.00 |
| 2024 | $3,811,208,026.00 | $602,197,318.00 | $10,800,000.00 | $0.00 | $0.00 | $0.00 | $612,997,318.00 | $612,997,318.00 | $3,198,210,708.00 | $3,198,210,708.00 | $0.00 |
| Sum, FY2015-2024 | $26,700,585,471.00 | $5,135,922,383.00 | $90,499,999.00 | $19,559,799.00 | $5,465,000.00 | $133,915,000.00 | $5,226,422,382.00 | $5,385,362,181.00 | $21,474,163,089.00 | $21,315,223,290.00 | $158,939,799.00 |
The ten-year difference between the two options is $158,939,799.00, 0.74% of Option A’s cumulative Total Revenue — a real but modest choice compared to ADR-0001’s own 2.83x naive-sum finding on the expenditure side. All of the difference is driven by three years where Orange issued debt or entered lease/installment-purchase agreements: FY2016 ($42.4M, mostly 385 refunding-bond proceeds), FY2020 ($103.9M, mostly 385 again), and FY2015 ($12.0M, split across 383 and 384). FY2022-2024 have zero difference — Orange reported no 383/384/385 activity in its own governmental columns in those years, so both options agree exactly.
The asymmetry each option carries against ADR-0001, quantified
ADR-0001 kept account codes 583 (Installment Purchase Acquisitions), 584 (Lease Acquisitions) and
585 (Payment to Refunded Bond Escrow Agent) in the Total Expenditures headline, reasoning that
financing-funded capital spending is real spending, not a transfer. Orange’s own expenditures
data never uses any of those three codes in any of its ten fiscal years — a direct query against
fl-edr-orange-expenditures.records.parquet for account codes 583/584/585 in the governmental
fund group returns zero rows for FY2015-2024. (24, 13, and 6 of the other 66 counties respectively
do report 583, 584, or 585 in their own expenditures files, per structural-audit.csv — so this
zero result is specific to Orange, not a corpus-wide absence.)
This matters for how the asymmetry actually shows up in Orange’s own published figures. Orange does pay routine debt service every year — account codes 711-716 (Debt Service fund type, always counted in the headline, never excluded under either ADR-0001 or either revenue option here) total between $27.2 million (FY2017) and $46.6 million (FY2024) annually. Under Option B, the years Orange took on new financing (FY2015, FY2016, FY2020) show the debt-proceeds inflow (384, 385) removed from Total Revenue while the corresponding debt-service outflow (711-716) stays fully counted in Total Expenditures every year, including years of new borrowing — the reader sees spending rise (correctly) without the matching one-time financing inflow that paid for it, which can read as revenue falling short of spending in a borrowing year, when the gap is financing, not a deficit. Under Option A, the 384/385 inflow stays in Total Revenue the same year the county borrows, keeping revenue and (eventual) debt-service spending on a comparable basis with how ADR-0001 already treats 583/584/585 spending: as real, not netted out.
Rejected framings
Option B, and the GAAP-caption counter-argument for it, is recorded in “Considered Options” above rather than repeated here — it was put to the maintainer as a real alternative, not dismissed in advance, and the maintainer’s reply (Decision sign-off, above) chose Option A.
Excluding 392/393 (Extraordinary/Special Items Gain) from either option’s exclusion set is not proposed here because ADR-0001’s own precedent explicitly kept the mirror-image codes 592/593 in expenditures as real, non-transfer amounts, and Orange itself reports $0.00 in 392/393 across all ten years — the choice has zero dollar consequence for Orange and is carried forward symmetrically with ADR-0001 rather than introduced as a new asymmetry.
Source Evidence
DFS Uniform Accounting System Manual
Fetched live from
https://myfloridacfo.com/docs-sf/accounting-and-auditing-libraries/manuals/local-government/2024-2025-uas-manual.pdf
on 2026-09-24 (HTTP 200, 182-page PDF, “Revised 11/2025,” Rule 69I-51.0012, F.A.C.) — the same
manual edition ADR-0001 quoted for the expenditures side. All quotations in the Rationale table
above are verbatim extractions from this document. It is reference documentation, not a pipeline
source, so it is not archived under data/raw/ or recorded in the source manifest (per this
plan’s mode_notes).
Orange County, all ten fiscal years FY2015-2024
Source: fl-edr-orange-revenues, archived at data/raw/fl-edr/orange/revenues/. Computed
directly from Plan 03-04’s parser output —
data/work/parsed/fl-edr-orange-revenues.totals.parquet (governmental-fund reported_amount per
fiscal year) and data/work/parsed/fl-edr-orange-revenues.records.parquet (leaf-row amount for
account codes 381-385, fund_group == 'governmental') — the same intermediate files Plan 03-04’s
oracle tests validate against data/audit/reconciliation-orange.csv. Every value in the evidence
table above is reproducible by re-running the query this record was built from; no value here was
hand-typed from a source other than these two Parquet files.
The 380-399 corpus-wide account-code census
data/audit/structural-audit.csv (670 revenue rows, all 67 governments, all ten fiscal years) —
the same audit dataset ADR-0001 used to find every 580-599 code across the expenditures corpus.
The seven codes 381, 382, 383, 384, 385, 392, 393 are the complete set present in the 380-399
range across every revenue file in the corpus; 386, 388, 389 are defined by the manual but never
appear.
Methodology Version
This decision takes effect in methodology_version: 2. It has no prior version to supersede —
this is the first record of the Total Revenue definition. status: active as of Task 3 of
03-06-PLAN.md, following the maintainer’s recorded Task 2 decision (Decision sign-off, above).
Revision (2026-09-24)
Same-day activation record, for the same visible-diff discipline every other active record in
this directory carries: Task 1 wrote this record as status: proposed with both options
quantified; Task 2 (checkpoint:decision, gate="blocking-human") obtained the maintainer’s
reply the same date; Task 3 rewrote the Decision section to Option A only, added the
machine-readable excluded_account_codes: line and the Decision sign-off section quoting the
reply verbatim, and flipped status to active — all recorded here as one dated, diffable
event rather than an untracked same-day edit. This revision recorded by Task 3, 03-06-PLAN.md.
Revision (2026-09-24)
This revision supersedes methodology_version: 2 with methodology_version: 3 (ADR-0009,
04-01-PLAN.md). The decision recorded above (Option A: exclude only 381 and 382) is carried
forward unchanged into methodology_version 3; the changes this version-3 coordinated bump makes
are recorded in 0009-category-and-revenue-classification.md, plus the two corrections below
(D-08).
Correction (a): account codes 711–716 are General Court-Related Operations, not debt service. This record’s own Rationale section above twice describes “the matching debt-service outflow (711-716)” and “the corresponding debt-service outflow (711-716).” Both sentences are factually wrong and stay unedited above, per this project’s append-only revision policy — the correction is recorded here instead. The DFS Uniform Accounting System Manual (2025 Edition) files 711–716 under 71x General Court Related Operations (711 Courthouse Security, 712 Courthouse Facilities, 713 Information Systems, 714 Public Law Library, 715 Legal Aid, 716 Clerk of Court Related Technology) — a sub-range of the manual’s own 600–799 Court-Related Expenditures heading, never Debt Service. Orange’s actual debt-service payments are account code 517, filed under 51x General Government Services:
| FY | 711–716 (General Court-Related Operations, not debt service) | 517 (Debt Service Payments, Orange’s actual debt service) |
|---|---|---|
| 2015 | $27,960,721.00 | $40,789,181.00 |
| 2016 | $28,490,082.00 | $72,037,885.00 |
| 2017 | $27,237,080.00 | $40,383,597.00 |
| 2018 | $28,580,976.00 | $35,265,647.00 |
| 2019 | $29,139,225.00 | $37,745,278.00 |
| 2020 | $29,242,274.00 | $134,342,341.00 |
| 2021 | $41,657,040.00 | $29,721,006.00 |
| 2022 | $42,938,781.00 | $29,716,001.00 |
| 2023 | $44,291,774.00 | $25,449,210.00 |
| 2024 | $46,597,527.00 | $23,309,250.00 |
This correction does not change the Option A exclusion set (381, 382) or any dollar total this
record publishes — 711–716 and 517 are both governmental-fund expenditure codes, outside the
scope of this revenue-side record, and are unaffected by which category label either is later
given in 0009-category-and-revenue-classification.md.
Correction (b): roots 386–389 do appear in the corpus. This record’s Rationale section
above states that codes “386, 388, 389 … never appear in any of the 67 counties’ revenue
files” and that root 386 is “never reported, by the manual’s own design.” A corpus-wide
structure-only scan of every archived revenue workbook (account_codes_in_workbook, Task 3 of
04-01-PLAN.md) found dotted codes under all four roots: 386.1, 386.3, 386.4, 386.6, 386.7,
386.8; 387.2; 388.1, 388.2; and 389.1 through 389.9. Orange’s own file reports non-zero,
negative amounts under root 386 starting FY2022 — 386.4 at $-1,190,112.00 (FY2022),
$-1,373,354.00 (FY2023), $-1,379,991.00 (FY2024); plus 386.7 at $-851,290.00 and 386.8 at
$-20,851.00 in FY2024 (root 386 total: $-2,252,132.00 in FY2024). Codes 387, 388 and 389 remain
$0.00 in Orange’s own governmental columns across all ten fiscal years. This does not reopen the
Option A decision above — the maintainer’s Decision sign-off named only 381 and 382 as
exclusions, and roots 386–389 stay in Total Revenue under Option A, unchanged. This revision
recorded by Task 3, 04-01-PLAN.md.
Revision (2026-09-25)
This revision supersedes methodology_version: 3 with methodology_version: 4 (ADR-0010,
05-01-PLAN.md). The decision recorded above (Option A: exclude only 381 and 382) is carried
forward unchanged into methodology_version 4; the changes this version-4 coordinated bump makes
are recorded in 0010-statewide-publication-rules.md. This revision recorded by Task 3,
05-01-PLAN.md.