Ten days to close, and most of it is waiting, then a bill dated last month arrives after the lock
None of the individual steps are slow. A statement gets exported, lines get matched against the ledger, someone asks whether the last two vendor bills have arrived, someone else reviews the accruals. The ledger holds every entry in that sequence and tracks none of the sequence itself, so the order lives in a checklist beside the system, and the close takes as long as the slowest unanswered item on the checklist rather than as long as the reconciliations. Then the period is locked and the month is finally final, until the bill dated the 28th turns up on the 3rd, and the quickest way to make it post is to change the date.
What changes with accounting close
Statement lines are matched against the ledger by rule, so a clean match reconciles itself and what is left in the queue is genuinely an exception.
The lock is enforced by the ledger rather than by a convention the team agrees to keep: a closed period refuses the entry instead of quietly accepting it.
A bill that belongs to a closed period stops there and names the period it belongs to, instead of having its date moved into the one that happens to be open.
That is our committed AP bill-posting workflow, and it carries a fiscal-period guard. It posts bills correctly across a period boundary. It does not run the close, and this page does not say it does.