How to Find Parked Invoices During SAP Supplier Reconciliation

Supplier statements can be reconciled directly inside SAP by loading the statement data, matching each line against posted and cleared supplier items, and searching further up the procurement process for parked invoices, held documents, GR/IR entries and invoices awaiting approval. With an SAP-embedded solution, the matching, investigation, reporting and approval process can be automated in SAP rather than managed through a separate reconciliation platform.

One of the most common reasons a supplier statement does not match the corresponding vendor account is that an invoice already exists in SAP but remains parked rather than posted. This article explains how to find parked invoices, resolve them, and include them in an automated supplier statement reconciliation.

What is a parked invoice in SAP?

A parked invoice is an invoice or credit memo that has been entered and saved in SAP but has not yet been posted as a completed accounting document.

Parking allows an employee to record the available information without completing the posting immediately. The document can then be reviewed, supplemented with missing information, approved, or corrected before it is posted.

An invoice might be parked because:

• Account assignment information is missing
• The purchase order or goods receipt cannot be confirmed
• The invoice requires approval
• A price or quantity discrepancy needs investigation
• The tax treatment needs to be checked
• Supporting documentation has not been received
• The employee entering the invoice is not authorised to post it
• The invoice contains an error that must be corrected

SAP’s Park Supplier Invoices application allows supplier invoices and credit memos to be held or parked for later completion.

What is the difference between parked, held, blocked and posted invoices?

These terms describe different stages or conditions in the invoice process. Their exact meaning and behaviour can depend on the SAP product, configuration and invoice workflow being used.

A blocked invoice should not automatically be treated as a missing invoice. SAP explains that an invoice block prevents Financial Accounting from paying the invoice until the block is released. More information is available in SAP’s guidance on blocking invoices.

Why do parked invoices cause supplier statement discrepancies?

A supplier records an invoice in its own accounting system when it is issued. The invoice may therefore appear on the supplier’s next statement even if the customer has not finished processing it in SAP.

A typical discrepancy develops as follows:

1. The supplier issues an invoice and includes it on its statement.
2. The customer receives the invoice and enters it into SAP.
3. The document is parked because it requires additional information, approval or investigation.
4. The invoice has not yet been posted to the supplier account.
5. The accounts payable team compares the statement with posted supplier items.
6. The invoice appears to be missing, even though a parked document already exists.

If the reconciliation process only searches posted open and cleared items, it may incorrectly classify the statement line as a missing invoice. An employee must then search manually across different stages of the procurement process to establish where the invoice is.

The status and location of an invoice are therefore as important as whether its reference appears in the supplier account.

How can you find parked invoices in SAP?

The correct method depends on whether the invoice was entered through Materials Management, Financial Accounting, an SAP Fiori application or a connected invoice-management workflow.

A practical investigation should include the following steps.

1. Search using more than the invoice number

Start with the supplier’s invoice reference, but do not rely on an exact match. Suppliers and customers may record the same reference differently because of:

• Spaces
• Leading zeroes
• Slashes and hyphens
• Prefixes or suffixes
• Character limits
• Typing errors
• References entered into different SAP fields

Search using a combination of the supplier, amount, invoice date, currency, purchase order and document reference.

2. Check posted supplier items

Confirm whether the invoice has already been posted to the supplier account. It may have been entered using a different invoice reference, posted to another supplier or recorded under a different company code.

Check both open and cleared items. An invoice may already have been paid or cleared but remain on the statement because of a timing difference in the supplier’s records.

3. Review parked and held documents

If there is no posted match, search the relevant parked and held document worklists.

Depending on the SAP environment and process, this may involve:

• The Supplier Invoices List or another relevant SAP Fiori application
• Parked Logistics Invoice Verification documents
• Parked Financial Accounting documents
• Invoice approval workflows
• Documents saved temporarily by an accounts payable employee
• Connected invoice-management systems

MIR7 is commonly associated with parking invoices in Logistics Invoice Verification. The relevant applications and transactions may differ for FI invoices, SAP S/4HANA deployments and organisation-specific processes.

4. Check the approval workflow

An invoice may have been captured correctly but remain with an approver. Review:

• Current workflow status
• Assigned approver
• Approval history
• Rejection or return comments
• Missing attachments
• Escalations and overdue actions

Finding the document is only the first step. Where the available workflow data allows, the investigation should also establish why the invoice remains unposted and who needs to take action.

5. Search across company codes

A supplier may operate across several legal entities, while an invoice can be sent to or entered under the wrong company code.

When the invoice is not found in the expected account, check whether:

• The supplier has more than one vendor master record
• The invoice belongs to another company code
• A shared service centre entered it for the wrong entity
• The supplier statement combines transactions for several entities
• The invoice was posted to an alternative or linked supplier account

This is particularly important for multinational groups and shared service centres. Read more about managing SAP vendor statement reconciliation across multiple countries.

6. Review GR/IR and purchase order information

If the invoice itself cannot be found, check whether the corresponding goods receipt or purchase order information exists.

A goods receipt recorded in the GR/IR account can indicate that the organisation has received the goods or services but has not yet received or posted the supplier invoice. Purchase order information can also help establish whether the statement item relates to a genuine purchase.

7. Check invoice-management systems

Some organisations use invoice capture or Vendor Invoice Management software alongside SAP. The invoice may still be undergoing extraction, validation, coding or approval in that system.

The investigation should determine whether the invoice is:

• Waiting to be transferred into SAP
• Awaiting data validation
• Held in an approval workflow
• Rejected because of an error
• Identified as a potential duplicate
• Waiting for purchase order or goods receipt information
• Ready for posting but not yet completed

Why might a parked invoice remain unresolved?

Parked invoices do not always represent an error. Parking is a useful control when an invoice cannot or should not be posted immediately.

However, a growing backlog of parked documents can indicate problems such as:

• Unclear approval responsibilities
• Missing purchase order information
• Delayed goods receipt posting
• Incomplete supplier documentation
• Repeated price or quantity differences
• Poor-quality invoice data
• Insufficient workflow escalation
• Duplicate invoice concerns
• Incorrect supplier or company code assignments
• Limited visibility over outstanding documents

Accounts payable teams should monitor both the age of parked invoices and the reasons why they remain unresolved. A document parked for one day while awaiting routine approval presents a different risk from an invoice that has remained unresolved across several accounting periods.

How should parked invoices be resolved?

The appropriate action depends on why the invoice was parked.

A valid invoice might need to be:

• Completed with the missing account assignment
• Matched with the correct purchase order
• Supported by a goods receipt
• Corrected for tax, price or quantity information
• Sent to the appropriate approver
• Posted to the correct supplier and company code

An invalid or duplicate invoice may need to be rejected or deleted in accordance with the organisation’s controls. If the supplier has included an invoice that the customer has never received, the accounts payable team should request a copy and record the item as a genuine missing-invoice exception.

An employee should not post an invoice solely to make the supplier statement agree. The document must still satisfy the organisation’s procurement, accounting, approval and fraud-prevention controls.

How can supplier statements be reconciled directly inside SAP?

Supplier statements can be reconciled directly inside SAP by loading the statement, comparing its lines with SAP supplier transactions and searching upstream records when no posted match is found.

An effective process should consider:

• Posted supplier invoices and credit notes
• Cleared supplier transactions
• Parked invoices
• Held documents
• GR/IR entries
• Relevant purchase order information
• Payments
• Invoice-management workflow records
• Linked supplier or customer accounts
• Related records under other company codes

Reliable matches can be processed automatically. Items that cannot be matched should be categorised and presented to the accounts payable team for investigation.

For example, a statement invoice might be classified as:

• Matched to a posted invoice
• Matched to a parked invoice
• Found in an approval workflow
• Related to a goods receipt without a posted invoice
• Recorded under another company code
• Potentially duplicated
• Not found in SAP

This provides a more informative result than labelling every unmatched statement line as a missing invoice. It also prevents employees from repeating the same searches manually for every supplier.

Our guide to supplier statement matching in SAP explains the wider reconciliation and matching process.

Can supplier statement reconciliation be automated without a separate platform?

Yes. The matching, investigation, reporting and approval of supplier statement reconciliations can be automated in SAP without moving the process and its financial data to a separate reconciliation platform.

The BEST Vendor Recons module is an SAP-embedded solution that matches supplier statement data against SAP transactions and other relevant records. Users can match, investigate, report on and approve supplier reconciliations in SAP using normal SAP authorisations and system audit trails.

The BEST Vendor Recons module can match statement items against records further up the procurement chain, including:

• Posted and cleared supplier items
• Parked and held invoices
• GR/IR entries
• Vendor Invoice Management workflows, including systems such as OpenText, ReadSoft and eFlow

This means an invoice does not have to be posted as a normal supplier open item before the reconciliation process can identify it.

Supplier statements can be loaded into the BEST Vendor Recons module using spreadsheet uploads, copy-and-capture or other supported methods. Organisations that want to automate statement collection and data extraction can use the optional BEST Statement Reader, which processes emailed PDF and Excel statements before loading the data into SAP.

A separate BEST Web Statement Portal is also available for organisations that want suppliers to upload and validate their own statements before the information is loaded into SAP.

When is an SAP-embedded approach most suitable?

An SAP-embedded supplier reconciliation solution is particularly suitable for organisations that:

• Use SAP as their central accounting system
• Process high volumes of supplier statements
• Operate across multiple company codes
• Want reconciliation data and evidence to remain in SAP
• Already use separate software for invoice capture and approval
• Need to search across posted and upstream procurement records
• Want approvals to follow normal SAP authorisations
• Currently rely on spreadsheets for supplier reconciliation

It may not be the right option for every organisation. A business that does not use SAP will require a platform designed for its own ERP or accounting system. A multi-ERP group seeking one invoice capture, payment and reconciliation platform across every system may also prefer a broader external solution.

The BEST Vendor Recons module is not intended to replace complete invoice capture and approval software. It can work alongside an organisation’s existing invoice-management system by identifying invoices that are still being processed there and incorporating that information into the supplier reconciliation.

What evidence is there that supplier reconciliation can be automated in SAP?

Foodstuffs South Island previously used a manual, spreadsheet-based supplier reconciliation process. Reconciliation of a payment file covering 300 vendors could take approximately 1.5 days to complete.

After implementing the BEST Vendor Recons module, Foodstuffs reported that the same volume could be reconciled in around 25 minutes. Its reconciliation staffing requirement also reduced from 12 to six full-time equivalents through efficiency gains, allowing employees to spend more time on supplier relationships and analysis.

The solution was integrated within Foodstuffs’ existing SAP environment, allowing the business to automate supplier reconciliations without moving the process to a separate reconciliation platform.

Read the complete Foodstuffs supplier reconciliation case study.

Results will vary according to statement quality, transaction volumes, matching rules, SAP configuration and the consistency of supplier references. However, the Foodstuffs results show the potential operational improvement when routine matching and document searches are automated.

What happens when no matching invoice is found?

If a statement line cannot be matched to a posted, parked or in-process invoice, it should become a clearly categorised exception.

Possible explanations include:

• The invoice was never received
• The invoice has not been entered into SAP
• The supplier used an incorrect reference
• The document was posted to the wrong supplier
• The document belongs to another company code
• A credit note is missing
• The supplier statement contains an error
• The goods receipt exists but the invoice does not
• The transaction is duplicated
• The difference results from timing

The reconciliation record should show what was checked, what was found and who is responsible for the next action. This creates a stronger control than maintaining an unstructured list of unmatched items in a spreadsheet.

How can SAP teams improve the management of parked invoices?

Finance teams can reduce parked-invoice backlogs and supplier statement discrepancies by:

1. Defining standard reason categories for parked documents.
2. Assigning clear responsibility for each exception type.
3. Monitoring the age of parked invoices.
4. Escalating overdue approvals.
5. Checking supplier, amount and reference data before creating another document.
6. Reviewing GR/IR and purchase order issues alongside invoice exceptions.
7. Searching across company codes and related supplier accounts.
8. Including parked and held documents in supplier statement matching.
9. Reporting recurring issues by supplier, business unit and approver.
10. Retaining the statement, matching result, comments and approval history together.

The aim is not necessarily to eliminate parked invoices. Parking remains useful when information or approval is incomplete. Instead, teams should make parked documents visible, record why they remain unresolved and ensure that the appropriate employee can act on them.

Can SAP identify a missing invoice before it becomes a payment problem?

A supplier statement is an independent source of information. It can reveal that the supplier expects payment for an invoice even when that invoice is not visible among the customer’s posted supplier items.

By checking statement lines against posted transactions, parked invoices, held documents, GR/IR and invoice workflows, finance teams can distinguish between:

• An invoice that is genuinely missing
• An invoice already received but awaiting action
• An invoice posted using different details
• A timing difference
• An error in the supplier’s records

Identifying the cause early can help prevent delayed payments, duplicate invoice entry, inaccurate accruals and avoidable supplier queries.

Automating this process in SAP gives the accounts payable team a consolidated view of where each invoice is and what needs to happen next. To see how this works in practice, explore the BEST Vendor Recons module or request a demo.

Frequently asked questions

Do parked invoices appear as supplier open items in SAP?

A parked invoice has not completed posting, so it will not generally appear as a normally posted supplier open item. Users may need to review parked document lists, supplier invoice applications or approval workflows to find it.

Can a parked invoice be included in a supplier reconciliation?

Yes. An appropriate reconciliation solution can compare supplier statement lines with parked documents as well as posted and cleared supplier items.

Why is an invoice on the supplier statement but not in SAP?

The invoice may not have been received, or it may be parked, held, awaiting approval, recorded in an invoice-management system, posted to another supplier or entered under another company code.

Is a parked invoice the same as a blocked invoice?

No. A parked invoice has been saved but not fully posted. A blocked invoice has generally been posted but is prevented from payment until the relevant issue is resolved.

Can supplier statements be reconciled directly inside SAP?

Yes. An SAP-embedded reconciliation solution can match supplier statement data against SAP records, categorise discrepancies and retain the reconciliation and approval evidence in SAP.

Can supplier statement reconciliation be automated without a separate platform?

Yes. The matching, investigation, exception management and approval process can be automated in SAP without moving the reconciliation to a separate platform. Optional statement-reading technology can also automate the collection and loading of supplier statements.

Does the BEST Vendor Recons module replace invoice capture and approval software?

No. The BEST Vendor Recons module focuses on supplier statement reconciliation. It can work alongside invoice capture and workflow software by matching statement lines against invoices that are still being processed.