Interfund transfers out of balance
Money that leaves one fund has to arrive in another. When total transfers in do not equal total transfers out across the file, some fund is missing its half of the movement.
In equals out, file-wide
Interfund transfers in are recorded in objects 8910 through 8929; transfers out in 7610 through 7629. Summed across every fund in the file, the two totals must be equal, because they are two views of the same movements. A difference means at least one transfer was recorded once instead of twice.
Where the missing side hides
- Timing. The sending fund booked its transfer out in June; the receiving fund's transfer in waited for July and missed the file.
- One-fund thinking. A transfer approved and posted where the work happened, with nobody owning the other fund's entry.
- Object family mismatch. One side posted outside the paired ranges, so the totals see only half the movement.
- A fund missing from the export. Both entries exist; one lives in a dataset that was not extracted.
Name the fund, book its side
The direction of the difference tells you which side is short. Transfers in exceeding transfers out means some sending fund never booked its 7600-series entry; the reverse means a receiving fund is missing its 8910-series line. From there it is detective work with a short suspect list: match the transfers you can pair, and whatever refuses to pair is the culprit.
As with contributions, the amount and the entry shape are computable; the fund is a judgment slot. Anything that fills it for you automatically is guessing.
Check your own file in the time it took to read this. Drop a SACS Other Export (.dat) into SACS Pre-Flight and see every finding, with line numbers, before the Official Export runs. Findings are free and your file never leaves your browser.
Run SACS Pre-Flight free