Goods Receipt vs Inspection — How to Record Entries

A Classic Problem: Goods in Hand, But Not Yet on the Books

Let's look at a scenario that actually occurs in many agencies:

Sequence of Events

Step	Event	System Status
1	Contractor delivers goods/work with a delivery letter	Registered in the document management system (receipt number)
2	Goods are in the warehouse / work is at the agency	Not yet recorded in the accounting/procurement system
3	Waiting for the inspection committee (may be hard to schedule / may take several days)	Still no recording — a "vacuum" period
4	Inspection committee completes review and signs the acceptance form	Only now recorded in the procurement and accounting systems

Notice that between steps 2 and 4 is a "vacuum" period where goods are already in the agency's possession but no accounting entry has been made. This period can be as short as 3 days or as long as weeks or months, depending on the inspection process.

Why Everyone Is Confused by the Regulations

This problem arises from different perspectives across departments:

Procurement's View: "We Can't Accept Until the Committee Inspects"

Under the Ministry of Finance's Procurement and Supply Management Regulations, goods/services must go through an inspection process by an appointed inspection committee. The committee must count, verify condition, and sign the acceptance form — before this, the goods are not considered officially "received"

So procurement's view is: no acceptance form = can't receive = can't record.

Auditor's View: "You Have the Goods, So Record Them"

Auditors follow accrual basis accounting — once an economic event has occurred (goods received/work delivered), the organization has a payment obligation that must be recognized in the books, regardless of whether the inspection process is complete.

So the auditor's view is: goods are here = liability exists = must record.

Accounting's View: "So What Do I Do?"

The accounting team is squeezed from both sides — recording risks violating procurement regulations, while not recording draws auditor criticism. Either way, it feels like they can't win.

The Solution: GR/IR Clearing Account

The solution is to use a Clearing Account as a bridge between the procurement and accounting processes. This is a standard approach used in ERP systems worldwide, known as the GR/IR Clearing Account (Goods Receipt / Invoice Receipt Clearing Account).

The principle is to split the recording into 2 stages:

Stage 1: When the Contractor Delivers (Registered in Document System)

When the agency receives goods/work (with evidence from the document system), record it in the ERP immediately via the IM-01 Purchase/Contract Receipt screen:

Result:

• Debit side — Recognizes assets/expenses already received (compliant with accrual accounting)
• Credit side — Records liability in the "clearing account" rather than directly as "accounts payable" because the procurement inspection process is not yet complete (compliant with procurement regulations — not officially received yet)

Stage 2: When the Inspection Committee Completes Review

Once the inspection committee signs off, the finance team proceeds with the disbursement request via the AP-01 Disbursement Approval Request screen:

Result:

• Debit side — Clears the clearing account to zero (procurement process is complete)
• Credit side — Recognizes the liability as actual "accounts payable," ready for payment processing (compliant with procurement regulations — officially inspected and accepted)

Why This Method Satisfies Both Sides

Issue	Accounting Compliant?	Procurement Compliant?
Recognizing assets/expenses upon receiving goods	✓ Correct per accrual basis	✓ Does not violate regulations — it's an accounting entry
Recording liability in "clearing account" not directly as "payable"	✓ Reflects actual status	✓ Not considered "received" per regulations until inspection
Converted to "payable" only after inspection approval	✓ Matches actual process flow	✓ Disbursement only after inspection
When auditors inspect	✓ Entries are already recorded	✓ Clear status distinction: clearing vs payable

The key is that the "GR/IR Clearing Account" serves as a bridge between the two processes:

• When the clearing account has a balance = goods/work have been delivered but are still awaiting inspection
• When the clearing account balance is zero = inspection is complete and the liability has been transferred to accounts payable

Auditors can instantly see the clearing account balance to determine which items have been delivered but are still awaiting inspection on any given date — transparent, auditable, and nothing falls through the cracks.

Workflow in Saeree ERP

Saeree ERP designs workflows to fully comply with both procurement regulations and accounting standards:

Step	ERP Screen	Accounting Entry
1. Contractor delivers goods/work	IM-01 Purchase/Contract Receipt	DR. Inventory/Expense CR. GR/IR Clearing Account
2. Inspection committee review	IM-01 Status update	(No journal entry — status changed to "inspected")
3. Disbursement approval request	AP-01 Disbursement Approval Request	DR. GR/IR Clearing Account CR. Accounts Payable/Accrued Expenses
4. Payment	FI-03 Payment Recording	DR. Accounts Payable/Accrued Expenses CR. Bank Deposit

Benefits of This Workflow in Saeree ERP

• No "vacuum" period — As soon as delivery is logged in the document system, it's also recorded in ERP. No period where goods are in hand but accounting is unaware.
• Clear status separation — Check the clearing account balance to see how many items are pending and how many days they've been waiting.
• Accelerate inspection processes — The system alerts when items have been in the clearing account beyond the defined period, such as over 7 days.
• Cannot disburse without inspection — AP-01 can only proceed when IM-01 has a status of "inspected."
• Complete Audit Trail — Who recorded IM-01 and when, which day the committee inspected, when AP-01 was created — everything is fully traceable.
• Auditor reports — Clearing account balance reports broken down by item with aging in days.

The GR/IR Clearing Account is the "bridge" connecting procurement regulations with accounting principles — enabling every department to operate correctly within their role without conflict.

- Saeree ERP Team

Conclusion

The problem of "goods received but can't record accounting entries" isn't unsolvable. You just need the right perspective — procurement regulations address "receiving" as a process (inspection then disbursement), while accounting addresses "recognition" of obligations (obligation arises then record). These don't contradict each other, but there must be a mechanism connecting both sides.

Saeree ERP uses the "GR/IR Clearing Account" as this mechanism, enabling:

• Procurement to follow regulations completely
• Accounting to record correctly under accrual basis
• Auditors to see complete data and verify every transaction
• Management to know actual work status with nothing falling through the cracks

If you're interested in using Saeree ERP for comprehensive procurement and accounting management in government agencies, you can contact our team for more information.