Ask a financial operations team where the real work happens and the answer is rarely a dashboard with a clean API behind it. It's a vendor portal for matching an invoice against a purchase order, a banking site for pulling a statement, a payer or trading-partner portal for chasing a reconciliation break. These are the screens finance teams have always worked in, and for most of them, an API integration was never built—and isn't coming. That's the gap a "digital coworker" is meant to close: not another script that scrapes a page and hopes the layout doesn't change, but an AI agent that operates a real, authenticated browser session the way an analyst would, and does it reliably enough to run unattended.
Why Financial Back-Office Work Resists APIs
Reconciliation, accounts payable, and vendor-portal work sit on top of systems that were built for a person clicking through a form, not a machine calling an endpoint. A vendor portal might expose a read-only status API while the actual invoice submission, dispute, or payment confirmation still requires logging in and clicking through the same screens a human uses. A legacy core-banking UI might have no API surface at all. And in a lot of these workflows, the screen itself—the confirmation page, the submitted form, the reconciled balance—is what a controller or auditor expects to see, not a JSON blob asserting that something happened.
That leaves the browser as the only viable integration point. But automation that logs into a vendor portal and initiates a payment, or reconciles a trade break against a counterparty's system, has to behave like production finance infrastructure—not a brittle scraper that happens to work until the next UI change.
What a Digital Coworker Looks Like in Practice
Three things separate an automation a finance team can actually rely on from one that quietly becomes a liability.
Credentials the automation never touches directly. Vendor and banking portals sit behind logins, and hardcoding a service account's password into a script is how credentials end up in logs and version history. Anchor's identities let you define a portal's login once and attach a stored identity to a session instead:
const session = await anchorClient.sessions.create({
identities: [{ id: "ap-vendor-portal-identity" }],
session: {
recording: { active: true },
},
});
// Session starts already authenticated against the vendor
// portal; the raw credential never passes through the script.A record of what actually happened on screen. Session recording is on by default and captures the run as video—independent evidence for when the question isn't "did the job return success" but "what did the portal actually show when that invoice was matched." That matters when a reconciliation exception surfaces three weeks later and someone needs to see the original run, not just a log line.
A human who can watch without taking the wheel. For higher-stakes runs—initiating a payment, closing out a reconciliation break—a finance controller often wants to watch the session live without being able to interfere with it. Anchor's live view can be embedded read-only, giving a reviewer a real-time window into the agent's screen while it works.
Coworker, Not Script
The distinction matters: a scraper is disposable and stateless by design. A digital coworker for financial operations is meant to run the same authenticated workflow every day, leave an audit trail behind it, and be governed the way any other member of the finance team would be—not a black box that occasionally breaks and no one notices until month-end.
If your team is still moving invoices, reconciliations, or vendor-portal work through manual screens, that's exactly the workload Anchor's finance automation is built to take on. Get an API key and put the next manual reconciliation run behind a governed, auditable session instead of a person's mouse.
