Financial model review
Date and timeline checks for financial models
Check dates and monthly timelines in Excel financial models. Find text dates, skipped periods and shifted cash flows with worked examples and review steps.

A financial model can add every amount correctly and still put cash in the wrong month. Review dates by defining the forecast periods, checking the underlying date values and tracing one transaction from its source date into the intended column. An annual total alone cannot reveal every timing mistake.
Work in a separate review copy and keep the original unchanged. The invented examples below use calendar months and simple cash movements. They demonstrate spreadsheet checks, not payment terms or accounting policies for a particular business.
Define what each date means
A month heading, an invoice date and an expected payment date describe different events. Write down which date drives each schedule. A sales forecast might follow delivery dates, while its collection schedule follows expected receipts. Linking both to the invoice month without an explanation can shift cash even when revenue is reasonable.
State whether columns represent calendar months, four-week periods or another reporting calendar. Identify the first forecast period and the last actual period. If January is already included in the actual results, including it again in the forecast can duplicate activity. The units, signs and periods guide explains the broader alignment checks.
Build a calendar timeline instead of adding fixed days
Suppose B2 is intended to represent January 2028 month-end. Enter:
=DATE(2028,1,31)
Adding 30 to B2 produces 1 March 2028, not February month-end: 2028 is a leap year. A fixed-day interval and a calendar month are different rules. Use the rule that the schedule actually requires.
For this month-end timeline, put =EOMONTH(B2,1) in C2 and =EOMONTH(C2,1) in D2. The results are 29 February 2028 and 31 March 2028. Microsoft's EOMONTH reference explains that the function returns the final day of the specified month. Display the results as dates.
Check the formula across a year boundary too: December should lead into January of the following year. A formula that merely changes a visible month label can leave its underlying date or linked input unchanged. These examples use English function names and comma separators; local Excel installations may display different names or separators.
Check the stored value, not just its appearance
A cell containing date-like text can look like a usable Excel date. Imported values need particular attention. In a spare review cell, =ISNUMBER(B2) checks whether B2 contains a number. Microsoft documents that ISNUMBER does not convert text into a number.
A TRUE result is only a first signal: any ordinary number can pass. It does not prove that the value represents the correct date, year or forecast period. Inspect the source, formula and displayed full date together. A FALSE result needs investigation before the value is used in a date comparison.
For dates entered from separate known components, =DATE(2028,3,2) explicitly represents 2 March 2028. Microsoft recommends four-digit years in its DATE documentation. Also validate the components: DATE can carry an out-of-range month or day into another period instead of rejecting it.
Avoid interpreting an imported 02/03/2028 without confirming the source convention. It can be read as 2 March or 3 February. Microsoft's DATEVALUE guidance notes that system date settings can affect conversion. Preserve the original text and verify a few known records before applying a consistent conversion in a preparation column.
Look for repeated, missing and reversed periods
For the stated month-end convention, use a separate review row beneath the headings. With B2 and C2 as consecutive period ends, this test asks whether C2 is the expected next month-end:
=C2=EOMONTH(B2,1)
Copy the test across the actual timeline. A failed comparison identifies a heading to inspect; it does not repair the model. Check the anchor date as well, since a consistently shifted series can pass every subsequent comparison.
A simple =C2>B2 can catch repeated or reversed dates, but it cannot prove that no month was skipped. Twelve columns are not necessarily twelve distinct consecutive months. Show the year alongside the month during review, especially when the model crosses December or compares several years.
Compare the headings on the sales, payroll, debt and cash schedules. A linked formula can refer to the correct-looking column position on a sheet whose dates start one month later. Follow the dates and business event, rather than accepting alignment by column letter. Use the forecast formula checklist when copied references also need investigation.
Trace a receipt that moves the cash shortfall
Consider a forecast with EUR 5,000 opening cash in February, an expected EUR 12,000 customer receipt on 29 February 2028 and EUR 10,000 February payments. March has EUR 4,000 payments and no other receipts. Ignore financing and all other movements in this exercise.
The intended cash bridge is:
February closing cash = 5,000 + 12,000 - 10,000 = EUR 7,000
March closing cash = 7,000 + 0 - 4,000 = EUR 3,000
Now suppose the receipt is assigned to 1 March because a date formula incorrectly adds 30 days to January month-end. The model instead shows:
February closing cash = 5,000 + 0 - 10,000 = EUR -5,000
March closing cash = -5,000 + 12,000 - 4,000 = EUR 3,000
March ends at the same EUR 3,000, and the two-month receipt total is still EUR 12,000. February nevertheless shows a false EUR 5,000 shortfall instead of EUR 7,000 cash. An annual or ending-balance check can miss that difference.
Confirm the expected receipt date against its approved source; do not move a payment merely to eliminate a shortfall. Check month-end, first-day-of-month and year-end cases in the review copy. The cash-flow review guide shows how to reconcile the full movement bridge.
Finish with a short timeline review
- Define each schedule's date basis and period boundaries.
- Verify the first forecast date against the last actual period.
- Inspect imported date values and ambiguous source formats.
- Test consecutive headings, leap February and the year boundary.
- Trace one receipt and one payment into their intended periods.
- Review the lowest monthly cash balance as well as the final total.
FinModelCheck inspects supported saved-file evidence; it does not recalculate Excel, audit date grids or determine the correct financial timing. A provisional score does not establish that receipts, payments or forecast periods are properly aligned.
Use the financial model checker alongside this manual review and see the example report. Online customer results show only the score and counts by Finding type. The complete PDF is free without registration in the current valid owning browser session. The revenue forecast guide also helps distinguish sales activity from collection timing.
Frequently asked questions
Does changing the date format fix imported text?
Formatting alone does not establish a correct stored date. Confirm the source convention and validate the converted value, including its year, before using it in forecast comparisons.
Should every monthly schedule use EOMONTH?
No. It fits the calendar month-end convention in this example. Four-week calendars, specific settlement dates and other schedules need their own defined rules.
Why can cash timing be wrong when the final balance agrees?
A receipt can move between periods without changing the total received. Reconcile individual months and inspect the lowest cash position, not only the final balance.


