Troubleshooting Purchase Invoices

1. Overview

This article covers the most common errors encountered when creating, releasing, and posting Purchase Invoices in Sparkrock 365, including errors specific to the A/P Batch Management feature and credit memo processing. Errors are grouped by the stage at which they occur.

2. Release Errors

These errors appear when the Release action is used on a Purchase Invoice. The release validates key header fields before the invoice can be approved or posted.

"Vendor Invoice No. must have a value."

The Vendor Invoice No. field is blank. This field is mandatory — it must contain the invoice number as it appears on the vendor's physical invoice.

1. Open the Purchase Invoice.
2. Enter the vendor's invoice number in the Vendor Invoice No. field on the General FastTab.
3. Release again.

"Vendor Invoice No. [X] already used in posted purchase invoice [Y] for this vendor."

This invoice number has already been posted for the same vendor. This is a duplicate payment prevention check — the same vendor invoice cannot be entered twice.

1. Note the posted invoice number shown in the error message (e.g., PI-00123).
2. Navigate to Search → Posted Purchase Invoices and open the referenced invoice.
3. Confirm whether this is a genuine duplicate (same goods/services already paid) or a different invoice that coincidentally has the same number.
4. If it is a duplicate: delete the new invoice — do not post it.
5. If it is a different invoice with the same number: contact the vendor to clarify. Consider appending a suffix to distinguish it (e.g., INV-001-A) and document the reason.

"Vendor Invoice No. [X] found in other unposted invoice(s) for this vendor."

The same vendor invoice number exists on one or more other unposted invoices for this vendor. The system is warning that releasing and posting this invoice could result in a duplicate payment.

1. Navigate to Search → Purchase Invoices and filter by vendor to find all unposted invoices with this number.
2. Determine which invoice is correct and delete any duplicates before proceeding.
3. Release the correct invoice.

"Vendor Cr. Memo No. [X] already used in posted credit memo [Y] for this vendor."

Applies to Credit Memos. The vendor credit memo number has already been posted. Same resolution as the duplicate invoice error above — confirm whether it is a genuine duplicate or a different credit, and act accordingly.

3. A/P Batch Management Errors

These errors only appear when A/P Batch Management is enabled in Purchases & Payables Setup. This feature requires invoices to be formally audited before they can be posted.

"SRF Audited must have a value."   (Invoice not audited)

The invoice has not been marked as audited. When A/P Batch Management is enabled, a user with batch auditing permissions must review and approve the invoice before it can be posted.

1. Assign the invoice to an A/P Batch if not already done.
2. A user with the Allow A/P Batch Auditing permission must open the invoice and use the Audit action to mark it as audited.
3. Post the invoice after it is audited.

"Allow A/P Batch Auditing must have a value." (No auditing permission)

The user attempting to reopen or audit the invoice does not have the Allow A/P Batch Auditing permission on their User Setup.

1. Navigate to Search → User Setup and open the card for the user who needs auditing rights.
2. Enable the Allow A/P Batch Auditing field.
3. Save and have the user try the action again.

4. T4A Validation Warnings

During release, the system checks whether the invoice is subject to T4A reporting requirements. Two confirmation dialogs may appear:

T4A Box is empty but vendor is T4A-liable

The vendor is marked as T4A-liable but the T4A Box field on the invoice is blank. The system will ask whether you want to continue without a T4A Box. If you continue without entering a T4A Box, the invoice will not be included in T4A reporting.

• To resolve: Cancel, open the invoice, and enter the correct T4A Box code before releasing.
• If no T4A applies: Confirm that you want to proceed without a T4A Box.

T4A Box is populated but vendor is not T4A-liable

A T4A Box is entered on the invoice but the vendor's T4A Liable flag is not set. The system asks for confirmation before proceeding.

5. Budget Checking Errors

Budget checking runs when a Purchase Invoice is released or posted, if budget checking is enabled for the Purchase Invoice document type. These errors indicate a configuration gap in the budget checking setup or that the invoice amount exceeds available budget.

"A Budget Checking Period could not be found for any of the encumbrance dates or posting dates in the document."

No Budget Checking Period record covers the posting date of this invoice. Budget checking periods must be set up for each fiscal period before invoices with dates in that period can be processed.

1. Navigate to Search → Budget Checking Periods.
2. Create a Budget Checking Period that includes the invoice's posting date.
3. Ensure the period is linked to the correct G/L Budget Name.
4. Re-release or re-post the invoice.

"There is no active Budget Checking Period for any of the encumbrance dates or posting dates in the document."

A Budget Checking Period exists for the date range but it is not active. Periods must be explicitly activated before they can be used for checking.

1. Navigate to Search → Budget Checking Periods.
2. Open the period covering the invoice date and set it to Active.
3. Re-try the release or post action.

"G/L Budget Entry related to Budget Checking Period [X] [Y] is not found."

The budget period is active and covers the posting date, but there are no G/L Budget entries for the accounts on the invoice within that period. Budget entries must exist before the system can check whether the invoice exceeds budget.

1. Navigate to Search → G/L Budgets → open the budget referenced in the error.
2. Confirm that budget entries exist for the G/L accounts on the invoice lines, within the budget period's calculation date range.
3. Enter budget entries if missing and re-try the action.

Budget exceeded — Warning or Error dialog

The invoice amount exceeds the available budget for one or more G/L accounts. The behaviour depends on the "Action If Budget Exceeded" setting on the Budget Checking Document setup:

• If Warning: review the budget detail, confirm the overspend is authorised, and proceed.
• If Error: the invoice cannot be posted until budget is available. Options are: increase the budget, recode the invoice to a different account with available budget, or request an authorised user to adjust the Budget Checking Document settings.

6. Credit Memo Errors

"You are restoring lines to purchase order(s). The purchase order(s) will be reopened. Do you want to proceed?"

This is a confirmation dialog, not a blocking error. It appears when a credit memo line has the Restore to Purchase Order flag set. If you confirm, the linked purchase order will be reopened and the credited lines returned to the order.

• Click Yes to proceed with the credit and reopen the PO.
• Click No to cancel the posting. Review whether restoring to the PO is intended before re-posting.

7. Quick Reference

8. Summary

• The most common invoice release errors are missing or duplicate Vendor Invoice No. — always use the vendor's own invoice number and confirm it hasn't been entered before.
• A/P Batch Management errors only appear when the feature is enabled. Check Purchases & Payables Setup if these errors are unexpected.
• Budget checking errors indicate a setup gap (missing period or budget entries) rather than a user error — involve your finance administrator to resolve them.
• T4A warnings require a decision — verify the vendor's T4A Liable setting and correct the invoice before confirming through.