Petty cash

Petty cash is a small amount of discretionary funds in the form of cash used for expenditures where it is not sensible to make any disbursement by cheque, because of the inconvenience and costs of writing, signing, and then cashing the cheque.[1]

The most common way of accounting for petty cash expenditures is to use the imprest system.[2] The initial fund would be created by issuing a cheque for the desired amount. An amount of $100 would typically be sufficient for most small business needs as the expenses to be covered are for small amounts. The bookkeeping entry for this initial fund would be to debit Petty Cash and credit bank account. This cheque would then be cashed to acquire the actual cash needed for payments.

As expenditures are made, the custodian of the fund (a bookkeeper or a member of the administration staff) will reimburse employees and receive a petty cash voucher with a receipt/invoice attached in return. At any given time, the total of cash on hand plus reimbursed vouchers must equal the original fund.

When the fund gets low, e.g. $20 remaining, the custodian requests a top up and submits the vouchers for reimbursement. Assuming the vouchers add up to $80, an $80 top up cheque is issued and an $80 debit towards office expenses is recorded. Once the cheque is cashed, the custodian again has cash at the original amount of $100.

Audit controls

Oversight of petty cash is important because of the potential for abuse. Examples of petty cash controls include a limit (such as 10% of the total fund) on disbursements and monthly audits by someone other than the custodian.[3] Use of petty cash is sufficiently widespread that vouchers for use in reimbursement are available at any office supply store.

The petty cash daybook is one of the daybooks used in bookkeeping and the double-entry bookkeeping system.[4]

gollark: Broadly speaking, you have a parser which turns the text into abstract syntax trees representing the code (`1 + 1` goes to `Operator("+", 1, 1)` or something, for example), then you generate structures for all the various functions and whatever and check things for validity, then turn those into output code.

gollark: Compilers are generally quite complex. I forgot what the best resources for them were.

gollark: Or database or something, yes.

gollark: Oh. No clue.

gollark: Search in what, exactly?

References

P. Hosein (29 July 1988). Principles of Accounts (Cxc). Heinemann. p. 92. ISBN 978-0-435-98309-3.
Alan Trenerry (1999). Principles of Internal Control. UNSW Press. pp. 125–. ISBN 978-0-86840-401-1.
Peggy M. Jackson (28 November 2006). Sarbanes-Oxley for Small Businesses: Leveraging Compliance for Maximum Advantage. John Wiley & Sons. pp. 101–. ISBN 978-0-470-05004-0.
Diane Canwell; Jon Sutherland (2005). BTEC First Business. Nelson Thornes. pp. 105–. ISBN 978-0-7487-9431-7.

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.

[Hosein1988-1] P. Hosein (29 July 1988). Principles of Accounts (Cxc). Heinemann. p. 92. ISBN 978-0-435-98309-3.

[Trenerry1999-2] Alan Trenerry (1999). Principles of Internal Control. UNSW Press. pp. 125–. ISBN 978-0-86840-401-1.

[Jackson2006-3] Peggy M. Jackson (28 November 2006). Sarbanes-Oxley for Small Businesses: Leveraging Compliance for Maximum Advantage. John Wiley & Sons. pp. 101–. ISBN 978-0-470-05004-0.

[CanwellSutherland2005-4] Diane Canwell; Jon Sutherland (2005). BTEC First Business. Nelson Thornes. pp. 105–. ISBN 978-0-7487-9431-7.