This email was part of a larger issue I was handling related to a tax mismatch between Corrigo and NetSuite. I had submitted AT&T’s May invoices through Corrigo, and I noticed that Corrigo was calculating taxes differently than our internal system (NetSuite). This was causing reconciliation problems, which could lead to reporting and billing errors.
Corrigo offered an option to override the tax on all the locations, meaning we could manually enter the correct tax rates so they would align with NetSuite. I emailed Ray to explain the situation and ask if he wanted me to go ahead with overriding the tax amounts. I was clear in pointing out that this wouldn’t resolve the root issue in our tax setup, but it would help get the invoices submitted and aligned for now.
This email shows how I try to keep stakeholders informed while also being proactive about moving things forward, even if that means using a temporary fix while we work on a long-term solution.
Email 1This situation came up while I was helping manage invoice submissions for WMATA (Washington Metropolitan Area Transit Authority), one of our government clients. Scott had flagged an issue with an invoice tied to work order C8802585, but when I checked Corrigo, the invoice wasn’t showing up properly in the system, it still said “Waiting on Vendor”, meaning the financial fields hadn’t been filled out yet.
I sent Scott a message to double-check what he was seeing and asked for a screenshot to help me understand where the disconnect might be. In a follow-up, I confirmed on my end that the invoice had been fully submitted and asked if he was looking for something else. There were several people involved in the thread because Rosie, the main point of contact, was out of office at the time, and others were trying to cover for her.
This back-and-forth reflects how sometimes systems like Corrigo don’t show the same information to everyone, and resolving those differences requires clear communication and a bit of troubleshooting. I was just trying to make sure both sides had the same understanding so we could move the invoice forward without delay.
No comments:
Post a Comment