Data with Sachin

What Does SOA Mean? Service-Oriented Architecture, Statement of Account and SOA Records

SOA has several meanings

In this article
  1. Quick reference: what does SOA stand for?
  2. SOA in software: service-oriented architecture
  3. SOA vs microservices vs APIs
  4. SOA in finance: statement of account
  5. SOA in DNS: the SOA record
  6. Frequently asked questions

SOA most commonly stands for service-oriented architecture, a way of designing software as a collection of reusable services that communicate over a network. In finance, SOA means statement of account, a summary of transactions and the balance owed. In networking, an SOA record (start of authority) is a DNS record holding key information about a domain's zone. The right meaning depends on context.

Because "SOA" means different things to developers, accountants and network administrators, this guide covers each meaning clearly, with the most attention on service-oriented architecture, which matters for anyone working on systems integration and automation.

Quick reference: what does SOA stand for?

ContextSOA meansIn one line
Software / IT architectureService-oriented architectureBuilding systems from reusable, loosely coupled services
Finance / accountingStatement of accountA summary of invoices, payments and the balance owed
DNS / networkingStart of authority (SOA record)A DNS record with authoritative information about a domain's zone
Actuarial professionSociety of ActuariesProfessional body for actuaries
Cybersecurity / complianceStatement of applicability (ISO/IEC 27001)Lists which security controls apply and why

SOA in software: service-oriented architecture

What is SOA?

Service-oriented architecture (SOA) is a software design approach in which an application's functions are provided as services: self-contained units of business functionality (such as "check customer credit", "create invoice", "get order status") that other applications can call over a network through standard interfaces.

Instead of one large application where everything is tightly connected, SOA breaks functionality into reusable services that different systems can share.

Core principles of SOA

  • Loose coupling: services depend on each other as little as possible.
  • Reusability: one service (e.g., "customer lookup") serves many applications.
  • Standardised contracts: each service has a defined interface describing what it does, its inputs and outputs.
  • Abstraction: consumers don't need to know how the service works internally.
  • Interoperability: services built on different technologies can communicate.
  • Discoverability: services are documented and registered so they can be found and reused.
  • Composability: services can be combined into larger business processes.

How SOA works

Traditionally, SOA implementations used:

  • Web services with SOAP (an XML-based messaging protocol) and WSDL (a language describing service interfaces)
  • An enterprise service bus (ESB): middleware that routes messages between services, transforms data formats and handles integration logic
  • Service registries for discovery
  • Orchestration engines (e.g., BPEL) to combine services into business processes

Example

A bank builds services for customer information, account balance, credit scoring, payments and notifications. The mobile app, the website, the call-centre system and the loan origination system all reuse the same services, rather than each building its own version. When the credit-scoring logic changes, it changes in one place.

Benefits of SOA

  • Reuse of business functions across applications
  • Easier integration of different and legacy systems
  • Faster development of new applications by assembling services
  • Alignment between business capabilities and IT
  • Easier maintenance when functionality is centralised

Drawbacks of SOA

  • Centralised ESBs can become complex bottlenecks and single points of failure
  • Heavy standards (SOAP/WSDL) add overhead
  • Governance and coordination across teams can slow change
  • Large shared services can still create tight dependencies

SOA vs microservices vs APIs

SOA's ideas evolved into today's microservices and API-first approaches.

SOAMicroservices
ScopeEnterprise-wide integration and reuseBuilding a single application as many small services
Service sizeOften larger, shared business servicesSmall, focused on one capability
CommunicationOften via an ESB; SOAP/XML commonLightweight APIs (REST/JSON, gRPC), messaging/events
DataServices may share databasesEach service typically owns its own data
GovernanceCentralisedDecentralised, team-owned
DeploymentOften coordinatedIndependently deployable services, containers

APIs are the interfaces through which services (SOA or microservices) are accessed. Today, REST and GraphQL APIs, event streaming (Kafka) and webhooks (see What is a webhook?) have largely replaced SOAP and ESBs for new systems, but the SOA principles of reusable, well-defined services remain foundational.

Why SOA matters for automation and AI

Well-designed services and APIs make automation dramatically easier. Workflow tools, RPA, and AI agents can call clean services ("create order", "check stock") instead of scraping screens. In fact, exposing business capabilities as tools for AI agents (often via the Model Context Protocol) is essentially SOA thinking applied to AI. (See What is AI orchestration?, What is robotic process automation? and What is CRM integration?.)

Platform as a service (PaaS) is a cloud model where a provider offers a managed platform (runtime, databases, middleware, scaling) for building and running applications, so developers don't manage servers. Examples include Heroku, Google App Engine, Azure App Service and many managed integration platforms (iPaaS, integration platform as a service, such as MuleSoft, Boomi and Workato), which are often used to implement modern SOA-style integration.

SOA in finance: statement of account

What is a statement of account?

A statement of account (SOA) is a document a business sends to a customer summarising their account activity over a period: invoices issued, payments received, credits applied and the outstanding balance. It's usually sent monthly.

What's on an SOA?

  • Customer name and account number
  • Statement period
  • Opening balance
  • List of invoices (dates, numbers, amounts)
  • Payments and credit notes received
  • Closing balance due
  • Ageing breakdown (current, 30, 60, 90+ days overdue)
  • Payment terms and instructions

Statement of account vs invoice

An invoice requests payment for a specific sale. A statement of account summarises all invoices and payments over time, showing what's still owed.

Automating statements of account

Accounting systems (QuickBooks, Xero, Zoho Books, NetSuite, SAP) can generate and email statements automatically. Automation can also send reminders for overdue balances and reconcile payments. (See What are automated financial systems?)

SOA in DNS: the SOA record

What is an SOA record?

A start of authority (SOA) record is a DNS record that every DNS zone must have. It contains administrative information about the zone, identifying the primary authoritative name server and controlling how secondary servers sync zone data.

Fields in an SOA record

FieldMeaning
MNAMEPrimary name server for the zone
RNAMEEmail of the administrator (with the @ written as a dot)
SerialVersion number of the zone; increases with each change
RefreshHow often secondary servers check for updates
RetryHow long to wait before retrying a failed refresh
ExpireWhen secondaries stop answering if they can't reach the primary
Minimum / negative TTLHow long resolvers cache "no such record" responses

Example

example.com.  3600  IN  SOA  ns1.example.com. admin.example.com. (
              2026111201 ; serial
              7200       ; refresh
              3600       ; retry
              1209600    ; expire
              3600 )     ; minimum TTL

You can view a domain's SOA record with dig SOA example.com or nslookup -type=soa example.com. Most people never need to edit it; DNS providers manage it automatically.

Frequently asked questions

What does SOA mean?

SOA most commonly means service-oriented architecture, a software design approach based on reusable services. In finance it means statement of account, and in DNS it refers to the start of authority record. Other meanings depend on context.

What is SOA in software?

Service-oriented architecture is a way of designing software systems as a set of loosely coupled, reusable services with standard interfaces that other applications can call over a network, often coordinated through an enterprise service bus.

What is the difference between SOA and microservices?

SOA focuses on enterprise-wide integration and reuse of often larger services, typically via centralised middleware. Microservices break a single application into small, independently deployable services that own their data and communicate through lightweight APIs.

What is a statement of account?

A statement of account is a document sent to a customer summarising invoices, payments and credits over a period and showing the outstanding balance, usually with an ageing breakdown.

What is an SOA record in DNS?

An SOA (start of authority) record is a required DNS record that identifies a zone's primary name server and administrator and contains timing values that control how zone data is synchronised and cached.

What is a statement of applicability (SoA) in ISO 27001?

In ISO/IEC 27001, the statement of applicability is a document listing the information security controls an organisation has selected, whether each is implemented, and the justification for including or excluding each control.

Want this built for your business?

I design and build AI agents and automations that run in production, not just in demos. Tell me which process is eating your team's week.

Start a conversation
Sachin Rawat

Written by Sachin Rawat

AI & automation engineer · websites, apps and motion design

I build AI agents, automations, websites, apps and motion design for businesses. These guides answer the questions people actually search, written from hands-on experience building them.

Work with meMore stories

More from Sachin Rawat

Sachin Rawat

How to Manage Daycare Communication With Parents (Apps, Daily Reports, Policies and Automation)

How to manage daycare and childcare communication: set communication policies, use a parent app for daily reports, photos and messages, check-in/out and billing, newsletters, handling incidents and sensitive conversations, staff communication, privacy and consent, and automating reminders and updates.

2 min read · Nov 13, 2026
Sachin Rawat

What Tools Do Accountants Use? Accounting Technology Stack for Firms in 2026 (Software, AI and Automation)

What tools and software accountants and accounting firms use: cloud accounting (QuickBooks, Xero), tax software, practice management, document portals and e-signatures, payroll, receipt capture, spreadsheets and BI, payments, AI and automation tools, plus what accounting technology means and how to choose a stack.

2 min read · Nov 12, 2026
Sachin Rawat

When to Suppress Inactive Email Subscribers to Protect Deliverability (Sunset Policy Guide)

When and how to suppress inactive email subscribers: how inactivity hurts deliverability and sender reputation, defining inactive (by clicks, opens, purchases), typical suppression timelines (90–180+ days), re-engagement campaigns, sunset policies, Apple Mail Privacy Protection, Gmail and Yahoo sender requirements, list hygiene, and automating suppression.

4 min read · Nov 12, 2026
Sachin Rawat

How to Create an Email Template in Outlook (New Outlook, Classic, Web and Mac) and Automate Replies

How to make and save email templates in Outlook: My Templates in new Outlook and Outlook on the web, .oft templates in classic Outlook for Windows, Quick Parts, templates on Mac, how to use and edit templates, sharing templates with a team, and how to automate emails with rules, Power Automate and AI.

3 min read · Nov 12, 2026