Use this form each time cash is taken from a petty cash float for a small, everyday business expense. Complete one entry per payment, attach or reference the supporting receipt, and obtain the required internal approval before the entry is considered final. Fields marked as required must be completed for the record to be usable during review.
This template is provided for general record-keeping convenience only. It is not legal, tax, accounting or regulatory advice, and it is not approved or endorsed by any authority. Requirements for receipts, retention periods, tax treatment and internal controls vary by jurisdiction and by business. If you are unsure which rules apply to you, consult a qualified professional who is familiar with your circumstances.
I understand that this log is a general-purpose record-keeping aid and that I remain responsible for meeting any record-keeping obligations that apply to my business.
Business or trading name
Department, branch or cost centre holding the fund
Internal reference or fund code
Log or ledger period covered
Approved petty cash float (imprest) amount
Date the float was last established or formally reviewed
Is this a newly opened petty cash fund?
Briefly explain why the fund was opened and who authorised it:
Reference to the previous log or period:
Where is the cash physically stored?
Locked cash box or drawer on the premises
Safe or strongroom on the premises
Off-site secure storage
Other:
Petty cash custodian (person responsible for the float)
Custodian job title or role
Contact number or extension for the custodian
Person requesting or benefiting from the disbursement
Is the requester the same person as the custodian?
Where one person both requests and holds the cash, consider asking a second person to review or approve the entry so that duties are shared.
Relationship of the requester to the business:
Alternate or relief custodian (if any)
Date cash was disbursed
Time of disbursement (if recorded)
Sequential entry or voucher number
Paid to (payee or supplier name)
Who received the cash?
An external supplier or vendor
An employee being reimbursed
An owner or partner
A delivery agent or courier
A community group, charity or collection
Other recipient
Employee reference or staff number:
Please describe who received the cash and why:
Clear description of what the payment was for
Was this expense planned or budgeted in advance?
Budget line or planning reference:
Why was an unplanned payment necessary?
Was the expense connected with an urgent or unexpected situation?
Please summarise the situation and the action taken:
Primary expense category
Office supplies and stationery
Cleaning and hygiene supplies
Minor repairs and maintenance
Transport, parking and local travel
Refreshments and staff meals
Postage, courier and delivery charges
Small tools or equipment
Printing and photocopying
Staff welfare or recognition
Bank fees or cash handling charges
Other:
Any additional tags that apply to this payment?
Recurring monthly cost
One-off purchase
Customer-facing activity
Staff-related cost
Facility or premises related
Replaces a damaged item
None of these
Internal account, ledger or project code (if used)
Does the payment relate to a specific customer, order or job?
Customer, order or job reference:
Is this payment likely to be recharged or invoiced to someone else later?
Who will be recharged, and how will the amount be recovered?
Enter the figures exactly as they appear on the supporting receipt. If a tax, levy or service charge is shown separately, record it in its own column so the total can be checked later.
Net amount before any tax or charge
Tax, levy or service charge shown separately
Total cash paid out
Cash handed over from the float
Change returned to the float
Running cash balance remaining in the float after this entry
Was any part of this amount later refunded, returned or cancelled?
Please state the refunded amount, date and how it was returned to the float:
Currency of the transaction
Same as the fund's main currency
A different currency
Currency used and the exchange rate applied (if recorded):
Use the table below when a single payment covers more than one item. The line total column calculates automatically from the quantity and unit price, and the grand total is the sum of all line totals. Leave a row blank if it is not needed.
Itemised Disbursement Lines
Item or Service Description | Category | Quantity | Unit Price | Line Total | Receipt Attached? | ||
|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | ||
1 | Replacement door hinge, heavy duty | Minor repairs and maintenance | 2.00 | $6.50 | $13.00 | ||
2 | Cleaning solution, 750ml | Cleaning and hygiene supplies | 2.00 | $3.75 | $7.50 | ||
3 | Parking meter top-up, delivery visit | Transport, parking and local travel | 1.00 | $4.00 | $4.00 | ||
4 | $0.00 | ||||||
5 | $0.00 | ||||||
6 | $0.00 | ||||||
7 | $0.00 | ||||||
8 | $0.00 | ||||||
9 | $0.00 | ||||||
10 | $0.00 |
Grand total of all line items (cross-check against the total cash paid out)
Do the line items reconcile with the total cash paid out?
Thank you. The entry is ready for the supporting documentation checks below.
Please explain the difference and how it will be resolved:
Which supporting documents are attached or referenced?
Original printed receipt
Handwritten or manual receipt
Order confirmation or quote
Delivery note or packing slip
Digital receipt or email confirmation
Photograph of the item purchased
None available
No receipt is available. Please explain why and describe any alternative evidence you can provide:
Upload a scan or photo of the receipt or supporting document
Receipt or invoice number (if shown)
Date printed on the receipt
Is the receipt clearly legible and does it show the supplier name, date and amount?
Great. Keep the original document in a safe place according to your normal record-keeping routine.
What information is missing or unreadable, and what alternative proof can be obtained?
Was a duplicate or copy of the receipt given to the person who received the cash?
Consider providing a copy or a written acknowledgement so both parties hold a record of the payment.
How was the cash handed over?
Paid directly to the supplier at the point of purchase
Given to an employee as a reimbursement
Given to an employee as a cash advance before purchase
Sent with a delivery agent or messenger
Other method
Has the advance been fully accounted for with receipts?
Date the advance was cleared:
Outstanding amount still to be accounted for:
Please describe the method used:
Was a second person present when the cash was counted or handed over?
Name of the witnessing person:
Was the amount paid above any internal limit that normally requires extra approval?
Please state the limit, the amount paid and who gave the additional approval:
Any handling notes, unusual circumstances or follow-up actions needed
Internal approval steps vary between businesses. Complete the fields that match your own routine, and keep the signed record with the supporting documents.
Approval level applied to this entry
Within the custodian's normal authority
Reviewed by a supervisor or manager
Reviewed by the business owner
Escalated for additional review
Approver's full name
Approver's role or job title
Date the entry was approved
Was the approval given before the cash was handed over?
Please explain why prior approval was not obtained:
How confident are you that this disbursement was necessary and reasonable?
Not at all confident
Slightly confident
Moderately confident
Very confident
Completely confident
Approver signature
Custodian signature confirming the cash was paid out
Opening cash counted in the float at the start of this check
Total of all disbursements recorded since the last check
Expected cash remaining (opening cash less recorded disbursements)
Actual cash physically counted in the float
Difference between expected and actual cash
Result of the cash count
Balanced — no difference
Small difference within an acceptable internal tolerance
Shortage that needs investigation
Oversupply that needs investigation
Please describe the shortage, the steps taken so far and who has been informed:
Please describe the possible cause of the extra cash and how it will be treated:
Date of the cash count
Person who performed the cash count
Was the count performed together with a second person?
Name of the second person:
Having two people observe a cash count can make it easier to resolve questions later.
Does the float need to be replenished now?
Amount requested to bring the float back to its approved level:
No replenishment is needed at this time. Continue recording entries until the float reaches your internal review threshold.
Date replenishment was requested
Date the replenishment cash was received
Reference for the replenishment transfer or withdrawal
How is the replenishment normally funded?
Cash withdrawal from a bank account
Internal transfer from another cash holding
Owner contribution
Other:
Were all receipts and vouchers submitted together with the replenishment request?
Which documents are still outstanding, and when are they expected?
Use this short review to spot weaknesses in how the petty cash fund is being handled. There are no right or wrong answers — the aim is to prompt discussion and improvement.
Please rate the following statements about the current handling of this fund
Needs improvement | Somewhat true | Mostly true | Fully true | Not sure | |
|---|---|---|---|---|---|
Cash is stored securely when not in use | |||||
Every payment has a clear business purpose | |||||
Receipts are collected and kept with the log | |||||
Duties are shared so that one person does not control the whole process | |||||
Cash counts are carried out at regular intervals | |||||
Entries are reviewed and approved promptly |
Which areas would you like to strengthen? (choose any that apply)
Receipt collection and storage
Speed of approvals
Frequency of cash counts
Clarity of spending limits
Separation of duties
Record-keeping and filing
None at present
Overall, how would you rate the current state of this petty cash process on a scale of 1 to 5?
Have any unusual, repeated or suspicious entries been noticed recently?
Please describe what was noticed and what action has been taken so far:
Total number of disbursement entries recorded this period
Total value of all disbursements recorded this period
Largest single disbursement this period
Most frequent expense category this period
Summary comments for the period, including anything a reviewer should know
Are all entries for this period complete and supported?
The period is ready to be filed and reviewed.
Please list the outstanding items and the date each is expected to be resolved:
Prepared by (name)
Date prepared
Reviewed by (name)
Date reviewed
Final sign-off signature
I confirm that this record reflects the cash movements I have handled to the best of my knowledge.
Decide how long you will keep this log and its supporting documents based on your own business needs and any professional advice you have received. Record your chosen routine below so that it is easy to find later.
Where will the completed log and receipts be filed?
Physical folder kept on the premises
Secure digital folder or drive
Both physical and digital copies
With an accountant or bookkeeper
Other location
Please state where the records will be kept:
How long do you intend to retain these records?
Next scheduled review or audit date for this fund
Would you like a reminder before the next review date?
Who should receive the reminder and how?
Any final notes, questions or suggestions about this log
Analysis for Small Business Petty Cash Disbursement Log & Reimbursement Record
Important Note:
This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.
AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.
This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.
Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
This form is a comprehensive Small Business Petty Cash Disbursement Log & Reimbursement Record designed to help a small business capture, approve, reconcile and retain records of everyday cash outflows from a petty cash float. The form is organised into fourteen clearly labelled sections that follow the natural lifecycle of a petty cash transaction: fund identification, custodian and requester details, disbursement entry, expense classification, amount breakdown, itemised line items, supporting documentation, payment handling, approval, cash count and reconciliation, replenishment, internal control review, period-end summary, and retention planning. This end-to-end structure is a notable strength because it mirrors the practical workflow a small business owner or office administrator would follow, reducing the need to consult separate documents.
The introductory section sets clear expectations before the user begins data entry. The paragraph explaining that one entry should be completed per payment, with a receipt attached and approval obtained, gives users a practical workflow. The checkbox I understand that this log is a general-purpose record-keeping aid... serves as a lightweight acknowledgement that the user retains responsibility for their own record-keeping obligations. This is a sensible way to establish shared understanding without adding significant friction.
Business or trading name establishes the entity to which the fund belongs. It is a foundational identifier that ensures the record can be correctly filed and associated with the right business, especially where multiple entities or trading names are involved.
Department, branch or cost centre holding the fund adds a layer of organisational context. While optional, capturing this helps larger or multi-site businesses allocate petty cash activity to the correct unit.
Internal reference or fund code supports cross-referencing between this log and other internal records. A short code such as PC-001 makes it straightforward to search and retrieve entries later.
Log or ledger period covered defines the time window this record spans. This is essential for organising entries chronologically and for later review or reconciliation against bank statements or accounting records.
Approved petty cash float (imprest) amount records the authorised level of the fund. Knowing the approved float is necessary for calculating expected balances and identifying shortages or overages during reconciliation.
Date the float was last established or formally reviewed provides a reference point for how long the current fund arrangement has been in place, which can be useful during periodic reviews.
Is this a newly opened petty cash fund? uses conditional logic effectively. If yes, the form asks for a brief explanation and authorisation reference; if no, it requests a reference to the previous log period. This supports continuity between records without burdening users with unnecessary fields.
Where is the cash physically stored? captures basic security information. The follow-up for the 'Other arrangement' option allows flexibility while still documenting the chosen method. This information can be useful when discussing fund security or during an internal review.
Petty cash custodian (person responsible for the float) identifies the individual who holds and manages the cash. This is a key accountability field that makes it clear who is answerable for the fund.
Custodian job title or role adds useful context about the custodian's position within the business, which can help reviewers understand the level of authority involved.
Contact number or extension for the custodian facilitates follow-up if questions arise about an entry. Keeping this optional respects that not all businesses may wish to record contact details in the log.
Person requesting or benefiting from the disbursement identifies who initiated or benefits from the payment. Recording this supports transparency and helps distinguish between the person requesting cash and the person holding it.
Is the requester the same person as the custodian? is a thoughtful design element. When the answer is yes, the form provides a paragraph suggesting that a second person review or approve the entry. This gently promotes shared oversight without mandating a specific process.
Alternate or relief custodian (if any) captures backup arrangements, which is practical for continuity when the primary custodian is unavailable.
Date cash was disbursed records when the payment occurred. This is a core chronological marker for every entry and supports ordering, searching and period-based reporting.
Time of disbursement (if recorded) is an optional detail that can help resolve questions about the sequence of events on a busy day.
Sequential entry or voucher number provides a unique identifier for each disbursement. A sequential numbering system helps detect missing entries and supports cross-referencing with receipts and approvals.
Paid to (payee or supplier name) identifies the recipient of the cash. This is fundamental to understanding who received the funds and is useful for supplier tracking or reimbursement follow-up.
Who received the cash? uses a single-choice list with targeted follow-ups. For example, selecting 'An employee being reimbursed' triggers a request for a staff reference number, while 'Other recipient' prompts a description. This conditional approach collects relevant detail efficiently.
Clear description of what the payment was for is one of the most important fields in the form. A specific, plain-language description ensures that anyone reviewing the log later can understand the business purpose without needing to consult the requester.
Was this expense planned or budgeted in advance? helps distinguish routine spending from ad-hoc decisions. The follow-ups capture either a budget reference or an explanation of why the payment was unplanned, which can be useful for budget monitoring.
Was the expense connected with an urgent or unexpected situation? captures context for unusual or time-sensitive payments. The follow-up summary field allows the user to briefly explain the circumstances.
Primary expense category provides a structured way to classify each payment. The eleven-option list covers common petty cash categories and includes an 'Other category' option with a free-text follow-up. This supports consistent categorisation across entries and makes period-end analysis more straightforward.
Any additional tags that apply to this payment? is a multiple-choice field that adds descriptive metadata. Tags such as 'Recurring monthly cost' or 'One-off purchase' can help identify spending patterns without requiring separate analysis.
Internal account, ledger or project code (if used) supports integration with broader accounting or project tracking systems where applicable.
Does the payment relate to a specific customer, order or job? uses conditional logic to capture a reference only when relevant, which is appropriate for businesses that recharge or allocate costs to specific jobs.
Is this payment likely to be recharged or invoiced to someone else later? flags potential recovery of costs. The follow-up captures who will be recharged and how, which supports follow-up and reduces the risk of forgotten recoveries.
The introductory paragraph instructs users to enter figures exactly as they appear on the receipt and to record tax separately. This is a practical instruction that supports accuracy.
Net amount before any tax or charge and Tax, levy or service charge shown separately allow the user to break down the cost into its components. Separating tax can be helpful for businesses that track recoverable or non-recoverable charges.
Total cash paid out records the full amount disbursed. This is the headline figure for the entry and is used in reconciliation.
Cash handed over from the float and Change returned to the float capture the physical cash movement. These fields help explain situations where the exact amount was not handed over in a single transaction.
Running cash balance remaining in the float after this entry supports a running tally, which makes it easier to spot discrepancies before the next formal cash count.
Was any part of this amount later refunded, returned or cancelled? captures reversals. The follow-up asks for the refunded amount, date and method of return, which supports accurate balance tracking.
Currency of the transaction handles the possibility of a payment in a different currency. The follow-up captures the currency and exchange rate, which is relevant for businesses operating across currencies.
The Itemised Disbursement Lines table is a well-designed element for payments covering multiple items. The automatic Line Total calculation (Quantity × Unit Price) and the Grand Total row reduce arithmetic errors. The 'Receipt Attached?' checkbox per row encourages receipt tracking at the item level. The follow-up question Do the line items reconcile with the total cash paid out? provides a built-in cross-check, with a conditional explanation field if there is a discrepancy.
Which supporting documents are attached or referenced? is a multiple-choice field that covers common receipt types and includes a 'None available' option with an explanatory follow-up. This is a practical way to document the evidence trail and flag gaps.
Upload a scan or photo of the receipt or supporting document provides a direct digital attachment option, which supports remote review and reduces reliance on physical paperwork alone.
Receipt or invoice number (if shown) and Date printed on the receipt capture key reference details from the document, making it easier to match the receipt to the log entry.
Is the receipt clearly legible and does it show the supplier name, date and amount? is a quality-check question that prompts the user to verify the receipt before filing. The follow-up for 'No' asks what is missing and what alternative proof can be obtained, which is a constructive approach.
Was a duplicate or copy of the receipt given to the person who received the cash? encourages shared record-keeping. The 'No' follow-up provides a gentle suggestion to provide a copy or written acknowledgement.
How was the cash was handed over? captures the method of disbursement. The conditional follow-up for cash advances (option 3) asks whether the advance has been accounted for and captures either a clearance date or an outstanding amount. This is a useful control for tracking unreturned advances.
Was a second person present when the cash was counted or handed over? promotes dual oversight. The follow-up captures the witness name when applicable.
Was the amount paid above any internal limit that normally requires extra approval? flags payments that exceed internal thresholds. The follow-up captures the limit, amount and additional approver, which supports escalation tracking.
Any handling notes, unusual circumstances or follow-up actions needed is an open-ended field that provides space for context that does not fit elsewhere. This is a practical catch-all that prevents important details from being lost.
The introductory paragraph acknowledges that approval processes vary between businesses and invites users to complete the fields that match their routine. This is a flexible and realistic approach.
Approval level applied to this entry categorises the type of review, from within the custodian's normal authority to escalated review. This supports consistent tracking of approval pathways.
Approver's full name identifies who authorised the disbursement. This is a key accountability field.
Approver's role or job title adds context about the approver's authority level.
Date the entry was approved records when authorisation occurred, which supports timeline tracking.
Was the approval given before the cash was handed over? checks the sequence of authorisation. The 'No' follow-up asks for an explanation, which helps document exceptions.
How confident are you that this disbursement was necessary and reasonable? is a subjective rating field that encourages the approver to reflect on the payment. While this is a soft measure, it can prompt discussion and surface concerns.
Approver signature and Custodian signature confirming the cash was paid out provide formal confirmation from both parties, supporting accountability and creating a clear record of authorisation and execution.
Opening cash counted in the float at the start of this check and Actual cash physically counted in the float are the two anchor figures for reconciliation. Together with Total of all disbursements recorded since the last check and Expected cash remaining, these fields enable a clear comparison between expected and actual balances.
Difference between expected and actual cash highlights any variance. The Result of the cash count question categorises the outcome and uses conditional follow-ups for shortages and overages to capture investigation details.
Date of the cash count and Person who performed the cash count document when and by whom the count was conducted. The follow-up on whether a second person was present encourages dual observation.
Does the float need to be replenished now? uses conditional logic to either capture the replenishment amount or confirm that no action is needed. The follow-up fields for request date, receipt date and transfer reference support a clear replenishment trail.
How is the replenishment normally funded? captures the source of replenishment cash, with an 'Other arrangement' follow-up for flexibility.
Were all receipts and vouchers submitted together with the replenishment request? checks documentation completeness. The 'No' follow-up asks which documents are outstanding and when they are expected, which supports follow-up tracking.
The matrix rating field covering six statements about fund handling is a well-designed self-assessment tool. The statements address security, business purpose, receipt collection, separation of duties, frequency of counts and promptness of approvals. The follow-up multiple-choice question Which areas would you like to strengthen? encourages actionable reflection.
Overall, how would you rate the current state of this petty cash process on a scale of 1 to 5? provides a quick summary metric. Have any unusual, repeated or suspicious entries been noticed recently? is a constructive prompt for surfacing concerns, with a conditional follow-up for describing what was noticed.
The summary fields — Total number of disbursement entries, Total value of all disbursements, Largest single disbursement and Most frequent expense category — provide a concise snapshot of the period's activity. Summary comments for the period offers space for qualitative context.
Are all entries for this period complete and supported? serves as a final completeness check. The 'No' follow-up asks for a list of outstanding items and expected resolution dates, which supports accountability.
Prepared by (name) and Date prepared establish who compiled the record and when. Reviewed by (name) and Date reviewed capture independent review. The Final sign-off signature and confirmation checkbox complete the formal sign-off process.
Where will the completed log and receipts be filed? documents the storage location, with an 'Other location' follow-up for flexibility. How long do you intend to retain these records? prompts the user to decide on a retention period based on their own needs and any professional advice they have received.
Next scheduled review or audit date for this fund and the reminder option support proactive fund management. Any final notes, questions or suggestions about this log provides an open channel for feedback.
This form collects a rich set of data spanning fund identification, individual transactions, financial amounts, documentation evidence, approvals and reconciliation results. The data quality benefits are significant: structured category lists, conditional follow-ups, sequential numbering and automatic calculations all contribute to consistent, verifiable records. From a privacy perspective, the form collects personal names (custodian, requester, approver, witnesses), contact details and signatures. Form administrators should consider how these personal details will be stored, who will have access, and how long they will be retained, in line with their own data handling practices and any applicable guidance for their jurisdiction.
The form is extensive, with fourteen sections and a large number of fields. For a single petty cash disbursement entry, users may find the full form lengthy; however, many fields are optional and many use conditional logic to appear only when relevant. The clear section headings, helpful placeholder examples and instructional paragraphs reduce ambiguity. The main potential friction points are the overall length of the form and the number of fields that may need to be completed for each entry. Users who are completing the form frequently may benefit from saving partial entries or using the form as a periodic summary rather than per-transaction record, depending on their workflow.
This petty cash disbursement log is a well-structured and thorough record-keeping tool that covers the full lifecycle of a petty cash transaction, from fund setup through to period-end sign-off and retention planning. Its strengths include logical section ordering, extensive use of conditional logic, automatic calculations in the line-item table, built-in reconciliation and internal control review sections, and clear disclaimers about scope and limitations. The form promotes good operational habits such as receipt collection, dual oversight and sequential numbering without being overly prescriptive. Areas for improvement include managing the overall form length for frequent users — potentially by allowing users to complete only the transaction-specific sections for routine entries and the reconciliation sections periodically — and considering whether some optional fields could be collapsed or moved to an appendix to reduce perceived complexity. Overall, the form provides a solid foundation for small business petty cash record-keeping and internal review.
Mandatory Question Analysis for Small Business Petty Cash Disbursement Log & Reimbursement Record
Important Note:
This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.
Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.
Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
The following questions are currently set as mandatory in the form. For each, a concise explanation is provided of how requiring the field may support data completeness, operational processing or record-keeping in the context of this petty cash log.
Business or trading name
Recommendation: Requiring this field ensures that every record can be clearly associated with the correct business entity. For businesses with multiple trading names or entities, this identifier prevents confusion during filing and review. The necessity of this field depends on whether the log is used for a single entity or multiple entities; in a single-entity context, it could potentially be pre-filled to reduce repetition.
Log or ledger period covered
Recommendation: Requiring this field establishes the time window the record spans, which is important for organising entries chronologically and for later reconciliation or review. Without a defined period, it can be difficult to determine which entries belong to which reporting cycle. This supports consistent filing and retrieval.
Approved petty cash float (imprest) amount
Recommendation: Requiring this field records the authorised fund level, which is essential for calculating expected balances during reconciliation and for identifying shortages or overages. Without knowing the approved float, the reconciliation section cannot function effectively. The form creator should confirm that this figure reflects their current authorised fund level.
Petty cash custodian (person responsible for the float)
Recommendation: Requiring this field establishes clear accountability for the fund. Knowing who is responsible for holding and managing the cash is fundamental to any internal review or follow-up. This supports operational clarity and ensures that questions about the fund can be directed to the right person.
Person requesting or benefiting from the disbursement
Recommendation: Requiring this field captures who initiated or benefits from each payment, which supports transparency and helps distinguish between the requester and the custodian. This is particularly useful when one person both requests and holds the cash, as the form already prompts for additional oversight in such cases.
Date cash was disbursed
Recommendation: Requiring this field provides a core chronological marker for each entry. Accurate dating supports ordering, searching and period-based reporting. Without a disbursement date, it becomes difficult to place the entry in the correct reporting period or to reconcile it against receipts and bank records.
Sequential entry or voucher number
Recommendation: Requiring this field ensures each disbursement has a unique identifier. Sequential numbering helps detect missing entries and supports cross-referencing with receipts, approvals and reconciliation records. This is a practical measure that supports data integrity across the log.
Paid to (payee or supplier name)
Recommendation: Requiring this field identifies the recipient of the cash, which is fundamental to understanding each transaction. It supports supplier tracking, reimbursement follow-up and general record clarity. Without a payee name, the entry would be difficult to interpret or verify later.
Clear description of what the payment was for
Recommendation: Requiring this field ensures that each entry includes a plain-language explanation of the business purpose. This is one of the most important fields for anyone reviewing the log later, as it provides context that cannot be inferred from amounts or categories alone. A clear description reduces the need for follow-up questions and supports consistent record-keeping.
Primary expense category
Recommendation: Requiring this field supports consistent classification of payments across the log. Structured categorisation makes period-end analysis more straightforward and helps identify spending patterns. The eleven-option list with an 'Other category' follow-up provides both structure and flexibility.
Net amount before any tax or charge
Recommendation: Requiring this field captures the base cost of the payment before any tax or service charge. Separating the net amount supports accurate breakdowns and can be useful for businesses that track recoverable or non-recoverable charges. This contributes to the overall accuracy of the amount breakdown section.
Total cash paid out
Recommendation: Requiring this field records the full amount disbursed, which is the headline figure for each entry. It is used in reconciliation and cross-checked against the line-item grand total. Without this figure, the reconciliation section cannot function and the running balance cannot be maintained accurately.
Approver's full name
Recommendation: Requiring this field identifies who authorised the disbursement, which supports accountability and creates a clear record of the approval trail. This is important for internal review and for resolving questions about who approved a particular payment. The form creator should confirm that capturing the approver's full name aligns with their internal approval process.
Opening cash counted in the float at the start of this check
Recommendation: Requiring this field establishes the starting point for the cash count and reconciliation process. Without an opening balance, the expected remaining cash cannot be calculated and discrepancies cannot be identified. This is a foundational figure for the reconciliation section.
Actual cash physically counted in the float
Recommendation: Requiring this field records the physical cash on hand at the time of the count. Together with the opening balance and recorded disbursements, this figure enables the calculation of any difference between expected and actual cash. This is essential for identifying shortages or overages.
Amount requested to bring the float back to its approved level
Recommendation: This field is conditionally mandatory — it appears only when the user answers 'Yes' to the question about whether the float needs to be replenished. Requiring it in that context ensures that the replenishment amount is clearly recorded, which supports the replenishment trail and helps the approver or reviewer understand how much cash is being requested and why. The form creator should confirm that this conditional requirement aligns with their replenishment process.
Prepared by (name)
Recommendation: Requiring this field identifies who compiled the period-end record. This supports accountability and provides a point of contact if questions arise about the summary. It is a practical measure for record-keeping and review purposes.
Date prepared
Recommendation: Requiring this field records when the period-end summary was compiled. This supports timeline tracking and helps reviewers understand when the record was finalised. Together with the 'Prepared by' field, it creates a clear audit trail for the summary.
The form currently designates approximately 18 fields as mandatory (including one conditionally mandatory field within the replenishment section). These mandatory fields are distributed across key sections: fund identification, custodian and requester details, disbursement entry, expense classification, amount breakdown, approval, reconciliation, and period-end sign-off. This distribution is reasonable because it ensures that the most operationally critical data points are captured in each section while leaving many contextual and descriptive fields optional.
The form is extensive, with a large total number of fields. While the mandatory fields are well-chosen, users completing the form for every individual disbursement may find the overall length demanding. Consider whether the form is intended to be completed per transaction or as a periodic summary. If used per transaction, the mandatory fields are appropriately focused on the essential transaction details. If used periodically, the mandatory fields in the reconciliation and summary sections become particularly important.
The form already makes effective use of conditional logic. For the mandatory fields, most are unconditionally required and appear in the main flow. The one conditionally mandatory field — Amount requested to bring the float back to its approved level — appears only when replenishment is needed. This is an appropriate use of conditional logic to avoid requiring a field that is not always relevant.
The mandatory fields are placed at natural points within each section, generally near the beginning of the section where the most critical information is captured. This is a sensible approach because it ensures that users encounter the required fields early in each section. The period-end sign-off section appropriately requires 'Prepared by' and 'Date prepared' to ensure the summary is attributed and dated. Overall, the mandatory field strategy supports data completeness and operational processing without being excessively burdensome, though the overall form length is the primary factor affecting completion effort.
To configure an element, select it on the form.