Help with the bill check.

How a check runs, what you need, where to get each file, and what to do if one is not read.

How a check runs

Seconds with Fin’s export alone; about five minutes for the whole check once you have your invoice.

Fin’s export first. In seconds, the checker says what the export records: how many of its resolutions are recorded as confirmed by the customer and how many as assumed, the procedure handoffs, and the workspace it names. No export yet? Start with the invoice, and add the export when it comes.
The invoice. Choose its PDF, paste its text, give a CSV or type its lines. The checker shows the lines it read for you to confirm, and stores nothing until they add up to the invoice’s total.
Your terms. One question: do you pay Fin’s published prices? Yes sets them. No opens a short form, which can read your order form’s PDF and shows each term with the line it came from.
The result. What differs from your contract comes first, with the email to Fin drafted for you to send. What could not be checked, the renewal figures and the calculation are each a click away. Download your record to carry it into next month.

Try it on the sample first, a fictional company with simulated data. What Fin bills as an outcome, in Fin’s own words: Ten Fin billing rules.

What you need

This month’s invoice. Its PDF, its text, a CSV, or its lines typed.
Your billing terms. If you pay Fin’s published prices, one answer sets them. If not, your order form, as a PDF or its text, or its price per resolution, any fixed fee and included outcomes, and your workspace ID.
Fin’s export, for the deeper checks. Where to get it, for your setup.
The outcomes total, if you have it. What it is.
Last month’s record, from your second check on.

Get Fin’s export

Take it on the invoice date or within two days after it. The export keeps each conversation’s latest state, so one taken weeks later can count differently from the invoice. Several files are read as one list.

Fin on Intercom

In Intercom, open Reports, then Dataset export. It needs the “Can access Chart drill-in” and “Can export CSV” permissions, which an Intercom admin can give you. The checker has a request ready to copy for your admin.
Choose the Conversations dataset.
Set the dates to cover your invoice’s billing period, as printed on the invoice. From your second check on, your last result names the dates to cover: from seven days before the oldest period still watched, so deductions can be followed.
Export it as CSV. Up to 10,000 rows it downloads straight away; above that, Intercom emails you a link, which can take up to an hour.

Fin with Zendesk, Salesforce or another helpdesk

In Fin’s reports for your helpdesk, export Fin’s conversations as CSV, covering your invoice’s billing period. The checker needs each conversation’s ID, its date, Fin’s resolution state and whether Fin took part, and asks if a column goes by another name.

Fin in Zendesk, counted from Zendesk’s tags

In Zendesk’s Admin Center, open Account, then Tools, Reports, and its Export tab. It needs a Zendesk admin on a plan above Team, and data exports stay off until the account owner asks Zendesk Customer Support to turn them on.
Choose CSV export, with dates from the first day of your invoice’s billing period, as printed on the invoice, to today: Zendesk picks tickets by their last update.
Zendesk emails you a link to a zip file, from a few minutes to a day or more later. Unzip it and choose its CSV files.

A view’s CSV will not do: a view cannot show tags. The checker reads each ticket’s ID, when it was created, and its tags. Fin tags each ticket it resolves fin-soft-resolution, or fin-hard-resolution once the customer confirms.

The outcomes total

Fin’s own “Fin AI Agent outcomes” total for the invoice’s billing period, from Fin’s reports. Type it in when the checker asks. It is optional: without it, the check compares the invoice with the export alone.

Next month

After each check, download your record and keep it with your billing records. Next month, open it on the checker with the new invoice and export. It carries the open questions, the deductions still being watched and what you recorded about Fin’s replies, and follows what is still open.

It names conversations by their ID and holds your contract’s prices, so do not send it to anyone. Or tick “Remember my record”, and this browser keeps it, on this computer only, until you untick it. You can also add a reminder to your calendar.

Supported formats and checks

Each format below was tested on simulated data so far. Your files may be among the first real ones the checker reads, and each result says what could not be checked.

What it reads

Invoice, as a PDF: A PDF with text in it, read in your browser; you confirm the lines it reads. A scanned PDF has no text to read: type its lines instead.
Invoice, as pasted text: The PDF’s text, pasted. The checker proposes the lines and sets the subtotal, tax and total aside.
Invoice, as a CSV: One row per invoice line, in the checker’s columns. The checker page has a template to download.
Invoice, as typed lines: Its number and dates, and each line’s quantity, unit price and amount, in US dollars.
Order form, as a PDF or pasted text: Read for the price per resolution and per procedure handoff, a fixed fee and included outcomes, the overage price, workspace IDs, payment days, and the term’s end and notice period, each shown with the line it came from. A term it cannot read plainly, such as a price in another currency, a discount or a yearly fee, is left for you to enter.
Intercom’s Conversations export (CSV): Each conversation’s ID, when it was created, Fin’s resolution state, whether Fin took part, its tags and its workspace; and, where the export has them, where it came from, its state, who wrote first, whether the customer replied and whether it was merged. Every other column is left unread and named, and what a customer wrote is never read.
Fin’s export on another helpdesk (CSV): Read as Intercom’s export is.
Zendesk’s ticket export (CSV): Each ticket’s ID, when it was created, and its tags. The requester’s name and email, and every other column, are left unread.
The outcomes total: A number you type.
Your record (JSON): The file you downloaded after your last check.

What it checks

The invoice against your terms: its line arithmetic and total; its number and billing period; its prices, including tiers, a fixed or base fee, outcomes included, a minimum charge, your commitment’s balance, overage, prorated charges and price rises; pooled workspaces; credits due; late fees; and its currency.
With Fin’s export: the invoice’s count against Fin’s own list, and against Fin’s outcomes total if you typed it; conversations listed twice; and which conversations it charges: assumed and confirmed resolutions, procedure handoffs, conversations your team tagged as spam or test and, where the export has the column, previews, conversations routed to spam, merged conversations and messages your team sent that got no reply.
Across months, with your record: the deductions Fin’s rule promises when a customer comes back to the same conversation, followed into later invoices for 90 days after each billing period ends.
Not checked: teammate replies, requests for a person and returns in another channel, which need the conversations themselves; and whether Fin’s answers were right.

Which checks run depends on the files and columns you give. Each result names any check that could not run, and what it needs.

Privacy and limits

The checker runs in your browser, and nothing is uploaded: its page allows no network connection.
It reads only the columns it needs, never what a customer wrote, and keeps nothing once you leave unless you tick “Remember my record”.
It is not an audit, legal advice or accounting advice, and it does not dispute your invoice. The questions are yours to send or not.
ScopeBlind is not affiliated with Fin, Intercom or Salesforce. Fin and Intercom are trademarks of their owners.

The engine file and how to check its hash are in the technical reference. How the page handles files is on Security.

If a file is not read

The checker says what it could not read, and why. The usual causes:

A scanned PDF.: It has no text to read. Type the invoice’s lines instead.
A different export.: For Fin on Intercom, use the Conversations dataset from Reports, then Dataset export. For Fin in Zendesk, use Zendesk’s ticket export, not a view’s CSV.
A column under another name.: The checker asks which column holds what it needs.
A file dropped in the other place.: It is read where it belongs, and the page says where it went.
Lines that do not add up.: Nothing is stored until the invoice’s lines add up to its total. Check each quantity and amount against the invoice.

Still not read? The checker offers a note for us, which you send only if you choose. It holds the file’s name, size, column names and number of lines, and what the checker said, but no rows. A file with no header row would put its first row where the column names go, so read the note first and remove anything you would not share.

Contact support

Write to support@scopeblind.com. Say which setup you use and what the checker said. Do not attach an export or your record: they name your customers’ conversations.

Rather have someone run it with you? Assisted review: US$500, fixed, for up to three months of bills.

Check your bill Technical reference