--Apple-Mail-8056DBBF-25AE-4CDD-9459-15A6AC8B6E17 Content-Type: multipart/related; type="text/html"; boundary=Apple-Mail-649AB365-33E8-49B9-A813-12C807F07B63 Content-Transfer-Encoding: 7bit --Apple-Mail-649AB365-33E8-49B9-A813-12C807F07B63 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable We will move forward with crediting the cli= ent in alignment with their requests, thank you. Par= don my brevity, Sent from my iPhone On Jul 24, 2023, at 7:20 AM, Timothy Thomas <tt@thekey.com>= ; wrote: =EF=BB=BF Melissa please confirm these times with the care= giver and why our clock in/out times don't line up with the client. Regardless I suggest we move forward with the credit as it'= s not material. Just want to be sure the CG is respecting our process and cl= ocking in/out properly. No need to meet = on this. On Mon, Jul 24, 2023 at 8:51=E2=80=AFAM < eclark@thekey.com > wrote: Hello All- In adva= nce of our time together I=E2=80=99d like to request that you review the bel= ow. The adjustment details provided by Melissa do not align with what the cl= ient requested. There are differences in the 20 th , 25 th , and 27 th . If someone can clarify which are correct, we c= an update the credits created, as appropriate, and cancel our meeting this m= orning. In the event the times we approve to credit differ from t= he Clients, I=E2=80=99d request someone from Operations call the customer to= discuss the credits we can provide, why, etc. versus inserting Finance. Melissa Provided: = Client Payer Provi= ded: = Date = Arrival Departure = Ttl Hrs Worked Ttl Hrs Billed <td width=3D"