TWO WEBSITES + EXCEL

Reconcile Records from Two Websites into Excel

Compare two systems without copying both tables by hand, while keeping every source field and reconciliation rule inspectable.

WHAT THE AI WILL BUILD

A real visual workflow, not a conceptual diagram.

The AI guide supplies a precise goal, safe target page, inputs, output contract, and verification rules. Paste that prompt into Runavelo's built-in assistant, then inspect and edit every generated command before execution.

  • Open two independent source pages and collect each visible record through documented CSS selectors.
  • Join the source maps by record ID rather than assuming both tables have the same order.
  • Classify matches, amount mismatches, status mismatches, and records present in only one source.
  • Write all records and their comparison outcome to a local Excel report.

Responsible use: adapt this pattern only for systems and data you are authorized to automate.

WORKFLOW WALKTHROUGH

How the visual workflow operates.

Each stage has a specific input, browser context, output, and verification point. Edit these commands directly when the destination system differs.

Open both sources

The application opens the two resettable source pages and stores a distinct webpage object for each one.

Collect source A by row

A count loop builds row-specific CSS selectors, reads ID, customer, amount, and status, then stores each record in a map keyed by ID.

Collect source B independently

A second loop repeats the same explicit extraction against source B. Source order does not affect the later join.

Join and classify every key

The deterministic comparison walks the union of both ID sets and applies a clear priority: missing side, amount mismatch, status mismatch, then match.

Create the exception report

The combined rows are written to Excel in the current user Documents directory, both browser pages are closed, and the output path is logged.

EXPECTED OUTPUT

Evidence you can inspect after the run.

  • A workbook named two-website-reconciliation.xlsx in Documents\Runavelo Demo Results.
  • Two matching rows, one amount mismatch, one status mismatch, one source-A-only row, and one source-B-only row.
  • A final runtime log containing the complete workbook path.
  • Runavelo's runtime log connects the visible workflow line to its result. That makes missing elements, rejected updates, and unexpected page states easier to locate than a generic success message.

COMMON QUESTIONS

What to change for a real workflow.

What if values use different formats?

Normalize authorized source values before comparison—for example, parse currency to a decimal and map equivalent status labels—then keep the raw values in separate report columns.

Can one source be an API or spreadsheet?

Yes. Replace either browser collection block with an API or spreadsheet input while preserving the keyed maps and deterministic comparison rules.

TRY THE COMPLETE AI PATH

Copy the goal, let AI build, then inspect and run.

The prompt targets the matching test page and states the expected evidence. A reference QYA remains available for comparison with a verified implementation.