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. File-based operation is a first-class production mode.
A practical implementation sequence
The goal is a working first reconciliation, not a long configuration project that ends at “setup complete.”
Define the scope
Confirm organization, team/venue context, fiscal periods, required ticketing reports, ERP, and the exact finance questions WREKONN must answer.
Load the finance structure
Import the chart of accounts and event master. Configure accounting rules, mappings, dimensions, tolerances, and materiality.
Map the source files
Use Ticketmaster/Archtics and ERP files already available to finance. Map fields into WREKONN’s standard model.
Run the first reconciliation
Process ticketing and ERP evidence, review exceptions, confirm mappings, and establish the repeatable workflow.
Configure journals and close
Confirm approval roles, journal export format, source-completeness requirements, event close, and period sign-off.
Automate selectively
Add API, SFTP, scheduled-file, middleware, or custom connectors later where automation creates enough value for that team.
Manual import can still be a controlled production workflow.
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.
Bring the reports you use today.
We can start by understanding how those files become your current reconciliation, journals, and close.