Solutions

Finance & Grants

Fees, fines, per-capita, and requisitions tied to the record, with every entry attributed, so the counts your CTAS and BIA reports ask for are ready without extra work.

Finance on one record · the same sealed audit trail

When money moves through the same governed record as everything else, every dollar in and out is attributed to a person and a date, and the audit is already done.

Grant and federal reporting stops being a project the office dreads each year and becomes a button, because the record already did the work.

It is the same governed system as every other part of your government, added when you are ready.

How this gets built: the court is where the work runs deepest today. Finance & Grants runs on the same record model, the same sign-in, and the same audit trail, and it is built with your government from your own code and your own data, at your pace. What you get is not a template you conform to. It is your government's records, on a kernel that already runs.

The audit is the design, not the deadline

A tribe that expends a million dollars or more in federal awards in a fiscal year must have a Single Audit, or a program-specific audit in the limited case where every award falls under one federal program. That threshold rose from seven hundred fifty thousand dollars for fiscal years beginning on or after October 1, 2024, and it is measured across every federal program together, not grant by grant. A tribe drawing from several sources can cross it without any single award being large.

The findings that recur for tribal entities cluster in a predictable place: allowable costs, missing supporting documentation, subrecipient monitoring, and reporting. Most of that is documentation, and documentation is what an attributed, sealed record produces as a byproduct of doing the work correctly the first time.

ObligationThe ruleWhat the record gives you
Single AuditRequired at $1,000,000 or more in federal awards expended in a fiscal yearA schedule of federal expenditures built from attributed entries rather than assembled by hand
Reporting packageDue within the earlier of 30 days after receiving the auditor's report, or 9 months after the audit period endsThe support behind every number is the record that produced it
Grant reportingTypically financial reports quarterly and performance reports semi-annuallyCounts computed from the sealed record, ready rather than reconstructed
Record retention3 years from submission of the final financial report, longer if an audit or claim is openThe complete history, unaltered, still provable years later

The obligations that shape a tribal finance office's year. Read your own award terms, and note that 200.334 bars an agency from adding retention requirements beyond the ones it lists.

Finance, from each seat

Tribal IT

The numbers come out of your own system.

No data request to a vendor, no waiting on an outside company to produce your government's own figures, and no export project standing between you and a deadline.

Council

Clean books protect the next award.

Attributed, sealed entries are the strongest position a tribe can be in when a funder or an auditor asks how the money was used, and clean audits are what keep funding relationships open.

Staff

Every dollar is already attributed.

An entry names the person, the date, and the matter it belongs to as it is made. Nobody spends the winter reconstructing a year from folders and a spreadsheet.

Money moves only when a person says so

Seeing a payment, approving one, and carrying one out are three separate authorities here, granted deliberately and to different people. The system can prepare a payment and request it. It cannot send one. A person authorizes, and that authorization is itself a sealed record naming who gave it.

Separating those powers is what closes the oldest exposure in any finance office: one person holding cash authority, approval authority, and an unattributed ledger. Here the ledger attributes every entry as it is made, and no single account can close the loop alone.

  • Every entry is attributed to a person and a date as it is made, not reconciled to one later.
  • Approval is a separate authority from action, with a ceiling you set.
  • The system cannot move money on its own. It can request a payment; a person has to approve it.
  • Every approval is sealed, so who authorized what is provable rather than remembered.
  • The prior version is always kept, so an adjustment is visible and attributed rather than quiet.

Many awards at once, each on its own clock

A tribal finance office is rarely running one grant. It is running a portfolio, and the awards arrive from different places on different calendars: self-determination contracts and BIA programs, IHS, housing funds, justice funds, health and human services funds. Each award carries its own reporting cadence and its own period of performance, so the office is never working toward one deadline. It is working toward all of them at once.

The Justice Department's Coordinated Tribal Assistance Solicitation shows both halves of that. Since fiscal year 2010, DOJ has combined its tribal government-specific competitive funding opportunities into one solicitation and required only one application from each tribe or tribal consortium, administered across four components. One application, then several awards, each reporting on its own schedule for years after the money lands.

Which is why reporting belongs on the record as a by-product of the work rather than a reconstruction of it. When every entry names its award, its person, and its date at the moment it is made, the quarterly report is a read of the record instead of a winter spent rebuilding a year out of folders and a spreadsheet.

The clocks outlast the award, and they stagger. Federal award records are kept three years from the date that award's final financial report is submitted, so each award opens its own retention window on its own date. Property and equipment records run three years from final disposition instead. Program income earned after the period of performance runs three years from the end of the fiscal year in which it was earned. One history, kept whole and provable, carries all three without anyone tracking them by hand.

ReportCadenceWhat the record gives you
Financial reportsQuarterlyFigures read from attributed entries, each already naming its award, its person, and its date
Performance reportsSemi-annual, with performance-measure data submitted in the Justice Department's grants systemThe counts are already there, because doing the work is what produced them
Final financial and performance reportsAt the close of the award, which is also the event that starts the retention clockA close-out assembled from the record that ran the award, not from memory
Annual audit reportWhere the Uniform Guidance at 2 CFR Part 200 appliesThe support behind every number is the record that produced the number

The post-award reporting cadence for a CTAS award. Purpose areas, ceilings, and award counts are set fresh each cycle, so confirm the current solicitation rather than last year's.

Records technology is fundable. Purpose Area 3 of the FY25 solicitation funded developing or enhancing adult tribal justice systems, expressly including data collection and analysis and information technology for court operations, at an anticipated ceiling of $900,000. Purpose Area 5 listed data management systems for record keeping and case management as allowable equipment. Those are FY25 planning estimates, not guarantees, and purpose-area numbering, ceilings, and award counts change year to year (FY25 had no Purpose Area 7 or 10 at all). Check the open cycle before planning against any of these numbers.

The Single Audit is two opinions, and the second one is about your record

A Single Audit produces two opinions, not one. The first is whether the financial statements are fairly presented in accordance with generally accepted accounting principles. The second is whether the tribe complied with the requirements that could have a direct and material effect on each major program, measured against federal statutes, regulations, and the terms and conditions of the awards themselves. The second opinion is the one your record answers.

Not every program gets examined to the same depth. The higher-scrutiny Type A floor starts at one million dollars in federal awards expended, and for a tribe expending up to thirty-four million dollars, the Type A and Type B dividing line sits at that same one million. Above thirty-four million the threshold scales on the table in 2 CFR 200.518(b)(1), which a larger tribe should read directly rather than from anyone's summary.

The auditee has its own list, and it is longer than hiring an auditor.

  • Arrange the audit, and give the auditor access to personnel, books, and records.
  • Prepare the Schedule of Expenditures of Federal Awards, which is a read of where the money went across every program at once.
  • Prepare the summary schedule of prior audit findings, which asks what you said last year and what you did about it.
  • Prepare the corrective action plan for this year's findings.
  • Follow up promptly and take corrective action, which is the part the next auditor checks first.

Two more facts shape the arithmetic. The program-specific audit, the lighter option, is available only when the awards are expended under a single federal program, so a tribe drawing from several does not reach it. And a tribe under the threshold is exempt from the federal single-audit requirement, not from scrutiny: its records remain subject to review or audit by the awarding agency, the pass-through entity, and the Government Accountability Office. The record earns its keep at every level of federal funding, not just above the line.

Expended is not the same as cash out the door. Federal awards expended can include the value of federally funded loans and loan guarantees, donated property, and certain noncash assistance, so the count runs on 2 CFR 200.502 rather than on a checkbook. Some tribal funding also sits outside this framework: self-governance and self-determination compacts and certain awards follow specialized audit rules. Confirm which awards count toward the threshold for your tribe.

Fees, fines, and per-capita: money attached to a person and a date

Most of the money a tribal government handles belongs to somebody in particular. A court fee, a fine, a bond, a housing payment, a per-capita distribution: each one attaches to a person and a date, and nearly every report that will ever be asked about it is a count of those two facts. When the entry carries them from the moment it is made, the count the report asks for is already there.

Per-capita is where this turns strict. Under the Indian Gaming Regulatory Act, net gaming revenues may be distributed per capita only under a revenue allocation plan the Secretary of the Interior has approved as adequate, with the interests of minors and legally incompetent persons protected, and with payments subject to federal taxation and notice to members. Making per-capita payments without an approved plan puts the tribe in violation of IGRA, and the Justice Department or the National Indian Gaming Commission may enforce it.

Read what the plan itself has to contain and you are reading a specification for a record: a percentage breakdown of net-revenue uses totaling one hundred percent, protection of minors and legally incompetent persons, a description of how members are notified of tax liability and how taxes are withheld under IRS rules, specific per-capita eligibility requirements, and a tribal court system, forum, or administrative process for resolving disputes. Every one of those is a fact your record either carries or does not.

  • Eligibility from the same person record the enrollment office maintains, so the roll and the distribution list are one list rather than two that somebody reconciles.
  • Minors' and legally incompetent persons' interests held on the person, so the plan's protection is a live state of the record rather than a paragraph in a binder.
  • Notice and withholding captured as events, naming who was notified, on what date, and what was withheld.
  • Every fee and fine attributed to the person, the matter, and the date as it is taken, so the court's money and the court's docket are one record.
  • The percentage breakdown as a read of the ledger, current whenever the plan is reviewed rather than assembled the month it is due.
  • Disputes reaching your forum with the evidence attached, because the payment, the eligibility determination, and the roll are already linked.

Per-capita is a choice, not an obligation. A tribe is not required to distribute net gaming revenues per capita, and many do not. IGRA permits net revenues to fund tribal government operations and programs, the general welfare of the tribe and its members, tribal economic development, charitable donations, and the operations of local government agencies. The plan requirement attaches only if the tribe elects to distribute. And this is federal law and federal regulation: your own constitution, your own ordinances, and your own approved plan control in practice, and those are what we build in.

Questions treasurers ask

Do we have to publish our Single Audit?
You must submit the reporting package, and it still goes to the funders and pass-through entities entitled to it. A tribe may choose not to authorize the Federal Audit Clearinghouse to publish it on a public website. The obligation to report is not an obligation to publish, and that choice is yours.
How does this help with per-capita?
Eligibility comes from the same person record the enrollment office maintains, and every distribution is attributed to a person and a date. The roll and the payment stop being two lists that somebody reconciles by hand.
When can we turn finance on?
Finance runs on the same record model as everything else, and it is built with your government from your own procedures and reporting obligations. Every deployment is a build, so the order the departments come up in is yours to choose.

Sources

  1. 2 CFR 200.501, Audit requirements · Cornell Legal Information Institute. law.cornell.edu
  2. 2 CFR 200.512, Report submission · Cornell Legal Information Institute. law.cornell.edu
  3. 2 CFR 200.334, Record retention requirements · Cornell Legal Information Institute. law.cornell.edu
  4. 2 CFR 200.502, Basis for determining Federal awards expended · Cornell Legal Information Institute. law.cornell.edu
  5. 2 CFR 200.508, Auditee responsibilities · Cornell Legal Information Institute. law.cornell.edu
  6. 2 CFR 200.511, Audit findings follow-up, prior findings and the corrective action plan · Cornell Legal Information Institute. law.cornell.edu
  7. 2 CFR 200.515, Audit reporting, the two opinions a Single Audit produces · Cornell Legal Information Institute. law.cornell.edu
  8. 2 CFR 200.518, Major program determination and the Type A threshold · Cornell Legal Information Institute. law.cornell.edu
  9. 25 CFR 290.8, a tribe is not required to make per-capita payments · Cornell Legal Information Institute. law.cornell.edu
  10. 25 CFR 290.10, per-capita payments without an approved plan violate IGRA · Cornell Legal Information Institute. law.cornell.edu
  11. FY25 DOJ Coordinated Tribal Assistance Solicitation (O-BJA-2025-172288) · U.S. Department of Justice. cops.usdoj.gov
Every change records who made it, and when.
Event
Record edited
By
the clerk
When
2026-07-12 · 09:31
Chain
seq 042 to 043

Every change is signed and saved for good. If someone edits a record, it shows exactly who did it and when.

Get started

Find your tribe's first step.

A short conversation, a look at the working system, and a plan that fits your tribe's timeline and budget.

No cost, no commitment. You will speak with the person who builds it.