Describe your register or petty cash close. Makeform creates a structured form for denomination counts, expected cash, variances, and manager review.
Send completed counts to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a starting point, adjust it, and send the prompt to the Makeform builder.
Audience
Cashiers and shift managers closing individual tills
Format
End-of-shift count with variance routing
Prompt size
305 chars
Example form structure
End-of-shift count with variance routing
Store, register, date, and closer
Expected cash and recorded movements
Notes and coins by denomination
Variance explanation when needed
Manager review status
Suggested routing tags
Balanced
Over or short
Manager review
Keep counted cash separate from expected cash so reviewers can inspect both source amounts.
Step 1
Identify
register, fund, date, and responsible closer
Step 2
Count
notes and coins recorded by denomination
Step 3
Compare
counted total measured against expected cash
Step 4
Review
variance explained and routed to a manager
A cleaner close
Preserve the expected amount, physical count, recorded movements, variance, and reviewer in one submission.
Give each note and coin a quantity field for a consistent, traceable count.
Keep expected and counted values separate, calculate the difference, and request context for variances.
File balanced submissions and route exceptions to the responsible manager.
Common count points
Use the same count, compare, explain, and review logic while changing the source values and movements for each workplace.
Match the physical till to the point-of-sale cash expectation after drops, refunds, and paid-outs.
Separate cash sales from tips paid out, refunds, service-period drops, and the opening bank.
Combine cash on hand with documented receipts and advances, then compare the result with the authorized fund.
Collect one close per register and create a location-level record for finance or operations review.
Build the workflow
Start with your existing count rules and source reports, then shape the generated form around the people who count and review cash.
Name the register or fund, the source of expected cash, allowed cash movements, denomination list, variance rule, and required reviewer.
Match currency denominations, label source amounts clearly, and set the formulas for counted total, expected ending balance, and variance.
Show explanation, attachment, and follow-up fields when the variance exceeds your internal threshold; keep routine balanced closes short.
Notify the shift manager or finance inbox, send selected values to a tracking sheet, and retain the submission as a dated review record.
Choose the record
Choose the approach that captures consistent inputs, explains exceptions, and reaches a reviewer.
Field guide
Use six sections to preserve the count, comparison, and review without unrelated credential data.
Count identity
Identify one close clearly. Use controlled store and register lists, with a separate business date.
Physical count
Quantity fields make counts repeatable and easier to inspect. Configure only the denominations you use.
Expected balance
Capture the starting float and recorded activity behind the expected ending balance.
Variance
Label one calculation convention clearly. Request facts about differences without assuming cause or responsibility.
Review
Separate preparation from oversight so a reviewer can confirm the record and select an outcome.
Data boundaries
Collect amounts, references, and relevant context—not payment credentials or secrets.
Related tools
Build supporting forms for petty cash activity, expenses, inventory differences, daily reporting, incidents, and internal review.
Document requests and movements that change a petty cash fund between counts.
Open toolCollect categorized expense details and supporting documents for a separate review workflow.
Open toolRecord internal observations, evidence references, owners, and follow-up actions.
Open toolRoute stock-count differences with item, quantity, reason, and reviewer fields.
Open toolCombine operational totals and shift notes in a consistent end-of-day report.
Open toolCapture a factual internal incident record when an exception needs separate follow-up.
Open toolFAQ
Practical answers for retail, restaurant, office, and finance teams organizing daily cash counts.
It records physical cash, expected cash, the difference, and the review outcome. Closers follow one sequence and managers receive a dated exception record.
Include location, register, date, shift, counter, opening float, expected cash, drops, paid-outs, denomination quantities, counted total, variance, explanation, and manager review. Match movement fields to your source report.
One convention is counted minus expected: positive is over and negative is short. Label the convention, preserve both amounts, and test positive, negative, and zero examples.
Yes. Compare cash plus documented receipts or advances with the authorized fund amount. Use replenishment and disbursement fields while retaining denomination, variance, and reviewer sections.
Use conditional logic to distinguish balanced closes from variances. Route notifications using your threshold and retain a review status for every exception.
No. Use a deposit amount and internal reference, but never request passwords, secrets, PINs, or full card data. Keep attachments relevant to the count.
Yes. Makeform provides unlimited free forms and responses. Generate, edit, publish, and use the form without a response cap; the paid tier removes the badge.
Pilot one register, compare totals with a manual count, confirm the variance convention, and test with a closer and reviewer. Then adjust labels, routing, access, and retention.
Make every count easier to review.
