Vendor invoices and adjustment notes
Choose the supplier document match the source and apply reducing notes
Use Vendor Transactions for supplier invoices, Vendor Charges and vendor notes. Use Vendor Payments for cash paid or advanced, then apply that payment to the intended open supplier lines. Receiving goods, recording a liability, allocating a note and sending money are different events.
This guide is for authorised purchasing and accounting users in their selected company and permitted locations. It explains which document to choose and how to recognise the result. The detailed regular form fields remain in vendor invoices and payments.
Choose the vendor document by its effect
| Requirement | RavenLedger route | Expected commercial effect |
|---|---|---|
| Record an ordinary supplier invoice | Invoice | Increases the amount payable; match the applicable PO/receipt or invoice-only policy. |
| Record an additional supplier charge | Vendor Charge where applicable | Increases the amount payable. This is not the reducing vendor Debit Note route. |
| Record a supplier service or expense | Invoice with an eligible non-inventory item | Uses the item's non-inventory posting design; item selection is still required. |
| Record stocked purchases | Invoice with an inventory item and supported matching/receipt allocation | Stock receipt and liability accounting depend on the configured purchasing policy. |
| Reduce a supplier amount due | Vendor Credit Note or Vendor Debit Note, according to the approved business evidence | Both ordinary vendor note types are reducing documents in this release. They have negative quantities and positive prices in the regular form. |
| Purchase or adjust a fixed asset | Supported fixed-asset purchasing/capitalisation route | Use the actual asset/event controls; a normal expense invoice does not replace capitalisation. |
| Pay or advance cash | Vendor Payment followed by application where appropriate | Payment save does not automatically clear a specific invoice or prove bank execution. |
| Receive money back from a supplier | Supported refund against the eligible original payment | A vendor note alone does not put cash back into the bank. |
Do not infer the sign from the word Debit alone. A customer Debit Note increases receivables; a vendor Debit Note in this release reduces payables. For an additional supplier liability, use the supported Invoice/Vendor Charge design, not a reducing note with a forced sign.
Prepare supplier item tax and account mappings
Confirm the active supplier, supplier liability account, location, document dates, purchasing policy and permitted matching sources. A supplier reference is evidence, not a guarantee of duplicate protection: check the original invoice number, date, currency and amount against existing records.
Select the actual item even for a service/expense purchase. Non-inventory items use their charge-account design; inventory items require the correct stock and receipt mappings. Review vendor tax defaults independently of customer tax defaults, and verify whether withholding is recognised at invoice posting or when cash is applied.
Before payments, prepare a bank account in the payment currency and its required supplier-prepayment mapping. Review the functional FX basis for the invoice and payment separately. See tax and currency applications.
Choose the correct purchase matching route
| Policy and item | Match source | Receipt consequence |
|---|---|---|
| Two-Way inventory | Eligible approved PO Line | Invoice receipt allocation supplies the one-step stock receiving detail. |
| Three-Way inventory with two-step receipts | Eligible posted GRN Line | Goods were already received; invoice matching clears the receipt basis rather than receiving the same stock twice. |
| Three-Way non-inventory | Eligible PO Line | No stock GRN is required for the non-inventory charge. |
| Invoice Only | No PO/GRN match required by that policy | Inventory still requires the applicable one-step receipt allocation. |
Do not change purchasing policy to make one invoice pass validation. Resolve missing approval, receipt, quantities, tolerances or account mappings through the responsible process. Read purchasing setup and orders and receipts.
Save and reconcile a supplier invoice
- Open Vendor Transactions in the selected company and choose the new-document action. Select Invoice and the intended supplier/location.
- Enter the supplier's invoice reference, Transaction Date, Ledger Date, currency, functional FX rate and terms. Compare the supplier's external evidence with the proposed record.
- Add the eligible items, quantities, prices and permitted discounts. Select the required PO Line or posted GRN Line; complete one-step inventory receipt allocations only where that route applies.
- Review vendor tax, withholding timing, base, chargeable tax, gross and net payable. Check both transaction and functional figures and any receipt/price/FX differences.
- Save once and retain the generated number. Reopen the saved document, matched quantities and linked processing/journals.
- Reconcile supplier open items, stock/expense or GRNI, tax and functional GL. Check that stock was not received twice and that an unapplied payment was not mistaken for settlement.
Use regular invoice/payment fields and the tax examples for the controls and calculations. A supplier PDF, imported row count or saved header is not proof of completed posting.
Record a vendor charge
Use the permitted Vendor Charge route for an additional supplier amount due, with the approved item/account, tax treatment and source evidence. Review whether the charge is an expense, stock-related cost or another supported adjustment; do not choose an inventory cost adjustment merely because an invoice has no physical quantity.
Ordinary positive invoice-like lines increase the supplier liability. Amount-only cost/FX/system transactions have separate rules and are not a workaround for an invalid ordinary line. Reconcile the charge's actual account destination and supplier open amount after processing.
Record a vendor debit or credit note
- Establish the reason, supplier's original reference and approved reducing amount. Select the note type that matches the business evidence and local process.
- In Vendor Transactions, choose Debit Note or Credit Note. Use the same supplier and the intended location, dates and currency. Review the negative quantity and positive price in the regular form.
- Select the required item and approved account/tax treatment. For returned inventory, follow the applicable goods-return and allocation/matching controls, including the eligible GRN Return source where required.
- Save once and reopen the note. Verify its negative net/open amount and the actual stock, cost, tax and liability effects.
- Apply the eligible note to the intended supplier invoice or Vendor Charge separately. If cash must be returned, use the supported payment-refund route instead of treating note allocation as a bank receipt.
Do not reverse physical goods twice by combining a goods return with a second unlinked inventory note. Equally, a price-only financial reduction does not by itself prove that any goods have left the warehouse.
Apply a vendor note to an open invoice
Open the saved eligible note line's Apply controls. Choose the exact target Invoice or Vendor Charge line, and verify the company, supplier, currency and current open amount. The normal note lookup filters eligible targets to the note's currency when the source note is supplied.
| Control or display | Currency and purpose | Entry or review rule |
|---|---|---|
| Target document and line | The invoice/charge being reduced | Match the supplier's original evidence and the intended open line. |
| Applied Amount | Target invoice currency | Enter a positive amount within the target's current open balance. |
| Note Applied Amount | Source note currency | Positive amount consumed from the negative note's available credit; review remaining source capacity. |
| Cross Currency Rate | Target units per one source-note unit | Same-currency applications use 1. Do not transfer the cash-application rate direction to this screen. |
| Functional Applied Amount | Target application at the target document's functional FX basis | Compare it with the source note's functional value and the linked FX result. |
| Transaction Date and Ledger Date | Application and accounting dates | Must satisfy the source/target date checks and open-period controls. |
| Application and FX journals | Separate application accounting | Inspect the actual linked records and posted state, not merely the original invoice journal. |
Apply once and reopen both documents. Applying USD100 from a USD100 reducing note to a USD1,000 invoice leaves invoice USD900 and source note zero when there are no other applications.
Distinguish foreign currency from different currencies
A USD note applied to a USD invoice is same-currency even in a PKR company. Its cross rate is 1, but different document FX bases can still produce a functional exchange difference. For example, USD100 at PKR285 is PKR28,500, while USD100 of an invoice at PKR280 is PKR28,000. Reconcile the PKR500 difference to the actual linked FX accounting; do not alter the document history to remove it.
Do not assume a EUR note can be allocated to a USD invoice because cross-rate columns exist. The standard vendor note lookup normally restricts targets to the note currency. Do not bypass the picker or manipulate requests to force an unavailable target. Ask the accounting owner to choose a supported correction route. The separate cross-currency cash route is described in receipt and payment applications.
Record and apply a vendor payment
Save the payment for the actual supplier and bank, in that bank's currency, with the actual cash amount and its functional FX rate. Review the initially unapplied amount. Recording a payment is not sending a bank instruction or automatically allocating it to an invoice.
Use the eligible saved payment's transaction-line selection and application controls. Review Gross Open Amount, Projected WHT, Net Cash Payable and Functional Net Cash. Net Cash Applied is in the target transaction's currency; Payment Applied Amount consumes the payment currency. Review both amounts, the cross rate, dates and resulting residuals before applying once.
Where withholding is recognised at settlement, the protected system withholding record is separate from the cash application. Do not pay the gross amount and also deduct withholding a second time. Read the partial and cross-currency examples.
Correct an allocation or refund safely
| Need | Supported control and check | Avoid |
|---|---|---|
| Correct an unsaved form | Fix the entry before Save | A second document for the same supplier evidence. |
| Correct a saved editable invoice | Review its source matches, applications, locks and actual journals before authorised maintenance | Changing type, deleting history or bypassing purchase policy. |
| Correct an ordinary note allocation | Use its supported edit/remove controls where permitted; reopen source and target | Treating removal as cancellation of the note or physical return. |
| Correct a payment application | Correct/unapply the original cash application and inspect both balances | Deleting its protected system WHT allocation manually. |
| Refund an unused eligible payment amount | Use the original payment's supported refund controls and separate treasury authorisation | Assuming a supplier credit note proves cash was received. |
| Undo an inventory receipt/return | Use the permitted originating goods movement process and dependency checks | A GL plug that leaves stock quantities or GRNI wrong. |
After an uncertain save, locate the payment, application, note allocation and processing state before retrying. Existing applications and document dependencies can restrict commercial edits; do not create duplicates to avoid a lock.
Keep vendor evidence separate from Pakistan customer e invoicing
A supplier's tax invoice, your vendor accounting record and the supplier's authority-submitted document are different evidence. Retain the supplier's invoice/note and accepted reference where applicable. Do not send vendor documents through a customer FBR route merely because both are called invoices.
FBR and provincial service-tax treatment depend on the transaction and applicable jurisdiction. The official FBR provisions and the company's approved country process determine the applicable evidence; a successful RavenLedger save is not proof of statutory deductibility or authority acceptance.
Reconcile the complete purchase trail
Match supplier invoice/note references, PO/GRN/return quantities, inventory or expense destinations, GRNI clearing, supplier open items, payment applications and tax. Use the same company, supplier, locations, cutoff and currency across reports. Compare transaction-currency residuals separately from functional GL and FX.
Use the regular payables reconciliation checks, individual report parameters, inventory reconciliation and GL close controls. A zero supplier balance does not prove the bank statement is reconciled.
Resolve common invoice and note problems
| Symptom | Check |
|---|---|
| Service invoice requires an item | Select the approved non-inventory item and charge posting group; free text alone is not an item. |
| Vendor Debit Note increases the intended liability | Recheck the required business event: ordinary vendor notes reduce AP; an additional charge uses the supported invoice-like route. |
| PO or GRN source is absent | Supplier, company/location, approval/posting, remaining quantity, matching policy and earlier invoices. |
| Note target is absent | Supplier, currency, eligible invoice/charge type, current open amount and earlier allocations. |
| Payment cash and invoice gross differ | Withholding timing, existing notes/applications, currency and rounding; do not force gross cash. |
| System WHT is locked | Correct the originating payment application, not its protected child record. |
| Payment saved but invoice is open | Inspect its actual application and processing state; a payment reference alone is not settlement. |
Continue with fields and bulk entry
Vendor invoice and payment fields, customer invoices and notes, tax and currency applications, purchasing policy, purchase bulk guidance, vendor transaction template and bank reconciliation.
