Finance Systems

1. You are here:
2. Business Technology
3. Enterprise Applications Team
4. Finance Systems

On this page

• Finance Systems Charter
• Meet the team
• How We Work within Enterprise Applications
  • Service Desk / Services We Support
  • Finance Systems Change Management Procedures
• Systems We Own

Finance Systems Charter

The Finance Systems Administrator Team implements and supports specialized applications for the finance team within GitLab.

Meet the team

• Wendy Lam - Finance Systems Administrator (P2P and Record to Report Expert)
• Jessica Salcido - Finance Systems Administrator (Interim Manager, Q2C Expert)
• Cristine Marquardt - Finance Systems Administrator (Service Desk Guru), Certified Zuora Administrator
• Brian Wong - Finance Systems Administrator, Certified Zuora Administrator

How We Work within Enterprise Applications

• All work in which requirements need vetting will need to follow the Enterprise Appliations intake process.
• Once requirements are cleansed, the Business Systems Analyst team will create issues for system configuration work to be performed by the Finance Systems team.

Service Desk / Services We Support

• Service Desk Board Labels: ~FinSys::Service Desk
• Our Service Desk takes care of:
  • User Access to the Finance Systems we manage through Access Requests and Offboarding issues.
  • All services outlined here: SKU Requests, SKU Retirement, Configuration Changes, Department Change Requests, EntApps System Incident Log, Coupa Sandbox Refresh, Netsuite Sandbox Refresh, Zuora Central Sandbox Refresh.
• Issues will be assigned a Priority:
  • ~BT-Priority::1
  • ~BT-Priority::2
  • ~BT-Priority::3
• Issues will be assigned to a Milestone by Enterprise Applications leadership team. Assignment to a milestone is based on the issue weight, priortiy, and team member capacity.
• Once issues are assigned to a Finance Systems Administrator and assigned to a Milestone, we track the status of the issue by asigning labels:
  • Open: Pending Priority and Admin assignment. Access Requests will progress to "In Progress" within 72 hours of assignment of the ~FinSys::Service Desk label.
  • ~BT::InProgress: Priority and Admin has been assigned and it’s actively being worked on.
  • Closed or BT::Done External: Request has been fulfilled entirely or next steps have been agreed to. Sometimes an issue cannot be closed by the FinSys team because there are tasks/requests for other teams (i.e. Access Requests), so in those cases we’ll mark it with BT::Done External which indicates all work for the FinSys team has been completed.
  • If an issue is still Open, and a milestone is pending closure, we may move to the next Milestone during the Milestone Planning process.

Finance Systems Change Management Procedures

Because the Finance Systems team works on in-scope business systems which are subject to compliance requirements, we adhere to the Business Technology Change Management policy.

This means that configuration changes made within the systems we own may require approvals, testing in pre-production environments, Peer Review, and/or Post-Implementation Review.

Systems We Own

System	Function
Adaptive Insights	Financial Planning and Budgeting
Avalara	Tax Engine
Coupa	Procurement and AP
Docusign	Signatures
Expensify	Expense Management
Netsuite	ERP
Stripe	Payment Processor
Tipalti	AP
TripActions	Travel Booking
Workiva	Reporting
Zuora Billing	Billing
Zuora Revenue	Revenue Recognition