Getting Strack Van Til to Actually Work for Your Budget Cycle
Strack Van Til is an Excel-based budgeting and financial management application. It is built entirely on VBA and Microsoft Access backends, designed mainly for nonprofits, municipalities, and government entities that need encumbrance accounting and grant tracking alongside traditional general ledger reconciliation. The company behind it sells it as a ready-made solution so you do not have to build your own system from scratch. That sounds reasonable until you actually sit down to implement it. At its core, the software is a suite of prebuilt Excel workbooks and Access databases that handle budget entry, actuals import, variance reporting, journal entry processing, and fund/program tracking. You get a chart of accounts template, budget templates, and reporting sheets that are already configured with the formulas and macros they expect. The main selling point is that it eliminates the need to construct a budgeting workflow from zero. You download it, fill in your chart of accounts, import your actuals from whatever source you have, and run the standard reports. There is no separate server or cloud component unless you add one yourself. Everything runs locally on your machine. That matters more than it sounds, because it determines how your data gets managed, backed up, and shared across a team. If your organization does not already have a disciplined file-sharing and backup routine, you will inherit that problem immediately.
Installation and Setup Process
Installation is not complicated. You purchase a license, receive a download link from the vendor, and extract the workbook files to a network location or local drive. The setup involves a few specific steps that most people rush through, which causes issues later. Here is how it actually goes. First, you enable macros. Excel blocks VBA by default, so you need to adjust your Trust Center settings or open the file from a trusted location. Without doing this, the budgeting interface will not load properly and you will spend an hour wondering why buttons do nothing. Second, you configure your connection strings in the backend Access database if you are using the full version with data storage. If you stick to pure Excel mode, this step does not apply. Third, you map your chart of accounts to their template format. Their workbook uses a specific column structure for account numbers, descriptions, fund codes, and program codes. You cannot simply paste your existing GL export into their sheet without rearranging columns to match their expected layout. I spent two days on this the first time because I assumed the software would accept a standard CSV. It will not. The column headers and their exact order matter. There is no import wizard that automates this mapping. You have to do it manually or write a quick pivot to rearrange your data first.
After that, you populate the budget years you need. Their templates support multiple budget years in the same workbook, usually organized by tabs or sections depending on the version you received. Input your adopted budget numbers, then your revised numbers if your process includes multiple revision cycles during the fiscal year.
Get the Full Details
Running the Budget Cycle
Once your data is in place, the monthly process typically looks like this. You import actuals from your accounting system. Most organizations pull a trial balance or a transaction-level export from their ERP. The import speed depends entirely on your system, but a clean GL export usually lands in the workbook within ten to fifteen minutes for a mid-sized nonprofit. Strack Van Til has macro-driven import routines that look for specific file formats, so check that your export matches what the software expects before you try to load it. After the import runs, you execute the reconciliation macros. These compare your actuals against the budget and calculate variances. The output goes to variance sheets that are already formatted with the standard budget vs actual layout. You review those sheets, flag any unusual variances, and then generate the reports your board or finance committee needs. The whole cycle for a typical 501(c)(3) with a moderate budget structure takes me about forty-five minutes to an hour once the import file is ready. The first time you set it up, expect three to five hours because you are learning the quirks of their import format and adjusting column mappings. That initial investment is real and it is not negotiable.
A Specific Problem I Ran Into
Here is something the documentation does not emphasize enough. If your chart of accounts contains accounts that were deactivated or retired in previous fiscal years but still appear in your GL export, the reconciliation macros will sometimes throw errors or silently produce incorrect variance figures. I discovered this when our variance report showed a negative budget for an account that had been closed three years ago. The macro was matching the account number from the import to an old budget line and calculating differences against a zero or outdated budget figure. The workaround was to create a filtering step in your GL export before importing. You strip out inactive accounts at the source, or you add a column to the import file that flags active versus inactive accounts and then use a quick VLOOKUP or INDEX/MATCH against a master active account list inside the Strack Van Til workbook to exclude stale accounts before the reconciliation macro runs. It adds about three minutes to your monthly process but prevents garbage data from corrupting your reports.
Common Pitfalls That Slow You Down
One thing people consistently get wrong is treating the Strack Van Til workbook as a static file. You need to keep a master copy and make working copies for each budget cycle. If you edit the master directly and then save over it, you lose your historical comparison data and any prior year references that the macros depend on. I have seen two organizations lose an entire budget year's worth of data this way because someone thought it was fine to save changes directly into the template file. Another issue is the file size. Excel workbooks with heavy VBA and large data ranges will become sluggish once they exceed roughly fifty thousand rows of account activity. Your budget sheet itself may stay small, but the actuals import and transaction detail sheets can grow quickly depending on how granular your GL export is. When the file becomes slow, the macros take longer to execute and you start experiencing timeout errors. The fix is to keep your transaction-level detail on a separate sheet or in a separate workbook and only bring summarized monthly data into the main budget workbook. This cuts calculation time significantly and keeps the interface responsive. Permissions and shared access is the third major headache. Because the software runs locally on Excel, multiple users cannot easily work on the same workbook simultaneously without conflicts. You either need a shared network drive with strict checkout discipline, or you need to assign different users to different sheets or budget periods. I have found that designating one person as the sole budget editor and having department heads submit their budget requests through a separate intake form is the most reliable approach. It avoids the chaos of simultaneous edits breaking macro references.
When Strack Van Til Is the Right Call and When It Is Not
This software makes sense if your organization already uses Excel as its primary financial analysis tool and you need encumbrance accounting without buying a dedicated ERP module. It also works well if you are a smaller government entity that does not have the budget or staff to implement a full-fledged financial management platform. The upfront cost is lower than custom development, and the prebuilt templates save you months of configuration work. It is a poor fit if you need real-time collaborative budgeting across a large team, if your chart of accounts is highly complex with hundreds of segments and subsidiaries, or if you require audit trails at the transaction level that go beyond what Excel's version history can provide. In those scenarios, you are better off looking at dedicated budgeting platforms like Vena, Anaplan, or even a purpose-built module within your existing ERP. Those systems handle concurrency, approval workflows, and audit compliance without requiring you to manage file backups and macro security yourself.
What the Vendor Does Well
The strength of Strack Van Til is that it is specifically designed around the budgeting needs of tax-exempt and governmental organizations. The fund accounting concepts, grant restriction tracking, and encumbrance logic are baked into the templates rather than being add-ons you have to configure. This means you do not spend weeks figuring out how to track a restricted grant budget versus an unrestricted operating budget. The structure is already there. For an organization that understands fund accounting, the learning curve is mostly about data import formatting and macro management rather than learning new financial concepts. The reporting output is also straightforward. The variance reports follow standard nonprofit and government presentation formats. Your finance director or board will recognize the layouts without needing an explanation. That is not trivial. Most custom Excel budgeting solutions produce output that requires significant reformatting before it is presentation-ready. Strack Van Til skips that step.
Cost and Licensing Considerations
The pricing model is per-seat licensing with annual renewal. The exact cost depends on the scope of your deployment and whether you need the Access backend version or the pure Excel version. You should expect to pay a few hundred dollars per user per year, with volume discounts available for larger deployments. This is not cheap compared to a free Excel template, but it is far cheaper than a custom development project or an enterprise budgeting platform license that runs into the tens of thousands annually. The hidden cost is the maintenance burden. VBA code breaks when Excel updates change macro behavior. Microsoft periodically releases updates that alter how Excel handles macros, security prompts, and certain worksheet functions. I have encountered at least one major update cycle where three of the import macros stopped working because of a change in how Excel handled text parsing. The vendor typically releases patches, but there is a lag between the Excel update and the patched workbook. During that window, you are stuck either reverting to an older Excel version or manually fixing the broken macros. Budget time for this if your IT team is not familiar with VBA debugging.
Final Practical Notes
If you decide to move forward with Strack Van Til, do not attempt to implement it during a critical reporting period. Give yourself at least four to six weeks from initial setup to your first clean monthly close. The first month will always take longer than the documented timeline because you will encounter data formatting issues and macro quirks that only appear when real numbers flow through the system. Plan for that. The second month will feel normal. By the third month, you should be running the cycle in roughly the timeframe I mentioned earlier. Keep a current copy of your chart of accounts template, your active VBA code modules, and your macro security settings documented somewhere outside the workbook itself. When something breaks and you need to rebuild or reinstall, having those pieces documented saves you from starting from zero. I learned this the hard way after a ransomware incident wiped our shared drive and we had to reconstruct the entire setup from scratch over three days because nobody had written down how we had configured the import mappings. The software works. It is not elegant, it is not modern, and it will frustrate you occasionally. But for the organizations it targets, it does the job without requiring a seven-figure software purchase or a dedicated IT department to maintain it. That balance is why it has stayed relevant for decades despite being built on tools that most people consider legacy technology.
