CURIOUSRUBIK
Let’s talk about your next move ↗View complete sitemap
Back to the blog

Controlling the NetSuite Vendor Prepayment Process

A controlled NetSuite vendor prepayment process follows the advance from authorization and payment through application to a supplier bill. Keep the prepayment balance visible until it is supported by delivery, billing or an approved refund. Paying a deposit and settling a bill are related events, but they need separate evidence.

The accounts payable team should know the supplier, purpose, purchase order where relevant, approved amount, currency and expected settlement date before entering an advance. Treasury or the authorized payment owner must separately control the release of funds.

Establish why the advance is required

Retain the supplier agreement or approved commercial terms showing the deposit requirement. Identify whether it relates to a particular purchase order, a group of purchases or an ongoing supplier arrangement. A vague payment memo creates problems when several bills arrive later.

Validate the vendor identity and payment instructions through your established fraud controls. A request for a changed bank account requires the company's independent verification process. The ERP transaction should not substitute for that verification.

Record the owner who will confirm delivery and follow up if the supplier does not perform. Aged prepayments often persist because AP can see the balance but has no authority to resolve the commercial issue.

Choose the linked or stand-alone path deliberately

A purchase-order-linked prepayment gives users a relationship to the intended purchase. Oracle notes that creating a prepayment from a PO autofills the full PO amount, even if the order has been partly paid. Review the proposed amount against the approved deposit and all prior advances before saving or releasing payment.

For a stand-alone prepayment, preserve a meaningful reference and expected application plan. Do not assume the system will later infer which purchase order or bill the advance was intended to cover. Define a review queue for unapplied amounts with no clear owner.

Confirm the required feature, permissions, bank or payment workflow, subsidiary and currency in the actual account. A user who can enter the transaction should not automatically receive unrestricted authority to pay it.

Separate transaction approval from payment evidence

Agree what each status means operationally. Verify whether an approved record represents an authorized instruction, a released bank payment or confirmed cash movement in your configured process. Reconcile the payment to bank evidence rather than assuming the record's existence proves that funds left the account.

Prevent duplicate payment through a check across vendor, currency, purchase reference and approved amount. Include prior prepayments and pending instructions. If a payment attempt fails, establish whether the original instruction is still capable of settling before anyone tries again.

This is particularly important when AP and treasury use different applications. Share stable transaction references and payment outcome information, with restricted access to sensitive banking data.

Apply the advance to an eligible bill

NetSuite prepayment applications reduce the prepayment balance and offset accounts payable. Oracle distinguishes automatic application for qualifying PO-associated prepayments from manual application of stand-alone advances. It also lists vendor, subsidiary, currency and bill-status eligibility constraints.

Review the actual bill before application. Confirm the delivered goods or services, approved amount and any differences from the original order. A deposit should not hide an invoice discrepancy merely because the remaining amount to pay appears small.

After application, verify the residual bill balance and remaining prepayment. If the bill is less than the advance, preserve the outstanding advance for subsequent application or refund handling under the approved policy. Do not write it off automatically to close the transaction.

Hypothetical partial-delivery example

A supplier order totals 20,000 currency units and requires a 30 percent deposit. The authorized advance is 6,000. When the prepayment entry defaults to the full order value, AP changes it to the supported 6,000 and checks that no earlier deposit exists.

The supplier delivers part of the order and issues an 8,000 bill. Assume the agreed terms allow all 6,000 to be applied to that bill. The application leaves 2,000 payable and no remaining advance. If the terms instead allocate the deposit proportionately to deliveries, the application policy must reflect that agreement and be validated in the configured process.

The example is hypothetical and excludes tax and foreign exchange. A controller must approve the actual accounting treatment, particularly where the supplier, currency or performance obligation introduces additional complexity.

Reconcile the remaining asset

At each close, review prepayments by vendor, subsidiary, currency, age and purchase reference. Compare the supporting schedule with the applicable general-ledger balance. Investigate amounts associated with cancelled orders, fully billed purchases or inactive vendors.

For each exception, document the next action: obtain the missing bill, apply an eligible balance, request commercial resolution, investigate a payment failure or assess recoverability. Accounting judgments about impairment, tax or foreign exchange require qualified review.

Avoid solving an old balance with an unexplained journal. A journal may change the ledger without repairing the transaction relationship AP needs to prevent later duplicate application or payment.

A prepayment control checklist

Before payment, confirm approved terms, verified vendor, correct currency and entity, deposit calculation, prior advances and authorized payment owner. After payment, retain bank evidence and the prepayment reference. Before bill settlement, verify delivery, application eligibility and the remaining amount due.

At close, assign an owner and expected resolution date to every aged or unexplained balance. Restrict edits to fully applied transactions and use the documented correction method, especially where money movement may still be in progress.

A good vendor prepayment process makes the advance easy to explain at every stage. The strongest control is a clear relationship among the commercial agreement, cash movement, supplier bill and application, with an accountable person responsible for any amount that remains open.

Related resources

What’s on your mind?

A little context is all it takes to begin.

Please leave out passwords, payment details and confidential account data.