Zendesk mark

ZENDESK

Senior Financial Systems Analyst

ZENDESKSenior Financial Systems Analyst

Turning reconciliation work into exception-led finance operations.

Workflow from raw transactions through matching rules, an exception queue, human review, controlled resolution, and close.

01 / Systems foundation

NetSuite and Expensify implementation

ERP foundation

NetSuite

NetSuite established the finance-system foundation across record-to-report, procure-to-pay, and quote-to-cash work.

  1. 01Configure the finance processes and system controls.
  2. 02Connect upstream and downstream operating systems.
  3. 03Test complete business cycles before go-live.

Expense operations

Expensify

The worldwide expense-reporting rollout connected Expensify with NetSuite.

  1. 01Discovery and setup
  2. 02NetSuite integration
  3. 03UAT and implementation

02 / Public-company audits

Taking the systems through public-company audits

After implementation, NetSuite and Expensify moved into the recurring work of public-company audit review.

The focus shifted from getting systems live to making transactions, approvals, integrations, and changes traceable through review.

01Operate the ERP and expense workflows
02Walk transactions and controls through audit testing
03Resolve findings and carry changes into the next close

03 / Close platform

BlackLine after the audit

After the ERP and expense foundations had been through public-company audits, the next implementation was BlackLine.

BlackLine’s published Zendesk case study says the company brought in BlackLine to automate transaction matching, account reconciliations, and task management.

Read the published Zendesk case study

04 / Matching areas

Each matching area solved a different comparison problem.

01

New and Expansion MRR

MRR ↔ provisioned seats Workflow diagram with New and Expansion MRR product icons on the left, a central matching symbol, and Salesforce provisioned seats on the right.
Revenue recordsSeat records

02

NetSuite and Zuora

Zuora ↔ NetSuite Two workflow diagrams with Zuora records on the left, a central matching symbol, and NetSuite records on the right.
Zuora recordsNetSuite records

03

NetSuite and Coupa

The procure-to-pay matching area connected Coupa and NetSuite records so exceptions could be identified and reviewed.

Systems: Coupa, NetSuite, and SFTP

Workflow: procurement records → matching → exception review

04

Cash application

Bank ↔ ledger Workflow diagram with daily bank transactions on the left, a central matching symbol, and NetSuite bank-account general-ledger detail on the right.
Bank activityLedger detail

05

Billing and provisioning

This matching area compared invoiced users with users provisioned in Zendesk so differences could move into exception review.

Systems: BlackLine, SQL, and Python/Django

Workflow: invoiced users → matching → provisioned users