Standard recs
Bank, vendor, AR, and intercompany file pairs use saved rules.
Controllers
Controllers and finance managers are responsible for whether the rec was done the same way and whether someone checked it. AuditExport makes the file work visible without claiming a compliance certification.
Sample preview
Synthetic counts. Not live control metrics.
Across this period’s runs
Finished, not checked
Human approval recorded
File could not be read
Too many workbooks, inconsistent processes, limited visibility, review bottlenecks, exceptions that live in chat, and month-end control risk when the only evidence is a file named Final_v7. The job is not more tabs. It is a queue and a history.
The spreadsheet work this audience already does.
Bank, vendor, AR, and intercompany file pairs use saved rules.
Preparation and approval are separate human actions.
Open items have an owner and a status.
See runs awaiting review and failed jobs without opening every workbook.
Export from the run. Approval is recorded. Source files stay unchanged.
Recipes keep mappings and match types from drifting by person.
Roles decide who can approve. The server re-checks the action.
The default work is what did not match.
Engines produce matches and findings. AI does not write the amounts.
Who uploaded, who commented, who approved — stored as events.
Open the product pages that usually sit next to this audience’s work.
See open exceptions, runs awaiting review, failed workflows, and automation status.
Maker/checker review with role-based access and audit history.
Work the rows that did not match — status, comments, assignment, and history.
Turn run results into Excel, PDF, and management packs a reviewer can open.
Upload two or more Excel or CSV files, map columns, and separate matches from exceptions.
Monday the dashboard shows three runs awaiting review and forty-two open exceptions. The controller opens the vendor queue, not the source AP file. Two items go back to AP. One run is approved. That is the control activity — not a certified attestation.
Step 1
Runs the recipe and clears obvious matches.
Step 2
Works the remaining exceptions and the balance gap.
Step 3
A user with permission approves. History keeps the name and time.
Control is visibility plus a second person plus a record. AuditExport provides that on uploaded files. It does not claim SOC 2, ISO, or statutory sign-off because a maker/checker workflow exists.
No. Reviewer controls are a workflow. We do not claim certified regulatory compliance on this page.
Yes. Approval is a recorded action by an authenticated user.
No. Approval is always a human user.
Start free. Invite a reviewer and keep approval on the run.