Scheduled report reconciliation
Stop rebuilding the same report by hand every month
Vector Index AI reconciles two recurring exports into one checked report your team can run again next cycle. You get five agreed metrics, traceable records and a list of every mismatch that still needs a decision.
$1,000 for the first project. Delivered in 10 business days after complete inputs and payment.
Two CSV or XLSX exports, up to 2,000 rows combined. No connection to your live systems.
Start with one email explaining what the report needs to show and how often you need it. Redacted samples of the two exports help. We confirm fit and agree the five metrics, handling rules and fixed scope before sending the payment link. If delivery still doesn't match that written scope after the correction round, you receive a full refund.
Get next month's report out of this month's work
When the same two exports arrive each cycle, matching them by hand means repeating the same decisions: which records belong together, which source wins and where the totals came from.
Your team decides what the five metrics mean and which source takes precedence. We build the matching rules, reconciled dataset, report, exception register and checks, then provide the instructions for another run.
The $1,000 project gives you a completed reporting workflow built around those agreed decisions. Your team can use it with the same file structure and definitions, or commission a later run for $300.
This fits operations consultancies, implementation agencies and service businesses that rebuild the same report by hand from recurring exports, with one person who can approve the rules. Project status from one tool and hours from another is one example.
Synthetic demonstration, fictional data, not a client result
See what happens to the rows that don't match
The example uses project-status and time exports with deliberate problems. An unknown project ID stays in total hours and is flagged for review. A blank project ID is also retained. A duplicated time entry is counted once, with the removal recorded.
Before: the two exports as they arrived, with the planted problems highlighted.
After: one report with five metrics, each checked against a second calculation, and every input row accounted for.
Invented data with problems planted on purpose. It is not a client result. Click either image to see it full size, or read how each problem was handled below.
What your $1,000 project includes
| Deliverable | What it gives your team |
|---|---|
| One reusable report with five agreed metrics | A defined report to produce again next cycle. |
| Reconciled dataset | A record of how every input row was handled. |
| Exception register | Each unmatched or unresolved record, with the decision it needs from your approver. |
| Change log | Every edit and the rule behind it. Your original files remain unchanged. |
| Visible checks | Reconciled row counts and totals, plus a rerun on fresh input to check repeatability. |
| Repeat-run instructions | The ability to produce the same report again yourselves or ask us to run it. |
| One consolidated correction round | One place to return the team's corrections against the agreed scope. |
A missing fact is listed for a decision. It is never guessed or silently removed to make a report look complete.
Agree the rules, then let us build the report
- Send two CSV or XLSX exports, up to 2,000 rows combined, with the purpose and frequency of the report.
- Agree five metrics and the handling rules. Tell us which source wins when records disagree, provide expected totals where available and name one approver for unresolved records.
- Approve the written scope and pay $1,000. Payment is in full before work starts. The 10-business-day delivery period begins when inputs and payment are complete.
- Review the report and its checks. Return one consolidated correction round and use the instructions for the next run.
Keep running it yourselves, or have us handle the next cycle
You receive the repeat-run instructions. After the initial project is delivered, you can have Vector Index AI run the approved workflow again for $300 per later run, in an agreed delivery slot.
That covers the same file structure, the same metrics, the same 2,000-row limit and one correction round. A second report, changed source or new business definition needs its own fixed quote.
$1,000
For the first project: the rules, the checks and the first report.
$300 for each later run of the same approved workflow, with the same file structure, the same 2,000-row limit, the same metrics and one correction round. Later-run dates are agreed separately.
Paid in full, in one payment, before work starts. We send the payment link once the scope is agreed in writing.
Money-back guarantee: If delivery doesn't match the scope agreed in writing, even after the correction round, you get a full refund.
Lead time: 10 business days after we have complete inputs and payment.
Questions before you send the files
Do you need access to our CRM or ERP?
No. We work from your exports. Writing to a live ERP or CRM and maintaining an API connection are outside this service.
What if the two files disagree?
We apply the source and handling rules you approve. Records we cannot resolve are listed for your approver, with the decision needed. They are not silently discarded.
Is this accounting sign-off?
No. The service does not include bookkeeping sign-off, accounting assurance, tax or legal advice, or sensitive regulated records.
Can the report change later?
A second report, changed source or new definition is a separately scoped project. The $300 repeat price covers running the same approved workflow again.
Synthetic example, fictional data
How each problem was handled
This example (download the files) was built on invented data for a fictional consultancy: a project status export with 40 projects and a time export with 300 rows for August 2026. Problems were planted in the files on purpose. Here is how each one was surfaced.
| Planted problem | What the report did |
|---|---|
| The same time entry appears twice | One copy removed, logged in the change log with the rule that removed it. The hours are counted once. |
| 4.00 hours charged to a project ID that is not in the status export | Kept in total hours, listed as unmatched, with the question: a new project or a mistyped ID? |
| 2.50 hours with no project ID at all | Kept in total hours, listed as a missing key, asking which project it belongs to. |
| A project marked Complete on 14 August, with 4.50 hours logged against it on 19 and 26 August | Counted as neither open nor completed. Flagged as a conflicting status for the approver to decide. |
| Status spelled two ways | Normalised by a stated rule, and each change logged. |
The report showed 24 open projects, 15 completed, 1,019.25 recorded hours, 6.50 unmatched hours and 1 unresolved status record. A second script worked out the same five figures a different way before the report was built, and the report is not written if the two disagree.
A fresh September pair of files then ran through the same code with no edits. An October file with the hours column renamed stopped the run: it named the missing column and wrote nothing, rather than producing a plausible report from the wrong input.
That demonstrates how the checks handle these test cases. It is not a claim about savings or results achieved for a client.
Have the next report built on agreed rules
Send a redacted sample of each export, the report's purpose and how often you need it. We'll confirm fit and put the scope in writing before asking you to pay.
$1,000 for the first project, delivered in 10 business days after complete inputs and payment. Later-run dates are agreed separately.
Or email [email protected].
All services · Supplier file preparation · Campaign variations