Count Anchored Paydays by Complete Calendar Month, Not by Four-Week Guess — Free
A fourteen-day cycle does not reset at the first of each month. Enumerate it from a known anchor, keep partial months separate, and verify every modeled deposit date against the employer’s calendar.
The proof surface
Leave balances are not deposit calendars: this enumerates anchored fixed-day pay cycles into complete versus partial calendar months.
Rare deviceLeave balances are not deposit calendars: this enumerates anchored fixed-day pay cycles into complete versus partial calendar months.
Output artifactComplete months with at least three modeled paydays plus complete labeled working
Cost$0 local core · no account, card, paid key or subscription · filing proposal has no checkout
Sample, not your facts: Invented records: Cedar payroll | 2026-01-02 | 2026-01-01 | 2026-12-31. Fixed pay cycle length (days) = 14; expected Complete months with at least three modeled paydays: 2 complete months with 3+ paydays. These are not quotations, verified observations or personal evidence.
Before using the paycycle calendar folio
This folio models a fixed number of civil days between paydays. It does not model twice-monthly dates, working-day shifts, arrears, earned pay, tax withholding or public holidays. An anchor is one date known to lie on the cycle; dates may be generated before or after it using whole cycle multiples. Choose a window no longer than 1,096 inclusive days, within years 1900–2100. The three-or-more-month headline is suitable for a biweekly illustration, but other cycle lengths may naturally create more dates. Multiple rows are separate payroll scenarios, not additive income streams or a guarantee of deposit availability.
Why the flat version breaks
Biweekly is treated as twice monthly
Twenty-six idealized 14-day pay cycles in a year are not twenty-four half-month periods. A calendar month may contain two or three cycle dates, but the total salary arrangement can still be unchanged. This model enumerates dates rather than declaring an extra paycheck bonus. Confirm the employment agreement if a cash-flow interpretation depends on the distinction.
Partial months are scored as full months
A window beginning halfway through a month can show only one date even when the full month has two or three. Mixing partial counts into the headline invents a contrast caused by selection. The folio labels each touched month complete or partial and limits its three-or-more tally to complete months. In-window dates remain available in either case.
A generated date is presented as a verified deposit
The fixed-cycle model has no holiday calendar, payroll cutoff, employer policy or banking data. It cannot confirm a deposit date. A shifted anchor can move every future modeled payday, so check that source carefully. Ask payroll about exceptions instead of manually moving individual model dates and then pretending the remaining series still follows one unchanged fixed cycle.
How to work the paycycle calendar folio
Start with an actual cycle convention
Confirm whether payroll is every fourteen days, every twenty-eight days, twice monthly or another arrangement. Only a fixed-day interval belongs in this model. Use a neutral plan code and an anchor date from the intended cycle. Do not use a pay-period end date as the deposit anchor unless the employer says those dates coincide. If a bank holiday shifts a real deposit, retain that exception outside the fixed-cycle list and ask payroll which schedule applies.
Select an inclusive civil-date window
Enter start and end dates as YYYY-MM-DD, checking the month and leap-day spelling. The start may be before the anchor; it simply asks for an earlier part of the same idealized cycle. The parser rejects reversed windows and spans beyond 1,096 days. The app also caps total generated dates across rows at 10,000. These limits keep the full date list readable and bounded rather than silently truncating a payroll plan.
Enumerate cycle multiples and classify months
Find the first anchor-plus-cycle-multiple date at or after the start, then advance by the entered whole-day cycle until the end is exceeded. Include exact endpoints. Group dates by calendar month. A month is complete only when its first and last days both lie in the window; count complete months with at least three dates. Do not multiply a weekly average by four and call that a calendar-month answer: actual months and weekday alignments differ.
Verify the calendar before planning cash use
Read every generated date, the month counts and the partial-month labels. Check them against the real employer schedule and bank availability rules before making bill-payment commitments. This folio has no salary field because deposit timing is not pay entitlement. A CSV or printed reading is a model record, not an employer notice. Copy the boundary with the dates, and use the unlimited article demo when you want to compare a different anchor or window.
What the paycycle calendar folio keeps distinct
Question
Before
Check this working
Biweekly is treated as twice monthly
Twenty-six idealized 14-day pay cycles in a year are not twenty-four half-month periods. A calendar month may contain two or three cycle dates, but the total salary arrangement can still be unchanged. This model enumerates dates rather than declaring an extra paycheck bonus. Confirm the employment agreement if a cash-flow interpretation depends on the distinction.
Select an inclusive civil-date window
Partial months are scored as full months
A window beginning halfway through a month can show only one date even when the full month has two or three. Mixing partial counts into the headline invents a contrast caused by selection. The folio labels each touched month complete or partial and limits its three-or-more tally to complete months. In-window dates remain available in either case.
Enumerate cycle multiples and classify months
A generated date is presented as a verified deposit
The fixed-cycle model has no holiday calendar, payroll cutoff, employer policy or banking data. It cannot confirm a deposit date. A shifted anchor can move every future modeled payday, so check that source carefully. Ask payroll about exceptions instead of manually moving individual model dates and then pretending the remaining series still follows one unchanged fixed cycle.
Verify the calendar before planning cash use
The paycycle calendar folio replaces this named manual reconciliation, not source verification or the responsible human's decision.
Run it on the samples, right here
FIRST-LOAD
HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.
Calendar illustration only, not employment, tax or financial advice and not a promised deposit schedule. Confirm actual pay dates, holiday shifts and pay-period conventions with the employer’s payroll team before scheduling payments.
Data note: This paycycle calendar folio calculates in the tab from Plan code | anchor payday YYYY-MM-DD | window start YYYY-MM-DD | window end YYYY-MM-DD. No input-collection endpoint, AI request or file upload is built into it. Drafts may be saved locally; explicit input-state links and optional external formatting can disclose the records. Use non-sensitive codes and clear the draft when finished.
Go deeper: the companion app files the same reading as a stapled evidence packet
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the paycycle calendar folio reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
Keep the complete paycycle calendar folio answer free; optional filing proposes its boundary-preserving print, row-and-summary CSV and five local reading summaries. The $4 one-time prototype is not for sale; another calculation remains free in the article demo.
Calendar illustration only, not employment, tax or financial advice and not a promised deposit schedule. Confirm actual pay dates, holiday shifts and pay-period conventions with the employer’s payroll team before scheduling payments.
What this is built on
Declared local method: Find the first anchor-plus-cycle-multiple date at or after the start, then advance by the entered whole-day cycle until the end is exceeded. Include exact endpoints. Group dates by calendar month. A month is complete only when its first and last days both lie in the window; count complete months with at least three dates. Do not multiply a weekly average by four and call that a calendar-month answer: actual months and weekday alignments differ.
Every sample code, measurement, date, price, fingerprint and scenario is invented. Artifact checks do not verify reader data, policies, actual files, tickets, votes or health/accessibility outcomes.
Google’s official Gemini pricing page, fetched 2026-10-01, lists AI Studio access in its Free section, limited model access and free input/output tokens. Free-tier content may be used to improve products. Optional external formatting may require an account; limits/access can change. Manual local entry needs none. Do not send sensitive records.
Before: a pay cycle was approximated as four-week months. After: anchored dates show actual calendar-month grouping and make truncated windows explicit.
Three worked readings, with different inputs
Sample A — typical inputs
Cedar payroll | 2026-01-02 | 2026-01-01 | 2026-12-31
An unshifted 14-day cycle anchored on 2 January has three modeled paydays in January (2, 16, 30) and July (3, 17, 31). All twelve months are complete within this window, so two complete months have at least three dates. The calendar does not say a third deposit is extra earned salary, predict employer holiday shifts or imply that the actual payroll will use these dates.
The dates inside this inclusive window are 16 February, 2/16/30 March and 13 April. March is the only complete month and contains three modeled dates. February and April are partial windows; their in-window counts remain visible but are excluded from the complete-month headline. This avoids calling a partial month a low-pay month simply because the selected window cut it short.
The two dates at the window’s endpoints, 1 and 15 May, both count because boundaries are inclusive. May is not complete, so no month enters the three-or-more headline. Zero complete months does not mean zero paydays. The folio prints the actual enumerated dates and the partial-month label so the two measures cannot be confused.
Optional AI formatting, never the calculation
Manual entry completes this paycycle calendar folio for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.
Format only these fictional or non-sensitive notes for a paycycle calendar folio. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Plan code | anchor payday YYYY-MM-DD | window start YYYY-MM-DD | window end YYYY-MM-DD; the setting is Fixed pay cycle length (days). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.
An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.