Over time
The full schedule is calculated once. First and last months are day-weighted. Residual cents land in the last period so the contract always ties.
Selected work · Professional services
A professional-services firm needed GAAP revenue on a contract book that QuickBooks was keeping on cash. We did not replace the GL. We built the overlay that turns the contract master into journal entries a close can trust.
The operational books were cash. The contracts were not. License terms, training content, translations, analytics, T&M consulting, and on-delivery work all sat in the same company — and they do not earn the same way.
A full ERP conversion would have been the loud answer. The useful answer was an Excel contract master that already knew every deal, a journal-data table that already knew every posting, and a monthly procedure that uploads into QuickBooks.
Every contract, regardless of method, uses the same three economic events. That is what makes the file hold.
Four methods, one table
The full schedule is calculated once. First and last months are day-weighted. Residual cents land in the last period so the contract always ties.
Open projects earn as a percent of estimated hours. Time from QuickBooks is appended each month and checked against the open-contract list.
Nothing earns until a delivery date is entered. The close updates deliveries; the file books that month and only that month.
This month’s invoices are this month’s revenue. No future schedule. No residual to babysit.
It is not a clever formula. It is a close that kept cash operations in place, told the truth about four different ways a contract earns, and was documented so the next month does not depend on the person who built the file. The bias here is the same: diagnose the constraint, then leave an artifact someone else can run.
Next