Frequently asked questions
Is a bank statement sufficient, or do I still need to issue an api developer receipt?
A bank statement alone is not a substitute for a proper receipt. Bank entries typically show an amount, a date, and a reference, but do not describe what the payment was for, who received it, or what services were rendered. Tax authorities, auditors, and insurers expect formal receipts as primary evidence of a transaction. Bank statements are useful as corroborating evidence but should not replace the receipt in your records or the client's.
What payment methods should I record on an api developer receipt?
Record the payment method used: cash, bank transfer, debit card, credit card, cheque, or digital wallet. For card payments, note the last four digits of the card if available. For bank transfers, record the reference number. For cash, state the amount tendered and any change given. Recording the payment method provides a complete audit trail and helps both parties reconcile accounts quickly if there is ever a query about how or when payment was made.
Can an api developer receipt double as proof of warranty?
Receipts are commonly accepted as proof of purchase for warranty claims, particularly for goods supplied alongside api developer services. If your work comes with a workmanship guarantee or you supply equipment under warranty, make sure the receipt clearly describes what was supplied, the date, and the warranty period if applicable. Some manufacturers and insurers have specific requirements, so check these in advance and ensure your receipt template captures the necessary details.
How quickly should I issue an api developer receipt after payment?
For cash payments, issue the receipt immediately at the point of payment. For card transactions, you can issue the receipt at the same time or immediately after the terminal confirms the payment. For bank transfers, wait until the funds have cleared before issuing the receipt, as a pending transfer is not the same as confirmed payment. In most cases "cleared" means the funds appear in your account with no risk of reversal. Prompt receipting keeps records clean and reassures clients that their payment has been properly recorded.
What should I do if the api developer receipt contains an error?
Do not simply amend the original receipt, as this can look like an attempt to alter records. Instead, issue a credit note or cancellation notice for the incorrect receipt and then issue a new, corrected receipt with a new receipt number that references the original. Keep all three documents (original, cancellation, replacement) in your records so the audit trail is unbroken. Inform the client promptly and send them the corrected copy.
Can I use one receipt for partial payments on an api developer invoice?
Yes, but each payment should get its own receipt. When a client pays in instalments, issue a receipt for each payment received, noting the amount received, the payment date, the method, the original invoice reference, and the outstanding balance. This keeps records clear for both parties. When the final payment clears, issue a receipt marked as payment in full. Avoid issuing a single receipt that bundles multiple payment dates, as this creates ambiguity in the audit trail.
Can I use this receipt template for free?
Yes. Tidybill's free plan lets you create and send receipts at no cost, with no credit card required. You can use the API Developer receipt template straight away after signing up.