Glossary

Service Received Note (SRN)

P

Paras

16 JUL 2026 · Updated 2 NOV · 4 min read

What is a Service Received Note (SRN)?

A Service Received Note (SRN) is a document that confirms a service has been successfully delivered and accepted by the customer or the requesting department. It acts as formal evidence that the agreed service was completed according to the purchase order or contract terms.

Unlike a Goods Receipt Note (GRN), which is issued when physical goods are received, an SRN is used for intangible services such as maintenance, consulting, security, transportation, software implementation, facility management, or professional services.

For example, a company hires an IT vendor to install networking equipment across its offices. After the installation is completed and verified, the IT department issues an SRN confirming that the service has been delivered as agreed. The finance team then uses the SRN to process the vendor’s invoice.

SRNs are commonly used in Accounts Payable (AP) processes to ensure businesses pay only for services that have actually been received.

How Does the SRN Process Work?

The Service Received Note is typically created after the service has been completed and verified.

A standard process looks like this:

  1. 1

    Purchase Order Created

  2. 2

    Vendor Delivers Service

  3. 3

    Service Verification

  4. 4

    SRN Generated

  5. 5

    Invoice Verification

  6. 6

    Payment Approval

The SRN acts as confirmation that the organization has accepted the completed work before payment is released.

Information Included in an SRN

A typical Service Received Note contains details such as:

  • SRN number
  • Service description
  • Purchase Order number
  • Vendor name
  • Department receiving the service
  • Date of service completion
  • Service period
  • Quantity or hours (if applicable)
  • Name of the approving employee
  • Remarks or observations

These details help finance teams verify invoices and maintain an audit trail.

Example of a Service Received Note

A company hires a facility management vendor for office maintenance.

Particular

Details

Purchase Order

PO-4587

Vendor

ABC Facility Services

Service

Monthly Office Maintenance

Service Date

30 June 2026

Status

Verified and Accepted

SRN

Generated

Once the SRN is approved, the Accounts Payable team verifies the vendor’s invoice and schedules payment according to the agreed payment terms.

Why is an SRN Important?

Unlike physical goods, services cannot usually be counted or inspected after delivery. An SRN provides documented confirmation that the work has been completed before payment is made.

It helps businesses:

  • Verify service completion.
  • Prevent payments for incomplete work.
  • Support invoice verification.
  • Improve procurement controls.
  • Maintain an audit trail.
  • Reduce payment disputes.
  • Strengthen vendor accountability.

Without an SRN, organizations may process invoices without sufficient evidence that the contracted service was actually delivered.

SRN vs. Goods Receipt Note (GRN)

Although both documents confirm receipt, they apply to different types of purchases.

Service Received Note (SRN)

Goods Receipt Note (GRN)

Used for services

Used for physical goods

Confirms service completion

Confirms receipt of products

Common for consulting, maintenance, logistics, and professional services

Common for inventory, raw materials, and equipment

Supports service invoice verification

Supports goods invoice verification

Both documents play a critical role in the Procure-to-Pay (P2P) process but are used in different purchasing scenarios.

Common Challenges

Managing Service Received Notes manually can create several operational issues.

Some common challenges include:

  • Delayed service confirmation.
  • Missing approvals.
  • Incomplete service documentation.
  • Invoice processing delays.
  • Disputes over service completion.
  • Paper-based records.
  • Poor visibility into pending SRNs.

These issues often slow down vendor payments and increase manual effort for procurement and finance teams.

Best Practices

Organizations can improve SRN management by:

  • Issuing SRNs immediately after service verification.
  • Clearly defining service acceptance criteria.
  • Digitizing approval workflows.
  • Linking SRNs with purchase orders and invoices.
  • Maintaining complete supporting documentation.
  • Reviewing pending SRNs regularly.
  • Standardizing the service acceptance process across departments.

A structured SRN process reduces payment delays and improves financial controls.

How Technology Improves SRN Management

Modern Procure-to-Pay (P2P) platforms automate the creation and approval of Service Received Notes.

These systems can:

  • Generate SRNs digitally.
  • Route approvals automatically.
  • Link SRNs with purchase orders and invoices.
  • Support two-way or three-way invoice verification.
  • Track pending service confirmations.
  • Maintain complete audit trails.
  • Provide real-time visibility into service procurement.

Automation reduces manual paperwork while ensuring vendor payments are released only after services have been properly verified.

Frequently Asked Questions

Question 01

Is an SRN mandatory for every service purchase?

Not always. The requirement depends on the organization’s procurement policies and the type of service. However, businesses commonly use SRNs for high-value, recurring, or contract-based services to ensure proper verification before payment.

Question 02

Who prepares a Service Received Note?

The department that requested or received the service typically prepares or approves the SRN after confirming that the work has been completed according to the agreed scope and quality standards.

Question 03

Can an invoice be processed without an SRN?

Some organizations may allow it for low-value or routine services. However, many businesses require an approved SRN before processing payment, particularly for services purchased through a formal purchase order process.

Question 04

How does an SRN help Accounts Payable?

An SRN gives the Accounts Payable team documented proof that the service has been delivered and accepted. It helps verify vendor invoices, reduces the risk of duplicate or incorrect payments, and strengthens financial controls within the Procure-to-Pay process.