Occasionally you may get a payment from a customer that is for more than they owe.\u00a0 There are a couple of different ways you can handle it.<\/p>\n
First let’s take the case of a customer overpaying by a negligible amount, such as 1 cent.\u00a0 You have to account for it in order for you bank account to reconcile.\u00a0 But it’s not worth the time and effort for you or the customer to record a credit.\u00a0 So in this case, when you are recording the customer’s payment, check the Pay <\/em>box by the invoice to pay it for the actual invoice amount, then click on the Apply To Revenues<\/em> tab and record the overpayment amount.\u00a0 You can put a note in the description field. Set the GL Account to something like Other Income.\u00a0 If there is not a column for GL Account, click the Journal<\/em> button at the top of the window and change the account there.\u00a0 Finally, if the amount is large enough to trigger sales tax, you will need to change the Tax type to exempt, assuming your state allows that.<\/p>\n If the overpayment is for a significant amount and they don’t have any other open invoices, you will need to keep track of the credit balance.\u00a0 In most cases, my recommended method for doing that is to manually enter the Amount Paid<\/em> for the invoice so that it includes the overpayment.\u00a0 The Amount Paid<\/em> for the invoice will be larger than the Amount Due<\/em>. This will cause the invoice to have a negative balance and show up on their account like a credit memo would.\u00a0 Later you can apply the credit to another invoice or refund it to the customer.<\/p>\n If the total amount of overpayment credits is a significant part of your total accounts receivable, and you have to provide financial reports to someone outside your company, such as your bank, you may need to use a different method.\u00a0 The reason is you owe that money to your customer which means it is a liability.\u00a0 But the above method makes it a negative asset (accounts receivable) instead of a liability.\u00a0 So instead of overpaying an invoice, you will pay the invoice for the actual amount due, then click on the Apply To Revenues<\/em> tab, enter a description, set the GL account to a liability account such as Customer Down Payments<\/em>, and put the overpayment in the Amount<\/em> field.\u00a0 Unless your state requires you to tax down payments, set the tax type to exempt.\u00a0 Using this method, the overpayment will show in the liability account, but it will not show in the customer’s balance. So you will have to carefully keep track of what is in the liability account.\u00a0 Your general ledger will more accurately show your financial position using this method, but from a practical point of view, it is much harder to keep track of your customer’s actual balance.\u00a0 That is why I recommend this method only when you are required to use it.<\/p>\n Sage 50 2014 has just released and it has a new feature allowing you to enter the total receipt amount and it will auto-apply it to the open invoices.\u00a0 If you enter an amount that is more than the total of the customer’s open invoices, when you save the transaction a window will open asking you if you want to have Sage 50 automatically create a separate prepayment transaction for the overpayment amount or if you want to “manually fix the difference on the receipt”.\u00a0 I recommend you manually fix the difference on the receipt using one of the methods described above. If you let it enter the prepayment automatically you will end up with two receipt transactions that add up to the total payment amount instead of one receipt that matches the actual payment.\u00a0 This is particularly significant if your print deposit tickets out of Sage 50 because the the number of checks would be incorrect.<\/p>\n","protected":false},"excerpt":{"rendered":" Customer over-payments don’t happen often, but do you know how to deal with them when the situation arises? I’ll also explain how they are affected by a new feature in version 2014.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[9,3],"tags":[],"_links":{"self":[{"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/709"}],"collection":[{"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/comments?post=709"}],"version-history":[{"count":2,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/709\/revisions"}],"predecessor-version":[{"id":711,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/posts\/709\/revisions\/711"}],"wp:attachment":[{"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/media?parent=709"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/categories?post=709"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.iqaccountingsolutions.com\/blog\/wp-json\/wp\/v2\/tags?post=709"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}