Skip to main content

Purchase to Pay

Purchase to Pay

Vendor payment detail showing fictional vendor Northwind Office Supply, check 1001, a fifty-dollar amount, and invoice DOC-BILL-1001.
A fictional partial vendor payment allocated to a vendor invoice.
Vendor invoice DOC-BILL-1001 for Northwind Office Supply showing dates, terms, amount, draft memo, and expense or asset line.
The fictional vendor invoice before posting, with its receiving-ticket link and accounting line.
Inventory receiving ticket showing fictional bill and bill-of-lading numbers, warehouse, vendor, and six filter cartridges received.
A receiving ticket linked to the fictional purchase order and vendor bill.
Purchase order DOC-PO-1001 showing partially received status, the fictional vendor, warehouse, and filter cartridge line.
A fictional purchase order after six of ten items have been received.

Outcome and roles

This workflow follows an inventory purchase from an approved order through a partial receipt, vendor invoice, and allocated payment. Vendor, warehouse, item, quantity, cost, receipt, obligation, and payment evidence remain connected so purchasing, receiving, and accounting can review the vendor'ssame bill,chain without re-entering it.

Demonstration scenario

Demonstration notice: Every vendor, item, identifier, amount, bank reference, and payment.transaction is fictional. Documentation fixtures persist safe states without sending purchase orders, issuing payments, or contacting external systems.

Workflow at a glance

OutcomeReceived inventory, supported vendor obligation, and traceable payment application
Starts withReviewed vendor, item, warehouse, and purchase need
Ends withPayment allocation plus any visible remaining amount
Primary rolesBuyer, receiving clerk, accounts-payable clerk
Brisk areas involvedVendors, Purchase Orders, Receiving, Vendor Invoices, Payments
Common businessesRetail, feed/supply, parts, equipment, wholesale
Approximate handoffsThree

Why this workflow matters

Purchasing staff needknow validwhat vendors,was items,ordered, costs,receiving knows what arrived, and aaccounting destinationsees warehouse. Receiving staff needwhat the deliveredvendor quantitiesbilled. Keeping those records linked makes partial delivery, cost, freight, invoice, and freightpayment information.differences Accountingvisible staffrather needthan theburying vendor'sthem in a single payable total.

Each status marks a real control point. A submitted order is not a receipt, a receipt is not a verified vendor invoice, expense or asset allocation, terms, and an authorizedallocated partial payment account.does not make the invoice fully paid.

Before you begin

Vendor detail for fictional vendor DOC-V-001 showing purchasing and payable context.
Confirm vendor terms and accounting setup before creating the purchase order.
  • TheRequired: vendorvalid mustVendor, haveitems, theunits, payabledestination warehouse, payable/fee accounts, terms, and fee accounts required by its setup.permissions.
  • InventoryRequired items and the receiving warehouse must exist.
  • Payment terms should reflect the vendor agreement.
  • Ifwhen receipt freight is entered, Brisk requires theentered: Receiving Freight Accrual Account preference.
  • Keep external payment processors disabled in documentation demo environments.

1. Create and submit the purchase order

Create a Purchase Order with vendor, warehouse, dates, and item rows. Purchase status begins as Draft. Review quantities, unit costs, freight, and total before submission because later receiving uses the order rows and copies freight information.

2. Receive the inventory

Convert the purchase order into an Inventory Receipt, then record the quantity receivedRequired for each order row. The code supports partial receipt tracking by comparing receipt quantities with ordered rows. When deferred costing is enabled, final-cost processingprocessing: also requiressupported vendor and vendor invoice number;reference. freight

  • Disable external payment actions in documentation environments.

    • End-to-end steps

    Purchase order DOC-PO-1001 showing Partially Received status and ten ordered cartridges.
    The order retains the vendor, warehouse, ordered quantity, and remaining quantity after partial receipt.
    Purchase Orders list containing fictional purchase order DOC-PO-1001.
    The purchase register shows the order in the purchasing pipeline before receipt.
    1. Buyer — verify vendor and need. Confirm vendor, warehouse, requested dates, item, unit, quantity, cost, freight, and total. If the need came from Restock, first review Automatic Restock to Replenished Inventory.
    2. Buyer — create and submit the Purchase Order. Create Purchase Order DOC-PO-1001. It begins Draft. Review rows before the supported submission action; submission alone does not prove a vendor received a message.

    Receiving checkpoint

    1. Receiving clerk — record delivered quantity. Convert the order to an Inventory Receipt. DOC-BILL-1001 records six of ten cartridges. Purchase status becomes Partially Received because the receipt total is below the ordered quantity.
    2. Receiving/accounting — review receipt costing. Confirm accepted quantity, date, warehouse, BOL, freight, costs, and remaining quantity. Deferred/final-cost processing can require configuredthe accrual accounting.

      3. Recordvendor and reviewvendor invoice number.

    3. Accounts payable — enter the vendor invoiceinvoice.

      Enter theCreate Vendor Invoice DOC-BILL-1001 from the vendor'svendor document. Verify vendor, invoice number, invoice and invoice/due dates, terms, totals,subtotal, and allocation lines. On the detail page, checkamount, receipt links, credits,allocation payments,accounts, and accountingposting transactionsstate.

      4. before
    4. Authorized approvingpayer — record payment.

      4. Pay the remaining obligation

      From the unpaid invoice, selectUse Pay Invoice to start acreate Vendor Payment. ConfirmCheck 1001 allocates $50 to the payment$75 fictional invoice. Confirm account, amount, date, reference/check information,reference, and allocation before posting or issuing anything.

    5. Reviewer — verify the chain. Review Purchase, Receipt, Vendor Invoice, credits, payment applications, accounting transactions, and the remaining open quantity/obligation.

    What Brisk keeps connected

    Vendor invoice DOC-BILL-1001 for fictional Northwind Office Supply in Draft and unposted state.
    The vendor invoice allocation.remains TheDraft invoice'suntil unpaidaccounting amountverifies accountsdates, forterms, bothamount, paymentallocation, and receipt support.
    Inventory receipt DOC-BILL-1001 showing six fictional cartridges received against DOC-PO-1001.
    Receiving records only the six units that physically arrived and keeps their link to the order row.
    ActionResult or downstream recordWhere to verify it
    Submit PurchaseVendor/warehouse order with item rowsPurchase detail
    Receive quantityReceipt rows tied to purchase rows; partial status when incompleteReceipt and Purchase detail
    Record Vendor InvoicePayable document with allocations and vendorreceipt credits.

    support    		Vendor Invoice detail
    Allocate Vendor PaymentPayment-to-invoice link and remaining unpaid amountPayment and Vendor Invoice detail

    Handoffs and common failure pointscontrols

      Vendor payment 1001 allocating fifty fictional dollars to invoice DOC-BILL-1001 with bank details masked.
      The
    • Purchasingpartial payment retains its invoice allocation while the remaining obligation stays visible.

      • The buyer hands an approved order and expected delivery informationexpectation to receiving. Receiving supplies quantity and freight/cost evidence to accounting. Accounts payable matches vendor invoice, receipt, and purchase before payment. Purchase, Receipt, Vendor Invoice, and Payment each remain authoritative for their own business event.

      Exceptions and safe corrections

      • Wrong draft vendor/item/quantity: correct the Purchase before submission.
      • ReceivingShort reportsdelivery: quantity,receive freight,only accepted units and exceptionskeep tothe purchasing/accounting.order Partially Received.
      • AccountingMissing matchesfreight theaccount invoiceor tofinal-cost theinputs: correct configuration/evidence before processing.
      • Duplicate vendor invoice: search vendor and receipt before payment.
      • A freight validation error can mean the freight accrual preference is missing.
      • A final-cost receipt error can mean vendor or vendor invoice number isbefore missing.creating another.
      • AnWrong unexpectedposted invoiceinvoice/payment: due date usually points to invoice date or vendor/payment-term setup.
      • Protected relationships can block deletion; correct throughuse the supported update,credit, credit,void, reversal, or paymentcorrected processallocation; afterdo review.not delete material history or create an unrelated opposite record.

      Start here

      Continue with

    Back to top