ABN AMRO Access Online

The business challenge

ABN AMRO needed an integrated financial workstation for corporate customers. Treasury teams needed to monitor payments and carry out banking work in a browser while retaining the familiar navigation and structured views of desktop tools.

Delivery across London and Amsterdam

The most difficult part of the project was coordinating delivery across London and Amsterdam. Frontend development depended on integration decisions and infrastructure readiness, with work and responsibilities spread across both locations.

When coordination broke down, the effects appeared in the engineering work. A frontend team could complete a worksheet or tab and still depend on another team’s decisions, integration work, or environment readiness before it could validate the experience end to end.

The architecture decisions

Use a familiar working model

We built a JavaScript frontend around spreadsheet-style worksheets, tabs, and structured financial views. That interaction model gave corporate users a familiar way to move between related tasks in the browser.

Integrate with the banking platform

The workstation needed to present a coherent experience across services with different underlying systems and operational dependencies. The frontend, service integrations, and supporting infrastructure had to come together for the customer workflow to work.

The project contribution

Our team developed the spreadsheet-style JavaScript frontend and contributed to establishing Access Online. The firsthand account describes the interface we built. Public evidence for project-specific adoption, performance, and productivity figures remains unavailable.

Historical platform milestones

2005

ABN AMRO introduced Access Online in the Netherlands as a global internet banking service for large corporate customers. ABN AMRO’s quarterly filing

2007

Online Client Service provided round-the-clock access to real-time balances and transactions through Access Online. The Banker

2009

ABN AMRO and RBS announced that customers would be able to manage accounts at both banks through Access Online. Joint announcement (PDF)

These milestones describe the platform’s evolution across several years. The sources describe service capabilities at each point in time.

The practical lesson

Technical architecture and delivery organisation are interdependent.

Looking back through the lens of Policy vs Detail, the integrated financial workstation was the business requirement. The worksheet interface, service integrations, and infrastructure were the engineering choices and dependencies that made it possible.

For a cross-team project, give each critical dependency an owner, agree when the integration environment must be ready, and validate one complete customer workflow early. That exposes coordination problems while the teams can still resolve them.