How to map a daily close process

How to map a daily close process such as a hotel night audit: reconcile in stages and draw the discrepancy loops with an exit for each. Live example from the audit start to the new business date.

An end-of-day close looks like a checklist, but its core is a set of checks that can fail. Draw each check with a loop back to correct it and an exit when it cannot be corrected, and the close becomes something you can hand over.

The short version

  • Turn every comparison in the close into a decision with an agree branch and a differ branch.
  • Send each correction back to the comparison that found the difference.
  • Give every loop an exit, such as escalating an open variance to a named person.
  • Order the checks so the cheaper ones come before the costlier ones.
  • End on the step that makes the close official, such as rolling the date, and say what has to be true first.

Checks that can fail, and loops that must end

A daily close is usually written as a list: post the charges, count the cash, print the reports, roll the date. The list is accurate and hides the point. Between the items sit checks that compare one number with another, and each check has two outcomes. The numbers agree and the close moves on, or they differ and somebody has to find out why. The differences are where the night is spent, and a list gives them no place to live.

The way to chart it is to find every comparison and make it a decision. A hotel night audit has several: do the postings agree with the day's reports, do the cash and card totals match the ledger. For each, draw two branches. Agreement continues down the close. A difference leads to a correction step, and the correction returns to the comparison, because the only way to know a fix worked is to compare again. That return line is the discrepancy loop.

A loop needs an exit, or the chart promises that every difference gets fixed before morning. Sometimes a variance cannot be traced that night. Draw a branch for that case: the cause is found and fixed, or the open variance goes to a named person and the close carries on with it recorded. Without the second branch the chart claims more than the process delivers.

The example is a hotel night audit in QueryChart, built in five stages. The same shape fits a shop till close, a restaurant end of day, a month-end ledger and a warehouse stock count. Accounting rules and approval limits differ by business and country, so treat the chart as a structure to fit against your own procedure rather than a statement of what any business must do.

A night audit from the first charge to the new business date

A hotel night audit with a no-show check, a posting reconciliation loop, a cash and card reconciliation and an escalated variance.

  1. Collecting and posting the day

    The audit starts after the evening handover. The night auditor collects outlet checks and room charges and posts the outstanding outlet charges to guest folios. A decision asks whether expected arrivals have still not arrived, and those bookings are marked as no-shows under the booking terms before the audit moves on.

  2. The first reconciliation loop

    The postings on the folios are compared with the day's reports, and a decision asks whether they agree. A difference leads to a correction step with the reason noted, and the line returns to the comparison so the fix is checked. This is the first discrepancy loop. It ends only when the answer is yes.

  3. Room charges, deposits and the tills

    Once the postings agree, the room charges and applicable taxes are posted, deposits and package allocations are applied, the cash drawers are counted and the shift batches are closed. The card terminal batches are then closed and their totals printed. These steps produce the numbers for the second comparison and none of them branches.

  4. The cash and card variance

    A decision asks whether the cash and card totals match the ledger. If they do, the reports are printed. If not, the auditor traces the variance and writes down the cause, and a second decision asks whether it was found and fixed. Yes continues to the reports. No escalates the open variance to the Duty Manager, which gives the loop its exit.

  5. Sign off, roll the date and the lanes

    The reports are reviewed and the audit pack is signed, the system is backed up and the business date rolls, which opens the new date for the morning shift. With the logic fixed, the lanes show which steps belong to the auditor, the outlets, the Duty Manager and the system.

How it works

  1. List the close as plain steps

    Write the steps in the order they happen and add them in QueryChart as a single line. Include the counting and printing steps. Do not add branches yet.

  2. Find every comparison

    Mark each step where one number is checked against another, such as postings against reports or cash against the ledger. Each becomes a decision with an agree branch and a differ branch.

  3. Draw the correction loops

    For each differ branch add a step that traces or corrects the difference and draw a line back to the comparison. The return line is what shows that the fix is checked.

  4. Give each loop an exit

    Add a second decision after a trace step asking whether the cause was found and fixed. Send the no branch to an escalation, and record who receives it.

  5. Order the checks by cost

    Put the cheap checks before the costly ones, so that a posting error is caught before the cash is counted against it. Move boxes until the order reads naturally.

  6. Mark what makes the close official

    End on the step that closes the day, such as backing up and rolling the date, and note what must be true before it runs. Then assign lanes.

Mistakes to avoid

  • A checklist with no decisions

    A list hides the checks that can fail. Turn each comparison into a decision with two branches.

  • A correction with no return

    A fix step that continues down the close without comparing again proves nothing. Draw the line back.

  • A loop with no way out

    If a variance can never be left open, the chart is not describing the night. Show the escalation.

  • Hiding the order of the checks

    Doing the costly check first wastes time when a simple error is waiting upstream. Let the chart show the order on purpose.

Map your own daily close

Open the hotel night audit example as your own chart, change the comparisons and the escalation to match your procedure, and then assign the lanes.

Map your own daily close

Related guides

Frequently asked questions

What is a discrepancy loop on a flowchart?

It is a decision that compares two numbers, a correction step on the differ branch and a line from the correction back to the decision. It repeats until the numbers agree or an escape branch is taken.

Can this chart be used for other end-of-day closes?

Yes. A till close, a restaurant end of day and a month-end ledger all have comparisons that can fail. For the booking side of the same hotel read /templates/hotel-reservation-and-booking-process, and for the front desk path see /guides/how-to-map-a-guest-stay-journey.

How do I show an unresolved variance?

As a second decision after the trace step. If the cause was found and fixed the close continues. If not, a branch sends the open variance to a named person and the close carries on with it recorded.

Is the chart a statement of accounting rules?

No. Reconciliation steps, approval limits and record keeping differ by business and country. The chart shows the structure; put your own rules in the labels and comments.

The template behind this guide

Hotel night audit process flowchart — Hotel night audit process flowchart: reconcile postings, check no-shows, post room charges and tax, balance cash and card batches, handle variances, print reports and roll the business date.