Implementation

Start with the finance process you already have. Replace the spreadsheet layer.

WREKONN does not require a direct integration to deliver the core reconciliation and close workflow. Your team can begin with existing ticketing and accounting exports, without waiting for a direct integration.

A practical implementation sequence

The goal is a working first reconciliation, not a long configuration project that ends at “setup complete.”

01

Define the scope

Confirm organization, team/venue context, fiscal periods, required ticketing reports, ERP, and the exact finance questions WREKONN must answer.

02

Load the finance structure

Import the chart of accounts and event master. Configure accounting rules, mappings, dimensions, tolerances, and materiality.

03

Map the source files

Use Ticketmaster/Archtics and ERP files already available to finance. Map fields into WREKONN’s standard model.

04

Run the first reconciliation

Process ticketing and ERP evidence, review exceptions, confirm mappings, and establish the repeatable workflow.

05

Configure journals and close

Confirm approval roles, journal export format, source-completeness requirements, event close, and period sign-off.

06

Automate selectively

Add API, SFTP, scheduled-file, middleware, or custom connectors later where automation creates enough value for that team.

File-first does not mean limited

Run a repeatable reconciliation and close workflow with file uploads.

Customers can upload Ticketmaster and ERP files, map them, validate them, reconcile them, approve journals, and download ERP-ready outputs without waiting for a native connector.

CSV and values-only XLSXUse common finance exports and retained source evidence.
Reusable mappingsSave reusable mappings for the columns in your ticketing and accounting exports.
ERP-ready journal outputsExport formats can reflect the target ERP and customer implementation.
Integration stays team-specificAutomate where the customer’s access, systems, and economics justify it.

Bring the reports you use today.

We can start by understanding how those files become your current reconciliation, journals, and close.

Discuss implementation