Approval Task - Client Rejection

Hi @David K Hatch, welcome to the Karbon community!

I’m also curious about this. We have only started testing approvals.

Hi @David K Hatch - in the conversations we had with customers when initially designing the feature, one of the very clear pieces of feedback we had that an approval was only requested when the client had seen the document(s) for approval and given feedback. i.e. the back and forth over the final version has happened and the client is satisfied with the document.

Can you tell me how your approval process works?

Also wondering about this. We prepare a board report, send it to client for approval. Nine times out of ten it is approved, sometimes though, there is a comment or question.

I would assume any function with client interaction would be capable of a back and forth.

Even items we think are final can always come back with a “just one more thought...” type of thing.

@StuartK  and @Stephanie Veal—I totally agree with the scenario provided by Stuart; however, there have been instances where, after all the “back and forth,” the client rejects the item of discussion. I was just looking for a way to close the activity with a client response of “Rejected.”  This will provide an audit trail for future reference if needed.

Now, being new to Karbon, this may already exist, and I am just not familiar enough with the product to know how to document the Client rejection. If so, please provide me with guidance. I want to learn, as I love the Karbon product.

Thanks.

Keith

For our company we have a number of bookkeeping clients we’re hoping to start using this approvals for - so we can send month end reports that the client can review and approve. If they don’t have any questions and are fine with the reports then they can just approve, but sometimes they do have a change or a question so some form of back/forth would be helpful here within the approval process.

Until now we’ve been using client tasks to send the reports, asking them to review and tick the task off as completed to indicate their approval, and there is the ability to have back/forth in client tasks. But I want to avoid having back/forth in a client task, and then re-sending a report for approval if there already were no questions in the client task...hope this makes sense.  

For now it seems like continuing to use client tasks would be our firm’s best approach if there isn’t that back/forth opportunity in the approvals task.

Ah, I thought it was a back and forth that ended in an approval. Like a way to document what lead to the approval. Not the final stamp of approval. Will need to reassess if and how we use.