Evaluating optional receiving features

Objective

After completing this lesson, you will be able to evaluate advanced optional receiving features in SAP Ariba Buying and Invoicing.

Evaluate asset data capture on receipts

Asset data capture in SAP Ariba Buying allows organizations to collect essential information about physical assets during the receiving process. Asset data can be used in conjunction with additional asset management features within SAP S4/HANA or other SAP ERP systems.

Note

Asset data capture is an optional feature that must first be enabled by SAP Support and configured by administrators or partners. Asset management functionality can only be integrated with SAP ERP systems.

Asset data details captured on receipts include:

  • Serial Number
  • Tag Number
  • Location

Capturing this data ensures accurate tracking of assets, compliance with financial regulations, and streamlined asset management processes .

Asset Workbench

The Asset Workbench is a tool within SAP Ariba Buying that allows asset managers to:

  • View and edit asset information for requisitions containing asset line items.
  • Add or validate asset data in receipts.
  • Manage asset-related approvals and workflows.

Asset Data Capture On Receipts

When receiving goods that are classified as assets, SAP Ariba Buying allows users to capture asset-specific information directly on the receipt. This ensures proper asset tracking, financial compliance, and integration with ERP systems.

When Is Asset Data Required?

Asset data entry is triggered only when:

  • The item’s receiving type is set to Manual Receipt by Quantity, and...
  • The item is flagged as requiring asset data via commodity code or part number configuration.

Steps To Capture Asset Data On A Receipt

  1. Start the Receipt
    • Go to Manage > Receive.
    • Open the relevant PO and begin creating a new receipt.
  2. Enter Receipt Quantities
    • Enter the quantities accepted (or rejected, if applicable).
    • Select Next to move to the Additional Info step.
  3. Enter Asset Data
    • For each unit of an asset item, a section appears prompting you to enter asset data such as:
      • Serial Number
      • Tag Number
      • Location
    • Each unit must have its own unique asset entry.
  4. Attach Supporting Documentation (Optional)
    • Upload delivery slips, packing lists, or supplier-provided asset tags.
  5. Submit the Receipt
    • Complete all required fields and select Submit.
    • The asset data is now associated with the receipt and can be passed to your SAP ERP system if integrated.

The screenshot below shows the process of capturing asset data during the receiving process.

A screenshot of SAP Ariba Buying showing step 3 of the receiving wizard. The screenshot shows fields that require the capturing of asset data on the receipt for items marked as requiring asset data.

Implementing asset data capture and utilizing the Asset Workbench in SAP Ariba Buying enhances asset tracking, ensures compliance, and streamlines integration with financial systems. By configuring receiving rules and leveraging integration capabilities, organizations can achieve efficient and accurate asset management throughout the procurement lifecycle.

Summary

  • Asset data capture is an optional feature that enables tracking of physical assets during receipt entry.
  • Required fields may include serial number, tag number, and location.
  • Asset capture is triggered by item configuration and manual receipt type.
  • The Asset Workbench allows asset data validation, editing, and workflow management.
  • Captured data integrates with SAP ERP for streamlined asset tracking and compliance.

Examine the evaluated receipt settlement functionality

Evaluated Receipt Settlement (ERS) is a streamlined invoicing process where the buyer automatically generates invoices based on goods receipts, eliminating the need for suppliers to submit invoices.This approach simplifies the procure-to-pay cycle, reduces manual effort, and minimizes errors.

Note

Evaluated Receipt Settlement (ERS) is an optional feature that must first be enabled and configured by administrators or partners.

Benefits of ERS

  • Efficiency - Reduces manual processing and accelerates the payment cycle.
  • Accuracy - Minimizes discrepancies by relying on system-generated data.
  • Cost Savings - Lowers administrative costs associated with invoice handling.
  • Supplier Satisfaction - Ensures timely payments, enhancing supplier relationships.

How ERS Works

  1. Mutual Agreement - Both buyer and supplier must agree to use ERS for specific transactions.
  2. Purchase Order Creation - The buyer creates a Purchase Requisition (PR) with the ERS flag enabled within one or more line items. Once the PR is approved, it generates a Purchase Order (PO) which is sent to the supplier, and includes the ERS flag on one or more line items.
  3. Goods Receipt - Upon delivery, the buyer records a goods receipt in SAP Ariba Buying.
  4. Automatic Invoice Generation - Based on the PO and goods receipt, SAP Ariba automatically generates an invoice on behalf of the supplier. The invoice captures only the amounts or quantities entered on the receipt.
  5. Payment Processing - The system processes the payment according to the agreed terms, completing the transaction without requiring a supplier-submitted invoice.

How To Set ERS In A PR

  1. Create a Purchase Requisition
    • Start a new requisition by adding items from a catalog, punch-out site, or a non-catalog item.
  2. Go to Line Item Details
    • Select a line item, then choose Actions > Edit.
  3. Set the ERS Field
    • Find the field labeled ERS Allowed.
    • Select Yes to enable ERS for the item.
  4. Repeat As Needed
    • Repeat steps 1-3 for all line items requiring ERS.
  5. Complete and Submit
    • Once all required information is filled in, submit the requisition as usual.

The screenshot below shows the Line Item Details of a PR line item. When ERS Allowed is set to Yes, the system will automatically create an invoice when a receipt is submitted for only the quantity or amount received.

A screenshot showing the ERS Allowed setting within a PR line item's details, which would enable Evaluated Receipt Settlement for the item.

The screenshot below shows the Invoices tab of a PO where we can see an invoice was created via the Evaluated Receipt Settlement functionality. We can tell it's an ERS created invoice because the invoice ID begins with the receipt ID.

A screenshot of the Inovices tab of a PO showing an ERS created receipt. The invoice ID is automatically generated with the receipt ID as it's prefix, which is an indicator that it was generated via the ERS functionality.

Summary

  • Evaluated Receipt Settlement (ERS) is an optional feature that auto-generates invoices from goods receipts—no supplier invoice needed.
  • ERS improves efficiency, accuracy, and supplier satisfaction while reducing costs.
  • Buyers and suppliers must agree to use ERS on specific transactions.
  • The ERS Allowed field must be enabled on PR line items.
  • ERS invoices are created upon receipt submission and approval.

Processing receipts with goods receipt based invoice verification

Goods Receipt-Based Invoice Verification (GR-Based IV) is a process where the system validates supplier invoices against the actual goods or services received, rather than solely against the purchase order. This ensures:

  • Only received goods/services are paid for.
  • Better control over spend and inventory.
  • Accurate three-way matching during invoice reconciliation: PO ↔ Receipt ↔ Invoice.

Note

Goods receipt-based invoice verification is an optional feature that must first be enabled and configured by administrators or partners.

How Goods Receipt-Based Invoice Verification Impacts the Receiving Process

  • Suppliers cannot invoice until a receipt is entered and approved (if applicable).
  • Receipts become the trigger for invoice reconciliation.
  • Partial receipts lead to partial invoice eligibility.
  • Rejected or missing receipts will block invoicing.

Steps To Process A Receipt Under Goods Receipt-Based Invoice Verification

  • Create Purchase Requisition
    • When creating a purchase requisition, set the Goods Receipt-Based Invoice Verification indicator to Yes at the line item level. This flag dictates that invoice verification for the item will be based on the goods receipt.
    • Generate a purchase order with the GR-Based IV indicator set for all applicable line items.
  • Receive Goods or Services
    • Upon delivery, create a goods receipt in SAP Ariba Buying, specifying the quantities received.
    • For partial deliveries, multiple receipts can be created corresponding to each delivery instance.
  • Approval of Receipts (if applicable)
    • If your organization requires approval of receipts, the goods receipt will follow the predefined approval workflow before being finalized.
  • Invoice Submission by Supplier
    • Suppliers submit invoices referencing the purchase order.
    • The system matches the invoice against the approved goods receipts.
  • Invoice Reconciliation
    • The system performs a three-way match between the purchase order, goods receipt, and invoice.
    • Discrepancies are flagged for resolution before payment processing.

Impact On Invoice Processing

  • Invoice Blocking - If a goods receipt is not available for a line item with GR-Based IV enabled, the corresponding invoice is blocked from payment until the receipt is recorded and approved.
  • Partial Receipts - Invoices are matched only to the quantities received. If only a portion of the order has been received, the invoice must correspond to that quantity.
  • Exception Handling - Any variances between the invoice and the goods receipt, such as quantity or price discrepancies, are managed through the invoice reconciliation process, requiring resolution before payment.

Summary

  • Goods receipt-based invoice verification is an optional feature that ensures invoices are matched to received goods or services, not just POs.
  • Invoicing is blocked until a receipt is entered—and approved, if required.
  • Only approved receipt quantities are eligible for invoicing and payment.
  • Partial receipts allow partial invoice matching; missing receipts prevent payment.
  • The system performs a three-way match between the PO (or contract), receipt, invoice, flagging discrepancies for resolution.

Manage team receiving and submit a team receipt

Team Receiving is a collaborative feature in SAP Ariba Buying that allows designated team members to perform receiving activities on behalf of the original requester. This functionality is particularly useful in scenarios where:

  • Teams work in shifts or across different locations.
  • The original requester is unavailable to confirm receipt.
  • Collaborative procurement processes are in place.

With Team Receiving, any member of a predefined team can:

  • Create receipts for goods or services.
  • Approve receipts (as the requester), if configured.
  • Monitor the status of team requisitions and receipts.

Note

Team receiving is an optional feature that must first be enabled and configured by administrators or partners. End users must also have the appropriate user group assignments to process receipts.

Setting Up Your Team

Once team receiving is enabled in a realm, teams need to be established. To configure a team:

  1. Access Your User Profile
    • Select the user icon at the top right of the dashboard to navigate to the user profile settings menu in SAP Ariba Buying.
    • Select Change your profile.
  2. Add Team Members
    • On step one of the profile change wizard, In the Team Requisition Members section, add the usernames of each team member.
    • In order for teams to be finalized, each team member must also add each team member to their team using the same steps.
    • Submit the user profile change request. Note that it must be approved before your team member changes are active.

The screenshot below shows the Team Requisition Members section of the user profile change request screen. This is where team members need to be added in order to enable team receiving within a PO.

A screenshot showing the Team Requisition Members section of the user profile change request screen.

Performing Team Receiving

  1. Create A Team Requisition
    • Create a purchase requisition.
    • Within the requisition, check the box labeled Is Team Received to allow team members to perform receiving actions.

    The screenshot below shows the Is Team Received option within the header level details of a Purchase Requisition. Select this box to enable team receiving for the resulting PO.

    A screenshot showing the Is Team Received check box within the header level details of a PR. This must be enabled to allow team receiving on the resulting PO.
  2. Submit And Secure Approvals
    • After submission, the requisition will follow the standard approval workflow.
  3. Team Receiving Actions
    • Any team member can now:
      • Create receipts for the associated purchase order.
      • Approve receipts, if the workflow requires.
      • Monitor receipt statuses and take necessary actions.

Team Receiving in SAP Ariba Buying enhances collaboration by allowing designated team members to manage receiving tasks collectively. By setting up your team correctly and understanding the process, you ensure timely and accurate receipt confirmations, even in the absence of the original requester.

Summary

  • Team Receiving is an optional feature that allows designated members to receive on behalf of the requester.
  • Teams must be configured in user profiles and mutually approved.
  • Enable Is Team Received on the requisition to allow team access.
  • Team members can create, approve, and track receipts collaboratively.
  • Feature supports shared responsibilities across shifts, locations, or teams.