Skip to navigation

The data behind your charts

View as Markdown

This chapter lists the tables you can build a chart from, explains what each one captures, and describes what each column means and what you would use it for.


1. How to read this chapter

When you start a new question, the Pick your starting data list shows the tables described here. Every one of them is scoped to your own organisation: you never see another customer’s rows, whatever you build.

Names appear differently in the picker. This chapter uses the underlying names, in lower case with underscores, because they sort predictably and are easier to search for. The Business Dashboard shows them with spaces and capitals: analytics_documents appears as Analytics Documents, analytics_export_logs as Analytics Export Logs, and so on.

1.1 Three shapes of table, and why it matters

The tables are not all built the same way, and the shape decides what you can ask of them.

ShapeWhat it meansConsequence
Per-recordOne row per document, per export, per scan, per fieldYou can filter by any date on the row, group by any dimension, and drill into the individual records behind a number
DailyAlready summed to one row per dayFast, and safe to plot over time, but you can only slice by the columns that were kept when it was summed
All-time summaryOne row per queue, with no date at allThe figures cover all time, so a Date filter has nothing to act on and the chart will not respond to it

This is the most useful thing to know before you build. If a card does not move when you change the Date filter, it is almost always built on an all-time summary table. To get a dated version, rebuild it on the per-record table underneath. Each entry below states which shape it is.

1.2 Columns you will see nearly everywhere

These are described once here rather than in every table.

ColumnWhat it holdsWhat you would use it for
document_idThe unique number of one documentCounting documents with Number of distinct values, and joining one table to another
queue_idThe queue the record belongs toGrouping or filtering by queue. It displays the queue name, not the number
model_idThe extraction model usedGrouping or filtering by model. It displays the model name, not the number

You may also see a few housekeeping columns, such as synced_at, which records when a row was last refreshed. Build date filters on a business date such as uploaded_at or exported_at, never on synced_at.

1.3 How each entry is laid out

Every table below gives you its shape, its grain (what one row represents), which columns you can filter dates on, and then its columns with their meaning and use.


2. Documents

2.1 analytics_documents

The central table. One row for every document in your queues, carrying its current status, the people who touched it, and the timestamp of each stage it passed through. Most questions can be answered from this table alone, without joining anything.

Shape: per-record · Grain: one row per document · Dates: created_at, uploaded_at, completed_at, exported_at, rejected_at, first_review_at, last_review_at

ColumnWhat it holdsWhat you would use it for
document_idThe document’s unique numberCounting documents, drilling to the individual record
user_idThe person who uploaded itVolume per uploader
queue_idThe queue it sits inComparing queues
doc_typeThe document type, such as INVOICE or RECEIPTFiltering to one type, or splitting a chart by type
model_idThe extraction model appliedComparing model performance
use_created_modelTrue when a model your organisation built was used, false when a Staple predefined model was usedSeparating custom model results from predefined ones
statusWhere the document currently standsCounting by outcome. Values are listed in section 10
companyThe company or entity named on the document, where one was capturedSplitting by entity
uploaded_byThe email address of whoever uploaded itAttribution by person
uploaded_fromThe channel it arrived through, such as email, API, UI or dropboxSeeing which ingestion route carries your volume
completed_byThe person who marked it CompletedReviewer throughput
exported_byThe email address of whoever exported itAttribution for exports
rejected_byThe person who rejected itWho is rejecting, and how much
exported_typeThe format it was exported as, such as XML, CSV or CONCURSplitting exports by destination format
created_atWhen the record was created in StapleThe creation date for generated documents
uploaded_atWhen the document entered its queueThe main volume date. Use this for “how much arrived”
completed_atWhen it was marked CompletedCompletion volume over time, and the end point of review duration
exported_atWhen it was exportedExport volume over time, and the end point of end-to-end duration
rejected_atWhen it was rejectedRejection volume over time
first_review_atThe first time someone opened it for reviewThe start of hands-on time
last_review_atThe most recent time someone opened it for reviewThe end of hands-on time
time_process_scan_msHow long scanning took, in millisecondsScan duration. Divide by 1000 for seconds, and restrict to values above zero
completenessThe percentage of expected fields that were filledFinding thinly extracted documents. Empty on documents that never reached extraction
error_messageThe processing error recorded against it, where there was oneCounting failures by message. DUPLICATE appears here rather than in status
scanning_errorThe error recorded at the scanning stageIsolating scan failures from later failures
status_codeThe numeric result code from processingGrouping failures by kind. 200 succeeded, 409 is a duplicate, codes in the 500s are processing errors
num_pagesHow many pages the document hasSum it for page volume
created_by_supernovaTrue when Staple generated the document rather than someone uploading itSeparating generated documents from uploaded ones. Most other tables exclude generated documents

2.2 analytics_document_counts

A set of headline totals per queue: how many documents you have in total, this month, last month, and how many were removed, duplicated or ended in an exception.

Shape: all-time summary · Grain: one row per queue · Dates: none

ColumnWhat it holdsWhat you would use it for
queue_idThe queueComparing queues
total_documentsEvery document in that queue, for all timeA headline total
current_month_documentsDocuments uploaded since the first of this monthA month-to-date figure
previous_month_documentsDocuments uploaded during the whole of last monthMonth-on-month comparison against the column above
removed_documentsDocuments that were deletedMeasuring how much gets removed
duplicate_documentsDocuments rejected as already seenMeasuring duplicate load
anomaly_documentsDocuments that were rejected, failed to export, or failed to scanOne combined exceptions figure

The month columns are fixed. This month and last month are calculated from today’s date, not from your Date filter.

2.3 analytics_status_counts

How many documents sit in each status, per queue.

Shape: all-time summary · Grain: one row per queue and status · Dates: none

ColumnWhat it holdsWhat you would use it for
queue_idThe queueComparing queues
statusThe status, such as EXPORTED or RECEIVEDThe category axis of a status breakdown
documentsHow many documents hold that statusSum it for the bar or pie value

2.4 analytics_document_actions_by_day

The five headline document actions, counted per day and per queue, each on its own date. A document uploaded on Monday and exported on Friday is counted under Monday in received and under Friday in exported.

Shape: daily · Grain: one row per queue and day · Dates: event_date

ColumnWhat it holdsWhat you would use it for
queue_idThe queueComparing queues
event_dateThe day the action happenedThe time axis
receivedDocuments that arrived that dayIntake volume
completedDocuments marked Completed that dayReview output
exportedDocuments exported that dayDelivery volume
rejectedDocuments rejected that dayRejection volume
export_failedDocuments whose export failed that dayFailure volume

2.5 analytics_document_events

Every stage a document can pass through, as a single list of dated events. Because the stage is a column rather than a set of columns, one chart can carry all of them as separate lines.

Shape: daily · Grain: one row per day, stage, queue and model · Dates: event_date

ColumnWhat it holdsWhat you would use it for
event_dateThe day the stage happenedThe time axis
event_typeWhich stage: Uploaded, Generated, Scanned, Scan Failed, Rescanned, Completed, Rejected, Exported, Export FailedSplitting one chart into a line per stage
queue_idThe queueComparing queues
model_idThe modelComparing models
docsHow many documents hit that stage that daySum it for the line value

This is usually the table you want for a processing funnel over time, because a single chart can show intake, output and failure together.

2.6 analytics_page_events

The same idea as the table above, counted in pages rather than documents.

Shape: daily · Grain: one row per day, stage, queue and model · Dates: event_date

ColumnWhat it holdsWhat you would use it for
event_dateThe day the stage happenedThe time axis
event_typePages Uploaded, Pages Generated, Pages Scanned, Pages Rescanned or Pages ExportedA line per stage
queue_idThe queueComparing queues
model_idThe modelComparing models
pagesHow many pages hit that stage that daySum it for the line value

2.7 analytics_uploads_by_day

Upload volume alone, already broken out by queue, document type and model.

Shape: daily · Grain: one row per day, queue, document type and model · Dates: event_date

ColumnWhat it holdsWhat you would use it for
event_dateThe day of uploadThe time axis
queue_idThe queueComparing queues
doc_typeThe document typeA line per document type
model_idThe modelComparing models
documentsHow many arrivedSum it for the line value

3. Extracted fields and accuracy

3.1 analytics_document_fields

Every field value Staple extracted, one row per field per document. This is the largest table you have access to, and it is where the extracted values live, so it is what you use to chart the contents of your documents rather than their processing.

Shape: per-record · Grain: one row per document and field · Dates: uploaded_at, completed_at

ColumnWhat it holdsWhat you would use it for
document_idThe document the value came fromCounting documents, joining to analytics_documents
queue_idThe queueComparing queues
doc_typeThe document typeFiltering to one type
statusThe document’s status at the time the row was writtenRestricting to exported or completed documents only
document_languageThe language detected on the documentSplitting by language
field_keyThe internal name of the fieldFiltering to one field. Use this rather than field_name, because it does not change
field_nameThe label shown for that field in StapleReadable axis labels
field_categoryThe section the field sits in, such as Basic Information or VAT & AmountsGrouping fields into areas
field_typeWhat kind of field it is, such as Text, Amount or DateRestricting to fields you can total
value_kindWhich of the value columns below is populated: text, number, date, boolean, json or nullFiltering to rows whose value you can chart
value_textThe value as text, for every rowGrouping by value, counting occurrences
value_numberThe value as a number, where it is oneSum or Average it, for example totalling invoice amounts
value_dateThe value as a date, where it is onePlotting by a date on the document, such as invoice date, rather than a processing date
value_booleanThe value as true or false, where it is oneCounting how often a checkbox was ticked
uploaded_atWhen the parent document arrivedThe time axis
completed_atWhen the parent document was completedAn alternative time axis

Two things to know before you total anything here. Rows where value_kind is json hold a structure rather than a single value, which is how line-item tables are stored, so value_text on those rows is structured data rather than a plain figure. And because there is one row per field, a plain count counts fields, not documents: use Number of distinct values on document_id when you mean documents.

3.2 analytics_document_field_catalog

The list of which fields exist on which queue, without any of the values. Use it to find out what you can chart before you go looking for it.

Shape: all-time summary · Grain: one row per queue and field · Dates: none

ColumnWhat it holdsWhat you would use it for
queue_idThe queueSeeing which fields a queue captures
doc_typeThe document type the field belongs toFiltering to one type
field_keyThe internal name of the fieldThe value to use when filtering analytics_document_fields
field_nameThe label shown in StapleRecognising the field
field_categoryThe section it sits inBrowsing fields by area
field_typeWhat kind of field it isJudging whether it can be totalled
available_value_kindsEvery value kind seen on that fieldChecking a field holds numbers before you try to sum it

3.3 analytics_field_differentials

One row for every field a reviewer looked at, recording what Staple predicted and what the value ended up being. This is the source of every accuracy figure in the product.

Shape: per-record · Grain: one row per field per document reviewed · Dates: created_at

ColumnWhat it holdsWhat you would use it for
differential_idThe reference for one document’s whole review comparisonCounting reviewed documents. There is roughly one of these per document
field_differential_idThe reference for this single field rowCounting individual field comparisons
document_idThe documentCounting documents that needed correction
user_idThe reviewerCorrection volume per person
queue_idThe queueComparing queues
model_idThe model that made the predictionComparing model accuracy
field_keyWhich fieldFinding the fields that need the most review effort
predictedWhat Staple extractedInspecting individual differences on drill-through
ground_truthWhat the value was after reviewThe same
is_matchTrue when the prediction was left alone, false when it was correctedThe accuracy column. Count where false for corrections, or average it for an accuracy rate
differential_accuracyHow close the prediction was, for partial matchesA finer measure than the true or false above
created_atWhen the review happenedThe time axis

3.4 analytics_accuracy_by_day

Accuracy already worked out per day, model, queue and field.

Shape: daily · Grain: one row per day, model, queue and field · Dates: event_date

ColumnWhat it holdsWhat you would use it for
event_dateThe dayThe time axis
model_idThe modelA line per model
queue_idThe queueComparing queues
field_keyThe fieldAccuracy for one field over time
accuracyThe percentage of fields left uncorrected that dayThe chart value
field_countHow many fields were reviewedWeighting, and judging whether a day’s percentage rests on enough data
edited_countHow many were correctedCorrection volume

Averaging accuracy treats a day with three fields the same as a day with three thousand. Where the difference matters, build the percentage from edited_count and field_count instead.

3.5 analytics_ocr_rework_load

Which fields your reviewers correct most, per queue. This is the table for “where is our manual effort going”.

Shape: all-time summary · Grain: one row per queue and field · Dates: none

ColumnWhat it holdsWhat you would use it for
queue_idThe queueComparing queues
fieldThe fieldThe category axis
edited_countHow many times that field was correctedRanking fields by correction volume
document_countHow many documents the field appeared onContext for the count above
edited_per_documentCorrections divided by documentsA fair ranking that does not simply favour common fields

3.6 analytics_ocr_rework_summary

The two headline automation figures per queue: what share of documents went through untouched, and how much of what was extracted was kept after review.

Shape: all-time summary · Grain: one row per queue · Dates: none

ColumnWhat it holdsWhat you would use it for
queue_idThe queueComparing queues
documentsDocuments in the queueThe denominator
straight_through_documentsDocuments nobody had to correctThe numerator
stpStraight-through rate as a percentageThe automation headline
accuracyPercentage of extracted fields left uncorrectedThe accuracy headline

This table powers the two all-time cards on Staple Dashboard, which is why they do not respond to the Date filter. For a dated version, build on analytics_field_differentials or analytics_accuracy_by_day instead.


4. Processing time

4.1 analytics_process_time_comparison

Average duration per day for three stages of processing.

Shape: daily · Grain: one row per queue, day and stage · Dates: event_date

ColumnWhat it holdsWhat you would use it for
queue_idThe queueComparing queues
event_dateThe day the documents were uploadedThe time axis
chart_typeWhich stage: TIME_TO_EXPORT, TIME_TO_SCAN or TIME_TO_REVIEWFilter to one of these. Mixing stages in one chart mixes very different magnitudes
none_editThe average duration for every document that dayThe main line
fields_onlyThe average duration for the documents that had at least one field correctedComparing corrected documents against the overall average

Every figure in this table is in hours, including the scanning stage, which is why scan times read as small fractions. Multiply by 60 for minutes or 3600 for seconds.

The two value columns overlap rather than add up. none_edit covers all documents and fields_only covers the corrected subset of those same documents.

For a document-weighted average, build it from analytics_documents instead. This table averages each day first, so a day with two documents counts as much as a day with two thousand. Section 2.1 has the timestamps you need.


5. Scanning

5.1 analytics_billing_scan_attempts

Every scan of every document, first scans and rescans together.

Shape: per-record · Grain: one row per scan attempt · Dates: attempt_at

ColumnWhat it holdsWhat you would use it for
attempt_idThe attempt’s unique referenceCounting attempts
document_idThe document scannedCounting distinct documents rather than attempts
queue_idThe queueComparing queues
model_idThe modelComparing models
attempt_typeINITIAL for a first scan, RESCAN for a repeatSeparating new work from repeat scans
statusSUCCESS, FAILED or PENDINGScan success and failure rates
attempt_atWhen the scan ranThe time axis
num_pagesPages in that attemptSum it for scanned page volume

5.2 analytics_rescan_attempts

Rescans only, in more detail than the table above carries.

Shape: per-record · Grain: one row per rescan · Dates: started_at, finished_at

ColumnWhat it holdsWhat you would use it for
attempt_idThe attempt’s unique referenceCounting rescans
document_idThe documentFinding documents rescanned repeatedly
queue_idThe queueComparing queues
model_idThe modelComparing models
requested_byWho asked for the rescanAttribution
engineWhich scanning engine ran itComparing engines
scan_typehard_rescan or soft_rescanSeparating a full re-extraction from a light one
statusSUCCESS, FAILED or PENDINGRescan success rate
document_statusThe document’s status when the rescan ranContext
outcomesuccess, duplicate or errorA finer result than status, because it separates duplicates from errors
status_codeThe numeric result codeGrouping errors by kind
error_messageThe error textReading what failed on drill-through
started_atWhen the rescan beganThe time axis
finished_atWhen it endedThe end point of duration
duration_msHow long it took, in millisecondsAverage it for rescan duration. Divide by 1000 for seconds
num_pagesPages rescannedSum it for rescanned page volume

6. Exports

6.1 analytics_export_logs

One row per export attempt, including the attempts that failed. A document exported three times appears three times.

Shape: per-record · Grain: one row per export attempt · Dates: created_at

ColumnWhat it holdsWhat you would use it for
export_log_idThe attempt’s unique referenceCounting attempts
document_idThe document exportedCounting distinct documents rather than attempts
user_idWho triggered the exportAttribution
export_typeThe destination format, such as CONCUR, CSV or JSONComparing integrations
web_hook_idThe webhook used, where one wasTying failures to a specific integration
is_successfulTrue when the export went throughThe success rate column. Average it for a rate, or count where false for failures
created_atWhen the attempt happenedThe time axis

6.2 analytics_export_fail_reasons

Every reason recorded against a failed export, one row per reason. A document that failed for three reasons appears three times.

Shape: per-record · Grain: one row per document and reason · Dates: exported_at

ColumnWhat it holdsWhat you would use it for
document_idThe document that failedCounting distinct documents affected
reasonThe message the receiving system returnedThe category axis of a failure breakdown
exported_atWhen the export was attemptedThe time axis

This is the export failure table to use for a specific period, because it carries a date.

6.3 analytics_export_fail_reason_snapshots

The same information with all of a document’s reasons held together in one row as a list.

Shape: per-record · Grain: one row per document · Dates: exported_at

ColumnWhat it holdsWhat you would use it for
document_idThe documentCounting documents
reasonsEvery reason for that document, as a listCounting how many distinct problems one document had. For charting reasons, 6.2 is easier
exported_atWhen the export was attemptedThe time axis

6.4 analytics_export_failure_reasons

Failure reasons already counted per queue.

Shape: all-time summary · Grain: one row per queue and reason · Dates: none

ColumnWhat it holdsWhat you would use it for
queue_idThe queueComparing queues
reasonThe failure messageThe category axis
num_docsHow many documents failed for that reasonSum it for the bar value

Quick to use, and covers all time. If you need the breakdown for a period, use 6.2.

6.5 analytics_export_reliability

A two-way split of your documents: those that exported cleanly, and those that failed at least once.

Shape: all-time summary · Grain: one row per queue · Dates: none

ColumnWhat it holdsWhat you would use it for
queue_idThe queueComparing queues
zero_export_failure_docsDocuments that never had a failed exportThe clean share
at_least_one_export_failure_docsDocuments that failed at least onceThe exception share

6.6 analytics_third_parties

Volume by external system, covering both directions: what each channel brought in, and what each format sent out.

Shape: all-time summary · Grain: one row per queue and system · Dates: none

ColumnWhat it holdsWhat you would use it for
queue_idThe queueComparing queues
sourceThe system. Inbound channels such as email, API or dropbox, and outbound formats such as CSV or CONCURThe category axis
importedDocuments that arrived through itIntake by channel
exportedDocuments successfully sent through itDelivery by integration
failed_to_exportDocuments that failed to send through itFinding the integration that needs attention

Inbound and outbound share one column. A row will usually have a figure in imported or in the two export columns, not both, so read the measure you asked for rather than the row as a whole.


7. People and review

7.1 analytics_review_logs

One row every time someone opened a document for review.

Shape: per-record · Grain: one row per review event · Dates: reviewed_at

ColumnWhat it holdsWhat you would use it for
review_log_idThe event’s unique referenceCounting review events
document_idThe document reviewedCounting distinct documents, or finding those opened many times
user_idWho reviewed itReviewer activity over time
reviewed_atWhenThe time axis

This is the table to use for review activity over a period, because it is the one that carries a review date.

7.2 analytics_user_activity

A standing scorecard per person per queue: what they have uploaded, what is still open, what they finished, and how quickly.

Shape: all-time summary · Grain: one row per user and queue · Dates: last_login_at only

ColumnWhat it holdsWhat you would use it for
queue_idThe queueComparing queues
user_idThe personThe category axis
nameTheir nameReadable labels
emailTheir email addressIdentifying them unambiguously
last_login_atThe last time they signed inFinding inactive accounts. The only date here
uploaded_docsDocuments they uploadedIntake per person
outstanding_docsDocuments still open in their nameCurrent workload
completed_docsDocuments they marked CompletedOutput per person
exported_docsDocuments they exportedExport activity per person
completed_docs_logCompletions counted from the review log rather than the document recordCross-checking the figure above
completion_time_secondsTotal time across the documents they completedThe numerator for a hand-built average
completion_time_docsHow many documents that total coversThe denominator for it
avg_time_hoursTheir average time from upload to completion, in hoursComparing turnaround between people
accuracyThe share of their extracted fields left uncorrectedQuality per person

Every figure except the last login is for all time, so a chart from this table shows lifetime totals whatever the Date filter says. For reviewer activity over a period, use analytics_review_logs.

You may also see analytics_user_activity_refresh and analytics_user_activity_source in the picker. They hold the same columns and rows as this table; use analytics_user_activity.

7.3 analytics_users

The people in your organisation.

Shape: per-record · Grain: one row per user · Dates: last_login_at

ColumnWhat it holdsWhat you would use it for
user_idTheir unique numberJoining to any table with a user_id
emailTheir email addressIdentifying them
first_nameTheir first nameReadable labels
last_nameTheir surnameReadable labels
last_login_atThe last time they signed inCounting active accounts, finding inactive ones

7.4 analytics_queue_members

Which people have access to which queues.

Shape: per-record · Grain: one row per user and queue · Dates: none

ColumnWhat it holdsWhat you would use it for
queue_idThe queueCounting people per queue
user_idThe personCounting queues per person

8. Queues, models and labels

8.1 analytics_queues

Your queues, and how each is configured.

Shape: per-record · Grain: one row per queue · Dates: none

ColumnWhat it holdsWhat you would use it for
queue_idIts unique numberJoining to anything with a queue_id
queue_nameIts nameReadable labels on any queue chart
doc_typeThe document type it handlesGrouping queues by what they process
model_idThe model it usesSeeing which model a queue relies on
use_created_modelTrue when it uses a model your organisation builtSeparating custom setups from predefined ones

8.2 analytics_models

The extraction models available to you.

Shape: per-record · Grain: one row per model · Dates: none

ColumnWhat it holdsWhat you would use it for
model_idIts unique numberJoining to anything with a model_id
model_nameIts nameReadable labels on any model chart
languageThe language it targets, such as en, multi or jaSplitting performance by language

8.3 analytics_labels

The labels defined in your organisation.

Shape: per-record · Grain: one row per label · Dates: created_at, deleted_at

ColumnWhat it holdsWhat you would use it for
label_idIts unique referenceJoining to assignments
nameThe label textReadable labels
colorIts colour in StapleDisplay only
typedefault or reconciliationSeparating ordinary labels from reconciliation ones
created_byWho created itAttribution
created_atWhen it was createdThe time axis
is_deletedTrue when it has been deletedExcluding retired labels
deleted_atWhen it was deletedTracking label changes over time

8.4 analytics_label_assignments

Every time a label was put on a document, and taken off again.

Shape: per-record · Grain: one row per assignment · Dates: tagged_at, untagged_at

ColumnWhat it holdsWhat you would use it for
assignment_idIts unique referenceCounting assignments
label_idWhich labelJoining to 8.3
label_nameThe label textReadable labels without a join
document_idThe document labelledCounting labelled documents
queue_idThe queueComparing queues
tagged_byWho applied it, where a person didManual against automatic attribution
sourceHow it was applied: rules, manual, vendor-master or datamapperMeasuring automation. How much labelling is rule-driven rather than by hand
tagged_atWhen it was appliedThe time axis
untagged_byWho removed itAttribution for removals
untagged_atWhen it was removedMeasuring how long labels stay on
is_activeTrue when the label is still on the documentRestricting to labels in force now

8.5 analytics_label_actions

The automated actions your labels trigger.

Shape: per-record · Grain: one row per action · Dates: created_at

ColumnWhat it holdsWhat you would use it for
action_idIts unique referenceCounting actions
label_idThe label that triggers itJoining to 8.3
label_nameThe label textReadable labels
action_typeWhat it does, such as move_documents_to_another_queue or trigger_webhookSeeing which automations you rely on
created_atWhen the action was set upThe time axis

9. Integrations

9.1 analytics_webhooks

The webhooks configured in your organisation.

Shape: per-record · Grain: one row per webhook · Dates: created_at

ColumnWhat it holdsWhat you would use it for
webhook_idIts unique referenceJoining to deliveries
nameIts nameReadable labels
urlWhere it posts toIdentifying the receiving system
is_activeTrue when it is switched onCounting live integrations against retired ones
created_byWho set it upAttribution
created_atWhen it was set upThe time axis

9.2 analytics_webhook_deliveries

Every webhook that fired.

Shape: per-record · Grain: one row per delivery · Dates: delivered_at

ColumnWhat it holdsWhat you would use it for
delivery_idIts unique referenceCounting deliveries
webhook_idWhich webhook firedComparing integrations
webhook_nameIts nameReadable labels without a join
event_idThe event that triggered itTracing one delivery
document_idThe document involvedJoining to the document
queue_idThe queueComparing queues
user_processedThe person involved, where there was oneAttribution
delivered_atWhen it firedDelivery volume over time

To tell integrations apart, use webhook_id or name.

9.3 analytics_concur_reports

Expense reports from SAP Concur, for organisations using that integration.

Shape: per-record · Grain: one row per report · Dates: report_created_at

ColumnWhat it holdsWhat you would use it for
report_idThe report’s referenceCounting reports
report_statusThe Concur status code: C, F or OPrefer derived_status in 9.4, which spells these out
error_codeThe Concur error, where the report failedGrouping failures by cause
rejection_remarkThe rejection textReading the reason on drill-through
employee_emailThe employee the report belongs toAttribution
employee_nameTheir nameReadable labels
employee_numberTheir staff numberJoining to your own HR data
expense_categoryThe category, such as Hotel or Airfare-InternationalSpend breakdown by category
transaction_amountThe amount claimedSum it for spend, or Average it for a typical claim
requires_mailingTrue when a physical copy is requiredCounting reports needing manual handling
queue_idThe queueComparing queues
report_created_atWhen the report was raisedThe time axis

9.4 analytics_concur_report_status

The same reports with the status codes translated into plain words.

Shape: per-record · Grain: one row per report · Dates: report_date

ColumnWhat it holdsWhat you would use it for
report_idThe report’s referenceCounting reports
queue_idThe queueComparing queues
report_dateThe day the report was raisedThe time axis
report_statusThe Concur codeCross-referencing with Concur itself
error_codeThe Concur errorGrouping failures by cause
rejection_remarkThe rejection textReading the reason on drill-through
employee_emailThe employeeAttribution
derived_statusApproved, Rejected, Unexpectedly Rejected or OpenThe status column to chart. Unexpectedly Rejected marks a rejection whose code is not one of the known business reasons, which is usually worth a closer look
requires_mailingTrue when a physical copy is requiredCounting reports needing manual handling

9.5 analytics_concur_invoices

Invoices from Concur, with their verification and duplicate outcomes.

Shape: per-record · Grain: one row per invoice · Dates: invoice_created_at

ColumnWhat it holdsWhat you would use it for
invoice_idThe invoice referenceCounting invoices
report_idThe report it belongs toJoining to 9.3 and 9.4
invoice_typeThe kind of invoice, such as Electronic Fapiao or Malaysia e-InvoiceSplitting by regulatory type
vendorThe supplierSpend or volume by vendor
verification_statusVerified or FailedVerification pass rate
duplicate_statusUnique or DuplicateMeasuring duplicate submissions
queue_idThe queueComparing queues
invoice_created_atWhen the invoice was raisedThe time axis

10. Value reference

The values you will meet most often when filtering.

Document status (status on analytics_documents)

ValueMeaning
RECEIVEDArrived and scanned, waiting for review
PROCESSINGBeing scanned now
UPLOADEDAccepted but not yet in a queue
COMPLETEDReviewed and approved, not yet exported
EXPORTEDSent to the destination system
EXPORT_FAILEDExport was attempted and did not go through
REJECTEDTurned away during review
REMOVEDDeleted
SPLITTEDSplit into separate documents
DUPLICATEAlready seen. Most duplicates are marked in error_message rather than here

Ingestion channel (uploaded_from): email, API, UI, plus_email, dropbox, drive, erp, peppol and other connected systems.

Export format (exported_type and export_type): XML, CSV, JSON, TXT, CONCUR, XERO, PEPPOL, SAP4HANA, IRAS, REDACTED_PDF, MATCHING, WEBHOOK.

Document type (doc_type): INVOICE, RECEIPT, PURCHASEORDER, BANKSTAT, PASSPORT, NRIC and the regional invoice variants such as INDIANINVOICE, USINVOICE, EMEAINVOICE, FAPIAOINVOICE. A blank value means the document never reached classification.


11. Good to know

  • Only tables with a date column respond to the Date filter. Each entry above states its dates. Where it says Dates: none, the figures cover all time.
  • Counting rows is not always counting documents. In analytics_document_fields, analytics_field_differentials, analytics_export_logs and analytics_review_logs, one document produces many rows. Use Number of distinct values on document_id when you mean documents.
  • Generated documents are excluded from most tables. Documents Staple created rather than you uploading them are left out of most summaries. analytics_documents keeps them, flagged by created_by_supernova.
  • Everything here is reachable through the question builder, including calculations, using Custom column and Custom expression. See Building a chart yourself.