How-toSYSPROAccounts Payable / Purchasing

SYSPRO AP invoice posting: GRN matching, posting and common errors

Question
syspro ap invoice posting

Also searched as

  • syspro grn matching
  • syspro post supplier invoice
  • syspro ap invoice error

Short answer

In SYSPRO you receive goods against the purchase order to create a GRN, then enter the supplier invoice in Accounts Payable and match it to the GRN, which clears the GRN suspense and posts the payable. Unmatched or mispriced lines are the usual cause of posting errors. Post the batch and check the GL distribution.

Applies to: SYSPRO 7 and 8 with Purchase Orders, Accounts Payable and General Ledger integration. Program names and screens vary by release and by whether GRN matching is enabled.

Post a supplier invoice against a GRN

  1. 1Confirm the goods are received on the purchase order in Purchase Orders, so a GRN exists.
  2. 2In Accounts Payable, open the invoice posting program and choose the supplier.
  3. 3Enter the invoice number, date, currency and total.
  4. 4If GRN matching is used, select the GRN lines this invoice covers and confirm quantity and price.
  5. 5Review the price variance between the invoice and the PO and let the system post it to the configured variance account.
  6. 6Add any non-PO lines, such as freight, with the GL account and tax code.
  7. 7Check the invoice total equals the sum of matched and manual lines, then post.
  8. 8Print or review the posting journal and the GL distribution before the batch is released to the ledger.

How the three way match works

Receiving a PO line creates a GRN and accrues the liability against a GRN suspense account. Matching the invoice to that GRN relieves the suspense and records the payable at the invoiced value, with the price difference posted as a variance. This is the three way match: PO, receipt, invoice.

That is why an invoice can only be matched to goods that have been received. Invoices for goods not yet receipted need receiving first, or must go through a defined exception route.

GL distribution

For matched lines the accounts come from the inventory or expense mapping and the variance account. For manual lines you choose the account. Tax follows the tax code on the supplier and line. Always review the distribution on the journal before releasing it.

If the GL integration for payables is set to hold journals, they wait for posting in the General Ledger, so a payable can show in the subledger before the ledger has it.

Common posting errors

Quantity or price outside tolerance: the invoice does not agree with the GRN, so correct the invoice or get the PO price amended. Invalid GL account or period: see the GL interface error page. GRN already matched: another invoice used it, so check for a duplicate invoice number.

Supplier on hold or currency mismatch also stop posting. Check the supplier record before assuming a system fault.

Try it here, free

SYSPRO SQL Query Generator

Open full tool

Generate read-only SQL Server queries against common SYSPRO tables. Fill in database and filters, then copy the code.

Common pitfalls

  • !Overriding the price variance without asking purchasing why it differs.
  • !Entering a duplicate invoice number because the control was off.
  • !Posting freight to the wrong account and polluting inventory cost.
  • !Leaving GRNs unmatched for months so the suspense balance grows.
  • !Releasing the batch without reviewing the GL distribution.

How an ERP-grounded AI assistant handles this

An assistant over SYSPRO can list unmatched GRNs, flag invoices that differ from the PO price and draft the exception note for a buyer, read-only. Netray hosts it on your own infrastructure so supplier and cost data stay private.

Frequently asked questions

Can I post an invoice without a GRN?

Yes for non-PO costs such as services, using manual lines with a GL account. For stock purchases, receive first so cost and quantity are correct.

What is the GRN suspense account?

An account that holds the liability for received but not yet invoiced goods. Matching the invoice clears it. A growing balance means unmatched receipts.

Where does the price variance go?

To the purchase price variance account set in the GL integration. With average costing, the variance may instead adjust cost, depending on setup.

How do I correct a wrong posted invoice?

Use the AP adjustment or reversal route rather than editing data, so the audit trail and GL stay consistent. Then post the correct invoice.

Related

Error fix

SYSPRO GL interface error: how to diagnose and fix it

A GL interface error means a subledger transaction could not build or post its journal to the General Ledger. The usual causes are missing or invalid GL account mapping, a closed or invalid period, journals left unposted, or an out-of-balance entry. Find the failing transaction, fix the mapping or period, then post the pending journals.

How-to

How to void a check (cheque) in SYSPRO

In SYSPRO you cancel an unreconciled cheque with the cheque cancellation or payment reversal route in Accounts Payable and Cash Book, which reinstates the supplier invoices and reverses the bank entry. A cheque already reconciled to the bank, or in a closed period, needs a reversal entry instead.

How-to

SYSPRO costing methods: standard, average, FIFO and last cost

SYSPRO sets the costing method on each stock code, so one company can mix methods. Standard cost holds a fixed cost and posts variances, average cost blends receipts into a moving cost, FIFO values stock at the cost of the oldest layers, and last cost uses the latest purchase cost. The method drives inventory value, WIP and variance postings.

How-to

SYSPRO reporting API: e.net, SRS server-side reporting, Crystal Reports and SRS preview problems

SYSPRO gives you three reporting routes: the e.net Solutions business object API (XML in, XML out) for programmatic data, SYSPRO Reporting Services (SRS) for designed reports run on the server, and Crystal-based or SQL-based custom reports. If the SRS preview does not work, check the services, the runtime and bitness, the SQL permissions and the client and server versions in that order.

Error fix

Error validating SYSPRO online profile: what it means and how to fix it

A profile validation error means the SYSPRO client or service could not confirm the operator, company, licence or database connection it was handed at logon. Check the service and licence first, then the operator and company, then the database and disk, in that order. Storage errors are usually full disks, a locked SQL file or a tempdb problem rather than a SYSPRO bug.

How-to

How to update SYSPRO (and how to check the latest version)

SYSPRO 8 ships as named releases (for example 2022 R1 style names) plus later updates, and the current release is listed on the SYSPRO partner and customer portals, not on a fixed public page. To update, back up, test the new build on a copy of your data, then update the server, services and clients in a planned window.

AI for ERP

AI for SYSPRO, Grounded in Your Own Manufacturing Data

Add AI to SYSPRO without moving your manufacturing data to a public model. On-premise and private-cloud LLMs for SYSPRO in Australia, NA, and beyond.

Stuck on SYSPRO?

Talk to engineers who work inside SYSPRO every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

AI on your ERP

Integrations

Software