tripwise

Documentation

Feature guide

Reports

The Reports section produces a clear, structured summary of your exception data that you can share with a client or present to management — without requiring them to log in to the dashboard themselves.

When to use a report

Reports are most useful at the end of a reconciliation cycle, once your team has worked through the exception queue. Common uses include:

  • Sending a weekly operational summary to a client who wants visibility on exceptions and resolution activity.
  • Briefing senior management on the current state of financial risk across live bookings.
  • Documenting what was found and resolved during an audit period.
  • Supporting a dispute with a supplier — showing that a specific issue was detected, logged, and acted on.

What the report shows

The report is designed to give a complete picture at a glance, without requiring the reader to understand how Tripwise works internally. It includes:

  • When it was generated — so the reader knows exactly how current the data is.
  • Total exceptions — the overall count, broken down by urgency level (Critical, High, Medium, Low).
  • Total amount at risk — the combined financial exposure across all open exceptions.
  • Breakdown by problem type — which categories of issue are driving the most risk, ranked by value.
  • Breakdown by supplier — which suppliers appear most frequently in exceptions, and how much is associated with each.
  • Top individual exceptions — the highest-priority cases with a brief description of each issue.
  • Recommendation — a plain-language statement of where to focus next and why.

Generating and printing a report

  1. Navigate to the Reports section from the top navigation.
  2. The report is generated automatically from your current data. By default it covers all exceptions with Open status.
  3. Click Print reportto open your browser's print dialog. Select Save as PDF to create a document you can email to a client or attach to a presentation.

Best time to generate a report

Generate the report after your team has finished triaging — not before. A report run mid-cycle will show a high number of open exceptions that are already in progress. Run it once the Critical and High cases have been actioned so the report reflects the resolved state.

When you print the report, the navigation bar, filter controls, and any other dashboard elements are automatically hidden. What prints is a clean document with the Tripwise logo, the report data, and your organisation's context — nothing else.

Changing the scope of a report

You can adjust what the report covers using the controls at the top of the Reports page:

  • Status filter — By default the report shows Open exceptions. Switch to Resolved to produce a report of everything your team fixed during a given period. Switch to Ignored or False positive to document exceptions that were reviewed and closed without action.
  • Top exceptions limit — Controls how many individual exceptions appear in the top exceptions table. The default is 10, which works well for most presentations. Increase this if your client wants a more detailed breakdown.

Per-import reports

In addition to the organisation-wide report, Tripwise also generates a focused report for each individual import. To view it, go to Imports, click on any completed import, and look at the exceptions section on that import's detail page.

This is useful when a client asks about a specific batch of data — for example, "what did last Tuesday's upload produce?" — or when you are investigating whether a particular file introduced an unusually high number of exceptions.

Understanding the recommendation

The recommendation at the bottom of the report is produced automatically based on which exception type is driving the most financial risk at the time the report was generated.

It is not a definitive instruction — your team knows the context better than any automated system. But it is a useful anchor for client conversations and for briefing colleagues who are coming to the situation fresh. The three possible recommendations are:

When payments without confirmations are the dominant issue:

"Start by reviewing captured payments linked to unconfirmed or missing bookings. These represent the strongest immediate operational and customer-impact risk."

When supplier mismatches are the dominant issue:

"Start by reviewing supplier confirmations that do not match the internal booking state. These may indicate booking state synchronisation issues or incomplete operational handoff."

When missing supplier references are the dominant issue:

"Start by reviewing confirmed bookings without supplier references. These may indicate incomplete supplier confirmation or missing operational handoff."

Turning a report into a client update

Here is an example of how to translate a Tripwise report into a clear client communication:

What the report shows

23 open exceptions — 8 Critical, 7 High, 5 Medium, 3 Low

Total amount at risk: £14,820

Primary issue: payments without confirmed bookings — 15 cases, £11,200 combined

How you might communicate this to a client

"Our reconciliation run for the week ending [date] identified 23 operational exceptions across 495 processed transactions. The main issue is 15 cases where a payment was captured but no supplier confirmation exists — these carry a combined risk of £11,200 and are being treated as same-day priorities. We will share an update on resolution progress by close of business today."