Memory & Reporting

Memory

Memory is how the platform learns from your corrections. Every time you fix a field, the platform records the correction. Once it sees the same correction enough times, it starts applying it automatically. The Memory page lists Field Corrections.

Column	What it shows
Field	The field the correction applies to (for example, `vendor_name` or `customer_legal_entity`).
Details	The mapping the platform learned, from the raw extracted value to the corrected value.
Streak	How many consecutive times the correction has been confirmed (for example, 1x, 2x, 3x).
Status	Learning while the streak builds, or Auto-applying once the platform applies it on its own.
Actions	Delete an entry to restore manual review for that field.

A correction stays in Learning while its streak builds. Once it reaches the auto-apply threshold, its status becomes Auto-applying and the platform corrects that field for you going forward. Delete the entry any time to send the field back to manual review.

Reporting

The Reporting workspace answers four questions: are we processing the volume we expected, where are invoices stuck, is the extraction accurate, and are we faster than the manual baseline. Two controls at the top filter everything on the page:

Range: Today, 7d, 30d, or a Custom range.
Entity: All, or a specific entity: SG, MY, HK, ID, PH, or other.

1. Volume & Coverage

The headline cards track throughput against target.

Metric	What it measures
Invoices posted	Successfully posted to the ERP in the selected window.
Invoices created	Top-of-funnel demand, invoices that entered the platform.
Coverage	Posted as a share of the monthly target.
Avg SLA (p50)	Median time from Review clicked to ERP posting.

Below the cards: a daily trend of created vs. posted volume against a per-day target line, a Posted by entity breakdown, a Funnel showing the count at each stage (Extraction, Matching, ERP Posting, Posted), and a Drop-off by reason panel showing where invoices exit the funnel.

08 Reporting Volume — Reporting, Volume & Coverage: headline metrics, daily trend, and the stage funnel.

2. Stage Health

A live snapshot of where invoices are currently stuck, broken out by entity. Each panel flags invoices sitting longer than expected.

Panel	Flag threshold
Stuck in extraction	More than 5 minutes in the extraction stage.
Stuck in matching	More than 15 minutes on the summary screen.
Stuck in ERP posting	More than 2 minutes in ERP posting after matching is confirmed.

Reporting, Stage Health: live view of invoices stuck at each stage, by entity.

3. Quality & Accuracy

The Rejection split shows user-initiated rejections broken down by reason, so you can see whether the extraction is doing its job and where corrections cluster. //need quality & accuracy screenshot with data

4. Efficiency & SLA

This section compares processing speed against the manual baseline of roughly 6 minutes per invoice.

Metric	What it measures
End-to-end SLA, percentiles	Total time from when the invoice entered the platform to when it posted, including any time it sat unassigned or unopened.
Review-to-posted time, percentiles	Only the time from Review clicked to posted. Strips out queue and wait time, this is how fast a human moves once they’ve started.
SLA trend (p50 vs. p95)	The typical case (p50) tracked against the worst case (p95) over time, so you can see if performance is drifting or holding steady.
Per-agent throughput	Invoices posted per agent, colored by median review-to-posted time.
Auto-confirm rate by stage	Of all invoices, the share that passed automatically at each individual stage, extraction, matching, or posting, without a manual correction.
Full auto-confirm (STP-eligible)	The share of invoices that passed automatically at all three stages combined, the true straight-through-processing rate. See Straight-Through Processing for what that means.

Reporting, Efficiency & SLA: percentile SLAs, throughput, and the STP-eligible share.

Reporting An Issue

If you run into a problem, click Report Issue in the left navigation.

Select your issue type

Choose an issue type from the dropdown.

Describe what happened

Enter the details in the text box.

Attach a screenshot (optional)

Add a screenshot or short clip: JPG, JPEG, PNG, BMP, WEBP, or MP4, up to 1MB each, 5MB total.

Submit

Click Submit to send the report to the team. You’ll get an email confirmation with a ticket ID for tracking.

​Memory

​Reporting

​1. Volume & Coverage

​2. Stage Health

​3. Quality & Accuracy

​4. Efficiency & SLA

​Reporting An Issue

Memory

Reporting

1. Volume & Coverage

2. Stage Health

3. Quality & Accuracy

4. Efficiency & SLA

Reporting An Issue