kevinstratton
My feedback
2 results found
-
84 votes
An error occurred while saving the comment kevinstratton
supported this idea
·
-
176 voteskevinstratton
supported this idea
·
This API documentation provides instructions on how to issue refund receipts in QBO,
https://developer.intuit.com/docs/api/accounting/refundreceipt
Voiding indivual invoices is also implemented via the Void section found in this documentation
https://developer.intuit.com/docs/api/accounting/invoice
Credit memos could also be used, but are not preferred.
In my opinion as a developer who's done plenty QBO API tasks for our clients I can tell you the easiest way to implement this functionality is;
1. If an entire invoice is voided or deleted from repairshopr, push the void command. QBO doesn't have object limits like desktop does, no need to worry about deleting invoices from QBO, Intuit's cloud can handle the data, which I understand can be resource intensive for cloud web applications like Repairshopr. Most customers love having the history in QB to provide an audit trail, Ex: clerk accidentally deletes invoice in RepairShopr, management who uses and watches QBO can see all history, basically a paper trail here.
Next, for refund receipts, this can be implemented by issuing indivual refunds to customers, or the register account. RepairShopr already generates a separate refund invoice when processing refunds. This could easily be pushed into QBO as a refund receipt. The detail here is nice to have in QBO as it can be used to see separate transactions in QBO as items are returned. Very useful for transactions that have many items that may be returned at different times. By pushing a correct payment type, as is already functional in the begin refund screen, deposits would match in QBO, eliminating manual double entry. Pushing refund receipts with dates is also very helpful for business to see their exact cash flows in QBO. Ex. 10 Items are purchased on 1/1/16, the invoice is pushed to QBO, 2 items are returned on 1/15/16, a refund is pushed on this date, leaving 8 that are still technically sold. After this refund is synced, the accounts are accurate with the current state and current time, as items maybe returned in the future, more refunds can be pushed. The functionality for this is already in Repairshopr, the connection just needs to be made.
I've reached out to our intuit reps in the channel, and this one of the biggest complaints they hear about Repairshopr as a QBO add on solution, basically that the QBO integration isn't completely functional, customer account charges isn't truly functional either. Repairshopr is a front end and operations solution, not accounting, many business have employees that handle billing, and not being able to print statements, and have payments received in QB not apply to Repairshopr adds a lot of manual work.
Overall we feel like the software is great, and feel like typing up the final strings with QBO integration wouldn't only help us, and our clients, but also Repairshopr.