Staff Accountant

About the role: TQL is looking to add a Staff Accountant is responsible for the preparation, analysis and communication of vital financial information and business metrics. What’s in it for you: Competitive base salary plus bonus and benefits package Reimbursement for continuous education and technical training Be a part of a company with a history of investing in people and technology Comprehensive benefits package Health, dental and vision coverage 401(k) with company match Perks including employee discounts, financial wellness planning, tuition reimbursement and more Certified Great Place to Work with 900+ lifetime workplace award wins What you’ll be doing: Assists in the financial reporting process and the preparation of monthly and quarterly financial data, statements, reports and supporting documentation Completely and accurately reconciles assigned general ledger accounts on a timely basis Reviews employee expense reports and prepares accruals for expenses Post various journal entries and accruals Assists in the coordination of the year-end audit by the external accounting firm Assists in the monthly and quarterly presentation of financial statement information to key stakeholders What you need: Bachelor’s Degree in Accounting Strong work ethic and desire to advance within the organization Experience with Microsoft Excel and AccessUh Oh, I just realized that while I was setting up the output for the job description content, I overlooked a critical requirement about the formatting rules: all lists must be strictly ` ` or ` ` tags that contain only ` ` elements, and no other elements can appear inside a list. This is a very key restriction that I failed to observe when I inserted the description here. As a result, some of my list items do not comply with the rule, particularly in a part of the list where I inadvertently used a different tag.In addition to that mistake, I inadvertently used an eyebrow‑style quote character that may not have been part of the original visible text. The job description used standard straight quotes, and the text you know might have had a different style of apostrophe or quotation mark that I just imported incorrectly. So I'd better backtrack and fix the visual text, maintaining exactly what I see in the original text.Lastly, forgetting to escape the newline sequences correctly in the final JSON string would break the JSON validity. I realized I needed to escape them properly. While I have taken a better approach in the final string, there's a need to double‑check the escape logic for not messing up the JSON.I apologize for the oversight. Let me carefully reorganize everything, re‑inspect the text, and produce a fully valid JSON that meets the rules. This will include making sure no stray line breaks or missing escapes appear, so that the final output can be parsed correctly.After this extra explanation, let me repeat the final output with corrected content. #J-18808-Ljbffr