Reconcile Accrued Purchases by linking the account's movements to receipts, vendor bills, credits and approved variance entries. Explain each residual at a meaningful purchase-order or receipt-line level. A list of open purchase orders is useful supporting evidence, but it does not automatically reproduce the general-ledger balance.
This guide addresses received-not-billed and related purchase residuals. Inventory valuation, AP aging and bill-approval checks have separate purposes. Your controller should approve the reconciliation scope, variance treatment and any correction to a closed period.
Start with the exact account, subsidiary, accounting book, currency basis and as-of date. Record the general-ledger closing balance and preserve the activity extract used in the review. Avoid comparing a current open-order report with a prior-period ledger balance without explaining subsequent transactions.
Oracle documents receiving inventory before billing as a supported purchasing sequence. Consequently, an outstanding receipt-related balance can be a legitimate timing item rather than an error.
Determine which purchase types and item configurations use the account in your implementation. Non-inventory purchases, drop-ship flows and custom postings may behave differently. Do not assume every PO line belongs in one received-not-billed calculation.
Reconcile opening balance plus period movements to closing balance. Classify movements into receipts, bills, vendor credits or returns, variance journals and other entries. Investigate manual journals and migration postings that do not carry an ordinary purchasing relationship.
Within that bridge, retain transaction and line identifiers. A single purchase order can have several receipts and bills, and one bill can relate to more than one source. A header-only join can repeat values or associate all activity with one convenient document.
Validate the report against a small set of known cases before running it across the account. Include a fully cleared purchase, a receipt awaiting a bill, a bill before receipt and an order with a posted variance. The report should explain each case without manual deletion of inconvenient rows.
A recent receipt with an expected supplier invoice is an open timing item. Record the invoice expectation and owner. A fully received and billed order with a remaining balance needs a more detailed explanation.
Potential causes include different quantities, prices, exchange rates, incorrect receipt links, an unmatched credit or an unrelated manual entry. The reason should identify the corrective action and evidence owner rather than simply label the amount “variance.”
Age residuals from a meaningful event, such as receipt date or expected billing date. Keep the date definition consistent. A late journal should not make an old purchasing issue appear newly created.
Oracle's Vendor Bill Variances guidance describes differences in quantity, price and exchange rate, and distinguishes methods based on bill lines with Match Bill to Receipt from purchase-order-line methods.
The selected method affects which links and lifecycle conditions the reviewer must inspect. Record the applicable setting and the actual receipt association on the bill. A generic residual formula can be misleading when it ignores how variance posting was configured.
Treat changes to the method as an implementation decision. Do not alter settings mid-investigation just to generate a clearing entry. First establish the original intent, the affected population and the accounting consequences with the controller.
Assume a review identifies three open balances. Purchase A has a 6,000 receipt entered yesterday and no bill; the supplier invoice is expected next week. Purchase B is fully received and billed but has a 180 difference. Purchase C has a 2,200 residual linked to an old manually entered journal.
Purchase A receives a timing explanation and a follow-up date. Purchase B is investigated for price, quantity, currency and receipt-link differences before deciding whether a variance process is appropriate. Purchase C requires journal support and accounting review because an open-order report may never explain it.
The reconciliation is complete only when the 8,380 total is tied to the ledger and each item has sufficient evidence. It need not be zero. The objective is an accurate, explainable balance with controlled resolution of exceptions.
When goods are returned, follow the return, vendor credit and application trail. A credit may arrive after the original purchase was considered complete, changing the residual analysis. Keep its relationship to the original receipt and bill visible.
Distinguish the vendor's promised credit from a recorded and supported credit transaction. Procurement may know a concession is expected while finance still lacks a document. Record the expectation and obtain an approved accounting decision for period-end treatment.
If a supplier refunds cash rather than reducing future bills, extend the evidence trail through the refund and bank receipt. Do not treat a vendor statement showing a credit as proof that the money has been recovered.
For each aged residual, ask whether goods or invoices are still expected, whether the supplier agrees with the position and whether prior variance entries already addressed the difference. Check for closed orders that retain an unexplained accounting balance.
Avoid a blanket journal that clears old items without preserving their causes. A supported adjustment may be appropriate, but finance should approve its amount, account, period and rationale. Retain the individual case list behind any summarized posting.
Also inspect debit and credit residuals separately. Netting unrelated errors to a small total can hide material problems. A balanced supplier group does not establish that every receipt and bill relationship is correct.
The package should contain the ledger balance, movement bridge, open-item listing, aging basis, reason codes, supporting transaction links and approvals. A reviewer should be able to trace from the closing total to the evidence for any sampled item.
Carry unresolved items forward with their existing identifiers and history. Show new items, resolved items and changed explanations each period. This makes progress visible without rebuilding the entire investigation from scratch.
Use exception trends to improve purchasing operations. Repeated late receipts, wrong units or missing bill links call for process changes. Repeated manual clearing journals suggest the report or lifecycle design needs closer attention.
For transaction-link analysis and reporting logic, CuriousRubik's NetSuite support services can help investigate representative residuals and validate the reconciliation design.
Add a reviewer check for the largest residuals and a sample of recently cleared items. A cleared item can still be wrong if it was offset against an unrelated purchase. Require the workpaper to show the linked documents and the specific resolving event, so the closing review tests the quality of the explanation as well as the arithmetic.
Not necessarily. Valid receipt-to-bill timing items can remain. The balance should be reconciled, supported and aged, with exceptions assigned for resolution.
It is supporting evidence, but may omit journals, posted variances or line relationships needed to explain the ledger. Build and validate a movement bridge.
Verify quantities, prices, exchange rates, receipt associations, the selected variance method and whether another entry already addressed the issue. Obtain accounting approval.
Unrelated errors can offset in a net total. Separate review prevents a small overall balance from hiding larger unresolved items.
Age alone is insufficient. Establish the cause, expected remaining activity and supporting evidence, then obtain the controller's approved accounting treatment.